Make lists and quantities
Generated for the day, organised so the kitchen can start without preparation work.
Product — KitchenOps
Operational software for school meal providers.
Designed around one workflow: kitchen production, through packing, dispatch and delivery. One shared picture of the day for the kitchen, the packing team, the office and the drivers.
| Run | Driver | Stops | Load | Status |
|---|---|---|---|---|
| Run 1 | Driver A | 3 | 6 | Loaded |
| Run 2 | Driver B | 2 | 4 | Loaded |
| Run 3 | Driver C | 4 | 7 | Packing |
| Run 4 | — | 2 | 3 | Unassigned |
Handover
Box count confirmedYes
Signature capturedYes
Run 4 sign-offPending
Exceptions
Load discrepancy1
Missing label1
Late departure0
Illustrative interface preview — generic sample data, not customer screens.
The workflow
From production to delivery.
The operational day does not end when the cooking does. KitchenOps follows the work through every handover, so a change in the kitchen does not become a surprise in dispatch.
01
Production
Make lists, quantities and production requirements.
02
Packing
Boxes and quantities per school and group, with labels to match.
03
Dispatch
Runs, load counts and handover sign-off, before departure.
04
Delivery
Route and stops per driver, with confirmation at each drop.
Kitchen and production.
The day's meal data becomes production-ready output: what to make, how much, and how it is organised for the kitchen. Dietary requirements are surfaced alongside the main list, and the whole kitchen sees the same position on a screen built to be read from a distance.
Queued 3
Mains 2
Start—
Sides 2
Start—
Specials 2
Start—
In progress 3
Mains 1
Running78%
Sides 1
Running22%
Mains 4
Running9%
Checking 1
Specials 1
Holdreview
Complete 3
Mains 3
Done—
Sides 3
Done—
Specials 3
Done—
Day progress
62%
Illustrative interface preview — generic sample data.
One shared board
Queued, running, checking and complete — visible to everyone in the room at once.
Schools as operations
Groups, delivery requirements and status that production and dispatch both agree on.
Packing.
Meals are organised into clearly structured boxes for each school and group, so quantities can be checked before they move into dispatch.
Image placeholder
Packing area — meal trays and boxes being prepared. drop-in: /assets/img/photos/photo-packing.jpg · 16:9 · 2400×1350 or larger
Boxes and labels
Box and quantity structure stated explicitly, so packing can be verified.
Dispatch.
Dispatch turns packed boxes into confirmed loads. Runs, quantities and handovers are checked before the vehicle leaves, giving the team a clear record of what went out and where it is going.
Image placeholder
Dispatch and loading — meal boxes and crates going into the vehicle. drop-in: /assets/img/photos/photo-dispatch.jpg · 16:9 · 2400×1350 or larger
| Run | Driver | Vehicle | Stops | Load | Status |
|---|---|---|---|---|---|
| Run 1 | Driver A | Van 1 | 3 | 6 | Loaded |
| Run 2 | Driver B | Van 2 | 2 | 4 | Loaded |
| Run 3 | Driver C | Van 3 | 4 | 7 | Packing |
| Run 4 | — | — | 2 | 3 | Unassigned |
Handover
Box count confirmedYes
Run 4 sign-offPending
Exceptions
Load discrepancy1
Missing label1
Illustrative interface preview — generic sample data.
Runs and loads
Who is taking what, and whether the load has been signed off.
Surfaced, not inferred
A discrepancy, a missing label or an unassigned run appears as it happens.
Drivers and delivery.
Each driver gets the route they are running and the stops in sequence, and confirms each drop as it happens. Delivery status therefore reaches the operation during the service window, rather than being reconstructed at the end of the shift.
Route progress
2 / 4
✓
Stop 1 — Delivered
Done
✓
Stop 2 — Delivered
Done
3
Stop 3 — Next stop
In transit
4
Stop 4 — Pending
Pending
Back to base
Empty box returnTracked
Driver notesNone
DiscrepancyNone
Illustrative interface preview — generic sample data.
Route and stops
The sequence for the run, on the device the driver already carries.
Confirmation at the drop
Each delivery confirmed as it happens, not reconciled afterwards.
The day, recorded
Activity, exceptions and outcomes in one place for the people running the service.
Scope
What KitchenOps is — and what it is not.
It is
- Operational software for school meal production, packing, dispatch and delivery.
- A complement to the systems already in place.
- Focused on practical reliability in a live kitchen environment.
It is not
- A replacement for your meal ordering or registration system.
- A payment platform or a parent-facing ordering system.
- A full allergen management system, a scheduling tool or a full ERP.
Pilot readiness. KitchenOps is a working product being prepared for live pilot deployment with school meal providers. We are not presenting it as a general-availability platform, and we are not publishing customer names or usage figures. There is no public pricing and no self-service sign-up.
See whether it fits your operation.
Tell us how your school meal service runs today and we will walk you through KitchenOps against that workflow.