A subcontractor compliance tracker is one record per subcontractor that shows, at a glance, whether they are cleared to start or keep working: insurance current, license valid, W-9 on file, safety documents in date, and the contract paperwork signed. The checklist and tracker table below are ready to copy into a spreadsheet.
We then show what breaks when the tracker lives in a spreadsheet and an inbox, and how the dull parts (reading documents, comparing dates, chasing) can be automated with n8n or Make and Claude while a person approves every exception. We also say when a compliance platform is the better buy. For a build quote, describe the job and your budget range in the contact form.
Subcontractor compliance checklist
Your contract and your own risk rules define what "compliant" means. The list below is a starting checklist of the items contractors usually ask subcontractors for. Treat it as a prompt for your own list, not as a legal requirement for every job.
| Item | What to collect | Expiry or trigger | Source or note |
|---|---|---|---|
| Insurance certificates | General liability, auto, umbrella or excess, workers compensation, any professional cover the contract names | Policy expiration date per coverage | A certificate is information only; ask for the endorsement pages the contract requires (Miller Nash). See the certificate of insurance tracking page |
| Form W-9 | Signed W-9 with legal name and taxpayer identification number | On engagement; again if name or TIN changes | The IRS page says Form W-9 is used to give a payer your correct TIN, and is requested by someone required to file an information return (IRS About Form W-9) |
| Business license | License number, classification, issuing body, status | License expiry date; recheck at renewal | Requirements vary by state and trade and we did not open any licensing authority for this page. Confirm with the issuing body |
| Safety program and records | Written safety program, training records for the crew on your site, incident records you require, any prequalification score you require | Annual, or when the contract says | Your contract and your safety manager set this list. We cite only the OSHA rule below |
| Subcontract and flow-down | Signed subcontract, signed flow-down clauses, any required acknowledgments | Before mobilization | Your attorney drafts these |
| Lien waivers | Waiver for each payment | Each pay period | See lien waiver tracking. State-specific |
| Certified payroll, where required | Weekly payroll reports on covered public work | Weekly | See certified payroll. Depends on the contract |
The tracker table to copy
The tracker is the same layout whether it lives in Sheets, Excel or a database. One sheet lists subcontractors and an overall status. A second sheet holds one row per document. The first sheet is computed from the second, so nobody types a status.
| Sheet | Columns | How it works |
|---|---|---|
| Subcontractors | Legal name, trade, contact, W-9 on file (Y/N), subcontract signed (Y/N), overall status, next expiry date, next action, owner | Overall status is Cleared only when every required document row is valid and in date |
| Documents | Subcontractor, document type, document number, issuing body, effective date, expiry date, file link, date received, reviewed by, status, exception note | Status formula: Missing if blank, Expired if the expiry is past, Expiring if inside your warning window, otherwise Valid |
| Requirements | Document type, required for which trades or contracts, minimum values (for example limits), warning window in days | Drives which rows appear for each sub. Change a requirement once and every sub is tested against it |
| Exceptions | Subcontractor, what is missing, who approved, why, until when | Exceptions have an end date and an approver or they are not exceptions |
Add one rule that matters more than any formula: no start without Cleared, or a dated exception signed by a named person. The tracker informs the decision. The rule enforces it.
Write the rules before the tool
The tracker only works if the rules behind it are written down. Before you build anything, settle five decisions with your project managers, your safety lead and your attorney, and put them in the Requirements sheet:
- What every sub needs, and what depends on trade. A concrete crew and an electrician rarely need the same list. Define two or three requirement sets and assign each sub to one.
- The warning window. How many days before expiry the sub and your project manager are told. Start with a number, watch how long renewals really take, and adjust.
- Who may approve an exception. One named role, not "whoever is around", and a maximum length for any exception.
- What happens at the gate. Whether a non-cleared sub is blocked from the start list, from payment, or both, and who tells them.
- Who owns the data. One person accountable for the tracker staying current, with a deputy for holidays.
These decisions take an hour or two and they are the part a tool cannot do for you. They are also what makes a later automation cheap to scope: a workflow built on clear rules is a short build, while a workflow built on "it depends" turns into a long conversation about the rules.
Where hand-run compliance goes wrong
Compliance sheets fail in predictable ways. The cost shows up when someone asks you to prove what you checked, or when something goes wrong on site.
| What goes wrong | Why it happens | Fix |
|---|---|---|
| A sub starts with paperwork half done | Schedule pressure beats the sheet, and the sheet does not stop anyone | A gate: the daily or weekly start list shows only Cleared subs |
| One document expires and nobody notices | Dates sit in a column nobody sorts | Computed status and reminders to both the sub and your PM |
| Different people keep different copies | Email attachments and personal folders | One intake mailbox and one folder structure |
| The sub is cleared but their sub-tier is not | Only the first tier is tracked | A tier column and a rule that lower-tier subs are listed with the same required documents, if your contract requires it |
| You cannot show what you checked | No log of who reviewed what and when | Reviewed-by, date and notes on every document row |
On safety responsibility, 29 CFR 1926.16 is worth reading with your attorney. The Cornell Legal Information Institute page we opened says the prime contractor is not relieved of overall responsibility for compliance, that a subcontractor that agrees to do part of the contract takes responsibility for complying with the standards for that portion, and that for subcontracted work the prime and subcontractors are deemed to have joint responsibility (29 CFR 1926.16). That page does not tell you which documents to collect. It does explain why a general contractor has its own reason to see what its subs are doing. How that applies to your projects is a question for your safety manager and counsel.
How to automate compliance tracking, step by step
The automation target is the repetitive work: receiving documents, reading them, comparing them to your requirements, and chasing gaps. This is a design we would propose with n8n or Make, Claude for reading and drafting, and custom code where your systems need it. It is not an existing product, it is the design we would propose.
| Step | What runs | Who decides |
|---|---|---|
| 1. Onboarding request | When a sub is added to the job, an email goes out listing exactly the documents your requirements sheet says that trade needs, with an upload link or a reply address | Your team approves the request template once |
| 2. Intake | Documents arriving by email or upload are saved to the sub's folder and logged | Nobody |
| 3. Classify and read | Claude identifies the document type (certificate, W-9, license, safety record) and extracts the fields: names, numbers, dates, limits. Its documentation says PDFs are processed page by page as images and its text is also extracted and provided alongside and that encrypted PDFs are not accepted (Claude PDF support documentation) | Nobody, but every field is checked next |
| 4. Compare by rules | Plain rules test the extracted values against the requirements sheet: expiry later than your horizon, limits at or above the minimum, W-9 name equals the subcontract name, license number present | Rules decide pass or exception |
| 5. Review exceptions | A reviewer sees the document next to the extracted fields and approves, rejects or requests a replacement. A workflow can wait for a form submission or webhook call before it continues (n8n Wait node documentation) | A person, always |
| 6. Chase | The sub gets one email listing everything outstanding, not eleven separate emails. Reminders go out on your schedule, and your PM is told when a start date is at risk | Wording approved by you once |
| 7. Status and start list | The tracker status updates itself. The daily or weekly start list pulls only Cleared subs and shows the reason for anyone held | A person releases exceptions |
| 8. Log | Every document, extraction, rule result and approval is stored with a date and a name | Automatic |
Two principles: the model reads, rules judge; and a field the model cannot find or is unsure of is returned blank and goes to a person. A blank is never a pass. Sensitive items such as a taxpayer identification number on a W-9 need extra care: we would usually propose extracting only the fields you need, keeping documents in storage in your name, and limiting who can open them. Settle that on the first call.
What the automation will not do
What this will not do:
- Decide who is qualified. A tracker shows documents are present and in date. It does not judge a safety record or whether a sub should be hired.
- Know your licensing rules. Each state and trade differs. Your requirements sheet carries what you tell it, and someone confirms licenses with the issuing body.
- Replace site safety work. Documents are not controls on site.
- Provide legal or tax advice. Contract clauses, W-9 handling and any 1099 questions belong with your attorney or accountant.
- Authenticate documents. Reading a license or certificate does not prove it is genuine.
When a platform is the better buy
Use a platform when it fits. These are the honest cases:
| Your situation | Better choice | Why |
|---|---|---|
| Many subs, several states, regular new subs each month | A subcontractor compliance and prequalification platform | Mature platforms maintain forms, portals and sub self-service |
| Subs will log in and manage their own documents | A platform with a portal | It changes sub behavior; an email workflow cannot |
| Your owner or client requires a named prequalification system | That system | The requirement is not yours to change |
| Under about ten active subs | The tracker above | A workflow costs more than the problem |
| You use Procore or a similar platform with agents or compliance tools | Check its modules first | Do not run two systems of record. See our construction automation overview |
| Compliance is one job inside a wider paperwork flow | A custom workflow | Value comes from joining compliance, waivers, certified payroll and payments |
We did not open any vendor pricing for this page, so we make no cost comparison. Our subcontractor management software guide is written for buyers comparing platforms. Get quotes from platforms and compare them with a scoped quote from us. A larger contractor with ERP needs may also want construction software that links subcontractor records to job costing.
Next step
The first call looks at how many subs you carry, which documents you ask for, where they arrive and who chases. We tell you whether the sheet, a platform or a workflow fits.
Describe the job and your budget range in the contact form. We quote to scope in writing after a short call. Meetings are online. Sibling guides in this cluster: submittal log and RFI log. If you want the cluster overview, start at AI automation for construction companies. For how we build agents with approval points, see AI agents and workflow automation.