Objective-Based Codes, and Why They Matter

Read a code provision and it looks like a number. Read the surrounding structure and you find something more useful: a statement of what that number is there to achieve, and an acknowledgement that following the number is one way to get there rather than the only way.

Canadian codes were restructured around this idea some years ago. Every technical provision is linked to objectives such as safety, health, accessibility and, more recently, environment, and to functional statements describing what a design has to do.

That sounds academic until a building will not fit the prescriptive answer, at which point it becomes the mechanism that lets the project proceed.

The change also altered how the code reads. Older codes stated requirements and left the reasoning implicit, so anything unusual met a wall. Writing the purpose down turned a closed list into a framework that can accommodate a building nobody anticipated.

How the structure fits together#

Following the acceptable solutions is what almost everyone does, and it is the fastest route through a permit. Doing so is deemed to satisfy the objective, so nobody has to prove anything.

The alternative path exists for the cases where the acceptable solution is impossible, disproportionate, or simply worse for the building. A heritage structure where a required stair cannot be built. An unusual geometry the prescriptive tables do not contemplate. A material that performs well and is not listed.

Why knowing the objective helps anyway#

Even on a project that never proposes an alternative, understanding what a provision is for makes it easier to apply. A requirement about openings near a property line makes more sense once you know it is about fire spreading between buildings, and that understanding tells you which details matter and which are incidental.

It also helps in conversation with a building official. An argument framed around the objective, showing that a proposal serves the same purpose, is a different discussion from one that starts with disagreeing about wording.

And it explains why some provisions look inconsistent. Two requirements that seem to contradict each other usually serve different objectives, and reading the objectives resolves it.

There is a practical benefit for anyone reading a code they did not write. Provisions that appear arbitrary become memorable once you know the failure they are guarding against, and requirements you understand are requirements you stop getting wrong.

The environment objective is the newest addition and the one to watch. Energy requirements have been folded into this structure, which is what allows compliance by modelling rather than by matching a list, and the same mechanism will carry whatever comes next.

1. 1

   Start with the acceptable solution

   It is the fast path and it is what reviewers expect. Only leave it when there is a real reason.

2. 2

   Identify the objective before proposing anything else

   The case for an alternative is built around what the provision is for, so that is where to start rather than with the design you prefer.

3. 3

   Talk to the department early

   Alternative solutions are accepted by the authority having jurisdiction. Finding out what evidence they expect before producing it saves producing the wrong thing.

4. 4

   Get someone qualified to prepare it

   This is usually engineering work, and the analysis carries a professional’s responsibility with it.

5. 5

   Record the acceptance with the drawings

   Put the reference on the drawing set so the inspector on site is not meeting it cold.

Common questions#

Does this apply to houses?

The structure applies throughout, and houses are covered by a prescriptive part designed to be followed directly. Alternative solutions on houses are uncommon and they do happen, usually on renovations to older buildings.

Who approves an alternative solution?

The authority having jurisdiction, on the evidence submitted. There is no central approval that binds every municipality.

Does acceptance in one city carry to another?

Not automatically. Precedent is persuasive and each authority makes its own decision, so the analysis usually travels better than the approval does.

Is it expensive?

It adds engineering and review time, so it is worth reserving for cases where the prescriptive route is genuinely unworkable rather than mildly inconvenient.

What if the department refuses?

Ask what evidence would change the answer. Refusals often reflect a gap in the submission rather than a rejection of the concept, and most jurisdictions have an escalation path.

Where do I find the objectives?

They are published as part of the code, in their own division, with links from the technical provisions. It is the part of the book almost nobody opens.