Step 3.1 — Load Creation in EZ Loader
Previous phase: Phase 2 — Carrier Onboarding Next step: Step 3.2 — Carrier Assignment
Note
🎯 Ideal State
Trigger: A greenlit Shipper has freight to move and a rate has been agreed upon by Sales or Ops.
Prerequisites Before a Load Can Be Created
EZ-Loader blocks load creation if either condition fails — this is a system gate, not a judgment call.
Prerequisite What EZ Loader Checks Shipper status Must be “Customer” (Phase 1 greenlight complete) — not “Onboarding Sent” or “Onboarding Signed” Available credit Shipper’s credit limit minus outstanding unbilled/unpaid loads must be ≥ Shipper rate for this load Data Entered at Load Creation
Shipper and rate:
Field Notes Shipper name Selected from active Shipper profiles (status = “Customer”) Shipper rate Total amount the Shipper will be invoiced Rate type Flat rate, per mile, per unit, etc. Accessorial charges Any additional charges on the Shipper side Shipment details:
Field Notes Origin / Destination Facility name, address, city, state, zip, contact name, contact phone Pickup / Delivery date and time Or appointment window Equipment type required Dry van, reefer, flatbed, step deck, etc. Commodity Affects insurance and handling requirements Weight Total shipment weight Temperature requirements If reefer — target temperature and acceptable range. Critical for produce loads. Special instructions Driver requirements, loading/unloading, PPE, pre-cooling standards Reference numbers:
🤖 SYSTEM AUTOMATION:
EZ-Loader auto-populates from the Shipper profile: default Sales rep, GP split, billing requirements, saved facility locations. Reference number fields are enforced based on the Shipper’s Step 1.6 configuration — if the Shipper requires a PO#, EZ-Loader requires it at load build, not at invoicing. Parade AI (activates at EZ Loader go-live) provides carrier capacity suggestions.
🛑 HARD GATE:
📍 Current State
- Load creation happens in MVMNT today — will migrate to EZ-Loader at May go-live.
- Shipper invoice document requirements and reference number enforcement are NOT configured per Shipper in EZ-Loader or MVMNT. Missing references are caught at invoicing, creating rework.
- Parade AI not yet live in EZ-Loader (can’t run on two TMS simultaneously) — activates at go-live.
- Load building is handled by James, Jen — working operationally.
🚧 Gap
- Reference number enforcement at load build is not configured — same root gap as Step 1.6. Loads can be built without Shipper-required references, creating downstream invoicing rework.
- Load building happens in MVMNT during transition; cutover to EZ-Loader pending go-live.
- No Forza-specific load-building SOP documented for reefer/produce loads with max equipment age or pre-cooling requirements.
🛠️ Gap Closure Actions
- Configure Shipper-specific reference number and document requirements in EZ-Loader — same action as Step 1.6 Gap Closure #2 Owner: Concetta | Dependency: Step 1.6 inventory built + EZ Loader live | Effort: Medium
- Document Forza’s load-building SOP with reefer/produce-specific requirements (pre-cooling, max equipment age, temperature range capture) Owner: Casey + James | Effort: Low
- Verify EZ-Loader’s saved facility locations are accurate for repeat Shipper origins/destinations before go-live | Effort: Low