Trailer Pool and Yard Management Telematics: Trailer Tracking, Yard Check Automation, Detention on Drop Trailers, and Pool Right Sizing

Why Trailer Pools Drift Out of Control

A drop and hook network is built on a simple promise: the tractor arrives, drops a loaded or empty trailer, hooks a different one, and leaves without waiting for a dock. The customer gets flexible loading windows and the carrier gets tractor utilization. The cost of that promise is trailers. To keep tractors moving, the carrier must stage trailers at the customer, at its own yards, and in transit between them, and every one of those trailers is capital sitting still most of the time. The moment the carrier stops knowing exactly where each trailer is and what state it is in, the pool grows to cover the uncertainty. Dispatch adds a trailer to a customer location because the last one could not be found. A customer holds a trailer for weeks because nobody noticed. A trailer sits in a far yard with a blown tire and an inspection sticker that expired two months ago.

Tractors rarely suffer this fate because a driver is attached to each one and the ELD reports every few minutes. Trailers have no driver and, in many fleets, no telematics. The yard check, where a person walks the lot with a clipboard or a tablet and writes down trailer numbers, is the traditional control, and it is slow, error prone, and impossible at a customer site three states away. Trailer telematics changes this by making the trailer report its own position and state, and the TMS changes it again by holding a single trailer table that every department reads from and that the telematics feed reconciles against. The rest of this monograph is about building that combination so that it does the work a yard checker used to do, and several things a yard checker never could.

Trailer GPS, Cargo Sensors, and What Each One Tells You

A trailer GPS unit, usually solar or battery powered with a small onboard battery for when the trailer is unhooked, reports position on a schedule and more frequently when moving or when it detects a tether to a tractor. Position alone answers where the trailer is. The next most valuable sensor is a cargo sensor, typically an ultrasonic or camera based device mounted inside the nose of the trailer that reports loaded or empty and sometimes an estimate of load fill. Loaded or empty is the difference between an asset waiting for a dispatcher and an asset waiting for a customer, and it is the single sensor that most improves pool management. Door sensors report open and close events, which support security and dwell analysis at customer docks. Tether or hook detection reports when the trailer is connected to a tractor, which lets the TMS infer a hook event even when the driver forgets to record it.

Tire pressure monitoring on trailers reports pressure and often temperature for each tire position and flags a slow leak before it becomes a roadside failure or a blown tire that destroys a wheel end. Reefer telematics, offered by the refrigeration unit manufacturers and by third party devices, report set point, return air and supply air temperature, operating mode, alarms, and fuel level. For a reefer carrier, fuel level on a trailer parked at a customer for a week is both a cost question and a cargo claim question. Each sensor type should map to a specific column in the trailer status table in the TMS and should drive a specific exception, which is the design rule that keeps a sensor project from becoming a dashboard nobody looks at.

Trailer to Tractor Ratios in Drop and Hook Networks

Carriers often describe their trailer fleet as a ratio to tractors, and the ratio is a useful summary but a poor planning tool. A live load carrier with one trailer per tractor plus a few spares has a low ratio. A dedicated drop and hook carrier serving customers with long loading cycles may run several trailers per tractor. The ratio is the result of the network, not a target to set first. What actually determines trailer need is the sum of trailers staged at each customer location, trailers at the carrier's own yards for staging and maintenance, trailers in transit, and a reserve for seasonal peaks and unplanned downtime. Each of those components can be measured once telematics is in place, and each one has a different owner: customer pools belong to account management and dispatch, yard pools to operations, transit trailers to dispatch, and the shop queue to maintenance.

The ratio becomes useful again as a trend indicator. If the measured ratio climbs while volume is flat, trailers are accumulating somewhere, usually at customers. If it falls while service complaints rise, the pool is too thin. The planning work happens at the customer location level, which is where the sizing math in a later section lives, and the fleet ratio simply summarizes the result. Carriers that set a ratio target first and then try to force customer pools to fit it usually end up either starving their best accounts or paying for trailers that sit in their own yard.

Automated Yard Checks With Geofences and TMS Reconciliation

An automated yard check replaces the clipboard with a query. Every yard the carrier operates and every customer location where trailers are dropped is drawn as a geofence, a polygon on the map stored in the location master with a type, an owner, and the applicable pool and detention terms. The telematics feed places every trailer inside a fence, outside all fences, or unreported. The TMS trailer table holds where the carrier believes the trailer is, based on the last dispatch event: dropped at customer X, in yard Y, hooked to tractor Z on load N. A scheduled query, typically run several times a day, compares the two and writes the differences to an exception list.

The exception categories are predictable and each one has a resolution path. A trailer the TMS shows at a customer but GPS shows at the carrier yard means a driver hooked it and did not record the event, so dispatch corrects the trailer record and the driver gets a reminder. A trailer GPS shows at a customer but the TMS shows as available in the yard means a drop was recorded against the wrong trailer number, which happens constantly when drivers key numbers by hand. A trailer outside every fence and not moving may be at an unlisted customer dock, at a repair shop, or stolen, and it needs a phone call within the hour. A trailer that has not reported in 24 hours may have a dead device, may be inside a metal building, or may have been moved somewhere with no coverage, and it needs a device health check. The yard check becomes an exception review of a handful of trailers rather than a walk of hundreds.

