The Post-Event Report: 12 Sections That Make Next Year Easier (With a Template)

Most events end with a tired conversation in a parking lot and nothing written down, which is why the same mistakes reappear the following year and why sponsors ask questions nobody can answer in March. A post-event report fixes both, and it does not have to be long: twelve sections, most of them numbers you already have, written within two weeks while the event is still fresh. This is the template, with where each number comes from, who reads it and the one decision each section is supposed to produce. It is written for community festivals, conferences, competitions and one-night events in Canada, and it pairs with the event analytics metrics guide for the numbers themselves and the budgeting guide for the plan you are reporting against.

Key takeaways

• Write it within two weeks. After a month the detail is gone and nobody will reconstruct it.
• Every section should end in a decision or a number next year's plan can use, not a paragraph of description.
• Report against the plan, not in isolation: attendance against capacity, revenue against budget, spend against line.
• Funders, sponsors and boards want different cuts of the same data; write one report and pull extracts rather than writing three.
• The report is worth more than the debrief meeting, because the meeting is forgotten and the document is not.

The 12 sections

1. The one-page summary

Written last, read first. Five lines: what the event was, attendance, net financial result, the single biggest win and the single biggest problem. Board members and sponsors read this and nothing else, so it carries the numbers you most want remembered.

Decision it produces: whether the event runs again, and at what scale.

2. Attendance against capacity

Tickets sold, tickets scanned, no-show rate, walk-ups, comps, and all of it against the capacity you planned for. The gap between sold and scanned is the number most organizers have never calculated and the one that changes catering, staffing and site planning next year.

Where it comes from: your ticketing platform's sales report and check-in report. On Eventist the check-in report sits beside the sales report, so scanned against sold is one screen rather than two exports.

Decision: next year's capacity plan and no-show allowance.

3. Revenue against budget

Gross ticket revenue by tier, add-ons, vendor and booth income, sponsorship, grants, bar and merchandise, donations. Beside each, the budget figure and the variance. Then net: after platform fees, card processing, refunds and chargebacks.

Where it comes from: the platform's revenue and finance reports for tickets and add-ons, your own ledger for everything else.

Decision: which revenue lines to grow and which to stop pretending will happen.

4. Costs against budget

Every line you budgeted, what it actually cost, and the variance with a one-line reason. Include the costs that were free because a volunteer absorbed them; next year that volunteer may not exist.

Decision: the line items to renegotiate, and the contingency percentage for next year.

5. Sales pace

When the tickets actually sold: by week, by tier, against your price steps. This is the most predictive section in the report, because next year's marketing calendar is built from it. Note the spike at each price deadline and the share sold in the final two weeks.

Where it comes from: the registration timeline or sales-by-date report.

Decision: the tier ladder and the on-sale calendar for the next edition; the festival pass pricing method turns this into prices.

6. Marketing attribution

What sold the tickets: email, each influencer and partner link, paid social, organic, the calendars and directories, the door. Include cost per channel where money was spent, and the recovered carts as their own line because they cost nothing.

Where it comes from: influencer and referral link reports, discount code usage, page views and funnel data, and your ad platforms.

Decision: where the marketing budget goes next year, and which partners get thanked first.

7. Gate and operations

Entry times by hour, queue lengths, peak arrival, which gates were busy, scanning problems, how long the line was at its worst. Add the operational notes: load-in, power, weather, anything that ran late.

Where it comes from: the check-in report by time and gate, plus the run of show marked up during the event.

Decision: gate staffing, scanner count and door-open time.

8. Vendors, sponsors and exhibitors

Who came, what they paid, what they reported selling, whether they want to return, and what they asked for that you did not have. Sponsors get their own subsection with the deliverables you promised and the evidence each was delivered: photos of signage, post reach, mentions, attendee numbers.

Decision: next year's booth pricing and the sponsorship package; the vendors and sponsorship guide has the structure.

9. Staff and volunteers

