[ Kestrel Knowledge Base ]

Compliance Isn’t a Milestone

A practical guide to managing code compliance throughout design.

Code decisions happen throughout design. This guide maps the requirements architecture teams establish, validate, revisit, and document as a project develops, and highlights where delays in compliance feedback can create downstream work.

It is intended as a practical planning resource for architecture teams, not a phase-by-phase substitute for professional code analysis.

Format: Practice guide
Scope: 9 areas × 6 phases
Includes: Matrix · Self-assessment · PDF
Published: Sep 2026

[ From the guide ]

Where does the gap open?

The distance between decision and feedback rarely comes from carelessness. It comes from how compliance work is structured: who holds the assumptions, what gets checked, and when.

[01]

Assumptions without an owner
[02]

Checking an output instead of the design
[03]

Changes that arrive from outside
[04]

Knowledge held by a few people
[05]

Findings without a trail

See the complete 9‑area × 6‑phase planning framework

[ Inside the guide ]

01 How to use this guide
02 The compliance lifecycle: establish, validate, revalidate, document
03 The matrix: nine compliance areas across six phases
04 Compliance changes as the design changes
05 Where the gap opens
06 How continuous is your compliance process today?
07 From periodic review to continuous compliance

Establish

Identify which requirements apply and set the working assumptions: classification, code editions, compliance paths, the numbers the design will be built around.

Validate

Test those assumptions against the design as it actually exists: the plan, the massing, the assemblies, the model.

Revalidate

Check again whenever the design, the program, the team, or the governing requirements change. This is the stage that repeats.

Document

Record the requirement, the decision, and the reasoning, so the project team, the reviewer, and the next project can follow it.

Area	Pre-Design	SD	DD	CD	Permit	CA
Occupancy and use	Establish	Validate	Revalidate	Document	Revalidate	Revalidate
Construction type and building size	Establish	Validate	Revalidate	Document	Revalidate	Revalidate
Egress and life safety	Establish	Validate	Revalidate	Document	Revalidate	Revalidate
Accessibility	Establish	Validate	Validate	Document	Revalidate	Validate
Fire resistance and separations	Establish	Validate	Validate	Document	Revalidate	Validate
Plumbing fixtures	Establish	Validate	Revalidate	Document	Revalidate	Revalidate
Energy	Establish	Validate	Revalidate	Document	Revalidate	Validate
Jurisdiction-specific requirements and amendments	Establish	Validate	Revalidate	Document	Revalidate	Document
Documentation and coordination	Establish	Document	Validate	Document	Revalidate	Document

Preview: stage marks only. The full guide explains what each looks like, area by area and phase by phase.

[ Get the guide ]

The complete 9‑area × 6‑phase planning framework

The full matrix, the worked example, all five gap mechanisms explained, and a self-assessment you can print and use with your team. Three fields, and it opens on this page, with a designed PDF to keep.

No demo request required. We’ll only contact you about Kestrel resources and product updates. Privacy

[ 01 · How to use this guide ]

A planning tool, not a code analysis

Download the PDF

Compliance checklists are often organized by phase: at schematic design, confirm occupancy; at design development, check accessibility. That structure is convenient, and it is also misleading. It suggests that a topic is handled once and is then complete.

In practice, requirements are established early, tested as the design takes shape, and tested again every time something they depend on changes. This guide organizes compliance around that cycle. Each compliance area is traced across six phases, with the kind of work that typically dominates at each point.

Read this first

Timing and applicability vary by project type, jurisdiction, delivery method, and how the design develops. Fast-track, design-build, and phased projects compress or overlap these phases.
Code references use the ICC model codes (I-Codes) as a common baseline and indicate where requirements usually live. Your project answers to the editions and local amendments your jurisdiction has adopted, and some jurisdictions and building types are governed by other codes and standards entirely.
This is not legal advice or code advice. Compliance determinations belong to the licensed professional of record and, ultimately, to the authority having jurisdiction.