• Location mismatch - GPS fence differs from TMS location; correct the TMS record and identify the missed event.
• Unknown location - Outside all fences; confirm by phone, add the fence if it is a legitimate dock.
• Silent device - No report beyond threshold; check device health, battery, and last known position.
• State mismatch - Cargo sensor says loaded, TMS says empty or the reverse; verify before dispatching.
• Unmatched hook - Tether detected with no dispatched load; find the tractor and the reason.

Our ELD and EDI integration work typically connects the trailer telematics API to the TMS so these comparisons run on a schedule without a person exporting a file. The TMS implementation side adds the geofence type, pool terms, and detention terms to the location master and the reconciliation status to the trailer table so dispatch sees the exception on the screen they already use.

Drop Trailer Detention, Trailer Rental, and Per Diem Clauses

Detention on a live load is measured in hours while the driver waits. Detention on a drop trailer is measured in days while the trailer waits, and it is governed by a different clause in the customer contract, usually called trailer rental, trailer detention, or per diem. A typical structure grants the customer a free allowance of a certain number of days per trailer, after which a daily charge applies, sometimes with a cap or an escalating rate. Many contracts also specify a pool size the carrier agrees to maintain and a notice period for changes. These clauses are often negotiated once and then never enforced, because the carrier cannot prove when the trailer arrived and when it left.

Trailer telematics supplies the proof. The geofence entry timestamp is the arrival, the geofence exit timestamp is the departure, and the dwell is the difference. The TMS customer master holds the free day allowance, the daily rate, the cap, the calendar rule for counting days, and whether weekends and holidays count. A billing query joins the dwell record to those terms and produces a detention line for every trailer whose dwell exceeded the allowance, with the arrival and departure timestamps and the GPS positions as backup. The carrier can then decide account by account whether to bill, waive, or use the data in the next rate conversation. Many carriers find that the data itself changes customer behavior before an invoice is ever sent, because the monthly dwell report shows the shipper which of their own sites are holding trailers.

Contract language matters, and this monograph is not legal advice. The point from a systems standpoint is that the terms must be in structured fields, not in a PDF, before the TMS can apply them, and the arrival and departure evidence must come from a source the customer will accept. GPS timestamps with positions inside the customer's own fence are difficult to dispute. Driver recollection is not.

Dwell Reports by Customer Location

Once arrival and departure timestamps exist for every trailer at every fence, dwell reporting is a grouping exercise. The basic report shows, by customer location and month, the number of trailer arrivals, the average and median dwell in days, the distribution of dwell in bands, the count of trailers currently on site by load state, and the detention days accrued and billed. Splitting dwell by load state is the key refinement. A loaded trailer sitting at a shipper is waiting for the carrier to pick it up, which is the carrier's problem. An empty trailer sitting at a shipper is waiting for the shipper to load it, which is the pool working as designed until it exceeds the allowance. An empty trailer sitting at a consignee is waiting for the carrier to retrieve it, which is often the largest hidden pool in a network because nobody owns the empty trailer at a delivery site.

The dwell report should also show trend by week so that account managers see a site drifting before it becomes a dispute, and it should list the specific trailers with the longest current dwell so that dispatch can act. A SQL data mining engagement usually produces this report as a set of saved queries against the dwell table, with the location master supplying the customer and site attributes and the trailer table supplying the load state. Carriers that have never had this view are regularly surprised by how concentrated long dwell is in a small number of sites.

Pool Right Sizing Math

With measured dwell and daily volume by location, pool sizing becomes arithmetic. The formulas below are illustrations of the approach and not industry constants; each carrier should fit them to its own measured data. The core idea is that the number of trailers a site needs is the number arriving each day multiplied by the number of days each one stays, plus a reserve for variability.

For example, a customer location that receives 4 trailer drops per day on average, where each trailer dwells 3 days on average, needs about 12 trailers on site at steady state, because 4 arrivals per day times 3 days of dwell equals 12 trailers present. If dwell varies and the carrier wants to absorb a day of slippage without a service failure, it adds one day of arrivals, so 4 more, for a pool of about 16 at that site. If the carrier can bring median dwell down from 3 days to 2 through the dwell report and the detention conversation, the same site needs about 8 trailers plus the reserve of 4, or 12. The 4 trailers released go to another site or come out of the fleet. Run that calculation for every site, add trailers in transit between sites, add the shop queue from the maintenance system, and add a fleet level seasonal reserve, and the total is the trailer count the network actually needs. Compare it to the trailers owned or leased and the difference is either excess capital or a shortage that is causing service failures.

The trailer pool utilization calculator on this site walks through that arithmetic for a single site and for a fleet, using inputs for daily drops, dwell, reserve days, transit count, and shop count. It is an illustration tool; the inputs should come from the dwell report, not from guesses. Carriers using the calculator alongside their own measured data get a defensible pool target for each account that can be written into the contract and monitored by the automated yard check.

Maintenance and Inspection Integration

