Event businesses: the gap between the booking taken and the event delivered

An event business runs two operations that look like one. The first is commercial and increasingly digital: enquiry, quote, availability, deposit, contract. The second is physical and time-bound: suppliers, logistics, run sheet, crew, delivery on a date that cannot move.

The commercial half has been modernised in most businesses. There is a website, an enquiry form, a booking system, perhaps online payments. The delivery half usually runs on spreadsheets, group chats and the memory of an experienced coordinator. The gap between them is where margin leaks, details are lost, and clients form their opinion of whether you are organised.

The booking captures the sale, not the event

A booking system is designed to secure a commitment. It records the date, the package, the headcount and the deposit. That is what it needs for the transaction to complete.

Delivering the event requires a different set of information: access times and loading restrictions at the venue, dietary requirements, the client’s actual running order as distinct from the template one, who has authority to approve changes on the day, what was promised verbally during the site visit, and which of the three quotes issued during negotiation is the one that was accepted.

Almost none of that lives in the booking system. It accumulates across email threads, a phone call, a site visit, and a series of messages, and it gets assembled into a run sheet by one person a week or two out. The quality of the event depends on how well that person assembles it, and on whether they were the same person who took the booking.

Four places the handover fails

Verbal promises with no record

Event sales happen in conversation. A client asks whether you can do something slightly outside the package, the salesperson says yes because it is a reasonable request, and the commitment is never written anywhere the delivery team will see. It surfaces on the day, when the client expects it and the crew does not know about it. The team absorbs it, which costs money nobody quoted for, or the client is disappointed at the worst possible moment.

Suppliers confirmed but not tracked

Most events depend on external suppliers: catering, audiovisual, furniture, entertainment, staffing. Confirmation typically happens by email or phone and is held by whoever made the booking. There is no single place showing which suppliers are confirmed, what each has been asked to deliver, when they arrive, and whether anyone has followed up. The check is a person going back through their sent items.

Change requests that never reach the quote

Headcount moves, timings shift, an extra room is added, the client wants a different linen. Each change is small enough that raising a variation feels petty, so the coordinator absorbs it and forgets to tell anyone in finance. Across a year, the aggregate of unbilled variation is frequently a significant portion of the margin the business thought it was making.

Run sheets that live in one head

Experienced coordinators build excellent run sheets, and they build them from scratch each time because the last one is buried in a folder structure only they understand. Nothing accumulates. A new coordinator cannot produce work of the same standard, so senior people stay on the floor and the business cannot add capacity. This is tribal knowledge operating exactly as it always does: excellent output, no leverage.

The client experiences one business. Internally you are running two, connected by a coordinator who remembers what the salesperson agreed to.

Why peak season exposes it

These gaps are survivable at four events a month. The coordinator holds the detail, the team is small enough to communicate informally, and problems get solved by people who care.

At sixteen events a month, with several on the same weekend, the model fails in a specific order. Detail slips first, because there is more of it than one person can hold. Supplier follow-up goes next, because it is the task with no deadline until it is suddenly critical. Then variations stop being billed, because chasing them competes with delivering tomorrow’s event.

Businesses in this position often conclude they need more coordinators. Adding coordinators to an undocumented model produces inconsistency instead of capacity, because each new person develops their own version of the process.

What closes the gap

One record per event, from enquiry to invoice, is the structural fix. Not necessarily a new platform: often it is the existing booking system extended, or a project record that the booking system feeds. What matters is that there is one place where the sold scope, the agreed variations, the supplier commitments and the run sheet all live, and that everyone works from it.

Then define the handover explicitly. A booking is not delivered to operations when the deposit clears. It is delivered when a defined set of information is complete, and the person taking the booking is accountable for completing it. Every service business has a version of this problem, and the internal handoff is reliably where client experience degrades.

Two further changes pay for themselves quickly. Make variation approval a two-minute step rather than an awkward conversation, so it actually happens. And run a short structured debrief after every event, captured in the same record, so that what the business learns about a venue, a supplier or a client accumulates somewhere other than in the memory of whoever happened to be there.