Nobody is 70% Automated: Node Coverage and Flow Coverage Are Different Numbers

Logistics automation coverage is normally reported as a share of sites, processes or order volume running without manual intervention, and logistics orchestration is what makes those automated steps behave as one decision rather than several. The reported number is almost always counted by node: this depot is automated, that one is not, 70% of the network is live. What a business actually experiences is flow coverage, meaning the share of end-to-end journeys that complete without a manual step anywhere along them. Those two numbers are related by an exponent, not by equality, and the gap between them is why enterprises report steady automation progress while the operation feels largely unchanged.

A network that is 70% automated node by node runs roughly 24% of its four-node flows end to end. Locus, the world’s first Decision-Intelligent, Agentic TMS, coordinates those flows across owned fleet, contracted transporters and more than 1,000 carriers in a single decision layer, which is what allows coverage to be measured and closed by path rather than by site.

Why node coverage overstates what the business feels

The relationship is simple and it is multiplicative. If a flow passes through several nodes and each must be automated for the journey to complete without intervention, the probability that a given flow is fully automated is node coverage raised to the number of nodes in the path.

Read the 70% row. A program reporting 70% automation is delivering end-to-end automation on 24% of four-node journeys and 11.8% of six-node ones. Both the program report and the operational experience are accurate. They are measuring different things, and only one of them appears in the benefits case.

Inverted, the table explains why automation targets feel perpetually out of reach.

Hitting 80% of flows requires 94.6% of nodes. That is not a rounding difference from 80%, it is a different program with a different budget, and it is the arithmetic behind the familiar pattern where the last stretch of an automation roadmap costs more than everything before it. The final increments are also the most valuable: moving node coverage from 95% to 100% adds 18.5 points of flow coverage, more than the 15.8 points gained going from 90% to 95%.

Heterogeneity is the normal enterprise condition rather than a failure. A network of any size has depots on the new platform, depots on the old one, a country running a different system after an acquisition, and at least one site where a spreadsheet still governs a step nobody has documented. Google’s engineering account of production systems names the resulting pattern directly, listing boundary erosion, entanglement and undeclared consumers among the risk factors that make deployed systems expensive to maintain, and a partially automated flow is all three at once: the automated and manual halves share state, the boundary between them is undocumented, and downstream teams consume outputs nobody knows they depend on. The American Trucking Associations reports almost 580,000 active US motor carriers as of June 2025, of which 91.5% operate 10 or fewer trucks, and that fragmentation reaches inside your flows wherever a small carrier performs a leg. Cost makes the unautomated remainder expensive rather than merely untidy, with ATRI putting the industry-average cost of operating a truck at $2.336 per mile in 2025, a record for the series and 3.4% above the prior year.

How to close coverage by flow rather than by site

1. Map flows before counting nodes

List the end-to-end journeys that actually carry your volume: order to dispatch to line haul to final mile to proof of delivery, or whatever the equivalent path is in your network. Most operations have fewer distinct flow types than they expect, often between six and fifteen, and each has a path length. Without this map, coverage can only be counted the way the org chart is arranged, which is by site.

2. Measure node coverage and flow coverage separately

Report both, labeled. Node coverage is what the program controls and what progress reviews should track. Flow coverage is what the business experiences and what the benefits case promised. Publishing only the first is how a program stays green for two years while the operations director reports no change.

3. Compute the flow number rather than assuming it

Raise node coverage to the path length for each flow type, then weight by volume. This takes minutes and usually produces the first honest picture the program has had. Where flows differ in length, the short ones will be carrying almost all of your realized benefit, which is itself a useful finding.

Path length is also longer than most maps show, because flows cross companies as well as systems. Armstrong & Associates put US 3PL gross revenues at $323.4 billion in 2025 against net revenues of $138.2 billion, which is a large share of enterprise freight moving through a third party at least once. Every such handoff is a node you do not control, and counting only your own sites produces a path length shorter than the one the shipment actually travels.

4. Identify the capping node in each flow

Every incomplete flow has at least one manual step, and that step caps the value of everything automated around it. List the capping node per flow and the list is almost always shorter than expected, because the same few nodes cap many flows. Those are the highest-value targets in the network and they are frequently unglamorous: a customs handoff, a yard process, a single depot on legacy software. Rank them by the volume of flows they cap rather than by the size of the node, because a small site sitting on a high-volume path is worth more than a large site sitting on a rarely used one. This ranking almost never matches the order a systems roadmap would produce, which is the point of doing it.

