Costing an Event: Conferences, Banqueting & the Function Sheet
Conferences and functions look like the most profitable business a Kenyan hotel takes, right up until somebody costs one properly. Where the margin actually goes, why the function sheet is a costing document, and the three numbers to capture before the guests arrive.
A conference package quoted at 3,500 per delegate for eighty delegates is 280,000 shillings of revenue landing on one day, which feels like an excellent piece of business. Then the kitchen caters for a hundred because the client said numbers might grow, six extra staff are called in, the hall is set twice because the layout changed on the morning, and nobody records any of it against the event.
The event is booked as a success. Whether it made money is genuinely unknown, and it will be unknown again next month, because the costs went into the general kitchen figure and the general wage bill.
An event is a project, not a sale
This is the shift that makes function business manageable. A room night is a sale — one price, predictable cost, repeated a thousand times. An event is a small project with its own budget, its own consumption, its own labour and its own variations, and it should be costed like one.
| Cost element | Where it usually disappears to | What capturing it reveals |
|---|---|---|
| Food and beverage consumed | The month's general kitchen cost | Whether the package price covers the covers |
| Casual and overtime labour | The general wage bill | The real cost of a Saturday function versus a weekday one |
| Equipment hire — PA, staging, extra linen | Sundry expenses | Whether hire should have been a purchase by now |
| Consumables — stationery, water, decor | Stores issues with no destination | Which package inclusions nobody uses |
| Room setup and turnaround time | Nowhere at all | Why a second event the same day is harder than it looks |
The last row is the one that surprises operators. A hall that must be stripped and reset between a morning conference and an evening function has a cost even when nothing is bought — it consumes labour hours that were needed elsewhere, and it is the usual reason a "good" double-booking day ends badly.
A room night is a sale. An event is a small project with a budget, a consumption profile, a labour bill and variations — and hotels that cost it as a sale never find out where the margin went.
The three numbers, captured before the day
Everything about event costing gets easier if three figures are written down before the event happens, because afterwards they become matters of recollection and negotiation.
-
The guaranteed number
The minimum the client pays for regardless of who turns up. Without it, the client's estimate is your risk — you cater for the estimate and bill for the attendance. This single clause moves more margin than any purchasing decision.
-
The costed inclusions
What the package contains, priced from your recipes and your stock costs rather than assumed. A package assembled from a competitor's price list rather than from your own costs is a guess with a decimal point.
-
The cut-off for changes
The point after which additions are chargeable extras rather than adjustments. Everything that happens after this line is a variation, and variations are where function business either makes or loses its money.
Variations, again
The pattern is identical to construction and consulting: work done at the client's request, agreed verbally on the day, never priced, never billed. In events it happens under time pressure with a client standing in the room. The defence is the same — a named person who agrees changes, and a written note at the time. Not an argument later.
Costing the package from your own recipes
A conference package is a recipe made of recipes. If your kitchen already costs dishes properly, the event package is arithmetic; if it does not, the package price is a market-derived number with no relationship to what you spend.
Eighty delegates, one package, honestly costed
Illustrative, in KES. Note where the money went: catering for a hundred against a guarantee of eighty cost 23,000 by itself. That is not a purchasing failure or a kitchen failure — it is a booking-terms failure, and it is invisible unless the event carries its own costs.
Costing from recipes rather than from instinct is the foundation, and it is the same discipline whether the output is a menu item or a package — see F&B cost control. The bar behaves differently again and needs its own tighter treatment: bar stock control.
Which events to take
Once a few events have been costed individually, patterns appear that no aggregate figure would ever show — and they usually contradict what the sales team believes.
What is assumed
- Large events are the profitable ones
- Residential conferences are the prize booking
- Weekend functions are worth the disruption
- A discount is worth it to fill an empty hall
- Repeat corporate clients are the best business
What costing frequently shows
- Large events attract the deepest discounts and the most variations
- Residential is excellent — if rooms would otherwise be empty, and poor if they displace paying guests
- Weekend labour cost can consume the entire premium
- A discounted event still consumes full labour and setup
- Repeat clients negotiate hardest and expect the most unbilled extras
None of these are universal truths — the point is that they are answerable questions in a hotel that costs events individually and pure opinion in one that does not. Three months of properly costed functions will settle arguments that have been running for years.
What we do and do not do
What AWRA OpsHub does today
- A project per event, carrying its own budget and its own costs.
- Stock issues charged to the job, so food, beverage and consumables consumed by an event sit against that event.
- Time and labour recorded against the job, which is what makes weekend and overtime cost visible per function.
- Purchases and expenses coded to the event, including equipment hire and outsourced services.
- Committed versus actual cost, so an outstanding hire invoice is visible before it arrives.
- Quotations and invoices to the client, with the event's costs and revenue in the same place.
What it does not do
- No banqueting or function diary. Room availability, floor plans, setup layouts and the event calendar are not part of this — that is a PMS or banqueting system.
- No package builder. Assembling and pricing a delegate package is done in your quotation, not in a product configurator.
- No guaranteed-number logic. The guarantee is a commercial term you enforce when invoicing, not a rule the system applies.
- No per-cover food costing engine. Recipe costing informs your package price; the system holds item costs, not a recipe module.
Read the first line before you evaluate. If you need a function diary and floor plans, that is a banqueting system and you will keep it. What this adds is the costing layer underneath it, which is usually the part that is missing.
Our take
Open a job for every event over a threshold you set, charge food, labour, hire and consumables to it, and always write down the guaranteed number and the change cut-off before the day. Cost six events properly and you will discover which of your function business is worth chasing — and it will not be the mix your sales team currently prioritises.
See job costing for events
A job per event carrying stock issues, labour, purchases and expenses, with committed versus actual cost against the revenue you invoiced.
Explore job costingFrequently asked questions
Is it worth opening a job for every function?
For anything above a threshold you set — many hotels use a value or a headcount, such as every event over fifty covers or over a certain contract value. Below that the recording effort outweighs the insight. Above it, the discipline pays for itself quickly, because the events that lose money are almost never the ones people suspect.
Do you provide a banqueting diary and floor plans?
No. Room availability, the function diary, setup layouts and the event calendar belong to a property management or banqueting system, and if you have one you will keep it. What is missing in most hotels is not the diary — it is the costing underneath it, so that a booked event is also a job carrying its food, labour, hire and consumables against the revenue it earned.
How do we handle a client who says numbers might grow?
With a guaranteed number agreed in writing before the day: the minimum they pay for regardless of attendance, with additional covers charged as they occur. Without it, you cater for the client's optimistic estimate and invoice for the actual attendance, which means their uncertainty is entirely at your cost. This one clause typically moves more margin than any purchasing improvement available to you.
How should casual labour be costed to an event?
By recording the hours against the job, which is what makes the real difference between a weekday and a weekend function visible. Most hotels absorb casual and overtime labour into the general wage bill, where it is impossible to attribute — and since labour is frequently the second-largest cost on a function after food, that absorption hides most of the variation between one event and another.
What is the most common costing surprise?
Catering above the guaranteed number, followed closely by unbilled variations agreed verbally on the day. Both happen under time pressure with a client present, and both are booking-terms problems rather than operational ones. The fix is not tighter kitchen control — it is a guaranteed number, a change cut-off, and one named person authorised to agree extras and write them down at the time.
