-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify Event Insurance and Waiver Solution #16
Comments
@djdubose You've already been thinking through some of this. I'd like to work with you to come up with a good insurance and waiver solution. Can you document here what you already know? |
Here's what I've got: That will cover everything Austin does, for each ACA member. We'll need to publish a schedule of our activities to the ACA insurance coordinator. We can update the schedule at any time. For one-off events like Nationals, participants can purchase insurance for the event for $5, or $4 if we buy at least 25 ahead of time. To name the YMCA as a covered entity we'd have to pay an additional $25. When guests come out to paddle with the Austin club we can have a pool of $4 event memberships we can either give out or ask guests to pay for. They'd need to sign a waiver before participating. This is all really standard stuff that covers our butts. Folks wouldn't be allowed to paddle with us in an organized fashion without being a member or having an event membership. |
Here's an email thread from October last year I had with Candy, their insurance coordinator:
|
They utilize smartwaiver.com which has support for more advanced flow than they're currently utilizing. I could integrate this into a payment process easily. |
There's a special ACA membership category for "Racing Athlete", and the list of sports includes Polo. That's the membership we'd want to have folks purchase, to show that the sport has some degree of participation. Looks to be the same price. |
We need to protect the YMCA and the club from any injury lawsuit that may arise from the event.
The text was updated successfully, but these errors were encountered: