How to Set Up an Employee Meal Programme in 4 Weeks

Most guides on how to set up an employee meal programme stop at "pick a budget and a provider." Then the programme launches, a third of staff never register, finance discovers the invoicing does not match their cost centres, and HR fields a complaint that the vegan options run out by noon.

The fix is sequencing. A meal programme touches HR, finance, IT, and facilities, and each has one decision to make before launch. Handled in the right order, the whole thing takes four weeks. This is the seven-step plan London firms actually follow — with the week each step belongs to.

Week 1 — decide what the programme is for

Step 1: Define the goal and the audience

"Free lunch" is not a goal. Pick the primary job the programme does, because it drives every later decision:

• Retention and morale → a daily budget, available every working day.
• Return-to-office incentive → budget active on in-office days only (the design covered in the hybrid playbook).
• Cafeteria replacement → scheduled group lunches plus individual ordering, sized for the whole building.
• Overtime support → extended-hours budgets for teams working past six.

Then decide eligibility. All staff is simplest and reads as fairest; by-team or by-grade rollouts work, but write the rationale down before someone asks.

Step 2: Set the budget and the tax route

London benchmarks are consistent: £8–£12 a day covers a solid high-street lunch (itsu, Farmer J, Pret A Manger); £12–£15 reaches the premium tier (Sticks'n'Sushi, Emilia's Crafted Pasta, Ottolenghi). Most firms start at £10 — staff pay anything above that on their own card, so the budget is a floor, not a ceiling.

In parallel, put thirty minutes in the diary with payroll. A recurring meal benefit is normally taxable in the UK, and the handling — P11D, payrolling, or a settlement agreement — must be agreed before launch, not discovered at year end. The full rules are in the UK employee meal benefits tax guide.

Week 1 output: a one-page brief — goal, eligibility, daily budget, tax route, sponsor.

Week 2 — choose the platform and write the policy

Step 3: Choose the delivery model

Three options, honestly compared:

For a daily programme, the platform model wins on flexibility — and the evaluation criteria are concrete: restaurant range (are the places your team already queues for on it?), delivery reliability, budget controls granular enough for your policy, and expense integration. A full 12-point provider checklist covers the catering side.

For reference, Ordit's numbers on those criteria: 300+ restaurants rated FSA 4 or 5, an own fleet delivering in 30 minutes, budget rules by team, location, day and time for any group you define, and no setup fees, lock-in, or minimums.

Step 4: Write the policy

One page, in the staff handbook, written so it survives first contact with real questions:

• Who is eligible, and from when
• The daily budget, and which days and hours it applies
• Above-budget spend: goes on employees' own cards
• Unused budget: resets daily (the default), or rolls over
• Where delivery applies — office only, or click & collect anywhere
• Who to contact when something goes wrong

A section-by-section template is in the meal allowance policy guide.

Week 2 output: signed platform choice, one-page policy.

Week 3 — integrate and pilot

Step 5: Set up access and integrations

This is the IT week, and it is shorter than expected:

• SSO so staff log in with their existing work credentials — no password resets, no orphaned accounts. Ordit supports SAML 2.0 (Okta, Azure AD) with setup in 1–2 weeks including testing.
• Employee sync so joiners get access automatically and leavers are deactivated — via SSO or a daily SFTP feed from Workday or your HR system. No manual user lists to maintain.
• Expense data flowing to finance: cost centres and expense codes captured at checkout and exported to SAP Concur, Coupa, or your P2P system. Finance signs off the invoice format here — weekly, monthly, or custom.

Firms that skip this step run the programme on spreadsheets for a year. It is the difference between a benefit and an admin burden.

Step 6: Run a one-week pilot

Pick one team of 15–30 — ideally a vocal one. Give them the live programme for a week and watch three numbers: registration rate (target: 90%+ by day two), order success (meals arriving on time, correctly labelled), and budget fit (are people regularly paying above budget? The budget is too low. Never reaching £7? It is generous).

Fix what the pilot surfaces. Common findings: a favourite restaurant missing from the selection, a delivery drop-off point that needs signage, a budget window that ends before the late lunch crowd eats.

Week 3 output: integrations live, pilot findings actioned.

Week 4 — launch properly

Step 7: Announce, demo, and measure

The announcement carries more weight than the platform choice. The framing that works is generosity and specificity: "From Monday, everyone gets a £10 daily lunch budget. Order from the restaurants that deliver to the office — Nando's, itsu, Farmer J, The Salad Project — in the app, delivered to the office in 30 minutes. No receipts, no expense claims."

Pair the email with a ten-minute demo at an all-hands and posters by the lifts. Then measure weekly:

1. Adoption — expect ~40% in week one, 60–70% by week four. Below 50% after a month means an awareness, restaurant-fit, or login-friction problem; all three show up in the data.
2. Average spend vs budget — calibrates the budget level.
3. Feedback — a two-question pulse survey at week four beats a suggestion box.

Review at the 90-day mark with finance: actual spend against the worked estimate, adoption by team, and whether the goal from Step 1 is moving.

The four-week timeline at a glance

Enterprise integrations (SSO, SFTP) run in parallel from week 2 where IT capacity allows — Ordit's standard setup is 1–2 weeks including testing, and self-serve teams without integrations can be ordering the same day.

For the full background — programme types, costs, and the platform-versus-caterer decision in depth — see the complete guide to employee meal programmes. The mechanics of daily budgets, above-budget spend, and controls are on meal budgets, and the HR team's view of eligibility and benefit design is on HR & people teams.