Companion tickets, and why they are priced wrong almost everywhere

Conferences routinely let a delegate bring a spouse, a colleague or a guest to the social programme. It is a small feature that goes wrong in a specific and expensive way.

The failure

The accompanying person gets modelled as an option on the delegate's booking — a checkbox, or a quantity. And then one of two things happens.

They are not charged at all. The delegate ticks "bringing a guest", pays the delegate rate, and two people arrive. If the accompanying rate was meant to be Rs 3,000, and forty delegates bring someone, that is Rs 120,000 that was never invoiced. Nobody notices until the caterer's numbers do not match the ticket numbers.

Or they are charged, but invisibly. The booking total is right, but nothing records what the extra amount was for. Refund half the booking later and nobody can tell which half.

Both come from the same root: the companion was treated as an attribute of a booking rather than as a person.

They are a person, and here is the proof

An accompanying person:

• occupies a seat at the gala dinner, and eats a meal that was catered for;
• needs their own badge, with their own name on it, because they will be in the room without the delegate;
• must be checked in separately — on a three-day event the delegate may come all three days and their guest only to the dinner;
• and may have their own dietary requirement, which is on their own form, not the delegate's.

Every one of those needs a record with a name on it. A quantity cannot do any of them.

What "charged correctly" means

The delegate makes one booking and makes one payment — that part should not change, because splitting the payment is worse for everybody.

But the amount must be the delegate rate plus the accompanying rate, and the booking has to record both components. When you look at that booking six months later you should be able to see: one delegate at Rs 8,000, one accompanying person at Rs 3,000, paid together, Rs 11,000.

If your system stores only the total, you have lost the information the moment the payment succeeded.

The badge test

Here is the quickest way to tell whether your setup handles this properly.

Print the badges. If the accompanying person's badge has the delegate's name on it, then they are not a person in your system — they are a number. Two people will arrive at the door holding the same name, and one of them will be turned away.

What to decide before you open registration

The rate. Accompanying persons usually pay for the social programme and not the academic one. Make that explicit on the registration page, because the commonest complaint is a guest who assumed they could sit in on sessions.

What it includes. Dinner only? Dinner and the welcome reception? Day trips? Write it down. This is the single biggest source of day-two arguments at the registration desk.

Whether they get a certificate. Usually not — they did not attend the academic programme. Decide it now rather than when one is requested.

Whether the count is capped. One guest per delegate is normal. Say so, or somebody will register four.

Why it is worth fixing

Because the failure is silent. An event that undercharges for accompanying persons does not produce an error; it produces a catering bill that is larger than the ticket revenue suggests it should be, and a finance conversation nobody can resolve from the records.