Post-event analysis is useful only while the decisions it informs are still open, so the target
is a final number ten business days after the doors close. You get there by accruing open
supplier costs from the contract, reserving for refunds, labeling every figure as final,
accrued, or open, and giving each line one named owner. Pipeline attributed to the event is
reported on its own clock and does not reopen the close.

This page is the finance side of a post-event review: the close calendar and the treatment of
each open figure. For the document itself, use the
[post-event report template](https://eventiq.io/md/blog/post-event-report-template).

## Why does a six-week post-event analysis produce a number nobody uses?

Because the decisions a wrap number should drive have short windows. Whether to renew a sponsor
at the same rate, whether next year's venue block should shrink, whether the paid media budget
worked, whether a track is worth repeating: all are live in the month after the event and closed
by month three. By week seven marketing has started the next cycle and the board meeting where
the number mattered has happened.

In a May 2026 Global DMC Partners survey of 162 event professionals drawn from its own network,
71% of them in the US, 68% reported stakeholder pressure to prove the business impact of their
meetings and incentive programs
([Global DMC Partners](https://globaldmcpartners.com/2026/05/event-roi-measurement-gap-mice-industry/)).
A late wrap report is one way the proof misses the people who asked for it.

The accounting in a six-week close is seldom hard. The work is unscheduled and unowned, and
most of it is manual reconciliation across systems that do not share records.

## What are the four things that block the close?

Almost every delayed close traces to one of four causes, each with a standard treatment.

**1. Open supplier invoices.** The venue, the AV partner, and the general services contractor
often invoice a month or more after the event, and teams wait for the paper. Do not wait.
Accrue from the contract.

**Accrual estimate for an open supplier line = Contracted amount + Approved change orders + Known onsite additions (signed banquet event orders, overtime authorizations) − Amounts already invoiced**

**Accrual band = Accrual estimate ± Largest single unresolved change order**

An accrual with a stated band is a better input to a decision than a blank waiting for a PDF.
Set a materiality threshold with finance, and most supplier lines close on day 3.

**2. The refund window.** If your policy allows refunds up to 30 days after the event, your
revenue number is open until then. You need two fixes together: shorten the post-event window
to something defensible, and reserve for the remainder.

**Refund reserve = Registrations still inside the refund window × Average net price × Historical post-event refund rate**

**Revenue, net of reserve = Gross registration revenue − Refunds processed − Refund reserve**

The historical rate has to be your own: no published post-event refund benchmark is worth
importing. If you have not tracked it, start this cycle. Once the controller signs the reserve,
the net figure is final.

**3. Unfulfilled sponsor deliverables.** Revenue recognition on a sponsorship often depends on
delivery, and a missed placement or an unsent list holds a line open while people argue about
whether it was delivered, because nobody wrote down what was owed in a form that can be
checked. The fix is a deliverables register per sponsor, populated at signature and checked
off during the event. The same register feeds the
[sponsor report](https://eventiq.io/md/templates/sponsor-report) you send after the close.

**4. Attribution lag.** Pipeline influenced by the event keeps arriving for months, and that is
no reason to hold the close. Set a cut-off, state it, and report attribution on a separate
clock.

**Attribution cut-off rule.** The wrap report states pipeline and revenue attributed as at the
close date, using the attribution rule in force on the event date. A 90-day attribution update
is published separately and does not reopen the close. The financial result and the attribution
result are two documents with two dates.

Which rule you apply is a separate decision, covered in the
[event marketing attribution guide](https://eventiq.io/md/event-marketing-attribution).

## What can you publish before the ledger closes, and how should you label it?

Anything, provided the label tells the reader how much weight the figure will bear. What
destroys credibility is a figure that changes without the reader having been warned it might.
Use three labels, consistently.
| Label | Meaning | What the line must state |
| --- | --- | --- |
| FINAL | Signed off by the named owner. Will not change | Any later change is reported as a restatement |
| ACCRUED | Estimate from the contract plus approved change orders | A range and the largest unresolved item |
| OPEN | Not yet estimable or not yet earned | What is blocking it and the date on which it will be resolved |
Every line of the wrap report carries exactly one label, and the summary page states the share
of total cost that is final.

Two rules make labeling work. A report where every line is final on day 10 has been fudged:
expect two or three accrued lines and say so on the front page. And a restatement is announced,
never quietly applied. A finance committee will forgive an accrual that moved inside its stated
band. It will not forgive learning that a number it approved changed without notice.

## Who signs off on each line?

One named person per line. Committee sign-off is how a close slips from ten days to thirty,
because it turns a decision into a meeting.
| Line | Owner | Evidence required |
| --- | --- | --- |
| Registration revenue, gross | Registration manager | Platform report tied to the ledger |
| Refunds and refund reserve | Controller | Processed refund list and historical rate |
| Comped registrations (count) | Event director | Comp category register |
| Sponsorship revenue recognized | Sponsorship lead | Deliverables register |
| Exhibit and booth revenue | Sales director | Contract schedule |
| Venue and catering cost | Operations lead | Contract and signed banquet event orders |
| AV and production cost | Production lead | Contract and change orders |
| Marketing and paid media | Marketing lead | Ad platform spend reports, invoices |
| Staff and travel cost | Finance analyst | Expense system export |
| Attributed pipeline (separate document) | Marketing operations | Attribution rule and cut-off date |
Sign-off means the owner has seen the evidence named in that row.

## How do you protect the calendar from the event itself?

By moving work before the event. A ten-day close is mostly won in the two weeks before doors
open, when the team has time and nobody is exhausted.

Four things belong in that window: the contract schedule the accruals will be built from, the
sponsor deliverables register, the definitions document covering registration revenue, comps,
and in-kind, and the wrap report template itself, with every line and owner filled in and the
figures blank. A team that walks out of the event with a blank template and named owners is
doing data entry in week one. A team that starts designing the report in week one is doing
design, reconciliation, and diplomacy at once, which is how six weeks happens.

## Example: a ten-business-day close calendar

Take an association annual meeting with 1,800 registrations, $1,500,000 of registration,
sponsorship, and exhibit revenue, and $900,000 of direct cost. The event ends on a Thursday and
day 1 is the following Monday. All figures are hypothetical.
| Day | Owner | Activity | Output |
| --- | --- | --- | --- |
| 1 | Registration manager | Freeze registration data, take final counts | Counts, FINAL |
| 1 | Operations lead | Collect signed banquet event orders and change orders | Cost evidence pack |
| 2 | Controller | Tie registration platform total to ledger receipts | Gross revenue, FINAL |
| 2 | Sponsorship lead | Review deliverables register per sponsor | Fulfillment status |
| 3 | Finance analyst | Build accruals from contract schedule | Cost lines, ACCRUED |
| 3 | Marketing lead | Pull final paid media spend by channel | Media cost, FINAL |
| 4 | Controller | Calculate refund reserve | Net registration revenue, FINAL |
| 4 | Sponsorship lead | Resolve two disputed deliverables | Sponsorship revenue status |
| 5 | Finance analyst | First full draft P&L with labels | Draft wrap report |
| 6 | All line owners | Line-by-line sign-off against evidence | Signed lines |
| 6 | Event director | Reconcile comp category register | Comp count, FINAL |
| 7 | CFO | Review exceptions and accrual bands | Exception list |
| 8 | Finance analyst | Clear exceptions and revise where needed | Near-final P&L |
| 9 | Head of events and CFO | Joint read, agree the headline narrative | Approved report |
| 10 | Head of events | Publish to leadership and line owners | Wrap report issued |
| +90 days | Marketing operations | Attribution update, separate clock | Attribution update |
Two days carry the schedule risk. Day 2 fails when the registration platform total and the
general ledger receipts do not agree, which they rarely do on the first attempt: refunds
processed after the export, processor fees netted on the deposit, partial payments, and currency
differences all pull them apart. Budget the whole of day 2 for that. Day 6 fails when a line
owner has not been told they are one, which is why the sign-off map goes out before the event.

This report splits the sign-off map into 17 lines, and on day 10 it publishes 14 of them as
final. Two are accrued: AV and production at $128,000 ± $9,000 on an unresolved overtime claim,
and general services at $61,000 ± $4,000 on one unsigned change order. One is open, a
sponsorship line of $45,000 held against a deliverable due the following month.

The summary page states that 79% of total direct cost is final ($711,000 ÷ $900,000) and 97% of
revenue ($1,455,000 ÷ $1,500,000). It gives revenue less direct cost as $600,000 with a stated
range of $542,000 to $613,000. The low end assumes the open line is never earned and both
accruals land at the top of their bands. The high end assumes both land at the bottom.

When the AV invoice arrives in week five at $131,500, it lands inside the stated band of
$119,000 to $137,000. The line moves to final with a note, total direct cost becomes $903,500,
and the result becomes $596,500, inside the range leadership already read.

## What to do this quarter

- Write the definitions document for registration revenue, comps, in-kind, and direct cost,
  and get finance and events to sign the same version before the next event.
- Build the sign-off map with named owners and required evidence, and send it to those owners
  before doors open.
- Assemble the contract schedule for accruals in the two weeks before the event.
- Shorten the post-event refund window if policy allows, and start tracking your own
  post-event refund rate so you can reserve and stop waiting.
- Separate the financial close from the attribution update: two dates, two documents, and a
  written cut-off rule.
- Publish the ten-day calendar and book the day 9 joint read before the event.

## Common questions

### Is ten business days realistic for a large trade show?

For the financial close, usually yes. The blockers are the same four and the treatments scale.
What does not compress is exhibitor space reconciliation after substantial onsite booth
changes. Budget two extra days for that line and let the rest close on time.

### Will auditors accept accrued lines in a wrap report?

The wrap report is a management report, not a statutory statement, and accruals with stated
bands and evidence are ordinary practice. Agree the materiality threshold and the labeling
convention with your controller, so the treatment is consistent across events.

### What if the number looks bad and leadership wants to wait?

That is the strongest argument for the labels. A report that says which lines are final and
which are accrued shows that the remaining uncertainty is bounded and small, so waiting buys
nothing.

### Should a post-event review include attendee survey results?

Include them if they are ready, and do not let them hold the close. In MPI's Meetings Outlook
for Q2 2026, built on 163 responses from MPI members, 47% named low survey response rates among the biggest
challenges in measuring the human impact of events
([MPI](https://www.mpi.org/docs/default-source/meetings-outlook/meetings-outlook-q2-2026.pdf)).
The [post-event survey questions](https://eventiq.io/md/blog/post-event-survey-questions) page covers how to raise
the response.

## Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run: event platforms
(Cvent, Zoom, Swapcard), CRM (Salesforce, HubSpot, GoHighLevel), and marketing (Google Ads, Meta
Ads, LinkedIn Ads, Mailchimp, Google Analytics). Platforms with an API outside that list are
connected on request.

For the close, it holds records behind three lines of the sign-off map. Registrations from
Cvent carry their date, ticket type, and price where the platform provides them, so the count
and the ticket-type mix behind the registration line can be read on the event. Marketing spend
that your team enters or imports from CSV sits by event and channel with the author of each
change. The ad platform connections bring campaign name and status only. Salesforce deals carry
stage, amount, and close date, linked to the event through a campaign relationship a person
confirms, which is the raw material for the attribution update.

None of the 12 connected platforms is an accounting system, so supplier invoices and the general
ledger stay outside EventIQ. The cost figures it holds are the budget fields your team enters,
and the ROI it shows is arithmetic on that budget and the revenue target you enter. It does not
accrue, reserve for refunds, or produce a provisional close figure, and it does not send
reports on a schedule. The day 2 tie-out, the status labels, the sign-offs, and the day 10
issue stay with your team.

[Book a demo](https://eventiq.io/#early-access) to see registration records, entered budget fields, and linked
Salesforce deals on a sample event, in a 20-minute demo.

---

HTML version: https://eventiq.io/blog/post-event-close