Letters of Assurance
Overview
Letters of Assurance were introduced in the 1992 Building Code as an accountability mechanism, to provide assurance that building design and construction are substantially in compliance with the Code and that the necessary field reviews have been completed. The set of standard Schedules in the Code, and the “Guide to the Letters of Assurance in the BC Building Code”, were developed by a technical committee made up of representatives from the Architectural Institute of BC, the Association of Professional Engineers and Geoscientists of BC, the Building Officials Association of BC, the Union of BC Municipalities, and the provincial branch responsible for building regulations.
As construction practices, technologies, and processes evolve, they require that building regulatory tools, such as the Letters of Assurance, change as well. The Province of BC has reconvened a technical committee comprised of the original associations who created the Letters of Assurance to propose changes. These proposals update the Letters of Assurance, responding to industry requests for change, and supporting the Modernization Strategy’s shift toward more clearly defined responsibilities and accountabilities
The following changes are proposed:
Change “Registered Professional” to “Registered Professional of Record”
This change clarifies the roles and accountabilities of individuals who sign Letters of Assurance. It was always intended that one professional signs a Letter of Assurance for each discipline. This change in wording would result in a number of small changes throughout the Building Code. In many situations there will be additional professionals supporting the Registered Professional of Record. These registered professionals do not sign Letters of Assurance.
Proposal:
1.4.1.2 Defined Terms
Add:
Registered professional of record means a registered professional retained to undertake design work and field review pursuant to Clause 2.2.7.2.(1)(b) in Division C.
The proposed Code changes document contains numerous examples of how the new term will be applicable throughout the Code.
A Single Schedule B
As part of clarifying the process for Letters of Assurance, the Schedules B-1 and B-2 would be merged into a single Schedule B. This change does not alter the fundamental content of the current Schedules.
Proposal:
Proposed new Schedule B.
Add Part 10 (Energy Efficiency and Water Conservation) Provisions to the Letters of Assurance
The Letters of Assurance would be altered to specifically reference the new Part 10 provisions under their respective disciplines. Since professionals are already responsible for including these new provisions, this change highlights the existing responsibility for considering these important new changes.
Proposal:
Proposed new Schedule B.
Expansion of the Application of Letters of Assurance in Part 9 Buildings
Letters of Assurance do not currently apply to Part 9 buildings, except in the case of structural components that fall within the scope of Part 4, or Part 9 buildings constructed with a common egress system that requires the use of firewalls. This change would expand this scope to include:
- Geotechnical components that are beyond the scope of Part 9 in Division B, and
- Sprinkler systems that are designed to NFPA 13 and standpipe and hose systems designed to NFPA 14.
Proposal:
2.2.7.1. Application
1) The requirements of this Subsection apply to an owner who applies for a building permit for all components of a building that fall within the scope of Part 3 in Division B.
2) The requirements of the Subsection apply to the following components of a building that fall within the scope of Part 9 in Division B:
a) structural components of buildings that fall within the scope of Part 4 in Division B (See Appendix A.), or
b) geotechnical components that are beyond the scope of Part 9 in Division B (see Appendix A), or
c) sprinkler systems designed to NFPA 13 and standpipe and hose systems designed to NFPA 14, or
d) a building that is designed with common egress systems for the occupants and requires the use of firewalls according to Article 1.3.3.4. of Division A.
Implementation
We are committed to providing lead-in time to allow those who use the code to prepare for the changes. Once analysis of the feedback is complete, we will move forward with implementation. This will include an updated Guide to the Letters of Assurance. Anticipated effective date for the changes to the Letters is Fall 2009.
