[hackerspaces] Classes and Liability

[bownes]

Interesting question. Short answer, ask your lawyer. If you don't have one, get one. 

One of the things we have everyone who walks in the door do is sign a waiver. It protects the space but I doubt it would protect an instructor. 

On the insurance issue, make sure you have Director and Officer insurance. Cheap and it keeps your officers from getting personally dinged for something that happens. 

Bob

> On Dec 20, 2013, at 11:00, Joshua Pritt <ramgarden at gmail.com> wrote:
> 
> That's a good idea to make it into a donation I think.  You can recommend an amount to donate like listing the cost of materials etc. to give them an idea of how much to pay to cover how much they think it's worth.
> 
> 
>> On Fri, Dec 20, 2013 at 10:49 AM, Pete Prodoehl <raster at gmail.com> wrote:
>> 
>> At our space we've been talking about teaching classes, which is something we want to encourage, but here's the tough part...
>> 
>> If I teach a class and charge money for it, I've been told that I will be liable if someone decides to sue because I am a "paid" instructor.
>> 
>> I believe we can get around this by not accepting any money, or by asking people to make a donation to the space, but as soon as an individual takes any monetary compensation, they are opening themselves up to some legal risk.
>> 
>> Our space has an insurance policy, and it covers things that happen at the space, but an individual charging for classes does not fall under our plan.
>> 
>> How do others deal with this?
>> 
>> (Note: We're based in the United States... land of the litigious!)
>> 
>> 
>> Pete
>> 
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
> 
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20131220/b5c64a2a/attachment.html>