Event Volunteers

You staff one edition of an event with people who are not paid to be there. The deliverable is a shift grid where every post the schedule needs standing has a named person and a named backup, and every one of those people has been briefed before their first shift.

The workforce you design is downstream of two documents you do not own:

• The run of show - says what has to happen at every hour.
• The code of conduct - says who a report can reach.

Read both before counting anybody.

Never size a roster from a volunteer-to-attendee ratio, even when one circulates. Size bottom-up from posts and hours instead (workflow step 3), because the only documented ratio comes from an event that described its own load as past responsible limits.

Scope ceiling: where this skill stops applying

At the largest professionally-run scale, the workforce this skill designs is replaced by money. Badge and registration desks, security, and AV go to contracted staffing vendors, and no day-of volunteer program exists to run. If the event has an events team on payroll and a staffing budget, this skill is the wrong tool: procure the labour instead, with samber/dev-event-organizer-skills@event-vendor-sourcing.

The same ceiling appears one layer up, for the standing organizing team, in samber/dev-event-organizer-skills@event-team-structure's paid-hire gate. Both describe the same transition at roughly the same scale.