Sub VaultCompliance recordsField guide

Field guide · Subcontractor records

A practical subcontractor compliance document checklist

A good document process answers five questions: what is needed for this scope, who supplied it, which project and work does it cover, who checked it against the subcontract, and what happens next? Use this workflow to keep insurance, safety, and payment-cycle records together and make open follow-ups visible.

Primary sources checked October 22, 2026.

A recordkeeping workflow is not a compliance ruling.

The steps below are general recommendations for organizing work. Specific duties come from the applicable law, signed contract, project requirements, and work being performed.

Requirement where applicable

Construction safety duties depend on the work and employer roles

For construction contracts subject to Section 107, OSHA § 1926.16 describes responsibilities for both the prime contractor and subcontractors under Part 1926. Section 1926.20 also places duties on employers to initiate and maintain required safety programs and provide for frequent, regular jobsite, material, and equipment inspections by competent persons designated by the employers. These rules do not prescribe one universal subcontractor packet or make every listed record a legal requirement for every job.[1][2]

Requirement where applicable

Safety data sheet access is tied to hazardous chemicals and exposure

Construction’s hazard communication standard incorporates 29 CFR 1910.1200. Among other requirements, the rule addresses employers at multi-employer workplaces where their use or storage of hazardous chemicals could expose other employers’ employees, including methods for onsite access to the relevant safety data sheets. The exact duties depend on the workplace and chemical; a GC’s document folder is not a substitute for the required worker access or hazard communication program.[3][4]

Requirement where applicable

Insurance and lien documents must be checked against the governing terms

An insurance certificate summarizes information; it does not itself rewrite the policy. As one state example, the Texas Department of Insurance says an ACORD certificate should indicate additional insured or waiver-of-subrogation status only when the policy has the relevant endorsement naming the certificate holder. Lien-waiver rules also differ: California’s licensing board describes statutory forms and conditional versus unconditional releases, while Texas law has its own statutory waiver forms. These examples are not a nationwide rule set.[5][6][7]

Use the checklist as a team workflow, not as a legal requirement or a determination that a subcontractor, insurance policy, safety program, or payment document complies. Confirm applicable requirements with the project documents and qualified advisors.

Collect what the subcontract and project call for before mobilization

Turn the executed subcontract, project requirements, scope, and planned work into a short document list. Set an internal mobilization review so the assigned person can find missing or mismatched items before a crew is scheduled. That is a practical company control; the documents and timing that are legally or contractually required depend on the job.

Make requests specific. Ask for the current certificate and the actual endorsements required by the subcontract, not just “proof of insurance.” For safety, request the plan, agreement, training record, license, or task-specific certification that the work or contract calls for. For payment administration, record how the project handles preliminary notices and lien waivers.

  • Executed subcontract, scope, project name, trade, and anticipated start date.
  • Certificate of insurance and each endorsement the subcontract requires.
  • Safety agreement or program, orientation, training, licenses, and task-specific credentials when applicable.
  • Relevant hazardous-chemical information and a plan for required safety data sheet access.
  • Project-specific notice, waiver, and payment-document instructions for the work.

Organize records by subcontractor and project

Use one stable subcontractor record across the company, then associate each project document with the job, trade, scope, and contract it supports. This makes it easier to distinguish company-wide information from a project-specific certificate, safety plan, endorsement, or waiver.

For each file, capture a consistent index: document type, subcontractor, project, scope or trade, issue or through date, effective and expiration dates where relevant, received date, reviewer, review outcome, and next action. Keep prior versions with a clear superseded label or history rather than silently replacing a file that was already reviewed.

  • Keep a company-level subcontractor record and separate job-level document groupings.
  • Tag the project, trade, scope, document type, and relevant dates on each record.
  • Store who received and reviewed the file, its status, and any follow-up owner.
  • Preserve superseded versions and link corrections to the file they replace.

Compare the certificate and endorsements with the subcontract

Review the submitted certificate against the actual insurance language in the signed subcontract. Check the named insured, insurer and policy identifiers, coverage lines, stated limits, effective and expiration dates, project or operations description, and any exclusions or gaps that need clarification. The required policy types, limits, and wording are contract-specific; a generic checklist cannot establish that a policy is adequate for a particular risk.

If the subcontract requires an additional insured, primary and noncontributory wording, waiver of subrogation, or completed-operations coverage, request and compare the policy endorsement itself. A box or note on a certificate is not a substitute for confirming the policy language. If the paperwork does not line up, mark the item for correction and ask the subcontractor or its insurance contact for clarification; do not treat a received upload as a completed review.[5]

  • Compare the insured name, policy period, coverage lines, and limits to the contract.
  • Check the project or scope description and note missing or unclear information.
  • Open each required endorsement and compare its wording, parties, and operations to the subcontract.
  • Record the reviewer, date, outcome, open question, and person responsible for the answer.

