
Exception Management for Container Depots: A Practical Guide
Exception management at a container depot means catching every deviation from the planned move, giving it one owner and one deadline, and closing it with a record that holds up in a dispute. It works when the exception is captured where it happens (the gate, the yard, the repair bay) in a system everyone shares, instead of on paper, radio and phone calls. That is why we built ContainerHub around digital gate, inspection, repair and billing records that sit in one platform.
TL;DR
- An exception is a condition that threatens the planned move and needs a decision. A routine event is not an exception.
- Most depot exceptions start at the gate: document mismatches, invalid transactions, unresolved tickets, damage, hazmat and reefer issues.
- Every exception needs a category, an owner, a deadline, evidence and a documented close. Without all five it comes back.
- Exception reporting is the second half of the job: count backlog, age and repeat causes, and fix the cause instead of the ticket.
- Digitizing gate, inspection, repair and billing in one platform keeps the evidence attached to the exception from the first scan to the invoice.
Table of Contents
- What exception management means at a depot
- The exceptions depots see most often
- How to run an exception from first flag to close
- Deadlines, escalation and who gets told
- Write the exception policy before you need it
- Exception reporting: turn closed tickets into fewer tickets
- Preventing exceptions and cutting manual rework
- Where ContainerHub fits
- Our perspective
- FAQ
- Sources
What exception management means at a depot
A depot runs on a plan: a container is booked, arrives, is inspected, is stored, is repaired if needed and leaves on a release. Anything that breaks that plan is a candidate exception. The key word is candidate. A truck arriving on schedule with matching paperwork is routine. A truck arriving with a booking number that does not match the equipment inventory is an exception, because someone must decide what happens next.
That distinction matters because a team that treats every event as urgent stops responding to any of them. A workable definition has three parts:
- Detection. A rule, a check or a person notices the deviation.
- Ownership. One named role is responsible for the next action.
- Closure. The condition is cleared and the record shows who acted, when and with what evidence.
Exception reporting is what you do with the closed records afterward. Management handles today’s problem. Reporting tells you why the same problem keeps arriving.
The exceptions depots see most often
Public port documents are a good guide, because they spell out what a gate has to catch. The North Carolina State Ports Authority’s Container Operations Manual describes an inbound gate application that checks transaction details against bookings, bills of lading, regulatory status and equipment inventory, with automated edit checks that flag discrepancies. From that manual and similar gate procedures, the recurring categories are:
| Category | Typical trigger | First decision |
|---|---|---|
| Document or booking mismatch | Booking, container number or line does not match the transaction | Correct, reject or hold |
| Invalid transaction details | Missing or wrong data on the gate ticket | Return to the driver or the customer for correction |
| Unresolved gate ticket | Driver cannot complete the transaction at the lane | Route to a trouble lane or office |
| Container damage | Exterior or structural damage seen at interchange | Record, photograph, assign for estimate |
| Oversize or hazardous cargo | Unit does not fit standard handling or carries hazmat | Special placement and verification |
| Reefer temperature mismatch | Setpoint or reading differs from the booking | Notify the owner and correct |
The same manual says oversized containers are sent to a trouble office, and hazardous containers are checked against booking information and a safety data sheet (MSDS) before they are placed in the yard. In other words, the exception has a defined route before it happens. That is the first rule of good exception management: decide the route in advance.
How to run an exception from first flag to close
A depot that handles exceptions well follows the same lifecycle every time, whatever the cause.
1. Identify
Detection should happen at the earliest possible point. Automated checks at the gate beat a clerk spotting the problem in the yard two days later. The NCSPA manual’s edit checks are the model: compare what the driver says against the booking, the bill of lading and the inventory, and flag the difference immediately.
Where it goes wrong: checks that live in a spreadsheet or in one clerk’s memory. When that clerk is off shift, the exception passes through unflagged and surfaces later as a billing dispute.
2. Document
Capture the evidence at the moment of the event. For damage, that means the Equipment Interchange Receipt (EIR), the record that describes a container’s condition when it changes hands. The NCSPA manual says gate clerks record exterior damage on the electronic EIR, which creates a traceable inspection record at interchange.
The record carries real weight. Under the Uniform Intermodal Interchange and Facilities Access Agreement (UIIA), EIRs describe observable damage, and condition can be recorded in the EIR or in images taken at interchange. A UIIA panel has ruled for a motor carrier where the ingate EIR did not record the damage. If your record is silent, you may be the one paying. For a deeper look at the document itself, see our guide to container equipment interchange.
Where it goes wrong: photos taken on a personal phone and never attached to the transaction, or notes written on a paper ticket that is later lost.
3. Assign
Every exception needs one owner. Not a department, a role: the gate supervisor, the yard planner, the repair estimator, the billing clerk. Port Houston’s Bayport gate process guide shows the principle in action. Drivers with trouble tickets are sent to a trouble lane and a customer-service kiosk, so the people who can resolve the problem handle it, and the main lanes keep moving.
Where it goes wrong: a shared inbox that everyone can see and no one owns.
4. Investigate and decide
The owner gathers the linked evidence (gate ticket, booking, photos, inspection notes) and makes the call: correct, reject, hold, repair or escalate. Port Houston’s guide shows the outcome logic. A coordinator prints an outbound EIR if all outbound equipment matches the original transaction. If the trouble transaction stays unresolved, it goes to the exit or reject gate for ticket cancellation. Both paths are defined, and both end with a record.
5. Resolve and close
Closing means more than clearing the flag. The record should show what the condition was, what was done, who did it and when. Where a repair is involved, the paperwork has its own rules. The Association of American Railroads Intermodal Checklist says a repair record must be prepared whenever repairs of any kind are made. It also says a foreign-unit repair record is made in detail at the unit and signed. A copy goes to the ramp office daily, and local supervision keeps it for at least seven days to compare with the final invoice and the work performed.
That last point is the closing test in miniature: the exception is closed when the repair record, the work and the invoice agree.
6. Reopen if the risk returns
A closed exception that recurs should reopen the same record, not start a new one. That is how you see the pattern later.
Deadlines, escalation and who gets told
Two kinds of clocks apply to exceptions: yours and your counterparties’.
Your own clocks. BNSF’s Hub Operations Manual offers a useful template for a corrective process. A regional director contacts the service partner about reported non-compliance within 48 hours and records the notification date, the person and the method until the issue is corrected. For problems that cannot be fixed immediately, an action plan is developed as soon as possible and no later than 14 days after discovery, naming deficiencies, responsible parties, actions, timelines and written progress reports. The pattern is worth borrowing for any depot: notify fast, plan within a fixed window, report progress until closed.
Your counterparties’ clocks. Damage reporting windows are set by the parties you deal with. Norfolk Southern’s Intermodal Rules Circular (revised August 20, 2024) says that, to be considered for damage reimbursement, damage must be reported prior to outgate, or within 14 days of outgate if it was not physically identifiable earlier. Its damage notification includes a description, the damage location terminal, photos, the unit initials and number, and the date and time noted. A copy is required when filing an intermodal equipment damage claim. Always check the current rules circular of the railroad or line you are dealing with, because these terms are revised.
A practical escalation ladder for a depot:
- Level 1, at the gate: the clerk resolves routine corrections on the spot.
- Level 2, supervisor: unresolved tickets, damage disputes and hazmat questions.
- Level 3, customer or shipping line: anything that changes a release, a repair approval or a billing term. Send the evidence with the message, not after it.
Escalate when a deadline is about to be missed or ownership has stalled, not on every event. A system that repeats the same warning every hour teaches people to ignore it.
Write the exception policy before you need it
A short written policy keeps the lifecycle consistent across shifts and sites. It should define:
- The categories of exception your depot recognizes (start with the six in the table above).
- The detection point for each: gate check, inspection, yard audit, billing review.
- The owner role for each category and a backup.
- Required evidence before an exception can close: photos, EIR, ticket, booking reference.
- Time limits for first response, plan and closure.
- Who must be notified outside the depot, and by what method.
- Close and reopen rules, including who may close.
Keep it to a page. A policy nobody reads at the gate is not a policy.
Exception reporting: turn closed tickets into fewer tickets
Once exceptions are captured consistently, reporting becomes possible. Four measures are enough to start:
- Open backlog by category. How many exceptions are open right now, and of what kind.
- Age of open exceptions. The oldest items, because they are the ones that turn into disputes and storage arguments.
- Time to first action and time to close. Measure by category and by owner role, not by person.
- Recurring causes. Group closed exceptions by root cause: a particular customer’s paperwork, a particular lane, a particular shift, a particular type of damage.
The last one is where the value is. If 30 percent of your document mismatches trace to the same booking source, the fix is upstream, not at the gate. Capturing a root cause on each closed record is a habit that costs seconds and pays back every month.
A worked example
Suppose a depot logs 120 exceptions in a month. Sorting by category shows 45 are booking mismatches, 30 are damage disputes, 20 are unresolved gate tickets and 25 are everything else. The 45 mismatches, grouped by customer, show that three customers account for 28 of them. A call to those three customers about booking references removes more than a fifth of the month’s exceptions without touching the gate. The numbers here are illustrative, but the method is the one to use on your own data.
Preventing exceptions and cutting manual rework
The cheapest exception is the one that never opens. Four levers do most of the work:
- Validate before arrival. Gate queues and unplanned arrivals create errors. Pre-arrival appointments and data checks move the problem away from the lane. Our guide to a vehicle booking system for container depots covers how this cuts gate queues.
- Standardize inspection. When every inspector records damage the same way, with photos and consistent codes, disputes shrink. See how container damage inspection can be structured around that idea.
- Connect the billing record to the evidence. Many disputes are billing disputes in disguise: storage clocks, repair charges and tariffs argued after the fact. Invoices that cite the gate record and repair record settle faster. We cover this in our piece on empty container depot billing.
- Remove double entry. Every time data is re-keyed from paper into a system, a new mismatch becomes possible. Capture once, at the source.
Where ContainerHub fits
Exceptions are hardest to manage when the evidence is spread across the gate, the yard, the repair shop and the billing office. ContainerHub is a cloud platform for empty container depots that brings those pieces together: digital gate-in and gate-out, yard management, AI-assisted damage inspection, repair workflows, billing, EDI links with shipping line systems and a client portal where customers can see their own status. Because the records live in one place, the photo, the EIR, the repair approval and the invoice belong to the same container history instead of four separate files.
Plans are published on our pricing page: Free at 0 USD per month, Starter at 199 USD per month, Growth at 499 USD per month and Enterprise from 999 USD per month. Depots handling gate traffic can start with gate management software for depots, and yards can look at our container yard management software.
If you want to see how a gate, inspection or repair exception would run through your own depot, start at containerhub.ai.
Our perspective
Most depots do not have an exception problem. They have a visibility problem. The exception happens at the gate on Tuesday, the evidence sits in a phone, the repair estimate sits in an email, and the dispute lands on the billing desk two weeks later. By then nobody can reconstruct what happened.
We built ContainerHub on the belief that the gate, yard, inspection, repair, billing and client portal should be one system with configurable workflows, so that an exception carries its evidence with it from the first scan to the final invoice. Our Agentic AI copilot is there to help the team work through the routine so people spend their time on the decisions that need them.
Our advice to any depot operator: define your categories, name an owner for each, require evidence before closing, and review your recurring causes monthly. Do that on a platform where the record is shared with your customers and shipping lines, and exceptions stop being arguments and become routine work.
William Carley
FAQ
What is exception management in a container depot?
It is the practice of identifying, assigning, resolving and documenting anything that deviates from the planned container move, such as a booking mismatch, damage or an unresolved gate ticket. The goal is a closed record showing who acted and when, so the depot can defend its decisions later.
What is the difference between exception management and exception reporting?
Exception management handles each deviation as it happens. Exception reporting looks across many closed exceptions to show backlog, age, time to close and recurring causes. Management solves today’s problem, and reporting reduces tomorrow’s.
What should an exception policy include?
It should list your exception categories, the owner role for each, the evidence needed to close, response and closure time limits, who must be notified outside the depot, and the rules for closing and reopening. One page is enough if the gate and yard teams actually use it.
How fast should a depot report container damage?
It depends on the counterparty’s rules. For example, Norfolk Southern’s Intermodal Rules Circular requires damage to be reported before outgate, or within 14 days of outgate if it was not physically identifiable earlier, to be considered for reimbursement. Record damage at interchange with photos so you can meet whichever window applies.
Sources
- North Carolina State Ports Authority, Container Operations Manual (2021)
- Port Houston, Bayport Container Terminal Gate Process (2017)
- Uniform Intermodal Interchange and Facilities Access Agreement, Exhibit B
- Association of American Railroads, Intermodal Checklist
- BNSF, Hub Operations Manual
- Norfolk Southern, Intermodal Rules Circular (revised August 20, 2024)