Request a code change

Guidelines for requesting changes

Suggestions for changes to Codes Canada publications are welcome from anyone at any time. However, anyone thinking of submitting a code change request should bear the following points in mind.

Consideration by code committees

To bring about a change in one of the Codes Canada publications, you must provide sufficient information to allow the CCBFC and its standing committees (code committees) to determine that your suggested change is needed and that it is technically correct. These code committees are made up of volunteers chosen for their expertise to represent all facets of the construction industry from all regions of Canada.

Clarity

The code committees expect proponents to make very clear what specific change they would like to see. Code change requests should identify the shortcomings of the existing Codes Canada publication, and existing code provisions that would be affected by the change. New wording should be suggested to address these shortcomings. It is recognized that not all those interested in improving the codes can be experts in code writing, and NRC Codes Canada staff will suggest improvements to the proposed wording, if necessary. Nevertheless, if specific wording is used, it will help to make the proponent's intentions clear. Code change requests that lack clarity may be returned to the proponents for clarification, thus prolonging the time required for the code committees to deal with the requests.

Focus on generic/widespread issues

It is not an appropriate role for Codes Canada publications to deal with specific products or with situations that arise only rarely. Code change requests should therefore address generic or widespread issues. Innovative products that are not yet covered by standards or mentioned in the codes are not necessarily excluded from use; they can be accepted by local authorities based on the compliance provisions in the codes regarding alternative solutions (equivalents). Services, such as the NRC Canadian Construction Materials Centre, are available to assist authorities in evaluating such innovative products. Similarly, unique situations are best dealt with by local authorities rather than swelling the codes with requirements that are seldom applied.

Focus on technical issues

With few exceptions, Codes Canada publications are strictly technical in nature and do not deal with administrative issues, such as what professional qualifications are required to perform certain functions or whether certification by a particular agency of products' compliance with standards is necessary. The provincial and territorial agencies, which adopt Codes Canada publications, have instructed the CCBFC to avoid addressing administrative issues in the codes because to do so could create conflicts with related provincial and territorial legislation and regulations. As a result, most administrative provisions in the National Building Code of Canada (NBC), National Fire Code of Canada (NFC) and National Plumbing Code of Canada (NPC) have been grouped in Division C of these documents. Code change requests should therefore address technical issues, which in the NBC, NFC and NPC are typically covered in Division B of these documents.

Objectives and functional statements

The NBC, NFC and NPC are objective-based codes. This means that the objectives and functional statements each code provision attempts to address are clearly stated. It follows that an objective-based code will only contain provisions that are related to achieving at least one of its stated objectives and functional statements.

The objectives and functional statements of the NBC, NFC and NPC have been determined by the CCBFC, in consultation with the provinces and territories. The objectives and functional statements are listed in Parts 2 and 3 of Division A of each code. Persons submitting a code change request to the NBC, NFC or NPC should ensure that the requested change is linked to at least one of the code's stated objectives and functional statements.

Adding a provision that cannot be linked to one of the currently stated objectives or functional statements would require adding at least one new objective or functional statement. Although this is not out of the question, the CCBFC would consider such an expansion of the scope of the code in question only after consultation with the provinces and territories.

Supporting documentation

Code change requests should be accompanied by enough documentation to make the case that a change is needed, and that the requested change is the right change. This documentation can include research and testing results, statistics, case studies and so forth.

Impact analysis

One aspect to include in the documentation supporting your code change request is information on the benefits likely to be achieved and the costs of implementing it.

Proponents of code change requests should also bear in mind the availability of suitable means to verify compliance. This problem can arise when requested changes are written such that there are no existing tools or models that can be used to evaluate whether or not a design or construction actually conforms to the provision. A related issue is the implications of code change requests for the existing building, fire or plumbing code enforcement infrastructure. Therefore, a code change request should include information on conformity verification and enforcement implications, including available resources.

Where the requested change has major cost or enforcement implications, the code committees may ask that a detailed impact analysis be provided.

Timing

Although suggestions for changes to Codes Canada publications are welcome from anyone at any time, the codes are revised and published according to a schedule and there may be a delay between the submission of a code change request and its publication in the relevant code, even if the request has clear sailing through the code committee and public review processes.

Persons with an active interest in the contents of Codes Canada publications should maintain an awareness of the various code cycle stages.

Summary

Code change requests should provide sufficient information to code committees to demonstrate that there is a problem with certain existing requirements or an omission in those requirements, that a change is needed, and that the requested change is the right change.

Each request should answer the following questions:

• What is the problem?
• What is the proposed solution and how does it address the problem?
• Which of the stated objectives and functional statements of the code will the proposed solution assist in achieving?
• What are the cost/benefit implications?
• What are the enforcement implications?

Requests should be clearly stated and should address generic or widespread technical issues and avoid administrative issues.

The CCBFC has instructed Codes Canada staff to return requests that do not satisfy these criteria to their proponents. Codes Canada staff are available to help proponents prepare suitable submissions, but the responsibility is on the proponent to satisfy these criteria.

Code change request status

Code change requests can be submitted by any proponent with an interest in improving codes. Every code change request is entered into a database where it is given a unique identification number for tracking purposes. The code change request then follows the path outlined in the codes development process.

Proponents can follow the progress of their request and its status by using the code change request tracking database.

Privacy notice and consent

In order to submit a request for a code change to Codes Canada publications, the NRC requires personal information from you such as your name, affiliation and contact information. The information submitted as part of the code change request, together with your personal information, is also included in the appendices of meeting minutes for completeness of records regarding proposed code changes. Except as required by confidentiality requirements, meeting minutes are available to the public upon request.

Specifically, this information is collected as it may be necessary to contact you in the event that your code change request is incomplete or missing essential information, or if clarification is needed. Furthermore, the purpose of the collection is to ensure that the code development work is unbiased, based on consensus, and that the source of the request is clearly identified. This information is also needed for the code change process to enable members of the CCBFC and the Provincial Territorial Policy Advisory Committee on Codes to track, review and analyze the request's content.

The collection and use of personal information is in accordance with the "Federal Privacy Act". The Privacy Act states that you have the right to access your personal information. Contact Codes Canada to report inaccurate information or to withdraw your request after submission.

If you require clarification about this Notice, contact the NRC Access to Information and Privacy Coordinator by email: ATIP.AIPRP@nrc-cnrc.gc.ca.

For more information on privacy issues, and the Privacy Act in general, contact the Office of the Privacy Commissioner of Canada at 1-800-282-1376.

By clicking on the "I agree" button below, you are confirming that you have read this notice and are in agreement with the collection and use of your information.

If you do not agree to the above terms and conditions, click "I decline", in which case you will not be able to submit code change requests.