5. Switch sequencing from geography to path once the first deployment is proven

Phasing a rollout by geography or fleet segment is the right way to start, because it contains risk, surfaces configuration errors cheaply and builds the operational confidence that determines adoption. It is the wrong way to continue, because it optimizes for deployment safety rather than benefit realization.

The difference is large. Take 100 nodes arranged as 25 flows of four nodes each, and automate 50 of them. Sequenced by path, completing whole journeys, that finishes 12.5 flows and delivers 50% flow coverage. Sequenced by site in an order that does not follow flows, it delivers 0.5 to the fourth power, or 6.25%. Same investment, same node count, eight times the realized benefit. The practical rule is to use geography for phase one and path for everything after it.

6. Report flow coverage to the business and node coverage to the program

These are different audiences with different questions. A steering committee asking whether the investment is working needs flow coverage weighted by volume. A delivery team asking what to do next week needs node coverage and the capping-node list. Sending the second number to the first audience is the most common reporting error in automation programs, and it is why the disconnect usually surfaces at a benefits review rather than in a status report.

Two ways to sequence the same investment

Neither column is wrong. They answer different questions, and a program that never moves from the left column to the right one will spend its whole budget before the benefit curve turns. The switch is a decision somebody has to make, and it rarely makes itself.

Five questions to ask about an automation program’s coverage

Is the reported number nodes or flows? If nobody can answer immediately, it is nodes, because flows require a map that most programs have not built.

What is the average path length of your highest-volume flows? This single number tells you how far apart the two coverage figures are. At four nodes they differ by a factor of roughly three at 70% coverage.

Which node caps the most flows? The answer is usually a small set, often a handoff between organizations rather than a system. Those are the highest-return targets and they are rarely on the roadmap, because roadmaps are organized by system.

What is the sequencing rationale after phase one? If the answer is still geography, the program is optimizing risk long after risk stopped being the binding constraint.

How is coverage weighted? Unweighted node counts treat a depot doing 40 orders a day the same as one doing 4,000. Weight by volume and the picture usually changes, sometimes favorably.

What this looks like in enterprise deployments

A leading North American retailer running multimodal logistics automation across several hundred stores replaced six legacy systems, reduced manual dispatch by more than 80%, and now achieves 99%-plus on-time store delivery with 95%-plus route compliance and exceptions resolved in under two hours. The detail that matters here is the six systems. Heterogeneity was removed rather than coordinated around, which is the most direct way to raise node coverage across every flow simultaneously, and it is why the operational numbers moved rather than only the program numbers.

A Fortune 50 parcel operation running centralized dispatch across a 120-country network moves more than a million freight shipments a year across 51 sites with a 4,500-strong driver pool split between captive and third-party. That is the heterogeneous case in its purest form, since a 120-country network cannot be uniform and the captive and third-party halves will never reach the same automation depth. The deployment lifted weekly execution adherence from 75% to 92% and surfaced more than $14 million of unused capacity, including $565,000 at a single site. Adherence is a flow measure rather than a node measure, which is why it moved.

Four mistakes enterprises make on automation coverage

Reporting a single automation percentage. It is almost always node coverage, it is almost always read as flow coverage, and the two differ by a factor of three at typical path lengths. Labeling the number costs nothing and prevents years of misreading.

Sequencing the whole program by geography. Correct for phase one and expensive thereafter. The benefit curve stays flat until node coverage gets very high, which is exactly when budgets are under the most scrutiny.

Treating the last nodes as cleanup. The final increments deliver the largest jumps in flow coverage, because they complete paths. Deprioritizing them because they are small in node terms discards the most valuable work in the program.

Ignoring handoffs between organizations. The capping node is often not a system at all but a point where responsibility changes hands, between a warehouse and a carrier, or between two business units. Those never appear on a systems roadmap and they cap flows regardless.

How Locus closes coverage by flow

