Skip to content
EventConsultant

Delegate pricing and ticket revenue

Planning employer-funded group registration journeys

A training manager wants to register 12 colleagues and pay by one invoice, and your registration form was built for individuals paying by card.

Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

An employer-funded group has two customers: the person who pays and the people who attend. Plan the journey for both, covering who enquires, who confirms names, who receives the invoice, who gets the tickets and what happens when someone drops out.

Decide the steps and owners before you open registration, so each group is a routine process and not a string of email exceptions.

Map the journey from the employer's side

StageWhat the employer needsWhat you need to decide
EnquiryGroup rule, price and deadlineIs the group price published, or quoted on request?
BookingReserve seats before names are knownCan seats be held, for how long, and with what payment trigger?
NamesAdd or change attendeesWhen must names be final, and who can change them?
Invoice and paymentA document finance can approveWho issues invoices, in whose name, with what payment terms?
ConfirmationA booking summary for the managerWhat does the confirmation show: seats, names, amount, rules?
AttendanceAttendee tickets and joining instructionsDoes each attendee receive their own ticket and updates?
After the eventEvidence of attendanceWhat record, if any, can you supply to the organiser?

The questions that stall employer purchases

  • Purchase order or approval needed before payment, and how long that usually takes inside the employer.
  • Invoice details: company name, registration number, billing address and a reference line.
  • Whether the employer pays by bank transfer or card, and your reconciliation process for each.
  • Whether the organiser needs a separate delegate record for each person for badges, dietary and access needs.
  • Personal data: the booker supplies other people's details, so decide what notice and consent wording applies and ask your adviser to confirm.

Build the journey in this order

  1. Write the group rule: minimum seats, price per seat, deadline, and what the price includes. Link it to your price structure.
  2. Choose how groups register: a shared form with a seat count, a bulk upload of names, or a manual process run by the secretariat.
  3. Define the hold: whether seats can be reserved before payment and until when.
  4. Set the name-change window and refer to the substitution and cancellation rules.
  5. Test the whole journey with a dummy group of three, ending with the invoice and one substitution.

Pitfalls to avoid

  • Collecting only the booker's details, so you cannot send joining information to attendees.
  • Letting a group hold seats indefinitely and blocking individual sales.
  • No single owner for group enquiries, so the answer depends on who picks up the email.
  • Invoices issued in the wrong entity name and reissued after finance rejects them.

Questions for finance and legal

  • Who may issue invoices and receipts, and what must they show?
  • What terms apply to payment by purchase order, and when is a booking confirmed?
  • What privacy wording applies where one person registers others? Ask the data-protection adviser to confirm before launch.

Worked example · Fictional example

A fictional insurer registers a team for an industry conference

Fictional organisation and figures, illustrative only.

Syarikat Fiktif Insurans Maju wants 12 staff at a conference. The training manager asks for one invoice and needs approval from a department head, which takes about two weeks.

The secretariat allows a seven-day hold on 12 seats, takes the invoice details on a group form, and collects names within a set window. The insurer submits 10 names at first and two later. One person withdraws, and under the substitution rule a colleague takes the seat. The secretariat's journey sheet shows who handled each step.

Use this yourself

Employer group journey checklist

Copy and complete before registration opens. Assign one owner to each line.

  • Group rule written: minimum seats, price per seat, deadline, inclusions:
  • How a group enquires and who answers within the working week:
  • Seat hold: allowed? maximum days? what releases the hold:
  • Booker details needed: name, company, registration number, billing address, reference:
  • Attendee details needed: name, email, role, dietary and access needs:
  • Name change window and who can change names:
  • Invoice owner, entity name, payment terms and accepted payment methods:
  • Confirmation message content for the booker and for each attendee:
  • Privacy wording for registering other people, checked by adviser:
  • Substitution and cancellation rule linked and visible:
  • Test run completed with a dummy group (date and result):

Open the tool: Event ticket break-even calculator

Handle it in-house, or bring in help?

Your team can usually handle this when

  • Groups are rare and the secretariat can handle each one personally.
  • Your registration platform already supports group booking and invoices.
  • Finance has agreed the invoice and payment process.

Outside planning help earns its fee when

  • Employer groups are a main source of registrations and the manual process is breaking down.
  • The registration platform, invoicing and attendee communications sit in three different tools.
  • Privacy, invoicing and attendance records need agreement between several teams before launch.

Need the group registration journey designed?

An Event Blueprint can map the group journey from enquiry to invoice, names and attendance records, with owners and supplier requirements for your registration platform. A project lead can then coordinate the set-up and a test run with your registration supplier. Group sales and any revenue results stay with your organisation.

Plan your group registrationOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Event Blueprint (planning pack)

Questions organisers ask

Should we ask for all attendee names at the time of booking?

Not necessarily. Allow a stated window for names after the booking, with a final date. Employers often confirm seats before they know who will attend.

Can one person pay for a group by card?

Yes if your payment set-up allows it, but many employers prefer an invoice. Decide which methods you accept and how each is reconciled.

Who is responsible for attendee data?

Your organisation decides how it uses the data it collects. Where a booker supplies other people's details, ask your data-protection adviser which notice and wording to use.

What if the employer wants to change the group size?

Write the rule before it happens: whether seats can be added at the group price, and whether reductions are refunded under your cancellation terms.

Related resources

Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.