How to manage company group bookings for a paid conference

So a company wants to send a team to your conference. The person emailing you can confirm the number of places, but their manager has to approve the spend. Finance wants the total in writing. The attendees haven't been chosen yet. Can you hold the tickets while everyone works it out?

Yes, if you have a clear process for what happens next. Manage conference group registration by separating the company's purchase from each person's attendance. Agree who can authorize the booking, what secures the places, when attendee details are due, and how changes work. Then keep the payment, remaining tasks and individual tickets connected to the same booking reference.

That distinction matters commercially. A promising conversation isn't money collected, and money collected doesn't tell you whether everyone has a usable ticket. When you treat those as separate questions, you can support a company buyer without reserving capacity indefinitely or leaving your registration team to reconstruct the booking at the door.

This guide follows an illustrative company booking through approval, payment, attendee registration and arrival. The example company, quantities and deadlines are fictional operating examples, not industry benchmarks. The aim is a process you can adapt to your conference, with enough flexibility for the buyer and enough certainty for your event business.

Start with the buyer, the coordinator and the attendees

The first thing you want to do is find out who you're speaking to. A company coordinator might arrange everything while someone else approves the purchase. The billing contact may need documents but have nothing to do with choosing the attendees. One enthusiastic employee may have started the conversation without permission to commit the company at all.

Ask who can accept your offer and authorize changes to the number of places. Ask who should receive payment documents, and who will make sure the attendees complete their information. These responsibilities can belong to the same person. You need to know when they don't, because each delay needs a different response.

Suppose a fictional business, Northfield, wants eight full conference passes. Its learning coordinator organizes the booking, a department head approves it, and finance pays. You don't need to involve every person in every email. The coordinator needs the booking status and outstanding actions. The approver needs the offer. Finance needs the agreed payment information. Each attendee needs their own arrival instructions and access details.

Keep the company relationship distinct from the attendee record. If you enter the coordinator's email for everybody, you may have a complete payment record but no reliable way to reach the people attending. If the coordinator changes jobs, your entire group can become difficult to contact. Wherever your registration system supports separate buyer and attendee details, use them.

Agree a named backup contact for the company too. This is particularly useful when the booking period crosses leave, holidays or a change of team. The backup should have a clear role, rather than receiving every attendee's private information simply because they are copied into an email.

Make the offer easy to approve internally

Company buyers often have to explain your conference to someone who hasn't seen the event page. Help them do that with a short, accurate summary they can forward. Include the dates, location, passes being purchased, what's included, the total payable and the point at which the booking becomes confirmed.

Explain why sending a team could be useful in terms your programme can support. Perhaps the company wants people from different departments to attend different sessions and share what they learn afterwards. Point to those sessions. Don't promise a financial return you can't substantiate, or turn a networking opportunity into guaranteed business for the buyer.

This approach already appears in professional conference practice. The Society for Hospitality and Foodservice Management offers a conference attendance justification toolkit to help prospective attendees explain the educational and business value to their organizations. The useful lesson is to help your contact communicate the actual offer. You don't need to write their company's business case for them.

For Northfield, the coordinator could forward this wording: "We're proposing eight full passes for our product and customer teams. The passes include the published conference sessions and meals listed in the offer. Travel and accommodation are separate. Please approve the stated total before the offer expires so we can complete payment and confirm the places."

Supply an offer reference and a version date. If the buyer later changes the quantity or adds a workshop, issue an updated offer and identify what changed. Otherwise finance might approve the original total while the coordinator expects the revised package. A booking that appears slow can simply be waiting for people to agree which document is current.

Keep your internal approval help proportional to the sale. A concise, forwardable explanation can remove an obstacle. Preparing a bespoke presentation for every small group can consume the value of the booking before you've sold a ticket.

Choose a booking route the company can finish

Ask whether the company can pay through ordinary ticket checkout before offering a more complicated route. If its authorized buyer can purchase the required quantity directly, that may be the simplest answer. Send the correct event link, explain the relevant ticket type, and confirm what attendee information you'll need afterwards.

If the company needs an agreed invoice process, establish that before you promise places. Find out whether it needs supplier onboarding, an approved reference or particular billing details. These requirements affect whether the buyer can pay on your timetable. Our event invoice template for group bookings covers the payment document itself; here, the question is whether that payment route can support the booking deadline.

A third possibility is that employees register individually while the company coordinates attendance. Be clear about who pays in that arrangement. If employees must claim reimbursement, say so. If the company is paying centrally, don't quietly send everybody to a checkout that requires them to use their own cards.

Choose one route for Northfield's eight passes, then communicate it to the whole group. Mixing a central company order with separate employee purchases can produce duplicate tickets and awkward refunds. If the coordinator says some colleagues already bought, check the actual orders before selling another allocation. Agree how those existing purchases fit the group rather than assuming they can be merged automatically.

