Skip to content

Regulatory literacy

OBC 1.2.2.2 is not only for structural engineers

Ontario Building Code Article 1.2.2.2 is the general review clause. It binds every Professional Engineer whose design required a sealed permit drawing, not only the structural engineer. This piece walks through what the clause actually says, the universal documentation skeleton it requires, and where discipline-specific vocabulary diverges without changing the regulatory structure.

What the clause actually says and who it binds

Ontario Building Code Article 1.2.2.2, sitting in Division C, Part 1 of the OBC, is the general review clause. It applies to construction regulated by the OBC for which the designer is required to hold a licence as a Professional Engineer or an Ontario-licensed architect. The clause requires the designer to carry out general reviews of the construction to determine whether, in the designer's professional opinion, the construction is in general conformity with the plans and other documents that formed the basis for the issuance of the permit.

"Designer" in this context is not a job title. It is a functional description of the person who prepared the design for a specific part of the work. In the typical multi-discipline building project, several Professional Engineers are simultaneously designers: the structural engineer designs the structural frame, the mechanical engineer designs the HVAC and life-safety mechanical systems, the electrical engineer designs the power distribution and fire alarm, the plumbing engineer designs the drainage and potable water systems, and so on. Each designer who sealed a permit drawing has an obligation under Article 1.2.2.2 to perform general review of the construction of that design.

This is a feature, not a quirk. The OBC is organised around the proposition that the person who claims professional responsibility for a design at permit stage is the person who must verify the construction of that design in the field. A structural firm cannot general-review mechanical work, because the structural firm did not design the mechanical work. The mechanical designer must do that. The same logic applies across every discipline whose design requires a sealed permit drawing.

Regulation 941 section 53, rewritten by O. Reg. 837/21 and in force in its current form since 2021, reinforces this at the sealing level. A practitioner shall sign and seal an engineering document if the engineering content is prepared by the practitioner, or if the practitioner otherwise assumes responsibility for any part of the document's engineering content. Either path applies to any discipline. The regulatory framework does not carve out a privileged position for structural.

The defensibility skeleton does not change by discipline

What a mechanical engineer, an electrical engineer, or a plumbing engineer documents during a site visit is discipline-specific. The framework the documentation fits into is not.

Every defensible field review report follows a consistent skeletal structure, regardless of which discipline the reviewing engineer belongs to:

  1. Scope identification. What was reviewed, on what date, for what portion of the work. A mechanical review of an eighth-floor fan coil installation and a structural review of an eighth-floor slab pour are scoped documents with start-and-stop boundaries. Silence on scope is a defensibility gap in any discipline.
  2. Observation. The engineer's direct observations of what was in place at the time of the review. Photographs where the observation is visual. Measurements, pressures, or readings where the observation is instrumental.
  3. Finding. Whether the observation is in general conformity with the design documents and the applicable codes or standards. If not, classified as deficient, requiring corrective action, or merely noted for follow-up.
  4. Reference. The design document or code/standard clause against which the finding is measured. The designer is the authority on what the design required; the code is the authority on the minimum standard.
  5. Recommendation. What, if anything, the engineer requires from the contractor or the owner to bring the work into conformity.
  6. Signature and seal. The engineer's assumption of responsibility for the report, applied under Regulation 941 section 53.

This skeleton applies to an unbraced connection at a beam-to-column joint as cleanly as it applies to an unterminated conductor at a panelboard lug, or to a missing backflow preventer at a domestic water line. The form of the review document is universal. The substance varies by discipline because the designs vary.

Firms that operate at the defensibility standard the general review clause contemplates already know this. It is a feature of how the profession writes reports, not an accident.

What changes by discipline

What changes, discipline to discipline, is the vocabulary, the kind of observations that carry information, and the body of material standards the engineer references.

Structural field review typically involves reinforcement placement and concrete cover, formwork and shoring, bolted and welded steel connections, masonry workmanship, and the structural treatment of penetrations. Applicable standards usually include the CSA A23 series for concrete, CSA S16 for steel, and CSA O86 for timber. Observations are frequently dimensional and geometric. A typical entry reads like "the bar spacing matched the design, cover was verified at the southeast corner, a single displaced stirrup was corrected on site."

Mechanical field review typically involves HVAC ductwork installation and sealing, diffuser and return-register placement, variable-air-volume box commissioning status, refrigerant piping, chillers, boilers, pumps, and terminal unit connections. Observations often involve instrumental readings: pressure tests, flow rates, temperature differentials, commissioning results. Applicable standards shift to the HVAC codes and mechanical installation codes that apply in Ontario.

Electrical field review typically involves conduit routing and support, panelboard terminations, feeder and branch circuit installations, grounding and bonding, emergency and life-safety circuit separation, fire alarm device placement, cable tray installation, and equipment pad bonding. Observations include circuit numbers, breaker sizes, and device identifications. The Canadian Electrical Code is the baseline reference.

