Challenge

 

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.

People1 Posts6 Dribs0

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.

7 months ago ~ loleg

Event finish

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.

7 months ago ~ loleg

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.

7 months ago ~ roland

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).

7 months ago ~ roland

Start

JOINED

7 months ago ~ AnnaSigrist

Challenge shared
Tap here to review.

7 months ago ~ AnnaSigrist

Hack:Org:X v.5
Challenge
Posted 7 months ago by AnnaSigrist for Hack:Org:X v.5
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

The contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License. The application that powers this site is available under the MIT license.