Event reporting is the process of turning the records your event systems already hold into a
small set of reports, each written for a named reader on a fixed schedule.

The event team,
the marketing lead, finance, the sponsor, and the board all ask about the same event, and each
of them needs a different page. Reporting trouble usually starts in one of two places: two
readers are handed the same word with 2 definitions behind it, or two figures on one page
were pulled at different moments. Arithmetic is rarely the culprit.

This page is about the process: who receives what, when, and from which records. The metrics
belong to the [event marketing analytics](https://eventiq.io/md/event-marketing-analytics) guide, and the fields of
the report you write after the event belong to the
[post-event report template](https://eventiq.io/md/blog/post-event-report-template).

## Who reads event reports, and what does each reader need?

Start from the reader. A report exists to support a decision someone is about to make, and
that decision says which figures belong on the page and which belong in an appendix. Keep a
figure when changing its value would change what the reader does with it.
| Reader | What they need | How often | Where the numbers come from |
| --- | --- | --- | --- |
| Event team | Registrations by source against the plan, check-ins, session activity, follow-ups still unassigned | Weekly while promotion runs, once after the event | Registration platform, engagement tools, campaign platforms |
| Marketing or department lead | Events side by side: spend by channel, registrations, attendance, deals linked to each event campaign | Monthly, and again at quarter close | Ad platforms, registration platform, CRM campaigns |
| Finance | Spend against approved budget, revenue recognized, and the cost definition each figure was built on | On the accounting close, monthly or quarterly | Budget file, invoices, marketing spend by event and channel, CRM |
| Sponsor or exhibitor | What the contract promised, what was delivered, and the audience the sponsored activity reached | Once after the event, again before renewal | Per participant engagement records, fulfilment checklist, the agreement itself |
| Board or executive committee | A handful of numbers, the same ones from last year, the difference, and the decision in front of them | Annually, or on the meeting cycle | The 4 reports above, after their definitions are agreed |
The event team reads for operations. They need registrations broken out by the source that
produced them, because the only useful week to fix a channel is the week it underperforms.
Their report can be rough, often a weekly
[event KPI dashboard](https://eventiq.io/md/templates/event-kpi-dashboard). It can carry a figure that will move, as
long as it says so.

The marketing or department lead reads to compare. One event on its own tells almost nothing;
12 events with the same columns tell you where the budget did work. This is the reader who
suffers most from definitions that drift between events, because comparison is the entire
purpose of the page.

Finance reads for the ledger. Their question is whether the money moved the way the approved
plan said it would, in the period it was booked to. Whether the event went well is somebody
else's page. A figure that cannot be tied back to an invoice, an expense record, or a closed
deal is one finance will set aside, correctly.

The sponsor reads for the contract: deliverables, the audience that showed up, and a year
over year comparison they can put in front of their own finance team. The
[event sponsorship ROI](https://eventiq.io/md/event-roi/event-sponsorship-roi) guide covers what that report
holds. The board
reads for a decision: continue, change the scale, or stop. Directors ask whether this year's
figure was calculated the way last year's was before they ask which direction it moved, and
the [board report template](https://eventiq.io/md/templates/board-report) sets out the page they read it from.

## How often should each report go out?

Report cadence follows the cadence of decisions. Ask what the reader can actually decide this
week, and set the schedule to that. The pacing report exists because registration is still
open and promotion can still change; once the event is over, a weekly version of it changes
nothing and costs an hour each time.

That gives 4 rhythms. Weekly while promotion runs, for the team. Once after the event, for
everyone, on a date you set in advance rather than when the last export arrives. Monthly or
quarterly for the [event portfolio dashboard](https://eventiq.io/md/event-portfolio-dashboard), aligned with the accounting close so finance is reading the
same period you are. Annually for the board, or whenever its cycle falls.

One report is worth waiting for. Deals connected to an event keep closing after it ends, so a
report issued the Monday after the doors close shows an incomplete pipeline picture by design.
Agree a follow-up window with sales, state it on the page, and say when you will read the same
event again. The [event ROI](https://eventiq.io/md/event-roi) guide covers what that second reading needs.

Data arrives on its own schedule, which is a separate matter from how often you publish.
Records reach a reporting layer anywhere from minutes to several hours after the platform
writes them, depending on the source, and no cadence you choose makes a source arrive faster.
What that does affect is comparability: if 2 figures on one page came from sources that last
updated hours apart, the page should say so rather than imply one moment.

Publishing more often than decisions get made has a cost of its own. A number that moves
between Tuesday and Thursday, with no decision in between, buys an explanation and nothing
else, and the hour goes to reconciling versions instead of reading them.

## Why do 2 event reports disagree?

The cause is almost never an addition error. Two things explain most disagreements: a
different definition behind a word, and a different moment of capture behind a figure. Sort
out which of the two you are looking at before anyone starts checking formulas.

Definitions drift in predictable places. Registrations may or may not exclude cancellations,
test records, and staff. Attendance may mean a check-in at the door, a session join, or a
minimum time in session, and the three produce three different numbers from the same event.
Spend may be what the ad platform reported or what the invoice said. A deal amount may be the
figure at the time of the event or the figure today. Currency and time zone quietly do the
same thing: an evening session in one region lands on a different day in a different report.

Capture time does the rest. Registration records, engagement records, CRM deals, and ad spend
each reach a report on their own schedule, so a page assembled on Monday morning can hold a
deal amount from Monday, session records from an hour ago, and ad spend that stopped updating
overnight. Nothing is wrong with any single figure. They simply do not describe the same
moment, and two people assembling the same page on different mornings will disagree.

A third case deserves naming. A person who reached you through 2 systems can appear twice
in any count built on top of them, unless somebody decides which record wins. Find out who
makes that call in your stack and where its result is visible, because the answer moves every
derived number on the page.

A disagreement is information: it tells you that 2 pages were built on different ground.
The repair is mechanical. Put the two versions side by side, find the first row where they
diverge, and check the definition and the capture time before touching the arithmetic. One of
those two usually explains it, and the fix is to write the answer down so the same hour is not
spent again next quarter.

## What has to be true before a report can be trusted?

Every number on the page carries 3 things: a definition, a source, and the time it was
captured. Without the definition, 2 readers argue about a word. Without the source, nobody
can reproduce the figure. Without the capture time, the figure cannot be compared with
anything, including its own earlier version. Those three travel together, and a report that
carries them survives being questioned.

Four more conditions turn that into something a reviewer can accept.

The definitions match last period, or the page says which one changed. Definitions do improve.
When one improves silently, every year over year comparison built on it becomes wrong that
day, and nobody in the room can tell which side of the change they are reading.

The records behind a figure are reachable. Someone who disagrees should be able to open the
registration list, the invoice, or the opportunity report without asking you for an export. A
figure nobody can open is a claim. Which kind of tool is supposed to keep those records
reachable is a question about [the event tech stack](https://eventiq.io/md/blog/event-tech-stack); this page is
about what the report itself has to show.

The gaps are shown rather than quietly closed. Say which systems were included and which were
not, and how many records could not be matched to a contact. An explicit gap costs less
credibility than an estimate presented as fact, and an unexplained unmatched share can change
the decision the report is asking for.

The page names an owner and a decision. Reports that end in figures get filed; reports that
end in a recommendation, with the person accountable for it and the date it will be reviewed,
get acted on. The rule that decides which event gets credit for a deal belongs in that same
written record, which the [event marketing attribution](https://eventiq.io/md/event-marketing-attribution) guide
works through.

Run the test on your last event report. Pick any 3 numbers on it and ask, for each, what
the definition is, which system it came from, and when it was pulled. If you can answer all
three for all of them, the process is working. If you cannot, that is the repair list, and it
is shorter than rebuilding the report.

## Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run: registration
and ticketing (Cvent, Zoom, Swapcard, StubHub), 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.

Registrations and attendance stay separate records. Contacts are matched by exact email, and
every record keeps its result: matched, unmatched, or no email. Salesforce deals, stages, and
close dates link to an event through a campaign relationship you confirm. Marketing spend sits
by event and channel, with the author of every change. Records sync on a schedule: Swapcard
every 15 minutes, Cvent every 30, Zoom every 2 hours, Salesforce every 4. The Event Dashboard
and the Portfolio Dashboard show them in one view, and a forecast is visible before the event.

Ask any vendor, including us, which of these it holds in the product rather than on a slide:
the full cost of the event, the ROI figure itself, one person counted once across sources, and
a total in a single currency. The method in this article is the one you run on top of those
records.

## See the records behind a report

[Book a demo](https://eventiq.io/#early-access) to see a sample event's registrations, attendance, marketing spend
by channel, and the deals linked to its campaign in one view, with the sync schedule of each
source beside it. The demo takes 20 minutes.

More reporting guides, templates, and open calculators are in the [EventIQ blog](https://eventiq.io/blog).

---

HTML version: https://eventiq.io/event-reporting