CarrierShield is not a full carrier onboarding packet system. We don't handle W-9s, broker-carrier agreements, or banking. What we do handle is the insurance side of onboarding — capturing the carrier, collecting a current COI, and starting the renewal cycle the moment they're in your account.
This is the part of onboarding CarrierShield handles end-to-end.
Manually, or by importing a CSV/XLSX with name, MC number, insurance contact, and expiry. Concierge import is included if your spreadsheet is messy.
Send the carrier a tokenized upload link. No account, no password — they upload a PDF or photo from any device.
The expiry is extracted and presented as a suggestion. A broker confirms before the carrier's status becomes "active."
From day one, the carrier is on the 45/30/14/7-day reminder cadence — so the next renewal is captured before it expires.
Name, MC number, contact email for insurance follow-up, and current COI expiry — manually or in bulk.
Tokenized, single-purpose upload links. Mobile-first portal. No carrier account required.
Extracted expiry dates are reviewed by a broker user before they become authoritative.
Automatic enrollment in the renewal reminder cadence so the next cycle is already running.
Every onboarding action is logged: upload, review, approval, status change — with timestamp and actor.
Send us your spreadsheet. We'll clean it up, dedupe, and load your carriers so onboarding starts on real data.
We keep scope tight on purpose. Onboarding packets belong in a system designed for them.
Out of scope. Use your TMS, accounting system, or a dedicated W-9 collection tool.
Out of scope. Use an e-signature tool (DocuSign, PandaDoc, etc.) and store the executed agreement in your document system.
Out of scope. Banking and factoring details belong in your TMS or accounting platform with their own change-of-banking controls.
Out of scope. Use a dedicated FMCSA authority verification service before activating a carrier in your TMS.
Out of scope. See freight fraud prevention for the honest scope conversation.
Out of scope. On-time performance and claims history belong in your TMS or BI layer.
Capture the carrier, collect the COI, confirm the date, and start the renewal cycle — all from one workspace.