The pilot went well. Collections happened on time, the route held, recipients were happy and the cost looked right.
Now comes the part most businesses underestimate. Everything the pilot taught you sits with the few people who ran it: the courier who found the side entrance, the coordinator who knows which recipient prefers a call, the operations lead who remembers why the Thursday collection moved earlier.
If that knowledge stays where it is, the model cannot grow. A second route, a new site or a busy season will depend on the same people remembering more.
This article explains how to turn the learning from a pilot into a delivery process that others can run, and why that, rather than booking more couriers, is what makes growth possible.
Part 3 of 4 in our series on building a delivery operation: test the delivery model, design the operation, turn it into a repeatable process (this article) and automate the process.
Key Takeaways
- A pilot proves the model. A written process makes it repeatable.
- Record what the pilot taught you about the route, the recipients, the timings and the exceptions.
- A process is ready when someone new can run it to the same standard.
- Scaling means repeating a proven process, not rebuilding it with more couriers.
- Personal attention lasts when the system carries it, not only the individual.
The path from a delivery problem to a system that scales
Delivery systems that work well have usually passed through the same stages, whether or not anyone planned them.
- Problem. A delivery need that repeats, or matters too much to leave to chance.
- Pilot. A small, real test of the model. We cover how to run one in how to test a delivery model before you scale.
- Learning. What the pilot showed about timings, access, recipients and exceptions.
- Process. The agreed way the work will be done from now on.
- Written procedure. The process recorded so that it does not depend on memory.
- Repeatable delivery. The same standard, whoever is on the route.
- Managed relationship. Regular review of what is working and what needs to change.
- Scale. More routes, sites or volume, run on the same foundations.
The stage most often skipped is the written procedure. It is also the one that decides whether everything after it can grow.
What the pilot should hand over to the process
Each item below is something a pilot usually reveals, and something a new courier or coordinator would otherwise have to rediscover.
- Collection behaviour. When goods are actually ready, who releases them and what the courier should check before leaving.
- Route characteristics. The order of drops, the hours when traffic or access changes and where to stop.
- Recipient requirements. Named contacts, preferred entrances, who may sign and what they expect to see.
- Timing tolerances. Which deadlines are fixed and which have room to move.
- Vehicle fit. The size, type and preparation of vehicle the load needs.
- Known access problems. Keys, codes, loading bays, security desks and lifts.
- Communication preferences. Who wants an update, about what, and through which channel.
- Exceptions. The usual problems and the agreed response to each one.
- Contingency. Backup couriers and vehicles, and what changes when volume rises.
Written down, this becomes the operating record for the route. It should be short enough to use and specific enough that a briefed courier could run the route without phoning anyone to ask.
A process is only useful if someone else can run it
The test of a delivery process is simple. Could a different, briefed courier run the route tomorrow to the same standard? Could a different coordinator handle a problem on it without calling the person who designed it?
If the answer is no, the process still lives in someone’s head.
Three habits help:
- Give every route an owner who keeps the record current and approves changes to it.
- Treat a permanent change as a change to the service. An earlier collection every day, a new drop or a different recipient should update the record and the courier briefing, not live on as a favour that only one person knows about.
- Build simple checks into the route itself. On a morning food route, for example, that might be a count of items at collection, a confirmation at each drop and one agreed channel for problems.
Inside Selena
On recurring work, we keep each client’s instructions, access notes and contacts in a structured profile, so a repeat booking starts from what we already know and a new member of the team can pick up the account without relying on memory.
Routes are reviewed rather than rebuilt. When volumes, sites or timings change, the plan is agreed with the client and the couriers are briefed before the change takes effect.
Scaling means repeating the process, not booking more couriers
When volume grows, the instinct is to add capacity: another courier, another van, another booking. Capacity matters, but on its own it adds more people who do not know the route.
Good scaling looks different. A second route is built from the same template as the first. A new site is added by recording its access, contacts and windows before the first delivery. Extra volume is planned into the schedule rather than absorbed on the day.
Two points are easy to miss:
- Core and flexible capacity are different. A route that runs every day needs couriers whose availability is agreed in advance. Occasional capacity is valuable for peaks, but the daily route should not depend on it.
- A good result can hide a near miss. If every delivery arrived but the week depended on one courier working late or on the only spare vehicle, record it. That is the moment to plan more cover, before the next busy week tests it.
This is where scheduled and multi-drop work benefits most. A multi-drop route that is written down, owned and reviewed can take additional drops far more safely than one that exists only in the courier’s head.
Personal attention, delivered through a system
Some of the most valued courier services in London are built around one person: an owner who knows every client, or a dedicated courier who handles every movement personally. For a single important delivery, that model can be excellent.
For recurring business work, it has a limit. When that person is on holiday, unwell or simply busy, the attention goes with them.
The alternative is not less attention. It is attention that has been written into the way the work is done: the recipient’s preferences recorded, the courier briefed on them, a coordinator accountable for the route and the client told early when something changes. That is how a boutique standard can hold across many routes and many days. We set out what that standard involves in what a premium courier service actually means.
Business Insight
A delivery process is ready to scale when the people who designed it are no longer needed to run it. They are still needed to improve it.
When a process becomes a managed delivery relationship
Once a delivery process is written, owned and repeatable, it no longer needs to be booked as a series of separate jobs. It can be run as a managed arrangement, reviewed regularly and extended as the business grows. We describe how that relationship usually develops, from a first booking to a partnership, in our article on recurring courier services, and what embedded support involves in Embedded Delivery Solutions Explained. Only once the process is stable is it worth automating; we explain why in automating delivery operations.
Selena’s Embedded Delivery Solutions are built on this approach: discover how the operation runs, design the routes and responsibilities, then run and review them with you. Scheduled routes, multi-drop work and urgent same-day jobs can sit within the same relationship.
If a pilot has shown you what works, talk to us about turning it into a process that can grow.
