When a trade show's pre-registration doubles in the final fortnight, three things have to cope: the form, the badge desk and the platform's pricing model. On eventcloud nothing is counted per visitor, so a surge changes your workload, not your bill. The limits that remain are operational, and for a visitor spike only two or three of them could ever matter.
Why Does Pre-registration Spike in the Last Fortnight?
Because visitors decide late and organisers keep nudging them. Exhibitors send their invitations, the show email goes out for the third time, a keynote speaker is announced, and a trade show that sat at 6,000 registrations for a month wakes up with 9,000 in ten days. Anyone who has stood behind a registration desk at a UK exhibition knows the pattern: the week before opening is the busiest week of the whole campaign, and the one where nobody has time to read an invoice.
The useful question is not "how do we stop the spike?" but "which parts of our setup get heavier when it arrives?". There are only three candidates: the registration form and its capacity rules, the badge and check-in workflow at the door, and the way the platform meters volume.
What Does a Registration Meter Do When Visitors Double?
It follows them. If a platform charges per registrant, per ticket or per badge, a surge is a bigger invoice by definition, and the final fortnight is exactly when the volume is least predictable. That is a perfectly legitimate model. It simply means the budget conversation happens after the marketing team has done its job, not before.
The published models show how different the shapes are. RegFox lists a per-registration fee that is capped per registrant, with the cap rising on its higher plans, plus card processing on top (RegFox pricing page, read 3 November 2026). Swoogo states that it does not charge per event or per registrant and prices by user (Swoogo pricing page, last modified 5 August 2026, read 3 November 2026). Bizzabo prices its Event Experience OS per user with a three-user minimum and lists unlimited registrations (Bizzabo pricing page, read 3 November 2026). Cvent does not publish prices; buyer-side write-ups report a per-registrant fee for its attendee hub and event app on top of an annual licence (InEvent, March 2026).
| Platform | What Grows When Visitor Numbers Double | Source and Date |
|---|---|---|
| RegFox | A per-registration fee on every registrant, capped per person, plus card processing | RegFox pricing page, read 3 Nov 2026 |
| Swoogo | Nothing per registrant; priced by user | Swoogo pricing page, modified 5 Aug 2026 |
| Bizzabo | Nothing per registrant; priced per user with a three-user minimum | Bizzabo pricing page, read 3 Nov 2026 |
| Cvent | Reported per-registrant fee for the attendee hub and event app on top of an annual licence; no published price | InEvent, Mar 2026 |
| eventcloud | Team seats only; registrations, attendees and events are not counted | eventcloud registration features |
That is a difference in model, not a verdict. If your visitor numbers are steady and known, a metered model is easy to forecast. If they spike, the question is simply which variable the invoice follows.
Which Limits Could a Visitor Surge Actually Touch?
Three, at most, and all of them are operational. The statement we use word for word: "Unlimited events, registrations and attendees on every plan. We count team seats, not tickets, so your bill does not rise because your event sells out. The limits that do exist are operational, not commercial: 99 of one ticket type per order line, 10,000 orders per Excel export, five languages per event, and one subdomain and one sending domain per organisation."
For a visitor surge, the order line limit matters when a company registers a coach party of 140 buyers: that is two order lines, or an attendee import if the list already exists. The export limit matters when you want a full visitor file on the morning of opening: filter by ticket group or date and export in slices. The language limit matters only if you add a sixth language to the form. Nothing in that list rises or falls with how many people register, and none of it can be bought past.
A Form for Every Audience. Answers on Every Badge.
Delegates, speakers and exhibitors each get their own registration form, and every answer flows to badges, emails and the Excel export.
How Do You Keep the Form Calm When Thousands Arrive at Once?
Give each audience its own form and set capacity before the surge, not during it. A trade show usually has trade visitors, exhibitor staff, press and VIP buyers, and each is a ticket group with its own questions, so a visitor never scrolls through exhibitor fields. Answers are checked as people type, which catches the typo that would otherwise turn up on a badge at the door. Capacity can be set per ticket type and for the whole event, and stacked price windows switch themselves, so an early visitor rate can hand over to a door rate on the date you chose without anyone logging in at midnight.
Exhibitor staff, press and VIP buyers should not queue with the public. Private ticket groups, reached only by a secret link, keep those registrations out of the open form, and promo codes can be limited to named email domains, which suits an exhibitor inviting their own customers. The registration features cover each of these, and the page for exhibitions and trade shows shows how they fit together for visitor and exhibitor registration.
Every registrant who fills in their details receives their own confirmation and ticket, with a nine-digit ticket number on it, and the person who books also gets an order confirmation listing who each ticket went to. That ticket number is what makes the next section work.
What Happens at the Door When 3,000 Extra Visitors Arrive?
The door is where a surge becomes visible, because queues are visible and invoices are not. Two paths run in parallel. Staff check people in from any phone or tablet with one link and a four-digit PIN, scanning the QR code on the ticket or typing the ticket number. The scanner shows name, email, phone, company, ticket and pass type, flags repeat scans and refuses refunded or unpaid tickets.
The second path takes pressure off staff entirely. A self-service Badge Kiosk is a laptop with a printer beside it: visitors type their ticket number, check the badge, correct their printed details if you allow it, and print, and printing checks them in. Because badges are designed in real millimetres with live data from the registration answers, the badge that prints is the one the visitor typed into the form. For design and printing detail, see the badge printing features.
A practical way to size the door: put the phone scanners on lanes for people who already printed or carry a ticket, and give visitors who want a fresh badge a kiosk. Each printer is a lane, so a surge means adding a laptop and a printer, not asking for a higher volume tier. Need name search at a staffed lane for visitors who forgot their ticket? Tell us how your door works, and we will talk it through at eventcloud.io/contact.
What Should You Decide Before the Surge, Not During It?
Four decisions made a week earlier save the most pain.
Capacity per ticket type and event-wide, so the form closes itself rather than relying on someone watching a dashboard.
The last price window and its end date, so the final switch to the door rate is automatic.
Which audiences get private links, so exhibitors and press register on their own forms.
How many kiosks and phone scanners you want at the door, and who holds the PIN.
If you are comparing platforms for a show that is growing, the question to put to each vendor is what, exactly, they count: seats, registrants, badges printed, scanners or leads. The related piece on what scales and what still has a ceiling at a sold-out conference lists the operational limits in full, and it works just as well as a checklist for your next vendor call.
Coming soon: a registration close date as its own setting. Need it for your show? Tell us at eventcloud.io/contact.
