Building regulations

Building regulations are legally binding requirements that govern defined aspects of building work and, in some systems, buildings in use. They provide a framework for protecting people and property, while the technical way of demonstrating compliance can differ between jurisdictions. Fire-related provisions may address escape, fire spread, structural performance, detection, suppression and firefighting.

A regulation is not the same as a design guide or a test standard. Legal instruments establish obligations, while compliance documents and verification methods describe accepted ways of meeting them. Some systems also permit alternative solutions when the required performance can be demonstrated.

The applicable jurisdiction, edition, building use and scope must therefore be identified. A rule that applies to one building or country cannot be presented as a universal fire-safety requirement. Compliance pathways and supporting standards can also change between editions.

Purpose and regulatory structure

Building regulations translate social objectives into enforceable requirements. IFEG describes their intent as mitigating risks to a level accepted by building users and the wider community. This does not mean that every regulation expresses risk numerically or that zero risk is the objective.

New Zealand provides a clear example of a legal hierarchy in the 2005 IFEG account. The Building Act provides the overarching building-control framework, regulations contain the Building Code, and the Code establishes minimum performance criteria. Compliance documents then describe ways of satisfying those criteria.

Legal requirements and ways of demonstrating compliance have different roles. Based on Australian Building Codes Board et al. (2005), pp. 0.2-1–0.2-2.

That example also distinguishes legal effect. The Act, regulations and Building Code are described as legally binding, while the handbook and compliance documents are not mandatory. An alternative solution must be assessed against the Code's performance criteria rather than merely copying a non-mandatory example.

The hierarchy prevents confusion between the objective and the method. A prescriptive detail is one possible route to compliance, not necessarily the only acceptable design. Where the regulatory system permits another solution, the evidence must address the underlying legal requirement.

Fire safety objectives belong to this distinction. They can include occupant protection, support for emergency services, protection of property and limitation of fire spread. Project-specific objectives may add heritage, environmental or business concerns without removing mandatory obligations.

Prescriptive and performance-based approaches

Prescriptive design follows specified instructions, dimensions, classifications or construction details. It offers a defined pathway that can be straightforward to apply when the building falls within its intended scope. The conditions and assumptions of that pathway still need to match the project.

Performance-based design evaluates whether a proposal meets functional and performance criteria. It can permit different technical arrangements when their results are demonstrated. The analysis must still use accepted objectives, methods, inputs and review processes rather than allowing unrestricted judgement.

IFEG explains that prescriptive codes cannot cover every emerging technology or combination of circumstances. It presents performance-based regulation as a way to reduce inappropriate constraints and support innovation. This does not make prescriptive evidence irrelevant, particularly where it provides a benchmark for comparison.

The New Zealand Building Code described by IFEG is performance based and does not itself contain prescriptive requirements. Associated compliance documents provide acceptable solutions and verification methods. This separation shows how one legal framework can support both detailed instructions and alternative demonstrations.

Performance-based regulation also creates evidence demands. Stakeholders need to agree on design scenarios, occupant groups, analysis methods and acceptance criteria. The evaluation must be documented so that a reviewer can examine the claimed performance and its limitations.

Prescriptive and performance-based approaches require different evidence. Based on Australian Building Codes Board et al. (2005), pp. 0.2-1–0.2-2 and pp. 1.2-2–1.2-3.

Compliance documents and verification

Compliance documents offer recognised methods for meeting legal requirements. They can include acceptable solutions, calculation methods and test methods. Their status depends on the legal framework, so their existence should not be confused with the binding performance criterion itself.

C/VM2 is New Zealand's verification method for Protection from Fire in its second edition of 2025. It provides one means of establishing compliance with the relevant Building Code requirements. If it cannot be followed in full, another means of demonstrating compliance is required.

The scope of that method is limited to particular design conditions. C/VM2 addresses simultaneous evacuation immediately to the outside and typical fire growth rates. Managed evacuation and hazards not defined in its rules fall outside its stated scope.

It also identifies buildings and situations for which other analysis is needed. Hospitals, care homes, stadia, some large shopping malls, tall buildings and tunnels are included in the commentary's examples. These exclusions prevent a method developed for one design context from being treated as universal.

Within its scope, C/VM2 uses ten design scenarios addressing matters such as blocked exits, concealed-space fire, horizontal spread and firefighting. Each scenario must be satisfied separately in that method. This illustrates how a verification method translates broad code objectives into particular design checks.

C/VM2 evaluates separate design scenarios within a defined scope. Based on Ministry of Business, Innovation and Employment (2025), pp. 6–9.

Equivalence and alternative solutions

Equivalency concerns demonstrating that another design provides the performance required by the regulatory system. It is not simply a declaration that a different arrangement is preferable. The evaluation must identify the criteria, evidence and any benchmark used for comparison.

IFEG distinguishes comparative and absolute approaches. A comparative approach evaluates a trial design against a deemed-to-satisfy or prescriptive benchmark using compatible criteria. An absolute approach evaluates directly against agreed performance criteria and accounts for uncertainty.

In a comparative assessment, the trial design should not perform less well than the benchmark under the chosen criteria. Using the same methods and assumptions can reduce differences introduced by the analysis itself. That does not remove the need to choose a relevant benchmark and appropriate scenarios.

C/VM2 treats varying its prescribed inputs and parameters as an alternative solution in its commentary. Those inputs need to be identified through the Fire Engineering Brief process. This makes clear that changing a verification-method value is not the same as continuing to follow that method in full.

Approval may involve an independent authority and, where required, third-party review. IFEG describes the value of independence between the reviewer and the design process. Documentation and the assumptions behind an alternative solution must therefore be available for examination.

Technical standards and classifications

