← All posts
Field Notes

How to Get a Code Question Answered

July 4, 2025 · 4 min read · Reviewed September 2026

Applies to Anyone with a code question in Canada. Which sources exist, and how much weight each carries, varies by province.

Laptop showing a provincial interpretation bulletin beside an open code volume and a notebook

Everyone has been told something about the code with complete confidence by someone who turned out to be wrong. Codes are long, they change, and much of what circulates on site is remembered from an edition that has since moved.

There is an order to work through, and the sources carry very different weight. An answer from the wrong one feels the same as an answer from the right one until it is tested.

Where answers come from#

SourceWhat it isHow much weight
The code textThe adopted provisions in your provinceDefinitive, where it is unambiguous
Provincial amendmentsWhat your province changed on adoptionDefinitive, and easy to overlook
ErrataCorrections to the published textCorrects what the provision always meant
Interpretation bulletinsProvincial guidance on applying a provisionStrong; departments generally follow them
The building departmentThe authority for your projectDecisive for your project
Industry associationsTrade guidance and summariesUseful, not binding
Manufacturer literatureProduct installation requirementsBinding for that product, and slanted
Other trades on siteExperience and recollectionLeast reliable, most abundant

The row that surprises people is manufacturer literature. Installation instructions frequently form part of what a code requires, so a product installed contrary to its own instructions can be non-compliant even where the code text says nothing specific.

The bottom row deserves its reputation. Trade knowledge is genuinely valuable and it ages badly, because it is built from what passed inspection on previous jobs under previous editions. A tradesperson with twenty years of experience is describing twenty years of accumulated practice rather than the current text.

Asking in a way that gets a usable answer#

Departments answer questions constantly and the quality of the answer tracks the quality of the question. A vague enquiry gets a cautious general reply; a specific one with a drawing attached gets something you can build from.

The other thing that improves an answer is asking the right person. Counter staff handle process questions well and technical ones less well. A plans examiner or a senior building official is who you want for an interpretation, and asking for them by role rather than by name usually gets you there.

  1. Do the reading first

    Find the provision, check the provincial amendment, and check the errata. Arriving with the reference shortens the conversation considerably.

  2. Ask about a specific condition

    Describe the actual situation with dimensions and a sketch rather than asking in general. General questions get general answers.

  3. Put it in writing

    Email rather than a counter conversation. You want a record that survives staff changes and eighteen months of construction.

  4. Ask for the reasoning, not only the verdict

    Knowing why an answer is what it is lets you apply it to the next situation instead of asking again.

  5. Keep it with the drawings

    File the response with the project so the site team and the inspector can both see it.

When the answer matters enough, a designer or engineer can prepare the question with an analysis attached and a proposed conclusion. That is a different kind of enquiry and it tends to get a more definite response, because the department is reviewing a position rather than inventing one.

Timing matters as much as phrasing. A question asked before an application is a conversation; the same question asked after a deficiency notice is a negotiation, and the department has already formed a view.

On anything that repeats across projects, build a small file of the answers you have received, with dates and the edition they referenced. It saves asking twice and it flags which answers need rechecking after a changeover.

Common questions#

Is a bulletin legally binding?
Generally it is guidance rather than law, and departments follow it, which makes it close to decisive on a real project. Where it conflicts with the adopted text, ask.
Can I rely on advice from an inspector?
For your project, largely yes, and get it in writing. Inspectors change and recollections differ, and a written answer is what you point at later.
What if two officials tell me different things?
Ask both for the reasoning and the reference, then escalate to a senior examiner or the chief building official. Most conflicts resolve once the reasoning is on the table.
Does an answer from one municipality apply in another?
No. Each authority decides for itself, and the underlying reasoning travels better than the ruling.
Are paid code-consulting services worth it?
On complex buildings, frequently. On a house, the department and the bulletins usually cover it for nothing.
How do I know an answer is out of date?
Check which edition it referenced. Advice from before a changeover is the most common source of confident, wrong answers.

Looking for the number?

These pages state the requirement and name the document it comes from.

Ask your own code question

Canadian Codes answers questions like this one from national, provincial, territorial, and municipal sources, and cites the document, section, and page so you can check it yourself.

Try it free →