A conference planning template is a one-page working document that lists every workstream of
the conference with an owner and a date. The version below opens with a goals-and-measurement
section: what the conference is for, the number that will show it, the record that number comes
from, and the date it will be read. Write that section first, because the venue contract and
the budget are both sized to numbers it produces.

[Download the conference planning template (CSV)](https://eventiq.io/templates/conference-planning.csv). No email required.

The template covers one conference. Cost lines stay in your
[event budget](https://eventiq.io/md/blog/event-budget-template) and promotion in your
[event marketing plan](https://eventiq.io/md/templates/event-marketing-plan). The template points to both.

## What should a conference planning template include?

Nine sections, each with one owner and a date. Copy the table and replace the prompts with
your own entries.
| Section | What to enter | Record it produces |
| --- | --- | --- |
| 1. Goals and measurement | Three to five goals, each with the nine fields shown below | The page the post-event report is checked against |
| 2. Budget | Cost and revenue lines, planned and committed, and the revenue target | Approved budget |
| 3. Venue and contracts | Space, room block, food and beverage minimum, and every date that turns a headcount into money | Signed contracts |
| 4. Program and speakers | Tracks, session count, speaker confirmations, final agenda date | Published agenda |
| 5. Registration and pricing | Ticket types, prices, complimentary categories, open and close dates, refund rule | Registration setup that matches the goal definitions |
| 6. Marketing | Audience segments, channels, spend by channel, a campaign label for every link | Labeled links and spend by channel |
| 7. Sponsors and exhibitors | Packages, prices, signed value, what each sponsor was promised | Signed agreements |
| 8. On-site operations | Check-in method, the definition of attended, staffing, session scanning if a goal needs it | Check-in records |
| 9. After the event | Reporting cutoff, survey send date, expense close, debrief date, read date for each goal | Post-event report |
Sections 2 to 8 are the familiar ones, and a task list handles them well. A task list tells you
whether the conference ran on time. Whether it did what it was funded to do is the question the
person approving next year's budget will ask.

In a survey of 162 event professionals (71% of them in the US) published by Global DMC Partners
in May 2026, 68% reported stakeholder pressure to prove the business impact of their meetings
and incentive programs, and 30% said they use data or analytics tools to track ROI
([Global DMC Partners](https://globaldmcpartners.com/2026/05/event-roi-measurement-gap-mice-industry/)).
The survey went to the company's own network and is not a probability sample, so read it as
context. Section 1 answers that pressure before the event, while the records can still be set
up.

## How do you write the goals-and-measurement section?

Write three to five goals. Each goal is a block of nine fields, and a goal with an empty field
is not ready for the plan.
| Field | What to enter | Test before you accept it |
| --- | --- | --- |
| Goal | The outcome in one sentence, in money or people | Finance would accept it as a reason to fund the conference |
| Measure | One number with a unit | Two people computing it get the same figure |
| Definition | What is counted and what is left out: paid or complimentary, registered or checked in | The budget and the report use the same wording |
| Source record | The system and the field the number is read from | The record exists, or a task in the plan creates it |
| Baseline | The same measure from your own last one or two editions | Same definition as the target |
| Target | The figure the budget assumes | It agrees with the lines in section 2 |
| Floor | The lowest result you would still accept | Written down before registration opens |
| Owner | One named person | They can pull the number themselves |
| Read date | The date the figure is final enough to judge | After the reporting cutoff for that record |
The floor is the field teams skip. Without it, any result below target turns into a discussion
about whether it was close enough. With it, a result has three possible readings: target met,
between floor and target, or below floor.

Run every draft goal through four tests before it goes into the plan.
| Test | If it passes | If it fails |
| --- | --- | --- |
| A record of the measure exists in a system you run | Name the system and the field | Add a collection task with an owner and a date before registration opens, or move the goal to notes |
| The record will be complete by the read date | Keep the read date | Move the read date, and say so in the plan |
| A baseline exists on the same definition | Set the target against it | Label the target a planning assumption and treat this edition as the baseline |
| One person owns the number | Enter the name | Hold the goal until someone accepts it |
## How do you set targets that agree with the budget?

Work backward from the revenue target, so that section 1 and section 2 cannot disagree.

**Paid registrations needed = Registration revenue target ÷ Average net price per paid registration**

**Expected attendance = Total registrations × Attendance rate from your own past editions**

**Budgeted cost per attendee = Total budgeted cost ÷ Expected attendance**

**Planned net = Revenue target − Total budgeted cost**

**Planned ROI = Planned net ÷ Total budgeted cost × 100**

Average net price is the revenue collected per paid registration after discounts and refunds,
taken from your last edition and adjusted for any price change. Complimentary registrations
for speakers, staff, and sponsor passes bring cost and no registration revenue, so add them to
paid registrations before you apply the
[attendance rate](https://eventiq.io/md/blog/event-attendance-rate) from your own check-in history.

Planned ROI is arithmetic on two figures you set yourself, the budget and the revenue target.
Whether the conference delivered it is a second calculation, run on closed revenue and final
cost.

Once registration opens, the paid registration target gets a second reference: the range from
your [registration forecast](https://eventiq.io/md/blog/conference-registration-forecasting). If the low end of that
range falls under the floor, you learn it while marketing and contract dates can still move.

## Which measurement tasks have a deadline before the event?

Most of the records behind the goals can only be set up in advance. Put these six tasks in the
plan with dates.
| Task | Do it before | What you lose if it slips |
| --- | --- | --- |
| Agree the definitions of paid, complimentary, and attended | The budget is approved | The plan and the report count different things |
| Set up ticket types that match the goal definitions | Registration opens | Paid and complimentary registrations cannot be separated cleanly afterward |
| Put a campaign label on every registration link | The first invitation is sent | Registrations that arrived unlabeled cannot be assigned to a channel |
| Choose the check-in method and what counts as attended | Badges are ordered | Presence that was not recorded on the day cannot be recovered |
| Add session scanning if a goal needs session-level data | On-site staffing is fixed | You know who entered the venue and have no record of their sessions |
| Write the survey, and set its send date and the reporting cutoffs | The event opens | The survey goes out late, and report figures are pulled on different dates |
## Example: a two-day conference planned for 600 paid registrations

Take a two-day regional conference. All figures are hypothetical. The budget assumes
registration revenue of $390,000 and signed sponsorship of $150,000, for a revenue target of
$540,000. Average net price at the last edition was $650, so paid registrations needed are
$390,000 ÷ $650 = 600. The plan adds 50 complimentary registrations, for 650 in total. The
attendance rate across the last two editions was 88%, so expected attendance is
650 × 0.88 = 572.

Budgeted cost is $468,000: venue $140,000, catering $171,600, marketing $46,400, and other
costs $110,000. Budgeted cost per attendee is $468,000 ÷ 572 = $818. Planned net is
$540,000 − $468,000 = $72,000, and planned ROI is $72,000 ÷ $468,000 × 100 = 15.4%.
| Goal | Measure and source | Baseline | Target | Floor | Actual at read date | Reading |
| --- | --- | --- | --- | --- | --- | --- |
| Net result | Revenue less total cost, finance ledger | $58,000 | $72,000 | $0 | $69,510 | Between floor and target |
| Paid registrations | Paid count, registration platform | 560 | 600 | 540 | 578 | Between floor and target |
| Attendance rate | Checked in ÷ total registrations, check-in records | 88% | 88% | 85% | 87.0% | Between floor and target |
| Signed sponsorship | Signed value, sponsor agreements | $142,000 | $150,000 | $130,000 | $156,000 | Target met |
| First-time attendees | Share of paid registrations with no match by email in the last two attendee lists | 31% | 35% | 30% | 28.0% | Below floor |
The actuals behind the table: 578 paid registrations at an average net price of $645 gave
$372,810, and sponsorship closed at $156,000, so revenue was $528,810. Final cost was $459,300.
Net was $528,810 − $459,300 = $69,510, and ROI on closed figures was $69,510 ÷ $459,300 × 100 =
15.1%. With 52 complimentary registrations the total was 630, and 548 people checked in:
548 ÷ 630 = 87.0%. First-time attendees were 162 of the 578 paid registrations, or 28.0%.

Net missed its target by $2,490. Registration revenue came in $17,190 short, sponsorship
finished $6,000 over, and cost closed $8,700 under budget. Three goals landed between floor and
target, and none of them needs a meeting.

First-time attendees fell below the floor written down in advance, and that goal does need a
meeting. Next edition's plan opens with a specific question: which segments and channels were
meant to bring new people. Without a floor, 28.0% against a baseline of 31% would have been
read as roughly in line with last year.

A sixth draft goal, knowing which tracks to keep, failed the first test at planning time:
check-in recorded entry to the building and nothing at session doors. The team added session
scanning as a task with an owner and a date. Without that task, the goal would have moved to
notes.

## Which mistakes make a conference plan useless?

**Writing the goals after the event.** A goal chosen once the results are in will always look
met. Date the section before registration opens.

**Using one audience number.** Registered and checked in are two counts, and catering, cost
per attendee, and sponsor promises depend on which one you meant.

**Leaving the read date open.** Net read before expenses close is preliminary, and a first-time
share read before refunds settle will move. Each goal gets one date, and the
[post-event report](https://eventiq.io/md/blog/post-event-report-template) uses the figure from that date.

## What to do this quarter

- Copy the nine sections into a working file and name one owner per section.
- Draft three to five goals and run each one through the four tests.
- Compute paid registrations needed, expected attendance, and planned net, and check that
  section 1 and section 2 agree.
- Put the six measurement tasks on the calendar with the date each one has to beat.
- Write a floor for every goal and have finance sign the page before registration opens.

## Common questions

### How is a conference planning template different from a checklist?

A checklist records whether tasks were done. A planning template also records what the
conference is for, the budget it runs on, and who owns each part. Venue, program, and on-site
checklists sit under sections 3, 4, and 8.

### How many goals should a conference plan have?

Three to five. Make one financial and one a registration or attendance count, and let the rest
reflect why this conference exists. Past five, the fields stop being kept current.

### What if this is a first conference with no baseline?

Mark the baseline field as none and label every target a planning assumption. Set the floor
from what the budget can absorb. This edition becomes the baseline for the next plan.

## 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 goals-and-measurement section, the product holds the figures you enter and the
registration side. Your team enters the budget lines (total, marketing, venue, catering, other)
and the revenue target on the event, and the ROI shown is arithmetic on those entries.
Registrations from Cvent carry their date, ticket type, and price where the platform provides
them, along with a check-in mark, so registered and checked in stay two counts. Marketing spend
is entered by your team or imported from a CSV, by event and channel. Before the event, the
attendance forecast fits a registration curve to the event's own sign-up pace, once there are
about two weeks of registration data, and it is shown as a range. A check for a registration
slowdown runs when you ask for it.

EventIQ does not hold the plan itself, so sections, tasks, owners, floors, and read dates stay
in your working file. The ROI in the product uses the revenue target you entered, so the net
result at close comes from finance's ledger. Registrations and check-ins are separate records,
and the attendance rate and cost per attendee are divisions you run on them. EventIQ makes no
recommendations, so the reading on each goal and the decision that follows are yours.

[Book a demo](https://eventiq.io/#early-access) to see the budget, revenue target, registrations, and check-ins
behind a goals-and-measurement section on a sample event, in a 20-minute demo.

---

HTML version: https://eventiq.io/templates/conference-planning