Checklist
What Is an Event Checklist?
A Worked Example, Phase by Phase
A checklist is not a list of everything you can think of. It is a short list of the things that are easy to miss and expensive to miss, read at a specific moment by a specific person.
The short answer
An event checklist is a written list of verification items, grouped by phase and assigned to an owner, used to confirm that work has actually been completed rather than merely planned. A useful checklist is short, phrased as something observable, has one owner per item, and is read at a defined trigger point — not kept as a general reference document.
Why most checklists are ignored
The usual failure is length. A 200-item document covering everything from venue search to post-event survey is a project plan, not a checklist, and nobody reads a project plan at 06:00 on load-in day. The second failure is ambiguity: items like 'confirm AV' cannot be answered yes or no, so they get a tick that means nothing.
| Weak item | Why it fails | Stronger version |
|---|---|---|
| Confirm AV | No way to tell if it is done | AV supplier has returned the signed schedule and the equipment list matches the run of show |
| Check catering | Who checks, and against what | Final headcount sent to caterer by the contract deadline, confirmation received in writing |
| Make sure venue is ready | Not observable | Room walked at 07:00 against the floor plan; chair count and stage position verified |
| Prepare registration | A project, not a check | Badge stock printed, two scanners charged, backup paper list printed |
Point
Write every item so that the answer is unambiguously yes or no when you look at the thing itself. If verifying it requires a conversation, it is a task, and tasks belong in the plan rather than the checklist.
A worked example, by phase
Split by phase so each list is short enough to read in one sitting. These are examples to adapt, not a universal list — delete anything that does not apply to your event, and add what your own post-event reviews have taught you.
Phase 1: Before you commit
- Objective written in one sentence, with the measure that will tell you it was met
- Date checked against competing industry events, public holidays and school terms in every market your audience travels from
- Budget envelope approved, with the approver named
- Venue capacity confirmed against the forecast headcount, including the seating layout you actually intend to use
- Venue access days confirmed in writing, including build and strike times
- Insurance requirements confirmed with the venue before signing
Phase 2: Locking suppliers and content
- Every supplier contract signed, with the exclusions read and listed
- Power requirement calculated and confirmed against what the venue supplies
- Internet requirement specified: wired drops, bandwidth, and whether it is dedicated
- Speakers confirmed in writing with date, time, duration and travel arrangements
- Content freeze date agreed with the people capable of breaking it
- Accessibility provision booked: captioning, interpreters, step-free routes verified in person
- Permissions and licences applicable in your jurisdiction identified, with the responsible owner named
Phase 3: Two weeks out
- Run of show complete, version numbered, and walked through aloud with the crew
- Final headcount sent to the caterer; locked number recorded
- All collateral at the printer, with delivery address and receiving contact confirmed
- Crew call times issued, with site address, entrance, and parking or transport details
- Every speaker has received their time, duration, arrival point and contact on site
- Risk list reviewed: for each item, the trigger, the response, and who decides
- Emergency procedures read and understood by the on-site team, including the venue's own
Phase 4: Load-in and show day
- Room walked against the floor plan before the crew starts
- Power distribution tested under load, not just plugged in
- Every microphone tested from the position it will be used, with fresh batteries fitted and spares counted
- Every speaker deck opened on the show machine, in the room, on the actual screen
- Registration dry run completed with a real badge and a real scan
- Sightlines checked from the back row and from the worst seat in the room
- Accessible seating, routes and facilities verified in place
- Radios distributed, channels agreed, and a radio check completed with every holder
- Crew briefing delivered, covering the run of show version, the cuttable segments, and who makes decisions
Phase 5: Strike and after
- Lost property collected and a return route agreed
- Hired equipment counted back against the delivery note before the truck leaves
- Venue walked with the venue manager and any damage documented with photographs on the day
- Final numbers captured: attendance, no-shows, and anything your objective is measured on
- Supplier invoices reconciled against quotes, with variances explained
- Debrief held within a week, while memory is accurate
Note
The items that earn their place are the ones that have bitten you before. After every event, add the two things that went wrong and delete two items that nobody has ever answered 'no' to. A checklist that only grows stops being read.
Rules for a checklist that gets used
- 01One owner per item. A shared item is an unowned item.
- 02Observable phrasing. The verifier should be able to look at something and answer.
- 03A trigger, not a vibe. Each list is read at a defined moment: at contract signature, at two weeks out, at crew call.
- 04Short enough to read aloud. If a phase list exceeds roughly twenty items, split it or move items into the plan.
- 05Read-and-confirm, not read-and-do. Checklists verify completed work. Doing the work is the plan's job.
- 06A single current version. Versioned, dated, and owned by one person who may edit it.
A checklist is cheap insurance against the failures you already know about. It cannot protect you from the ones you have never had.
Running the check
How you run through the list matters as much as what is on it. Three practices make the difference.
- 01
Read it out loud, with two people
One reads the item, the other confirms. Silent self-checking is how people tick items they intended to do rather than items they did. This is standard practice in aviation and theatre for the same reason.
- 02
Verify at the object, not at the desk
'Microphone tested' means someone stood where the speaker will stand and spoke into it through the main system, not that the supplier said it was fine.
- 03
Record exceptions in writing
Where an item is genuinely not applicable, write why. Where it failed, write what you did instead. A list of ticks tells you nothing afterwards; a list with three annotated exceptions tells you exactly where the event was fragile.
Sizing the on-site checks
Some checks scale with the size of the event and need a time estimate of their own. Microphone checks are the usual example. If testing one microphone from its working position takes three minutes and you have twelve microphones, that is 12 × 3 = 36 minutes of sound-check time, before any content rehearsal. Replace three minutes with your own measurement, and schedule the result as a row in the run of show rather than assuming it fits in the gaps.
Point
Build the checklist read-throughs into the schedule as named items with durations. A check that has no time allocated is a check that gets skipped when the build runs late — which is precisely when it matters most.
Key takeaways
- A checklist verifies finished work. It is not a task list and not a project plan.
- Phrase every item so the answer is visibly yes or no; one owner per item, no shared ticks.
- Split by phase and keep each phase short enough to read aloud at a defined trigger point.
- Read it with two people, verify at the object, and write down every exception.
FAQ
Frequently asked questions
A short, phase-specific list of verification items, each with one owner, read at a defined moment to confirm that work has actually been completed. It differs from a project plan, which tracks the work itself. Checklists are deliberately short because they are read under time pressure, often on site.
Short enough to read aloud in one sitting — roughly twenty items per phase is a practical ceiling. Beyond that people skim, and skimming defeats the purpose. If a phase keeps growing, split it into two triggers or move the items that are really tasks into your plan.
The checks that are both easy to miss and expensive to miss: room walked against the floor plan, power tested under load, every microphone tested from its working position, every deck opened on the show machine in the room, a registration dry run, sightlines from the worst seat, radios distributed and checked, and the crew briefing delivered.
One person edits it; many people run it. Typically the producer owns the document and each phase list is run by whoever is accountable for that phase — the production manager at load-in, the registration lead at doors. Shared editing produces competing versions, which is worse than having no list.
After each event, add the things that went wrong and remove items nobody has ever answered 'no' to. A checklist that only accumulates eventually becomes unreadable and stops being used, so deleting is as important as adding. Keep the annotated exceptions from each run as the evidence for what to change.