Locus, the world’s first Decision-Intelligent, Agentic TMS, is built to hold a whole journey in one decision rather than automating each node separately. Allocation runs across owned fleet, contracted transporters and a network of more than 1,000 carriers, decided per shipment against live cost and serviceability, which means a leg performed by a third party does not have to become a manual node in an otherwise automated flow. ShipFlex handles multi-carrier execution and the Control Tower consolidates the resulting movements into one operational picture, so a flow spanning several parties is still one path rather than several disconnected ones.

Because the route planning system produces dispatch-ready plans in roughly two minutes against more than 250 real-world operating constraints and re-optimizes continuously, a node that would otherwise need manual intervention when conditions change can be re-planned instead, which is how nodes stay automated rather than reverting under pressure. Explainability and Traceability record the trigger, context, reasoning, action and outcome for each decision, which is what makes the capping-node analysis possible against evidence rather than recollection.

Two boundaries belong here. Locus does not automate nodes it does not touch. A yard process, a customs broker’s workflow or a warehouse step running on another system remains a manual node in your flow regardless of what the transportation layer does, and mapping those honestly is part of the implementation rather than an afterthought. And sequencing is your decision, not the platform’s. The arithmetic above says path order beats site order for benefit, but whether your organization can absorb a path-ordered rollout depends on change capacity that only you can assess.

Locus supports more than 360 enterprise customers across 30-plus countries, with over 1.5 billion deliveries optimized, more than $320 million in documented client logistics savings and 99.99% uptime. It has been recognized by Gartner for seven consecutive years, featured in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, named a Leader in TMS by QKS Group (SPARK Matrix), and ranked #1 in Route Planning on G2’s 2026 Best Software Awards.

In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

So how automated is a network that reports 70% automation? On four-node flows, 24% of them run end to end, because flow coverage is node coverage raised to the path length and one manual step makes the whole journey manual. That exponent is why targets feel unreachable: 80% flow coverage requires 94.6% of nodes, and the final increments deliver the largest gains, with 95% to 100% adding 18.5 points of flow coverage. It is also why sequencing dominates spend. The same 50% of nodes automated delivers 50% flow coverage sequenced by path and 6.25% sequenced by site, an eight-fold difference, which argues for geography in phase one and path order after that. Locus supports the path view by holding a whole journey in one decision layer across owned, contracted and 1,000-plus carrier capacity, with ShipFlex for multi-carrier execution, a Control Tower consolidating the movements, a route planning system that re-plans in roughly two minutes so nodes stay automated under change, and decision records that let the capping node be identified from evidence. Request a Locus assessment to compute your own flow coverage against your node coverage.

Frequently Asked Questions

What is the difference between node coverage and flow coverage? Node coverage is the share of sites or process steps running without manual intervention. Flow coverage is the share of end-to-end journeys that complete without a manual step anywhere. Flow coverage equals node coverage raised to the path length, so at 70% of nodes automated only 24% of four-node flows run end to end.

Why does one manual node ruin a whole flow? Because end-to-end automation is a conjunction. The journey is only unattended if every step is unattended, so the value of a flow is capped by its least automated step rather than by the average across the network. Automating around a manual node improves the nodes, not the journey.

How much node coverage do we need for 80% of flows? On four-node flows, 94.6%. For 50% of flows you need 84.1%, and for 90% of flows, 97.4%. The targets sit much higher than the flow figures they produce, which is the arithmetic behind automation roadmaps that cost more at the end than at the beginning.

Should we phase rollout by geography or by flow? By geography for the first phase, because it contains risk and surfaces configuration errors cheaply. By flow path after that, because sequencing the same 50% of nodes by path delivers 50% flow coverage against 6.25% by site. Programs that never make the switch spend the budget before the benefit curve turns.

Why do the last nodes matter so much? Because they complete paths. Moving node coverage from 95% to 100% adds 18.5 points of flow coverage, more than the 15.8 points from 90% to 95%. Treating the final nodes as cleanup discards the highest-return work in the program.

What is a capping node? The manual step that prevents a flow completing end to end. They cluster, so a small number of nodes usually cap many flows, and they are often handoffs between organizations rather than systems, which is why they rarely appear on a systems roadmap.

What should we report to the board? Flow coverage weighted by volume, labeled as such, alongside node coverage for the delivery team. Reporting node coverage to a benefits audience is the most common error in these programs, because it stays green while the operation reports no change.