Building compliance, explained.

Definition

The body of legal requirements governing how buildings must be designed and constructed, covering life safety, egress, fire protection, accessibility, structure, and energy. In the United States, most jurisdictions adopt model codes such as the IBC and then modify them with local amendments.

Why it matters

In practice there is no single "the code." Every project answers to a specific stack: a model code, an edition year, and the local changes layered on top. Establishing that stack is the first step of any code analysis, manual or automated.

Often confused with

• Zoning code. Zoning governs what may be built where (use, density, setbacks); the building code governs how the building itself must perform. A project must satisfy both, usually through different review processes.

Definition

The model building code published by the International Code Council and adopted, with amendments, by most United States jurisdictions. The IBC governs commercial and most multi-family construction; the companion IRC covers one- and two-family dwellings.

Why it matters

The IBC is revised on a three-year cycle and jurisdictions adopt editions at their own pace, so two active projects in neighboring cities can be governed by different editions of the same code. "Meets the IBC" is only meaningful with an edition and a jurisdiction attached.

Definition

The nonprofit organization that develops and publishes the International Codes (I-Codes), including the IBC, through a governmental consensus process. Most US building regulation starts as ICC text before jurisdictions adopt and amend it.

Why it matters

The ICC also publishes its codes as structured digital data, which is what makes official code content available to software rather than only to readers. Kestrel builds on official ICC code data through a direct collaboration.

Definition

The organization or official with legal authority to enforce building regulations on a project: usually a municipal or county building department, and often several authorities at once, such as a fire marshal, a health department, or a state agency.

Why it matters

The AHJ determines which code editions and amendments apply, reviews submissions at plan check, issues corrections, inspects construction, and grants the approvals a project needs to proceed. For architects, the AHJ is the reader the drawing set must ultimately satisfy, which is why understanding how your AHJ reviews is as important as understanding what the code says.

Often confused with

• Code-writing body. The AHJ mostly does not write the code. Bodies like the ICC write model codes; the AHJ adopts, amends, and enforces them.

Definition

The geographic area subject to a specific authority’s building regulations. Two projects on opposite sides of a city line can face different code editions and different amendments, which is why a compliance check is only meaningful relative to the specific jurisdiction the project sits in.

Why it matters

The jurisdiction is also the unit of digitization. Every authority that structures its adopted codes and moves review to digital processes shortens the feedback loop for every firm that builds there, which is why digital permitting tends to spread jurisdiction by jurisdiction rather than all at once.

Definition

The changes a state, county, or city makes to a model code when adopting it: stricter requirements, deletions, or additions. Amendments are why meeting the IBC does not automatically mean meeting code in a given city.

Why it matters

For jurisdictions, amendments are how local conditions get encoded: seismic risk, wildfire exposure, density, climate. For compliance software, they are the hard part. Checking against an unamended model code produces confident answers that are wrong in exactly the places local authorities care about most.

Definition

The categorization of a building or space by how it is used: assembly, business, residential, institutional, and so on. Classification drives much of what follows in a code analysis, including allowable height and area, egress capacity, required fire separations, and sprinkler thresholds.

Why it matters

Misclassifying occupancy early is one of the most expensive code mistakes available, because so many downstream requirements key off it. It is also a genuinely interpretive judgment in mixed-use and unusual programs, which is why classification stays with the architect even when checking is automated.

Definition

The continuous, protected path occupants travel to exit a building safely: exit access, the exit itself, and exit discharge. Requirements for travel distance, corridor width, door swing, and the number of exits are among the most frequently checked and most frequently violated parts of the building code.

Why it matters

Egress is unforgiving because it is spatial: a late change to a corridor or stair does not stay local, it propagates through room layouts, door schedules, and rated assemblies. That makes egress the clearest example of why compliance issues are cheapest the moment they are created.

Definition

The length of time, expressed in hours, that a building assembly is required to withstand fire exposure, established through standardized testing. Ratings apply to walls, floors, doors, and structural elements, driven by occupancy, construction type, and required separations.

Why it matters

Ratings are a good example of data the BIM model can carry natively: a wall type knows its rating, a door knows the rating of the wall it sits in. When that data is structured, checking separation requirements stops being a sheet-by-sheet reading exercise.

Definition

