The debrief almost nobody does

4 September 2026

The event is over, it went well, everyone is tired and grateful. This is the moment almost every project quietly ends. It is also the only moment where the next edition gets decided, and skipping it has a cost that shows up a year later, when nobody remembers why.

Why it gets skipped

Not out of laziness. It gets skipped because of when it falls.

The debrief lands in the worst possible week: everyone is exhausted, the client is happy, and there is already another project waiting. Reopening something that went well feels like looking for problems that nobody is asking about.

And there is a second reason, less comfortable. A debrief done properly turns up things that could have gone better, and after a successful event there is little appetite for that conversation.

So the project closes on the good feeling, and everything learned stays in the heads of the people who were there. Twelve months later some of those people have moved on.

The three questions

I close every project with the same three, and I keep them in this order on purpose.

The word that does the work

Why is what separates a debrief from a set of minutes.

"Move the registration desk" is an instruction. In a year nobody will remember whether it was because of the queue, the draught from the door, or because the desk blocked the caterers' route, and someone will move it back for a perfectly good reason of their own.

"Move the registration desk, because with two hundred arrivals in thirty minutes the queue reached the entrance and the caterers could not get through" is a decision that survives. It carries its own justification, so the next person can weigh it instead of guessing at it.

This is the single thing that makes the difference between a debrief people read and a document that gets attached to an email and never opened.

The numbers half

Alongside the conversation there is the reconciliation, and it is not the same exercise.

Invoices get checked against what was agreed, line by line, and the final cost picture gets closed. What comes out is not just a total: it is which lines were underestimated and by how much. That is the part that makes the second year's budget more accurate than the first year's, and there is no other way to get it.

It is also the moment where the year's surprises become visible as a pattern rather than as isolated annoyances. Build-up overtime, changes after the final headcount, shipping and storage: they rarely look like much on their own, and they add up to double digits.

What makes a reconciliation useful, though, is having something to compare it against. An overrun on set-up hours means nothing in isolation. It means something when you know what that line usually runs to in that kind of venue, in that part of the country, at that time of year. That comparison is not available in a spreadsheet: it comes from having closed the same kind of project many times in the same places, and from having written down each time what the real number turned out to be.

It is the least visible thing I carry from one project to the next, and probably the most useful.

What an agency gets out of it

If you are agency side and you run the same event annually, this is the document that stops each edition starting from zero.

It is also, in practice, what you hand to the next producer. Event knowledge is mostly held by people, and people move. A debrief is the only part of it that stays with the project instead of with the person.

And there is a version of this that is worth saying plainly: the debrief is the least glamorous thing I do and the one clients thank me for most, usually a year later, when we are planning the next edition and the answers to half the questions are already written down.

The cost side of the reconciliation is in the corporate event budget. The document the numbers are checked against is in the document that keeps a project on course. Closing the project properly is part of the event management service.