Loopyah's ticket checkout supports guest purchases and confirmation emails linking to QR tickets. Its public ticketing page also describes configurable per-buyer ticket limits. Check your event's limit before directing a company buyer to buy the whole allocation. The published checkout features don't establish a company approval or procurement workflow, so test the company's actual requirements before committing to that route.

Set a hold that has a real end

The uncomfortable part of group bookings is deciding how long to reserve places before money arrives. You want the company to buy. You also need those places available to people who can pay now. An open-ended promise to hold tickets pushes that uncertainty onto your event.

Separate an indicative offer from a capacity hold. An offer can state the current price and availability without taking tickets off sale. A hold reserves an agreed quantity until a stated deadline. A confirmed booking meets the condition you agreed, such as verified payment. Choose the conditions your business can support, and explain them before the buyer accepts.

For Northfield, you might reserve eight places until a particular date and time while approval is pending. Your message should say whether the price is protected too, what action confirms the booking, and what happens when the deadline passes. Include the time zone. "Friday" doesn't tell a finance team in another country when your hold expires.

If your system cannot reserve those places, don't describe an email promise as a protected allocation. Either manage the hold in a supported capacity process or tell the buyer availability remains subject to purchase. Your public sales inventory and your commitments to company buyers must agree. Otherwise you can sell the same places twice without realizing it.

Set an extension rule for your team. A coordinator asking for more time deserves a quick decision, but staff shouldn't extend holds simply to avoid an awkward conversation. Check current availability, the likelihood of payment and the next operational deadline. Record the new expiry when you approve an extension, and tell the buyer which previous deadline it replaces.

When the hold ends, follow the terms you communicated. Confirm whether the allocation has been released and invite the company to check current availability. Leaving the booking marked as held after expiry makes the next buyer's availability harder to trust.

Keep payment status separate from registration status

Once a company accepts the offer, the booking still has several things to finish. Payment might be pending while attendee details are complete. Payment might be complete while only some attendees are named. Calling everything "confirmed" hides the action your team needs to take next.

Use simple descriptions that staff and buyers can understand. Record whether the offer has been accepted, whether payment has been verified, how many places are purchased, how many attendees are named, and whether each person has received usable access information. Keep these facts together under the booking reference. You don't need a second homemade system if your existing tools already show them reliably.

For Northfield, the coordinator accepting eight places doesn't authorize you to report eight paid tickets. A finance email saying payment has been arranged doesn't prove funds have arrived either. Check the payment against the order or invoice reference. If your agreement allows confirmation before settlement, record that exception and the person who approved it rather than pretending the booking is paid.

This distinction also protects your event forecast. Report confirmed paid business separately from offers and unpaid holds. Company bookings can be commercially valuable, but a sales forecast becomes misleading when hoped-for orders appear in the same total as collected revenue. Your venue and supplier bills will arrive whether those approvals finish or not.

When payment arrives, send a clear confirmation of what the company has bought and what remains outstanding. "Your eight passes are paid. We still need the attendee names and email addresses by the agreed deadline" is more useful than a generic thank-you message. It closes the payment task and opens the registration task without asking the coordinator to guess.

Keep the purchase record even if people later change. A substitution changes the person attending. A cancellation may change the money owed. Treating both as a name edit makes the financial history unreliable.

Collect attendee details without rebuilding the sale

Company buyers may know the quantity before they know the names. You can allow that if your event and registration process support it, but decide in advance what remains incomplete. Unnamed places need an owner and a deadline. Otherwise they become a last-minute chase for your team.

Collect the information required to admit and serve each attendee. Their name and a reliable contact address are usually the starting point. Badge information, session choices or access requests may need separate collection depending on the conference. Our event registration form guide explains how to separate buyer fields from attendee fields without turning checkout into a long questionnaire.

For Northfield, the company coordinator can confirm the list of people while each attendee completes their own personal requirements. That avoids asking a coordinator to guess a colleague's dietary needs or access arrangements. Tell attendees why you're contacting them, identify the booking, and make clear that completing the information doesn't require another ticket purchase.

Use the registration system's supported attendee invitations or editing process where available. If your tools can't do this, establish a controlled alternative before opening group sales. Decide who updates the actual registration records and who verifies that the changes reached ticket delivery and badge production. A spreadsheet attachment in someone's inbox isn't evidence that those systems have changed.

Make the form understandable to someone who hasn't followed the company emails. The World Wide Web Consortium's guidance on labeling form controls explains why clear labels matter for people using assistive technology as well as other users. Label buyer and attendee details explicitly, explain required fields, and identify which person an answer concerns when the form contains multiple registrations.

