The 2026 Construction GC's Subcontractor Compliance Playbook

Construction general contractors operate at a different scale and risk profile than property managers running standing vendor programs. A single commercial project might involve 80-200 subcontractors, all flowing down requirements from the prime contract. Miss a single endorsement on one sub's COI and you face a chain of consequences: prime contract default, mechanic's lien on the property, OSHA penalty exposure, retention withheld, and a six-figure indemnification claim if anything goes wrong on-site.

This is the operational playbook for construction GCs — the prime-contract flow-down requirements that drive everything, the per-project compliance workflow, OCIP/CCIP coordination, AIA G706 final-payment compliance, and the lien-claim prevention process that actually works.

Key Takeaways

• GC compliance is project-scoped, not vendor-scoped. Same subcontractor may be compliant on Project A and non-compliant on Project B because the prime contract requirements differ. Per-project tracking is non-negotiable.
• Prime contract flow-down is the source of truth. Every requirement subs must meet ultimately traces back to what the owner/lender required of you. Document the trace explicitly.
• OCIP/CCIP changes the workflow dramatically. When the project carries a wrap-up policy, sub compliance shifts from "verify their GL/WC" to "verify their excess coverage + waiver enrollment." Most GCs misconfigure this.
• AIA G706 (final lien waiver + contractor's affidavit) is the choke point. Final payment can't be released until every sub has provided lien waivers + complete insurance documentation. Missed paperwork blocks the GC's retention release.
• The pre-mobilization vs in-progress vs close-out compliance phases each have different requirements. Treating them identically produces gaps during the highest-risk windows.
• The construction lien claim is the killer. Without proper sub compliance documentation, a sub can file a mechanic's lien against the property even if the GC paid them. The property owner blames the GC. Documentation is the defense.

Why GC Compliance Is Different

Property management compliance is about ongoing vendor relationships across many properties. GC compliance is about project-bounded coordination across many subs simultaneously. The structural differences:

• Project lifecycle: GCs manage subs from pre-mobilization → in-progress → close-out (often 6-24 months). Compliance requirements differ in each phase.
• Prime contract dependency: Every flow-down requirement traces to what the owner required of you. Sub requirements aren't org defaults — they're project-specific.
• OCIP/CCIP variability: Some projects carry wrap-up insurance covering all subs; others don't. The compliance workflow is fundamentally different.
• Higher risk-per-incident: Construction injuries, property damage, and lien claims have higher per-event values than property-management vendor incidents.
• Lien rights: Subcontractors have mechanic's lien rights even against an owner who paid the GC in full. Documentation is the GC's defense.

The Prime-Contract Flow-Down

Every compliance requirement for a sub originates somewhere in the prime contract. The typical chain:

1. Owner requires: $5M/$10M GL, named-insured + additional-insured endorsements, OCIP enrollment if applicable, specific bonding (payment + performance) on subs over $500K.
2. GC's prime contract incorporates: owner's requirements + GC's own indemnification + any project-specific lender or local-jurisdiction requirements.
3. GC's subcontract flows down: owner's requirements + GC's requirements + sub-tier-specific overrides (e.g. roofers need $2M/$4M when the prime requires $1M/$2M floor for structural trades).

Documentation rule: every requirement on a subcontract must trace explicitly to the prime contract clause that demanded it. When a sub pushes back on a requirement, the GC's response is "this is flow-down from Section X of the prime, here's the language."

Use our free Requirements Generator to produce trade-specific baseline requirements; layer prime-contract flow-down on top for project-specific overrides.

Pre-Mobilization Phase

Before any sub mobilizes to the site, the compliance verification checklist:

1. Subcontract executed — signed by sub's principal, not estimator
2. Insurance certificate received — current, with proper additional insured endorsements (CG 20 10 + CG 20 37 minimum)
3. OCIP/CCIP enrollment completed if applicable — sub has been enrolled in the wrap-up policy and has confirmation
4. Payment bond + performance bond if sub value exceeds project threshold (typically $500K) — bond drafts reviewed by GC's legal
5. W-9 + workers' comp certificate on file
6. Safety prequalification — many GCs require ISN, Avetta, or Highwire prequalification
7. Project-specific orientation completed — site-specific safety, BIM standards, communication protocols
8. Indemnification + waiver of subrogation verified on the COI

Missing any of these and the sub doesn't mobilize. The discipline matters because pulling a sub off-site mid-project costs 5-10x what pre-mobilization rework costs.

OCIP / CCIP Coordination

Owner-Controlled Insurance Programs (OCIPs) and Contractor-Controlled Insurance Programs (CCIPs) — collectively called "wrap-ups" — change the compliance workflow significantly.

When the project is wrap-up enrolled

• Subs don't need to provide their own GL or WC on this project (the wrap-up provides it)
• Subs DO need to provide proof of OCIP/CCIP enrollment
• Subs DO need their own auto coverage (always carved out of wrap-ups)
• Subs DO need excess liability above the wrap-up tower
• Pre-OCIP enrollment work is not covered — common gap

When the project is NOT wrap-up enrolled

• Standard sub-provides-own-coverage workflow
• All standard requirements apply

The most common error: assuming an OCIP covers what it doesn't. Excess liability above the wrap-up tower, auto coverage, professional liability, environmental liability — these are usually carved out and need sub-provided proof. GCs that don't verify these gaps end up on the hook for them.

In-Progress Phase Compliance

Once subs are mobilized, ongoing compliance focuses on:

Renewal tracking

Project lifecycles regularly span 12-24 months. Sub insurance policies renew during the project. Lapsed-during-project coverage is the most common gap that produces lien claims and indemnification disputes. Automated renewal reminders at 30/14/7/1 days before expiry are critical.

Change-order compliance

A sub takes on additional scope mid-project (change order). The change order may push them past bonding thresholds, may add new trade types (electrical sub adds low-voltage data), and may exceed their original COI scope. Compliance must be re-verified at change-order execution.

Tier 2/3 sub compliance

GCs are responsible for tier 2 subs (a sub hires their own sub). The lower-tier sub's compliance is typically the responsibility of the tier 1 sub, but the GC's prime contract usually requires the GC to verify the chain. Most GCs miss this entirely.

Daily activity tracking

For high-risk trades (steel erection, demolition, work at height), some prime contracts require daily activity tracking — which sub is on-site, what work is happening, which OSHA-covered activities are occurring. The COI verification feeds into this — only currently-compliant subs should be allowed on the gate.

Close-Out Phase

The phase that determines whether retention gets released and whether liens can attach.

AIA G706 — Contractor's Affidavit of Payment of Debts and Claims

The standard form GCs sign at substantive completion attesting that all debts to subs, materials suppliers, and labor have been paid (or that conditional lien waivers cover them). Cannot be signed if any sub has unresolved compliance gaps that would leave them in a position to file a lien.

AIA G707 — Consent of Surety to Final Payment

Surety bond company's consent to release of final payment. Surety reviews the GC's documentation of every sub. Missing COI documentation produces surety objections that delay final payment.

Unconditional Final Lien Waivers

Every sub must provide an unconditional final lien waiver (the form varies by state — typically a state-statute-defined waiver). Cannot be obtained from a sub who hasn't been paid their final retention. Cannot be released by GC if sub's compliance is incomplete.

As-Built Documentation Including Insurance

Some prime contracts require as-built documentation including a final compliance package showing every sub's insurance for the project duration. Missing periods (e.g., 3-week gap when a sub's policy lapsed) become litigation evidence years later.

