How to digitalise a small road-haulage company without changing everything

In brief

Digitalising a small road-haulage company should not start with a huge project. It should start with one question:

Which important piece of information is currently written down two or three times and might end up being different?

For many small businesses, the answer is the transport order and everything around it: planning, assignment, changes, communication with the driver and documents.

The safest strategy is to digitalise in layers, while keeping operations running:

orders → plan → resources → communication → documents → data → integrations

There is no need to eliminate the phone, email, Excel and paper in a single day. Each tool needs a clear role, while duplication is gradually removed.

Digitalising does not mean changing everything at once

A project that tries to introduce all of the following at the same time:

• new management software;
• new ERP;
• new driver app;
• invoicing;
• telematics;
• CRM;
• automations;
• AI;
• customer portal;
• document retention,

can fail even when every individual product is sound.

An organisation’s capacity to absorb change is limited. In a small company, the same people must keep delivering goods while learning the new process.

A useful rule is: one new official source at a time.

Phase 0: capture how the company really works

Before buying software, follow an order from beginning to end.

Write down:

1. where it arrives;
2. who reads it;
3. where it is copied;
4. who decides the truck/driver;
5. how it is communicated to the driver;
6. what happens when it changes;
7. which documents come back;
8. who closes the work administratively;
9. where it is looked for after a month.

Mark every duplication.

Example:

customer email → printout → Excel → driver WhatsApp → paper note → PDF folder

Digitalisation should reduce those steps, not simply add a seventh platform.

Phase 1: create one source for orders

The first objective can be as simple as:

“From 1 October, every new order must have a record in the system.”

It does not matter if the order still arrives by email. What matters is that, after receipt, there is one operational source.

Define a few required fields:

• customer;
• reference;
• date;
• collection;
• delivery;
• time windows;
• goods information needed for planning;
• operational notes;
• status.

If essential data is missing, the order should appear incomplete rather than being “completed from memory”.

Phase 2: make the plan shared

Once orders are structured, the plan must follow from them.

Objective:

• see what still needs planning;
• assign resources;
• order activities;
• identify obvious conflicts;
• keep the current version visible.

A digital plan does not replace checks of regulatory constraints. Driving and rest times, working time, suitability and other requirements must remain in the process through the systems, data and checks required by the applicable rules.

Phase 3: link drivers and vehicles

Creating essential master data means names and number plates no longer need to be free text.

For every piece of data, ask:

• is it needed for planning?
• is it needed for a concrete obligation?
• who needs to see it?
• how long must it be retained?

Do not upload every document to management software “because there is space”. Driving licences, personal documents, certifications and sensitive or special-category data need appropriate purposes, access controls and retention.

Phase 4: structure communication and statuses

The next step is not to eliminate WhatsApp. It is to avoid WhatsApp being the only evidence of the latest decision.

Define a process:

1. the customer communicates a change;
2. the office checks it;
3. the order is updated;
4. the plan changes;
5. the driver receives the updated version;
6. any conversation remains support, not the primary source.

For statuses, start with a few clear values.

Example:

to be planned → assigned → in progress → completed

Add “issue” and “cancelled” only if they are genuinely needed.

Phase 5: organise documents without confusing an archive with retention

Management software can help link the following to an order:

• received DDTs;
• CMRs;
• PODs;
• operational photographs;
• other relevant attachments.

But two concepts need to be distinguished.

Operational archive

It helps find the file connected to an order, trip or customer quickly.

Digital retention where required

For some kinds of documents, the law may require specific retention requirements. The AgID Guidelines govern the creation, management and retention of digital documents within the framework provided by Italian law; AgID also explains that private entities, when the law prescribes retention obligations, must define processes and responsibilities consistent with those obligations.

Therefore:

“The file is in the cloud” does not automatically mean “the document is retained in compliance with the rules”.

For tax, employment, technical or other documents subject to specific obligations, check with the relevant professional which process is required.

Phase 6: secure data and access

Digitalisation concentrates data that was previously scattered. That is an advantage, but it makes security more important.

Individual accounts

Avoid “office@company / one password for everyone”. Each person should have their own identity when the system allows it.

Permissions

A driver does not necessarily need to see all customer data. An operator does not necessarily need to administer users and settings.

MFA

Enable multi-factor authentication when available, especially for administrative accounts.

Backups

Understand what is saved, how often, and how restoration works.

Staff departures

