Check-in is the formal entry record of a unit into the yard: it validates that the appointment exists, that the driver is who they claim, that equipment is correct and in condition, and that the unit has an assigned next step with an owner. It is the first link of the shipment trip file, and the time logged there later defends (or loses) a detention dispute.

steps
5
areas
4
times (gate+dock)
2
ownerless queue
0

The typical problem is not lack of people but lack of flow: the queue has no owner because nobody created it on purpose.

Cluster: detention · release · audit.

Who validates what

Five steps, four areas, one record. Security, traffic, and warehouse in order.

Who validates what (and in what order)

Five steps, four areas, one record. Without timestamps it is not check-in.

StepOwnerValidatesRecords
1. ArrivalSecurityID / platesReal time
2. ApptTrafficSame-day appointmentOn time / late
3. EquipmentTraffic / warehouseType + sealSeal # + photo
4. ConditionWarehouseBox / temperatureExceptions
5. Next stepTrafficDock or holdInstruction to driver
Source · MX yard playbook

The ownerless queue

A unit without a next step enters limbo: detention, cascading appointments, and a full yard.

The ownerless queue

No unit crosses the gate without an assigned destination.

Select a step to see detail

Step detail · 01

Gate

Entry with destination

Gate logs arrival and gives instruction. Without destination, limbo starts here.
Even if the destination is “hold zone, stall 3, traffic will call”.
Yard operations with units in check-in and hold
If your gate does not log times, you have access control, not check-in.

Three early rejects

No appointment, wrong equipment, or incomplete documents: say no early.

Three early rejects that should hurt little

Saying no at the gate costs minutes; at the dock it costs the slot.

01

No appointment

Log arrival and reject or reschedule in writing.

02

Wrong equipment

Dirty or wrong box type: reschedule, do not load.

03

Incomplete docs

License or shipment papers: minutes at gate, hours at dock.

Source · MX check-in playbook

Gate vs dock time

Arrival, assignment, handling start/end, exit. Related: bottleneck, detention.

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. Arrival

    Gate

  2. Appt

    Validate

  3. Next

    Assign

  4. Log

    Defend

6–8 week pilot (check-in)

Latest detention bills: timeline reconstruction and % defendable. Goal: 100% of entries with arrival time and destination.

Elige un paso para ver el detalle

Detalle del paso · 01

Real arrival time

Real arrival time
Pilot checklist
Key takeaways5 points
  1. Check-in = appointment, identity, equipment, condition, and next step with an owner.
  2. Without logged times you have access control, not check-in.
  3. No unit crosses the gate without an assigned destination.
  4. Rejecting at the gate costs minutes; at the dock it costs the slot.
  5. The timeline defends (or loses) detention.

Do you pay detention you cannot dispute because the gate never logged the story?

Related reading

Frequently asked questions