Regulatory documents can refer to technical standards for particular systems and products. C/VM2 lists editions of New Zealand standards for sprinklers, alarms and hydrants among its references. The applicable edition and amendments are part of the compliance basis.

Other technical frameworks include Euroclass system for fire-related classification and Eurocodes for structural design topics. Their use depends on the jurisdiction and the question being assessed. A classification or structural calculation is not, by itself, a complete demonstration of building-regulation compliance.

IFEG gives examples of structural design information found in Eurocodes for steel and composite construction. Those methods address defined aspects of structural fire performance. They do not replace the broader assessment of evacuation, detection, smoke or other code objectives.

Referenced documents should remain within their technical scope. A test method may establish material behaviour, while a system standard addresses installation and performance. Confusing those levels can lead to a product classification being treated as evidence for the whole building.

Edition control is essential because regulatory references can name particular years and amendments. Later technical developments do not automatically change the document required by a specific legal pathway. The project record should identify the edition used for each relevant standard.

Fire-safety content and design scenarios

Fire regulations can address occupants, neighbouring property and emergency responders. C/VM2's scenarios show these different concerns through separate code objectives. The design must not assume that demonstrating one objective automatically satisfies all others.

Occupant protection can involve detection, escape time, smoke conditions and route availability. C/VM2 uses some scenarios based on inspection or specified provisions and others based on fire and evacuation modelling. The chosen analysis must correspond to the scenario's requirements.

Protection of other property includes external fire spread and radiation. C/VM2's horizontal-spread scenario distinguishes sprinklered and unsprinklered cases under its specified assumptions. Those values are regulatory design inputs rather than universal descriptions of real fire behaviour.

Firefighting provisions can include vehicle access, water delivery, information and structural stability. C/VM2's firefighting scenario brings those requirements together. Treating suppression as the only concern of fire service design would omit these access and operational needs.

Robustness can also be addressed explicitly. C/VM2 requires key systems to be rendered ineffective in turn for its relevant scenario, with exemptions stated in the document. This examines whether the design still meets its objectives when a depended-upon function fails.

Approval, construction and use

The regulatory process continues beyond design documentation. IFEG describes review of construction, commissioning and changes needed as the project develops. The approved safety case must be realised in the installed systems and building arrangement.

Authorities can approve, request further information, impose conditions or refuse a proposal within their legal role. IFEG describes these possible actions in its New Zealand discussion. The fire engineer supports the technical justification but does not replace the authority's decision.

Construction changes may require supplementary analysis. If a component or layout differs from the design, the reviewer needs to know whether the evidence remains valid. Approval should not be treated as covering every later alteration automatically.

Buildings also change in use and occupancy. IFEG includes management, maintenance, alteration and change of use within the life-cycle framework. The regulatory and engineering assessment should remain connected to those actual conditions.

Limits of regulatory interpretation

Compliance is not a complete description of every possible safety objective. IFEG notes that an owner may choose to exceed mandatory requirements for property protection, continuity or other aims. Those project objectives must be distinguished from the legal minimum.

Nor do detailed provisions always express a quantified risk level. Van Rossum discusses the difference between measurable limits in measures and the broader goals they serve. An accepted risk or required performance may need to be established through the project and review process.

Older guidelines and historical code comparisons must be dated. IFEG was published in 2005, while C/VM2 is identified here as the 2025 second edition. Their descriptions should not be merged into one claim about current requirements in every jurisdiction.

A regulatory checklist should not hide interactions between systems. A door, alarm, smoke-control system and escape route can depend on one another during a fire. C/VM2's separate scenarios and robustness check help expose those dependencies but do not make every design identical.

The reliable interpretation therefore identifies the legal objective, permitted compliance route, technical evidence and building conditions. This is more informative than quoting a rule without its country, edition or scope. It also makes clear where alternative analysis is required.

A project review should start with the building's actual use and characteristics. Occupant numbers, activities, layout and fire hazards determine which provisions and scenarios are relevant. Applying a rule before establishing those facts can produce a formally quoted but irrelevant compliance argument.

The compliance route should be recorded explicitly. A reader needs to know whether the design follows an acceptable solution, a verification method or an alternative solution. Each route has different evidence requirements, and mixing their inputs without explanation can obscure which route is being claimed.

Acceptance criteria should be agreed before the final analysis. They must correspond to the objectives and the evaluation method rather than being selected only after a favourable result appears. IFEG requires them to be realistic and, for quantitative analysis, numerical.

The approval record should include the reasons behind the selected criteria and scenarios. Another reviewer should be able to identify the trial design, input data and assumptions that produced the result. This is particularly necessary where expert judgement supplies information that is not available from a standard method.

Construction and commissioning evidence should be connected to the approved documents. A listed product or installed system may differ from the analysed configuration, and a changed detail may affect several scenarios. The review should follow those differences rather than treating approval as independent of construction.

The operating manual should preserve regulatory and engineering assumptions in usable form. Maintenance, inspection and management actions must be identifiable for the people responsible for the building. This links the accepted design to the conditions under which it is expected to remain compliant.

Changes in legislation or standards may also alter the compliance context. A project should identify the requirements applicable to its approval and use rather than assuming an undated reference remains sufficient. The source edition is part of the evidence, just as the building's use and condition are.

See also

• NFPA
• Occupant load
• Prescriptive design

References

• Australian Building Codes Board. (2020). Fire safety verification method data sheets (Version 1.1). Author.
• Australian Building Codes Board, National Research Council of Canada, International Code Council, & Department of Building and Housing New Zealand. (2005). International fire engineering guidelines (2005 ed.). Australian Building Codes Board.
• Ministry of Business, Innovation and Employment. (2025). C protection from fire: Verification method C/VM2 (2nd ed.). New Zealand Government.
• Van Rossum, E. (2027). Introduction to Fire Safety Engineering. Fire Safety Academy.