Compliance: Scope

Compliance scope defines which structures, systems, occupancies, and jurisdictions fall under the authority of a given building or life-safety code at any particular moment in a project's lifecycle. Applying the wrong edition of a code or misidentifying the trigger for full code application is one of the most common sources of failed plan reviews and stop-work orders across US construction activity. This page covers how compliance scope is defined, the mechanisms that activate or limit it, the scenarios where scope disputes most frequently arise, and the boundaries that separate one compliance category from another.

Definition and Scope

Compliance scope, in the context of building regulation, describes the defined boundaries within which a code or standard has legal authority over a construction project, an existing structure, an occupancy type, or a regulated system. Scope is not a single threshold — it operates across at least four overlapping dimensions: geographic, occupancy-based, work-type-based, and code-edition-based.

The International Building Code (IBC), published by the International Code Council (ICC), states its scope explicitly in Chapter 1: it applies to the construction, alteration, movement, enlargement, replacement, repair, equipment, use and occupancy, location, maintenance, removal, and demolition of every building or structure. That breadth is then narrowed by local adoption ordinances, which may modify, delete, or add provisions — making state-level code adoption a mandatory reference point before scope can be confirmed for any specific project.

The National Fire Protection Association (NFPA) operates a parallel framework. NFPA 101, the Life Safety Code, defines its scope in Section 1.1 to cover the minimum requirements for new and existing buildings and structures for safety from fire, explosion, and similar emergencies — language that is functionally distinct from the IBC's construction-centric framing. A structure can fall simultaneously within both frameworks, requiring compliance teams to reconcile overlapping scope statements.

Key scope-defining variables include:

1. Occupancy classification — IBC Chapter 3 establishes 10 primary occupancy groups (A, B, E, F, H, I, M, R, S, U), each triggering different code requirements.
2. Construction type — IBC Table 601 sets fire-resistance ratings by construction type (one through V), affecting allowable building height and area.
3. Work category — New construction, additions, alterations, change of occupancy, and repairs each activate different sections of the code and carry different scope thresholds.
4. Code edition adopted — A jurisdiction adopting the 2018 IBC operates under different scope parameters than one on the 2021 edition. The ICC's code adoption tracker shows adoption status by state.
5. Federal overlays — Federal facilities and certain federally assisted projects fall under HUD, GSA, or Department of Defense standards that supersede local codes in specific circumstances.

How It Works

Scope determination follows a structured sequence before any compliance pathway can be assigned.

Step 1 — Identify the applicable jurisdiction. Determine which local authority having jurisdiction (AHJ) governs the project. Municipal, county, and state AHJs may have adopted different code editions. The code enforcement authority for a given parcel is confirmed through the local building department or state fire marshal's office.

Step 2 — Confirm the adopted code edition and local amendments. The adopted edition and any locally enacted amendments define the precise version of the code in force. Local amendments and adoption ordinances can restrict or expand base code requirements.

Step 3 — Classify the occupancy. Occupancy classification drives most downstream scope decisions. Misclassification at this stage — for example, treating an assembly space as a business occupancy — can invalidate an entire plan review submittal.

Step 4 — Categorize the work. The International Existing Building Code (IEBC), Chapter 1, establishes three compliance methods for work on existing buildings — the Prescriptive Compliance Method, the Work Area Method, and the Performance Compliance Method — each with different scope triggers.

Step 5 — Identify all overlapping regulatory systems. Energy codes (ASHRAE 90.1 or the IECC), accessibility standards (ADA Standards for Accessible Design), and fire codes operate in parallel. The process framework for compliance maps how these systems interact during permitting.

Common Scenarios

New construction on a greenfield site activates the full scope of the adopted IBC or IRC (International Residential Code for 1-and-2-family dwellings), with no carve-outs for pre-existing conditions. Every system — structural, mechanical, electrical, plumbing, fire protection, and accessibility — is subject to current code.

Tenant improvements in an existing commercial building frequently trigger the "change of occupancy" provisions of IEBC Chapter 9, which can require bringing non-conforming elements up to current code even when the physical scope of work is limited to a single floor.

Additions to existing residential structures fall under IRC Section R102.7, which allows the existing portion of the structure to comply with the code in effect at the time of original construction — but only if the addition does not adversely affect the performance of the existing structure.

Historic buildings present a specialized scope question. The IEBC Chapter 12 and NFPA 914 provide alternative compliance pathways for historic building compliance, allowing documented equivalency in place of strict code conformance.

Decision Boundaries

The most consequential scope boundary in US building regulation is the line between new construction scope and existing building scope. New construction triggers full current-code compliance across all systems. Existing buildings trigger the IEBC, which offers graduated compliance obligations based on the extent and type of work — a distinction with direct cost and schedule implications.

A second critical boundary separates federal jurisdiction from local AHJ jurisdiction. Federally owned buildings are not subject to local building codes; they are regulated under GSA's P-100 Facilities Standards or equivalent agency-specific standards. Federally assisted private projects, however, remain subject to local codes with federal overlay requirements added on top.

The threshold between Level 1, Level 2, and Level 3 alterations under the IEBC Work Area Method is defined by the percentage of aggregate area of the building affected: Level 1 covers the smallest scope of work, Level 2 triggers when work affects more than 50% of the aggregate area, and Level 3 activates when more than 50% of the aggregate area is reconfigured. Misidentifying the alteration level is a documented source of plan review rejections and compliance delays. For projects where scope is disputed, code variance and appeals procedures provide a formal resolution mechanism through the AHJ.