A Depot Inspection and Handoff Workspace

A depot handoff is a chain of small decisions. A driver arrives with a unit. The gate records identity and time. An inspector notes damage. A repair estimate goes to an owner or lessor. Someone approves part of the work, rejects another line and asks for a second photo. A release desk later has to determine whether the unit can leave and which documents travel with it.

When those decisions live across email, chat, spreadsheets, camera rolls and a depot system, the weakest handoff controls the quality of the final record. An HNOR unit makes the gap easy to see. The equipment's non-operating reefer status needs to stay visible, but so do its identity, physical condition, machinery state, examination status, custody and approved next move. A depot inspection workspace could put that evidence on one timeline.

The customer and the first promise

The likely customer is a depot operator handling equipment for several owners, carriers or lessors. Other participants include gate staff, surveyors, repair estimators, maintenance technicians, owner representatives, trucking companies and release staff. Each participant needs a different slice of the record, and no participant should be able to rewrite the whole history.

The first product promise should be simple: every material handoff leaves a traceable event with an accountable source. The workspace does not need to replace the terminal operating system or billing platform on day one. It can begin as the condition-and-decision layer around gate-in, inspection, repair authorization and gate-out.

Start with an equipment journey, not a feature list

The design team should map one real unit from arrival through release. The map should identify what happens, who acts, what evidence is created, which decision follows and where an exception can stop the flow.

Gate-in

Capture the complete container number, visible size-and-type marking, delivering carrier, vehicle or visit reference, facility, gate lane, date, time and receiving user. Photograph the door end and any obvious handling concern before the unit moves deeper into the facility. If the record arrives with an HNOR label, retain the exact source value and system that supplied it.

UN/EDIFACT carries a dedicated CODECO gate-in and gate-out report message for exchanges involving depots, terminals and trading partners. A modern workspace should respect that existing event language instead of assigning a new meaning to gate-in.

Intake inspection

Assign an inspection scope and named inspector. The photo plan should cover structural members, fittings, doors, seals, floor, interior surfaces and machinery areas relevant to the owner's criteria. Each observed defect needs a component, location, description, image, severity or action category if the chosen criteria define one, and a way to state that the area could not be inspected.

Inspection criteria cannot be improvised from a generic checklist. The Institute of International Container Lessors publishes dedicated guides for container equipment, steel-container repair and refrigerated-container inspection and repair. An implementation should record which owner, lessor or applicable technical criteria governed the survey and which version was used. The software can enforce completeness, but qualified people still make the technical judgment.

Estimate and decision

Turn selected defects into proposed actions with labor, material, responsibility and supporting images. The owner representative should be able to approve, reject, defer or request more evidence at the line-item level. A changed estimate becomes a new version. It should not erase the amount, scope or comments that were previously reviewed.

For a non-operating reefer, machinery decisions require their own path. “Do not repair cooling function,” “isolate for safe handling,” “remove components,” and “no machinery work authorized” are different instructions. The workspace should never convert a commercial decision not to repair into proof that the system is empty, decommissioned or safe to open.

Work and verification

Record the technician or repair team, start and completion times, parts or materials where needed, after-work images and any variance from the approved line. A verifier can accept the completed item, reopen it or mark it outside the original scope. The application should make a rejected verification obvious rather than hiding it behind a green overall status.

Release and gate-out

Release requires more than a button. Confirm that the authorized party approved movement, required holds are clear, the pickup reference matches, the collecting party is identified and the unit's visible condition has not materially changed. The DCSA definition of gate-out treats it as complete when possession transfers from the controlled-area operator to the collecting entity. That is a useful event boundary, but it is not the same as cargo release, condition acceptance or repair approval. The workspace should keep those states separate.

What the record should contain

A practical data model can be organized into five linked records:

1. Equipment identity: container number, size-and-type code, owner or controlling party, equipment labels and source systems.
2. Facility visit: location, gate events, appointments, vehicle or movement references, custody state and holds.
3. Condition evidence: inspections, component observations, images, criteria, inspector and limitations.
4. Decision history: estimates, approvals, rejections, comments, exceptions, versions and responsible organizations.
5. Release package: completed work, unresolved items, final observations, authority, collecting party and exported evidence.

Files should not float independently from those records. A photo belongs to an event and observation. A PDF report belongs to an inspection version. A message belongs to a decision thread. The system should retain original uploads and display when a corrected record supersedes an earlier one.

Permissions matter as much as fields

Gate staff may create arrival records but should not approve repairs. Inspectors may add observations but should not alter the owner's commercial decision. Repair teams may mark authorized work complete but should not close a safety hold. An owner representative may approve cost while lacking authority to release equipment from the depot.

Role templates can help, but the workspace also needs organization boundaries and delegation records. If an approver is covering for a colleague, that authority should have a start and end date. If a third-party surveyor contributes a report, the depot should be able to share the necessary unit evidence without exposing unrelated customer inventory.

Retention and correction policies belong in the product specification. A user who fixes a transcription error should provide a reason and preserve the earlier value. A deleted image may need to remain in an audit record while disappearing from ordinary views. Legal retention periods and privacy rules vary, so the product needs configurable policy rather than a universal promise.

An illustrative handoff

Imagine a unit arriving at a depot with an HNOR status from the owner's equipment feed. Gate staff verify the container number and photograph the door end. The intake inspector finds a distorted lower rail, surface corrosion at two panels and an incomplete machinery-status note. The workspace stops the record from moving directly to “available.”

The surveyor uploads wider and close images, measures the observed distortion under the applicable criteria and asks for a qualified machinery review. The owner authorizes a structural repair but does not authorize restoration of cooling function. A technician documents the machinery condition and isolation steps within the assigned scope. The repair team completes the rail work, and a verifier accepts that line while leaving one cosmetic item unrepaired by agreement.

At pickup, the release user sees the current owner authorization, cleared structural hold, unresolved cosmetic observation, machinery note and collecting reference. The final package records what was inspected, what was done, what was excluded and when possession transferred. No one has to reconstruct the story from an inbox after the unit leaves.

How to reach the first users

Distribution can begin with a depot pilot rather than a broad software launch. Choose one facility, one owner account and one equipment journey that currently creates repeated follow-up. Import identity and visit data from the existing system, then let the new workspace own photos, decisions and the release evidence package.

An API or structured export can come after the team learns which events and fields are stable. DCSA's Track and Trace standard shows the value of common definitions for gate, pickup and drop-off events across stakeholders. A depot product can align with those definitions while remaining honest about the condition and repair data that sit outside movement tracking.

The first success measure is whether the depot, owner and collecting party can review the same unit history without a parallel message thread. Track missing evidence, decision turnaround, reopened items and release exceptions before adding forecasting or analytics.

The boundary of the product

The workspace would organize evidence and authority. It would not certify structural fitness, guarantee that an inspection found every defect or decide that a container is suitable for cargo or conversion. The IMO's CSC material keeps maintenance and periodic examination responsibilities with the owner under the applicable framework. Software should make those responsibilities visible, not blur them.

HNOR.com fits a product that treats status as the start of a workflow. The domain is short, specific and tied to equipment that often needs a careful second-hand record. The product earns its place by making each handoff clearer than the one before it.