Use this page to keep the exam organized around role, process, and legal authority. The main risk is getting distracted by light technical detail and forgetting that the core of the exam is still administrative.
30-second triage
- Is this mainly a legal authority question, a process question, or a role/responsibility question?
- Does the answer live first in the Building Code Act or in Division C?
- Is the question really asking:
- who is responsible
- what document is required
- what step comes next
- what approval or notice is needed
- Is the technical detail only context?
- Is an alternative solution, enforcement tool, or occupancy step the real issue?
Fast code map
- Building Code Act: powers, duties, legal framework, offences, orders, and broader statutory responsibilities.
- Division A: compliance, objectives, and functional statements.
- Division C: permits, applications, documents, inspections, occupancy, notices, records, qualifications, and alternative solutions.
- Technical crossover parts in the syllabus: limited material from Parts 2, 3, 5, 7, 8, 9, 10, and 11 only where the legal/process question depends on that context.
Party map to keep straight
- owner
- designer
- builder
- official / chief building official / inspector context named in the syllabus
- registered code agency context where named
Process sequence to keep visible
- application or proposal
- required documents and supporting information
- review and decision point
- inspections, notices, or follow-up
- occupancy, enforcement, or alternative-solution outcome
Questions that are usually about process, not technical detail
- permit application content
- revised drawings or changed conditions
- notices and orders
- inspection and occupancy steps
- qualifications, records, and insurance items
- alternative-solution procedure
Technical crossover guardrails
- Do not turn this into a full technical-code study project.
- When a technical part appears, ask: why is this technical detail here?
- Most of the time it is there to identify:
- the responsible party
- the required document
- the governing process step
- the legal consequence
Common trap patterns
- Answering from technical instinct instead of legal/process logic.
- Mixing responsibilities of different parties.
- Missing the order of the administrative steps.
- Reading too far into a technical part that appears only in a limited crossover role.
- Forgetting that alternative-solution questions often test process discipline more than technical design.
What to tab before exam day
- the Building Code Act sections you use most
- Division C permit and document sections
- inspections, notices, and occupancy provisions
- qualification, records, and insurance sections named in the syllabus
- alternative-solution provisions
- the first page of each technical crossover area you find hardest to place
Error log labels to use while drilling
- wrong party
- wrong legal source
- wrong process step
- wrong document
- over-read technical detail
- missed alternative-solution trigger
- too slow to locate administrative rule
Final-week review priorities
- duties of parties
- permit and occupancy workflow
- enforcement and notices
- qualifications, records, and insurance items
- alternative-solution procedure
- light technical crossover only where the syllabus requires it
Exam-day reminders
- Ask first: what is the legal or administrative decision hiding inside this question?
- If the question feels technical, strip it back to role, document, process step, and authority.
- Keep the Building Code Act and Division C distinct in your head.
- When stuck, reduce the problem to: party, authority, process step, document, outcome.