ForzaOKB

Step 2.3 — Highway Carrier Onboarding and Push to EZ Loader

3 min read

Step 2.3 — Highway Carrier Onboarding and Push to EZ Loader

Previous step: Step 2.2 — Pre-Onboarding Carrier Vetting Next step: Step 2.4 — Carrier Accounting Details Verification

🎯 Ideal State

Trigger: Carrier has passed Highway vetting (Step 2.2).

Highway owns the carrier-facing onboarding flow. Forza does not use EZ-Loader’s native digital carrier onboarding webform. The carrier completes Highway’s onboarding packet and Highway pushes the completed profile into EZ-Loader via API.

What Highway Collects During Onboarding

Data CategoryFields
IdentityCarrier legal name, MC#, DOT#, physical address, primary contact (name, email, phone)
InsuranceCargo + liability coverage, policy numbers, expiration dates, certificates of insurance
AuthorityFMCSA operating authority status, authority documents
EquipmentEquipment types operated, observed equipment from Highway’s historical tracking
ComplianceSafety rating, CSA scores, risk assessment
Carrier AgreementDigitally signed Forza carrier agreement

The Highway → EZ Loader Push

Once the carrier completes Highway’s onboarding, Highway’s API pushes the completed carrier profile into EZ-Loader. Accounting’s role is review-only — not creation. Highway handles data entry.

Owner: Highway (carrier-facing onboarding). Concetta (downstream review in EZ-Loader).

🤖 SYSTEM AUTOMATION:

Largely automated. The carrier self-enters data in Highway, uploads documents, e-signs the agreement, and Highway’s API pushes everything into EZ-Loader. Concetta’s role is review, not data entry.

🛑 HARD GATE:

An EZ-Loader carrier profile that arrived via Highway push is in a pre-active state. It cannot be assigned to loads until Concetta (Accounting) reviews and activates it at Step 2.5.

📍 Current State

  • Highway is the active carrier onboarding engine — integration working and used as default path.
  • Exact field mapping from Highway to EZ-Loader is not fully documented from Forza’s side.
  • Concetta receives the EZ-Loader carrier profile after Highway pushes it and reviews for completeness at Step 2.5.

Who does this today: Highway (onboarding engine). James, Jen (initiating Highway onboarding). Concetta (downstream review).

🚧 Gap

  1. Highway-to-EZ-Loader field mapping not documented from Forza’s side.
  2. Unclear whether Highway collects all required accounting details (factoring company, NOA, W-9, payee info) or whether Concetta must capture these separately.
  3. No documented process for re-running Highway onboarding for a carrier whose profile needs updating (e.g., insurance expired, factoring company changed).

⚠️ Open Verification Question

Does Highway’s onboarding packet collect: accounting contact name/email/phone, payment method (self-invoicing vs. factoring), factoring company name and contact info, carrier’s NOA, W-9, and bank info for ACH? If not, Concetta (Accounting) must capture these gaps at Step 2.4.

🛠️ Gap Closure Actions

  • Document Highway-to-EZ-Loader field mapping with Highway support team Owner: Casey + James + Highway support | Effort: Medium
  • Identify specific fields Concetta must capture separately if Highway does not collect them (factoring company info, NOA, W-9) Owner: Casey + Concetta + James | Effort: Low
  • Document the process for re-running or updating Highway onboarding for existing carriers Owner: Casey + James + Highway support | Effort: Low
  • Establish standard for when Forza initiates Highway onboarding for a carrier vs. when the carrier self-initiates | Effort: Low

Graph View

Backlinks