Before sending invitations, try the process as a group buyer and an attendee. Find out whether a person can complete their information without seeing colleagues' private answers, whether an incorrect address can be corrected, and whether the coordinator can see the completion status they actually need.

Use deadlines that match the work behind them

Your payment deadline, attendee-detail deadline and substitution deadline do different jobs. Payment secures the purchase under your terms. Attendee details support tickets, badges and services. Substitution rules explain how a purchased place can move to somebody else. Using one vague "registration closes" date for all of them creates unnecessary confusion.

Work backwards from the commitments you have to make. If your badge supplier needs the approved list on a particular day, allow time for checking names before that handoff. If catering needs confirmed requirements, collect them before the supplier's deadline. A date chosen because it looks neat on the website won't help when it falls after the actual production decision.

An illustrative sequence for Northfield would be approval and payment first, names next, then personal requirements and final arrival instructions. You might allow later substitutions while explaining that certain meals or printed materials can no longer be changed. Those timings should follow your conference arrangements. There is no universal number of days that makes every group booking safe.

Put the relevant deadline beside the action. The coordinator's payment message needs the payment date. An attendee invitation needs the date for completing their details. A change request needs the rule that applies to that change. Repeating every policy in every message makes the urgent task harder to find.

When a deadline is missed, describe the outstanding information and the consequence. Perhaps you can still issue the ticket but can no longer guarantee the requested printed badge. Perhaps an unpaid hold expires. Apply the consequence you agreed, rather than introducing a new penalty when staff are already under pressure.

Before you refuse a late request, check whether the restriction is real. Some changes are difficult because a supplier has committed costs. Others are easy within your system. A reasonable exception can help a company return next year, provided it doesn't create an unmanageable promise for the team delivering the event.

Protect personal requirements from the group email

The company pays for the booking, but that doesn't mean its coordinator needs every personal detail you collect. A request for an accessible route, a meal adjustment or a private conversation about attendance can require more care than a badge-name correction.

Explain what the coordinator can see. Completion status may be enough: attendee details submitted, ticket delivered, action outstanding. Let each attendee send personal requirements through the appropriate channel. Avoid a shared group sheet that reveals everybody's answers, especially when the sheet is accessible to people who only need to check payment or attendance.

The UK Information Commissioner's Office describes data minimisation as collecting information that is sufficient, relevant and limited to the stated purpose. Its guidance is about UK data protection rules, but the practical question helps any organizer: what will we do with this answer? If the answer is nothing, don't request it just because the field exists.

Limit access to the people arranging the service. Your registration desk may need to know where to direct an attendee, while the catering contact needs the relevant meal instruction. Neither necessarily needs the full conversation. Build that distinction into your handoff so staff don't circulate a complete personal record whenever someone asks about one requirement.

The US Federal Trade Commission's guide to protecting personal information also advises businesses to keep information they need, protect it and dispose of it when no longer required. Review exported group lists and attachments as part of that process. A controlled registration system loses much of its value if copies remain in personal inboxes indefinitely.

Be clear about your own privacy notice and applicable obligations. The company submitting a colleague's details doesn't settle every question about how you may use those details. In particular, buying admission and agreeing to future marketing are separate matters. Keep your group registration messages focused on completing and delivering the booking.

Handle substitutions as a recorded change

Someone in Northfield's group can no longer attend, and the company wants to send a colleague instead. That's a normal company booking question. Your process should answer it before the coordinator starts forwarding tickets and hoping the badge desk will sort things out.

Publish who may request the change, which places can be substituted, whether eligibility affects the price, and any deadline or charge. Tell the buyer what happens to optional sessions and personal requirements. A substitution into the full conference pass doesn't necessarily mean a sold-out workshop can be reassigned on the same terms.

The American Geophysical Union's annual meeting registration policies illustrate the need for specific rules. AGU requires written substitution requests from the original registrant, transfers the full registration, and says member and promotional rates don't transfer to the substitute. That's one organizer's policy, not a rule every conference must copy. It shows why "name changes allowed" leaves important questions unanswered.

Choose an authorization rule that fits your company booking arrangement. If your terms permit the authorized company coordinator to request substitutions, record that permission when the group buys. If the original attendee must approve, make that requirement clear. Don't let an unfamiliar person replace a name merely because they know the booking reference.

Update the actual registration and access records through your supported process. Confirm whether the old ticket needs cancellation or replacement, whether the new person has received access, and whether badges or reserved activities changed. Where the ticket system supports transfers, use it. Don't assume editing a badge list has also changed the ticket's valid holder.

Send the company a confirmation of the change and the new attendee their own instructions. Keep the record of who requested it, what you changed and when. Our ticket transfer policy guide develops these decisions for ticketed events more broadly; your company terms should explain the parts relevant to a purchased team allocation.

Keep cancellations and extra places distinct

