Overtime Meal Delivery in London: Feeding Teams That Work Past Six
How London finance and consulting firms put overtime meals on rules: rule-based budgets, late delivery, and a timestamped, coded record of every order.

Finance teams work long hours. Investment banks, consulting firms and asset managers routinely have staff at their desks past 6pm — and on quarter-end weekends. Feeding them is both a perk (people feel valued) and a necessity (nobody wants to buy their own dinner at 9pm).
But overtime meals come with a specific operational problem: they need to be tracked, budgeted, compliant, and available at short notice. Most catering models fail at least one of those tests.
Why overtime meals are harder than lunch
The hours are unpredictable. A trading floor might be quiet at 5pm or heaving at 10pm depending on the markets. A deal team might wrap at six or at midnight. Catering that needs 24 hours' notice — the traditional model — simply cannot serve a team that finds out at 7pm it is staying late.
The spend is significant. In the worked example below, a 50-person desk where half the team eats dinner twice a week runs to about £3,000 a month on dinners alone. That is a real budget line, and finance wants controls on it, not a stack of delivery-app receipts.
Compliance needs proof. An overtime meal is an expense. For audit purposes it needs a cost centre, an expense code, a person and a timestamp showing when the meal was ordered. The timestamp records when the order was placed; the employer's policy, not the platform, decides who is eligible.
The rule-based model
The approach that has replaced receipt-and-reimburse at firms like the global investment bank Ordit serves in Canary Wharf is rule-based budgeting. The office manager sets a policy once in the Admin Portal:
Before 6pm, staff have a £10 lunch budget. After 6pm, meals are covered in full.
The platform enforces the rule automatically. Staff order dinner at 8pm; eligibility is checked at checkout, not by a PA; the company covers the cost with no one out of pocket. Every meal is tagged with the expense code ("Overtime Meals"), the cost centre ("Trading Floor"), the time it was ordered (19:45) and the amount, all flowing into SAP Concur without anyone filing anything.
Rules can also be temporary (switched on for quarter-end week and off again afterwards) or differ by team: for example, no daytime budget but covered evening meals for the deal team, and a flat £10 all day for operations.

What the numbers look like
A worked example for a 50-person trading desk, with a £10 daytime budget and covered meals after 6pm:
- Lunch: 40 staff × £10 × 20 working days = £8,000 a month
- Dinner (twice a week): 25 staff × £15 × 8 evenings = £3,000 a month
- Annual total: around £132,000
The tracking side is what wins finance over: filter the Admin Portal to "Overtime Meals", see £3,000 of January evening spend, download 200 individual meals with timestamps and cost centres. No spreadsheets, no chasing, no audit anxiety.
Delivery is the hard constraint
A rule engine is worthless if dinner cannot actually arrive at 8:30pm. Two things matter:
The delivery window. Ordit's own fleet delivers until 9pm as standard, with later windows arranged for events. Check the last booking window in the app for the branch and day, because a late slot depends on both the kitchen and the delivery window. Ordit’s own riders are on shift for corporate orders only and take every order first, with vetted last-mile partners extending capacity on demand, so evening cover does not depend on who happens to be online.
Restaurant hours. Closing times vary by branch and by day, so check the branch menu in the app before you set the rule. For a City team on Liverpool Street, the Coqfighter Liverpool Street menu is one to look at; for a Canary Wharf desk, Pizza Pilgrims Canary Wharf; for dinner ordered individually, Chicken Shop lets colleagues choose a branch, and Marugame Udon is another to check locally. Dishes, evening availability and closing times need confirming for the branch and day.
Who runs the evening handover?
Ordit's own riders take each evening order from the restaurant to the building, so one operator controls the whole delivery and reception deals with one handover. Meals arrive accurate, and the team can give reception a contact name for the dinner. Every Ordit delivery carries the on-time delivery guarantee. Employees can order meals delivered in around 30 minutes, from the same app. See individual ordering or book a demo.
Setting it up
The typical rollout takes five to ten business days: define the rule with an account manager, connect SSO (Azure AD or Okta, two to three days), connect SAP Concur and test the "Overtime Meals" code, then launch. Put the rule in writing first with the employee meal allowance policy template. Staff see the rules take effect immediately, with no training needed beyond "order dinner like you'd order lunch."
Overtime meals are the use case where the difference between consumer platforms and corporate platforms is starkest. The finance-team workflows, including budgets per group and client entertainment codes, are covered on the financial services page and in the guide to employee meal benefits for London banks and fintechs.
Ready to feed your team properly?
Join hundreds of London offices already using Ordit for individual meals, group orders, and catering.



