Step 2.1 — Carrier Identification
Previous step: Step 1.11 — Greenlight Declaration Next step: Step 2.2 — Pre-Onboarding Carrier Vetting
🎯 Ideal State
A carrier enters Forza’s system through one of two sourcing modes. Regardless of the path, the full onboarding process applies — no shortcuts for urgency.
Load-Driven Sourcing — James or Jen has a load to cover and identifies a prospective carrier through one or more channels:
Sourcing Channel Role EZ-Loader freight matching System matches lane, equipment, and pickup date against carriers in Forza’s network DAT load board Primary load board for posting loads and receiving carrier responses Parade AI AI-powered capacity suggestions from truck-list emails and partner networks (activates at EZ-Loader go-live) Trucker-Tools Carrier responses from the Trucker Tools network Direct carrier outreach Ops calls or emails a carrier based on lane knowledge Relationship-Driven Sourcing — Ops or Sales wants to add a carrier to the network proactively. No immediate load, but Forza wants the carrier ready for future dispatch.
Owner: Operations (James, Jen) — identification and initiation of onboarding.
🛑 HARD GATE:
📍 Current State
- Carrier identification happens through multiple channels as described above — this part of the process works.
- Carriers are identified primarily by Ops (James and Jen).
- Pressure from load urgency does sometimes result in pushing carriers through onboarding faster than ideal. The process gate at Step 2.5 (activation) is what prevents dispatch before full onboarding, but it can be bypassed by admin-level users.
🚧 Gap
- No documented carrier sourcing priority or decision tree — no standard for which sourcing channel to check first for a given lane.
- Informal time-pressure workarounds to move carriers through onboarding faster than the process allows.
🛠️ Gap Closure Actions