Contents
- 1Purpose and levels of objectives
- 2Occupants and emergency responders
- 3Property, environment and continuity
- 4From objectives to acceptance criteria
- 5Risk, prevention and consequence
- 6Strategy and design integration
- 7Documentation and stakeholder agreement
- 8Review and limitations
- 9See also
- 10Notes
- 11References
Fire safety objectives are the outcomes that a building's fire-safety provisions are intended to achieve. They can concern occupants, emergency responders, property, neighbouring buildings, the environment, heritage or continuity of operations. Objectives provide the starting point for selecting measures and judging whether a design is acceptable.[1][2]
Some objectives come from building regulation, while others arise from other legislation or project stakeholders. They must be distinguished and recorded so that a design is not assessed against the wrong target. Non-fire goals can also influence the building and its fire risks.[1][3]
An objective is broader than a product requirement or a calculation output. It explains the intended safety result, while acceptance criteria define how that result will be evaluated. Clear objectives make it possible to compare alternative protective measures without assuming that one technology is always required.[4]
Purpose and levels of objectives
Objectives describe what is valued and what the fire-safety system must protect. IFEG identifies occupants, emergency services and property as recurring concerns. It also includes prevention of fire spread between buildings among building-regulatory objectives.[1]
At a broad level, Fire safety engineering applies scientific and engineering methods to those outcomes. The engineer selects scenarios, evidence and measures in response to them. The technical analysis is therefore a means of serving objectives, not an objective in itself.[2]
Regulatory objectives establish mandatory outcomes within a jurisdiction. New Zealand's framework, as described by IFEG, separates the legal Building Code from documents that offer ways to comply. This allows the required outcome to remain stable while different evidence or solutions are considered.[5]
Other regulatory objectives can come from occupational safety, environmental protection, fire-service or dangerous-goods requirements. These may overlap with building objectives but have their own legal context. Their applicability must be checked rather than assumed.[1]
Project objectives can extend beyond minimum regulation. IFEG gives examples including business continuity, infrastructure, corporate image, heritage and limiting releases of hazardous materials. These objectives should be explicit because they may require additional scenarios or criteria.[3][6]
Occupants and emergency responders
Occupant objectives commonly concern safe escape and avoidance of unacceptable fire effects. C/VM2's stated Building Code objective is to safeguard people from an unacceptable risk of injury or illness caused by fire. The wording belongs to the New Zealand regulatory context.[7]
A related objective is maintaining viable escape routes. C/VM2's exit-blocking scenario asks whether one or more routes remain available under its stated conditions. This turns the broad occupant objective into a particular design question.[7]
Smoke and toxicity also belong to occupant objectives. IFEG lists escape-time margin, layer height, hot-layer temperature, optical density and carbon monoxide among possible acceptance parameters. The selected criteria must match the occupants and fire scenario being analysed.[4]
Emergency-responder objectives address safe and effective operations. C/VM2 includes facilitating firefighting and rescue among its code objectives and examines access, water delivery, information and structural stability. Those needs differ from occupant evacuation even where the same systems are used.[8]
These groups should not be merged into one generic life-safety claim. An arrangement that protects occupants during evacuation may not provide safe firefighter access, and an effective suppression system may not provide intelligible warning. Separate scenarios help reveal those different requirements.[9][8]
Property, environment and continuity
Property objectives can concern the building itself, its contents or adjacent property. IFEG includes structural and fabric damage, equipment damage and fire spread between buildings among possible stakeholder concerns. These are distinct consequences requiring different evidence.[3]
C/VM2's external-spread scenario uses radiation criteria and unprotected areas to address fire spread towards other property. Its numerical values belong to that New Zealand verification method. They are not universal targets for every property-protection objective.[10]
Heritage objectives introduce the value of historic fabric and significant places. Standard building measures may have different consequences for that value, so alternatives may need assessment. The fire strategy should protect life without unnecessarily destroying what the project intends to preserve.[6][3]
Environmental objectives can include smoke toxicity and impoundment of firefighting water. IFEG lists these among possible acceptance parameters. They extend the analysis beyond immediate injury and property damage to wider releases and effects.[4]
Continuity objectives concern the ability to maintain operations and financial viability. Fire suppression or compartmentation may limit interruption, but the required recovery outcome must be defined. A building that meets minimum life-safety criteria does not automatically satisfy those additional objectives.[6][4]
From objectives to acceptance criteria
Acceptance criteria specify how the evaluation will decide whether objectives are met. They should be appropriate to the objectives, performance requirements and analysis method. IFEG calls for numerical criteria in quantitative analysis and rejects zero risk as a realistic target.[4]
Criteria can include escape-time margins, smoke conditions, structural performance, radiation, water supply and monetary loss. The list must be selected for the particular objective rather than copied indiscriminately. Each parameter should correspond to a meaningful consequence.[4]
Comparative evaluation uses a reference or prescriptive design as a benchmark. The trial design should not perform less well than that benchmark under compatible criteria. Absolute evaluation instead uses criteria agreed for the project and addresses uncertainty directly.[4][11]
Criteria should be established before the final analysis. Selecting a favourable threshold after seeing the results would obscure whether the original objective was met. The Fire Engineering Brief records these decisions and their stakeholder context.[12]
Building regulations influence but do not eliminate this translation work. Performance requirements can use terms such as adequate or appropriate, which require project-specific interpretation. IFEG recommends stakeholder involvement to reduce variation in those judgements.[13]
Risk, prevention and consequence
Fire risk connects possible fire events with their consequences and likelihood. Objectives help define which consequences matter and to whom. Without that definition, a numerical probability or fire-size estimate does not establish acceptability.[14][15]
Prevention and consequence management are complementary ways of pursuing objectives. Preventing ignition addresses the initiating event, while managing fire impact addresses events that still occur. A strategy should not assume that one branch makes the other unnecessary.[16]
The Fire safety concepts tree represents this distinction through its primary branches of preventing fire ignition and managing fire impact. It can help examine whether proposed measures address the intended objective and where gaps remain. It is a representation of professional judgements, not a guarantee of safety.[16]
Risk acceptability also involves values and uncertainty. Watts and Hall discuss scientific uncertainty, human variability and differing attitudes to risk. Stakeholders should therefore be involved in setting criteria and understanding what the analysis leaves unresolved.[14][13]
A low calculated frequency does not by itself demonstrate that objectives are met. The consequence measures, data quality and exposed population must still be examined. Similarly, a severe scenario does not establish its likelihood without an appropriate basis.[14]
Strategy and design integration
The Fire safety strategy translates objectives into a coordinated set of preventive and protective measures. It can include fuel control, compartmentation, detection, suppression, smoke control, evacuation and firefighting provisions. The selected combination should address all relevant objectives.[17]
Multiple objectives can compete in a design. Security, open layouts, natural lighting and future flexibility may change fire exposure or escape arrangements. The engineering review should integrate these aims while preserving the required fire performance.[3]
One measure can serve several objectives. Suppression may reduce occupant exposure, property damage and fire spread, but its performance depends on activation and supply. Those dependencies should be evaluated rather than claiming every benefit automatically.[18][19]
Objectives also need separate scenarios. C/VM2 evaluates life safety, external spread, surface linings, firefighting and robustness through different design scenarios. Satisfying one scenario does not remove the need to satisfy the others within that method.[9]
Robustness testing helps determine whether objectives depend too heavily on one feature. C/VM2 considers key systems ineffective in turn under its stated conditions. This can reveal whether alternative protection is needed to preserve the intended outcome.[20]
Documentation and stakeholder agreement
The Fire Engineering Brief should record the agreed objectives and their origins. Building-regulatory, other-regulatory and non-regulatory objectives can then be traced to suitable criteria. The record also shows which goals were not included in the analysis.[1][12]
Stakeholder agreement helps clarify what is valued and which trade-offs are acceptable. This is relevant where property, heritage or continuity aims extend beyond life safety. Agreement does not replace technical evidence, but it defines the questions that evidence must answer.[13][1]
Documentation should connect each objective to scenarios and acceptance criteria. A reviewer should be able to follow the path from desired outcome to design measure and evaluation result. Missing links can reveal an objective that was stated but not actually assessed.[4][9]
Operational requirements should be included when a measure depends on management. Fuel limits, staff roles, maintenance and route availability can all affect the outcome. Those requirements must be communicated to the people responsible for the building.[21][22]
Changes in ownership or project priorities can alter the desired objectives. A previous analysis may no longer address the relevant property or continuity goals. Review should distinguish changed objectives from changes in the physical building.[23]
Review and limitations
Objectives should be reviewed as the design develops. A rejected trial design can require revised measures or clarification of the acceptance basis. IFEG treats this as an iterative process rather than a one-time declaration at project start.[12]
Construction and use can affect whether the intended outcomes are realised. Installed systems must match the assessed configuration, and the building must be operated consistently with its assumptions. Approval alone does not demonstrate continuing achievement of the objectives.[21][22]
Changes of use can introduce new occupants, hazards and operational goals. IFEG calls for the existing fire evaluation to be checked in those circumstances. The original objectives and criteria may need to be revisited together with the physical analysis.[23]
No objective should be used to claim absolute safety. IFEG and the regulatory examples recognise uncertainty and reject zero risk as a practical acceptance criterion. A defensible assessment states the achieved performance and the conditions under which it was demonstrated.[13][4]
Clear objectives therefore remain important throughout the building life cycle. They guide the initial strategy, the evaluation and later management. Without them, technical outputs can appear precise while failing to answer what the fire-safety work was intended to achieve.[24][1]
An objective-to-evidence matrix can help expose omissions in a design review. Each objective can be linked to the exposed group, scenario, measure, criterion and supporting evidence. An objective without a corresponding assessment would then remain visibly unresolved.[4][9]
Occupant objectives should be tested for the population actually expected. Sleeping occupants, visitors and people needing assistance can have different response times and support requirements. A general statement about protecting people does not show that those groups have been represented.[25][26]
Property objectives also need a defined subject. Protection of the building frame, contents, neighbouring property and historic fabric can lead to different scenarios and acceptance measures. Grouping them under one damage label would hide those differences.[3][10]
Acceptance criteria should not be confused with the measures selected to achieve them. A smoke-layer criterion describes an environmental condition, while a fan is one possible means of influencing it. Keeping that distinction allows different systems to be compared against the same objective where appropriate.[4][27]
Uncertainty should remain visible in the objective assessment. A model can produce an exact-looking time or temperature while relying on uncertain fire, occupant and equipment inputs. The result should be interpreted through sensitivity and evidence limits rather than presented as a guaranteed outcome.[28][14]
Redundancy can support objectives where failure would have severe consequences, but it must be genuine. Two components that depend on the same power, detection or control path may fail together. C/VM2's robustness scenario provides a method-specific way to examine key-system failures.[20][19]
Review after commissioning should examine whether the assessed objectives were translated into operational requirements. Staff instructions, fuel limits and maintenance actions need to match the analysis. A technically accepted design can otherwise lose its intended performance through everyday use.[21][22]
The record should also identify objectives that remain open because evidence is unavailable. Such limitations should not be removed by silently narrowing the objective or inventing a criterion. They belong in the project decisions and, where relevant, in the scope of further analysis. Explicitly recording those limits preserves the meaning of the objective and keeps unresolved evidence needs visible during later review.[29][15]
See also
Notes
- ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 Australian Building Codes Board et al. (2005), pp. 1.2-7–1.2-8.
- ↑ 2.0 2.1 Australian Building Codes Board et al. (2005), pp. 0.3-1–0.3-3.
- ↑ 3.0 3.1 3.2 3.3 3.4 3.5 Australian Building Codes Board et al. (2005), p. 1.2-8.
- ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 Australian Building Codes Board et al. (2005), pp. 1.2-25–1.2-26.
- ↑ Australian Building Codes Board et al. (2005), p. 0.2-2.
- ↑ 6.0 6.1 6.2 Australian Building Codes Board et al. (2005), p. 0.3-3.
- ↑ 7.0 7.1 Ministry of Business, Innovation and Employment (2025), p. 37.
- ↑ 8.0 8.1 Ministry of Business, Innovation and Employment (2025), p. 53.
- ↑ 9.0 9.1 9.2 9.3 Ministry of Business, Innovation and Employment (2025), pp. 7–9.
- ↑ 10.0 10.1 Ministry of Business, Innovation and Employment (2025), pp. 44–45.
- ↑ Australian Building Codes Board (2020), pp. i–ii.
- ↑ 12.0 12.1 12.2 Australian Building Codes Board et al. (2005), pp. 1.2-2–1.2-3.
- ↑ 13.0 13.1 13.2 13.3 Australian Building Codes Board et al. (2005), pp. 0.2-7–0.2-8.
- ↑ 14.0 14.1 14.2 14.3 Watts and Hall (2002), pp. 5-158–5-160.
- ↑ 15.0 15.1 Van Rossum (2027), §1.2.
- ↑ 16.0 16.1 Watts and Hall (2002), pp. 5-158–5-159.
- ↑ Australian Building Codes Board et al. (2005), pp. 1.2-9–1.2-10.
- ↑ U.S. Nuclear Regulatory Commission (2005), p. 10-2.
- ↑ 19.0 19.1 Australian Building Codes Board (2020), p. 131.
- ↑ 20.0 20.1 Ministry of Business, Innovation and Employment (2025), pp. 58–59.
- ↑ 21.0 21.1 21.2 Australian Building Codes Board et al. (2005), pp. 0.3-7–0.3-8.
- ↑ 22.0 22.1 22.2 Australian Building Codes Board et al. (2005), pp. 1.8-13–1.8-14.
- ↑ 23.0 23.1 Australian Building Codes Board et al. (2005), p. 0.3-8.
- ↑ Australian Building Codes Board et al. (2005), pp. 0.3-4–0.3-5.
- ↑ Ministry of Business, Innovation and Employment (2025), pp. 29–31.
- ↑ Proulx (2002), p. 3-350.
- ↑ Cooper (2002), p. 3-219.
- ↑ Australian Building Codes Board et al. (2005), pp. 1.2-24–1.2-25.
- ↑ Australian Building Codes Board et al. (2005), pp. 1.8-9–1.8-11.
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.
- Cooper, L. Y. (2002). Smoke and heat venting. In P. J. DiNenno (Ed.), SFPE handbook of fire protection engineering (3rd ed.). National Fire Protection Association.
- Ministry of Business, Innovation and Employment. (2025). C protection from fire: Verification method C/VM2 (2nd ed.). New Zealand Government.
- U.S. Nuclear Regulatory Commission. (2005). Fire dynamics tools: Quantitative fire hazard analysis methods for the U.S. nuclear regulatory commission fire protection inspection program (NUREG-1805). Author.
- Van Rossum, E. (2027). Introduction to Fire Safety Engineering. Fire Safety Academy.
- Watts, J. M., Jr., & Hall, J. R., Jr. (2002). Building fire risk analysis. In P. J. DiNenno (Ed.), SFPE handbook of fire protection engineering (3rd ed.). National Fire Protection Association.