[ 02 · The compliance lifecycle ]

Establish, validate, revalidate, document

Every compliance area moves through the same four kinds of work. The order is not strictly linear: revalidation recurs for as long as the design is changing, and documentation is most useful when it records reasoning as it happens.

[01]

Establish

Identify which requirements apply and set the working assumptions: classification, code editions, compliance paths, the numbers the design will be built around.

[02]

Validate

Test those assumptions against the design as it actually exists: the plan, the massing, the assemblies, the model.

[03]

Revalidate

Check again whenever the design, the program, the team, or the governing requirements change. This is the stage that repeats.

Repeats whenever the design changes

[04]

Document

Record the requirement, the decision, and the reasoning, so the project team, the reviewer, and the next project can follow it.

A requirement is never simply “done.” It is current, or it has not been checked since the last relevant change.

[ 03 · The matrix ]

Nine compliance areas across six phases

Each mark identifies the kind of work that often dominates at that point, not a required sequence. Validation and revalidation may occur repeatedly, whenever the information needed to test a requirement becomes available or changes.

Legend:

Establish Validate Revalidate Document

Compliance area	[01] Concept / Pre-Design	[02] Schematic Design	[03] Design Development	[04] Construction Documents	[05] Permit / Review	[06] Construction Administration
Occupancy and use IBC Ch. 3 and mixed-occupancy provisionsIn the KB →	Establish Classify intended uses from the program. Flag mixed-occupancy conditions and the likely approach: accessory, separated, or nonseparated.	Validate Test the classification against the actual plan: room uses, occupant loads, and accessory-area limits as spaces take shape.	Revalidate Recheck when the program moves: a meeting room picks up event use, a tenant changes, an accessory area outgrows its allowance.	Document Code plans show occupancy by area, with occupant load calculations that agree with the current model.	Revalidate Reviewer questions about use or classification are resolved and carried through every dependent sheet.	Revalidate Owner-driven program revisions and tenant changes after permit can alter classification.
Construction type and building size IBC Ch. 5 and 6: height, stories, area	Establish Test allowable height, stories, and area for candidate construction types, including sprinkler and frontage increases.	Validate Confirm massing against allowable area as floor plates, story count, and frontage are set.	Revalidate Recheck when area or story count changes, or when changes to structural framing, materials, or assemblies affect the selected construction type.	Document Area calculations, construction type, and required element ratings recorded in the code analysis.	Revalidate Reviewer questions on area calculations, increases, and the separations used to justify them.	Revalidate Material and assembly substitutions checked against the required construction type.
Egress and life safety IBC Ch. 10In the KB →	Establish Estimate occupant loads and exit counts. Set the stair, core, and exit-discharge assumptions the plan will be organized around.	Validate Test exit count, exit separation, common path, and travel distance against the emerging plan.	Revalidate Door swings, corridor widths, dead ends, and egress capacity rechecked as layouts, doors, and furniture are detailed.	Document Life-safety plans: occupant loads, egress paths, travel distances, exit capacity, and signage.	Revalidate Egress comments rarely stay on one sheet. Trace each response back to every affected plan and schedule.	Revalidate Field changes to partitions, doors, hardware, and furniture layouts.
Accessibility IBC Ch. 11, ICC A117.1, ADA Standards, Fair Housing, state requirements	Establish Identify which accessibility standards apply, and which state or federal requirements sit alongside the building code. Determine applicable requirements, including required accessible units, features, and spaces where relevant.	Validate Accessible routes, entrances, vertical access, and the distribution of accessible units or spaces in the plan.	Validate Clearances become testable as rooms are detailed: door maneuvering space, turning space, toilet room layouts, reach ranges. Recheck them every time a room is re-planned.	Document Enlarged plans, mounting heights, and details that make the clearances buildable.	Revalidate Reviewer comments on clearances and counts carried back into plans, elevations, and details.	Validate Verify field dimensions, fixture substitutions, and hardware. Small changes erode clearances that were compliant on paper.
Fire resistance and separations IBC Ch. 7 and rating tablesIn the KB →	Establish Identify separations implied by the occupancy mix and construction type, and exterior wall ratings driven by fire separation distance.	Validate Locate fire walls, barriers, and shafts. Test exterior wall openings near property lines against allowable limits.	Validate Select rated assemblies. Locate doors, glazing, and penetrations. Check continuity where rated walls meet floors, roofs, and shafts.	Document Rated wall plans, assembly references, opening protective ratings, and penetration and joint details.	Revalidate Reviewer comments on ratings and continuity resolved across plans, sections, and details.	Validate Submittals for doors, dampers, glazing, and firestopping checked against the required ratings.
Plumbing fixtures IPC Ch. 4 / IBC Ch. 29, or the locally adopted plumbing code	Establish Estimate fixture counts from occupant load and occupancy. Confirm which plumbing code the jurisdiction has adopted.	Validate Size and locate toilet rooms against required counts and travel distance to facilities.	Revalidate Recheck whenever occupant load or occupancy changes. Confirm accessible fixtures and separate-facility requirements.	Document Fixture calculations and schedules that agree with the plans.	Revalidate Count and ratio comments reconciled with architectural and plumbing drawings.	Revalidate Revisit if tenant use or occupant load changes during construction.
Energy IECC or ASHRAE 90.1, plus any local stretch code	Establish Identify the adopted energy code, climate zone, any stretch code, and the intended compliance path, such as prescriptive or performance.	Validate Test window-to-wall ratio, envelope, and orientation assumptions against the chosen path.	Revalidate Assemblies, glazing, and systems rechecked. A change of compliance path has consequences well beyond the envelope.	Document Envelope values, assembly documentation, and the compliance forms the jurisdiction requires.	Revalidate Energy comments resolved across architectural, mechanical, and electrical documents.	Validate Glazing and insulation substitutions checked against documented values; commissioning where required.
Jurisdiction-specific requirements and amendments Adopted editions, local amendments, state codes, local interpretationsIn the KB →	Establish Confirm adopted code editions, local amendments, and applicable state codes. Note known local interpretations and unusual conditions.	Validate Test unusual conditions against local practice, through pre-application meetings where the jurisdiction offers them.	Revalidate Monitor adoption and effective dates. The governing edition at permit may differ from the edition assumed at pre-design, depending on jurisdiction-specific transition and vesting rules.	Document The code analysis cites the adopted editions and amendments, and records any interpretations or agreements reached.	Revalidate Reviewer interpretations are recorded and carried back into the design, not only into the response letter.	Document Inspector interpretations and approved alternates recorded for this project and for the next one in the same jurisdiction.
Documentation and coordination Code analysis, life-safety plans, consultant drawings, specifications	Establish Decide where code assumptions will live and who owns them. Start the code analysis as a working document, not a deliverable.	Document Record early assumptions with the reasoning behind them, not only the conclusion.	Validate Coordinate structural, MEP, and fire protection drawings against the code assumptions they depend on.	Document Code sheets, life-safety plans, and specifications agree with each other and with the model.	Revalidate Every comment traced from response to the affected sheets and model elements.	Document RFIs, substitutions, and field changes with code implications recorded with their rationale.

