Carrier Onboarding Packet
A self-serve portal that collects a new carrier's W9, insurance certificate, MC/DOT authority, banking/remit details, and signed agreement, checks the packet for completeness, and routes it to compliance for approval before the carrier can ever be tendered a load.
A working onboarding portal where carriers upload their documents and details, the system flags anything missing, compliance reviews and approves the packet, and only then is the carrier marked active - with a full audit trail and a clean carrier-master CSV export.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account
- Your current carrier-master spreadsheet or export (for the no-API fallback)
The problem this kills
A new carrier wants to haul your freight. Someone emails them a packet, the carrier emails back a W9 here, an insurance certificate there, an MC number scribbled in the body of a message - and three weeks later half the file is still missing. Worse: a load gets tendered to a carrier whose insurance lapsed, whose operating authority was never verified, or who turns out to be a double-broker. Now you have cargo at risk and a claim you can't defend.
The root problem is that onboarding lives in inboxes and shared drives. There's no single place that knows whether a carrier's packet is actually complete, no enforced checklist, and no hard gate stopping an incomplete or risky carrier from being marked "active" and getting a load.
What you'll build
A self-serve carrier onboarding portal. You send a new carrier a secure intake link. They upload their documents - W9, certificate of insurance (COI), MC/DOT operating authority, signed carrier agreement - and fill in their company, contact, and banking/remit (including factoring) details. The tool checks the packet against the required-document checklist for that carrier type and flags anything missing or expired. A compliance reviewer sees the completed packet, approves or rejects it, and only an approved carrier gets set to "active" and becomes eligible to be tendered a load. The carrier gets a welcome email, and you can export a clean carrier-master CSV in the exact columns your TMS or system of record expects.
What's inside the Implementation Plan
- A copy-paste runbook you feed to an AI coding agent (Claude Code) - no prior coding needed.
- It opens by interviewing you about your business - your carrier types, the exact documents you require, the fields and naming you use (MC vs DOT vs SCAC), your approval rules, and your messy edge cases - so the tool is tailored to how you onboard carriers, not a generic template.
- Step-by-step build instructions, each ending in a ready-to-paste prompt.
- The data model, document checklist, completeness rules, and approval workflow.
- A "No API yet?" fallback: import your existing carrier-master spreadsheet and export a clean CSV in the columns your system expects - so you can ship this today with zero integration work.
The governance it includes (this is the point)
- Login so only your team can see and review carrier packets.
- Row-level security so each organization only ever sees its own carriers and documents.
- A complete audit trail - who uploaded what, who reviewed it, who approved, and exactly when.
- A hard human-in-the-loop approval gate - the tool checks completeness and drafts the recommendation, but a compliance person must review and approve before a carrier is ever set active.
- Duplicate guards keyed on MC or DOT number so the same carrier can't be onboarded twice or slip in under a new name.
Who it's for
Carrier compliance teams, procurement, and brokerage operations - anyone responsible for making sure a carrier is fully vetted and documented before a load ever moves.
You've got this - paste the first prompt and let the agent interview you.