Registration is a promise.
A plan is a commitment.

A day they built, not a programme they were handed

• Nothing to fill in to start. They browse, filter and build before anything asks who they are. The value lands first, which is the only reason they finish.
• Recommendations, not a list of everything. Tell it what you are considering and the programme reorders itself around you, instead of nine hundred words of PDF.
• Clashes solved, not discovered on the day. Two things at 10am is caught the moment it happens, with the alternative session offered right there.
• Full sessions still capture them. A waitlist with a real queue position, so a popular talk becomes another point of contact rather than a dead end.
• Someone real to meet. A current student in the course they are considering, bookable into the plan like any other session.
• It works on the day. A phone plan with rooms, a campus map and what is next — no download, no login, no app store.
• Reason to finish. A saved plan, a calendar file and a reward on completion turn a browse into a booking.
• It looks like the university. Your colours, fonts, logo, crest, campuses and Acknowledgement — not a third-party widget bolted to the corner of a page.

A live picture instead of a post-mortem

• The plan is the data. Not just who registered, but which sessions, which campus, which faculty and what they nearly chose instead. Zero-party, volunteered, consent-clean.
• Attendance you can forecast. Session-level demand as it builds, so you can move a talk to a bigger room in week two rather than turning people away on the day.
• Waitlists that manage themselves. Capacity, queue position and promotion when a place frees up — no inbox, no spreadsheet, no one manually emailing forty people.
• No rekeying. Every completion pushes to Salesforce, Marketo, Eloqua, Dynamics or Adobe Campaign with the answers attached, so nobody exports a CSV on Monday.
• Multi-campus and multi-date without the pain. Six campuses across four dates is a config change, not four separate builds and four separate programmes to keep in sync.
• Change it yourself. Sessions, times, rooms, capacities, copy and dates come from one config. A room change at 8pm on Friday does not need a developer.
• It cannot drift off brand. Palette, fonts, logo, crest and Acknowledgement are set centrally and inherited everywhere.
• Fast to stand up. A branded edition is a config plus a logo. Hours, not a redevelopment project.

Your brand, your domain

One self-contained build on your own subdomain, or embedded in a landing page. It does not need to live inside your CMS, so Squiz, AEM, Sitecore, Drupal and Optimizely are all equally fine.

Additive, not a replacement

If registration is already a first-party form wired to your CRM, this sits in front of it and hands the lead over warmer. There is no ticketing platform to rip out.

Reads and writes

Sessions, rooms, capacities and campus content come from your source of truth. Plans, consent and session choices go back to your CRM and marketing automation.

It keeps working

The plan is a phone itinerary with rooms, a campus map and what is next. Print it, add it to a calendar, or scan a QR at the gate. No install, no account, no signal anxiety.

Consent handled properly

Nothing is captured before the plan exists. Comms opt-in is explicit and channel by channel, and the wording is written with your compliance team rather than around it.

Joined to the rest

Imagine warms them up all year, Open Day converts the visit, Orientation lands the first week. One engine, one visual system, and each edition links to the other two.