Trailers in drop pools are the equipment most likely to fall out of inspection compliance because they are out of sight. 49 CFR 396.17 requires every commercial motor vehicle, which includes trailers and semitrailers, to pass a periodic inspection at least once every 12 months, performed by a qualified inspector under 49 CFR 396.19, with the inspection report retained under 49 CFR 396.21 and proof of inspection carried on or in the vehicle. 49 CFR 396.3 requires a systematic inspection, repair, and maintenance program for all vehicles under the carrier's control, with records of the vehicle identification, due dates, and work performed. Drivers must inspect trailers as part of pre trip and post trip duties, and 49 CFR 396.11 governs the driver vehicle inspection report when defects are found. Carriers should read the current text of these sections and confirm any detail with FMCSA.

The data model treatment is simple. The trailer table carries the periodic inspection date and the computed due date, the preventive maintenance interval and next due date, and the open defect count from the maintenance system. The exception report flags any trailer whose inspection is due within 30 days and whose GPS position is at a customer site or distant yard, so that dispatch can route it home or schedule a mobile inspection before it is overdue. It also flags any trailer dispatched on a load with an expired inspection or an open out of service defect, which should be a hard stop in dispatch. Tire pressure alerts and reefer alarms from the telematics feed create work orders in the maintenance system automatically, with the trailer position attached so the shop knows whether to dispatch a road service or wait for the trailer to arrive. The predictive dispatch optimization work on this site extends this by routing trailers due for service toward terminals with shop capacity as part of normal load planning rather than as a separate recall.

The Trailer Data Model

A trailer program needs five tables that most TMS platforms either have or can add. The trailer master holds trailer number, VIN, year, make, type, length, ownership or lease status, telematics device identifier, reefer unit identifier if any, inspection and maintenance due dates, and current status fields for location fence, load state, hook state, tractor, and last report time. The location master holds every yard and customer site with the geofence polygon, type, customer link, pool target, and detention terms. The trailer event table holds every arrival, departure, hook, unhook, door, and cargo state change with timestamp, source, and position, which is the audit trail for everything else. The dwell table is derived from arrival and departure pairs by trailer and location and holds dwell days, load state at arrival, and detention days computed against the terms. The exception table holds each open reconciliation exception with type, trailer, detected time, assigned owner, and resolution.

The joins are what make the model work. Trailer events join to loads through the hook and drop events, so that every load shows which trailer actually moved it according to telematics, not just which trailer the driver typed. Dwell joins to the customer master for billing terms. Exceptions join to users for ownership. The telematics device identifier on the trailer master is the key that ties the vendor feed to the carrier's trailer number, and keeping it accurate when devices are moved between trailers is a maintenance process worth writing down. Our business process optimization practice often starts a trailer project here, because a device swap that is not recorded will make a perfectly good trailer appear to be in two places at once.

KPIs and the Weekly Cadence

The program should report a small set of indicators weekly. Trailer utilization is the share of trailers that moved under load in the period. Average and median dwell by location and in total, split by load state, show whether the pool is working. Reconciliation exceptions open and the average time to resolve them show whether the yard check is trusted. Detention days accrued, billed, and waived show whether the contract is being enforced. Trailers out of inspection compliance, and trailers within 30 days of due at remote sites, show the maintenance exposure. Device health, meaning the share of trailers reporting within the last 24 hours, shows whether the telematics layer itself can be trusted. The fleet trailer to tractor ratio, as a trend, summarizes all of it.

The cadence is weekly for the operations review and daily for the exception queue. Each morning, dispatch works the reconciliation exceptions and the trailers approaching inspection due dates. Each week, operations reviews dwell by location and the detention accrual, account management reviews the sites with the longest dwell and decides on customer conversations, and maintenance reviews the tire and reefer alerts that did not already create work orders. Each month, management reviews the pool sizing calculation against the measured dwell and decides whether to move trailers between accounts, add trailers, or return leased units. For example, a 100 truck fleet running a drop and hook network would typically be managing several hundred trailers, and a daily exception list of a dozen or two is the sign of a healthy program; a list of hundreds means the device identifiers, the fences, or the driver event capture need repair before the pool math can be trusted.

Related practice areas for this work include ELD and EDI Integration TMS Implementation SQL Data Mining Predictive Dispatch Optimization. Each practice page describes scope, deliverables, and how an engagement starts with a short discovery call. The trailer pool utilization calculator provides a starting point for the sizing arithmetic.

How Strong Tower Consulting Helps

Strong Tower Consulting helps carriers connect trailer telematics to the TMS trailer table, draw and maintain the geofence and pool terms in the location master, and build the reconciliation, dwell, detention, and inspection exception queries that make the pool measurable. The work starts with a device and trailer inventory and a first reconciliation, which usually surfaces the mismatches and silent devices on day one, and moves to the dwell report and the sizing model once the data is trusted. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. That separation keeps consulting advice vendor neutral and focused on the carrier operation.

To discuss your trailer fleet, your drop and hook accounts, and the telematics you already have, call 763-244-1373 and ask for Scott Elliott. A short call is enough to scope the first reconciliation and identify which customer sites to measure first.

Frequently Asked Questions