Occupancy and use

[01]

IBC Ch. 3 and mixed-occupancy provisions · In the KB →

[01] Concept / Pre-Design
Establish
Classify intended uses from the program. Flag mixed-occupancy conditions and the likely approach: accessory, separated, or nonseparated.
[02] Schematic Design
Validate
Test the classification against the actual plan: room uses, occupant loads, and accessory-area limits as spaces take shape.
[03] Design Development
Revalidate
Recheck when the program moves: a meeting room picks up event use, a tenant changes, an accessory area outgrows its allowance.
[04] Construction Documents
Document
Code plans show occupancy by area, with occupant load calculations that agree with the current model.
[05] Permit / Review
Revalidate
Reviewer questions about use or classification are resolved and carried through every dependent sheet.
[06] Construction Administration
Revalidate
Owner-driven program revisions and tenant changes after permit can alter classification.

Construction type and building size

[02]

IBC Ch. 5 and 6: height, stories, area

[01] Concept / Pre-Design
Establish
Test allowable height, stories, and area for candidate construction types, including sprinkler and frontage increases.
[02] Schematic Design
Validate
Confirm massing against allowable area as floor plates, story count, and frontage are set.
[03] Design Development
Revalidate
Recheck when area or story count changes, or when changes to structural framing, materials, or assemblies affect the selected construction type.
[04] Construction Documents
Document
Area calculations, construction type, and required element ratings recorded in the code analysis.
[05] Permit / Review
Revalidate
Reviewer questions on area calculations, increases, and the separations used to justify them.
[06] Construction Administration
Revalidate
Material and assembly substitutions checked against the required construction type.

