StateLicense blog
Contractor Onboarding Verification: The 7-Step Checklist
A practical contractor onboarding verification checklist: license, insurance, bond, W-9, and sanctions screening — with primary sources and a final checklist.
Contractor onboarding verification is the process of confirming a contractor's license status, insurance coverage, bond, tax identity, and eligibility to do the work — before you approve them, dispatch them, or cut the first check.
Skipping any one of these checks is how compliance incidents start. A license can be perfectly valid at onboarding and expire mid-project; a certificate of insurance can show coverage that was cancelled the week after it was issued; and a Workers' Comp exemption that looks fine on paper can be disallowed for the trade in question. This checklist is built for the people who own onboarding — ops managers, compliance officers, and vendor-management teams — with links to the primary sources behind each step.
Last reviewed September 25, 2026. This is an operational framework, not legal advice. Confirm requirements with counsel or compliance professionals familiar with your jurisdictions and contracts.
What does contractor onboarding verification cover?
At minimum, seven documents and checks:
- License status and classification — verified against the official state board, not the contractor's word.
- Certificate of insurance (COI) — general liability and workers' compensation, confirmed active with the right limits.
- Bond confirmation — the contractor license bond is on file and current with the surety.
- Tax and identity documents — a completed W-9, and business registration where required.
- Sanctions and debarment screening — no federal exclusions or state disciplinary actions that disqualify the contractor.
- Signed subcontract agreement — scope, payment terms, insurance requirements, lien-waiver process.
- Monitoring setup — a recheck cadence so credentials don't go stale after onboarding.
How do you verify a contractor's license?
Verify directly with the licensing authority. Screenshot or save the record, and check four things: the license is active (not expired, inactive, suspended, or revoked), the classification covers the scope of work, the business name on the record matches the entity you're contracting with, and there are no unresolved disciplinary actions.
Each state runs its own portal:
- California: the CSLB's public data portal. The board is explicit that license status can change at any time, so check at onboarding and again when work actually starts.
- Florida: the DBPR license search at myfloridalicense.com/wl11.asp. Confirm the license type covers the trade — Florida distinguishes certified contractors (statewide) from registered contractors (local jurisdiction only).
- Washington: L&I's verification tool for contractor registration, bond, and insurance.
The official online record is the source of truth — suspensions and bond cancellations show up there, not on a paper card. For more on what a license record contains, see our guide to the contractor license verification API.
What insurance documents should you collect?
Ask for a certificate of insurance (ACORD 25 form) covering general liability and workers' compensation, plus auto liability if the contractor brings vehicles onto your sites. Set your own minimums by contract and risk tier — $1,000,000 per occurrence GL and statutory workers' comp with $500,000 employer's liability are common commercial baselines.
Reading the certificate matters more than collecting it. Check that:
- The policy is active with dates that cover the work period.
- Your company is named as an additional insured on the general liability policy.
- A waiver of subrogation applies in your favor on GL and workers' comp, so the carrier can't pursue you for claims paid on the contractor's behalf.
- The description-of-operations box references your company and the project, if your contract requires it.
Where possible, have the contractor's agent send the certificate directly to you instead of accepting a PDF forwarded by the contractor — that closes a common forgery vector. Treat workers' comp exemptions with care: contractors with no employees can often file one, but several states and trades disallow it. In California, for example, the CSLB does not permit workers' comp exemptions for C-8 concrete, C-20 HVAC, C-22 asbestos, C-39 roofing, or C-61/D-49 tree service classifications — and failure to maintain required workers' comp coverage can result in license suspension.
How do you verify a contractor license bond?
A license bond is not insurance — it guarantees the contractor's compliance with license law and pays eligible claimants (consumers, unpaid employees) when the contractor violates it. At onboarding, confirm the bond is on file with the licensing board, issued by an admitted surety, and hasn't been cancelled.
Amounts vary by state, so don't assume one number works everywhere:
- California: a $25,000 contractor's bond under Business and Professions Code § 7071.6 — no active license is issued or renewed without it. LLCs carry an additional $100,000 employee/worker bond. The CSLB's bond requirements page lists the exact filing rules.
- Washington: general contractors must carry a $30,000 bond; specialty contractors $15,000.
- Oregon, Texas, Florida, Virginia: bond or insurance alternatives differ by trade and local rules — verify per jurisdiction.
What tax and identity documents are required?
Collect a completed IRS Form W-9 before the first payment — for any subcontractor you'll pay $600 or more in a calendar year, you'll need it for year-end 1099-NEC reporting. Confirm the legal name, business name, and EIN or SSN on the form match the entity you're paying; mismatches are a classic source of IRS backup-withholding notices.
Alongside the W-9, collect proof of business registration (secretary of state business-entity search in the contractor's home state) and file a signed subcontract agreement that spells out scope, rates, payment terms, insurance requirements, indemnification, and the lien-waiver process. Collecting tax documents through an e-signature tool rather than email gives you a timestamped audit trail.
Should you screen for sanctions, debarment, and legal standing?
Yes — especially on public or federally funded work. Anyone debarred, suspended, or voluntarily excluded is barred from receiving federal contracts, and agencies may not consent to subcontracts with them (48 CFR § 9.405). Run the contractor's legal entity name (and UEI, if they have one) through the public exclusion search at SAM.gov — no account required — and save the dated results in the contractor's file.
Beyond federal exclusions, check state-level disciplinary actions in the license record you already pulled, and confirm the business is in good standing with its secretary of state. Background checks on principals are common for high-risk or client-facing roles; run them consistently by role tier so the policy is defensible.
Who owns each onboarding verification step?
Verification stalls when ownership is fuzzy. A workable split for a mid-size operation:
| Step | Owner | Evidence filed |
|---|---|---|
| License status + classification | Compliance / onboarding team | Dated board-record screenshot |
| COI collection and review | Compliance, with agent direct-send | COI + additional-insured endorsement |
| Bond confirmation | Compliance | Board record or surety confirmation |
| W-9 and tax identity | Finance / accounts payable | Signed W-9, business registration |
| Sanctions/debarment screen | Compliance | Dated SAM.gov + state search results |
| Subcontract agreement | Legal, executed by ops | Executed agreement with insurance exhibits |
| Monitoring setup | Compliance / ops | Recheck cadence in the vendor record |
Automation helps here: marketplaces and compliance teams use a contractor compliance API to run license, insurance, and bond checks at scale instead of opening five browser tabs per contractor. StateLicense currently covers California, Florida, New York City, Oregon, Texas, Virginia, and Washington — see the coverage map.
FAQ
How long does contractor onboarding verification take? A manual pass — license board, COI review, bond, W-9, SAM.gov screen — typically takes 30–60 minutes per contractor. API-driven checks return in seconds, which is why high-volume onboarders automate the repeatable parts and reserve manual review for exceptions.
What if a contractor has no employees? They may be eligible for a workers' comp exemption, but don't assume it. Exemption rules vary by state and trade — California disallows exemptions for several classifications outright.
What if the license covers the wrong classification? Stop and resolve it before work starts. A general license doesn't authorize specialty electrical or plumbing work, and paying a contractor for work outside their classification can void insurance coverage and create liability. The board record shows every classification held — check it against the scope of work.
Do I need to re-verify after onboarding? Yes. Licenses expire, bonds get cancelled, and policies lapse. See our guide on how often to recheck a contractor license for a risk-based monitoring schedule.
Contractor onboarding verification checklist
Before approving a contractor for work, confirm each item and file the evidence:
- License verified active with the state board; classification matches the scope of work
- Business name on the license record matches the contracting entity
- No unresolved disciplinary actions on the license record
- COI collected (GL + workers' comp), policy dates cover the work period
- Additional insured endorsement and waiver of subrogation confirmed
- License bond on file with the board, issued by an admitted surety, not cancelled
- Workers' comp exemption (if claimed) verified as current and allowed for the trade
- W-9 collected before first payment; name and EIN/SSN match the payee
- Business registration / good standing confirmed
- SAM.gov exclusion search run and dated; no active exclusions
- Subcontract agreement executed with insurance requirements and lien-waiver terms
- Recheck cadence set (expiration, renewal, and event-based triggers)