Monday, 07:40. The ops director opens five exports: gate times from the tablet, a yard sheet with “moves,” an M&R queue in email, a billing dispute list from finance, and yesterday’s radio notes. None of them disagree politely. They disagree in units, timestamps, and definitions. By 08:10 the meeting is about which file is “more right,” not which KPI should change the shift.
That is the analytics problem at a US empty depot. Not “do we have a dashboard.” A decision-spine problem: gate dwell, turn time, rehandles, open repairs, and dispute-ready billing events must come from the same events the yard already runs—or the chart is theatre.
This piece is for empty-depot operators evaluating depot operations analytics software—ops visibility that changes Monday morning priorities, not BI tooling bolted onto a freight TMS. For what Available must mean before a pick, see container availability management. For count-vs-bay trust, see container yard inventory management. Here the focus stays on shift KPIs that change decisions.
Vanity charts vs KPIs that change a shift
A vanity chart answers “how busy did we look?” A shift KPI answers “what do we change before lunch?”
Vanity patterns show up fast:
- Beautiful TEU-on-hand trends that ignore holds, open M&R, and false Available
- Average “cycle time” with no Gate In / Gate Out event definition
- Move counts that mix productive picks with forced rehandles
- Repair backlogs measured as ticket volume, not days blocking release
- Revenue charts that hide dispute age and missing gate evidence
Empty depots (~200–5,000 TEU) sell named unit events: Gate In, inspection/grade, hold, rehandle, Gate Out, estimate, invoice clock. Depot operations analytics software earns trust when those events feed the KPI—not when a nightly CSV is reshaped into a pretty tile.
If a metric cannot be traced to a unit timeline event, park it. It will not survive peak week.
Gate dwell and turn time from real Gate In/Out
Gate dwell and turn time are the first honest ops KPIs—when they are event-timed.
Define the clocks
- Gate dwell: time from truck arrival / check-in intent to Gate Out complete (or to clear-of-gate, if that is your commercial rule). Same definition for every truck type you measure.
- Turn time (empty programme): time from Gate In complete to Gate Out complete for the unit, or from booking advice to release—pick one and stick to it. Mixing both in one chart invents “improvement.”
What breaks the metric
Paper EIRs filed hours later. Radio “already out” with no Gate Out event. Batch Gate In that stamps one timestamp for twenty boxes. Side apps that record gate photos but never write the event the yard uses for inventory and billing.
When dwell and turn time live outside the depot OS, Monday’s chart is an argument about clocks, not a queue plan. Gate product context: gate management software for depots. Empty-programme spine: empty container depot software.
Practical rule: dwell and turn time are derived from Gate In/Out on the unit record. If the KPI needs a second stopwatch, the gate event is incomplete.
Rehandles and blocked-bay signals
Rehandles are not “busy yard energy.” They are cost, damage risk, and a leading indicator that stacking or release rules are fighting the pick plan.
What to count
- Forced rehandles: moves required to free a buried unit for a confirmed pick
- Planned rehandles: intentional restacks (programme change, grade segregation) — still cost, but different root cause
- Blocked-bay signals: picks delayed because the bay plan and the Available list disagreed
A move counter that cannot separate productive Gate Out staging from “dig out the wrong stack” will celebrate volume while margins shrink. Inventory spoke owns count-vs-bay accuracy; this analytics spoke owns rehandle rate as a shift cost KPI—link, do not rewrite: container yard inventory management.
If rehandles only appear in radio lore, you do not have a rehandle KPI. You have a story.
Open M&R and false Available as linked metrics
Open repair and false Available are one ops problem with two faces.
- Open M&R backlog: estimates waiting approval, unfinished work, graded units still marked sellable
- False Available rate: units shown Available that fail hold, grade, open M&R, or reservation checks when the desk verifies
Directors who watch only “Available count” will staff for a yard that does not exist. Directors who watch open M&R days-to-release and false Available sample rate will catch the lie before the line does.
Availability owns the definition of Available; analytics owns how often the definition fails under pressure. See container availability management. Do not retarget M&R product keywords here—fold repair language into the open-repair KPI, not a second M&R pillar.
Soft check: sample ten Available units and ten open repairs. If Available and open M&R disagree on more than a couple, your “ops dashboard” is lying politely. See the same unit timeline on containerhub.ai.
Billing disputes as an ops lagging indicator
Billing disputes are not only a finance problem. They are a delayed ops KPI.
Dispute-ready billing events need:
- Gate In / Gate Out timestamps that match the commercial clock
- Storage / handling triggers tied to those events
- Evidence the client portal and the invoice can both cite
When finance opens a dispute pack by hunting screenshots and radio notes, the lagging indicator is already red: ops events were not invoice-grade when they happened. Billing spoke owns dispute workflow and tariff mechanics; analytics owns dispute age and dispute rate as feedback into gate/yard discipline: empty container depot billing software.
A rising dispute rate with “stable” gate charts usually means the gate chart and the billing clock are not the same event.
What the director should see Monday morning without exporting five sheets
Ignore brochure BI for a moment. Before the first stand-up, the ops screen should expose:
| Monday view | Why it changes the shift |
|---|---|
| Gate dwell / turn time (last 24–72h) from real Gate In/Out | Staff the queue you actually have |
| Rehandle count vs productive picks | Spot buried-stack and plan fights early |
| Open M&R blocking release (count + age) | Protect Available honesty |
| False Available sample / blocked reasons | Stop promising stock you cannot stage |
| Dispute-open / dispute-age tied to missing gate evidence | Fix the event, not the PDF |
| One unit drill-down | Argue from the same timeline as the yard |
Nice-to-haves that still serve decisions: programme or client filters on the same KPIs; role-safe views for site desk vs central ops; alerts when dwell or false Available crosses a threshold you named.
Reject as “depot operations analytics software”: a freight TMS empty-TEU dashboard; a generic YMS heat map with no empty-depot release rules; five CSVs stitched in Looker with no shared event ID; vanity TEU trends that ignore holds and open M&R.
ContainerHub’s framing for empty-depot operators is this spine: gate, EIR/inspections, M&R, yard state, billing, and portal on one model—so KPIs are consequences of events, not a second spreadsheet religion.
Soft CTA: live depot KPIs on one timeline
If Monday still starts with five exports that disagree on clocks and Available, the fix is not a prettier chart theme. It is depot operations analytics software fed by the same unit timeline the yard already runs: dwell and turn from Gate In/Out, rehandles as cost, open M&R linked to false Available, disputes as ops lag—not vanity tiles.
ContainerHub is a depot / yard OS for physical empty-container operations (~200–5,000 TEU)—gate, digital EIR, inspections, M&R, yard, billing, client portal, and Jarvis on one model—not freight TMS, not WMS SKU software, not a marine TOS pitch. Soft next step only: review the product, book a demo, or compare pricing. No directory “claim your depot” ask.
Walk one Monday pack in a demo with your dwell definition, rehandle reasons, and dispute clocks. Ask whether each KPI drills to a unit event—and whether Available can disagree with open M&R on the same screen. If those answers are clear, the stand-up gets shorter.
Visit ContainerHub · Pricing · Demo
Related reading: Empty container depot software · Container availability management · Container yard inventory management · Empty container depot billing software · Gate management software for depots