Egress and life safety

[03]

IBC Ch. 10 · In the KB →

[01] Concept / Pre-Design
Establish
Estimate occupant loads and exit counts. Set the stair, core, and exit-discharge assumptions the plan will be organized around.
[02] Schematic Design
Validate
Test exit count, exit separation, common path, and travel distance against the emerging plan.
[03] Design Development
Revalidate
Door swings, corridor widths, dead ends, and egress capacity rechecked as layouts, doors, and furniture are detailed.
[04] Construction Documents
Document
Life-safety plans: occupant loads, egress paths, travel distances, exit capacity, and signage.
[05] Permit / Review
Revalidate
Egress comments rarely stay on one sheet. Trace each response back to every affected plan and schedule.
[06] Construction Administration
Revalidate
Field changes to partitions, doors, hardware, and furniture layouts.

Accessibility

[04]

IBC Ch. 11, ICC A117.1, ADA Standards, Fair Housing, state requirements

[01] Concept / Pre-Design
Establish
Identify which accessibility standards apply, and which state or federal requirements sit alongside the building code. Determine applicable requirements, including required accessible units, features, and spaces where relevant.
[02] Schematic Design
Validate
Accessible routes, entrances, vertical access, and the distribution of accessible units or spaces in the plan.
[03] Design Development
Validate
Clearances become testable as rooms are detailed: door maneuvering space, turning space, toilet room layouts, reach ranges. Recheck them every time a room is re-planned.
[04] Construction Documents
Document
Enlarged plans, mounting heights, and details that make the clearances buildable.
[05] Permit / Review
Revalidate
Reviewer comments on clearances and counts carried back into plans, elevations, and details.
[06] Construction Administration
Validate
Verify field dimensions, fixture substitutions, and hardware. Small changes erode clearances that were compliant on paper.

Fire resistance and separations

[05]

IBC Ch. 7 and rating tables · In the KB →

[01] Concept / Pre-Design
Establish
Identify separations implied by the occupancy mix and construction type, and exterior wall ratings driven by fire separation distance.
[02] Schematic Design
Validate
Locate fire walls, barriers, and shafts. Test exterior wall openings near property lines against allowable limits.
[03] Design Development
Validate
Select rated assemblies. Locate doors, glazing, and penetrations. Check continuity where rated walls meet floors, roofs, and shafts.
[04] Construction Documents
Document
Rated wall plans, assembly references, opening protective ratings, and penetration and joint details.
[05] Permit / Review
Revalidate
Reviewer comments on ratings and continuity resolved across plans, sections, and details.
[06] Construction Administration
Validate
Submittals for doors, dampers, glazing, and firestopping checked against the required ratings.

Plumbing fixtures

[06]

IPC Ch. 4 / IBC Ch. 29, or the locally adopted plumbing code

