Event fallback readiness evidence
The plan says there is a backup, and nobody has checked who holds it or whether it can actually be used.
The short answer
A fallback is ready when it has a trigger, a named person who can invoke it, something concrete to switch to, and evidence that the thing exists and can be reached on the day.
A line in the plan that says backup available is an intention. Evidence turns it into a ready option, or shows you that it is still only an idea.
Which dependencies need a fallback
List the things the event cannot proceed without, or would have to change publicly without: the main venue space, a key speaker, a presentation file, the registration list, the microphone and display chain, a catering slot, a transport arrangement.
You do not need a fallback for everything. Decide which dependencies are critical, then give each critical one an owner and a fallback or an agreed decision not to have one.
What counts as evidence
| Fallback idea | Evidence that it is ready | Not enough |
|---|---|---|
| Spare copy of a presentation file | Copy opens on a second device; location and owner named | It is on someone's phone |
| Alternative speaker or chair | Person has agreed in writing and has the brief | We could ask someone |
| Offline copy of the attendee list | Current copy exists, access is limited to named people | The platform will be fine |
| Alternative room or layout | Venue has confirmed in writing that it is available on the day | They said they might be able to |
| Supplier substitute | Written confirmation from the substitute, with scope | We know a company |
| Printed programme or signage backup | Copy exists and checked against the master | It can be printed if needed |
For each fallback, record five things
- Trigger: the observable condition that starts the switch.
- Decision owner: the person authorised to say go.
- The alternative itself, with its limits stated.
- Evidence and the date it was last checked.
- Who is told, and how, when it is used.
Check the fallbacks work together
- Take the critical dependencies from your pre-launch checklist.
- Fill the table for each one and attach the evidence.
- Read the table with the programme owner and look for fallbacks that depend on the same person or the same device.
- Run one fallback end to end, such as opening the spare file on another laptop, and note any problem.
- Add unresolved fallbacks to the decision log, and show the table at final sign-off.
What this page does not cover
Emergency procedures, evacuation, first aid and crowd safety are for the venue and the competent authorities. Ask them what plans exist and request a copy you can file. A fallback for programme content is not an emergency plan.
Worked example · Fictional example
A seminar organiser checks four fallbacks
Fictional organisation and figures, for illustration only.
A fictional trade body checks four fallbacks for a 150-person seminar. The spare presentation files are on a USB drive held by the project coordinator and opened successfully on a second laptop, so that one is ready.
The alternative chair has agreed in writing. The offline attendee list exists but is held by one person who is away on the day. The alternative room has not been confirmed in writing. Two of the four are marked not ready and given owners and dates.
Use this yourself
Fallback readiness table
Copy one row per critical dependency. Leave Evidence blank until you can show it.
| Critical dependency | Trigger | Decision owner | Fallback | Evidence held | Last checked (date, name) | Who is told | Ready? |
|---|---|---|---|---|---|---|---|
| Ready / not ready / no fallback by decision | |||||||
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have a short list of critical dependencies.
- Each fallback can be shown in a few minutes.
- One person can decide on the day.
Outside planning help earns its fee when
- Fallbacks depend on suppliers, venue and speakers who do not talk to each other.
- Nobody is clearly authorised to invoke a fallback.
- Several fallbacks rely on the same person or the same equipment.
Want fallbacks reviewed before sign-off?
A planning diagnostic can review which of your critical dependencies have a named owner, a trigger and evidence, and which are only intentions, then list what to settle first. It does not assess safety or plan emergency response. Those stay with the venue and the competent authorities.
Questions organisers ask
How many fallbacks do we need?
One for each critical dependency, or a recorded decision to accept the risk of not having one. More than that adds work without making the event more ready.
Who should be allowed to invoke a fallback?
One named person per area, with a deputy. The point is that nobody has to ask a committee during the event.
Is a fallback the same as an emergency plan?
No. A fallback keeps the programme running when something fails. Emergency and safety plans are for the venue and the relevant authorities to set and share.
When should fallbacks be tested?
Test the ones that are simple to test, such as file copies and contact details, before final sign-off. For the rest, confirm the arrangement in writing.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.