Employee Benefits

How to Set Up an Employee Meal Programme in 4 Weeks

A practical 7-step plan for setting up an employee meal programme in the UK — goals, budgets, tax, platform choice, policy, pilot, and launch week by week.

Bianca Duarte
11 Jun 2026
9 min read
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 a seven-step plan, with the week each step belongs to and the test that closes each week.

WeekStepsOwnerSigned off when
1Goal, eligibility, budget, tax routeHR + financePayroll agrees the tax treatment
2Platform choice, policyHR + procurementHR publishes eligibility and the policy
3SSO, HR sync, expense flow, pilotIT + platformA test order reconciles to the right cost centre
4Announcement, demo, measurementHR + commsSupport has resolved the pilot's exceptions

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

Set the budget from the menus staff will actually order from rather than a benchmark. On 18 November 2026, a chicken teriyaki rice bowl at itsu in Aldgate was £11.15, and a small create-your-own poke bowl at Poke House in Canary Wharf was £10.95 (menu prices). A £10 budget would leave staff topping up either lunch on their own card; £12 would cover both. Shortlist a few menus the team already uses and check them the same way.

Prices checked on 18 November 2026.

In parallel, put thirty minutes in the diary with payroll. A recurring meal benefit is normally taxable in the UK (GOV.UK, meals for employees), and the handling, whether P11D, payrolling the benefit 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:

ModelCost structureFits
Meal platformMeals at menu price plus delivery and service feesDaily budgets, individual choice
Traditional catererA quoted price per headSet-menu group lunches, events
Staffed canteenA kitchen, staff and a fixed annual costLarge single sites with a steady daily headcount

For a daily programme, the platform model is the most flexible, 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 on those criteria: 300+ restaurants and caterers; employees can order meals delivered in around 30 minutes through individual ordering; budget rules by team, location, day and time for any group you define; and no setup fee and no minimum spend or commitment on the account. The employee meal programme page shows how the delivery models combine.

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 can get access automatically and leavers are deactivated, via SSO or a daily SFTP feed from Workday or your HR system. None of it is required: without a feed, an admin adds people in the Admin Portal or shares a company sign-up code.
  • Expense data flowing to finance: cost centres and expense codes captured at checkout and, where you connect one, 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.

An admin dashboard showing meal budget controls and spend reporting

Step 6: Run a one-week pilot

Pick one team of 15 to 30 people, ideally a vocal one. Give them the live programme for a week and watch three numbers against targets set in advance: registration rate (an example target is 90% by day two), order success (meals arriving on time and correctly labelled), and budget fit (if people regularly pay above the budget, it is too low; if they rarely get near it, it is generous). Ask the pilot team to nominate the restaurants they want, for example atis, and check those are in the selection before launch.

Fix what the pilot surfaces. Typical 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.

Checking the pilot's first deliveries

Ordit delivers the pilot's orders with its own fleet, so it controls each one from the restaurant to the office. Group meals arrive accurate and labelled with each person's name, which the organiser can check against the sign-up list. The pilot's deliveries carry Ordit's on-time delivery guarantee from the first order. Through the app, employees can order meals delivered in around 30 minutes. See how meal budgets work or book a demo.

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 £12 daily lunch budget. Order in the app from the restaurants that deliver to the office, such as itsu, Farmer J, Poke House and The Salad Project. Every employee can order meals delivered in around 30 minutes. No receipts, no expense claims." A link to one menu, such as The Salad Project, takes each reader straight to a first order.

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

  1. Adoption. Set thresholds before launch, for example a target for week one and a higher one for week four. Low adoption after a month usually points to awareness, restaurant fit or login friction, and 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 meal programme ROI guide sets out what to measure.

Running the integrations in parallel

Enterprise integrations (SSO and an SFTP employee feed) can run in parallel from week 2 where IT capacity allows. Ordit configures them in one to two weeks including testing, and teams without integrations can self-register with work email addresses and order 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.

Ready to feed your team properly?

Join hundreds of London offices already using Ordit for individual meals, group orders, and catering.

Frequently asked questions

Recent Posts