How do you run a large-scale conference from brief to close?

What “large-scale” usually means here

Not a headcount trophy. The shape that needs this map is an offline conference where several of these are true at once: more than one legal entity or bank account in play, more than one currency on the ticket or the invoice, a programme that creates an arrival peak, and a close that has to finish before memories and bank statements diverge.

If every sale, refund and settlement stays inside one entity and one currency, the same phases still apply. You simply have fewer decisions to lock at the start: which entity settles and which currency to price in are already answered.

Six phases, in the order the work actually runs

Nothing below is a marketing funnel. It is the order in which irreversible choices show up. Jump into any phase; hand single topics to the people who run them.

The open playbook expands each row into stand-alone topics. Open /playbook and use the phase guide to jump — full link in Read next below.

Define: five locks that are cheap now and expensive later

Write these down before the kick-off pack travels. Moving any of them after first sale, first invoice, or badge sign-off usually means re-issuing orders, reprinting access rules, or arguing across two tax years.

• Settlement entity — which company takes the money and returns refunds.
• Pricing currency — what the buyer sees as the ticket face.
• Tax and place of supply — locked by the first invoice you cannot quietly rewrite.
• Ticket categories — not a design choice; they become the identity system for badges and access.
• Time zone of record — a time without a zone is venue-local; everything else must carry its zone.

Define also sets the price floor: fixed costs divided by paying attendance, plus the variable cost per head. Count paying attendees only. Two fees get confused in that sum. The payment fee goes to your payment provider; a platform fee is what a ticketing platform takes on top, where it charges one. Put them on separate lines; the ticket fee calculator under Read next compares the two.

Related deep dives on this site (linked under Read next): who sells the ticket, pricing conference tickets, refunds and cancellations.

Build: the programme sets your arrival peak

Venue capacity and badge design matter, but the timetable decides when people arrive. A single keynote start packs the door; staggered openings spread it. Door staffing and lane counts are downstream of that choice — not a volunteer surprise on the morning.

Ticket categories here are an identity system: each category must map to a printable badge rule and an access rule you can still explain at 08:30. Pricing mechanics belong in Build, not as a checkout afterthought: early-bird deadlines that are enforced, allocations that are real, and an invited price that replaces a promo code instead of stacking with it.

Sell: every registration should know where it came from

One link per source, where a source is a campaign, an outside partner or one sales rep. Judge each on four numbers: link opens, registrations, approved and paid, checked in. If two sources share a URL, the debrief ends at “we do not know which channel worked.” If a partner earns commission, agree which of the four numbers it is counted on before the links go out.

Invitation-only events need three seats, not one: an inviter who submits names and sees only their own list, a reviewer who approves and holds the quota, and an administrator who gives final confirmation. Write three rules down before the first invitation goes out:

• Two reps, one prospect — who keeps the credit and who rules on a dispute, decided once and not per deal.
• A free seat — always goes to a reviewer. Nobody approves their own invitee.
• A request nobody answers — passes to a named person after a fixed number of days.

When the channel is a sales force rather than a campaign URL, the operating detail is in the sales invitation field guide: measure value per invite and channel through check-in, keep attribution clean for CRM, and hold seat quotas with first-inviter credit.

Four messages carry the registration: confirmed, pending or declined, doors open soon, and not yet arrived. They are contract performance. A save-the-date is marketing and needs consent, and so does any survey that promotes something.

Some forms are now filled by an AI agent acting for the attendee. The answers arrive complete and plausible, the referrer is often missing, and blocking bots turns a real person’s assistant away. Verify at approval or payment, confirm to the attendee’s own address, and judge channels on checked-in rather than clicks. Sponsors need a written list of what you owe them, and an agreed reporting format, before the floor opens.

Run: size the door against the peak, not against hope

Hand volunteers pages they can follow after one hour of briefing: shift plan, lane layout, desk scripts, what to do when the network fails. Lane count is arithmetic against the arrival peak and throughput — then one spare lane, because one printer or scanner will fail.

The playbook’s worked example uses 3 people per lane per minute, which is a pre-printed badge handed over without a word. The free check-in lane calculator allows about 25 seconds a person, greeting included, so it sizes more generously, and it exports an Excel manual from your numbers: countdown, lane-by-lane staffing, kit list, volunteer scripts and an exceptions sheet.

Related deep dives (Read next): on-site check-in, session access and attendance, hosted invitation events, controlled-list registration.

Close: counts, then money, then the debrief

• Counts within 24 hours — who arrived, which category, which sessions — while the floor memory is still fresh.
• Money within 48 hours — settled by entity, not pooled into a story nobody can unpick.
• Debrief within a week — result first, then causes with evidence and changes with an owner and a date. It comes after the first two, or the discussion becomes inventing numbers.

Skipping the first close turns the rest into arguments, and it needs one written definition of attendance: a scan at the entrance, a scan anywhere and a steward marking present are three different numbers. Sign-off and archive are what let next year’s team inherit decisions instead of Slack archaeology.

Keep the feedback survey to six questions, all of them about this event. Add an offer or a next-event pitch and it becomes marketing, which needs consent.

Comply: disclose what you must, audit in an afternoon

Where pricing mechanics and AI-assisted systems meet the law, treat the playbook pages as an operator summary with dates — not legal advice. Since 2 Aug 2026 the EU AI Act’s transparency rules apply: an AI assistant, generated imagery or a synthetic voice has to be disclosed at first exposure, and the rule follows the attendee, not the organiser’s home country.

Attendee data rules decide what may cross the venue network and what stays on the desk that printed the badge. An attendee directory shows only the people who chose to be found, and contact details only after they accept.

Related deep dive (Read next): GDPR for event organisers.

How to use the open playbook with this guide

• Read this page once for the map.
• Open the operations playbook and jump to the phase you are in.
• Hand a single topic to the owner of that row — venue, finance, door lead, compliance.
• Download the PDF when you need a print pack for the war room; the web edition stays open for search and citation.

Examples in the playbook are fictional. Converted figures are marked and dated. A time without a timezone is venue-local.