Step 2.2 — Pre-Onboarding Carrier Vetting (Highway + Carrier 411)
Previous step: Step 2.1 — Carrier Identification Next step: Step 2.3 — Highway Carrier Onboarding
Note
Forza uses Highway as primary vetting engine — not SaferWatch (EZ Loader’s default). Highway’s vetting is more comprehensive and integrates into EZ-Loader via API.
🎯 Ideal State
Trigger: A carrier has been identified (Step 2.1) and Forza is considering dispatch or proactive network addition.
Highway Vetting Checks
Check What It Verifies Automation Identity verification Carrier is who they claim to be Automated by Highway Insurance monitoring Current cargo + liability coverage, policies not expired Automated — Highway pulls directly from insurer databases Compliance tracking FMCSA operating authority active, DOT# in good standing Automated by Highway Fraud / double-brokering detection Suspicious patterns, known fraud alerts Automated by Highway Observed equipment What equipment carrier actually operates Automated — Highway tracks historical load data Lane activity heatmap Whether carrier is actively running quoted lanes Automated by Highway Total broker connections How many brokers have worked with this carrier Automated by Highway Weekly load volume Carrier’s typical weekly volume Automated by Highway Equipment age Age of trucks/trailers — critical for reefer on produce loads Automated by Highway Supplementary Check — Carrier 411
Highway does not provide Freight Guard reports. Forza uses Carrier 411 for Freight Guard reports only. Data is not auto-synced — Ops manually reviews and notes concerns in the carrier record.
Risk Assessment Outcomes
Risk Classification Action Acceptable Proceed with onboarding Conditional James (Ops Manager) reviews case-by-case. Based on specific factors and load type. Unacceptable Do not onboard. Carrier does not enter Forza’s system. Owner: James, Jen run vetting checks. James (Ops Manager) makes judgment call on Conditional cases.
🤖 SYSTEM AUTOMATION:
Highway’s checks run automatically and continuously re-verify. Risk assessment is automated — human judgment applies only at Conditional-tier cases.
🛑 HARD GATE:
📍 Current State
- Highway is the active primary vetting tool, integrated with EZ-Loader via API — working correctly.
- Carrier 411 is used standalone for Freight Guard reports. Data does not flow into EZ-Loader or Highway automatically.
- Load Guard ($49/mo) is in Forza’s stack but neither James nor Concetta uses it. Candidate for cancellation — pending Nick (Founder/CEO) decision.
- SaferWatch is not in use despite being EZ-Loader’s default carrier monitoring integration.
- Load Lock Plus — Forza pays for this Highway feature but does not utilize it. Status in EZ-Loader integration unverified as of early March.
🚧 Gap
- Carrier 411 runs in parallel with Highway but is not integrated — creates a manual context-switch during vetting.
- Load Guard is being paid for but not used.
- Load Lock Plus is paid for but not utilized — need to verify whether it’s live in the EZ-Loader integration.
- No documented Ops Manager review protocol for Conditional risk assessments.
- No centralized record of Carrier 411 Freight Guard report findings preserved in the carrier profile.
🛠️ Gap Closure Actions
- Document the Ops Manager review protocol for Conditional risk assessments Owner: Casey + James | Effort: Low
- Establish a standard for preserving Carrier 411 Freight Guard findings in EZ-Loader carrier documents | Effort: Low
- Verify Load Lock Plus status in EZ-Loader integration — activate if live, track roadmap if not Owner: James + EZ Loader support + Highway support | Effort: Low
- Nick decision required: Cancel Load Guard subscription | Effort: Decision
- Evaluate whether Carrier 411 is still the right tool for Freight Guard reports or whether an integrated alternative exists Owner: Casey + James | Effort: Medium