The Subcontractor Onboarding Checklist

Onboarding a new subcontractor is the least glamorous part of running a project and one of the most consequential. Do it well and the sub starts on schedule with everything in order. Do it in a rush — because the crew is already booked and the clock is running — and you inherit whatever gaps you didn’t catch: an expired policy, a missing endorsement, a misclassified worker. Here is the checklist we’d hand any general contractor, built from the same requirements we automated into TradeGuard Pro.

This is a general operational guide, not legal or insurance advice — your contracts and local regulations set the real requirements. Use it as a starting framework and confirm specifics with your broker or attorney.

1. Company & Legal Identity

Before anything else, confirm you are hiring who you think you are hiring.

• Legal business name, DBA, and business structure (LLC, corporation, sole proprietor)
• Federal EIN / tax ID and a completed W-9 for tax reporting
• Active contractor’s license for the trade and jurisdiction — verified against the state license board, not just a number on a form
• Business address, primary contact, and after-hours contact

2. Insurance & Risk Transfer

This is the section that protects your company when something goes wrong. A missing item here is not a paperwork gap — it’s an uninsured loss waiting to land on your policy.

• Certificate of Insurance (COI) showing active general liability, workers’ compensation, and auto coverage
• Coverage limits that meet or exceed your contract and the project owner’s requirements
• Additional insured endorsement naming your company — ongoing and completed operations
• Waiver of subrogation and primary & non-contributory wording
• The policy expiration dates, recorded so you’re alerted before they lapse mid-project

If any of those terms are unfamiliar, they’re worth ten minutes: we broke them down in the COI clauses that actually protect you.

3. Contract & Scope

• Signed subcontractor agreement with a clear scope of work
• Payment terms, retention, and lien-waiver process defined up front
• Indemnification and insurance requirements written into the contract — not just assumed from the COI
• Schedule, milestones, and change-order procedure agreed before mobilization

4. Compliance & Safety

• Safety program and any required certifications (OSHA training, site-specific orientation)
• Worker classification confirmed — employees vs. 1099, to avoid misclassification liability
• Any jurisdiction-specific requirements: local business registration, prevailing-wage documentation on public work, permits tied to the trade
• Emergency contacts and incident-reporting procedure shared with the sub’s foreman

5. Payment & Records Setup

• Banking / payment details and preferred invoicing method
• A single file (digital, not a desk drawer) holding every document above
• A renewal calendar for anything that expires — licenses and COIs especially

The endorsement is the part that actually transfers risk

Collecting a certificate of insurance feels like the box being ticked, and it is the single most misunderstood step on this list. A COI is a summary prepared for your convenience. It confirms that a policy existed on the day it was issued and nothing more — it is explicitly not a contract, it does not amend the policy, and it grants you no rights under it.

What actually gives you protection is the additional insured endorsement: the form attached to the sub's policy naming you as an insured party. Without it, you have a receipt proving your subcontractor bought insurance for themselves.

The distinction that catches general contractors is the difference between coverage for ongoing operations and coverage for completed operations. Ongoing-operations coverage responds while the work is being performed. Completed-operations coverage responds after the sub has finished and left — which is precisely when construction defect claims surface, sometimes years later. A sub who carries only the ongoing form leaves you exposed for exactly the window in which you are most likely to be sued.

Ask for copies of the endorsement forms themselves, not just the certificate that references them. If your contract requires primary and non-contributory status or a waiver of subrogation, those are separate endorsements too, and a certificate saying so in the notes box does not create them.

Track the policy, not the certificate

Every certificate you collect is out of date the moment it arrives, because it describes a policy that can be cancelled the following week without anyone telling you. The classic failure is a sub who was properly covered at onboarding, let a policy lapse mid-project, and kept working — with your file showing a certificate that looked fine.

Do not rely on notification. Certificates historically promised the insurer would notify you of cancellation, and that language has been steadily walked back; most modern forms commit to nothing, leaving the obligation with the sub, who has every incentive to stay quiet.

The workable habit is to key your tracking to expiry dates rather than to the date you received a document. Set a reminder well before each policy expires, refuse to let a sub back on site with an expired certificate, and re-verify at renewal rather than treating onboarding as one-time. The administrative cost is small; the cost of discovering the gap during a claim is not.

None of this is legal or insurance advice — requirements vary by state, trade and contract. Have your broker set the limits and endorsement language, then hold the line on collecting exactly what they specify.

Where Onboarding Actually Breaks

The checklist is the easy part. The failure mode is that onboarding is a one-time event but compliance is continuous. You verify everything on day one, the sub starts, and then — three months in — their insurance quietly lapses and nobody notices, because the folder that said “compliant” in March never updated itself. The onboarding was perfect; the ongoing tracking is what failed.

That’s the reason a static checklist eventually needs a system behind it: something that stores each sub’s documents, watches the expiration dates, lets subs upload their own renewals through a portal, and flags anyone who has slipped out of compliance — without you re-running this whole checklist by hand every quarter.

That’s exactly what we built TradeGuard Pro to do: turn this checklist into an always-on system with a self-serve sub portal and automatic expiry alerts. Want it, or a compliance tool shaped around your own process? Talk to us at Rebel Studios.