How to write a post-event report for a paid event

A post-event report should tell you what the event earned, what it cost, what attendees experienced, and what you should change before running it again. Start with the financial result and the decision it supports, then show the records behind your numbers.

You don't need to document every social post or turn the night into a slide deck. You need an honest account of the event as a business. A busy room, happy comments, and strong ticket sales can all be true while the event leaves you with less money than planned.

This guide walks through the records to collect, ticket and attendance figures, revenue and costs, marketing results, attendee feedback, and a report template you can copy. We'll use one fictional paid event throughout, so you can see how the numbers connect.

Decide what the report needs to answer

Write for the person deciding whether to repeat the event, change the offer, or commit another deposit. That might be you, your business partner, or the person who approves your budget.

Put these questions on the first page:

• Did the event make the profit we planned?

• What explains the difference between the plan and the result?

• Which parts of the experience should we keep or fix?

• What needs to change before we commit to the next event?

Include the event name, date, reporting date, author, and whether the figures are provisional or final. A report prepared while supplier invoices and refunds are outstanding needs to say so. List each unresolved amount, who will confirm it, and when.

Set an initial review date before the event. You can capture operational lessons while everyone remembers the night, then confirm the financial result when the records are ready. Don't delay a useful debrief because one invoice is missing, and don't label estimated costs as final.

Keep the original budget intact. VisitScotland's event marketing guidance recommends evaluating performance against your original objectives, including ticket purchases and revenue. Changing the target after the event hides the very gap you need to understand.

Collect the records behind the report

The first thing you want to do is agree which record answers which question. An advertising dashboard, order export, check-in list, and bank statement can describe different parts of the same sale.

Use ticket records for paid tickets, ticket types, discounts, refunds, and complimentary tickets. Use check-in records for attendance. Use supplier invoices, staff records, and your expense records for costs. Use payment and bank records to confirm what has reached your account.

Gather sponsorship agreements and delivery records too. Use the agreement to confirm the promised payment and benefits. Use delivery records to check what you completed, and invoices and payment records to track what you billed and received. Include the costs of fulfilling your commitments.

Give each figure a source and a date. Someone reviewing the report should be able to trace ticket revenue back to the relevant orders without asking you to recreate the calculation. Keep detailed records accessible to the people who need them; the shared report can use totals.

If your event runs on Loopyah, ticketing and sales tracking already show sales by source, while QR check-in records who arrived. Use those records as inputs. Your job is to connect the ticketing result to supplier costs, sponsorship commitments, and the decisions about the next event.

For sales from several channels, check whether each export contains unique purchases or copies of purchases already recorded elsewhere. A sale shown in your ticketing platform and your payment provider is still one sale.

Apply the same rule to expenses. A venue deposit and the final venue invoice may refer to the same total booking cost. Record the full cost once, then show how much has been paid and what remains due.

Pick a reporting cutoff and save dated copies of the records you used. A refund processed tomorrow can change today's ticket total. If you update the report, explain what changed and retain the earlier version so people understand the difference.

Assign someone to resolve mismatches before the review meeting. If the door report shows a sale missing from the order records, investigate it. Was it entered manually, refunded, duplicated, or recorded against another event? An unexplained adjustment might make the totals agree, but it leaves the underlying problem for the next show.

Reconcile tickets sold with people who attended

Here's our example: a fictional evening event with usable capacity for 600 guests. Every amount in this example is illustrative USD. The figures are teaching assumptions, including the fees, and are not Loopyah prices or industry benchmarks.

The organizer reserves 20 places for complimentary guests, leaving 580 places available for paid tickets. Across the sales period, buyers purchase:

• 100 early-bird tickets at $30, bringing in $3,000.

• 350 standard tickets at $40, bringing in $14,000.

• 70 door tickets at $50, bringing in $3,500.

That is 520 individual tickets sold and $20,500 in ticket face value before refunds. Twenty standard tickets are then fully refunded and returned to available inventory. The organizer retains 500 paid tickets and $19,700 in ticket revenue.

