Delegate pricing and ticket revenue
Diagnosing weak paid registration before cutting prices
Registrations are behind where the committee hoped, and someone has proposed a discount.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A price cut fixes only one cause of slow registration. Before changing the price, find where people drop out: not reaching the page, reaching it and leaving, starting and abandoning checkout, or being unable to get approval to pay.
Count each step, ask a small sample of the people who did not register, and match the cause to the response. Cut the price only if price is the cause you can show.
Look at the funnel before the price
Use only your own counts. Where a figure is missing, write unknown, because a guess will point you at the wrong fix.
| Step | What to count | If it is weak, check |
|---|---|---|
| Reach | Invitations sent, opened, page visits by source | Is the right audience hearing about it, through the right channels? |
| Interest | Time on programme page, enquiries received | Is the programme and speaker line-up clear and relevant? |
| Start | Registrations begun | Is the page clear on date, place, price and what is included? |
| Complete | Registrations finished against started | Is checkout, payment or the form a barrier? |
| Approve | Enquiries asking for invoices or approval letters | Do employers need documents or time you have not planned for? |
| Commit | Registrations by week against the earlier pattern | Are people waiting for a deadline or a decision? |
Causes that look like a price problem but are not
- Programme not yet published, so people cannot justify the cost to their employer.
- Dates clash with another industry event, a holiday or a financial year-end. Check against your own calendar.
- Employers need an approval letter, invoice or budget cycle that has not caught up yet.
- Registration form is long, or payment fails for some methods.
- The invitation reached the wrong people, or reached them once.
Run the diagnosis in this order
- Pull the counts for each funnel step and mark the largest drop.
- Compare registrations by week with last year's event or a comparable event of your own, if you hold that record.
- Contact a small, varied sample of invitees who did not register and ask one open question: what would you need to decide? Record answers without leading the person.
- Match each recorded reason to a cause and a response: communication, programme, process, approval or price.
- If price is a cause, test it as a scenario in the early-bird calculator and the break-even calculator, and agree in advance what discount the budget can afford.
If price is the cause
- Model the effect of a cut on contribution, not only on the number of seats. See ticket revenue and contribution.
- Consider targeted options first: a concession for a defined group, or a group rate. See member, non-member and group prices.
- Think about people who have already paid, and decide how you will handle them.
- Avoid inventing urgency. See early-bird deadlines.
Questions to settle with the committee
- What decision will we take at each registration level, such as keep, push, reprice or reduce scale?
- Who approves a price change, and by when?
- What do we tell members and earlier registrants if prices change?
Worked example · Fictional example
A fictional accountants' forum finds the real cause
Fictional organisation and figures, illustrative only.
Forum Fiktif Perakaunan Tahunan has 62 registrations from 500 invitations at six weeks out, behind the committee's hope. The proposal is a 20 percent discount.
The secretariat counts 1,400 page visits, 210 started registrations and 62 completed. Of 148 abandoned, most stopped at the payment step. Six of eight invitees contacted say they need an invoice and manager approval, and two did not know the programme. The team publishes the programme, adds invoice payment, reaches out to employers and reviews the position in two weeks before deciding on any price change.
Use this yourself
Weak registration diagnosis worksheet
Copy into a spreadsheet. Write unknown where you have no figure. Complete it before any price discussion.
| Funnel step or cause | Our count or evidence | Compared with (last event or plan) | Likely response | Owner and date |
|---|---|---|---|---|
| Invitations sent and audience match | ||||
| Page visits and enquiries | ||||
| Registrations started | ||||
| Registrations completed | ||||
| Invoice or approval requests pending | ||||
| Programme and speakers published? | ||||
| Date clashes found | ||||
| Reasons given by non-registrants (sample) | ||||
| Price as a stated cause? Evidence: |
Handle it in-house, or bring in help?
Your team can usually handle this when
- You can pull funnel counts from the registration system without help.
- The secretariat can contact a sample of invitees and record answers.
- The committee agrees to wait for the diagnosis before deciding on price.
Outside planning help earns its fee when
- Counts sit in separate tools and nobody can join them up.
- The committee is split between cutting price, extending promotion and postponing.
- Finance needs a defensible view of income scenarios before any change.
Need a clear read on slow registration?
An Event Blueprint or planning diagnostic can set out the funnel counts, the sample questions, the decision points and the scenario view of income, with an owner for each response. A project lead can then coordinate the agreed fixes with your registration supplier and promotion team. Whether to change price remains your committee's decision, and no registration outcome is promised.
Questions organisers ask
How early can we tell registration is weak?
Compare weekly counts with a prior event of your own as soon as you have two or three weeks of data. If you have no comparison, use the funnel steps to find where people drop out.
Should we ask people why they did not register?
Yes, with a short, open question and a small sample. Record the words they use, and avoid suggesting an answer such as price.
Is discounting ever the right answer?
Sometimes, when price is the cause you can show. Model the effect on contribution first, and decide how earlier registrants will be treated.
What if the audience is simply too small?
Then review format, scale and cost base with the committee before the price, because a smaller event may suit the audience better.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.