How do you run check-in at a hosted, invitation-only conference?

Two kinds of check-in

Everything below inverts the usual advice, so it is worth being precise about when it applies.

The tell is who is paying. If you booked the room, arranged the dinner and chose the roommate, you have obligations to communicate that a ticket buyer does not create. And because arrivals are spread across a whole day rather than compressed into ninety minutes, you have the time.

Do not run a hosted event on a throughput desk. Two or three lanes plus an enquiry lane, open from early morning to late evening, is the shape. The constraint is not lanes, it is hours.

The desk is the only moment you have everybody

Guests do not read the pre-event email. They read the subject line, note the dates, and arrive.

So the desk carries the briefing. What belongs in it is anything that is conditional on this specific guest and actionable in the next few hours:

Your room is booked for two nights — the front desk will need your ID.

You are sharing with [name].

Your checkout is the tenth. Rooms are needed for the next group, so please check out before nine.

You are attending both conferences, so come back to this desk on the tenth for your second badge.

Breakfast is in the room rate; your voucher shows where lunch and dinner are.

Scan the code on your badge for the agenda.

We have arranged invoices with the hotel in advance so there is no queue at checkout — please confirm your details when you check in.

Seven lines. Perhaps ninety seconds. Every one of them prevents a phone call, a queue, or a guest missing something.

Three rules make this work rather than becoming a monologue:

• Only say what is conditional. If it applies to everyone and it is printed on the voucher, it does not need saying. If it is specific to this guest — their roommate, their checkout date, their second badge — it does.
• Generate it, do not memorise it. The script differs by attendee category, by whether they are staying, by which conferences they attend, by whether they pay their own way. A volunteer cannot hold that in their head. It should appear on the screen with the guest's record: two nights, sharing, checkout the tenth, both conferences, self-paying.
• Write it once, centrally. The wording for a delicate item — a checkout time you are enforcing, a cost the guest is bearing — should not be improvised by seven different people at seven desks.

Script the venue's staff too

This is the step almost nobody takes, and it is where the guest experience actually breaks.

Your guest leaves your desk and walks twenty metres to the hotel front desk, which is staffed by people who do not work for you, have not been briefed, and are dealing with your entire arrival curve at once. Whatever happens there is part of your event.

Give the front desk a written brief covering:

• Dates to verify. Arrival and departure per guest, checked against your list, with a route back to your team when they do not match.
• Invoice details to collect. For guests whose details you did not supply. Pre-arranging invoices removes the checkout queue on the final morning, which is the second-worst queue at any hosted event.
• Which guests pay for what. Some attendees at partner and distributor events cover their own costs. The front desk needs the list and the amount.
• Extra housekeeping cover. A hundred simultaneous arrivals will outrun a normal cleaning schedule.

And most importantly, the words for when a room is not ready, because that is the failure that will happen:

I am sorry — with so many arrivals your room is not ready yet. Please make yourself comfortable in the lobby; the concierge can store your luggage and there is water available. Your room will be ready by [time]. If you prefer, you are very welcome to leave your bags and go into town, and check in when you return.

An apology, a concrete time, and two options. Not “it'll be a while.”

While you are there, put the practical answers within reach of the desk: what is nearby and how far, what the hotel itself offers, what a guest with a free afternoon can do. Your reception team will be asked this all day, and “I don't know” from the person who checked them in reads as an event that was not thought through.

Hosted events have money in them

At a public conference the money question was settled at registration. At a hosted event it resurfaces at the desk, and it is delicate.

Some guests pay for part of it. Partner and distributor programmes commonly have the organiser covering the event and the guest covering their own room, or a fee agreed in advance. The desk must state the amount plainly, route them to pay, and — this matters more than it sounds — specify the invoice category, because the guest is expensing it and the wrong category creates work for them weeks later.

Handle it privately. A cost conversation happening in front of the next guest in the queue is a bad moment. This is one more reason for an enquiry lane, and for enough desk spacing that conversations do not carry.

Settle invoices before checkout, not at it. Collecting invoice details at arrival and pre-arranging them with the venue is the single most effective way to avoid a queue at the front desk on the last morning, when everyone is leaving for the same flight.

Back-to-back events with overlapping guests