At the event, 450 paid ticket holders and 18 complimentary guests check in. Total attendance is 468.

Those figures answer different questions. Paid ticket sales fill 86.2% of the 580 places available for sale. Attendance uses 78% of the venue's 600 guest places. Of the 520 valid paid and complimentary tickets remaining after refunds, 90% are checked in.

Write the denominator beside each percentage. A report saying "90% attendance" without explaining whether that means capacity, paid tickets, or all valid tickets makes the reader guess.

The room has 132 unused places: 80 unsold paid places, 50 paid ticket holders who did not attend, and two absent complimentary guests. That breakdown matters. Better reminders might address some no-shows; they won't sell the 80 unsold places.

Keep refunded tickets out of your no-show count. Check duplicate scans, re-entry records, ticket transfers, and manual admissions before treating scans as unique attendees. If the door team admitted people without recording them, state the limitation rather than inventing an exact attendance figure.

Our event KPI guide covers broader measurement choices. For this report, keep the numbers that explain demand, turnout, and money.

Show what the event earned and cost

Start with revenue after refunds, then list the event's costs. Keep your treatment consistent so you can compare this event with its budget and with previous editions.

For our example, assume all sponsorship income has been earned, all event costs are recorded, and there are no unresolved disputes. Figures exclude sales taxes collected for authorities. The example calculates an event operating surplus before income tax, financing costs, and any business overhead not allocated to this event.

State those boundaries in your own report. If you leave your own labor unpaid or omit a share of business overhead, the result is not the full profit of running your event business. Include a reasonable cost for that work when deciding whether the event is worth repeating.

Revenue and expenses in the worked example

The event keeps $19,700 of ticket face revenue after the $800 refund. It also earns $5,000 from sponsorship, giving total event revenue of $24,700.

The organizer's recorded expenses are:

• Ticket transaction fees: $900.

• Sponsorship transaction fees: $225.

• Venue and production: $12,000.

• Staff: $2,500.

• Marketing: $2,000.

• Sponsorship delivery: $1,000.

• Other event costs: $1,375.

Total costs are $20,000. Revenue of $24,700 minus those costs leaves an event operating surplus of $4,700, or about 19% of revenue.

Show what sits inside broad categories. "Other costs" should have a supporting breakdown, even if the first page stays short. In a real report, include items such as licenses, transport, equipment hire, and cleaning wherever they belong in your budget.

Avoid subtracting fees twice. Here, ticket revenue is recorded before the organizer's transaction fees, so the fees appear as expenses. If your starting figure already deducts those fees, reconcile it back to the same basis before applying this calculation.

Treat sponsorship delivery with the same care. The $5,000 sponsor payment is associated with $1,000 in fulfillment costs and $225 in transaction fees. It contributes $3,775 before shared event costs. That gives you a more useful basis for the next negotiation than the headline payment alone.

Keep cash sponsorship separate from goods or services supplied in exchange for benefits. A sponsor providing equipment may reduce a bill you would otherwise pay, but it doesn't put that equipment's advertised value in your bank account. Describe the arrangement and apply a consistent treatment agreed with whoever prepares your accounts.

If one production purchase benefits several events, explain the amount assigned to this edition. Don't load the entire purchase into one event and then compare it with another that carries none of the cost. The comparison should help you choose, rather than depend on where someone entered an invoice.

Explain the difference from budget

The original plan expected 550 paid tickets at an average retained price of $40. That meant $22,000 in ticket revenue, plus $5,000 in sponsorship. With planned costs of $19,500, the target surplus was $7,500.

The actual surplus of $4,700 is $2,800 below that target. The explanation is straightforward: ticket revenue came in $2,300 lower, and expenses were $500 higher. Sponsorship revenue matched the plan.

