Guides
The driver handover checklist
Almost every delivery failure in a meal-plan business is an information failure rather than a driving one, and nearly all of them are created in the ten minutes before the van leaves.
Before loading
Stop count agreed
The driver and the bench agree how many stops and how many boxes. A mismatch found here costs a minute; found at a door it costs a return trip.
Flagged addresses reviewed
Any stop that failed or caused a call last time gets thirty seconds of attention now.
Access notes present
Gate codes, tower names, reception instructions — confirmed as attached to the stop rather than remembered.
Before departure
Route order understood
Not necessarily optimal — understood. A driver following their own sensible order beats one improvising against a list they disagree with.
Cold chain check
Especially through summer, where the window between chiller and customer fridge is genuinely short.
How to report a failure
Agreed before it happens, so a failed stop is recorded rather than mentioned in passing at the end of the day.
The printed sheet is the problem
Most of this checklist exists to compensate for a manifest that stopped being true when it was printed. An address corrected at ten o’clock never reaches a sheet produced at six, and no amount of briefing fixes that.
Where the driver reads the live record scoped to their own stops, several of these checks simply stop being necessary — which is the right direction for any checklist to move.
Common questions
- Should drivers plan their own route order?
- Often yes. An experienced driver on a familiar round knows the traffic and the parking, and a route they understand is followed more reliably than one they quietly disagree with.
- What is the most valuable handover check?
- Agreeing the box count before loading. A discrepancy found in the kitchen costs a minute; the same discrepancy found at a customer door costs a return trip and a conversation.
- Why do printed manifests cause problems?
- Because they stop being true the moment anything changes after printing. A driver reading the live record cannot be carrying yesterday’s address; a printed sheet always can.
See how this works in practice
The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.
Related reading
- GuidesDelivery manifests and the driver handoverThe handover from kitchen to road is where a well-run morning gets undone. Almost every failure at this boundary is an information failure rather than a driving one.
- GuidesPreventing meal delivery address errorsAddress problems look like small individual incidents and are actually one of the largest recurring costs in a delivery operation, because each one consumes two people at once.
- GuidesA daily operations checklist for a meal-plan kitchenMost operational checklists are organised by department, which is convenient and wrong. Ordering them by when a problem is still cheap to fix is what makes a checklist worth running.
- SolutionsRoute planning and driver manifests for meal deliveryA meal-plan round is not a set of ad-hoc jobs appearing through the day. It is a known list, knowable the night before — which makes it a planning problem rather than a dispatch problem.