ForzaOKB

Step 3.7 — Delivery and Status Change (Phase 3 → Phase 4 Handoff)

4 min read

Step 3.7 — Delivery and Status Change (Phase 3 → Phase 4 Handoff)

Previous step: Step 3.6 — In-Transit Monitoring Next phase: Phase 4 — Invoicing & Factoring

Note

This is the critical handoff from operational to accounting. Everything before delivery is Ops. Everything after delivery is Accounting. The quality of Phase 4 depends on what happens in the seconds and minutes after the driver departs the destination.

🎯 Ideal State

Trigger: Load delivers. Driver unloads, gets signed POD, departs the facility.

EZ Loader Status Change to “Delivered”

PathwayHow It Works
Automatic via Trucker-ToolsDriver departs destination geofence → Trucker Tools fires “Departed Destination” → EZ-Loader status auto-changes to “Delivered”
ManualJames or Jen marks the load “Delivered” in EZ-Loader

Either pathway triggers the same downstream automation:

What Happens Automatically at “Delivered” Status

1. Carrier ranking prompt. EZ-Loader prompts Ops to rank the carrier’s performance (1–5 stars). Takes seconds. Feeds Forza’s internal carrier performance database for future Step 3.2 capacity matching decisions.

2. POD/Invoice Request to carrier. EZ-Loader automatically sends an outbound request to the carrier (or their factoring company) for the POD and carrier invoice. Contains a link to an upload portal — documents drop directly into the EZ-Loader load record. Available for Step 4.1 audit.

3. Shipper delivery notification. If configured per Shipper (Step 3.5), an automated delivery notification is sent to the Shipper.

What Should Be True at the Moment of Delivery

  • Load record has all shipment details, both rates, all reference numbers, both rate confirmations signed and filed
  • Any in-transit accessorials from Step 3.6 have already been entered
  • Carrier has received the automated request for POD and invoice
  • Shipper has been notified of delivery (if configured)
  • Carrier ranking captured (or prompt is pending Ops action)

Owner: Trucker-Tools / Ops (status change). EZ-Loader (downstream automation). Carrier (document submission). Concetta (takes over at Phase 4).

🤖 SYSTEM AUTOMATION:

Status change can be fully automated via Trucker-Tools. All three downstream actions (carrier ranking prompt, POD/Invoice Request, Shipper notification) are EZ-Loader-automated at status change. If those automations aren’t configured, every one becomes a manual task for Concetta.

🛑 HARD GATE:

“Delivered” status is the operational boundary. Phase 4 begins at this moment. If the Phase 3 record is incomplete (missing rate con, unreconciled in-transit exceptions, no carrier ranking), Phase 4 starts with gaps that compound downstream.

📍 Current State

  • Delivered status change via Trucker-Tools geofence works when Trucker Tools is active.
  • Manual status change via EZ-Loader works.
  • Carrier ranking — adoption unclear, not confirmed as captured on every load.
  • POD/Invoice Request automation is NOT enabled. Tech stack meeting confirmed: “Not enabled, sounds nice… would be nice to trigger a POD reminder based on the geofencing notification.” Concetta manually chases carriers for POD and invoice after delivery.
  • Shipper delivery notification is ad hoc, not configured.

🚧 Gap

  1. POD/Invoice Request automation not enabled — highest-leverage Phase 3 improvement available. Activating it eliminates manual document-chasing for most loads and dramatically reduces time from delivery to invoicing.
  2. Carrier ranking adoption not confirmed. If Ops isn’t consistently ranking, Forza’s carrier performance database isn’t being built.
  3. Shipper delivery notifications are reactive, not automated.
  4. No documented Phase 3 → Phase 4 handoff protocol — when Ops closes the delivery, how does Concetta know to pick up?

🛠️ Gap Closure Actions

  • Activate POD/Invoice Request automation in EZ-Loader. Configure to fire on “Delivered” status, direct carrier to upload portal, auto-file documents into the load record. Owner: Casey + Concetta + EZ Loader support | Effort: Medium — highest priority
  • Document Forza-specific POD/Invoice Request email content, carrier-facing instructions, and reminder cadence for non-responders Owner: Casey + Concetta | Effort: Low
  • Make carrier ranking a documented requirement at delivery — Ops ranks every carrier on every load Owner: Casey + James | Effort: Policy
  • Configure Shipper delivery notifications per Shipper visibility preference (captured in Step 3.5 gap closure) Owner: Concetta | Effort: Low
  • Document the Phase 3 → Phase 4 handoff protocol — what Concetta checks at “Delivered” status before Phase 4 begins Owner: Casey + Concetta | Effort: Low

Graph View

Backlinks