The most useful event document I own has never been read by a single guest.
It’s the January post-mortem for San Francisco’s New Year’s Eve party, which I produced for eight consecutive years. Every January I sat down while the bruises were still visible and wrote down what broke, what almost broke, who saved us, and which vendor I would trust with a bigger slice of the night. By the later years it was a document people actually opened. I’ve called it the real deliverable before. I meant that literally.
The event debrief guides that rank for this are mostly about the meeting, and they’re good on it. Hold it a week or two out, once everyone has slept. Invite the people who worked the floor as well as the department heads. Appoint a chair and someone to take notes, open with what went right, walk back through the goals, then get into budget variance and attendance. I agree with every word! What they skip is the reader. Each of them treats the post-mortem as a conversation about the event that just ended, and I write mine as a letter to whoever produces the next one, which on a recurring event is usually me, eleven months later, having forgotten almost all of it.
Write for the Stranger Who Runs It Next Year
Year one runs on adrenaline.
Year two is when you find out what was skill and what was luck. The checklist you swore you’d write down in January is gone. The loading dock has a new manager who has never heard your name, and the floor plan that felt completely obvious at 2 a.m. in December reads like a stranger’s handwriting by spring, even though the stranger was you.
So the test I hold a post-mortem to is simple. Could a capable person who has never seen this event pick the document up in October and run the night from it? If they couldn’t, what I’ve written is a diary, and diaries are lovely, but nobody produces a countdown from one.
Draft It Before Anyone Has Rested
Seven to fourteen days out is a sensible time for the meeting. For the first draft it’s much too late.
By day ten the story has been tidied. People remember the ending, which was fine, and forget the forty minutes before it, which were not. The small things evaporate first, like which door the caterer really used or who was holding the key to the closet with the spare extension cords, and they’re exactly what a stranger needs.
Load-out does a lot of this work for you if you let it. When we handed Pier 39 back after the Tostitos activation at Super Bowl 2026, the site was photographed clean and the vendor invoices and damage assessments were filed within 48 hours. Those photos and that paperwork are a first draft hiding in plain sight. Pin them to the document before they scatter into five different inboxes.
The Section the Guides Leave Out: What Almost Broke
Every template I read boils down to two questions, what worked and what didn’t. Near misses fall straight through the gap between them, because from the audience’s seat nothing happened.
The Target Runis my favorite example. A breakout speaker walked on stage with no screen, because the sales rep had forgotten the TV. I drove to Target, came back with one, and the session went on. Nobody in that room knew anything had gone wrong. In a what-worked, what-didn’t meeting, that session gets a happy little check mark, and the actual lesson disappears with it: the fix was me in a car, and I will not always be ten minutes from a Target. The line that belongs in the post-mortem is a dull one about who confirms the screen, and by when.
I’d argue the almost-broke list is worth more than the broke list. Real failures get remembered without anyone writing them down, because people were embarrassed and embarrassment is memorable. The near miss gets one exhale in a hallway and is gone by Monday.
It took me about a dozen golf tournaments at Presidioto see this. Early on, the day after a tournament, I honestly couldn’t tell you which decisions had mattered and which had been wasted motion. Once I knew the five moments that carried the day (arrival check-in, the shotgun horn, the turn, the scoring tent, the awards), the morning-after question got much easier. Did any of those wobble, even slightly, even if nobody noticed?
Who Saved Us, by Name
The guides ask what your vendors thought of the event. Fine. I care more about which person at which vendor saved the night, and I write their first name down.
A recurring event compounds through people. The house electrician who answers your text in November. The security lead who already knows where your pinch points are before you finish describing them. By year five the caterer picks up at 11 p.m. because you once picked up for them, and that relationship lives in exactly one place besides your phone, which is this document. A first-year producer rents a venue. An eighth-year producer has a bench, and the bench is written down.
The same section tells you whose slice of the night gets bigger next year, and whose gets smaller. Be honest there. Be kind, too, since documents travel.
Every Rule Needs Its Reason
Champagne poured and staged by 11:40. That’s a line from my New Year’s Eve run of show, and on its own it looks fussy, like the kind of thing a sensible new producer would push to 11:50 to save the bar team ten minutes of standing around. The reason is what protects it: in the last hour of the year the crowd compresses, the noise doubles, and every errand takes three times as long as it did at nine.
I learned this opening a second sunglasses shop, where I had to hand everything I did by instinct to someone else and watch which pieces survived the trip across town. Instinct doesn’t travel. A checklist does, provided the person holding it understands why each line is there. So every rule in my post-mortem gets its because, and anything that got cut live goes straight into next year’s “If late” column, decided calmly, months ahead.
Leave Room for the Number
Attendance, budget variance and survey scores are all ready within a week, and they belong in there. For a B2B event the number leadership will actually ask about arrives a lot later. At Arxan, after RSA Conference, every lead had a 30-60-90 day follow-up cadence, and I didn’t open the spreadsheet to measure the show’s ROI until the end of Q2. A post-mortem closed in week two has a hole exactly where the most important answer goes. Leave a heading for it, put a date next to the heading, and go back.
On Tone
Write it so the people who saved you would be glad to read it.
The Takeaway
An event post-mortem is a set of instructions for a stranger. Draft it before anyone rests, give the near misses their own section, name the people who carried you, attach a reason to every rule, and leave a dated hole for the pipeline number. Then hold the meeting the guides describe, with a document already on the table, and watch how much faster it goes.
If your team runs an event that has to happen again next year, let’s talk. I’ll ask to read last year’s post-mortem before I ask to see the venue, and if there isn’t one, I’ll be very happy to write the first.