Lien Claim Prevention

The mechanic's lien is the GC's worst-case scenario. Sub files a lien claim against the property; property owner pursues the GC for failure to ensure clean payment trail; the GC's retention gets withheld pending resolution; the dispute often becomes litigation.

The defense is documentation:

1. Joint-check arrangements with the sub-tier sub (tier 2/3 subs). Reduces likelihood of disputes traveling back to the GC.
2. Conditional lien waivers on progress payments. Documents that each payment cleared specific claims.
3. Unconditional lien waivers on final payment.
4. Complete COI documentation showing the sub had coverage at every moment of their work. Disproves negligence-based claims.
5. Joint-defense agreements with subs' carriers on incidents where multiple parties might be at fault.
6. Indemnification documentation showing the sub agreed in writing to indemnify the GC for claims arising from their work.

Without this stack, a sub's $300K lien claim can produce $500K-$1.5M in GC legal exposure even if the GC ultimately wins.

Per-Trade Considerations

Different trades carry different compliance gotchas. Trade-specific guides:

• Electricians — high fire-loss potential drives elevated GL minimums; specific UL certifications required
• Plumbers — water damage coverage clarifications; backflow-prevention certifications
• HVAC — refrigerant handling EPA 608, rooftop fall protection
• Roofing — completed operations critical (CG 20 37 mandatory); fall protection compliance
• General Contractors — when acting as tier 2/3 — prime contract flow-down considerations
• Concrete & Masonry — silica exposure compliance, OSHA-specific
• Demolition — environmental liability, asbestos handling, lead paint, project-specific permits
• Fire Protection — NICET certifications, NFPA-specific endorsements
• Elevator Contractors — state elevator inspector certifications
• Flooring — adhesive-fume-related environmental concerns
• Painting — lead paint compliance for renovation work
• Welding — fire-watch protocols, hot-work permits
• Tree Service — required during site prep on undeveloped sites
• Fencing — site security trade