Track expirations and follow renewal requests through to review

Record each applicable expiration date as a follow-up date, then review it alongside the project schedule. Send a renewal request early enough for the subcontractor and broker to respond before the current term ends. An approaching expiration is a prompt to verify current coverage and scheduled work, not proof by itself that coverage has ended or been renewed.

Close the loop only after someone reviews the replacement certificate and required endorsements against the subcontract. Log when the request went out, who replied, the new policy term, the review result, and any project decision made under the contract and company procedure. A team could start with reminder points 30 and 14 days before a recorded expiration; those are adjustable internal examples, not legal deadlines.

  • Set an expiration date and named follow-up owner for every time-limited record.
  • Use early reminder points that fit your project schedule; 30 and 14 days are sample internal intervals.
  • Record each request, response, updated policy term, and missing item.
  • Review renewed documents before changing the record to your team’s completed status.

Keep safety and lien records with the relevant work or payment cycle

File applicable safety plans, orientations, training or competency records, inspection notes, incident follow-ups, and work-specific chemical information with the project and trade that generated them. Identify who created the record, when it applies, and how the field team can find the information it needs. Some requirements are assigned to employers and require access at the worksite, so central filing alone may not satisfy them.[2][4]

For payment administration, group preliminary notices, conditional or unconditional waivers, payment applications, proof of payment, and exceptions with the relevant draw, payee, project, and through date. Before relying on a waiver, confirm the correct form and timing for the state and contract, whether payment has actually cleared when relevant, what work or period it covers, and any stated exceptions. Ask qualified counsel about jurisdiction-specific deadlines and forms.[6][7]

  • Attach safety and work records to the project, subcontractor, trade, date, and activity they concern.
  • Keep any required worker-facing safety information accessible where and when the work occurs.
  • Group each lien notice or waiver with its payment application, payee, amount, through date, and exceptions.
  • Track receipt, review, payment evidence, and any state- or contract-specific next deadline.

Before closing a document follow-up:

  • Is the file linked to the right subcontractor, project, and scope?
  • Was it checked against the signed subcontract and project requirements?
  • Are the reviewer, result, missing items, and next owner recorded?
  • Does a renewal or payment-cycle follow-up have a due date?
  • Can the field or accounting team find the record when needed?

Use this as a repeatable filing and review workflow, then tailor the document list to the signed subcontract, project specifications, work hazards, and the law that applies. This guide does not decide whether a subcontractor is legally compliant or whether a policy covers a claim.

Keep subcontractor documents together.

Sub Vault organizes insurance certificates, lien waivers, and other compliance documents with each subcontractor, including document dates and review status in a private workspace.

A recordkeeping workspace does not interpret a contract, verify insurance coverage, or determine legal compliance. Your team remains responsible for its review process.

Sources and scope

The supplied research snapshot was truncated before its numbered source bibliography, so its references could not be traced. This guide uses the primary sources below for the limited legal and regulatory statements it makes.

  1. [1]
    29 CFR 1926.16 — Rules of construction

    OSHA describes prime-contractor and subcontractor responsibilities under Part 1926 for covered construction contracts.

  2. [2]
    29 CFR 1926.20 — General safety and health provisions

    See paragraphs (b)(1)–(2) for employer safety programs and frequent, regular inspections by employer-designated competent persons.

  3. [3]
    29 CFR 1926.59 — Hazard communication

    The construction standard points to the requirements in 29 CFR 1910.1200.

  4. [4]
    29 CFR 1910.1200 — Hazard communication

    See paragraphs (e)(2) and (g)(8) for applicable multi-employer access to safety data sheets and employee access requirements.

  5. [5]
    Texas Department of Insurance — Certificates of Insurance FAQ

    A Texas-specific example: the FAQ explains when an ACORD certificate may indicate additional insured or waiver-of-subrogation status.

  6. [6]
    California Contractors State License Board — Conditional and Unconditional Waivers

    California guidance describes statutory waiver forms and distinguishes conditional from unconditional progress and final payment releases.

  7. [7]
    Texas Property Code, Chapter 53 — Mechanic’s, Contractor’s, or Materialman’s Lien

    See §53.284 for statutory waiver and release forms under Texas law.

This guide is general information, not legal advice or a compliance determination. Requirements and deadlines may depend on jurisdiction, contract, project, employer, and work. Consult the governing sources and qualified counsel for a specific job.