School meals shouldn't need three systems

Meal ordering for parents and the office

Parents may place orders in one system, pupil details may sit in another, and the kitchen may wait on a report from somewhere else. Each part can work and still create a daily round of checks.

Connect meal ordering to the pupil record. Parents, office staff, and catering then work from the same information, with fewer manual checks and fewer missed updates.

The process is not the hard part. The information is just in too many places.

Dietary requirements that stay with the child

Allergies and dietary requirements are some of the most important records a school holds. When they are stored in more than one place, staff update them twice and still worry a copy is stale.

Keep dietary requirements on the child profile so the latest detail is there when a meal is ordered or served. That cuts repeat entry and supports safer meal service.

Kitchen numbers without a manual report

Catering teams need meal counts and the dietary requirements that go with them. Pulling that from several systems is a cost every service.

One view of numbers and requirements saves that assembly step and gives the kitchen a clearer plan for the day. Catering teams can work from the same record as the office.

Free school meal eligibility in the same record

Free school meal eligibility creates extra admin when a change has to be copied into every system that serves a meal. A missed update means an eligible pupil is treated as if they should pay, or the other way round.

FSM eligibility can sync from the school MIS. Universal infant free school meals can follow the year group. Staff are not retyping the same status into a second meals system.

The same friction shows up in a single school and across a trust. The aim is less duplicate entry, a clearer picture, and staff time spent on pupils rather than cross-checking.