Large organisations frequently run two conferences on consecutive days at one venue — an internal meeting followed by a partner event — with three overlapping populations: guests attending only the first, only the second, and both.

This is harder than it looks, and almost every part of it lands at the desk.

• Different meal vouchers per combination. A guest attending both eats at different places on different days than a guest attending one. The voucher is issued at check-in and has to be right, because nobody re-issues meal vouchers at a restaurant door.
• A second check-in for the second event. Guests attending both need a second badge, which means coming back. The only reliable way to make that happen is to tell them at the first check-in and print it on something they keep.
• A checkout deadline you have to enforce. If the second group needs the rooms, the first group has to leave by a specific hour. Enforcing this is unpleasant, and doing it at the desk on arrival — kindly, with the reason given — works far better than a note under the door on the last morning.

The general principle: a guest's itinerary is a property of their record, not of the event. Two guests standing at the same desk on the same morning may have entirely different instructions. If the desk cannot see which, it will give both of them the same instructions, and one of them will be wrong.

Arrivals do not stop when the desk does

At a hosted event with guests flying in from everywhere, someone always lands at midnight.

The pattern that works:

• Desk open long — early morning to late evening, longer than the casual staff shift.
• Casual staff work a shorter shift than the desk is open. Your own team covers the tail.
• After the desk closes, pre-print every remaining badge. The guest goes straight to the hotel front desk, and collects the badge at the desk in the morning.
• Somebody meets them. Not necessarily at a desk — but a guest arriving at midnight should be met by a person, not by a sign.

Print named badges in advance for senior guests — the ones whose names you already know and who should not queue. Assign a named person to collect them, at a named time, before the event opens. It is a two-line table in the plan and it prevents the most visible possible failure.

Desk conduct

Small things, and they are the difference between a desk that reads as premium and one that does not.

• Stand. Staff stand while checking guests in and sit only once the arrival peak has passed. At a hosted event the desk is the first physical impression of the whole programme.
• Keep the desk clear. Personal belongings out of sight. Materials stacked, not sprawled.
• Issue gifts once and mark it. Where every guest receives something, a mark on the back of the badge as it is handed over is a complete, unfalsifiable, zero-cost record. Do not build a system for this.
• Balance the dining rooms at the door. Where meals split across two restaurants, issue the two voucher types alternately at check-in and control headcount at each restaurant door. Left to choose, guests all go to the same one.

No proxy check-in. A colleague cannot collect someone else's badge. Room allocation, roommate, dietary requirements and the briefing are all personal, and handing a badge to the wrong person breaks the chain. But refuse by redirecting, never by blocking:

We're not able to check in on someone else's behalf — but the desk is open all day. What time is your colleague arriving?

Coordination across many owners

Hosted events are rarely run by one team. Invited customers belong to one owner, channel partners to another, media to a third, exhibitors to a fourth — each nominating and approving their own guests.

Two things keep this from collapsing.

• One named owner per channel, published to everyone. Every guest belongs to exactly one owner, and every person on the project knows who to ask about any given guest.
• Owners work in the system, not in a spreadsheet they send you. Give each of them access limited to their own segment, and train them — properly, with a written guide they keep. Half a day spent training a dozen coordinators eliminates weeks of list reconciliation, and it removes you from the middle of every routine question.

Keep the guest categories aligned with those owners: invited customers, channel guests, media, exhibitors, and — a category worth its own line — guests invited by exhibitors, so their attendance is attributed to the exhibitor who brought them.

What actually goes wrong

Where software actually helps

Four places, and they are the ones to test a system against before a hosted event, ours included:

• A guest record that carries the itinerary. Nights booked, roommate, checkout date, which events, which meals, who pays. If the desk cannot see it, the briefing does not happen.
• A briefing that is generated, not remembered. The conditional lines appearing on screen with the record, so a casual hire delivers the same message as your event manager.
• Segmented access for channel owners. Each coordinator seeing and approving only their own guests, with attribution preserved to the individual owner — including exhibitor-invited guests.
• Badges that can be printed early or printed live. Named guests in advance, everyone else on arrival, from one list.

Everything else here is hospitality — what you say, who says it, and whether you thought about the guest who lands at midnight. No tool decides that for you.