Roles filled, shifts covered, no-shows, hours worked, which positions were under-staffed and which were unnecessary. Note the three people who made it work and the one role nobody wanted.

Decision: next year's staffing plan and the volunteer recruitment target.

10. Incidents and complaints

Every incident logged, medical calls, ejections, refund requests and the reasons, accessibility complaints, lost property, anything the police or the municipality were involved in. Write it factually and completely: this section is what your insurer wants after a claim and what the city wants with next year's permit application.

Where it comes from: the incident log kept during the event, the refund log, and the inbox.

Decision: the safety plan and the permit application for next year; the security guide explains why the log matters.

11. What the attendees said

Survey results with the response rate, the two or three things people loved, the two or three complaints that repeated, and any quotes worth reusing in marketing. Send the survey within 48 hours while the event is fresh; a short survey with four questions gets ten times the responses of a long one.

Decision: the programme and site changes for next year, and the testimonials for next year's page.

12. Decisions and owners for next year

The section that justifies the report. Every conclusion above turned into a specific change, with a name and a month: "book the second entrance by March", "move the beer garden away from the kids' zone", "raise the early bird to $120 and cap it at 500", "hire two more gate staff for 6 to 8 p.m.".

Decision: the whole plan for the next edition, before anyone has forgotten why.

The template

Copy this structure into a document and fill it in:

When to write it

• Within 48 hours: send the attendee survey, thank staff, volunteers, vendors and sponsors, and pull the sales and check-in reports before anything is archived.
• Within one week: hold the debrief with the section owners in the room and fill the operational sections while memories are accurate.
• Within two weeks: finish revenue and costs (once refunds and final invoices have settled) and write the summary and the decisions.
• Within one month: send the sponsor and funder extracts, and put every decision into next year's plan with a date.

If the event ran on a platform that holds the tickets, the schedule, the staff and the gate, most of sections two to nine are exports rather than reconstructions. On Eventist the sales, check-in, coupon, influencer, attendee and page-view reports export to CSV or Excel, and a custom report builder answers the question the standard reports do not; the festival revenue reporting comparison covers how other platforms handle the same job.

Frequently Asked Questions

What should be in a post-event report?

Twelve sections: a one-page summary, attendance against capacity, revenue against budget, costs against budget, sales pace by week and tier, marketing attribution by channel and partner, gate and operations data, vendor and sponsor performance with deliverables evidence, staff and volunteer coverage, incidents and complaints, attendee survey results, and a list of decisions for next year with owners and dates.

How soon after an event should you write the report?

Send the attendee survey and pull the reports within 48 hours, hold the debrief within a week while the operational detail is accurate, and finish the financial sections and the summary within two weeks, once refunds and final invoices have settled.

What do sponsors want in a post-event report?

Attendance, audience demographics if you have them, evidence that each promised deliverable was delivered (signage photos, post reach, mentions, booth traffic), and what their link or code sold. Pull it as a short extract from the main report rather than writing a separate document.

How do I measure whether an event was successful?

Against the plan, not against a feeling: attendance versus capacity, net revenue versus budget, no-show rate, cost per attendee, sales pace against your price steps, survey scores and repeat-purchase intent. The event analytics metrics guide has target ranges for each.

What is the difference between a debrief and a post-event report?

The debrief is the conversation, usually within a week, where the people who were there say what happened. The report is the document that survives it, with numbers attached and decisions assigned. Events that only do the debrief repeat themselves.

How long should a post-event report be?

Two to six pages for a community event, longer only if a funder requires it. One page of summary, three or four of numbers with short commentary, and a decisions list. Nobody reads twenty pages, and the sections that get used are the ones with figures in them.

The report is the cheapest thing you can do to make the next edition better, and the only artefact of this year that will still be useful in February. Write the twelve sections, assign the decisions, and put the dates in the calendar before the adrenaline wears off. If you want sections two through nine to be exports rather than archaeology, the Eventist events platform keeps the tickets, the gate, the staff and the vendors in one reporting suite.