AEC definitions

What Is Code Compliance in Construction?

Last reviewed: September 2026

Code compliance means a design, and the work built from it, satisfy the building codes and standards the local jurisdiction has adopted. It is demonstrated through a code analysis, verified at plan review for permit, and confirmed by inspection during construction.

Set by
The code edition and amendments adopted by the jurisdiction
Enforced by
The authority having jurisdiction — the AHJ
Demonstrated in
The code analysis, then plan review, then inspection
Typical scope
Occupancy, construction type, egress, fire, accessibility, energy
Common trap
Code in the analysis but never carried onto a drawing

Definition

Code Compliance

Building codes set the minimum legal requirements for safety, accessibility, structural adequacy and energy performance. What makes compliance harder than reading a code book is that codes are adopted locally: a jurisdiction picks a model code such as the International Building Code, selects an edition, and amends it. Two neighbouring municipalities can enforce different editions with different amendments, so the governing requirement is never simply "the IBC" — it is the specific edition and local amendments in force at that address, on the date of application. Compliance is demonstrated three times: in the code analysis the design team prepares, at plan review when the authority having jurisdiction examines the submitted set, and during construction when inspectors verify the work.

In depth

Adoption is what makes code compliance local

Model codes are written by organisations that have no enforcement power. They become law when a state or municipality adopts them, and adoption is where the variation enters: a jurisdiction chooses which edition to adopt, when to adopt it, and what to amend. Amendments are frequently substantive — stricter seismic provisions, additional fire requirements, local energy targets, accessibility requirements above the federal baseline.

For a firm working across jurisdictions this is the whole difficulty. The applicable requirement for a project depends on the address and on the date the permit application was filed, and a detail that satisfied the last project may not satisfy this one. Confirming the governing edition and the local amendments at the start is basic diligence and it is skipped surprisingly often.

The code analysis and where it leaks

A code analysis establishes the fundamentals — occupancy classification, construction type, allowable area and height, occupant load, egress requirements, fire resistance ratings, accessibility scope, energy path — and usually appears on a dedicated sheet at the front of the set.

The recurring failure is that the analysis and the drawings drift apart. The analysis states a two-hour rating for a shaft; the wall type on the plan is one hour. It calculates an egress width; the door schedule shows a narrower leaf. The analysis is correct and the building described by the drawings is not compliant, because the requirement was determined once and never carried through to the sheets where it had to be implemented.

Plan review and inspection

Plan review is the jurisdiction reading the submitted set against the adopted code and returning comments that must be resolved before a permit issues. Review times vary from days to months by jurisdiction and project type, which makes plan review a schedule risk as much as a technical one — and makes a set that generates a second and third comment cycle genuinely expensive.

Inspection continues the same verification into construction, at defined stages: footing, framing, rough-in, fire-stopping, final. A failed inspection stops work in that area until it is corrected and re-inspected. Compliance at permit does not survive on its own; it has to be built.

Why checking a set against code is difficult

The requirements are distributed. A single fire-rated corridor assembly touches occupancy classification, construction type, corridor rating tables, opening protectives, door hardware, penetration fire-stopping and accessibility clearances — each in a different chapter, and each landing on a different sheet drawn by a different person.

Verifying compliance means holding all of that at once and checking it against every place it appears. That is why code errors cluster in the same places on every project: at the interfaces between disciplines, and in requirements that appear once in an analysis and needed to appear in twelve places on the drawings.

Examples

Code Compliance on a real project

  • 01

    A code analysis establishes Type IIB construction and Business occupancy, setting the allowable area and required fire ratings for the project.

  • 02

    Plan review returns a comment that the accessible route to a raised platform lacks a compliant ramp or lift.

  • 03

    A framing inspection fails because fire-stopping at rated wall penetrations does not match the tested assembly called out in the specification.

Tooling

Where AI helps with code compliance

The mechanical half of code checking is finding every place a requirement should appear and confirming it does. Whether the rating in the code analysis matches the wall type on the plan, whether the assembly in the specification matches the rating on the drawing, whether an accessibility clearance is actually dimensioned — these are exhaustive comparisons across a large set, with citations available on both sides.

What automation does not do is exercise code judgment. Deciding how a provision applies to an unusual condition, or negotiating an alternative means and methods approach with an AHJ, is professional work that carries professional liability. Nomic checks documents against code requirements and cites both the provision and the sheet; it does not certify compliance or replace the AHJ.

Compare AI tools for code compliance

Best AI for Building Code Compliance in 2026

FAQ

Frequently asked questions

Code compliance means a design and the work built from it satisfy the building codes and standards adopted by the local jurisdiction. It is demonstrated in the design team’s code analysis, verified at plan review before a permit issues, and confirmed by inspections during construction.

The edition and local amendments adopted by the jurisdiction where the project is located, as in force when the permit application is filed. Model codes such as the IBC only have legal effect once a state or municipality adopts them, and local amendments frequently make requirements stricter than the model text.

The AHJ is the office or official empowered to enforce the adopted codes — typically a building department, plus fire marshals and health or accessibility officials depending on the scope. The AHJ interprets the code for the project, reviews the submitted documents, and inspects the work.

A code analysis establishes the project’s occupancy classification, construction type, allowable area and height, occupant load, egress requirements, fire resistance ratings, accessibility scope and energy compliance path. It usually appears on a dedicated sheet, and its requirements have to be carried through to every drawing that implements them.

Plan review is the jurisdiction checking a submitted set against the adopted code as part of permitting — a regulatory, external process. Drawing review is the design team’s internal check for consistency, coordination and completeness. A set can pass an internal review and still receive plan review comments.
Accelerating the design and construction of the built world.

Unlock the value of your institutional knowledge—organized, connected, and grounded in your team's critical workflows with Nomic.

Start for free