Thanks for posting this question and discussing it with us today: I hope this exchange between organizers will lead to best practices and ideas being more widely shared.
Participant management & no-shows
As Opendata.ch team, we organize and support hackathons in various fields and locations. A continuous challenge that we face is the management of participants both in terms of the tool (we currently use Hitobito as CRM) as well as regarding the high no-show rates. We are curious to learn from other organizers how they handle these issues and what tools / processes they use.
People | 1 | Posts | 6 | Dribs | 0 |
---|
Event finish
In addition, we have limited seats and we remind people in the last newsletter to cancel if they cannot show up because it occupies somebody else's seat.
At BaselHack we have a no show rate of ±10%. It used to be much higher, until we introduced a 20CHF fee for joining that participants get back at the hackathon (participation is free).
Start
JOINED
Challenge shared
Tap here to review.
Hack:Org:X v.5
I'm testing integration between Dribdat and Pretalx for next week's DINAcon event in Bern, and I think the topic of easy payment processing & frictionless refund would be a great way to reduce no-shows in the future. With thanks again to Roland for the excellent advice.