How to Run an Event Washup (And Actually Make Your Next Event Better)

The event is over. The venue is packed down, the client is happy, and your team is exhausted. The last thing anyone wants to do is sit in another meeting.

But the washup — the post-event debrief — is where the real value of your experience gets captured. Without it, the things that went wrong quietly repeat themselves. The things that went brilliantly get forgotten. And next time, you're starting from roughly the same place you started this time.

A well-run washup takes an hour. It makes every subsequent event measurably better. Here's how to do it properly.

What Is an Event Washup?

A washup (also called a post-event debrief or post-mortem) is a structured conversation held after an event where your team reviews what happened, what worked, what didn't, and what to change next time.

The goal isn't to assign blame. It's to capture institutional knowledge while it's still fresh — before the details fade, before team members move on, and before the same problems show up at your next event.

Done well, a washup becomes the foundation of a continuously improving event operation. Done poorly (or skipped entirely), it's just a missed opportunity dressed up as a meeting.

When to Hold It

Timing matters. Hold your washup too soon and people are too tired to think clearly. Hold it too late and the detail is gone.

The sweet spot for most events is 24 to 72 hours after the event ends. People have had time to recover and reflect, but the specifics are still sharp. For large or complex events, 48 hours is usually ideal.

If your team is spread across locations or suppliers are involved, a written survey sent immediately after the event (within 24 hours) — followed by a call a few days later — works well.

Who Should Be in the Room

Your washup is only as useful as the perspectives in it. For most events, you want:

The event coordinator or manager — who owns the debrief and takes notes
Any in-house team leads — AV, catering, front-of-house, production
Key suppliers — particularly those with operational roles (caterer, AV lead, venue manager if external)
The client contact — for private events or corporate bookings, even a short separate call with the client captures feedback you won't get internally

Not everyone needs to be in the same session. You can debrief your internal team separately from suppliers, and gather client feedback independently. The important thing is that all of it gets collated in one place.

The Five Questions Every Washup Should Answer

Structure your washup around these five questions. They cover everything without letting the conversation drift.

1. What went well?

Start here, always. It sets a constructive tone, surfaces things worth repeating, and makes sure positive learnings don't get lost in the rush to fix problems.

Ask people to be specific. "The setup went well" is not useful. "The staggered supplier arrival schedule meant nobody was waiting on each other" is something you can put in a template and use again.

2. What didn't go as planned?

This is the honest review of what fell short — not to criticise individuals, but to identify system failures, gaps in the run sheet, unclear ownership, or supplier problems.

Encourage the team to separate what happened from why it happened. "The speeches ran 20 minutes over time" is what happened. "There was no hard stop time in the run sheet and no one was empowered to intervene" is why it happened — and that's what you can fix.

3. What surprised us?

Things that weren't anticipated — good or bad. A higher-than-expected turnout, a supplier who arrived unprepared, a moment that landed much better than expected. Surprises are data. They tell you where your planning assumptions were off, and where there's potential you haven't been exploiting.

4. What would we do differently?

The forward-looking question. For every problem identified in question 2, there should be a proposed change here. This is where the washup produces its actual value — actionable improvements that feed back into your process for next time.

Keep the changes specific and assignable. "Better communication" is not an action. "Add supplier briefing notes to the run sheet by T-minus 7 days, owned by the event coordinator" is.

5. What should we stop, start, or keep doing?

A simple framework for closing out the conversation. It forces the team to make decisions rather than just observations, and produces a clear list of commitments.

The Washup Template

Use this as your agenda and note-taking document. Circulate it to attendees before the session so people come prepared.

Event: [Name] Date of event: [Date] Washup date: [Date] Attendees: [Names and roles]

What went well? (List specific moments, decisions, or systems that worked)

What didn't go as planned? (What fell short, and what was the underlying cause?)

What surprised us? (Anything unexpected — positive or negative)

What would we do differently? (Specific changes for next time, with an owner and deadline)

Stop / Start / Keep

Stop: [Things to remove from our process]
Start: [New things to introduce]
Keep: [Things to do exactly the same]

Action items:

Action	Owner	By when

Getting Honest Feedback From Your Client

Internal washups are valuable, but they have a blind spot: your team can only see what your team sees. The client's experience of the event — how it felt to be a guest, whether the flow made sense, whether they'd book again — is different information entirely.

A short post-event client survey or call does three things. It catches problems your team didn't notice. It gives you a testimonial or case study if the event went well. And it shows the client that you care about improving, not just completing.

Keep it brief. Five questions is plenty:

Overall, how satisfied were you with the event?
Was there any moment where things didn't meet your expectations?
Was there anything that exceeded your expectations?
How did you find communication with our team in the lead-up?
Is there anything you'd want us to do differently if you booked again?

Send it within 24 hours of the event, while the experience is still vivid. Response rates drop sharply after 48 hours.

Turning Washup Findings Into Process Changes

A washup that produces a list of observations and nothing else is a wasted hour. The output needs to feed back into something — your templates, your run sheets, your supplier briefing documents, your onboarding process for new team members.

Here's a simple way to think about it. Every finding from your washup falls into one of three buckets:

Fix it in the run sheet. A lot of event problems come down to gaps or ambiguities in the run sheet — missing time buffers, unassigned roles, unclear cues. These are the easiest fixes. Update your run sheet template so the problem can't recur.

Fix it in the briefing. Some problems happen because suppliers or staff weren't given the right information before the event. Add the relevant detail to your supplier briefing template or pre-event checklist.

Fix it in the selection or contracting process. If a supplier underperformed or a piece of equipment failed, the fix might be upstream — in who you book or what you specify in a contract.

The action items from your washup should always have an owner and a deadline. Otherwise they sit in a document and nothing changes.

How Your Run Sheet Helps the Washup

One of the most useful documents to have in your washup is the run sheet from the event — specifically, the version your team actually used on the day, with any handwritten notes or annotations on it.

The run sheet is a record of what was supposed to happen. Comparing it to what actually happened is one of the fastest ways to surface gaps and timing issues. If the speeches were supposed to start at 8:45 PM and actually started at 9:10 PM, the run sheet tells you where the 25 minutes went — and where you need to build in more buffer next time.

If your team made adjustments on the day, noting those on the run sheet (even a quick scribble) means the washup has evidence to work from, not just memory.

Making the Washup a Habit

The difference between event teams that improve and those that plateau is usually this: the improving teams have made the washup a non-negotiable part of their process. It's not something they do when they have time. It's something that's booked before the event happens.

A few things that help make it stick:

Book the washup before the event. If it's already in the calendar, it happens. If it's "something we'll organise after," it usually doesn't.

Keep it short. One hour is enough for most events. Two hours maximum for very large or complex ones. If your washups are running long, the problem is usually a lack of structure — use the five questions above to keep it focused.

Circulate the notes within 24 hours. The action items need to land while the motivation is still there. Notes that go out a week later are notes nobody reads.

Review last time's washup at the start of next time's planning. Before you start building a run sheet for a new event, open the washup notes from the last comparable event. What did you say you'd do differently? Did you do it?

Wrapping Up

The washup is the event industry's equivalent of the training debrief — the moment where experience gets converted into improvement rather than just history. It doesn't require a lot of time, but it does require consistency and structure.

Start with the five questions. Assign an owner to every action item. Feed the findings back into your run sheets and templates. And book the next washup before the current event even starts.

The best event coordinators aren't the ones who never have problems. They're the ones who have fewer problems each time.

A good run sheet makes the washup easier — because you have a clear record of what was planned versus what actually happened. Build your run sheet for your next event with Run Sheets, and start every debrief with the evidence right in front of you. Get started free →