Diagnosing an event registration shortfall
Registrations are behind where the committee hoped, and everyone has a different theory about why.
The short answer
Before changing anything, find which stage of the path is thin: people not reached, reached but not interested, interested but stuck at registration, or willing but blocked by date, approval or cost. Each cause has a different fix and a different owner.
Use your own counts at each stage, compared with this event's own targets and earlier events if you have them. Do not apply an outside benchmark.
Lay out the path with the numbers you have
Write the stages in order: invited or reached, opened or visited, started registration, completed registration. Use the definitions you agreed in registration funnel definitions so the committee counts the same way.
If a stage has no count, note that as a gap. Guessing the missing number is how teams end up fixing the wrong thing.
Match the symptom to the likely cause
| What you see | Likely area | First check | Who owns the fix |
|---|---|---|---|
| Few people reached | Invitation or list | Is the list current and are invitations going out as planned? | Invitation owner |
| Reached, few visits | Message or channel | Does the first line say who it is for and what to do? | Communications |
| Visits, few starts | Offer or relevance | Is the programme clear and is the audience right? | Event owner |
| Starts, few completions | Registration friction | Is the form long, is payment unclear, is approval needed? | Secretariat or finance |
| Interest voiced, no sign-ups | Date, approval or cost | Ask a small set of invitees directly what is blocking them | Event owner |
Ask people, in a few short conversations
Call or message a handful of invitees from each stage and ask one open question: what would have to be true for you to attend? Write down their words rather than coding them immediately.
Three to five honest conversations often show a clash with another event, a budget cycle or an approval step that no count would reveal.
Choose one change per cause and date it
- Pick the thinnest stage and the most likely cause.
- Make one change, such as shortening the form or adding a named endorser.
- Record the date, the owner and the count you will look at.
- Review after the next registration milestone, then decide whether to keep, adjust or revert.
- Use an attendance scenario planner to explore different outcomes without calling any of them a forecast.
Worked example · Fictional example
A committee finds the real gap
Fictional organisation and figures, for illustration only.
The Persatuan Fiktif Pegawai Pematuhan expects a half-day seminar to fill, yet registrations are slow. The secretariat's counts show many people open the invitation and visit the page, but few start the form.
Five short calls reveal that registration requires a company approval number most attendees do not have to hand. The committee makes the number optional, adds a line explaining how to find it, and moves the reminder to the week after month-end when approvals are processed.
Use this yourself
Registration shortfall diagnosis worksheet
Complete one row per stage, then pick one change.
- Stage name and definition used:
- Count at this stage, and date taken:
- Target or comparison point and where it came from:
- Gap seen (or count missing):
- Likely cause: reach / message / offer / friction / date, approval or cost:
- Evidence: counts, conversations, form data:
- One change to try, owner and date:
- Count to check after the change, and review date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have counts for each stage and one person who can test changes.
- The cause looks clear, such as a form problem or a date clash.
- The committee accepts small, reversible changes.
Outside planning help earns its fee when
- Several channels and partners each hold part of the picture.
- Stakeholders blame different causes and need a neutral read of the evidence.
- Fixes cross invitation, form, payment and partner promotion and need one coordinator.
Need a neutral read and someone to chase the fixes?
A conference project lead can consolidate counts from each channel, run the short invitee conversations, and turn the likely causes into dated actions with named owners. Your committee decides which changes to make and keeps authority over message and price.
Questions organisers ask
How far behind is too far behind?
That depends on your own target and earlier events. Do not use a general percentage. Set a milestone for each stage when you plan, and compare against that.
Should we extend the deadline straight away?
First find the cause. If people are blocked by approval or date, a longer deadline may help. If reach is the issue, more time without more invitations changes little.
Can we run a survey instead of calling people?
A short survey can add breadth, but a few conversations show reasons you did not think to ask about. Keep any survey to one or two questions and avoid leading wording.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.