You can explain the ticket shortfall further. Selling 50 fewer tickets than planned accounts for $2,000 at the planned average price. The remaining $300 comes from the actual average retained ticket price of $39.40 across 500 tickets, below the planned $40.

Now the discussion has somewhere useful to go. Was the sales target too optimistic? Did the mix of ticket releases change? Which expense lines exceeded their allowance, and why? Check the supporting records before blaming the price, the campaign, or the venue.

In the example's expense breakdown, staff costs exceed budget by $300, marketing by $200, and sponsorship delivery by $200. Ticket transaction fees are $100 below budget, and other costs are $100 lower. Venue and production, and sponsorship transaction fees, match the plan. Those changes explain the $500 net overspend.

The next step is finding the cause. Extra staff hours might reflect a late finish, a roster change, or an unrealistic allowance. More sponsorship delivery spending might reflect an approved addition. Record the explanation supported by the paperwork, and distinguish a deliberate investment from an avoidable mistake.

Use the event budget guide to improve the next plan. Keep this report focused on explaining what happened.

Separate the event result from cash received

A bank deposit is not a profit calculation. Your payment provider may deduct fees, combine transactions, or still hold unsettled amounts when you prepare the report.

Stripe's payout reconciliation documentation explains how its automatic-payout reports connect payouts with underlying transactions and distinguish amounts still unsettled. Use the equivalent records available for your payment setup.

In our fictional event, $19,700 in retained ticket revenue minus $900 in transaction fees leaves $18,800 payable to the organizer. Suppose $17,300 has reached the bank and $1,500 remains with the provider at the reporting date. Those two amounts reconcile to $18,800.

That $1,500 is a timing difference, not another expense. Record its expected settlement separately, along with unpaid supplier bills and sponsor balances. The cash-flow forecast guide explains how to plan around those payment dates.

Assess marketing and attendee experience honestly

The financial result tells you what happened. Marketing records and attendee feedback help you decide what to investigate and change.

Compare channels using consistent definitions

Report each channel's spend, recorded purchases, and the basis used to credit those purchases. Specify whether a figure counts orders or individual tickets. One order containing four tickets should not quietly become four customers in the next paragraph.

Google's attribution guidance defines attribution as assigning credit to interactions before a conversion. Different models can distribute that credit differently. Include the model, date range, and reporting date so someone reading your report understands what the figures represent.

Keep the verified ticket-order total beside the marketing results. Don't add channel totals together when the systems may credit the same purchase. Report refunds consistently, and label tickets whose source is unknown.

For our event, the known marketing cost is $2,000. That expense alone doesn't tell us which campaign caused additional sales. To recommend a budget change, the report needs the channel records, the ticket revenue associated with them, and an explanation of their limits.

You can still make a practical decision with incomplete attribution. For example, investigate an expensive campaign with few recorded purchases, or test a stronger message for returning buyers. Describe the evidence and the next test instead of claiming certainty you haven't earned.

Keep comparisons fair. A campaign aimed at existing buyers and a campaign introducing the event to new people have different jobs. Show the audience and offer alongside the result. Otherwise, a cheap sale from someone already planning to attend can make a campaign look like the obvious place to spend everything.

Keep survey responses in proportion

Suppose the organizer emails all 468 checked-in attendees and receives 117 replies. That is a 25% reply rate for this fictional example. It is useful feedback, but it doesn't make the respondents representative of everyone who attended.

AAPOR's guidance on survey definitions explains why response rate alone cannot establish whether nonresponse error exists. People who reply may differ from those who don't.

Show the question, who received it, the reply count, and when responses were collected. Say "30 respondents reported a long entry queue" if that is what your results show. Don't turn it into "attendees hated the check-in" or an unsupported percentage of the whole audience.

Compare recurring comments with staff notes, admission records, and supplier reports. If the same issue appears in several records, explain that connection. If the evidence conflicts, keep the disagreement visible and name what you need to check.

