Fire Safety Standards: EN, NFPA and ISO

Combining EN, NFPA and ISO references in one paragraph can create more ambiguity, not more safety.

This guide shows how to establish a code hierarchy, verify current editions and connect product evidence to the actual curtain application.

EN, NFPA and ISO Are Not Interchangeable Labels

International projects may reference European EN standards, NFPA codes and standards, ISO publications, national regulations and authority-specific requirements. These documents can address different parts of the problem: product testing, classification, system design, installation, inspection or integrated testing. Listing several acronyms in a specification does not create a coherent compliance route.

The project should state the jurisdiction, adopted building and fire codes, authority requirements and contract standard hierarchy. Product evidence must then be checked against the exact application. For smoke barriers, BS EN 12101-1 is a recognised European specification. NFPA 92 addresses smoke-control system design topics, while ISO committees publish a wider family of smoke and heat control standards.

Check Edition, Scope and Evidence

Standards are revised. A document number without an edition or adoption status can leave bidders interpreting different requirements. The specification should identify the applicable edition where the contract demands it, while the design team confirms whether national adoption, amendments or authority rules modify that reference.

Evidence review should identify the tested assembly, classification, dimensions, installation arrangement, permitted field of application and issuing body. A certificate logo or catalogue statement is not enough to show that a specific curtain configuration satisfies a project requirement.

Build an Evidence Route, Not an Acronym List

For each requirement, identify the controlling source. A national regulation may establish the legal objective; a fire strategy may define the performance needed at a particular opening; a product standard may describe test and classification methods; an installation code may guide application; and an integrated-testing standard may address system interfaces. These documents should form a traceable route rather than a decorative list.

International tenders should also separate “equivalent” from “identical.” Evidence issued under another standard family may be technically valuable, but equivalence is a project and authority decision. Suppliers should not be asked to self-declare that two classification systems mean the same thing without an agreed assessment route.

Create a standards register and review it at design freeze, tender clarification and submittal approval. Record revisions and authority comments. When a standard changes during a long project, the contract team can then decide which edition governs and whether the technical change affects the design, evidence or commissioning plan.

What a Useful Technical Enquiry Contains

A useful enquiry identifies the project country and authority, building use, opening schedule, plans and sections, required classification and duration, mounting substrate, ceiling constraints, control cause-and-effect and programme. Include the relevant specification clauses and any preferred evidence format. This information allows the manufacturer to flag application limits, interface risks and missing decisions before price becomes the only comparison. If requirements are still being developed, mark assumptions clearly and assign the design team to confirm them; a supplier proposal should not silently become the project fire strategy. State whether installation, access equipment, power wiring, alarm interfaces, commissioning, witness testing and operator training belong to the curtain package so quotations remain technically comparable.

Create a Project Standards Matrix

Record each document’s purpose, edition, contractual status, responsible reviewer and affected package. Resolve conflicts before tender rather than asking suppliers to guess the intended hierarchy.

Specifier and Project-Team Checklist

• Record the adopted code basis, authority requirements and project-specific fire-strategy objective before selecting a product.
• Define the required classification, duration, dimensions and field of application for every curtain location.
• Coordinate structure, head-box space, guides, finishes, services, power, controls and safe maintenance access on shared drawings.
• Verify that test and classification evidence covers the proposed assembly rather than a similar marketing name.
• Write the alarm, power-loss, manual-control, delay, reset and status-feedback logic into the cause-and-effect matrix.
• Witness integrated tests, close deviations and hand over as-built drawings, evidence, test records and maintenance instructions.

Common Coordination Mistakes

Treating a catalogue as the design

Product literature can describe a system, but it does not establish the project objective, authority acceptance or application limits.

Reviewing disciplines in isolation

A curtain package touches architecture, structure, electrical controls, fire alarm, smoke control and operations. Late coordination creates avoidable risk.

Accepting evidence by headline only

A test duration or certification logo must be traced to the exact assembly, classification, dimensions and installation arrangement.

Official References and Currency Note

A catalogue statement is not a project approval. Confirm the adopted code, the current standard edition, the approved fire strategy and the exact scope of the product evidence.

• BSI — BS EN 12101-1 smoke barriers
• NFPA — NFPA 92 Smoke Control Systems
• ISO — Smoke and heat control committee

This article is general technical guidance, not a project-specific compliance decision. The authority having jurisdiction, appointed fire engineer, approved fire strategy and current product evidence govern the final design.

Frequently Asked Questions