Substituting a colleague preserves a purchased place. Reducing the group size changes the booking itself. Decide how those requests differ before a company asks for money back. Explain whether cancellation applies per place or to the whole order, and refer to the refund terms accepted at purchase.

If Northfield drops from eight attendees to six, don't simply delete two names. Establish whether the company is keeping the places for replacements, canceling them under your policy, or accepting that the paid places will go unused. Record the decision against the purchase. Any refund or credit needs to follow the supported payment and accounting process.

Extra places need an availability check too. A company that bought early may assume colleagues can join later at the same price. State whether additions use the original rate or the current rate, and whether they need a new order. Don't guarantee the same package when particular sessions or ticket types have sold out.

If the group price depends on quantity, explain how reductions affect it before accepting the booking. That's a pricing decision rather than an administrative detail. Our group ticket discount guide covers the commercial calculation. A generous company booking process doesn't require a discount, and a discount doesn't compensate for unclear changes or payment terms.

When somebody asks for an exception, evaluate the request against real costs and remaining capacity. A refund may be possible under your terms; a colleague substitution may be simpler for everyone. Offer the options you can actually deliver without pressuring the buyer into one or promising an exception your team hasn't approved.

Keep the updated quantity consistent everywhere it matters. Payment records, registration counts, badge production and catering may have different owners. Tell the relevant owner what changed. A company message confirming six attendees won't prevent you paying for eight meals if nobody updates the supplier commitment.

Write updates around the next action

A company coordinator shouldn't have to compare your latest email with an old attachment to understand the booking. Whenever something changes, state the current position before asking for the next action. Include the booking reference in the subject so finance and registration staff can find the same conversation.

Here's an illustrative message after Northfield pays. Replace the brackets with the actual agreed details before sending it.

"Your booking for eight full conference passes is paid and confirmed under reference [booking reference]. We have attendee details for six colleagues and still need details for two. Please complete the remaining registrations through [supported registration route] by [date, time and time zone]. This completes information for passes you've already purchased; no additional payment is required."

Then explain the delivery arrangement separately. "Each attendee will receive their access instructions through [verified delivery method]. Please ask colleagues to check that they've received them before travelling. If somebody needs replacing, contact [authorized team or supported process] with the booking reference and follow the substitution terms agreed with your booking."

That message answers the question the coordinator is likely to ask first: has the money been received? It also names the unfinished task without making them feel that the whole booking is in doubt. If every attendee has completed their details, remove that request. A standard template should help you communicate the current facts, rather than sending everyone the same warning.

For a stalled approval, use different wording. "Your offer remains open until [expiry]. We haven't confirmed payment, and the eight places are [held until the stated deadline or subject to availability, according to your agreement]. Please tell us whether your approval is expected before that time. We can check an extension, but it hasn't been agreed yet."

Avoid "everything is sorted" while tasks remain. The coordinator might interpret it as permission to stop following up with colleagues. Equally, don't send a payment reminder after funds have been verified simply because an attendee hasn't finished a form. Those mistakes tell the company your departments aren't communicating.

Make replying straightforward. Use a contact your team actually monitors, explain which details identify the booking, and assign someone to handle the response. If you rely on a general inbox, agree who takes ownership when a reply arrives. Confirm receipt when their request arrives, even if the decision needs more time. Otherwise a carefully written deadline message can still fail when the buyer replies promptly and nobody acts before the hold expires.

Prepare every attendee to arrive independently

Payment settles one part of the booking. Arrival preparations are complete when each person can get into the conference under the agreed terms. Those moments may be weeks apart. Treat ticket delivery and attendee preparation as work that needs verification.

Ask whether the company coordinator will distribute access details or whether your system sends them directly to attendees. Test the chosen method. Nobody should need the coordinator standing beside them at the door, particularly when the team arrives on different trains or attends different days.

Our event confirmation email guide covers the information buyers need after payment. For company groups, add explicit distribution instructions if the buyer holds multiple tickets. Explain how an attendee gets help when their name is missing or their ticket hasn't arrived, and avoid exposing other people's tickets in a shared message.

Brief your registration team on the latest group changes before doors open. Identify who can resolve an unpaid order, an unnamed place or a substitution request. Check-in staff need the current admission information and a route for exceptions. They shouldn't have to negotiate company payment terms while a queue grows.

Loopyah allows organizers to grant staff check-in access so they can scan QR tickets from their phones. That helps the admission task without sharing the organizer's login. It doesn't replace your decision about who can approve a disputed company booking, so appoint someone with that responsibility and make them reachable during registration.

After the conference, close remaining payment questions and ask the coordinator what made the booking difficult. Review the point where your team had to intervene. If every company needed help distributing tickets, fix that explanation before the next sale. If approvals regularly outlasted your holds, revisit the offer and timetable. Start the next group booking with a process that reflects what you learned.