Guides
How to run a school meal programme
A school programme is the strictest operating environment in this business. The eaters are children, the allergen consequences are severe, the calendar has holes in it, and the person paying is not the person eating.
Allergens are the whole operation
In an adult meal plan an allergen error is a serious service failure. In a school it is a medical emergency involving a child who cannot advocate for themselves, and it will end the contract.
That raises the bar on how allergen data is held. A note in a comments field is not adequate. The requirement is structured, per-child allergen data that is checked against the specific meal on the specific day, with the conflict surfaced before production rather than at the bench.
It also raises the bar on labelling. A box handed to a child needs the child’s name and the allergen information on it, legibly, because the adult supervising lunch is not the person who packed it.
What makes a school different from other contracts
The calendar has holes
Term dates, half terms, exam weeks, sports days and public holidays. A weekly recurring schedule with no concept of term will produce meals for an empty school.
The payer is not the eater
Parents subscribe, children eat, and the school administers. Three parties, and all three need a different view of the same subscription.
Headcounts are known but not stable
A class trip removes thirty covers with a week’s notice. That is a scheduled change, not an emergency, if the system can express it.
Age bands change portions
A reception portion and a year-eleven portion are different quantities, and purchasing needs to see the mix.
The school audits you
Expect to evidence what was served, to whom, with what allergen checks. Reconstructing that later is not viable.
Setting the programme up
Load the term calendar before anything else
Delivery days should be generated against the school calendar, not a generic weekly pattern. This single step removes most of the wasted production.
Collect allergens as structured data at enrolment
From the parent, per child, in fields — not as free text in a signup form. Re-confirm each term rather than assuming last year still holds.
Agree who can change what
Parents change their own child’s selections; the school changes headcounts for trips and closures. Both need to be recorded and attributed.
Label with the child’s name and allergens
Legible to a supervising adult who was not involved in packing.
Keep the record
What was produced, what was checked, what was delivered, day by day. This is the evidence base if anything is ever questioned.
Billing parents without creating an administrative burden
Parent billing is where school programmes generate disproportionate admin. Hundreds of small subscriptions, term-length cycles, mid-term joiners and leavers, and a school office that does not want to be your collections department.
The workable arrangement is that each parent holds their own subscription with its own record, so a joiner mid-term is a normal subscription starting mid-cycle rather than a manual adjustment to a school-wide invoice. Proration handles the rest.
Where the school pays centrally and recharges parents, the contract behaves like a corporate account instead, and the count accuracy discipline matters more than the individual billing does.
Common questions
- How should allergen information be held for a school programme?
- As structured, per-child data collected from the parent at enrolment and re-confirmed each term, checked against the specific meal on the specific day. A note in a comments field is not adequate in this setting.
- How do term dates affect scheduling?
- Delivery days should be generated against the school calendar rather than a generic weekly pattern. A recurring weekly schedule with no concept of term will produce meals for an empty school during half term.
- Who should be able to change what?
- Split the permissions: a parent adjusts only their own child, while the school handles closures and trip headcounts. Record and attribute both, because you will be asked to evidence what happened and when.
- Should parents be billed individually or through the school?
- Individually where possible — each parent holding their own subscription means a mid-term joiner is a normal subscription starting mid-cycle rather than a manual adjustment to a school-wide invoice.
Allergen checks that run before the pan
See a per-person allergen conflict flagged ahead of production on a demonstration kitchen’s cook list.
Related reading
- SolutionsSoftware for school meal programmesFeeding children at school shares a shape with meal-plan delivery and differs in three ways that each carry real consequences.
- SolutionsAllergen management software for meal businessesEvery other field in a meal-plan system can be wrong and cost you money. This one can be wrong and cost someone a hospital visit, which is why it deserves different treatment from the rest of the customer record.
- GuidesAllergen management in a meal-prep kitchenAllergen handling is the one part of a meal-plan operation where a data-entry problem becomes a medical one. It deserves a different standard of care from the rest of the customer record.
- SolutionsMeal label software for prep kitchensThe label is the last line of defence in a meal-prep operation and the only artefact the customer actually reads. Everything about how it is produced matters more than it appears to.
- SolutionsSoftware for senior meal programmesDelivering meals to older adults shares its production shape with any meal plan and differs sharply at the door, where the delivery is often as much a check on the person as a handover of food.