Code compliance pathways: how to choose without overbuilding

Two issues can make a selected pathway harder to document:

• choosing too late (forcing redesign)
• choosing without aligning drawings/specs/documentation

The pathway is not only a calculation choice. It controls which inputs must be coordinated, what evidence the file needs, and when changes should trigger an update.

A practical approach

1. Confirm the building type, project boundary, jurisdiction, and stage.
2. Ask what documentation the authority having jurisdiction (AHJ) expects.
3. Compare the pathways that are actually available to the project team.
4. Align envelope and mechanical assumptions with current drawings and specifications.
5. Record open decisions, source documents, and model versions.
6. Recheck the file when a material design input changes.

Inputs that commonly need alignment

• assemblies, transitions, windows, and doors
• building geometry and the modelled boundary
• mechanical and ventilation information
• schedules, specifications, and product selections
• the intended submission milestone and responsible parties

The exact list depends on the pathway and project. Start from the AHJ’s requirement and the responsible design team’s decisions rather than a generic checklist.

Keep the file reviewable

Use one current set of inputs, label assumptions, and separate confirmed information from placeholders. A technically sound calculation can still create rework when its inputs no longer match the permit drawings or specifications.

Boundaries

Kates Energy can support pathway comparison, modelling, and the agreed documentation package. The AHJ makes acceptance decisions, and the project’s responsible professionals retain their design and submission duties. Support does not guarantee a permit or replace project-specific direction.