[01] Concept / Pre-Design
Establish
Estimate fixture counts from occupant load and occupancy. Confirm which plumbing code the jurisdiction has adopted.
[02] Schematic Design
Validate
Size and locate toilet rooms against required counts and travel distance to facilities.
[03] Design Development
Revalidate
Recheck whenever occupant load or occupancy changes. Confirm accessible fixtures and separate-facility requirements.
[04] Construction Documents
Document
Fixture calculations and schedules that agree with the plans.
[05] Permit / Review
Revalidate
Count and ratio comments reconciled with architectural and plumbing drawings.
[06] Construction Administration
Revalidate
Revisit if tenant use or occupant load changes during construction.

Energy

[07]

IECC or ASHRAE 90.1, plus any local stretch code

[01] Concept / Pre-Design
Establish
Identify the adopted energy code, climate zone, any stretch code, and the intended compliance path, such as prescriptive or performance.
[02] Schematic Design
Validate
Test window-to-wall ratio, envelope, and orientation assumptions against the chosen path.
[03] Design Development
Revalidate
Assemblies, glazing, and systems rechecked. A change of compliance path has consequences well beyond the envelope.
[04] Construction Documents
Document
Envelope values, assembly documentation, and the compliance forms the jurisdiction requires.
[05] Permit / Review
Revalidate
Energy comments resolved across architectural, mechanical, and electrical documents.
[06] Construction Administration
Validate
Glazing and insulation substitutions checked against documented values; commissioning where required.

Jurisdiction-specific requirements and amendments

[08]

Adopted editions, local amendments, state codes, local interpretations · In the KB →

[01] Concept / Pre-Design
Establish
Confirm adopted code editions, local amendments, and applicable state codes. Note known local interpretations and unusual conditions.
[02] Schematic Design
Validate
Test unusual conditions against local practice, through pre-application meetings where the jurisdiction offers them.
[03] Design Development
Revalidate
Monitor adoption and effective dates. The governing edition at permit may differ from the edition assumed at pre-design, depending on jurisdiction-specific transition and vesting rules.
[04] Construction Documents
Document
The code analysis cites the adopted editions and amendments, and records any interpretations or agreements reached.
[05] Permit / Review
Revalidate
Reviewer interpretations are recorded and carried back into the design, not only into the response letter.
[06] Construction Administration
Document
Inspector interpretations and approved alternates recorded for this project and for the next one in the same jurisdiction.

Documentation and coordination

[09]

Code analysis, life-safety plans, consultant drawings, specifications

[01] Concept / Pre-Design
Establish
Decide where code assumptions will live and who owns them. Start the code analysis as a working document, not a deliverable.
[02] Schematic Design
Document
Record early assumptions with the reasoning behind them, not only the conclusion.
[03] Design Development
Validate
Coordinate structural, MEP, and fire protection drawings against the code assumptions they depend on.
[04] Construction Documents
Document
Code sheets, life-safety plans, and specifications agree with each other and with the model.
[05] Permit / Review
Revalidate
Every comment traced from response to the affected sheets and model elements.
[06] Construction Administration
Document
RFIs, substitutions, and field changes with code implications recorded with their rationale.

[ 04 · The distance ]

Compliance changes as the design changes

Compliance is not simply something that happens at the end of a phase. Early assumptions about occupancy, egress, accessibility, fire separation, and other requirements influence downstream design decisions.

When compliance feedback arrives significantly after the decision that created the issue, other work may already depend on that decision. The plan has been laid out around it, consultants have coordinated to it, details have been developed from it, and the documents describe it.

The opportunity is therefore not only to make review faster. It is to reduce the distance between a design decision and the compliance feedback on it. That distance is measured in dependent work, not only in days, which is why the same issue can be a quick correction in one week and a rework problem a month later.

Reduce the distance

Design decision → Compliance feedback

Periodic review

Feedback arrives at the next review milestone

Decision → feedback

Plan layout builds on it

Consultants coordinate to it

Details develop from it

Documents record it

Continuous compliance

Feedback arrives close to the decision, and again after each change

Decision → feedback

Plan layout builds on it

Consultants coordinate to it

Details develop from it

