Trip plan: what it is and how to organise it

In brief

A trip plan is the view a company uses to decide who does what, with which vehicle and in what sequence. It does not have to be a complex diagram. For a fleet of 5–10 trucks, a very clear grid can be enough, provided it shows orders, drivers, trucks, times, status and issues.

The plan does have an important limit: it cannot be built on geography alone. A trip that looks convenient can become impossible because the driver must take a break, the vehicle is unsuitable, the previous load is running late or a delivery time window is not compatible.

What a trip plan should show

For each assignment, it is useful to display at least:

• order/reference;
• collection and delivery;
• time window;
• driver;
• truck or vehicle combination;
• sequence of activities;
• status;
• any critical notes;
• known conflicts or unavailability.

Commercial information can sit elsewhere. The plan must remain readable in a few seconds: whoever opens the screen at 07:30 should immediately understand what is happening.

Commercial, operational and legal planning: three levels not to confuse

A frequent mistake is to turn the commercial objective (“this delivery absolutely has to arrive today”) into an operational plan without checking whether it can actually be carried out.

Commercial level: what has been promised to the customer.

Operational level: how the company intends to carry it out with the resources available.

Regulatory level: constraints that cannot be exceeded simply because the customer has an urgent need.

The rules on driving and rest periods in Regulation 561/2006 are the clearest example. The customer may ask for an earlier delivery; the dispatcher may look for a different solution; but the plan must not assume that the driver will systematically exceed the limits.

Tachograph and driving data

Regulation (EU) 165/2014 governs tachographs in road transport. A tachograph is not simply an “hours counter”: it records data relevant to checking times and, in more recent smart versions, further information required by legislation.

For company planning, this means the trip plan should be consistent with actual driving and activity data. A sheet that starts again from zero every morning is not enough if the driver comes from previous days that affect the weekly or fortnightly limit.

From 1 July 2026, the scope of Regulation 561/2006 and of the tachograph obligation was extended, for specific international/cabotage operations, to vehicles over 2.5 t as well. Mixed fleets must therefore pay close attention to which vehicles and services fall within the rules.

How to build the plan

Step 1 — set the constraints

Enter fixed appointments, certain unavailability, maintenance, restrictions and trips already under way.

Step 2 — create the sequences

Group activities that make sense together. The criterion should not be distance alone: assess timings, service time and the risk of delay.

Step 3 — assign driver and vehicle

The assignment must be compatible both technically and with the driver’s availability. Additional requirements may be necessary for goods or special transport.

Step 4 — add buffers

A plan without room to spare works only if nobody encounters traffic, no warehouse runs late and no customer changes their mind. That is not a plan: it is a hope.

Step 5 — check the “reasonable worst case”

Ask yourself: if the first unloading is 45 minutes late, what happens to the activities that follow? If the answer is that the whole day collapses, the sequence is too fragile.

How to keep it live

The plan needs an operational owner. When something changes, the new version must be visible to everyone who needs it. The real step up from a static sheet is not the colour of its cells, but the ability to keep the dispatcher and drivers aligned.

It is useful to distinguish between planned and actual. If a delivery was planned for 14:00 but took place at 16:10, both pieces of information can be useful: one says what was intended, the other what really happened.

Example and checklist

A fleet of eight trucks has twelve activities during the day. The plan is built by assigning appointment-based deliveries first, then flexible collections. One vehicle has maintenance scheduled at 17:00 and one driver must begin their rest with enough time to spare.

The best plan does not maximise the number of assigned rows: it makes conflicts visible before they become urgent phone calls.

Checklist:

• fixed constraints highlighted;
• vehicle and driver availability up to date;
• driving/rest situation checked through appropriate processes;
• realistic buffers;
• one current version only;
• record of what actually happened.