Codes and regulations are not formally included as construction documents, and that fact raises practical questions for every general contractor managing multi-trade projects. The separation between contractual documents (drawings, specs, addenda) and regulatory requirements (building codes, OSHA rules, insurance mandates) creates confusion about who is responsible for what and how to track compliance across both systems.

This guide answers the most common questions GCs ask about the regulatory gap in construction documentation. Each answer includes state-level considerations, because code adoption and enforcement vary widely across jurisdictions.

The Core Question: What Counts as a Construction Document?

The AIA A201-2017 General Conditions defines construction documents as the agreement between owner and contractor, the conditions of the contract, the drawings, the specifications, addenda, and modifications. Building codes, environmental regulations, workplace safety standards, and insurance requirements are explicitly outside this definition.

This matters because construction documents create contractual obligations between parties. Codes and regulations create legal obligations imposed by government agencies. The enforcement mechanisms, remedies, and responsible parties differ for each.

State-by-State Code Adoption and Its Impact on GCs

States adopt building codes on different timelines and with different amendments. This creates a patchwork that GCs must navigate on every project.

State	Current Building Code Edition	Adoption Year	Notable Amendment	Impact on GCs
California	2022 CBC (based on 2021 IBC)	2023	Seismic and fire provisions	Strict documentation for structural compliance
Texas	2021 IBC (local adoption varies)	2022	No statewide mandate	Must check each municipality
New York	2020 BCNYS (based on 2018 IBC)	2020	Energy code overlay	Additional insulation documentation
Florida	2023 FBC (7th edition)	2024	High-velocity wind zones	Wind mitigation certificates required
Illinois	2021 IBC (with state amendments)	2022	Accessibility additions	ADA compliance documentation
Washington	2021 IBC (with WA amendments)	2023	Energy code stringency	Performance testing documentation
Ohio	2017 OBC (based on 2015 IBC)	2017	Older code edition in effect	Verify local amendments carefully
Georgia	2012 IBC with 2020 amendments	2020	Limited statewide adoption	Local codes may override
Colorado	2021 IBC (local adoption)	Varies	No statewide mandate	Each jurisdiction sets its own
Pennsylvania	2018 UCC (based on 2015 IBC)	2018	Residential code differences	Separate residential requirements

Common Questions and Answers

Why do construction documents not include building codes?

Construction documents are contractual instruments created by the design team to communicate project requirements. Building codes are external laws adopted by government jurisdictions. The design team designs to code, but the codes themselves are not part of the contract between owner and contractor. This separation exists because codes change independently of contracts, and multiple jurisdictions may apply to a single project.

Who decides which codes apply to a project?

The jurisdiction where the project is located determines which codes apply. This is typically the city or county building department. In states without statewide code adoption (like Texas and Colorado), each municipality may adopt a different code edition. The GC must verify applicable codes with the local building official before starting work.

Can a contract override a building code requirement?

No. Codes and regulations set minimum standards that cannot be reduced by contract. A contract can exceed code requirements (requiring thicker insulation, stronger structural members, or higher safety standards), but it cannot waive code minimums. Any contract provision that conflicts with applicable codes is unenforceable.

How do OSHA regulations interact with construction documents?

OSHA regulations operate independently of construction documents. OSHA standards apply to every construction worksite regardless of what the drawings or specifications say. The GC must comply with OSHA requirements even if the construction documents do not reference safety standards. OSHA can cite and fine a GC for violations without regard to the contract between project parties.

How Insurance Regulations Fit Into This Framework

Insurance requirements present a hybrid situation. Your subcontract may require specific coverage limits and endorsements (contractual requirement). State law may also mandate workers' compensation coverage (regulatory requirement). Both exist outside the formal construction documents.

GCs must track both contractual and regulatory insurance requirements. A subcontractor might satisfy your contract requirement for $1M in general liability but fail the state regulatory requirement for workers' compensation. Your document management system needs to check both.

The Practical Impact on Document Management

The separation between construction documents and regulations means GCs need two parallel document tracking systems.

System 1: Construction document control. This system handles drawings, specifications, submittals, RFIs, and change orders. It tracks revisions, distributions, and approvals within the contractual framework.

System 2: Compliance tracking. This system handles building code compliance records, OSHA documentation, insurance certificates, licenses, and permits. It tracks regulatory requirements that exist outside the contract but affect every aspect of project execution.

The most common compliance failure happens when GCs try to manage regulatory documents through their construction document control system. The two systems have different structures, different update cycles, and different stakeholders. Combining them creates blind spots in both.

Key Regulatory Areas GCs Must Track Separately

Regulatory Area	Governing Body	Update Frequency	GC Documentation Requirement
Building codes	Local building department	Every 3-6 years	Permit applications, inspection records
OSHA safety standards	Federal/state OSHA	Annual updates	Safety plans, training records, incident logs
Insurance mandates	State insurance commissioner	Varies	Certificates, endorsements, policy verifications
Environmental regulations	EPA/state agencies	Varies	Permits, monitoring reports, disposal records
Labor and wage laws	DOL/state agencies	Annual updates	Payroll records, certified payroll, posting requirements
Licensing requirements	State licensing boards	Varies	License verification, renewal tracking

FAQs

Do GCs need to keep copies of applicable building codes on-site? Most jurisdictions do not require physical copies of building codes at the jobsite. However, the GC must demonstrate knowledge of applicable codes and show compliance through their work. Keeping a digital copy of the applicable code sections accessible to field staff is a best practice that supports inspection readiness.

What happens when a building code changes during construction? Most jurisdictions apply the code in effect at the time of permit issuance. However, some states require compliance with code amendments adopted during construction if the amendment addresses life safety. Check your permit conditions and local building department policies to determine which code edition governs your project.

Can a subcontractor claim ignorance of applicable codes? No. Subcontractors are expected to know and follow the codes governing their trade. A plumbing subcontractor must know the applicable plumbing code. An electrical subcontractor must know the NEC edition adopted locally. Ignorance is not a defense in code enforcement proceedings.

How do federal projects handle the code vs. construction document separation? Federal projects follow the Unified Facilities Criteria (UFC) instead of local building codes. UFC standards are incorporated directly into federal contract documents, effectively closing the gap between construction documents and regulatory requirements. However, federal projects must still comply with OSHA and EPA regulations, which remain external.

What is the GC's liability for code violations by subcontractors? In most jurisdictions, the GC shares liability for code violations committed by subcontractors. The GC holds the building permit and bears overall project responsibility. While the GC can pursue contractual remedies against the subcontractor, regulatory agencies typically cite the GC first. Strong subcontract language and active compliance monitoring reduce this exposure.

Should GCs include specific code references in their subcontracts? Yes. Listing specific codes, editions, and local amendments in your subcontracts removes ambiguity about compliance obligations. Generic "comply with all applicable laws" language is legally sufficient but practically weak. Specific references give you a stronger contractual position if a subcontractor violates a code requirement.

Track Regulatory Compliance Alongside Your Project Documents

SubcontractorAudit monitors insurance certificates, licenses, and safety certifications so your regulatory compliance keeps pace with your construction documents. Request a demo to see the platform in action.