Group registration is a block of seats that one organization buys on one decision, and it does
not arrive on the individual registration curve. Group bookings tend to come late, in blocks, at
a negotiated price. Forecast them as a separate line built from a pipeline of named accounts,
price the discount on net contribution per seat, and hold seats under a rule that releases them
before your catering guarantee is set.

A pacing model that counts registrations one at a time will misread the group line, and at an
event with large delegations that line can decide whether you hit the number.

## Why does group registration break a pacing model?

A pacing model compares cumulative registrations at a given number of weeks out against the same
point in prior cycles. It assumes registrations are roughly independent events arriving at a
rate that changes smoothly. Groups violate both assumptions. One group booking is a single
decision that can produce thirty registrations at once, so arrivals are lumpy. The decisions are
also linked, because a handful of large accounts respond to the same budget conditions.

The timing makes it worse. The Maritz Registration Insights Report analyzed more than 360,000
registration records across 30 trade shows and found that in 2023, 45% of registrants signed up
in the final 4 weeks before the event, 29% in the final 2 weeks, and 9% on site
([PCMA Convene](https://www.pcma.org/rethinking-early-bird-pricing-other-event-registration-strategies/)).
Those are registration records from trade shows, not a survey and not association conferences,
so read the shape as a warning. The report does not split out groups. Expect yours to land late
as well, because a delegation usually needs a purchase order (PO), a travel approval, and a name
list before it can register.

The result is a pacing chart that can look acceptable at eight weeks out and then either surge
or fail to. Kyle Jordan, director of meetings at INFORMS, told
[Skift Meetings](https://meetings.skift.com/2026/06/22/late-registrations-are-not-the-only-thing-stressing-planners-out/)
in June 2026: "Our old registration pacing models are not as reliable as they used to be." A
blended curve will not tell you which of those two outcomes you are heading for until it is too
late to act on the answer.

## What counts as a group, and why write the definition down first?

Before you can track a curve you need a rule that decides which registrations belong to it, set
before the cycle opens. Three definitions are in common use, and they produce different numbers.

- **Discount-based.** Any registration that used a group code. Easy to pull, but it misses
  delegations that paid list price and includes clusters of two or three.
- **Payer-based.** Any set of registrations paid on one invoice or purchase order. Closest to
  how the money arrives, and usually the most useful for finance.
- **Account-based.** Any set of registrations belonging to the same employer record, however
  they paid. Best for retention work, hardest to maintain because employer fields are free text.

Pick one as the reporting definition and write the threshold down. A workable starting rule: a
group is five or more registrations on a single invoice or purchase order from one organization,
tracked against a named account owner. The threshold matters less than the fact that it does
not move mid-cycle.

## What is a group seat worth net of the discount?

The headline group rate is easy to state. The contribution per group seat takes one more step,
and it is the number that decides whether the discount adds margin or gives it away. The
arithmetic is short, but it has to include the variable cost of serving the person and the
cost of acquiring the seat.

**Net contribution per seat = Price paid − Variable cost per attendee − Acquisition cost per seat**

**Group margin contribution = Net contribution per group seat × Group seats delivered**

**Discount cost of the group program = (Net contribution per individual seat − Net contribution per group seat) × Group seats the discount did not create**

Variable cost per attendee covers food and beverage, materials, the badge, and onsite service:
the per-head lines of your [event budget](https://eventiq.io/md/blog/event-budget-template).

On the last line: a discount only costs you money on seats that would have sold at list price
anyway. On seats the discount created, it bought volume you would not otherwise have had. You
cannot know the split precisely, but you can bound it. Ask your group contacts how many people
they would have sent at list price. A buyer negotiating a discount has a reason to understate
that number, so treat the count of seats the discount created as a ceiling.

## How do you build a group curve with no history for it?

You do not need three years of clean data. You need the current cycle instrumented and two prior
cycles reconstructed roughly.

Start with a pipeline, and let the forecast fall out of it. Every organization that could send a
block gets a row with an account owner, a stage, a seat count, a decision date, and a names-due
date. Stages should follow the actual approval path: contact made, seats discussed, budget
confirmed, PO issued, names submitted.

**Group seat forecast = (Seats with PO issued × Committed show rate) + (Seats with budget confirmed × PO conversion × Expected show rate) + (Seats discussed only × Discussed-to-PO conversion × Expected show rate)**

**Group-adjusted attendance forecast = Individual attendance forecast with groups removed + Group seat forecast**

**Group pipeline coverage = Total seats in pipeline ÷ Group seat target**

The individual side is the ordinary
[conference registration forecast](https://eventiq.io/md/blog/conference-registration-forecasting), run on the count
with groups taken out and converted to attendance at its own show rate.

A note on show rate. Group seats are paid seats, so start from your own paid
[attendance rate](https://eventiq.io/md/blog/event-attendance-rate). They differ in one respect: a named seat that
cannot travel is often swapped, which keeps the count and changes the person. If your onsite
planning depends on who is in the room, track the swap rate separately.

On coverage: if you have never measured it, you have no ratio to compare against. Do not borrow
one. Record it this cycle and the next, and you will have a usable rule by the third.

## Which two weeks decide whether you hit the number?

If your groups follow the late pattern above, it is the window from four weeks out to two weeks
out. Check that against your own purchase order dates from prior cycles. Two weeks out you can
still send a personal ask to nine budget holders. Two weeks out you cannot buy your way to 120
individual registrations.

So the group pipeline needs a review cadence tighter than the marketing standup and a named
owner on each large account. Agree the escalation rule in advance. If committed seats at four
weeks out are below a stated share of target, the response is a direct call from the executive
who signed the partnership agreement.

## How do you hold seats without holding cost?

Groups ask for held inventory, and the named list comes later. The exposure is that you commit
food and beverage and materials guarantees against seats that never fill. The fix is a hold rule
with a hard release, published in the agreement.
| Term | Rule |
| --- | --- |
| Deposit at agreement | 25% of contracted seats × net group price |
| Names due | 21 calendar days before doors |
| Unnamed seats | Release automatically at the names-due date |
| Released seats | Return to general inventory at the prevailing tier price |
| Food and beverage guarantee | Set on named seats only, not on contracted seats |
| Substitutions | Free until 7 days out, then an administrative fee |
The deposit turns the hold into a commitment. The automatic release keeps your catering
guarantee tied to named people. Do not negotiate the names-due date per account unless you are
willing to run per-account guarantees.

## Example: 240 group seats at an 1,800-attendee meeting

Take an association annual meeting that budgeted for 1,800 attendees. Nine organizations
delivered 240 seats between them, which is 13% of the room. All figures are hypothetical.
| Line | Individual seat | Group seat |
| --- | --- | --- |
| Price paid | $1,095 | $875 |
| Variable cost per attendee | $190 | $190 |
| Acquisition cost per seat | $115 | $40 |
| Net contribution per seat | $790 | $645 |
The group price is $220 below list, a discount of about 20%. Because a group seat costs less to
acquire, the gap in net contribution is smaller: $790 − $645 = $145 per seat.
| Organization | Seats | Contribution at $645 per seat |
| --- | --- | --- |
| Org A | 45 | $29,025 |
| Org B | 40 | $25,800 |
| Org C | 33 | $21,285 |
| Org D | 28 | $18,060 |
| Org E | 24 | $15,480 |
| Org F | 20 | $12,900 |
| Org G | 18 | $11,610 |
| Org H | 16 | $10,320 |
| Org I | 16 | $10,320 |
| Total | 240 | $154,800 |
Across 240 seats the $145 difference comes to $34,800. That is not the cost of the program,
because some of those seats were created by the discount. Suppose the account owners judge that
90 of the 240 would not have attended at list price. The discount then cost $145 × 150 = $21,750
in forgone contribution, and it bought 90 incremental seats worth $645 each, or $58,050. On
those assumptions the program returns about 2.7 times what it gave up, a net gain of $36,300.

The result rests on the estimate of 90. The program breaks even when the incremental seats at
$645 cover the $145 given up on the rest. With n incremental seats, $645 × n = $145 × (240 − n),
so n = $34,800 ÷ $790 = 44.05, which means 45 of the 240 seats. Write the estimate down and
revisit it each cycle.

Concentration is the second risk. The three largest organizations hold 118 of the 240 seats,
which is 49% of the group line and $76,110 of contribution. If Org A cuts from 45 seats to 15
because of a travel freeze, the room loses 30 seats, 1.7% of attendance, and $19,350 of
contribution in a single phone call. Tracked as one line in a pacing chart, that call is
invisible until the chart bends. Tracked as an account with an owner and a decision date, it is
a conversation you can have five weeks out.

## What to do this quarter

- Pick one of the three group definitions, write it down, and tag this cycle's registrations
  against it.
- Reconstruct the last two cycles' group seats well enough to get a rough share of the room and
  an arrival profile by weeks out.
- Build the group pipeline: stages, seat counts, decision dates, and a named owner per account.
- Calculate net contribution per group seat and per individual seat on your own cost base, and
  put both in front of whoever approves the discount.
- Publish the seat hold rule with a names-due date and automatic release, and set the food and
  beverage guarantee on named seats.
- Add a four-weeks-out escalation trigger on committed seats as a share of target, with the
  executive call named as the response.

## Common questions

### Should the group forecast be added to the pacing chart or kept separate?

Keep two curves and one total. The individual curve is what marketing spend moves, and the group
curve is what account conversations move. Combining them hides which lever is failing, and the
two levers have different lead times.

### How do we set the group discount level?

From your own contribution figures and your own judgment about incremental seats. A discount
level copied from a comparable event imports that event's cost base along with it.

### Is a group discount the same decision as an early bird discount?

No. An [early bird registration](https://eventiq.io/md/blog/early-bird-pricing) rate discounts by date and is judged
by the spike around a deadline. A group rate discounts by buyer and is judged account by
account. Say in the agreement which rate a group pays if it books before the early deadline.

### What is the most common mistake with group registration?

Treating a verbal commitment as a forecast. Seats discussed are not seats with a purchase order,
and the conversion rate between those two stages is the most valuable number in this exercise.

## 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.

The attendance forecast works at the event level, on total registrations. It 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 on registration pace flags a slowdown, and it runs when you ask
for it.

Registrations from Cvent carry their date, ticket type, and price where the platform provides
them. If you sell group seats under their own ticket type, the count and the average price of
that type are figures you can read on the event.

EventIQ does not put group bookings on their own forecast line, and it does not group
registrations by invoice or employer. The pipeline on this page, with its account rows, stages,
seat counts, and names-due dates, is work your team keeps itself, and the net contribution per
seat is yours to run. If groups are a large share of the room, treat an event-level slowdown as
a prompt to open that pipeline, because the check cannot tell you which account moved.

[Book a demo](https://eventiq.io/#early-access) to see the ticket-type mix and the registration curve with its
forecast range on a sample event, in a 20-minute demo.

---

HTML version: https://eventiq.io/blog/group-corporate-registrations