Contents
A lot of people in our industry believe that the right time to look back on an event is once things have calmed down. Let the invoices settle, let everyone rest, then sit together in two or three weeks and talk it through with a clear head. It sounds mature and considerate, and I understand why it is the default.
In practice, that calm meeting almost never happens, and when it does, it is too late to be much use. By the third week the half hour queue at registration has become “a bit of a wait at the start,” the argument with the venue about the sound check has become “some technical issues,” and the people who saw the problems up close have scattered to other projects. The calm is real, but so is the forgetting, and the forgetting wins. A post-event debrief earns its time when it starts within a day, with a few honest lines from everyone who worked the event, and ends a few days later in a short meeting that turns those lines into one page next year’s team can use.
In my view this is one of the most expensive habits in the business and one of the least visible. Events everywhere are full of lessons learned on the day: the transfer that left late, the room block that ran out, the hostess team that had no briefing, the speaker who arrived without a presentation. If nobody writes them down, the same team, or a different one, pays to learn them again.
The useful version of the conversation happens while people are still tired
A post-event debrief is a structured conversation among the people who ran an event about what happened compared with what was planned. It is not the client report, which is written for someone who was mostly not there and usually wants to hear about event ROI, and it is not a celebration, although there is nothing wrong with celebrating separately. At its centre is one question: where did reality differ from the plan, and why? Sometimes the plan was wrong, sometimes the plan was right and the execution slipped, and sometimes something happened that nobody could have foreseen, in which case the question becomes how quickly the team noticed and reacted.
That is a different conversation from “what went well and what went badly.” It is less about feelings and more about decisions. Which assumption turned out to be false? Which supplier did exactly what the contract said but not what the event needed? Which piece of information arrived too late, and who was left waiting for it?
The freshest answers to those questions come on the night of the event or the next morning, when people are tired, a little irritated and very honest. I am not suggesting a full meeting at midnight during load out, which nobody would thank you for. A short message to everyone involved, asking what worked, what did not and what they would change, is enough to collect the raw material while it is still raw. The replies are often a single line, some of them grumpy, most of them true. The proper conversation can then take place a few days later with those notes on the table, once people have slept and the first figures against the event KPIs have come in, so the discussion is calmer without losing its detail.
Those notes are impressions, though, and part of the meeting’s job is to check them against what was recorded. If the registration team remembers the whole morning as slow, the scan times may show that the queue really came in one wave after two coaches arrived together, and that changes the fix completely: more staff at the desk would have helped a little, while spacing the coaches would have solved it.
The people who saw the problems are usually not in the room
A debrief with only the core team and the client is a debrief about what the core team and the client saw, which is a small part of the event. The people who know where things went wrong are often left out: the agency coordinator who looked after the day rate staff at the doors, the technical crew chief who knows why the second session started late, the hotel’s banquet captain who could tell you the menu change came after the kitchen had already ordered, the transfer company’s dispatcher, and the handful of university students who spent the day at the information desk answering questions nobody had briefed them on.
I understand why they are not invited. They are suppliers or temporary staff, the relationship ends with the event, and including them feels like extra work. Yet even a short phone call with the main suppliers, or three questions sent to the people who worked the floor, changes the quality of a debrief completely. When something serious happened on the day, a fall, a medical case, a crush at an exit, the circle has to widen further, and HSE’s guidance on managing an event in Great Britain recommends including the other agencies involved, such as the police and the local authority, in that kind of debrief. Temporary staff who were paid by the day, and in our business sometimes paid late, will say what they really think far more readily once they have been paid and thanked, so the order of those two things matters.
Suppliers also hold a second debrief that almost never gets asked for, the one in which the client and the agency hear what they did wrong. Hotels, venues, AV companies and transfer operators see many clients a year and know exactly which of your habits made their work harder: final numbers that came two days late, a stage design that changed after the rigging plan was approved, dietary requirements that arrived on the morning of the dinner. They rarely say it, because a supplier who criticizes a client might not be called again. Hotel sales and operations teams on the projects I have run are often very candid once the relationship is good and they believe you really want to know, and what they say about late changes and unclear briefs tends to be the cheapest improvement available, since it costs nothing except changing your own behaviour.
Blame ends the talking, and the run of show keeps it on track
In our business the agency, the organization company and the client are rarely equals in the room. The client pays, the agency wants the next project, the suppliers want to stay on the agency’s list, and a sponsor at the table wants to know whether the reasons it agreed to sponsor an event like this one were met. Every admission can sound like a confession that might cost a contract, and when a debrief turns into a search for whose fault something was, people stop talking. The supplier remembers that everything was according to the order, the agency remembers that the client changed the rooming list three times, the client remembers that the proposal promised something else, and everybody is partly right while nothing is learned.
A debrief is only useful if the people who carried the event are allowed to say what the plan got wrong.
What helps most is talking about the process instead of the person. Not who forgot to confirm the second bus, but how the transfer list was confirmed and where in that chain a change could get lost. The answer usually points to a gap that several people shared, and a shared gap can be repaired far more easily than a person can be replaced. A client who sets that tone at the start, and admits one of their own late decisions first, will hear far more from everyone else. Money is better kept in a separate room. A genuine dispute over an invoice or a missing service deserves its own conversation with the contract on the table, and when it leaks into the debrief, every supplier starts speaking like a lawyer.
Structure helps as well, and the best agenda is a document the team already lived by. The run of show, the minute by minute timeline of the event, follows the day in the order guests experienced it. Walking through it from the first arrival at the airport or hotel to the last transfer out, and asking at each point whether it happened as written, forces the conversation to cover the moments nobody thinks of as important: the time between sessions, the walk from the plenary hall to lunch, the hour after the official program ended. Those are often where guests had their worst experience, and they rarely come up when people discuss only what they remember as highlights. The rooming list, the transfer manifest, the registration report and the printed conference agenda do the same job for their own parts of the event, because each is a plan written in advance that can be laid next to what actually happened.
Next year’s team will only know what this year’s team wrote down
The final step is the one that makes the whole effort worth it: writing the lessons in a form someone else can use. Next year’s event may be run by a different person on the client side, a different agency, or the same agency with a new project manager, because in our business people move often. If what was learned stays in this year’s heads, it leaves with them.
The written result does not need to be long. One page that says what to repeat, what to change, which supplier to keep or avoid, which date or venue caused problems, and which decision should be made earlier next time is enough, as long as it uses plain language and specific details rather than phrases like “communication could be improved.” What worked deserves a line as well, because a new team that does not know why something went smoothly is perfectly capable of removing it to save money.
For the changes themselves I prefer a small table to paragraphs, since an empty column shows at once what nobody has taken on:
| What we found | What changes | Who owns it | How we will know |
|---|---|---|---|
| A flight change reached the agency but not the bus driver | The transfer list goes to the dispatcher directly, dated | Operations lead | The next manifest carries the date and the dispatcher’s reply |
| Final numbers reached the hotel two days late | The numbers deadline goes into the client’s own timeline | Client project owner | The hotel confirms on the agreed day |
| The information desk students had no briefing | A one-page brief and a venue walk before doors open | Agency coordinator | The brief exists before the next event starts |
Some rows cannot be closed in a week. Sponsor results and the final financial picture often arrive a month or more later, so the page should carry a date for a second, shorter look and a name next to it.
Where that page lives matters almost as much as what it says. In many companies the event folder sits on one person’s computer or in an agency’s shared drive that disappears when the contract ends. Keeping it with the client, next to the contract and the final event budget, and sending it to whoever opens the next request for proposals, is a small habit that saves a surprising amount of rediscovery a year later. No software or extra budget is required for any of it, only protection from the next project, which always arrives in the same week and always seems more urgent than looking back. A debrief that waits for a free afternoon usually does not happen at all.
The date for it can go in the calendar on the day the venue is booked.