Governance and stakeholder ownership
How to set up an event escalation ladder
A problem sat with one person for a week, and by the time the chair heard about it the options had narrowed.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
An escalation ladder names the levels a problem moves through, the trigger for moving up each level, and the time allowed before it moves. A problem escalates because a limit was reached, not because someone failed.
Agree it before the event is under pressure, and write it on one page.
Choose triggers you can measure
Triggers work better when they are specific. Examples: a decision is overdue by two working days, a cost change exceeds the limit in your decision-rights matrix, a supplier or speaker withdraws, or a stakeholder disputes scope.
A trigger can also be a question, such as: does this change what attendees are told? If yes, escalate.
Build three or four levels
- Level 1: the task owner tries to resolve it within a set time, for example one working day.
- Level 2: the workstream lead or project lead decides within the limits they hold.
- Level 3: the chair or event owner decides, with finance consulted if money is involved.
- Level 4: the full committee or board, only for decisions outside delegated authority.
Set time limits and name deputies
Each level needs a response time and a named deputy. Without a deputy, a holiday or travel day stalls the ladder.
Write times in working days and state who confirms receipt, so that escalation does not depend on someone noticing a message.
What the ladder does not cover
Safety incidents, medical emergencies and security matters follow the venue's and your organisation's own emergency procedures, and those are for the competent people to define. Ask the venue and your safety adviser how emergencies are reported, and keep that separate from this ladder.
Legal and data protection questions should go to your own legal or data protection contact, with a note in the ladder of who that is.
Keep the record
- Log each escalation in the decision log: what, level, owner, due date.
- Review the log after the event to see which triggers fired and whether the limits were right.
- Update the ladder when committee members change.
Worked example · Fictional example
A speaker withdraws three weeks out
Fictional organisation and timings. Limits and days are illustrative.
A fictional healthcare administrators' association has a keynote speaker withdraw on a Monday. The programme lead (Level 1) has one working day to propose two replacements.
Because a replacement would change printed material and the speaker fee line, the project lead brings it to the chair on Tuesday (Level 3). The chair decides on Wednesday, finance is informed, and the change is logged. The full committee only learns at its next meeting because the decision stayed inside delegated authority.
| Level | Who | Time allowed | Moves up when |
|---|---|---|---|
| 1 | Programme lead | 1 working day | No acceptable replacement identified |
| 2 | Project lead | 1 working day | Printed material or fee line changes |
| 3 | Chair, finance consulted | 2 working days | Outside delegated authority |
| 4 | Committee | Next meeting or special meeting | Not applicable |
Use this yourself
Event escalation ladder template
Copy and fill. Keep it to one page and attach it to your terms of reference.
- Triggers (overdue by __ working days; cost above __; supplier or speaker withdrawal; scope dispute; attendee-facing change):
- Level 1 owner, deputy, time allowed:
- Level 2 owner, deputy, time allowed:
- Level 3 owner, deputy, time allowed:
- Level 4 body and how a special meeting is called:
- Who confirms receipt of an escalation:
- Where escalations are logged:
- Matters handled outside this ladder (emergencies, legal, data protection) and who handles them:
- Review date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The committee is small and the chair responds quickly.
- You already have a clear delegation of authority.
- The event is short and has few suppliers.
Outside planning help earns its fee when
- Several organisations are involved and nobody is sure who can overrule whom.
- Problems tend to reach the chair late and in a tangle.
- You want someone to run the ladder day to day and keep the log.
Want someone to run the ladder with you?
A conference project lead can draft the escalation ladder with your chair, take Level 2 decisions within limits you agree, and bring the rest to the right level with options and a recommendation. Your committee keeps the decisions that are its own.
Questions organisers ask
How many levels do we need?
Three or four is enough for most professional events. More levels slow decisions and blur ownership.
Should every problem be escalated?
No. Only when a trigger is met. Task owners should solve what they can within their own limits.
Who writes down an escalation?
The person escalating, in a decision log entry, with the time. The receiver confirms receipt.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.