How school meal providers plan delivery rounds before lunch
Plan school meal delivery routes each morning: schools put in order from the central kitchen, shared between vans, and checked for road closures before loading.
Part of the guide Workflow automation
School meal delivery routes are planned backwards from lunch: every school must receive its hot meals inside a narrow window, so the caterer puts the day's schools in the shortest sensible order from the central kitchen, shares them between the vans available, and checks the roads on each round for closures before the first container is loaded. Done each morning, it turns a whiteboard and a phone call to each driver into one email per van with its stops in order and the minutes between them.
This article is for school catering companies, central kitchens run by councils and school groups, and the charities that deliver breakfast and lunch programmes. It covers what makes these rounds different from ordinary delivery, a made-up example, how to build the planning as an AI employee, and the errors that make meals arrive cold.
Why school rounds are their own problem
A parcel round has hours to work with; a school round has minutes. Food leaves the kitchen hot and must arrive before the first lunch sitting, often between 11:15 and 12:00, and each school's sitting time differs. That gives three rules ordinary route planning does not always follow:
- The last stop sets the departure. If the round takes 70 minutes, the van must leave 70 minutes before the latest school's window opens, plus loading.
- Rounds stay short. Better four vans with six schools each than two vans with twelve, because meals held too long in a van lose quality.
- The list changes daily. A school trip, a closure for an inspection day or a strike means the stops for Tuesday are not Monday's.
A made-up example from Manchester
Picture an invented caterer with one central kitchen in Manchester serving 22 primary schools with four vans. The schools and each day's meal numbers sit in a shared sheet the office updates by 08:00. At 08:30 the planning flow runs.
In this made-up case, Thursday's sheet shows 21 schools, as one is closed for a staff training day. The route planner shares them between four vans: two rounds of five schools and two of six, each starting and ending at the kitchen. Each driver's email lists the schools in order with the distance and minutes from the stop before and the total minutes of travel to each school. The road check finds roadworks within 500 m of one school on van 3's round, so the email to that driver says so and the office calls the school to warn that the van may use the back entrance.
Building the morning plan
In xMap Flows the plan is an AI employee built from these blocks, in this order:
- Schedule: every school day at 08:30, with holidays skipped and term dates entered as dates to skip.
- My data: the table of schools, each with its address placed on the map and today's meal count, refreshed by the office each morning.
- Filter: keep only schools with meals today, so a closed school drops out on its own.
- Route planner: start at the central kitchen, share between your vans (2 to 10), by car, coming back to the kitchen, with at most a set number of stops in a route.
- Traffic incidents: around each incoming place, within 500 m, so each stop carries the number of incidents near it and the closest one.
- Email: one email per van to its driver, or one sheet per round in Google Sheets for the office.
Each stop arrives with its van, its place in the round, the leg's distance and minutes, the minutes from the kitchen and a directions link for its part of the round; a long round has several links. If the routing service cannot answer, the planner falls back to an estimate on straight lines and the email says so, which is the signal to check that round by hand. The templates new outlets, graded and routed to each rep and routes for the weekly surplus food pickup use the same planner, and road closures near my schools before the buses leave is a ready closure check around schools.
Mistakes to avoid
- Planning on yesterday's list. Have the office update the meal counts before the run, and let the Filter drop schools with none, so changes made at 07:55 count.
- Balancing stops but not meals. Share between vans gives each a compact area, but a van can only carry so many containers. Check the meal totals per round, and move a large school to its own van if needed.
- Ignoring sitting times. The planner orders by travel, not by lunch time. If two schools nearby sit 45 minutes apart, split them across rounds or start that van later.
- No check for closures. One closed road near a school gate costs more time than a slightly longer round. The closure check is cheap insurance.
Schools and caterers will find more flows on the education and training and food delivery pages, and the guide to an AI employee for field operations covers rounds and visits more broadly. To plan your own rounds, book a call.
Questions
Can each van get its own email?
Yes. The route planner names each round, and the email can be sent once per round to the driver whose name is on it.
What if a school changes its lunch time?
Update the time in your sheet. The planner orders stops by travel, so use the sitting times when you decide each van's departure or which round a school belongs to.
Does it work for breakfast clubs and after-school snacks?
Yes. Make a copy of the flow with its own schedule and list of sites for each service.
Can drivers follow the route on their phones?
Each stop comes with a directions link for its part of the round, which opens on a phone. Long rounds have more than one link.