What documents should a general contractor collect from subcontractors?

Start with the decision, not the document

Before requesting a file, identify why it is needed, who will review it, when it must be current, and what happens if it is missing or different from the requirement. This prevents teams from collecting sensitive or irrelevant information “just in case” and then leaving it unreviewed in an inbox or shared drive.

A practical requirement register can record the item name, applicability, request date, due date, administrative status, reviewer, decision, expiration or renewal date when relevant, and next action. Keep sensitive values out of general-purpose trackers whenever a secure system of record is available.

Common subcontractor document categories

1. Business identity and tax setup

Common records include legal business name, DBA, business address, primary contact, entity information needed by accounting, and a current signed Form W-9 when appropriate. The IRS explains that Form W-9 is used to provide a taxpayer identification number to a person required to file an information return. Because the form contains sensitive tax information, follow your organization’s approved collection and access controls.

2. Insurance evidence

Teams may request a certificate of insurance and other evidence required by the contract or reviewer. A certificate is evidence presented for review; an expiration date alone does not establish whether coverage, endorsements, limits, named parties, operations, or contract requirements are acceptable. Record “received” separately from the reviewer’s decision, and route interpretation to the broker, risk professional, attorney, or other authorized reviewer designated by your company.

3. Contractor and trade licenses

Request licenses or registrations that apply to the trade and place of work, including the license number, issuing authority, holder name, classification, and expiration date when permitted by your process. Verify requirements with the relevant state or local authority. Do not assume that a license from one state, locality, company, or individual applies elsewhere.

4. Contract and commercial records

The onboarding file may include the executed subcontract or work order, scope and exclusions, project exhibits, accepted alternates, schedule commitments, change-order procedures, billing instructions, and lien-waiver procedures. These records connect the document workflow to the actual project obligation.

5. Safety and workforce information

Depending on the work and company program, teams may collect safety-program acknowledgements, incident or experience information used during prequalification, competent-person designations, required training evidence, site-orientation completion, emergency contacts, and project-specific plans. OSHA notes that more than one employer may be citable at a multi-employer worksite, which is one reason responsibilities and coordination should be explicit.

6. Project mobilization information

Useful operational records include project manager and superintendent contacts, workforce and schedule expectations, submittal and RFI procedures, delivery and parking rules, access or badging steps, site logistics, orientation, and the owner of any unresolved exception. These are easy to omit when onboarding is treated as document collection alone.

What not to collect in an ordinary workflow tool

Avoid entering Social Security numbers, taxpayer identification numbers, bank details, complete insurance policy numbers, medical information, identity documents, passwords, or other sensitive personal information into an unapproved form, tracker, analytics event, or email. GCProof’s free tools are designed for requirement labels and working drafts, not for receiving completed tax, insurance, banking, or identity documents.

How much should you collect?

Use a risk-based and proportionate approach. A low-value, limited-duration scope may not need the same prequalification depth as a high-hazard, high-value, long-duration package. Public work, owner-controlled insurance programs, regulated trades, union requirements, or unusual contract terms may create additional obligations. More fields are not automatically better; every requested item creates handling, review, retention, and follow-up work.

Primary references

Check the current IRS Form W-9 information, OSHA’s Safety and Health Program guidance, and the applicable state and local licensing authority. Contract-specific insurance, tax, legal, and safety requirements should be defined and reviewed by the qualified people responsible for those decisions.

This guide is general workflow information. It does not determine what your company is legally required to collect and is not legal, tax, insurance, licensing, or safety advice.