The practice of evaluating building code compliance continuously throughout design rather than at discrete milestones. Continuous compliance shifts issue discovery earlier, when changes are less expensive and coordination impacts are smaller.

Why it matters

The alternative treats compliance as an event: a code review before a deadline, a plan check after submission, each one a snapshot that starts going stale immediately. Continuous compliance treats it like cost or structural performance, a property of the design that is always current. The design questions do not change; what changes is when you find out.

Often confused with

• Permit review. Permit review is a milestone event conducted by the AHJ after submission. Continuous compliance happens during design, on the design team’s side, and does not replace the AHJ’s review.
• Model checking. Model checking (clash detection, BIM QA rules) validates model quality and coordination. Continuous compliance evaluates the design against regulation. A clean model can still be a non-compliant building.

Definition

Building regulations represented as structured data that software can evaluate deterministically, instead of requiring human interpretation of natural language for every check.

Why it matters

A requirement like a minimum corridor width becomes a rule with a scope, a condition, and a value. That structure is what allows a model element to be tested against it, and what allows the result to carry a citation back to the exact source text. Not all of the code structures cleanly; the parts that require judgment are exactly the parts that should stay with a licensed professional.

Often confused with

• Digitized codes. A PDF of the code online is digital but not machine-readable. Machine-readable means structured: scoped rules software can evaluate, not pages software can only display.

Definition

Building regulations represented as structured, machine-readable intelligence rather than unstructured legal prose, enabling software to reason about compliance directly within digital design workflows.

Why it matters

This is the broader idea behind machine-readable codes: not just one code book as data, but zoning, energy, accessibility standards, and local amendments becoming queryable the way financial and tax rules already are in their industries. Regulation you can query like data instead of re-reading like a contract changes who can act on it, and when.

Definition

Structured regulatory knowledge that combines building codes, jurisdictional amendments, interpretations, and design context into a form software can evaluate consistently.

Why it matters

The distinction from raw code data matters: the code text alone does not know that your project is a mixed-use podium building in a city with a stricter egress amendment. Compliance intelligence is regulation plus applicability, the difference between a library and an answer.

Often confused with

• Code data. Code data is the text in structured form. Compliance intelligence adds applicability: which rules govern this project, in this jurisdiction, under these conditions.

Definition

A shared foundation of machine-readable regulatory intelligence built from codified regulations, verified interpretations, and project experience. Every jurisdiction modeled and every validated rule expands the usefulness of the system as a whole.

Why it matters

Most industries that run on rules eventually turn those rules into data; the built environment has not yet. Once the layer exists, design-phase checking is only the first thing it makes easier: digital permitting, portfolio review, and as-operated compliance all draw on the same foundation.

Definition

Evaluating compliance directly against the live BIM model instead of exported drawings or manually interpreted documentation. The model-native framing makes the point sharper: the model is the source of truth, so a check that runs anywhere else is checking an artifact of the design rather than the design itself.

Why it matters

The practical difference shows up in feedback speed and traceability. A check against the live model can run whenever the model changes and tie every issue to the specific element that caused it. A check against an export can only run after the export exists, against geometry that may already be out of date.

Often confused with

• BIM QA / clash detection. Clash detection finds geometric conflicts between systems; BIM QA validates modeling standards. Neither evaluates the design against building regulation.

Definition

Evaluating code compliance directly within the BIM model during design, rather than reviewing drawings after they are complete. Issues are tied to specific model elements and surface while changes are still inexpensive to make.

Definition

The use of artificial intelligence in checking building designs against applicable regulations. AI is genuinely good at reading, structuring, and cross-referencing large bodies of regulatory text. But a building permit is a high-trust decision, so trustworthy compliance systems pair AI with deterministic evaluation and direct citations to authoritative code sources. The role of AI is to accelerate regulatory understanding, not to replace professional judgment.

Why it matters

The test for any AI compliance tool is verifiability: can a licensed professional trace every result back to the exact section, paragraph, and amendment behind it, and confirm it independently? If the answer is no, the tool is producing opinions, and the architect who seals the drawings is absorbing the risk. Where the code genuinely requires interpretation, the honest behavior is to say so rather than to guess fluently.

Often confused with

• Code chatbots. A general chatbot summarizes code text fluently but cannot guarantee a citation or a deterministic result. Fluency without verifiability is exactly the failure mode that matters in a permit context.

