Release is the last validation before a loaded unit leaves your site. It is the point of no return: an error caught before the gate is fixed in minutes on your yard; the same error after is fixed with a return, detention, customer rejection, or a customs problem.

min
5–10
checks
5
signers
4
point of no return
1

Release is not a security formality: it is a witnessed custody handoff.

Cluster: check-in · Carta Porte · DODA.

Checklist by owner

Warehouse, traffic, security, and driver each sign their part. The gate does not replace the dock.

Checklist by owner

Release is a witnessed custody handoff, not a gate formality.

ChecksOwnerConfirms
CargoWarehouseReference, count, stow
UnitTrafficPlates vs Carta Porte
DocumentsTrafficInvoice, CP, remittance, customs
SealSecurity + driverNumber + photo
RouteTraffic + driverDest, appointment, contact
Source · MX release playbook

Three discrepancies that cost after

Seal ≠ paper, crossed documents, and a driver without briefing.

Three discrepancies that cost after the gate

Every error that crosses the gate multiplies.

01

Seal ≠ paper

One transposed digit turns a normal delivery into a rejection.

02

Crossed docs

Plates or quantities that do not match each other.

03

No briefing

“He already knows” is the root cause of the wrong door.

Source · MX outbound playbook
Loading dock with a unit ready to leave
An error caught before the gate is fixed in minutes; afterward it multiplies.

Why the driver also signs

By signing, the driver accepts custody of unit, cargo, seal, and documents in the recorded condition.

Why the driver also signs

By signing they accept custody of unit, cargo, seal, and documents.

Select a step to see detail

Step detail · 01

Check

Cargo and seal

Driver witnesses visible count and photographed seal number.
Without an exit signature, “that’s how I got it” and “that’s how it left” are worth the same: nothing.

How long it should take

If release takes 40 minutes, push work upstream. Related: custody, DODA, Carta Porte.

What OCL runs

OCL Cargo is an autonomous TMS with agents and computer use (operating screens and portals like an analyst). It builds the trip file per shipment, cross-checks evidence, and leaves exceptions to humans. It coexists without a day-one TMS migration. OCL can stamp invoice and Carta Porte. On the Mexico–US corridor, the value is closing the trip file before paying.

Trip file

Flow control

  1. Cargo

    Confirm

  2. Docs

    Match

  3. Seal

    Photo

  4. Sign

    Gate

6–8 week pilot (release)

Rejects and returns this quarter: how many would have stopped at the gate. Goal: signed checklist on 100% of loaded exits.

Elige un paso para ver el detalle

Detalle del paso · 01

Final count vs shipping document

Final count vs shipping document
Pilot checklist
Key takeaways5 points
  1. Release = last validation before the point of no return.
  2. Cargo, unit, documents, seal, and route: five confirmations.
  3. Any of the four signers can stop the exit.
  4. A photographed seal disarms the “broken seal” dispute.
  5. Without the driver’s signature, “that’s how I got it” equals “that’s how it left”: nothing.

How many rejects last quarter died at the exit?

Related reading

Frequently asked questions