Plumbing field review typically involves venting layout, backflow prevention, pipe sizing and support, domestic water heater installation, drainage slope, trap primers, and mechanical room clearances. Observations include pressure-test results, flush-test notes, and fixture-unit counts.

Architectural field review typically involves envelope installation, fire separation continuity, exit path widths and hardware, finishes against code-prescribed fire ratings, and accessibility elements.

None of this is controversial. Each discipline has its own vocabulary, its own observation types, and its own body of applicable standards. What is controversial, and frequently misunderstood, is the assumption that only some disciplines are bound to the general review obligation Article 1.2.2.2 describes. That assumption is not supported by the clause. The clause binds every designer whose work required a sealed permit drawing.

Why this is misunderstood as a structural-only obligation

Several factors have created the impression that OBC 1.2.2.2 is primarily a structural matter.

Structural field review has the longest and most visible published history. Structural engineering firms in Ontario have refined their field review documentation over decades. Templates, observation libraries, and internal style guides exist in mature form. MEP firms, particularly smaller practices, often have less mature internal documentation on field review and fewer published examples to consult. The result is an imbalance of public material that suggests, wrongly, that field review is primarily structural work.

General contractors sometimes consolidate the paperwork. In multi-discipline projects, the general contractor or the lead architect sometimes manages a consolidated general review file that sits on the structural engineer's letterhead. The MEP disciplines may contribute observations informally, which can create the appearance that the structural engineer is covering them. The general contractor's administrative convenience does not alter the regulatory obligation. Each discipline's field review of its own design remains that discipline's obligation.

Historic inspection regimes cloud the picture. Before Article 1.2.2.2 matured, inspection was handled in ways that varied by municipality. Some jurisdictions relied on building-official inspections; others relied on the designer. The current form of the clause makes the designer's obligation explicit and jurisdiction-neutral, but the historical variation has left residual confusion in firms that predate it.

The clause is abstract until a non-structural engineer reads it with their own discipline in mind. An MEP engineer reading "designer ... shall carry out general reviews of the construction" may not instinctively recognise themselves as the designer. They are. If the HVAC permit drawing was sealed by a P.Eng., the P.Eng. who sealed it is a designer within the meaning of the clause, and the clause's obligations are addressed to them.

What firms should do

The practical response is straightforward. Firms in any discipline that seal design drawings for a building permit under the OBC should:

Confirm the obligation. If your discipline's design required a P.Eng. seal on the drawings submitted for permit, Article 1.2.2.2 applies to your discipline's construction work. Talk to the municipality's building services department if there is any doubt in a specific project.

Adopt the defensibility skeleton. The scope-observation-finding-reference-recommendation structure is universal. Firms without a mature field review template can start from the structural-firm playbook because the structure is discipline-neutral.

Write to your own standards, not someone else's. Your reports should cite the code clauses and material standards that apply to your discipline's work. A mechanical field review of a boiler commissioning should cite the applicable mechanical standards, not the concrete code. Generic borrowing from a structural template is a durability gap that surfaces when the report is examined.

Retain documentation for the long horizon. The standard of care expects retention aligned with Ontario's fifteen-year ultimate limitation period under the Limitations Act, 2002. Audit-trail practices that are mature in structural firms apply equally in MEP firms. Observations, photographs, measurements, the final report, and the record of who signed and when are the minimum retained artefacts.

Keep the seal consistent with the design scope. A mechanical engineer's seal on a field review covers mechanical work. A structural seal on the same document covers structural work. Multi-discipline projects require multiple sealing engineers, each within their own scope. The OBC does not, and has never, contemplated a single sealing engineer as the catch-all for general review across every discipline on a project.

A note on what this piece does not cover

A full mapping of discipline-specific material standards, covering CSA B149 for natural-gas installations, CSA B64 for backflow prevention, CSA Z662 for pipeline systems, the Canadian Electrical Code for electrical work, and the other code-family references each MEP discipline relies on, sits outside the scope of this piece. Those mappings are the subject of future, discipline-specific articles.

The argument here is narrower and more immediate: OBC 1.2.2.2 is not a structural clause. It binds every Professional Engineer whose design required a sealed permit drawing. The clause has always worked this way. The construction industry would function poorly if it did not.

If your firm seals MEP or architectural permit drawings in Ontario and has not been operating with OBC 1.2.2.2 in mind, the first question to ask is not whether the obligation applies. It does. The question is whether your documentation is at the defensibility standard the clause contemplates. That standard is discipline-neutral, and the playbook is not new.

The Fermito notes

One email when a new piece or template drops.

Practice notes on sealed engineering work, the regulation around it, and what AI drafting does and does not change. No cross-promotion, no re-selling the list.

One email per release. Unsubscribe any time.

← All articles