Tuesday, 10:15. A line asks for six 40HC empties “available for pickup this afternoon.” Your filter shows eight Available. Two sit on a damage grade nobody cleared. One has an open repair estimate waiting approval. One was reserved for another programme and never released. You still have to answer—and decide whether “Available” means safe to promise or someone typed a status.
That gap is the availability problem at an empty depot. Not “how many boxes are in the yard.” Not “which bay holds the stack.” A release-readiness problem: presence is only the first gate. Hold, grade, open M&R, and release rules must clear before a pick is honest.
This piece is for US empty-depot operators who need release-readiness rules they can defend under line pressure—without rewriting inventory accuracy (count vs bay) or yard rehandle mechanics. For count-vs-bay trust, see container yard inventory management. Here the focus stays on what Available must mean before the desk confirms a pick.
Why “Available” at an empty depot is not “in the yard”
“In the yard” answers a location question. Available answers a commercial and operational question: can we release this unit to this requester, under this programme, today?
Those are not the same.
A unit can be physically on site and still be:
- On hold (damage, unpaid storage, customs, wait-for-line, programme block)
- Wrong grade for the booking (cargo-worthy vs repair vs scrap / scrap-candidate rules your lines already enforce)
- Mid-repair with an open estimate or unfinished work order
- Reserved or allocated to another booking that has not been released
- Staged for someone else, or gated in without a completed inspection outcome
Freight TMS and generic “empty container management system” language often collapse this into a quantity: TEUs on hand, empties by size. Empty depots (~200–5,000 TEU) sell named units that must clear release rules before a truck is told “come get it.”
So container availability management is earning Available on a unit timeline—not typing it into a cell after a radio call. Presence is necessary. Presence is not sufficient.
The four blockers: hold, grade, open repair, and unreleased reservation
False Available almost always fails one of four checks. Name them so the desk stops inventing fifth explanations under pressure.
1. Hold
Any active hold—damage tag, commercial block, regulatory, programme instruction—must flip releasability even when the unit is still “in inventory.” A hold that lives in chat while the status stays Available is how you stage a blocked box. The count was fine; the promise was not.
2. Grade
Lines do not accept “a 40HC.” They accept a grade that matches the booking or pool rule. If grade sits in a side note and Available ignores it, the filter lies. Grade is not decoration on the EIR; it is a release gate.
3. Open repair (M&R)
Open estimate, pending approval, or unfinished work means the unit is not release-ready—unless your commercial rule explicitly allows a graded exception (rare, and still a rule, not a vibe). Dual truth kills trust: workshop knows the box is open; the Available list does not.
4. Unreleased reservation / allocation
A unit reserved for Programme A that still shows Available for Programme B will get double-booked. Reservations that never expire, never release, and never touch the Available filter create phantom stock that looks healthy until two trucks show up.
A practical ops rule: Available = no active hold + grade eligible + no open M&R blocking release + not reserved elsewhere + gate/inspection state complete enough to leave. If any clause is missing from the software, the desk will fake it in Excel—and peak week will expose it.
How Gate In / Gate Out drift creates phantom Available
Availability is an event consequence, not a nightly flag. Gate drift is where phantom Available is born.
Gate In without a releasability outcome
Gate In puts the container on site. If inspection outcome, initial grade, or default hold rules are skipped under queue pressure, you get a unit that looks inventoriable, an Available filter that includes boxes nobody cleared to sell, and a desk that promises picks the yard will refuse once someone reads the EIR.
Batch Gate In for peak returns is healthy when the same flow attaches inspection/grade quickly. A batch that only creates “in yard + Available by default” accelerates phantom stock.
Gate Out that never clears Available
A truck leaves; the system still shows Available or In yard—paper EIR filed later, radio “already out,” release closed in one tool and status updated in another. Available climbs above what you can stage. Lines book against ghosts.
Status edits that skip the gate event
Someone sets Available because the line is waiting—without clearing the hold or closing the repair. That is typing, not container availability management. Phantom Available is usually stale or forced state, not theft.
Gate protects availability only when Gate In/Out, inspection/grade, holds, and reservations write to the same unit timeline. Isolated gate apps that dump CSV into an “Available list” recreate phantom stock every shift. Empty-programme context for that spine: empty container depot software.
Soft check: pull ten units marked Available and verify hold, grade, open M&R, and reservation on the record—not on the radio. If more than a couple fail, the problem is the Available definition, not the stacker. See one unit timeline on containerhub.ai.
What the desk must show before confirming a pick to a line
Ignore brochure dashboards for a moment. Before the desk says “yes” to a line or trucker, the operator screen must expose, per candidate unit:
| Must show | Why the pick depends on it |
|---|---|
| Unit ID + size/type | Named asset, not a TEU quantity |
| Available / blocked reason | Releasability, not presence |
| Hold (if any) + who can clear | Stops false promises |
| Grade vs booking requirement | Line acceptance, not “any empty” |
| Open M&R state | Estimate / approval / work complete |
| Reservation / programme | Avoids double-book |
| Last gate / inspection event | Proves the status was earned |
| One timeline | Desk and yard argue from the same story |
Nice-to-haves that still serve release readiness: filters that exclude blocked units from Available by default; portal views that read the same releasability the yard uses; audit of who flipped Available and why.
Reject as “availability software”: a green status with no hold/grade/M&R gates; a freight TMS empty count with no depot release rules; a cleaned line export that strips holds “for the email”; nightly reconciliation as the primary design.
ContainerHub’s framing for empty-depot operators is this spine: gate, EIR/inspections, M&R, yard state, billing, and portal on one model—so Available is earned on the unit record, not maintained as a side list.
Spreadsheet Available lists vs an ops-tied unit timeline
Spreadsheets are fine as working files. They fail as the system of record for releasability—especially when one sheet is “ops truth” and another is “what we tell the line.”
Failure mode 1: Two Available columns
Yard sheet says 40 releasable. Customer export says 47 after someone strips holds and open repairs “so the line doesn’t panic.” Both teams believe they are helping. The line books the higher number. The bay cannot deliver.
Failure mode 2: Holds and grades as free text
Available stays green because hold/grade never had filterable fields—or the fields are notes nobody queries. The list “passes” a glance. Dispatch still stages a blocked or wrong-grade box.
Failure mode 3: Repair in inbox, Available in cells
Workshop tracks open estimates in email. The Available workbook never hears about them. Phantom stock looks fine until the reach-stacker finds a tagged unit.
Failure mode 4: Reservations in chat
“Hold six for Maersk tomorrow” lives in WhatsApp. The filter still sells those six to the next caller. Dual booking is not a yard problem; it is an Available-definition problem.
Failure mode 5: Nightly paste as integration
CSV from gate → paste into Available workbook → clean → email to line. Every handoff can revive a gated-out number or bury an open repair. Dual systems fail as small permanent over-promise.
An ops-tied unit timeline flips the dependency: gate, inspection, hold, grade, M&R, and reservation post first; Available is derived (or strictly gated) from those events. Inventory accuracy (count vs bay) still matters—see container yard inventory management—but clean counts with false Available still burn line trust. For a broader look at solutions, see our guide to container availability management.
Buyer checklist: availability rules that survive peak week
Use this when you evaluate container availability management inside a depot / yard OS—or when you audit your sheet stack before peak empties.
- Available is gated, not typed — hold, grade, open M&R, and reservation block sellable status unless an authorized override is logged with a reason.
- Gate In does not auto-mean Available — inspection/grade (or an explicit default rule) must complete before the unit is promise-ready.
- Gate Out clears Available the same event — no orphan sellable units after the truck leaves.
- One Available for desk and line — portal or export reads the same releasability ops uses; no “cleaned” second list.
- Open repair is visible on the pick screen — not only in the workshop queue.
- Reservations expire or release on purpose — no silent forever-holds that shrink real stock while the filter looks fat.
- Overrides leave an audit trail — who forced Available, when, and why.
- Peak batch Gate In still attaches releasability — grade/hold state lands fast enough that Tuesday’s list is honest; “in yard” and “Available” stay separate views.
If more than a couple of rows fail, you do not have a training problem. You have a definition problem the software must enforce. Product frame: empty-depot OS (gate, EIR, inspections, M&R, yard, billing, portal)—not freight TMS empty counts, not a marine TOS pitch.
Container availability in ContainerHub
If your empty depot still promises from a green status while holds, grades, open repairs, and reservations live somewhere else, the fix is not a stricter email template. It is container availability management on one timeline: Available earned from gate, inspection, hold, grade, M&R, and release rules—per unit.
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 busy empty window in a demo with your hold reasons, grade labels, and reservation habits. Ask whether Available can stay sellable while a hold or open repair is active—and whether the line-facing view can disagree with the yard. If those answers are clear, pick confirmations get shorter.
Visit ContainerHub · Pricing · Demo
Related reading: Empty container depot software · Container yard inventory management · Container yard management software · Gate management software for depots · vs Excel