Every freight brokerage has a carrier packet. It is usually a stack of PDFs emailed back and forth, a Docusign envelope assembled manually, or - in the worst case - a physical folder mailed to the carrier. The process looks like this: someone adds a new carrier to the TMS, someone else remembers to pull the carrier packet template, fills it in, emails it, waits for it to come back, checks the signatures, uploads it to a shared drive, then manually flips the carrier to "active" status. Maybe two days pass. Maybe five.
At five carriers a week that is manageable. At twenty carriers a week you have a dedicated person doing nothing but carrier onboarding. At fifty carriers a week - which a growing brokerage can easily hit during a capacity crunch - the manual process collapses entirely.
This guide covers what belongs in a carrier packet, how to calculate the real cost of doing it manually, and how to design an automated workflow that handles the entire sequence from carrier creation to active status without human intervention.
A carrier packet is actually two different things depending on context: an onboarding packet and a load-specific carrier packet. These are often confused, and conflating them causes process problems.
This is the set of documents collected once when a new carrier is added to your network. It establishes the legal and compliance relationship:
This is generated per shipment and sent to the driver or carrier dispatcher for each load. It contains:
The onboarding packet is signed once and filed. The load packet is generated per load, often dozens of times per day. For guidance on what rate confirmations should contain and common broker mistakes, see our post on rate confirmation best practices for freight brokers.
The $15-30 per carrier onboarding estimate is not hyperbole - it is what the math produces when you account for actual time spent. Consider the sequence of tasks:
At 20-25 minutes of actual labor per carrier, and a fully-loaded labor cost of $35-45/hour for an operations coordinator, you land at $12-19 per carrier just in labor. Add in e-signature platform costs ($0.50-2.00 per envelope for DocuSign at standard pricing), document storage, and the cost of errors - wrong insurance dates let through, missing W-9s, unsigned agreement pages - and $15-30 is conservative.
Multiply by carrier churn: many brokerages turn over 20-30% of their carrier pool annually. A brokerage with 500 active carriers is onboarding 100-150 new carriers per year. That is $1,500-4,500 in direct cost, before accounting for the opportunity cost of the time spent.
The automated carrier onboarding workflow has six stages. Each stage has a clear trigger, action, and exit condition:
The workflow starts when a new carrier record is created in your TMS with a status of "pending onboarding." Most TMS platforms support webhooks on record creation events. Configure a webhook to fire to your document automation service when carrier.status == "pending". The webhook payload should include the carrier's MC number, DOT number, company name, dispatcher contact email, and any data already collected during the carrier sourcing process.
// Example webhook payload from TMS carrier creation event
{
"event": "carrier.created",
"timestamp": "2026-03-24T09:14:22Z",
"carrier": {
"id": "CAR-00441",
"mc_number": "MC-884221",
"dot_number": "3041882",
"company": "Lakewood Transport LLC",
"dispatcher_name": "Marcus Webb",
"dispatcher_email": "dispatch@lakewoodtransport.com",
"dispatcher_phone": "614-555-0881",
"status": "pending_onboarding"
}
}On receipt of the webhook, call your document generation API to produce the carrier packet. This is where the ROI lives: a task that took 10 minutes manually completes in under 3 seconds. The generated packet is a single PDF combining all documents with pre-filled fields (carrier name, MC/DOT numbers, your brokerage's contact information, current date, insurance minimums).
The W-9 and direct deposit form are left blank for carrier completion - you cannot pre-fill banking information for a new carrier. Everything else - the carrier-broker agreement, the accessorial schedule, the COI requirements notice - can be fully templated and pre-populated.
Push the generated packet into DocuSign or HelloSign (now Dropbox Sign) via their API. Configure the signing workflow to route to the carrier's dispatcher email with specific signing tabs on: the carrier-broker agreement signature line, the operating authority acknowledgment, and the W-9/direct deposit fields.
DocuSign integration tip: Use DocuSign's "embedded signing" feature for the W-9 and direct deposit fields rather than free-form text fields. Embedded signing walks the signer through each required field in sequence, significantly reducing incomplete returns.
Set a reminder sequence: one reminder at 48 hours if unsigned, another at 96 hours, and escalate to your carrier relations team at 7 days. Automated reminders eliminate the follow-up labor that eats most of the manual onboarding time.
Configure DocuSign/HelloSign webhooks to fire back to your system when the envelope status changes. When all parties have signed (envelope.status == "completed"), the workflow advances automatically.
Retrieve the completed signed PDF via the e-signature platform API and store it in your document management system. At this stage, run automated validation checks:
Flag incomplete submissions for human review rather than letting them pass silently.
On successful validation, call your TMS API to update the carrier status from "pending_onboarding" to "active." The carrier is now available for load tendering. The entire sequence - from carrier creation to active status - can complete in under 24 hours with no human involvement if the carrier signs promptly.
Broker regulations under 49 CFR Part 371 require brokers to maintain records of each freight transaction for a minimum of three years. For carrier relationships specifically, you must be able to produce: evidence that the carrier held valid operating authority at the time of each load, proof of insurance on file at the time of each load, and the signed carrier-broker agreement.
The FMCSA minimum insurance requirements are $1,000,000 auto liability and $100,000 cargo insurance for most freight types. Household goods carriers have different requirements. Hazmat carriers require additional insurance minimums. Your onboarding packet's COI requirements section should specify these minimums and require the carrier's insurer to list your brokerage as a certificate holder so you receive cancellation notices automatically.
Insurance expiration monitoring is a compliance gap most brokerages ignore. Collecting a COI at onboarding is not enough - you need to monitor for expiration and flag carriers whose insurance is about to lapse. Build expiration date extraction into your onboarding workflow and set calendar alerts at 60 and 30 days before expiration.
Carrier fraud - specifically double-brokering and fictitious pickup schemes - has increased significantly as freight volumes have grown. The common thread in most fraud cases is that the compromised brokerage had weak carrier vetting processes that were bypassed because they were manual and time-consuming.
Automated carrier onboarding reduces fraud risk in several concrete ways. First, it enforces a consistent vetting checklist on every carrier, every time - there is no "we were busy and skipped the FMCSA check" because the check is automated. Second, it creates a timestamped audit trail proving due diligence for each carrier. Third, by making the compliant path the easiest path, it reduces the temptation to approve carriers informally and "do the paperwork later."
Integrate an FMCSA SAFER Web API check into Stage 2 of your workflow. Before generating the packet, query the SAFER Web API with the carrier's MC and DOT numbers to confirm: operating authority is active, the entity type matches what the carrier claimed, and there are no pending revocation actions. Reject the onboarding workflow automatically if any check fails and flag it for manual review.
For a comprehensive checklist of every document and verification step in the carrier onboarding process, see our detailed post on carrier onboarding documents: the complete freight broker checklist.
Full automation is the goal, but some elements of carrier onboarding benefit from human judgment:
Build an exception queue in your workflow that routes flagged carriers to a human reviewer with all the relevant data pre-fetched and displayed. The reviewer should be making a judgment call, not spending time gathering information - the automation handles the research, the human makes the decision.
Most enterprise TMS platforms (McLeod Software, MercuryGate, Aljex/Revenova) support outbound webhooks on carrier creation events. Smaller or custom-built TMS implementations may require polling an API endpoint instead. If your TMS does not support webhooks, set up a scheduled job that queries for carriers with status == "pending_onboarding" every 15 minutes and triggers the packet generation workflow for any new records.
For the return path - updating carrier status after packet completion - most TMS platforms have an inbound API for record updates. If yours does not, a database direct-write (with appropriate access controls) is an acceptable alternative for internal systems.
The architecture should be: TMS owns the carrier record and status, the document automation service handles packet generation and e-signature orchestration, and the e-signature platform handles the actual signing ceremony. Each system does one thing well and communicates via webhooks. Avoid building a monolithic onboarding system that tries to replicate TMS functionality - it will become a maintenance burden.
Ready to stop manually assembling carrier packets? FreightDoc's API handles carrier packet generation, BOL creation, rate confirmations, and full document workflow automation in a single integration.
FreightDoc generates BOL, rate confirmations, carrier packets, and customs docs via API - in under 2 seconds.
Join the Waitlist