How to organise transport orders in a small company

In brief

A small company can work well with only a few tools, provided the order flow is clear. The problem is not caused by using Excel or WhatsApp: it starts when nobody knows with certainty which version of the order is the latest, who has to carry it out, which documents are linked to it, or whether the customer has changed something.

An essential process can be described in seven steps: receipt → verification → recording → planning → execution → closure → archive. If every order goes through these steps, the company reduces the need to reconstruct the shipment's history each time.

The order life cycle

1. Receipt

The order may arrive by email, telephone, customer portal or message. Whatever the channel, the information must flow into a single record. The incoming channel should not become the management system.

2. Verification

Before operationally accepting the transport, it is necessary to check whether there is enough information: location, dates, goods, quantity/weight, any constraints, price or the relevant agreement. Specific requirements must be checked for special categories of goods.

3. Recording

The order receives an identifier and becomes visible in the system used by the company. This is when the data stops belonging only to the individual who received the call.

4. Planning

A vehicle and driver compatible with the service are assigned. Availability, vehicle characteristics, driver qualifications and driving/rest constraints all come into play here.

5. Execution

During the day, at least the events that change the situation should be recorded: departure, collection, significant delay, delivery, exception or inability to proceed.

6. Closure

Delivery should not automatically mean “order finished”. Before closing it, it is useful to check documents, any anomalies, POD and notes to pass on to administration.

7. Archive

The contract/agreement, the order and linked documents must be retrievable without searching personal inboxes or employees' phones.

What to check before planning

For each order, it is worth answering five questions:

1. Who is assigning us the transport?
2. What do we have to transport and with which characteristics?
3. Where and when do we have to collect/deliver?
4. Under which commercial and contractual agreement?
5. Are there special requirements for the vehicle, driver or documentation?

A missing answer does not always mean that transport is impossible. It means there is a point to clarify before the problem reaches the yard or the consignee.

Contract and traceability

Italian Legislative Decree 286/2005 governs road freight transport contracts and encourages the use of written form. For an SME, the operational effect is simple: important conditions should not live only in the owner's memory.

If there is a framework agreement, the order should refer to it. If the relationship begins order by order, it is useful to document the commercial and operational conditions consistently. Good management does not replace legal validation of the contract, but it makes it much easier to show which information was available at the start of the service.

Managing loading and unloading: an increasingly important issue

Since 2025, Italian rules on waiting times for loading and unloading have changed. The new Article 6-bis of Legislative Decree 286/2005 provides for a 90-minute allowance for each operation and regulates compensation where it is exceeded. The legislation also considers the information that parties in the chain must provide about the place, time and access arrangements.

For those managing orders, this means the scheduled arrival time is not a cosmetic detail. Correctly recording the appointment, actual arrival, start/end of the operation and any waiting time can have operational and economic consequences. In certain cases, the rule also allows records from satellite systems or the second-generation smart tachograph to be used to prove the arrival time.

The practical value is huge: a well-managed order does not merely say “collection in Milan”, but records when the vehicle was due to arrive, when it arrived and how long it remained stationary.

Order statuses: few but clear

A small fleet does not need thirty statuses. An essential set can be:

• to be planned;
• planned;
• in progress;
• collected;
• delivered;
• with an anomaly;
• closed.

The status must describe reality, not wishful thinking. If the driver has not yet collected the goods, the order should not be marked as out for delivery simply because that was in the plan.

Practical example

A company with six vehicles receives 25 orders per week. Five come from a customer portal, ten by email and the rest by telephone. The owner notes them in Excel and then communicates with drivers through separate messages.

The improvement does not require an enterprise project. It is enough to turn every request into an order record with reference, collection, delivery, goods, times, driver/vehicle, notes and status. The message to the driver becomes a consequence of the order, not a second version of it.

Checklist

• Is there a unique identifier for every order?
• Is the receiving channel distinguished from the official operational source?
• Are the vehicle, driver and main constraints checked before assignment?
• Can the planned and actual arrival times at loading/unloading be reconstructed?
• Do customer changes update the central record?
• Does closure include a document check?
• Can administration find the order without asking the dispatcher “where is the email?”