An event portfolio dashboard puts records from multiple events in one place so you can see
where registrations, participation, marketing spend, and linked commercial records differ.

It is useful for finding questions to investigate across a program. It is not, by itself, a
ranking of which event earned the most. That conclusion needs a cost definition and evidence
that the events were measured on the same basis.

You probably have a calendar already. A portfolio view should tell you which figures can
sit in the same column and what is missing before a budget owner uses the table.

## What is an event portfolio?

An event portfolio is the set of events for which one team is accountable. The boundary may
be a fiscal year, a business unit, a client account, or a defined program. Write that boundary
above the dashboard. Without it, a new event can enter a total while an older one quietly
disappears, and the apparent trend says more about the filter than the work.

Treat an event as a row with a stable identity, not just a name. A title reused every year
needs an edition or date. A roadshow with several stops needs a declared rule: either each
stop is a separate event or the roadshow is the parent with its stops visible underneath.
You cannot compare last year's parent total with this year's individual stops and call the
change performance.

Keep purpose beside format. A paid conference and a customer briefing can appear in the
same portfolio without promising the same outcome. If you need to decide which events to
fund, first establish what each was meant to do. That decision is separate from reading
the records on the screen.

## What belongs on an event portfolio dashboard?

The layout below is a way to review a program, not a list of features in any particular
product. Some fields belong in a working file beside the dashboard.

Start with columns that a reviewer can trace back to a source. Event name, date, format,
owner, registration source, and reporting period make the rest of the row intelligible.
Then show registrations and presence as separate records. A registration is an intention to
take part; a presence record says something happened under the source platform's own rule.
Putting them in adjacent columns is useful. Collapsing them into a single unexplained
"audience" figure is not.

Marketing spend belongs by event and channel, with the period used to collect it. Commercial
records need a stated relationship to the event. A deal tied through a confirmed campaign
relationship is different from a contact who happened to register. Neither should be
silently presented as money earned by that event. For each figure, keep a source name and a
date when someone reviewed the row. If your software does not display a review date, put it
in the accompanying working file rather than pretending the screen does.

| Field in the review | What the reader needs to know | Where to check it |
|---|---|---|
| Event identity | Which edition, stop, or parent the row covers | Program calendar and event owner |
| Registrations | Which statuses and sources are included | Registration records |
| Presence | What action created the record | Check-in or session source |
| Marketing spend | Which channels and dates the amount covers | Campaign records and budget owner |
| Commercial link | Which relationship connects a deal to the event | Confirmed campaign and CRM record |
| Missing information | Whether a blank means none, not collected, or not reviewed | Owner of the source field |

