Planning an Office Catering Budget Finance Will Approve

Most office catering budgets fail at the approval stage for the same reason: they arrive as a single number with no workings. Finance does not reject catering — finance rejects estimates it cannot interrogate.

This guide builds an office catering budget the way a finance team wants to read it: cost-per-head benchmarks for London, the hidden costs that wreck naive estimates, a calculation framework, and the controls that keep actual spend tracking the plan. Numbers throughout are London 2026 rates.

Start with cost per head, not total spend

Every defensible catering budget is built from one unit: cost per head per occasion. London benchmarks by format:

Two calibration notes. First, individually boxed meals cost slightly more per head than shared platters but waste far less — platters are routinely over-ordered by 20% "to be safe", which erases the saving. Second, dietary coverage is built into the boxed format; with platters it means ordering parallel options, which compounds the over-ordering.

The hidden costs that derail estimates

Food is usually only 80–90% of the real number. The rest hides in four places:

Delivery fees. Per-order fees range from £0 to £40+ across London providers depending on distance and order size. Ordit charges a flat £15 + VAT per group or catering delivery — flat rates make budgets predictable; percentage-based or distance-based fees do not.

Service fees and commissions. Platforms charge somewhere between 5% and 15% on spend. Ask for the number in writing and put it in the budget line. (Ordit's is 5% + VAT on monthly spend, and £0 in months with no orders.)

Admin time. The invisible line. An office manager spending three hours a week collecting orders, chasing dietary requirements, and reconciling receipts costs £3,000–£5,000 a year in salary time. Consolidating to one platform with one invoice moves this line close to zero — and it is a real saving finance will recognise, because they process the invoices.

Waste. Over-ordering on shared formats, no-shows at headcount-based events, and "just in case" buffers typically run 10–15% of food spend. Individually ordered or boxed formats cut this to low single digits because the order matches actual attendees.

The budget framework

The calculation finance wants to see:

Annual budget = Σ (occasion type × frequency × average headcount × cost per head) + delivery + service fees

A worked example for a 120-person London office:

Round to £92,000, present the table, and the conversation changes from "why so much?" to "which lines move?". That is the conversation you want — it means finance is editing the plan, not rejecting it.

Note what this budget is not: a daily individual meal benefit. That is a separate programme with its own (larger) budget and its own tax treatment — covered in the employee meal programmes guide and the meal benefits tax guide. Keeping the two budgets separate is itself a credibility signal with finance.

What finance actually checks

Having sat on both sides of these approvals, the questions are predictable. Build the answers in:

"What does this replace?" If catering replaces expensed client lunches at restaurants (£40–£80 per head) or an underused canteen contract, show the offset. Catering budgets that consolidate scattered spend often net out cheaper than the status quo — but only if the scattered spend is quantified. Pull twelve months of food-related expense claims; the total surprises most teams.

"How is spend controlled in-month?" The honest answer with ad-hoc ordering is "it is not — we find out at month end." The better answer: per-event budgets set in the platform, spend visible in real time in the Admin Portal, and expense codes captured at checkout so every order lands against the right cost centre automatically.

"What is the per-head trend?" Track cost per head per occasion type quarterly. It is the metric that catches drift — headcount creep at events, format inflation, the £14 lunch becoming £19.

"Who can spend?" Named bookers with per-person or per-event limits beats an open account. Platforms with admin controls make this a setting; email-and-invoice caterers make it a hope.

Five ways to cut the budget without anyone noticing

1. Switch shared platters to individually boxed meals for recurring occasions — the ~20% over-order buffer disappears.
2. Make headcount confirmation a 24-hour rule for events. No-shows are the purest form of waste.
3. Set per-head caps by occasion type in the platform rather than approving each order — £14 for team lunches, £25 for client sessions. Control without friction.
4. Consolidate providers. Every additional caterer is a separate invoice, a separate reconciliation, and a separate negotiation. One platform with 300+ restaurants gives the variety without the vendor sprawl.
5. Use click & collect where it fits — employees pick up from nearby restaurants and the delivery fee disappears entirely.

Making the case in one page

The approval memo that works has four parts: the framework table above; the offset analysis (what scattered spend this consolidates); the control story (real-time visibility, expense codes, one monthly invoice with 30-day terms); and the per-head benchmarks as an appendix. With transparent pricing — and providers who publish their fees, which not all do — there are no unknowns left to challenge.

For the operational side — formats, lead times, choosing between providers — see the complete guide to office catering in London and the 12-point provider checklist. For how Ordit handles catering end to end, from boxed lunches to pop-ups for 50+ people, see Office Catering.