Research 2026
Carrier Onboarding Time: A Measurement Design
A measurement design for carrier onboarding that separates document collection, verification, and activation.
Published October 22, 2026.
Research question: How long does carrier onboarding take from first document request to first dispatch, and which stage creates the delay?
Method and evidence scope
This paper is a measurement design. The unit is a carrier onboarding case. The start event is the first document request sent after a complete carrier application. The end event is the first load dispatched, not the date the carrier was approved. The design separates document collection, verification, and activation. Cases still open at the cut-off are reported by stage and age. Sources on carrier registration and freight operations provide context, not a benchmark.
Table of contents
- Why activation is the end event
- The three stages
- Document completeness rules
- Open cases and withdrawals
- Stratify by source and document type
- Reporting and limits
- What the stage report should show
- Limits and comparison
Why activation is the end event
A carrier can be approved and still unable to haul because the insurance certificate expired or the agreement was not signed. Ending the clock at approval hides the operational delay. Ending at first dispatch captures the outcome the business cares about. Record the approval date separately so the two stages can be compared.
The three stages
Collection runs from the first request to receipt of all required items. Verification runs from receipt to the compliance owner's acceptance. Activation runs from acceptance to the first dispatch. Each stage has an owner and a timestamp. A single total hides whether the carrier was slow to send documents or the office was slow to review them.
Document completeness rules
Define required documents and blocking items before measuring. An insurance certificate with the wrong legal entity is not complete even though a file exists. A missing page is incomplete. A document received but not verified is not accepted. Record the defect category so a pattern can be fixed rather than blamed on the carrier.
Open cases and withdrawals
Report open cases by stage and age. A carrier that withdraws is an outcome, not a missing completion time. A carrier that is declined is also separate. Report the counts alongside the completed cases so the reader can see what is excluded. Do not drop slow cases to make the median look better.
Stratify by source and document type
Stratify by how the carrier arrived (referral, load board, inbound), by fleet size, and by whether the carrier already had an active authority record. A small carrier with a new authority may take longer to produce insurance and agreement documents. The pattern should guide the onboarding checklist, not a judgment about the carrier.
Reporting and limits
Report count, median, 75th percentile, open cases by stage, and the top blocking document. Pair the timing with a data-quality measure: the share of documents returned for a specific defect. The design does not measure carrier quality, safety fitness, or the value of the first load. It measures the onboarding workflow.
What the stage report should show
Show the count by stage, median and 75th percentile for collection, verification, and activation, open cases by age, the top blocking document, and the share returned for a specific defect. Add the owner of each stage and the next review date. This lets an operations lead see whether the delay is carrier response, office review, or first-load availability.
Limits and comparison
Onboarding time is not a carrier quality score. A new authority, a complex ownership structure, or a slow insurer can lengthen the process without any party behaving poorly. Compare stages and defect patterns rather than ranking carriers. Use the result to fix the checklist and the review queue, not to screen carriers on speed alone.
Limits
The design assumes a clear first-request timestamp and a first-dispatch record. Onboarding that starts verbally before the application is complete will have a different clock. It does not measure the cost of delay or the carrier's experience. It also does not establish that faster onboarding improves retention or service; those require separate evidence.
Sources
Frequently Asked Questions
Should approval or first dispatch end the clock?
First dispatch for the operational measure. Report approval separately as a stage milestone.
How do we treat carriers that never complete onboarding?
Report them as withdrawn, declined, or open by stage. Do not include them as zero-day completions.
What is the most useful stage measure?
The median and 75th percentile for collection, verification, and activation, plus the top blocking document.
Can we compare onboarding times across recruiters?
Only with the same document requirements and definitions. Otherwise compare defect patterns rather than raw time.