Keep a source reference for each row in your working file. Record definitions and open
questions in the [post-event report template](https://eventiq.io/md/blog/post-event-report-template). When
someone disputes a portfolio row, inspect the event report rather than the summary.

## Which events can you compare directly?

Compare events only when the field means the same thing and the observation period is alike.
Registrations from two ticketed conferences may be comparable if both exclude cancelled
orders and use the same cutoff. A webinar registration count and an on-site check-in count
are not 2 versions of the same measure. One records intent before the event. The other
records an action at a venue.

Format is only a starting filter. A regional series may use the same registration system,
yet one stop sells tickets while another invites customers without charge. A conference
may record presence at each session while a smaller meeting does so once at the door.
Compare their presence records only after you have chosen a common definition. Otherwise
show the methods side by side and leave the cross-event total out.

Time matters too. A completed event has a closed registration period; an upcoming event
does not. A sales record may change stage after the event, while marketing spend for the
same event may already be settled. Label a row as planned, in progress, or completed in your
review file. Do not read an unfinished event's lower count as weaker demand without
checking how long registration has been open and which channels have run.

When definitions do not match, group the events. Keep ticketed events apart from
invitation-only programs or separate views by format. Make exceptions visible before
someone uses a total. The [event marketing analytics guide](https://eventiq.io/md/event-marketing-analytics)
covers definitions for an individual event.

## How do you compare events held in different currencies?

Keep the original currency with each amount. A dollar sign without a currency code is not
enough for a cross-border portfolio, and adding amounts in different currencies produces a
number that has no financial meaning. EventIQ does not convert currencies or give you a
single-currency portfolio total.

If the finance team needs a common-currency review, it must supply the conversion policy:
which rate, which date, and whether the comparison uses planned or final spend. Apply that
policy outside the dashboard and label the converted figure as a finance calculation. Do
not overwrite the source amount. A reviewer should still be able to see what the campaign
actually cost in its original currency.

Conversion does not fix scope. One event's marketing spend may include agency fees while
another's does not. Check both before a cross-market comparison.

## How should you read marketing spend across the portfolio?

Marketing spend tells you where promotion money was assigned. It does not tell you the full
cost of running an event. Venue, production, travel, and staff time may live in other files
or with other owners. Keep those lines separate rather than naming the marketing-spend total
"event cost." A portfolio screen can expose a shift in channel spend without claiming to
explain the event's final financial result.

Start by checking allocation. Does each campaign have an event and channel owner? Did a
shared campaign support several events? If so, state the allocation rule in the working
file before splitting its expense. A late reassignment can move spend between event rows
without changing what the organization paid. The budget owner needs to see that distinction
before calling the movement a saving.

Compare the shape of spend, not just its size. An event funded mainly by paid media asks a
different question from one promoted through an existing member list. In the working file,
note funded channels for which your team cannot identify a registration source. Also mark
events with registrations but no assigned campaign expense. Check the underlying records
before making claims about a channel.

Use the same spending window for events that share a format. If one row stops at event day
and another includes follow-up promotion, the channel comparison is distorted. Document
the dates, then let finance add non-marketing costs in its budget file when needed.

## What decisions can a portfolio view support?

A portfolio view directs attention to the records behind a row. If registration records
exist but presence records are absent, ask the source owner why. If spend sits under a
different event name, check the campaign assignment. If a campaign relationship has not
been confirmed, send it to the CRM owner. None of these checks establishes event return.

Review events with the same registration definition together. If one venue collected
presence only at entry while the others tracked sessions, flag it before the meeting. The
exception belongs next to the row so nobody treats the presence counts as equivalent.

Spend allocation is another valid question. Compare assigned campaign spend with the
separate approved [event marketing plan](https://eventiq.io/md/templates/event-marketing-plan). If they differ, check the channel records with the campaign owner.
Moving the remaining budget requires context outside this view: contracts, committed
production cost, audience capacity, and the event's purpose.

## Which decisions should this screen not make?

Do not rank events by financial return from marketing spend alone. The denominator is
incomplete, and a CRM deal linked to an event is not automatically revenue caused by it.
EventIQ's Portfolio Dashboard does not calculate ROI, assemble full event cost, or divide
the influence of a deal among contacts or activities. A claim about which event earned
more needs a separate, agreed method and the cost and revenue records that method requires.

Do not treat an absent record as a zero. The source may not collect that action, the event
may have used another method, or the record may not have been reviewed yet. Zero is a
measurement; blank is a question. Keeping them distinct may make a portfolio table look
less tidy, but it prevents a missing feed from becoming a budget verdict.

Avoid comparing stages without the dates behind them. A deal that is still open is not the
same as closed revenue, and a recent event has had less time for a linked deal to progress.
An identical stage label across 2 event rows does not make their commercial outcomes
identical. Ask the CRM owner what relationship was confirmed and when the stage was read.

Finally, do not use the screen alone to decide which events to stop. That decision requires
the event's purpose, complete cost, contractual obligations, and a consistent decision
rule, such as the protect, optimize, and eliminate rules of a
[B2B event strategy](https://eventiq.io/md/blog/b2b-event-strategy). The portfolio view can surface a row for review; it is not the review itself.

## How do you run a useful portfolio review?

Before the meeting, freeze the set of events under discussion. List each event's format,
status, and owner. Ask the registration owner what counts as a valid registration, the
presence-source owner what action created the participation record, and the campaign owner
which expenses belong to each event. Give a blank field an explanation instead of filling
it from memory.

In the meeting, clear the obvious record problems first. Then inspect comparable rows that
changed. Put budget questions that need more financial evidence on a separate list with a
person responsible for the next check. That list can live in the meeting's working document;
it need not be an automated dashboard function.

Afterward, preserve the definitions used in that review. If a source changes its check-in
rule, write down the date and avoid comparing later rows with earlier ones as though the
method stayed fixed. If finance changes its cost policy, do the same for financial work
outside the dashboard. A stable column name is not proof of a stable measure.

At the next review, begin with the unresolved rows. You should not have to rediscover why
a webinar and a ticketed conference produced different presence records.

## Where does EventIQ fit?

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. The Event
Dashboard and the Portfolio Dashboard show them in one view.

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](https://eventiq.io/md/event-roi) 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.

If you want to inspect the Portfolio Dashboard, [see the demo](https://eventiq.io/#early-access) on sample data.
Bring the question your budget owner asked, and ask which supported records can appear
on the screen and which checks still need a separate review.

---

HTML version: https://eventiq.io/event-portfolio-dashboard