Event registration pace dashboard: read the curve, not the total
Registrations are coming in, and nobody on the committee can say whether the number today is good, bad or normal for this point.
The short answer
A registration pace dashboard compares registrations at each date with checkpoints the committee agreed beforehand, using counts defined the same way every week. It exists to prompt a decision when the pace moves away from the plan, not to predict attendance.
Your own past events and your own target range are the only fair baseline. Do not borrow numbers from other events.
Define the counts first
| Count | Definition to write down | Common trap |
|---|---|---|
| Registered | A completed form that meets your acceptance rule, for example paid or approved. | Counting unfinished forms or unpaid invitations. |
| Confirmed | Registered and the delegate has confirmed attendance where you ask for it. | Mixing confirmed with registered. |
| Waitlisted | Wanted a place but is held until space opens. | Adding waitlisted to registered. |
| Cancelled | Withdrew or was removed, with the date. | Not subtracting, or dropping the record. |
| Complimentary or invited | Speakers, guests and organiser places, counted separately. | Including them in the paid pace. |
Set checkpoints before the campaign starts
Pick three to five dates between opening and the event, and write a target range for each, such as registered by the end of week four. Base the range on your past events, a member list, or a stated target, and label the basis.
If you have no history, say so on the dashboard and use the first weeks to learn the shape of your curve. Do not present an invented benchmark as a norm.
What the dashboard shows
- Registered, confirmed, waitlisted and cancelled, each with its date and source.
- The checkpoint range for today and the actual count against it.
- A weekly change, with the number of cancellations shown separately.
- Mix by delegate type or channel, only if the committee will act on it.
- Data last updated and who supplied it. If the data is stale or missing, show Grey, not green.
Triggers that call a decision
| Situation | Question for the committee | Possible actions to consider |
|---|---|---|
| Below checkpoint range | Is the audience aware, is the registration step working, or was the range wrong? | Review the invitation list, reminders and registration steps. Decide who owns the follow-up. |
| Within range | Is anything else changing the pace, such as a closing date near? | Keep the plan and update the next checkpoint. |
| Above range | Is the venue or catering capacity going to be tested? | Check the agreed capacity with the venue in writing. Decide whether to cap or add sessions. |
| Cancellations rising | Are they from one group or reason? | Ask the delegates why, and review the cancellation terms. |
What the dashboard must not claim
The dashboard reports what has happened. It does not promise that a number will be reached, and coordinating the reporting is separate from selling tickets or sponsor places. Any sales or promotion work is a separate decision for the committee.
Worked example · Fictional example
A forum that read the dashboard instead of the total
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional healthcare administrators' forum set a target range of 180 to 220 registered by event day, with checkpoints at weeks 4, 8 and 11. At week 8, it had 74 registered against a range of 90 to 110.
The dashboard showed that 40 of the 74 had registered in one week after a reminder, and that 12 invited members had never opened the first email. The committee decided to review the invitation list and send a second reminder from the chairman. At week 11, registered was 141 against a range of 140 to 165.
Use this yourself
Registration pace dashboard layout
Copy this into a sheet and update it on the same day every week.
- Definitions of each count are written at the top.
- Checkpoint dates and ranges are agreed by the committee before opening.
- Basis for each range is stated: past event, member list or stated target.
- A weekly note says what changed and what the committee decided.
- Grey is used when the data is old or the source is unclear.
| Date | Registered | Confirmed | Waitlisted | Cancelled | Complimentary | Checkpoint range | Source | Status |
|---|---|---|---|---|---|---|---|---|
| (date) | (count) | (count) | (count) | (count) | (count) | (low to high) | (system or list) | R / A / G / Grey |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One system or sheet holds the counts, and one person updates it.
- The committee has history or a stated target to compare against.
- Registration is simple, with few ticket types.
Outside planning help earns its fee when
- Counts differ between the registration system, finance and the venue.
- Several ticket types, groups and invitations make the picture hard to read.
- The committee reacts to each day's number instead of the plan.
Want registration reported clearly?
A conference project lead can define the counts with you, set up the checkpoint report, reconcile the sources and bring each trigger to your committee as a decision with options. Ticket sales and promotion are not part of this support. Send what your registration system reports today.
Questions organisers ask
What is a good registration number?
There is no universal figure. A good number is one at or above the range your committee set from its own history or target, with the basis stated.
Should we count waitlisted and invited people?
Count them separately. Mixing them makes pace look better or worse than it is and hides capacity questions.
How often should we update the dashboard?
Weekly is enough for most events, and daily in the final fortnight if registration closes then. Update on the same day each time so the change is comparable.
How does it connect to the budget?
Registration income feeds the budget forecast. See budget variance and the weekly status report.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.