Diagrams Library

Code clarity you can see

High-fidelity visual explanations that reduce misinterpretation and make complex requirements easier to apply

Try it for Free
Get a Demo
Code clarity you can seeCode clarity you can see
Visual clarity for compliance

See and apply code requirements with confidence

Code interpretation shouldn’t rely on guesswork. The Diagrams Library turns complex requirements into clear, visual references-grounded in adopted codes and tailored to jurisdiction, code year, and context. Diagrams surface exactly where teams work, helping everyone interpret, align, and move forward with confidence.

Bring the code to life
Codes

Bring the code to life

Detailed visualizations break down geometry, clearances, egress rules, fire ratings, accessibility conditions, and more.

- 2,500+ diagrams
- Jurisdiction-specific variations
- Linked directly to governing code sections
Understand tricky code in context
Contextualized

Understand tricky code in context

Diagrams surface directly in Copilot and within code sections-so you’re not hunting for interpretation while you’re mid-decision.

Each diagram links back to to its governing code section and related assemblies-so interpretation stays grounded in the requirement itself.
Filter diagrams to match your project
Filter Diagrams

Filter diagrams to match your project

Navigate diagrams with smart filtering for jurisdiction, code year, code type, topic, or phase. Focus on the exact code cycle and location your project is using, and switch between disciplines without losing context.
How it Works

Whether you’re planning, reviewing, or enforcing, diagrams slot into work you’re already doing.

Diagrams show up exactly when teams need them. Whether you’re exploring requirements, coordinating across disciplines, or validating decisions, diagrams provide fast visual confirmation tied directly to the code. That keeps interpretation consistent as projects move from early planning through review.
Early Design
Coordination
QA / QC
Validate direction early
Early Design

Validate direction early

While scoping a project, teams skim key code sections and open linked diagrams to check clearances, separations, and ratings before committing to a direction.

1/4
Learn more
Align across disciplines
Coordination

Align across disciplines

During refinement, diagrams help coordinate between architecture, MEP, and structural by giving everyone a shared picture of what compliance looks like.

1/4
Learn more
Confirm before submission
QA / QC

Confirm before submission

As you review drawings, diagrams provide a quick visual reference to confirm whether layouts, heights, and relationships match the intent of the code text.

1/4
Learn more
How we build and maintain the diagrams library

Behind each diagram is a structured process designed to keep visuals aligned with the code.

We prioritize diagrams for tricky or frequently asked-about sections, plus direct user requests where text alone isn’t cutting it.

Code consultants and subject matter experts help interpret jurisdiction-specific nuances before anything is drawn.

Diagrams go through QA/QC to verify dimensions, labels, and intent, and to avoid misreadings (like mixing up “shall” and “shall not”).

Once published, diagrams are linked to their code sections and related resources. User feedback, jurisdiction updates, and new interpretations drive revisions and, when needed, new jurisdiction-specific versions.