Tracking hours across a multi-day festival

A multi-day festival amplifies every problem a single-day event has. The same volunteer might work three different shifts across three different days in three different roles. The crew leadership changes by day. The reporting question "how many hours did we run?" needs to be answerable both in aggregate and by day, by crew, and by role.

The setup ahead of the festival

Create worker groups for each crew (parking, registration, hospitality, security, kitchen). Assign volunteers to their primary crew so the kiosk picker scopes to their team. Create tags for each phase or day if you want per-day or per-phase slicing (day-1, day-2, day-3, or setup, execution, teardown).

Post a QR poster at every volunteer entry point, main gate, back-of-house, crew tent. Same QR everywhere; the worker's first-visit choice persists across the whole event because the cookie is scoped to your workspace.

During the festival

Volunteers tap in when they arrive, tap out when they leave. Auto-close protection catches forgotten clock-outs (very common at festivals, people leave through a different exit) and caps them at your configured cutoff. Flagged entries land in a review queue for crew leads or coordinators to confirm in the morning.

Watch the live dashboard to see who's currently on the clock. Useful for emergency headcount ("are all the registration volunteers actually here?") and for spotting no-shows in real time.

Post-festival

Filter the reports page by the festival's date range, pull totals overall and per tag/group. Export the CSV for your post-event report and for any per-volunteer follow-ups (thank-you emails, certificates, hours letters).

For per-volunteer hours certificates, see the free certificate generator. Back to the events hub.