How to build an event standby personnel plan
Someone will be late, ill or pulled away on the day, and you want a named person ready before that happens.
The short answer
A standby personnel plan names the people held in reserve, the posts they can step into, the trigger that calls them in and the point at which they are released. It is a short roster, not a second full crew.
Build it around the posts that would stop the event if left empty, and confirm each standby person is trained for those posts.
What standby is for, and what it is not
Standby covers a gap in a post that matters: a no-show at registration, a runner who falls ill, a speaker liaison stuck in traffic. It is not a way to hide an under-resourced plan.
If the base plan already needs every standby person to be at work, the plan has a capacity gap that standby will not close.
The decision sequence
- Pick the posts that cannot stay empty, using your staffing plan as the source.
- For each, ask how long the event can run without that post before a real problem appears. This decides how fast the standby person must arrive.
- Choose standby people who can do those posts. Check training with the competency checklist.
- Decide where each standby person waits: on site, nearby on call, or remote. Remote standby cannot cover physical posts.
- Write the trigger for each: who may call them in, by what message, and who covers if the first standby is also needed.
- Agree the release point, such as after the plenary, so standby people know when they are free to go.
- Brief standby people as fully as the base crew. They should arrive knowing the layout, the contacts and the handover notes.
On site, on call or remote
| Standby type | Suits | Limits |
|---|---|---|
| On site, in a ready room | Posts where a gap harms guests within minutes, such as registration or door control. | Uses a person for the whole period and needs a place to wait. |
| On call, nearby | Posts that can wait a short while, such as a runner or a second liaison. | Arrival time depends on distance and traffic. Ask the person for an honest estimate. |
| Remote, by phone or message | Coordination, supplier chasing or document tasks. | Cannot cover a physical post. |
Who authorises the call-in
Name one person who can activate standby, normally the supervisor or the project lead, and one deputy. Without that, either nobody calls or three people call the same person.
Record each activation with a time and reason. It tells you afterwards whether the plan is thin.
Common pitfalls
- Standby people are named but never briefed, so they arrive unable to do the post.
- The same person is standby for two posts and both gaps appear at once.
- Standby is assumed to include the supervisor.
- No release point, so people wait all day without knowing.
- Standby volunteers are unpaid and untold what they may claim. Settle expenses and meals before the day.
Worked example · Fictional example
A 300-person members' seminar with two standby people
Fictional organisation and figures, for illustration only.
A fictional fintech association runs a one-day seminar with eight crew. The planner marks registration and the speaker ready room as posts that cannot stay empty. Registration can run with one fewer person for about fifteen minutes before queues build, so a nearby standby is enough there. The ready room cannot be left unattended in the 30 minutes before a session.
Two standby people are named: a trained registration volunteer waiting in the crew room until 9:30, and a runner on call who is a short walk from the hall. The supervisor and the deputy may activate them by a single message. Both are released after the first plenary, and the supervisor logs one activation, a late runner, which shows the plan held.
Use this yourself
Standby roster
Copy this and fill one row per protected post. Add rows if a standby person covers more than one post.
| Protected post | Standby person | Waits where | Trained on post? | Trigger | Who may call | Backup if also needed | Release point |
|---|---|---|---|---|---|---|---|
| Registration desk | On site / On call / Remote | Yes / No | |||||
| Speaker ready room | On site / On call / Remote | Yes / No | |||||
| Hall door | On site / On call / Remote | Yes / No | |||||
| Coordinator | On site / On call / Remote | Yes / No |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your crew is small, known to each other and the event is a single session.
- Posts are few and the base plan already has some slack.
- The supervisor can brief standby people in person.
Outside planning help earns its fee when
- The base plan has no slack and you suspect standby would be a hidden extra crew.
- Standby has to cover specialist posts that nobody on your team has done.
- Several days, several rooms or multiple sources of crew make the call-in rules hard to keep consistent.
Want someone to hold the call-in decisions?
A conference project lead can set up the standby roster with you, brief the standby people with the same pack as the crew and hold the activation decisions on the day. Which posts are protected and how much reserve to carry remain your calls; the project lead coordinates the people and handover notes.
Questions organisers ask
How many standby people do we need?
There is no fixed ratio. Start from the posts that cannot stay empty and how quickly each gap causes a problem, then name one person per protected post, sharing only where two gaps are unlikely at once.
Can the supervisor be the standby?
Not safely. The supervisor is already the person handling problems. A supervisor who covers a post has no capacity left to decide.
Do standby people need to be paid?
That is a matter for your organisation, the supplier contract or the volunteer agreement. Settle it before the event and tell each standby person what applies.
What if the standby is used up by 10am?
Treat that as a signal. Ask the supervisor to log it, call the next backup and tell the organiser, because the plan may need more people for the rest of the day.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.