A trailer pool is the quietest capital decision in road freight. Nobody signs it off as an investment, it accumulates one drop trailer at a time, and two years later a site is carrying forty units it does not track, cannot value and will not admit to owning. Every operation running drop-and-hook eventually needs the same thing: a count, a cost per unit, and a live picture of where each trailer sits, which is what a yard management system is for.
This guide covers what a trailer pool actually is, how to size one with arithmetic instead of instinct, when drop-and-hook beats live loading and when it quietly stops paying, and the utilisation numbers that tell you which of the two you are in.
What a trailer pool is, and who owns the steel
A trailer pool is a set of trailers stationed at or dedicated to a site so that loading and transport are decoupled: the trailer is loaded on the warehouse’s schedule, and a tractor collects it later on the carrier’s schedule. The pool is the buffer that makes that decoupling possible.
Ownership is the first thing to write down, because it decides who carries the cost and who carries the risk:
- Carrier-owned. The carrier stations trailers at the shipper’s site. Cheapest to start, and the arrangement most likely to be withdrawn at renewal when the carrier recalculates what those units are earning.
- Shipper-owned. The shipper buys or leases and any carrier can hook. Maximum flexibility, full capital and maintenance exposure, and the only model where a shipper can genuinely multi-source a lane without disturbing the pool.
- Leased to the shipper, maintained by the lessor. The middle path most European DCs land on: predictable monthly cost, maintenance outsourced, no residual-value risk.
- Shared pool. Several carriers hook a common fleet under a pool agreement. Highest utilisation on paper, and it fails without an authoritative record of who took which unit and when.
Whichever model applies, the pool needs one owner of record per unit and one system holding that record. Pools kept in a spreadsheet drift by roughly one trailer a quarter, and the drift is always in the direction of units nobody can locate.
Sizing the pool: the arithmetic
Most pools are sized by memory of the worst week anyone remembers. The arithmetic is straightforward and gives a smaller, defensible number.
You need four inputs, all measurable from your own gate data:
- Loads per day at the site, in the direction the pool serves.
- Trailer cycle time in hours: gate-in, positioned, loaded, ready, hooked, gate-out, and back. Measure the whole loop, not the loading portion.
- Buffer factor for peaks, breakdowns and units in maintenance. Between 1.15 and 1.35 for most European DCs.
- Detention exposure: how long trailers actually sit ready but unhooked.
The base calculation is loads per day multiplied by cycle time in hours, divided by 24, then multiplied by the buffer factor. A site running 30 loads a day on an 18-hour cycle with a 1.25 buffer needs about 28 trailers. If the operation is holding 45, the extra 17 are not a safety margin, they are unexamined cost, and they are usually the direct product of a cycle time nobody has measured since the pool was set up.
Re-run this quarterly. Cycle time moves with dock throughput, and the pool is the last thing anyone resizes downward.
Drop-and-hook versus live load: where the economics actually sit
Drop-and-hook is not automatically cheaper. It moves cost from the carrier’s clock to the shipper’s balance sheet, and whether that trade is good depends on numbers specific to the lane.
Drop-and-hook wins when driver waiting time is long or unpredictable, when loading cannot be synchronised with arrival, when the lane runs at volumes that keep trailers cycling, and when the site has yard space that is not otherwise earning. It is also the model that removes most detention exposure, which is worth quantifying before anything else, using the method in the guide to detention and demurrage.
Live loading wins when volumes are low or irregular, when yard space is scarce or expensive, when the goods are high-value or temperature-controlled and should not sit, and when the lane is served by multiple spot carriers who will never invest in a pool.
The point where drop-and-hook stops paying is usually reached quietly: volume on the lane falls, nobody resizes the pool, and utilisation drops below the level at which the trailers earn their standing cost. That is why the utilisation number below matters more than the pool size itself.
The utilisation numbers that matter
Three measurements tell you whether a pool is an asset or a car park.
Trailer utilisation is the share of hours a trailer spends loaded, in transit or actively being loaded, against total hours available. Healthy European DC pools run 55% to 70%. Below 40%, the pool is oversized or the cycle is broken.
Ready-but-unhooked time is how long loaded trailers sit waiting for a tractor. This is the number that exposes a mismatch between warehouse output and transport plan, and it is invisible in any system that only records gate events. It sits inside overall yard dwell time, and it is usually the largest single component of it.
Spot occupancy is the share of yard spots holding a pool trailer at peak. Above 85%, the yard has no room to absorb a bad afternoon, and gate queues start appearing for reasons that have nothing to do with the dock.
All three need the trailer identified automatically at the gate rather than written down. Which identification technology fits which yard is a separate decision, covered in the comparison of RFID and ANPR gate identification.
Where trailer pools go wrong
Four failures account for most of the value lost:
- No unit-level record. The pool is managed as a count rather than a list. Nobody can answer which trailer has been on site longest, so the oldest unit is hooked last, forever.
- Pool sized to peak, never resized. Peak was two Christmases ago. The buffer is now permanent.
- Maintenance invisible. Units out of service still count toward the pool, so the effective pool is smaller than the plan assumes and everyone concludes they need more trailers.
- Shared pools without an authoritative log. Two carriers, one pool, no record of who took what. The dispute arrives at invoice time, months after the evidence expired.
Every one of these is a data problem before it is an operations problem. A pool with a live unit-level record and a measured cycle time will be sized correctly almost by accident. A pool without one will not be fixed by buying more trailers, and the dock calendar will not fix it either, because by the time a site is running a pool the binding constraint has already moved from the door to the yard, as the rules governing dock scheduling stop being the thing that limits throughput.
Where to start
Count the pool. Measure the real cycle time from gate data over a full quarter. Run the sizing arithmetic. Compare the answer to what is standing in the yard. In most operations the gap is between four and fifteen trailers, and it has been there long enough that nobody questions it.
