Guide

Automated Building Code Compliance Checking.

Automated code compliance checking tests a building model against the rules of a building code, so reviewers start from measured results instead of measuring again by hand. This guide explains how it works, what model data it needs and where people still decide.

The Short Answer

A Building Code, Checked By Software.

A building code sets requirements a design must meet: how far a building stands from the boundary, how tall it may be, how wide an exit stair must be, how many parking spaces it needs. Traditionally a reviewer reads the drawings and measures each of these by hand, for every submission and every resubmission.

Automated checking writes each requirement as a rule that software can test against a building model. The software measures the model, compares the result with the rule and reports Pass, Fail, or a result that needs a person to look at it. The reviewer then confirms the results instead of producing them.

From Text To Rules

How A Clause Becomes A Check.

Building codes are written for people. A clause such as “every exit stair shall have a clear width of not less than 1.2 metres” has to be translated into something precise: which elements count as exit stairs, where the width is measured, and what happens at a landing. That translation is the core of any compliance system.

Each rule therefore has a few parts: the elements or spaces it applies to, the value it measures, the limit, and the clause it comes from. The jurisdiction's own experts should review and approve every rule before it runs, because the interpretation is theirs to make.

  • Applies to: which elements or spaces, such as exit stairs, habitable rooms or car park bays
  • Measures: a distance, height, area, width, count or ratio taken from the model
  • Limit: the threshold from the clause, such as at least 1.2 metres
  • Source: the clause, so every result can be traced back to the text
What It Can Check

Measurable Rules Work Best.

ExamplesHow Well It Automates
DimensionsSetbacks, building height, stair and corridor widths, door clear widthsWell, when the model is accurate
Areas And RatiosPlot ratio, room sizes, open space, glazing ratioWell, when spaces are modelled
CountsParking bays, sanitary fittings, number of exitsWell, when elements are classified
RelationsTravel distance to an exit, rooms opening onto a corridorPartly; needs spaces and doors modelled properly
JudgementAdequate daylight, appropriate design, fire engineering solutionsPoorly; stays with the reviewer
What The Model Needs

Good Results Need A Prepared Model.

Software can only check what the model contains. Rules about rooms need rooms (IFC spaces) with names and uses. Rules about fire need fire ratings on walls and doors. Rules about parking need car park bays modelled as separate elements, not drawn as lines.

Open IFC models make this possible across authoring tools, because the same element types and properties are available whichever tool the architect uses. Some authorities already accept building submissions as IFC models, with a published list of the properties each element must carry.

Where People Decide

The Software Measures. The Reviewer Decides.

A result that says Fail is a finding, not a refusal. The reviewer checks whether the rule applies in this case, whether the model is right, and whether an approved alternative solution covers it. A good system records that decision with its reason, so the next round and any later audit can see why a result was accepted or overruled.

Resubmissions benefit most. When a revised model arrives, the rules run again and the reviewer sees which results changed, so a second round only looks at what is new.

In SpaceDesignX

SDX Zynora.

SDX Zynora uses AI to read building codes into machine-readable checks that a jurisdiction's experts approve, validates each IFC submission against them and shows every result with its clause, measured value and verdict. Reviewers confirm or overrule results, raise comments as tracked issues and record a decision for every round.

Questions

Common Questions.

What Is SDX Zynora?

SDX Zynora is an intelligent compliance platform for building permits: it uses AI to read building codes and regulations from any jurisdiction into machine-readable checks and validates open-standard IFC models against them automatically. Reviewers open the submission in 3D and on 2D plans in the browser, confirm each result, raise comments as tracked issues and record a decision for every review round.

Which Jurisdictions And Building Codes Does SDX Zynora Support?

Any jurisdiction and any building code. Our data preprocessing pipelines and machine learning models turn regulatory documents, such as building codes, zoning by-laws, fire and accessibility standards, into structured, machine-readable checks. A new jurisdiction is onboarded from its own documents with minimal manual configuration, and its experts review and approve the checks before they run.

How Does Automated Compliance Validation On IFC Models Work?

Each machine-readable check runs against the elements of the submitted IFC model: distances, heights, areas, widths, counts and the relations between spaces. Every result shows the clause, the measured value and Pass, Review or Fail, and links to the elements it measured. Reviewers confirm or overrule a result with a reason, so people keep the decision.

How Does A Design Submission Get Reviewed And Approved?

The design team uploads the model as a new version of the project. Reviewers are invited, examine it in 3D, on dimensioned plans and in Walk Mode, and raise issues with an owner, a priority and a status. When the round is complete, an approver records the decision and the reason. A resubmission is compared with the previous version.

All Questions

See Your Own Model In SpaceDesignX.

Send us a model you know well. We will walk you through it live in the products that fit your work: approvals, clash detection, defects and handover, or carbon.