Shift plan

The grid that turns a volunteer team into coverage. Stations run down one side, the blocks of the day run across the top, and every box where that station has to be covered gets a name and a call time. Boxes that cannot go dark, so check-in during the arrival rush, anything holding cash or equipment, or the moment the whole room wants to be watching the same thing, get a second name as backup. The count of filled boxes is the recruiting number, which is why this course never quotes a volunteer-to-attendee ratio: no credible published ratio exists, and a grid tells you what people are doing as well as how many of them you need.

Source: Standard volunteer-event practice, stated most directly in the DevOpsDays organizing guide, which advises assigning “on duty” shifts so one person is not the single point of failure for last-minute decisions, and in Dewan Ahmed’s DevOpsDays Halifax account, which advises creating “a schedule outlining who is doing what to ensure a fair distribution of tasks” so that quieter volunteers do not end up on the registration desk all day. The absence of any credible staffing ratio is a documented gap in this course’s source review (industry map §8, item 1).

First used in: 2.7 · The volunteer engine.