Tuesday, 10:40. A line desk pings three channels at once: "Is REEU 482917 ready?" WhatsApp says washed. The M&R ticket says PTI pending. The yard board says Available. Gate books the truck. Forty minutes later the unit fails pre-trip on the pad—and everyone was "right" in their own spreadsheet.
That is the empty reefer PTI depot operations problem at a US empty depot. Not "do we own a reefer plug map?" Ops fails when PTI pass/fail, wash/survey status, and release authority disagree on the same unit. "In yard" is inventory. "Ready empty reefer" is a commercial decision the line already treats as truth.
This piece is for ops and line-service buyers who demo to stop reefer-ready chaos across WhatsApp, Excel, and ticket threads on an empty-container depot/yard OS (~200–5,000 TEU)—gate, EIR, inspections, M&R, yard, billing, portal, Jarvis—not freight TMS, marine TOS, or a terminal reefer camera stack. Inspections/M&R timeline: container M&R / inspection software. Availability language: container availability management. Release authority: empty container hold and release. Line visibility: empty container depot client portal. Yard spine (optional): container yard management software. Focus stays on PTI, wash/survey, and when a unit is truly releasable—without rewriting the M&R product page or the gate pillar.
What "ready empty reefer" must mean at the depot (not just "in yard")
Ask five empty-depot teams what "reefer ready" means and you will hear five different clocks:
- Physically present — unit in a reefer bay / stack, genset or plug context known
- Structurally acceptable — grade / damage state the programme will accept
- PTI complete — pre-trip inspection pass (or documented fail → repair path)
- Wash / survey clear — food-grade / chemical / programme wash state the line desk asks for
- Commercially releasable — no hold, Available for that line/programme, gate can book without a side call
Most "we're ready" stories are (1) plus hope. That is not empty reefer PTI depot operations. That is inventory theater. The line did not ask whether the box casts a shadow on the asphalt. They asked whether they can put a truck on it without a morning failure.
Practical rule: if "ready" can mean different things in WhatsApp, the M&R ticket, and the Available board, you do not have reefer readiness—you have three opinions.
PTI pass/fail on the unit timeline
Pre-trip inspection is not a sticky note on the machinery. It is an ops event that must sit on the same unit timeline as gate-in evidence, holds, and Available.
What must already be true on the depot OS before anyone tells the line "PTI done":
- Unit identity continuity — same container ID from gate → inspection PTI → release
- PTI outcome as a recorded state — pass / fail / incomplete with timestamp and who signed
- Fail path that blocks release — fail does not silently coexist with Available
- Pass that does not invent wash — PTI green is not a food-grade wash certificate
- Re-PTI triggers — after repair, prolonged dwell, or programme rules that invalidate the last pass
- Proof the line can see — not a photo in a private chat the portal never receives
PTI belongs next to inspection history on container M&R / inspection software—so the shop and the line desk argue from one trail, not from "I thought we ran it yesterday."
| PTI state on depot OS | What the line should hear | What breaks if it lives in a side sheet |
|---|---|---|
| Not started | Not ready — schedule / queue visible | WhatsApp claims "done" while bay is empty |
| In progress | Not releasable yet | Gate books; pad fails mid-shift |
| Pass | PTI clear (wash/holds still apply) | Stale pass after repair / long dwell |
| Fail | Held pending repair / re-PTI | Available stays green; truck wasted |
| Void / expired | Must re-run before release | Portal shows last week's green check |
Practical rule: if PTI pass lives in a chat while Available lives in Excel, your "ready" answer is already outdated by the time the truck turns into the lane.
Wash / survey status the line desk actually asks for
Lines rarely ask for a novel about detergent. They ask a blunt commercial question: is this empty reefer in the wash/survey state our programme requires before pickup?
Typical desk questions that must map to unit states—not tribal knowledge:
- Food-grade / clean vs chemical / last-cargo context
- Wash complete vs wash required vs wash waived by programme
- Survey / condition confirmation tied to the same unit ID
- Photos or checklist references the portal can show without a side drive
- Whether wash failure creates a hold or only a "not Available" signal
Wash is adjacent to M&R and inspections, but it is not "rewrite the repair product page." It is release gating language the line already uses. Pair wash outcomes with container availability management so "clean enough" and "Available" cannot diverge for a week.
Practical rule: if the wash bay whiteboard is more trusted than the unit record, the line desk will keep calling—because your system is optional.
How PTI ties to holds, Available, and release authority
This is where empty reefer PTI depot operations either become a product story—or stay a morning fire drill.
A unit can be in the yard, PTI-passed, even washed, and still not releasable. Holds and release authority are not decorative flags; they are the commercial brakes. See empty container hold and release.
Healthy coupling looks like this:
- PTI fail → hold or blocked Available — no silent green board
- Wash required → not Available for that programme until cleared
- Hold clear does not invent PTI — releasing a commercial hold is not a pre-trip pass
- Available means releasable under current facts — PTI + wash + hold state agree
- Gate proof matches the desk answer — the truck that books is booking the same truth the portal shows
When PTI, wash, holds, and Available share one timeline, the empty container depot client portal stops being a brochure and starts being the line's first answer—before WhatsApp.
Soft check: pick last week's three "reefer ready?" escalations. If any root cause was "PTI was done but Available was wrong," "washed but still on hold," or "portal said OK and the pad failed," you do not have empty reefer PTI depot operations yet—you have parallel truths. See unit-timeline ops on containerhub.ai.
Practical rule: release authority without PTI/wash inputs is theater; PTI/wash without release authority is a lab note the gate ignores.
What not to bolt on (fleet TMS, terminal TOS camera stacks)
When reefer chaos hurts, vendors offer the wrong spine:
| Tempting bolt-on | What it optimizes | Why it misses empty-depot PTI |
|---|---|---|
| Fleet / freight TMS | Loads, drivers, dispatch | Does not own depot Available, holds, or PTI-as-ops-event |
| Marine terminal TOS + reefer monitoring | Powered stacks, alarms, vessel plans | Empty depot release truth ≠ terminal reefer TOS |
| Standalone mobile "damage app" | Photos in a silo | Wrong SERP for depot OS; no hold/Available coupling |
| Second M&R spreadsheet "just for reefers" | Familiar pain | Guarantees dual truth with the yard board |
You do not need a camera-heavy terminal stack to answer "is the empty reefer releasable?" You need depot OS events: PTI outcome, wash/survey state, hold, Available, gate-ready proof—on one unit.
Practical rule: if the demo starts with vessel bay plans or over-the-road dispatch, you are buying someone else's product category.
Buyer checklist: reefer-ready empties without a second system
Before you buy another reefer module or enlarge the WhatsApp group, walk this checklist in a demo with your own failed pickup sample:
- PTI as unit event — pass/fail/incomplete with timestamp, actor, and audit—not a chat claim
- Fail blocks release — fail cannot coexist with Available for that line/programme
- Wash / survey states the desk recognizes — required / complete / waived mapped to programme rules
- Hold interaction — commercial and quality holds compose with PTI/wash without a side sheet (empty container hold and release)
- Available = releasable — board language matches container availability management, not "somewhere in the yard"
- Portal answer matches pad reality — line sees the same PTI/wash/hold facts before booking (client portal)
- Re-PTI / re-wash triggers — after repair or rule-based expiry, old greens do not linger
- Boundary clarity — depot OS owns empty-reefer readiness; TMS/TOS stay in their lanes
If more than two items fail, do not start with a prettier wash log. Start with one unit timeline the line can trust.
Soft CTA: reefer-ready empties on one depot OS
If the line still asks "is the reefer ready?" across WhatsApp while PTI, wash, holds, and Available live in different places, the fix is not a louder group chat. It is empty reefer PTI depot operations on an empty-depot OS where pre-trip, wash/survey, and release truth share one unit timeline.
ContainerHub is a depot / yard OS for empty-container operations (~200–5,000 TEU)—gate, digital EIR, inspections, M&R, yard positions, billing, client portal, and Jarvis on one model—not freight TMS, not WMS, not a marine TOS pitch. Soft next step only: review the product, book a demo, or compare pricing. No directory ask.
Walk one failed reefer pickup and one "ready on WhatsApp, dead on the pad" unit in a demo. Ask whether PTI pass/fail, wash/survey, holds, and Available update as the same timeline the portal and gate will show—without a second system for reefers.
Visit ContainerHub · Pricing Demo
Related: Container M&R / inspection software · Container availability management · Empty container hold and release · Empty container depot client portal · Container yard management software
