A route can look completely documented until the regular driver is away. Then the office discovers that the gate code, the preferred unloading point, the Thursday cash arrangement, the order the shops are usually visited in and the lines a customer always takes were never really in the system. They were in one person’s memory.
That is key person risk in distribution. The operation works while the person is available, so the missing records stay invisible. Holidays, sickness, retirement or a route change reveal them all at once. The objective is not to write down every anecdote a driver has ever learned. It is to identify the knowledge another competent driver would need to run the same round without a stream of phone calls.
The regular driver is absent. What breaks first?
The categories matter because each belongs in a different kind of record. Access instructions belong with the delivery point. Timing belongs in delivery windows, schedules and route patterns. Commercial arrangements belong in pricing, standing orders, customer defaults or credit terms. Service knowledge belongs in delivery messages or visit instructions. Exceptions need reasons and history so the next person can see what happened instead of hearing a story about it.
| Head-knowledge | What the cover driver needs | Shared-record test |
|---|---|---|
| Access | Gate code, entrance, parking, key holder, where goods are accepted. | Can the driver see it before arriving? |
| Timing | Receiving window, closed day, market-day change, recurring sequence constraint. | Does the schedule/plan reflect it? |
| Commercial | Usual lines, agreed price rule, standing order, payment arrangement. | Will the same commercial rule apply with a different driver? |
| Service | Where to leave goods, proof expected, returns or collection routine. | Is the instruction attached to the customer/visit rather than a message thread? |
| Exceptions | What changed recently and what should happen next time. | Can the office see the reason and history? |
In one driver’s head
- Gate and parking habits
- Which contact receives goods
- Timing quirks and exceptions
- Commercial context
In the shared record
- Delivery-point access and messages
- Customer and visit history
- Order/customer defaults where appropriate
- Named owner for new information
Separate customer facts from route habits
That request produces a long document nobody maintains. Capture the round through real work instead. Take the stops one by one and ask what another driver would need to know before, during and after the visit.
Start with the highest-friction stops: locked yards, restricted receiving times, unusual payment arrangements, multi-site accounts, customers with special ranges, or stops that regularly generate office calls. Move the operational facts into the record that should own them. If a detail only lives in a Word file named after the driver, the business has documented the person rather than documented the operation.
Some knowledge belongs to the customer regardless of which route serves them. A gate code, delivery message, access instruction or normal product range should not disappear because the account moves to another round. Other knowledge genuinely belongs to the route or schedule: the sequence used on a particular day, which stops are grouped together, or how a recurring site-visit pattern is generated.
This distinction matters when the business grows. A customer may move to another driver, one round may split into two, or a branch may start servicing part of the area. If customer facts are buried in a route note, the change creates new head-knowledge immediately. Put stable customer facts on the customer or delivery point; put route-specific patterns on the route and schedule.
Commercial memory deserves its own treatment
Access mistakes cause delay. Commercial memory can create invoice disputes. A driver may remember that one customer has an old agreed price, another only buys a restricted range, and a third expects the same recurring order unless they say otherwise. Those arrangements need a system owner and a maintained rule.
If the issue is not missing route knowledge but a customer whose order pattern is quietly changing, treat that as a separate declining-account signal rather than asking the driver to diagnose it from memory.
Audit the round for informal pricing first. Compare a sample of recent invoices with the price rules the office believes are current. Then look at recurring orders and usual product ranges. The aim is that changing the driver does not change the customer’s commercial experience.
If the regular driver has discretion to negotiate a price within your process, record the resulting commercial transaction normally. Do not turn the audit into a ban on judgement. The problem is an agreement that only one person knows exists.
Use cover work as the audit
A holiday cover week is useful because it tests the records under normal pressure. Before the regular driver leaves, brief the cover driver from the system rather than from a handwritten route sheet. During the week, log avoidable questions by stop. Afterwards, decide where each answer should live permanently.
The goal is not zero questions. Customers can always surprise you. The useful distinction is between a question caused by a new event and a question caused by information the business already knew but had never shared.
Key person risk returns if the capture exercise is treated as a one-off project. Routes change. Customers move doors, alter opening times, appoint new key holders and change how they want goods received. The operating habit should be: when a driver discovers something that will matter next time, put it in the appropriate shared record.
Give every type of route knowledge an owner
The regular driver can discover information, but should not become the permanent owner of every record. Assign ownership by subject. Operations can own access notes, delivery windows and route patterns. Sales or commercial teams can own price agreements and customer range decisions. Finance can own payment and credit policy. Warehouse or quality teams can own handling instructions that affect stock condition or compliance.
That distinction matters when the driver reports a change. The driver should be able to capture or pass on the fact, but the responsible office team should decide whether it changes a permanent rule. Otherwise the business simply moves key-person risk from one driver to whichever administrator happened to receive the message.
Capturing route knowledge does not mean putting every fact into one giant note. That creates a different version of the same problem: the information is technically stored, but the next driver still has to search through a paragraph to find the one thing that matters at the stop.
Put information in the record that owns it. Access instructions and site-specific handling belong with the delivery point. A recurring route pattern belongs with the route or schedule. Customer pricing belongs in maintained pricing rules, not in a driver message. A usual product range belongs in the customer setup or ordering workflow. Delivery messages should be reserved for the practical information somebody needs while servicing that location.
This also makes maintenance easier. When a gate code changes, one delivery-point record can be updated. When a customer moves to a different route, the site information travels with the customer rather than staying behind in a route sheet. The goal is not maximum documentation; it is minimum ambiguity for the next person doing the work.
Shared records replace phone-a-friend
RouteMagic gives the operation several places to hold the kinds of knowledge that accumulate on a round. Delivery points can carry their own settings and delivery windows. The Driver App shows delivery messages at the site visit, including practical instructions such as access or parking notes. Route Schedules define van-sales and site-visit patterns at route level.
On the commercial side, Customer Default Products hold the lines a customer usually takes, while price lists can be assigned to customers or customer groups. Standing Sale Orders can generate recurring orders on a schedule. The Driver App also exposes customer sales and invoice history and future orders, so the next driver is not starting with a blank screen.
Those mechanisms do not remove the need to maintain the records. They provide a shared home for knowledge that would otherwise stay attached to one person. The practical demo test is the cover-driver test: open a difficult stop and see whether the information needed to service it is visible without asking the usual driver.
Conclusion
The risk in a long-serving driver is not their experience; it is experience that never became organisational knowledge. Audit the round in five categories: access, timing, commercial rules, service instructions and recurring exceptions. Put stable customer facts on the customer or delivery point, route patterns on the route and schedule, and commercial arrangements in the pricing or recurring-order rules that actually govern the transaction. Then use cover work to test whether the record is good enough. Every avoidable phone call points to something the business already knew but had failed to share. Keep the capture habit alive after the project: when a customer changes how the stop works, update the shared record then, not the evening before the regular driver goes on holiday. That is how route knowledge remains useful without remaining personal.
