Compound congestion is an accounting identity before it is an operational problem. If more units arrive each day than depart, the yard fills, and the only questions are how fast and what breaks first. What makes 2026 awkward is that this is happening inside a lean system rather than an oversupplied one. Industry days' supply sits around 48, well below the pre-pandemic norm nearer 65, and manufacturers have held to leaner inventory strategies throughout. The congestion is not coming from too many vehicles overall — it is coming from mix. Strong turnover in high-demand segments now sits alongside ageing inventory in weaker ones, which means a compound can be full of the wrong units while the fast-moving ones cycle through normally. Total volume looks fine. The yard does not. Book an architecture review to see your inflow, outflow and ageing profile on one view.
FVL · COMPOUND CONGESTION
Compound Congestion and Ageing Stock
Inflow against outflow measured daily, ageing separated from held, storage cost attributed properly, and the linkage back to production made visible before it becomes a phone call.
Arriving
420 / day
Departing
390 / day
Net
+30 / day
Thirty units a day is invisible on any single morning and fills a thousand-space compound in a bit over a month. Congestion is almost never a sudden event — it is a small imbalance nobody was measuring daily.
There Are Only Four Levers
Once the arithmetic is stated, the response set is short. Everything else is a variation on one of these.
01
Reduce inflow
Slow or divert arrivals. The lever with the shortest reach into logistics and the longest reach into everything else, since it eventually means talking to production.
02
Increase outflow
More capacity, faster loading, quicker release. Usually the right answer and usually constrained by carrier availability rather than by the compound's own effort.
03
Add space
Overflow storage or a temporary site. Fastest to arrange, most expensive to keep, and it converts a flow problem into a rent line that outlives the surge.
04
Use the space you have better
Reduce unproductive movement, tighten slotting, clear ageing units. The cheapest lever and the one that requires knowing what is actually in the yard.
Where the yard sits in the network
Historically yards were where problems first appeared and rarely where investment or leadership attention went — that went to long-haul transport. The relationship runs the other way: reduced dwell reduces congestion, faster turns improve loading productivity, better flow supports transport schedules, and when the yard runs with discipline the whole network becomes more predictable. The compound is not downstream of the network's performance; it is upstream of it.
A Lean System Can Still Congest
The 2026 pattern is specific, and it defeats the usual response of waiting for volume to fall.
~48
Days' supply industry-wide, edged up but still comfortably below the pre-pandemic norm of around 65 — production discipline rather than oversupply
Split
Strong turnover in high-demand segments alongside ageing inventory in weaker ones — lean overall, but increasingly fragmented
Shifting
Affordability pressure moving buyers toward lower-priced vehicles, producing uneven sales rates across segments and brands
The operational consequence is that a compound can be full while total inventory is healthy. Fast-moving variants cycle through in days; slower ones accumulate in the same footprint and occupy the positions the fast movers need. Managing to a total unit count will not detect this, because the total is fine. Managing to age by segment will.
Ageing Alerts, Done Usefully
Five design decisions. The second is the one that determines whether anyone acts on the alerts or learns to ignore them.
Band by age, not by a single threshold
A unit at thirty days and one at ninety need different responses. Bands make the distribution visible and let escalation increase with age rather than triggering once and then going quiet.
Separate ageing from held
A unit sitting because nobody has dispatched it and a unit sitting because it is blocked by a quality or campaign hold look identical on an inventory report and need opposite responses. Reporting them together makes the whole list unactionable, because half of it is somebody else's problem.
Set bands by segment, not fleet-wide
If one segment genuinely turns in a week and another in six, a single threshold flags the second constantly and never flags a genuinely stuck unit in the first. Bands calibrated per segment surface the real anomalies.
Attach an owner and an action
Dispatch it, relocate it to lower-value space, chase the hold, or escalate commercially. An ageing alert with no available action trains people to close it.
Report the trend, not just the count
The share of inventory above each band, month over month. A stable count with a worsening distribution is deteriorating, and only the trend shows it.
+30
units / day
How many days until you are full?
Most compounds cannot answer that from memory.
Daily inflow, daily outflow, remaining headroom and the resulting date. Bring a month of gate records to a 30-minute session and we'll produce the balance in Fleet Rabbit, split ageing units from held ones, and show which segments are consuming positions they do not need.
The Congestion Nobody Counts: Unproductive Movement
A congested yard generates traffic that carries nothing, and that traffic is both a cost and a further cause of congestion.
Deadhead and empty movement
Non-material movements increase transit time and site traffic without moving anything of value. At one major assembly plant these were measured at around $21,000 per day and roughly 27% of all daily miles driven on site — more than a quarter of the movement producing nothing.
Rehandling to reach buried units
Moving three vehicles to extract one. Rises sharply as occupancy climbs, which is why congestion compounds — the fuller the yard, the more movement each dispatch requires.
Searching for misplaced units
Inaccurate inventory drives wasted moves directly. A continuously accurate record enables smarter sequencing so priority units go straight out, improving turns and reducing rehandles.
Resequencing after late information
Carrier arrival changes and appointment shifts that reach the yard too late to influence the plan. Where transport signals feed yard execution, work can be resequenced and units staged appropriately; where they do not, the yard discovers the change when the truck arrives.
Prioritise moves by urgency, not by proximity
The same plant found that prioritising movements according to production urgency helped mitigate shutdowns even as volume rose. The principle transfers directly to a compound: a move queue ordered by what is blocking something else beats one ordered by what is nearest, and the difference shows up as fewer stalled dispatches rather than as faster individual moves.
What a Compound Day Actually Costs
Six cost lines. Only the first two are usually in a storage budget, and the last is the one that makes the case.
← Swipe to see all columns →
| Cost line | What drives it | Where it appears |
|---|---|---|
| Space | Rent, rates and site cost per position per day | Storage budget — the one line everyone sees |
| Handling | Moves per unit, rising with occupancy | Labour, usually unattributed to congestion |
| Damage exposure | Every additional handling event is another opportunity | Claims, months later, with no link back |
| Working capital | Vehicle value tied up for the duration of the dwell | Finance, and rarely discussed with logistics |
| Condition deterioration | Batteries, tyres and surface condition over long dwell | Preparation workload at the far end |
| Overflow and premium recovery | Temporary space, expedited movement, weekend working | Wherever the emergency was authorised from |
Building a defensible cost per position per day matters more than getting it precisely right. Once a number exists, an ageing unit stops being a space issue and becomes a quantified one — and the commercial conversation about a slow-moving segment becomes considerably easier when the holding cost per unit per month can be stated rather than described.
The Production Linkage
The consequence nobody wants to reach, and the reason congestion is a manufacturing conversation rather than a logistics one once it passes a certain point.
1Positions run outThe compound reaches practical capacity, which is always below nominal capacity because access lanes and staging have to remain usable.
2Overflow is arrangedTemporary space at cost, usually further away, adding transport legs and a second location to keep track of.
3Handling degradesRehandling rises, search times lengthen, and the compound loses the ability to dispatch quickly — which reduces outflow and worsens the original imbalance.
4The line slows or stopsWith nowhere to put completed vehicles, production has to moderate. This is an extremely expensive outcome caused by a logistics constraint, and it is the point at which everyone becomes interested in yard data that was available all along.
Dwell is a leading signal, not a report
Dwell is most often reviewed after problems occur, which wastes its most useful property. Rising average dwell, a worsening age distribution and a persistent positive net balance all appear weeks before positions run out — long enough to book additional capacity, adjust release sequencing or raise the mix question commercially. Used proactively it is a forecast; used retrospectively it is an explanation.
Running Multiple Sites Consistently
Five practices. Networks running each compound differently produce fragmented data and outcomes nobody can compare, let alone manage centrally.
Standardise the core workflowsCheck-in, move requests, dispatch rules and communication handled the same way at every site. Variability across sites is what makes network-level reporting meaningless.
Keep inventory continuously accurateInaccurate records drive wasted moves and congestion directly, while an accurate one enables sequencing that sends priority units straight out and cuts rehandles.
Feed transport signals into yard executionArrival changes, appointment shifts and detention risk arriving in time to resequence work and stage units, rather than after the decisions were made.
Measure the same things everywhereNet balance, dwell distribution, moves per unit, held share and occupancy against practical capacity — identically defined, so a comparison between sites means something.
Balance across the network deliberatelyOne compound at capacity while another has headroom is a routing decision nobody made. It only becomes visible where both sites report on the same basis.
Twenty minutes on your net balance, age distribution and held share
On an architecture review we'll take a month of gate and dispatch records into Fleet Rabbit, calculate daily inflow against outflow and the resulting headroom, split ageing units from those blocked by holds, and break the age distribution by segment. You keep the analysis either way — and for most operations it is the first time the fill date has been an actual date rather than an impression.
Frequently Asked Questions
Our total inventory is healthy. Why is the compound full?
Because congestion is driven by mix rather than by total volume. The current pattern is a system that is lean overall but increasingly fragmented — strong turnover in high-demand segments alongside ageing inventory in weaker ones. Fast-moving variants cycle through in days while slower ones accumulate in the same footprint and occupy the positions the fast movers need. A total unit count cannot detect this because the total is fine; age distribution by segment can.
What should we actually measure?
Start with daily inflow against daily outflow, because congestion is that arithmetic sustained over time. A net imbalance of thirty units a day is invisible on any given morning and fills a thousand-space compound in a bit over a month. Add occupancy against practical rather than nominal capacity, age distribution by segment, the share of inventory blocked by holds, and moves per unit — which rises as the yard fills and quietly reduces your outflow.
Why separate ageing units from held units?
Because they look identical on an inventory report and require opposite responses. A releasable unit sitting because nobody dispatched it is a logistics problem you can act on today. A unit blocked by a quality or campaign hold is a release problem belonging to someone else, and no amount of dispatch effort will move it. Reporting them together makes the whole list unactionable, since half of it cannot be resolved by the people reading it.
How much does congestion cost beyond storage?
Considerably more than the space line. Handling rises as occupancy climbs because reaching a buried unit takes more moves; each additional handling event adds damage exposure; working capital is tied up for the duration of the dwell; condition deteriorates over long dwell and lands as preparation workload later; and overflow space plus expedited recovery arrive as emergency spend. Only space and sometimes handling appear in a storage budget.
How much movement is genuinely unproductive?
More than most sites assume. One major assembly operation measured non-material movements at around $21,000 per day, accounting for roughly 27% of all daily miles driven on site. Rehandling to reach buried units and searching for misplaced ones add to that, and both rise with occupancy — which is why congestion compounds. Prioritising the move queue by what is blocking something else, rather than by what is nearest, was found to help mitigate shutdowns even as volume increased.
When does this become a production problem?
Sooner than the capacity figure suggests, because practical capacity always sits below nominal — access lanes and staging have to stay usable. The sequence runs from positions running out, to overflow at cost, to degraded handling that reduces outflow and worsens the imbalance, to production having to moderate because there is nowhere to put completed vehicles. That last step is an extremely expensive outcome caused by a logistics constraint that was visible weeks earlier.
Where should we start?
By calculating the net daily balance and the resulting fill date, then splitting the age distribution by segment and separating held units from ageing ones. Those three numbers cost nothing beyond data you already generate at the gate, and together they turn congestion from a condition into a forecast — which is the difference between booking additional capacity in advance and authorising overflow in a hurry. Book a session with a month of gate records and we'll produce them with you.
Thirty a Day Is a Month to Full
Measure the balance daily rather than the total weekly, band ageing by segment and separate it from held, price a compound day so an ageing unit has a number attached, and treat dwell as the forecast it is — because everything after positions run out is more expensive than everything before.
Figures illustrative unless sourced · Bring a month of gate and dispatch records to the call
August 31, 2026
By Alex Rowan
All Articles