Documents record it

Design decision Compliance feedback Work built on an unchecked decision Work built on a checked decision Illustrative, not to scale

[ Worked example ]

A room that changes use

Thresholds reflect recent IBC editions. Confirm against the adopted code and amendments.

Schematic design

A 900 sq ft training room in an office building is planned as part of the business occupancy. Its calculated occupant load stays below 50. Assuming the applicable common-path limits and other egress conditions are satisfied, a single exit access doorway can serve the room, and the door may swing into the room.
Design development

The owner asks for the room to host events. At the applicable occupant-load factor for tables and chairs, its calculated occupant load is now roughly 60. At 900 square feet and an occupant load of 50 or more, the room no longer qualifies for the IBC’s small accessory assembly exceptions and would generally be classified as Group A.
What now depends on it
- A second exit or exit access doorway from the room, with the required separation where applicable.
- Egress doors serving the room swinging in the direction of egress travel, with panic or fire exit hardware where required.
- Corridor egress capacity and plumbing fixture counts recalculated with the new load.
- A decision on how the Group A space relates to the rest of the building: an accessory occupancy if the area limits allow it, separated occupancies, or a nonseparated analysis applying the more restrictive requirements.
The point

None of this is hard to resolve the week the owner asks. It is harder once the adjacent rooms, the corridor, the door schedule, the plumbing layout, and the consultants’ drawings have developed around a single-exit room. The code question did not change. The amount of work depending on the answer did.

[ 05 · Where the gap opens ]

Five places feedback falls behind the design

The distance between decision and feedback rarely comes from carelessness. It comes from how compliance work is structured: who holds the assumptions, what gets checked, and when.

[01]

Assumptions without an owner

An early classification or occupant load is set in a meeting and never written down with its reasoning, so no one knows to recheck it when the program moves.

[02]

Checking an output instead of the design

Review happens on an exported set while the model keeps moving. By the time comments come back, they describe a version of the building that no longer exists.

[03]

Changes that arrive from outside

Consultant coordination, value engineering, and owner requests change the design without anyone asking which code assumptions they touch.

[04]

Knowledge held by a few people

The firm knows how a jurisdiction reads a provision, but only because one senior architect remembers. Everyone else finds out at review.

[05]

Findings without a trail

A comment is resolved on one sheet and never traced to the other sheets, schedules, and model elements built on the same decision.

[ 07 · Where Kestrel fits ]

From periodic review to continuous compliance

Traditional code workflows depend heavily on periodic review. Kestrel brings that feedback loop into the building model: continuous compliance directly against the design as it develops.

Kestrel runs inside Revit and evaluates structured code requirements against the model. Individual checks can run in about thirty seconds, making it practical to recheck requirements throughout design rather than waiting for a review milestone. Each finding identifies the relevant model element and cites the governing code provision from Kestrel’s licensed ICC code content.

The goal is not to automate architectural judgment. It is to give architects better information when they exercise that judgment.

Kestrel checks the code. Architects keep the judgment.

See continuous compliance in your model

Run Kestrel on an active Revit project.

See Kestrel on your project

Keep reading:

Compliance during design vs. plan check rework What is model-based compliance? The Knowledge Base

Compliance Isn’t a Milestone

Where does the gap open?

The complete 9‑area × 6‑phase planning framework

The full guide is open below.

A planning tool, not a code analysis

Establish, validate, revalidate, document

Establish

Validate

Revalidate

Document

Nine compliance areas across six phases

Occupancy and use

Construction type and building size

Egress and life safety

Accessibility

Fire resistance and separations

Plumbing fixtures

Energy

Jurisdiction-specific requirements and amendments

Documentation and coordination

Compliance changes as the design changes

A room that changes use

Five places feedback falls behind the design

Assumptions without an owner

Checking an output instead of the design

Changes that arrive from outside

Knowledge held by a few people

Findings without a trail

How continuous is your compliance process today?

From periodic review to continuous compliance