← Back to Blog
People & Accountability

Subcontractor Documentation: What to Collect Before Anyone Steps on Site

A subcontractor gets hurt on a job site. There's no signed agreement on file, no certificate of insurance, and nobody can say for certain what that sub was actually contracted to do. That gap doesn't stay the subcontractor's problem — depending on how the relationship was structured, it can become the general contractor's problem, fast, and it's the kind of exposure that's entirely preventable with paperwork that takes minutes to collect.

Most contractors know they should collect insurance certificates. Fewer have a consistent process for collecting everything else that actually matters before a sub ever shows up on site.

Why this gap is so common

Subcontractor relationships often move fast — a job needs coverage, a sub is available, and the paperwork gets treated as something to circle back to later. Later frequently doesn't happen, especially with subs used repeatedly, where "we've worked with them before" quietly replaces "we have current documentation on file."

A subcontractor you've used for years is still a subcontractor whose insurance can lapse without anyone noticing — until the day it matters.

What to collect before anyone steps on site

Before Day One

  • Certificate of insurance, with an expiration date you're actually tracking
  • A signed subcontractor agreement defining scope, payment terms, and responsibilities
  • Confirmation of any required licenses or certifications for the work being performed
  • A signed safety acknowledgment referencing your site's safety expectations
  • Emergency contact information for every individual the sub sends to site

Why "we've used them before" isn't a system

Repeat relationships are exactly where this documentation habit erodes fastest, because familiarity feels like verification. It isn't. An insurance certificate collected two years ago tells you nothing about coverage today, and a verbal understanding of scope from a previous job doesn't carry over to a new one automatically.

What this protects against

Documentation here isn't about distrust — it's about being able to answer specific questions quickly if something goes wrong: Was this sub covered? What were they actually contracted to do? Did they acknowledge our safety requirements? A subcontractor file that can answer those questions on request reduces risk for everyone on the job, including the sub.

Building this into a standard intake step — the same three or four documents, collected before access is granted, every time — turns a recurring liability gap into a five-minute checklist. That's a far smaller cost than untangling a claim after the fact with no paperwork to point to.

— Worklog Systems

Get the Subcontractor Management System

Intake checklists, insurance tracking, and signed agreements built to close this gap before it opens.

Browse Individual Docs on Etsy → Browse Complete Systems on Gumroad