ForzaOKB

Step 3.6 — In-Transit Monitoring and Exception Management

4 min read

Step 3.6 — In-Transit Monitoring and Exception Management

Previous step: Step 3.5 — Dispatch and Tracking Activation Next step: Step 3.7 — Delivery and Phase 4 Handoff

⚠️ The Fundamental Rule

If a financial change happens in transit, it gets entered into the EZ-Loader load accounting section immediately — not mentioned verbally, not written down for later, not remembered at invoicing. Reconstruction after the fact is how margin quietly disappears.

🎯 Ideal State

Trigger: Load in transit. Any deviation from the planned shipment creates an in-transit exception.

Common In-Transit Exceptions That Affect Accounting

Detention. Driver held at a facility beyond the free time window. Creates an accessorial charge — typically $50–75/hour after the free period. May be charged to the Shipper, absorbed by Forza, or split. Entered in EZ-Loader’s load accounting section immediately.

Layover. Driver cannot deliver on the scheduled date and waits overnight. Additional cost similar to detention. Entered as accessorial on the appropriate side.

TONU (Truck Ordered Not Used). Load cancels after carrier is dispatched or arrives at the facility. Carrier is owed compensation for time and fuel. Captured as a cost against the load even though no freight moved.

Rate adjustment. Load scope changes mid-transit — additional stop, weight differs, equipment change. Carrier rate, Shipper rate, or both may change. Must be reflected in EZ-Loader immediately.

Cargo claim. Freight damaged in transit. Financial impact (credit to Shipper, charge to carrier, insurance claim) must be flagged on the load even if the claim plays out over weeks.

The Financial Entry Discipline

For each in-transit exception, James or Jen capture two things in EZ-Loader:

ItemEntry
Operational recordWhat happened, when, facility, driver statement
Financial impactDollar amount, which side (Shipper/carrier/both), accessorial type, new total rate

Owner: James, Jen (Operations) — exception detection and financial entry. James (Ops Manager) — escalation on complex exceptions.

🤖 SYSTEM AUTOMATION:

Exception detection can be partially automated — Trucker-Tools tracking data showing a driver stationary at a facility for X hours can flag potential detention. Financial impact entry is human. The system should make entry easy and immediate.

🛑 HARD GATE:

A load cannot move through Phase 4 (invoicing) with unreconciled in-transit exceptions. If Ops and the carrier are disputing detention, the load’s carrier rate is unsettled — meaning the load’s margin is unsettled — meaning the Shipper invoice may need adjustment. Exceptions must be resolved or explicitly documented as pending before Phase 4 begins.

📍 Current State

  • Ops handles in-transit exceptions as they arise.
  • Financial impact entry timing is inconsistent — some exceptions captured in real time, some captured after-the-fact when Concetta asks about a discrepancy.
  • No documented standard for exception types or entry procedures.
  • Detention/layover rate standards not formally documented — Ops and carriers negotiate per-load.
  • Cargo claim process is informal — “James and Concetta have both been through a claims process. That is all the detail I have.”

🚧 Gap

  1. Timing discipline is not formal. Exceptions captured after-the-fact create margin erosion surfacing at Phase 5 reconciliation.
  2. No documented detention/layover rate standards — each load is a negotiation, creating inconsistency and harder Phase 4 audits.
  3. No documented cargo claim subprocess — deferred pending Forza claims experience capture. Gap remains open.
  4. No Ops Manager escalation threshold defined for significant in-transit changes.
  5. No real-time flagging mechanism for loads with open exceptions — not surfaced to Concetta for Phase 4 readiness.

🛠️ Gap Closure Actions

  • Establish “financial impact entered in EZ-Loader immediately” policy as non-negotiable for Ops Owner: Casey + James | Effort: Policy
  • Document standard detention/layover/TONU rates as starting points for Ops negotiations Owner: Casey + James + Nick | Effort: Low
  • Capture Forza’s existing cargo claim experience (James + Concetta) and draft the Forza-specific cargo claim subprocess Owner: Casey + James + Concetta | Effort: Medium
  • Define Ops Manager escalation threshold — rate adjustments above $X require James review Owner: Casey + James | Effort: Policy
  • Establish an “open exception” flag visible in the EZ-Loader load record that signals Phase 4 readiness Owner: Casey + Concetta + EZ Loader config | Effort: Medium

Graph View

Backlinks