A transport company runs on a combination of physical assets, permits and planning software that are often barely separable from one another. A vehicle fleet doesn't stand on its own: it is linked to route planning, to drivers with specific licenses and exemptions, to maintenance contracts and to customer agreements about delivery times. Where in many sectors people and systems form the core of an integration, here a third layer is added: the equipment and the permits attached to it. The ratio between these three — people, systems, equipment — largely determines where the integration becomes difficult. An acquisition where most of the value lies in the permits and routes requires a different approach than an acquisition where the value lies mainly in customer relationships or the planning knowledge of staff.
Route planning, track-and-trace and warehouse management are systems used operationally on a daily basis, often with no margin for downtime. Merging two planning systems doesn't just mean migrating data, it also means aligning two ways of planning — with their own assumptions about driving times, loading windows and driver availability. A synergy baseline that determines in advance which systems will continue to exist, which will be phased out and which dependencies are involved, prevents this choice from being made under time pressure in the first weeks after closing.
Transport permits, tachograph rules, ADR certification and cabotage rules are rarely transferable one-to-one between the merging entities. What on paper is a merger of two companies can operationally mean a period in which two permit structures have to continue to exist side by side because merging is not legally or practically possible in the short term. This is one of the cases where the question of whether something should be integrated at all weighs more heavily than the question of how. A Day 1 plan that identifies these permit issues as a dependency, rather than as an administrative footnote, prevents the transport process itself from grinding to a halt on the first day.
Merging two vehicle fleets into a single management structure seems like an obvious synergy, but maintenance contracts, lease terms and the age composition of the equipment determine whether that actually delivers a benefit. Merging an older fleet with remaining contractual obligations with a newer fleet can raise the average cost per kilometer instead of lowering it. This is a place where the decision-list tool adds value: not all equipment needs to fall under one management structure, and not every maintenance contract needs to be renegotiated on day one.
Drivers and planners often have years of route knowledge and customer relationships that are not recorded in any system. An integration that looks only at the hard assets — trucks, permits, contracts — and underestimates the soft knowledge of planners, risks losing that knowledge exactly at the moment when two planning teams are merged. A Day 100 plan that explicitly identifies which knowledge needs to be retained, and who holds it, prevents that knowledge from walking out the door before the new structure is in place.
Transport companies often work with contracts that guarantee hard delivery times and availability. During an integration, when planning systems, routes or vehicle fleets are temporarily organized differently, meeting those commitments comes under pressure. The risk lies not in the merger itself, but in the transition period in which two operational models must keep functioning at the same time. Benefit tracking that monitors this as a point of attention, rather than only discovering afterward that customers have dropped off, provides grip on what would otherwise remain invisible until it's too late.
The tension between operational continuity and integration pressure is not unique to transport. Those wishing to draw a comparison with other sectors can look at the bottlenecks around physical locations and inventory in retail, at the role of permits and compliance in the agricultural sector, or at how system dependencies delay an integration in the IT sector. The underlying question — which part of the value lies in people, which part in systems, which part in physical or legal assets — recurs in every sector, only in a different ratio.
For every part of a transport integration, the question arises whether merging actually adds value. Merging two planning systems can cost more than it delivers if the customer bases have little overlap. Bringing two vehicle fleets under one management structure can raise maintenance costs instead of lowering them. This is not an exception to the rule, it is the rule: integrating is a choice per component, not an automatism that follows from the deal.
Much of the work that stalls in a transport integration — comparing planning systems, taking stock of permits, merging maintenance data — consists of tasks that can be broken down into steps that are partly manual and partly automated. The work scan from FTE TO AI calculates, per task, what portion of that work can be taken over by AI, making it clear where people remain needed for judgment and where taking over repeatable work frees up time for the integration itself.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.