Our post-event survey questions can help you collect feedback that leads to an actual change. Ask about the experience people had, then connect the answers to decisions you control.

Copy this post-event report template

Use the structure below in a document your team can edit. Keep the summary readable on its own and attach detailed records where reviewers can find them. You can adapt the same structure for a concert, paid conference, workshop series, or festival.

Event details and reporting status

Record the event name, date, venue, usable capacity, report owner, reporting date, and version. State whether the financial result is provisional or final. List missing invoices, unsettled payments, open refunds, and the person responsible for resolving each item.

Executive summary

State the financial result, the gap against budget, and your recommendation. For our example: "The event generated $24,700 in revenue and incurred $20,000 in costs, leaving a $4,700 operating surplus. This was $2,800 below budget. Review the sales forecast and cost overruns before confirming the next edition."

Ticket sales and attendance

List paid places available, ticket purchases before refunds, refunded tickets, valid paid tickets, complimentary tickets, and checked-in attendees. Add the ticket types and average retained ticket price. Define every attendance and sales percentage so the figures can be compared with the next event.

Financial performance

Show budget and actual revenue by source, then budget and actual costs by category. Explain the largest differences. Include the resulting surplus, the costs excluded from that calculation, and a separate note reconciling payments received with outstanding amounts. Link to the supporting records.

Marketing, feedback, and delivery

Record channel spend and attributed purchases with their reporting definitions. Summarize survey responses using the actual respondent count. List material operational problems, sponsor commitments delivered, and anything still owed. Include enough evidence to explain each finding without pasting entire dashboards into the report.

Decisions, owners, and deadlines

Finish with specific actions. For each one, record the finding, proposed change, owner, deadline, and evidence that will show whether it helped. Separate changes already approved from ideas that still need a decision. Make any conditions for repeating the event explicit.

Copy and complete this action record for each agreed change:

• Finding: [Describe the problem and link to its evidence.]

• Change: [Write the specific adjustment you will make.]

• Owner: [Name the person responsible for completing it.]

• Deadline: [Give a date or a clear decision point.]

• Approval needed: [Name the approver and any spending limit.]

• Success check: [State what you will measure next time.]

For example, the sales owner could revise the ticket forecast before the next venue deposit, using this event's retained sales by release. The approval question is whether the revised budget still meets the organizer's required return. At the next review, compare retained ticket sales and average price with that forecast. Keep the previous forecast visible so the comparison remains meaningful.

Review the report with the people who can change the next event

Send the report before the meeting and ask each owner to check their section. Finance should confirm the cost treatment and outstanding balances. Marketing should explain the campaign figures. The door lead should confirm attendance limitations, and the sponsorship owner should confirm what was delivered.

Use the meeting to resolve decisions, with the source records available when a number is challenged. Start with the gap against budget, then discuss the operational findings that matter most. Give each agreed change an owner who has the authority and time to make it happen.

Share the detail each recipient needs. A sponsor needs evidence of agreed benefits and any remaining commitments. Your internal team needs the costs and commercial result. Avoid sending the full financial report or attendee-level records to everyone simply because they were involved in the event.

For the next edition, carry approved changes into the budget, staffing plan, sponsor offer, or campaign brief. Add a short note linking each change to the finding that prompted it. Otherwise, the report becomes another file nobody opens when the next event gets busy.

Finish with a decision someone can act on

A report earns its place when it changes the next event. "Improve marketing" is too vague to assign. "Review the sales forecast before paying the next venue deposit" gives someone a job and a decision point.

For our example, the event produced a positive operating surplus but missed its target. That supports a closer look at the next budget. It doesn't automatically justify a bigger venue, deeper discounts, or more advertising.

Agree which assumptions need testing, which costs need renegotiating, and what result would make another edition worthwhile. Then carry those changes into the next plan and keep this report available for comparison.

Your post-event report should leave you knowing what you earned, why the result differed from the plan, and what you will do about it. That's the useful outcome after the last ticket has been scanned.