.svg)
.svg)
.svg)
.svg)
.svg)
A carrier contract can specify an excellent vehicle standard, dimensions, payload, equipment, fuel type, and still lose its value over time if nothing after onboarding checks whether that standard holds. Specification is the easy part. Enforcement is what makes it durable.
Getting the standard right at signing is necessary. On its own, it isn't enough.
What a workable fleet standard specifies
Four categories worth writing into any carrier contract
Dimensions and payload capacity. Fuel type and range, especially as electric vehicles enter a mixed fleet. Operational features like loading height, tail lift, and access points. And geographic requirements, urban zone clearance, weight restrictions, certifications, tied to where the vehicle needs to operate. Specific enough that a planner, or a route optimizer, can tell immediately whether a given vehicle matches what was contracted.
One route, planned three different ways depending on what shows up
Picture a single route built against a regional fleet standard.
- The plan assumes the standard, the route is built assuming a large truck cleared for urban access, since that's what the contract specifies for carriers in this region.
- The vehicle that arrives, a smaller van shows up instead, without the urban clearance, since nothing in the process checked whether this carrier's actual fleet still matched what was signed.
- The fix, done by hand, the planner reworks the route on the spot, sequencing around a vehicle the plan was never built for. It looks like a routing problem. The cause was a contract term nobody verified that morning.
Nothing about the route optimizer was at fault here. It planned correctly against the standard it was given. The standard was the part that had quietly stopped being true.
The same gap shows up in capacity, not just access
A contract might specify a vehicle capable of carrying up to 1,000 kilograms. A vehicle that carries 500 can fill the same contract line without anyone noticing, and the difference isn't marginal, it roughly doubles the number of stops or reloads needed to move the same volume. Neither gap shows up as a contract issue. Both show up as a route that looks harder to plan than it should be.
Sourcing and planning are both accountable for this, in different ways
Sourcing typically owns the standard at the point of signing, dimensions, equipment, and access requirements written into the contract. Planning typically holds the day-to-day evidence of whether that standard is holding, mismatches between what a route assumes and what shows up. The strongest setups connect the two, planners flagging drift as it happens, and that drift feeding back into contract review and renewal, rather than sourcing and planning working from two separate pictures of the same fleet.
One furniture retailer traced its overrides back to one cause
One furniture retailer coordinating last-mile delivery through external service providers found a recurring pattern of planner overrides that looked, at first, like a routing problem. The actual cause was wide variation in vehicle types and sizes across providers serving the same region, even though every contract nominally specified a standard. Enforcing that standard on an ongoing basis, not just at the point of sourcing, was what brought the overrides down.
This applies wherever deliveries run through more than one external carrier
Grocery networks running mixed vans across regions, direct-store delivery operations depending on specialized equipment, and big and bulky networks needing two-person or tail-lift capable vehicles all depend on the same discipline, a standard specific enough to check, and checked often enough to matter.
The takeaway
Write the fleet standard specifically enough that a mismatch would be obvious the moment it happened, then build in a cadence for checking it. A standard verified once, at signing, is a snapshot. A standard checked on a schedule is one an operation can plan against.
