Risk identification and contingency
How to design an event risk register
Your committee has asked for a risk register, and the first draft is a long list of worries with no owners and no next step.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A useful event risk register has one row per risk, written as a sentence a committee member can read: what might happen, what would trigger it, who owns it, what you will do beforehand, what you will do if it happens, and when it is next reviewed. Keep it short enough that the owners read it.
A register lists risks and decisions. It does not certify that an event is safe. Safety, security and emergency planning conclusions belong to the venue and other competent parties. Use the planning readiness diagnostic to see which planning decisions are still open, and the contingency scenario calculator for budget reserves.
Write risks as events, not worries
A worry such as weather is too broad to own. A risk is specific: the keynote speaker's flight is cancelled the day before, or the registration system is unavailable on the opening morning.
Group the risks by workstream, such as programme, speakers, venue, suppliers, registration, finance, communications and people, so each group has a natural owner.
Columns that make the register usable
| Column | What to write | Why it matters |
|---|---|---|
| Risk statement | What might happen and what it would affect | Makes it specific enough to own |
| Trigger or early sign | What you would see first | Gives owners something to watch |
| Owner | A named person, not a committee | Without an owner nothing happens |
| Prevention | What you do beforehand, with a date | Turns the risk into a task |
| Contingency | The decision or step if it happens, and who decides | Avoids deciding under pressure |
| Assumptions | What you assumed, such as supplier confirmed in writing | Shows what to recheck |
| Review date | When the row is next looked at | Keeps it current |
| Residual note | What remains after the response, and who accepted it | Records who accepted what remains |
What belongs to someone else
- Crowd safety, fire, structural, electrical and emergency evacuation matters belong to the venue and its competent staff or authorities. Record the question and the written answer, not your own conclusion.
- Medical, security and legal matters belong to the relevant competent party.
- Your register can record that the question was asked, who answered, and the date, so gaps are visible.
Sequence
- Run a one-hour session by workstream and list specific risks.
- Cut the list to those where a decision or action is possible.
- Assign each risk a named owner and a review date.
- For each, write a prevention step and the contingency decision, with who decides.
- List what is out of your control and send the questions to the venue and competent parties.
Worked example · Fictional example
A register for a one-day members' forum
Fictional organisation and figures, for illustration only.
A fictional association drafts 14 risks across five workstreams. One row reads: the keynote speaker cancels within a week. Trigger: no travel confirmation by a set date. Owner: programme chair. Prevention: confirm travel in writing. Contingency: a named alternative speaker and a decision date. Assumption: the speaker's agreement is in writing.
Six rows concern venue safety. The secretariat does not score them. It records the written questions sent to the venue and marks each as waiting for answer.
Use this yourself
Event risk register template
Copy one row per risk. Leave safety rows as questions to the competent party.
| Risk statement | Trigger or early sign | Owner | Prevention and date | Contingency and who decides | Assumptions | Review date | Residual note and who accepted |
|---|---|---|---|---|---|---|---|
| Keynote speaker cancels within a week | |||||||
| Registration system unavailable on opening morning | |||||||
| Key supplier fails to deliver | |||||||
| Venue safety question (for the venue to answer) |
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single event with a small committee and a secretariat that can chase owners.
- Venue and supplier contracts are in place and the risks are mostly about your own decisions.
Outside planning help earns its fee when
- Many workstreams, suppliers or venues, and open planning decisions nobody owns.
- The register will be reviewed by a board or auditor and needs a clear method.
- You want contingencies written into supplier requirements and a decision log.
Want help turning the register into decisions?
A planning diagnostic can review which planning decisions are open across your workstreams and give a prioritised action list, with risks and contingency questions written up for the people who own them. It does not approve safety or compliance. Send your draft register, even if it is only a list.
Questions organisers ask
How many risks should a register hold?
As many as an owner can act on, often ten to twenty for a one-day event. A long list nobody reads is less useful than a short one with owners.
Do we need to score every risk?
Not to start. Scoring needs agreed assumptions, covered in risk scoring assumptions. Owners and next steps matter first.
Can the register show an event is safe?
No. It records risks, owners and questions. Safety conclusions come from the venue and other competent parties.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.