Definition

Software evaluation of a building design against code requirements, replacing manual cross-referencing of drawings and code books. Checks run against the BIM model or exported drawings and return a list of issues.

Why it matters

The idea is decades old; what changed is the inputs. Structured code data and data-rich models now exist at the same time, which is why checking has moved from research prototypes and one-off scripts into design software itself.

Definition

A reference to the exact code section, paragraph, and adopted amendment behind a requirement or a flagged issue. Citations let an architect verify a finding against the source text instead of taking a summary on faith.

Why it matters

For public agencies the same property matters in reverse: a review decision backed by a citation is defensible, auditable, and consistent across reviewers in a way an unsourced judgment is not. In compliance software, citations are the difference between an answer and an opinion.

Definition

The practice of designing a building as a structured 3D model whose elements carry data: walls know their fire rating, doors know their width and swing direction. Because the model is data rather than lines on a sheet, software can query it.

Why it matters

For compliance, BIM is the enabling half of the equation. Code checking needs two structured inputs, the design and the regulation, and BIM supplied the first one years before the second existed.

Definition

Autodesk’s BIM authoring platform and the most widely used in United States architectural practice. Because Revit models are structured data with a plugin API, they can be checked programmatically while the design is being worked on.

Definition

An open, vendor-neutral file format for exchanging BIM data between software platforms. IFC lets a model authored in one tool be read by another.

Why it matters

IFC matters to permitting because it is the format public agencies can standardize on without endorsing a vendor. Jurisdictions that accept model-based submissions typically specify IFC, which makes export quality a compliance concern in its own right.

Definition

A data-rich digital counterpart of a physical building, kept current with information from the built asset through its operating life.

Why it matters

Compliance is usually discussed as a design-phase problem, but buildings drift from their approved state over years of tenant improvements and operations. The same structured model data that supports design-phase checking is what makes ongoing, as-operated compliance evaluation conceivable for owners.

Definition

A defined interface that lets one piece of software query another’s data or capabilities. APIs are how BIM platforms, structured code data, and permitting systems connect to each other.

Why it matters

The ICC’s Code Connect API, which serves official code content programmatically, is a concrete example: it turns the code book from a document into a service. Compliance tooling is largely the work of composing interfaces like these into a workflow architects never have to leave.

Definition

The AHJ’s review of submitted construction documents for code compliance before a permit is issued. Reviewers examine the drawing set against the adopted codes and amendments and either approve it or issue corrections.

Why it matters

Plan check is where compliance problems become schedule problems: review queues run weeks to months in many cities, and each correction cycle repeats the wait. For jurisdictions, the pressure runs the other way, high submission volumes against limited reviewer capacity. Both sides benefit when submissions arrive already checked, which is the practical argument for moving compliance upstream of submission.

Often confused with

• Inspection. Plan check reviews the documents before construction; inspection checks the built work in the field. A project passes through both.

Definition

The AHJ’s written list of code issues found during plan check, and the revised submission that answers them. A project cycles through corrections and resubmittals until the reviewer is satisfied.

Why it matters

The asymmetry is the point: an issue that takes minutes to fix in early design takes a full correction cycle to fix after submission, with redrawn sheets, re-coordination, and another turn in the review queue. Correction counts are also one of the few compliance metrics both firms and jurisdictions already track, which makes them the natural measure of whether design-phase checking is working.

Definition

The movement of permit submission and review from paper and PDF to structured digital processes, up to and including review performed against the BIM model itself.

Why it matters

For jurisdictions, structured submissions promise faster, more consistent review with the same staff. For design teams, the same structure makes requirements checkable before submission instead of discoverable after. Digital permitting and design-phase compliance are the two ends of one shift: permitting starts long before permit submission.

Often confused with

• E-submission. Uploading PDFs to a portal digitizes paper handling, not review. Digital permitting proper means the submission itself is structured data an authority can evaluate consistently.

Definition

Design and documentation effort spent redoing completed work after an issue surfaces late: moving a wall after coordination is locked, redrawing sheets, rechecking everything that was built on the earlier assumption.

Why it matters

Late-discovered code issues are one of the largest avoidable sources of rework in practice, and the least visible, because the cost is spread across the team as overtime rather than invoiced as a line item. Owners feel it as schedule; firms feel it as margin.