Revoke access and devices promptly when a person leaves the company or changes role.

Phishing

A secure platform does not protect a password given to a fake page. Basic training remains necessary.

Phase 7: integrate only what is needed

Once the internal process works, data transfers between systems can be automated.

Possible priorities:

Order import

If a customer always sends the same file, importing it can remove manual entry.

ERP/invoicing

If data from a closed order must feed administration, an integration or structured export can make sense.

Telematics

If the fleet uses telematics systems, some data can be connected to the operational flow when there is a clear purpose.

Customers and partners

APIs/EDI can become useful when volumes and frequency justify the cost.

Automating an unstable process produces mistakes faster. Standardise first, then integrate.

eFTI and the future of transport data

Regulation (EU) 2020/1056 created the European framework for electronic freight transport information (electronic Freight Transport Information — eFTI).

According to the roadmap published by the European Commission, from 9 July 2027 the framework will be fully applicable: Member State authorities will have to accept regulatory information made electronically available by operators through certified eFTI platforms, within the scope set by the regulation.

For a small company, this does not mean that every process must be replaced today. It is, however, a clear strategic signal: European transport is moving towards structured, interoperable and verifiable digital data.

When choosing software in 2026, sensible questions include:

• can my data be exported?
• are APIs available?
• does the provider follow European standards?
• how will eFTI be addressed?
• if the provider speaks of a certified eFTI platform, can it demonstrate the actual certification status when the regime requires it?

There is no need to buy speculative features today; it is useful to avoid completely closed systems.

A 30-60-90-day plan for a small fleet

Days 1-30 — put the data in order

Objectives:

• map the current process;
• choose the single source for orders;
• clean up customers and locations;
• clean up drivers and vehicles;
• define 4-6 statuses;
• define users and permissions;
• import only what is needed.

Expected outcome: new orders are structured and searchable.

Days 31-60 — use the system for the day

Objectives:

• plan all new orders in the system;
• assign drivers/vehicles;
• standardise changes;
• introduce the planned driver communication;
• define a procedure for system unavailability.

Expected outcome: the shared plan becomes the current operational source.

Days 61-90 — documents and light automation

Objectives:

• link the attachments that are genuinely useful;
• define what must be archived and what requires specific retention processes;
• set 3-5 KPIs;
• assess imports from recurring customers;
• remove sheets and steps that have become duplicates;
• retrain system users on the issues that emerged.

Expected outcome: less duplicate work, more reliable data and a base ready for possible integrations.

Mistakes to avoid

1. Digitalising chaos

If every operator calls the same status by a different name, agree the process first.

2. Migrating everything

Ten years of duplicated data do not become useful simply because they are imported.

3. Keeping two official sources for months

“For safety, we update both Excel and the management software” inevitably creates differences. The parallel period must be limited and have an end date.

4. Customising before understanding the product

Many initial requests come from habits formed with the old method.

5. Confusing tracking with planning

Knowing where the truck is does not mean having a well-managed order; having a well-managed order does not mean doing tracking.

6. Confusing a cloud archive with compliant retention

An attachment that is easy to find is not automatically retained according to the applicable requirements.

7. Giving everyone access to everything

Operational simplicity does not require the absence of permissions.

8. Automating before standardising

An API can duplicate a wrong order automatically, very efficiently.

9. Measuring 40 KPIs

Three indicators that are used are better than forty ignored dashboards.

10. Not planning an exit from the provider

The ability to export your own data should be checked before signing, not when you decide to change software.

Final digitalisation checklist

Process

• Have we described how an order moves from arrival to closure?
• Is there one official source?
• Are statuses few and clear?
• Are changes recorded in the official source?

Data

• Are customers and locations clean?
• Are drivers and vehicles reusable entities?
• Do we avoid unnecessary personal data?
• Can the data be exported?

People

• Has the person who plans taken part in the project?
• Do drivers know the new flow?
• Are individual accounts in place?
• Are roles and responsibilities clear?

Security

• MFA where available?
• Are backups included and verifiable?
• Is there a procedure for revoking access?
• Is there a minimum plan for system unavailability?

Documents

• Are attachments linked to the order?
• Do we know which are only an operational archive?
• Have we identified any specific retention obligations?

Evolution

• Does integrating a system really eliminate manual entry?
• Are APIs documented?
• Does the provider follow eFTI developments?
• Can we change software without losing data?