Wednesday, 11:40. A line ops desk pings: “Where is MSCU7654321—and can you send the EIR?” Ten minutes later a trucker asks whether the unit is Available for pickup this afternoon. Your clerk knows both answers live somewhere—Gate In sheet, hold chat, M&R folder, last night’s export. None of those places is what the line can open themselves. Peak week turns every status ask into archaeology.
That is the empty container depot client portal problem at a US empty depot. Not a second inventory system. Not a directory listing. Not a freight TMS track-and-trace widget. A visibility layer on the same movement, hold, repair, and gate events the yard desk already trusts—so lines (and optionally truckers) stop asking for truth that should already be shared.
This piece is for ops-desk buyers who demo to cut “where’s my box / send EIR / repair status?” email on an empty-container depot/yard OS (~200–5,000 TEU)—gate, EIR, inspections, M&R, yard, billing, portal, Jarvis—not a freight TMS and not a marine TOS. Yard spine: container yard management software. Inventory trust: container yard inventory management. Available definition: container availability management. Release authority: empty container hold and release. Focus here stays on what external parties should see live—without inventing a parallel ledger.
Who the portal is for (line ops vs trucker appointment view)
One portal URL does not mean one role. Empty depots usually need at least two scoped views.
Line ops care about their equipment programme: which units are on site, Gate In / Gate Out with timestamps, hold vs Available vs Released, grade where commercial rules allow, open M&R / estimate status, and EIR or gate proof when the desk would otherwise email a PDF. They do not need every neighbour line’s stack plan.
Truckers / haulers (when you expose them) need a thinner appointment-facing slice: slot confirmation, which unit or equipment ask is tied to the visit, whether the unit is still releasable before they roll, and gate outcome after the move—not the full commercial hold ledger. Pair with vehicle booking system for container depots so appointment and status share one unit timeline.
Practical rule: if line ops and truckers see the same unscoped dump, you do not have a client portal—you have a public spreadsheet with a login.
Status that must be live (not a nightly export)
A portal that refreshes from last night’s CSV is theatre. Lines escalate during the day because the unit moved this morning.
Minimum live fields on the unit the party is allowed to see:
- On-site / departed — Gate In and Gate Out as committed events, not “probably still here”
- Releasability state — Hold, Available, or Released (and to whom), aligned with your availability and hold/release rules—not a green cell someone typed
- Grade / programme context the party is cleared to know
- Open M&R blocking leave (or clear commercial status) when the line will ask anyway
- Last meaningful event time — so “is this stale?” is answerable without calling the booth
Nightly exports are fine for ERP handoff. They are not a portal. If the desk still answers from a fresher sheet than the portal shows, external users will keep emailing.
Practical rule: if the portal can disagree with the booth for more than a few minutes after Gate In, you trained the line to distrust both.
Gate proof and EIR visibility without flooding email
Most “send the EIR” threads are not document requests. They are trust requests: prove the unit hit your gate, under what condition, at what time.
A healthy empty-depot portal pattern:
- Gate In / Gate Out appear as events the party can open (timestamp, direction, unit ID)
- Digital EIR (or a scoped gate-proof view) is downloadable or viewable from that same unit timeline—when commercial rules allow
- No re-attach ritual for every line ask after the booth already captured the move
- Exceptions stay visible as exceptions—not silent “we’ll email later”
Gate queues belong with gate management software for depots. Machine handshake out: CODECO EDI for empty container depots. The portal’s job is human-readable proof on the same events—so the line desk skips the PDF chase.
Practical rule: if every EIR still starts as an email attachment after Gate In, the portal never owned proof—Outlook did.
Holds, Available, and M&R status lines actually ask for
Lines do not ask abstract “status.” They ask concrete releasability questions:
- Why is this unit blocked?
- Is it Available for my booking / programme today?
- Is repair still open—or is the estimate waiting on us?
- Who released it, and to which trucker / appointment?
Those answers must match container availability management and empty container hold and release—not invent a softer “portal Available” the booth will refuse. Portal language should reuse Hold / Available / Released, scoped hold reason, grade the party may see, and whether open M&R blocks leave.
The portal should not invent Available, clear holds, or rewrite FIFO. Those are depot OS authorities. The portal shows the outcome.
Practical rule: a portal Available that the booth will reject is worse than no portal—it teaches the line to book against fiction.
Soft check: pick the last three “where’s my box / send EIR / repair status?” emails from a line. If the answers lived in chat, a folder, and a nightly export—and the line could not open the same unit timeline themselves—you do not have an empty container depot client portal yet. You have status archaeology. See shared yard truth on containerhub.ai.
What not to expose (role-safe views)
Visibility without scope becomes a commercial incident. Role-safe views are part of the product, not a nice-to-have.
Keep out of the wrong login:
- Other lines’ units, programmes, and commercial holds
- Full yard map / stack plan when the buyer only needs unit status (expose positions only if contract allows)
- Internal clerk notes or unscoped billing packs
- Hold reasons confidential to another party
- Ability to edit inventory, clear holds, or force Available from outside depot authority
Line view ≠ trucker view ≠ depot admin. Scope by party, depot, and programme so the portal stays a visibility layer—not a leak.
Practical rule: if “client portal” means every authenticated user sees the whole yard, you built a second control room—not a portal.
How portal pairs with VBS / hold-release without becoming a second system
The failure mode is familiar: VBS in one tool, holds in a sheet, portal fed by export, gate in something else. By Thursday the four truths disagree.
Healthy pairing on one depot OS:
| Layer | Owns | Portal shows |
|---|---|---|
| Gate + EIR | Physical commit | Gate proof / EIR the party may open |
| Hold / release | Who can block and clear | Hold vs Available vs Released (+ scoped reason) |
| Availability rules | What Available must mean | Releasability the yard will honour |
| VBS / appointments | Slot + expected unit ask | Appointment state tied to the same unit |
| CODECO / EDI | Machine handshake out | Human-readable status that does not contradict EDI |
| Portal | Visibility for external roles | The above—not a fifth ledger |
Appointments: vehicle booking system for container depots. Release authority: empty container hold and release. The portal should consume those events—not become where clerks re-type status “for the customer.”
Practical rule: if updating the portal requires a second typing after Gate In or a hold clear, you already have two systems—one of them will lie first.
Soft CTA: shared yard truth for lines on containerhub.ai / demo or pricing
If the desk still answers line and trucker status from email archaeology—while the yard OS already knows Gate In, holds, Available, and M&R—the fix is not a louder mailbox. It is an empty container depot client portal: role-safe, live visibility on the same events the booth trusts.
ContainerHub is a depot / yard OS for 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, not a marine TOS pitch. Soft next step only: review the product, book a demo, or compare pricing. No directory ask.
Walk one unit in a demo. Ask whether the line (and trucker, if in scope) see Gate In, hold/Available, EIR proof, and open M&R from the same timeline the desk uses—without a nightly export between yard and portal.