For all 20 trades with specific minimums, use the free Requirements Generator.

State-Specific Construction Compliance

State law materially affects GC compliance workflow:

• Lien laws vary widely. California has 90-day window post-completion; Texas 120 days; Florida 90 days. Document retention must extend past the statute of limitations.
• Anti-indemnification statutes in some states (e.g., California Civil Code 2782, Texas Insurance Code Chapter 151) limit how much GCs can shift liability to subs. Compliance documentation must reflect what's enforceable in the jurisdiction.
• Workers' Comp class codes differ — see our state-specific requirements for California, Texas, New York, Florida, and other major states.
• Prevailing-wage projects (federal Davis-Bacon, state-specific) add documentation requirements beyond standard COI.

Software Workflow at GC Scale

A GC running 5+ active projects with 30-200 subs each cannot manage compliance manually. The infrastructure that scales:

1. Per-project compliance profile with prime-contract flow-down requirements documented
2. Vendor self-service portal — subs upload their own documents, get instant compliance feedback
3. Automated renewal reminders — 30/14/7/1 day before any sub's policy expires on any active project
4. Change-order compliance verification — when sub scope changes, compliance auto-rechecks
5. Multi-step deficiency campaigns — auto-escalation if sub doesn't respond to compliance gaps
6. AIA G706 documentation export — push-button generation of the close-out compliance package
7. Lien-waiver tracking — conditional + unconditional waivers tracked per payment per sub
8. OCIP/CCIP integration — verify wrap-up enrollment status real-time

COIPulse provides all of the above, scoped per-project (not per-vendor). See pricing.

The 30-Day Roll-In Plan

For GCs transitioning from manual to systematic compliance:

Week 1: Inventory

• Pull every active project + every active sub
• Extract prime-contract flow-down requirements per project
• Build the project-trade-state requirements matrix

Week 2: Triage

• Identify obvious gaps (lapsed COIs, missing endorsements, no OCIP enrollment proof)
• Send 14-day correction notices to non-compliant subs
• Halt mobilization for any sub with critical gaps

Week 3: Standardize

• Roll out per-trade flow-down templates
• Train PMs on endorsement form-number verification (CG 20 10 vs CG 20 37 vs CG 20 33/38)
• Implement standardized escalation workflows

Week 4: Automate

• Deploy vendor self-service portal
• Set up automated renewal reminders
• Configure project compliance dashboards
• Test AIA G706 documentation export

After 30 days: the program runs continuously with PM-level oversight rather than dedicated FTE compliance management.

The Free Tools to Start With

Three free tools for GCs:

1. COI Requirements Generator — pick a trade + state, get customized requirements as a print-ready exhibit
2. COI Grader — upload a sub's COI and get instant compliance score against trade+state ruleset
3. COI ROI Calculator — calculate hours saved vs. manual tracking at your project portfolio size

Use these before evaluating paid software.

Key Takeaways

• GC compliance is project-scoped, not vendor-scoped — same sub may be compliant on Project A and non-compliant on Project B
• Every requirement traces to prime-contract flow-down; document the trace explicitly
• OCIP/CCIP changes the workflow fundamentally — verify excess + auto carve-outs
• AIA G706 final-payment compliance is the choke point that determines retention release
• The mechanic's lien is the worst-case; documentation is the defense (joint checks + conditional/unconditional lien waivers + complete COI documentation)
• Per-trade compliance requirements vary 3-5x; per-state legal frameworks add another variable
• At 5+ active projects with 30+ subs each, manual tracking breaks down — automation pays for itself in 30-60 days
• Start with the Requirements Generator, COI Grader, and ROI Calculator before evaluating paid software