How to communicate deliveries and collections to drivers

In brief

A delivery should be understandable to a driver without having to reconstruct five voice messages. The best approach is a standard task sheet: short but complete, containing what is needed to perform the job and updated when the plan changes.

The phone remains important for emergencies and unforeseen situations, but it should not be the only place where the destination, load reference or customer instructions exist.

The minimum mission sheet

For an ordinary collection or delivery, the following can be useful:

• order/trip number;
• type of activity: collection or delivery;
• full address;
• date and time window;
• customer or warehouse reference;
• operational contact, where needed;
• short description of the goods;
• packages/pallets/weight where relevant;
• access notes;
• documents to collect, hand over or have signed;
• any instructions on reservations or anomalies;
• the status to report when the activity is completed.

For special transport, the sheet must be supplemented with the instructions and documents required by the applicable rules.

What the driver should see — and what they should not

A well-designed system shows the driver the information needed for the mission, without automatically passing on everything that belongs to the commercial or administrative side.

For example, the driver may need the address, reference number and goods, but not necessarily the customer's commercial margin or confidential internal notes. This is useful both for simplicity and for data protection.

How to handle changes

When a destination changes, the new instruction should:

1. identify the order concerned;
2. clearly state the new information;
3. replace the previous version;
4. reach the driver in a way that can be consulted safely;
5. also be recorded by the operations office.

The phrase “as I told you on the phone” is not a procedure. If the driver has to remember which of three calls contains the final version, the company is shifting an organisational problem onto them.

Instructions and responsibilities

Italian Legislative Decree 286/2005 governs the relationships and responsibilities of the parties in the road-haulage chain. Operational instructions must not lead the carrier or driver to breach rules on safety, road traffic, or driving and rest periods.

For this reason, a customer request such as “it has to arrive by 17:00 anyway” cannot automatically become an instruction for the driver to continue beyond the applicable limits. The office must filter commercial requests and make them workable.

When to use phone, chat and app

Phone: ideal for emergencies or immediate clarification. An important change must then be recorded.

Chat: useful for quick communications and confirmations, but it should not be the only archive for several orders at once.

Driver app: useful when it presents assigned activities, details and updates to the driver in an orderly view. The app should also be designed with safety in mind: the driver must not be encouraged to interact with the screen while driving.

Paper documents: remain relevant when required or when they are part of the customer's process; where possible, however, they should be linked to the order's digital reference.

Practical example

The driver receives three activities: collection A, delivery A, collection B. In the afternoon, delivery A is moved to another warehouse. The system updates the address on the same activity and flags the change. The driver sees one current order, not two different screenshots sent in chat.

The office, instead, retains the history: previous destination, new destination, time of the change and source of the request.

Driver sheet checklist

• Clear order number?
• Complete, geographically checked address?
• Time window?
• Warehouse reference?
• Relevant goods and quantities?
• Documents to handle?
• Special instructions?
• Change updated in one place only?
• No unnecessary commercial information?
• Can the driver consult it without having to read a long chat?