Code compliance on site, code change and capstone code review

The earlier lessons explained what codes require. This final lesson turns to practice: how construction managers keep a project in compliance from permit to occupancy, how deficiencies and disagreements with officials are resolved, how codes change and how you can take part, and finally a capstone code review that brings the whole course together on a small commercial building.

Code compliance on site is a management system, not an event. It depends on approved documents being on site and current, on every design change being checked for code impact, on inspections being called and passed in sequence, on records being kept and on the team knowing which details matter most. The construction manager owns that system.

Managing compliance during construction

A practical compliance system has a few simple parts.

• Approved documents: keep the permit, approved drawings and specifications, conditions of approval and any alternative solutions or modifications on site, and mark superseded drawings clearly. Inspectors check work against the approved set, not the latest set in the office.
• Code-sensitive items list: identify the items most likely to fail or be changed: fire separations and firestopping, rated doors and hardware, exit stairs and guards, accessibility features, structural connections, envelope and energy details, and fire protection systems.
• Change control: route every RFI, substitution and site change through a check for code impact. Changes that affect code compliance go to the designers and, where required, to the building department before the work is built.
• Inspection schedule: show every inspection hold point in the look-ahead schedule, call inspections in time and record results.
• Records: photographs of concealed work, inspection reports, test certificates, field review reports, firestop logs and special inspection reports, organized for close-out.
• Close-out: track deficiencies from inspectors and designers to completion, collect certificates and as-built documents, and plan occupancy approvals.

Deficiencies, disagreements and alternatives

Inspectors will find deficiencies. Most are straightforward to correct, and the right response is to fix them promptly, document the correction and request reinspection. Occasionally, the construction manager or designer believes the inspector is wrong, or a site condition makes the approved design impractical. There are proper routes for these situations.

In Canada, the first step is a professional discussion with the inspector and, if needed, the chief building official, supported by the code text, the NRC's intent statements and provincial interpretations. Where a design cannot meet an acceptable solution, the designer can prepare an alternative solution showing that it achieves at least the required performance, for acceptance by the chief building official. Ontario's Building Code Commission resolves disputes about whether a design achieves the technical requirements of the code, and the Minister can issue binding rulings on the use of innovative materials and systems. Orders can be appealed to the courts. Other provinces have similar mechanisms, such as Alberta's Safety Codes Council appeals and BC's Building and Safety Standards Branch interpretations.

Keep disagreements professional. Building officials have wide discretion and long memories, and projects go more smoothly when the relationship is respectful. Present evidence, not frustration, and put agreements in writing.

How codes change

The national model codes are updated through an open process managed by the NRC for the Canadian Board for Harmonized Construction Codes. Anyone may submit a code change request through the NRC's website. Standing committees of volunteers, with technical support from NRC staff, consider requests, and proposed changes are published for public review, typically twice in each code cycle. Comments are considered before the committees and the board approve final changes for the next edition. Provinces then adopt the new edition on their own schedules, sometimes adding their own changes through separate public consultations, such as Ontario's Environmental Registry postings.

Construction managers have useful knowledge for code development: they see which provisions are hard to build, which products fail in the field and which requirements add cost without benefit. Industry associations represent contractors in code development, and individuals can submit proposals or comments. Following code changes also gives early warning of new requirements that will affect estimating, scheduling and procurement in the next cycle.

Capstone: a code review of a small commercial building

The capstone applies the course to a single building. The building is a proposed two-storey building on a corner lot with retail on the ground floor and offices on the second floor. Work through each step as a designer or plans reviewer would, using the values given. Where the course has given typical values, the capstone uses them; a real review would use the exact tables of the code in force.

Project data: footprint 40 m × 25 m = 1,000 m² per storey; two storeys; ground floor retail (sales floor 850 m², remainder washrooms, stair, service rooms); second floor offices 1,000 m²; sprinklered throughout; facing two streets; proposed combustible construction with wood-frame floors; west wall 9 m from the property line and north wall 3 m from the property line.

The capstone shows how one decision affects others. If the owner later asked to drop the sprinkler system, the permitted area, travel distance, exit separation, opening percentages and separation ratings would all change, and the combustible construction might no longer be allowed. If the tenant on the ground floor became a restaurant, the occupancy, occupant load, exits, fixtures and separations would change. Code review is iterative, and construction managers should expect every significant change to send the design back through these steps.