When to Call the Fire Engineer

An architect can, and should, lead the fire strategy on the great majority of ordinary buildings: a house, a small office, a shop, a modest school. For these, the code's standard provisions are written to be applied directly by a competent designer, and the life-safety logic - short protected escape routes, sensible compartmentation, the right detection - is within the reach of anyone who has taken this course seriously. Leading those strategies confidently is exactly what the earlier modules were for.

But competence has an edge, and pretending it does not is where danger begins. Some buildings pose fire problems that depend on quantitative analysis - how fast smoke will fill a tall atrium, whether a crowd can clear a complex hall before conditions turn untenable, how a phased evacuation of a high-rise actually behaves - that no amount of design intuition can settle reliably. These are engineering questions, answered with modelling, calculation and specialist judgement, and getting them wrong does not produce a slightly worse building; it can produce one that kills people while appearing, on the drawings, entirely reasonable.

The professional failure is not asking for help - it is not asking when you should. The architect who presses on alone past the edge of their competence, because admitting a limit feels like weakness or because the fee is tight, is taking a gamble with other people's lives and with their own liability. The architect who says early, "this one needs a fire engineer," is doing precisely what the duty of care requires. Module 10.1 made the point in the abstract; this is its sharpest practical expression.

Calling a specialist does not hand away your role. You still lead the strategy, set the architectural moves, and own the coordination; the fire engineer brings the analysis, the modelling and the code-level judgement you do not have, and helps you justify an approach to the authority. Think of it as the same relationship you already have with a structural engineer on anything but the simplest building: you would not size a transfer beam by feel, and there are fire problems you should not size by feel either.

Fire codes offer, broadly, two routes to compliance, and understanding the difference is the key to this whole lesson. The prescriptive route - often called deemed-to-satisfy - is the familiar one: the code gives you tables and rules (travel-distance limits, required exit widths, fire-resistance periods, where sprinklers and detection are needed) and you follow them. Meet the rules for your occupancy and you are deemed to have met the underlying safety objective. It is simple, fast, predictable and entirely appropriate for the typical buildings it was written for.

The performance-based route - fire engineering, or an alternative solution - starts from the objective itself rather than the rules: it sets out what safety must be achieved (everyone can escape before conditions become untenable; the structure stands long enough; the fire service can operate) and then demonstrates, by analysis and modelling, that the specific design achieves it. A common framing is comparing ASET and RSET - the Available Safe Egress Time before a space becomes untenable against the Required Safe Egress Time people actually need - and showing a sufficient margin between them. This is specialist work, and it is how genuinely unusual buildings get designed safely.

It matters enormously that performance-based design is not a loophole or a way to dodge an inconvenient rule. It is a higher-effort, evidence-based route that typically demands more analysis, more documentation and explicit acceptance by the authority having jurisdiction - not less rigour. Used honestly it lets a tall atrium, a stadium or a historic building be made genuinely safe when the prescriptive tables simply do not fit. Used as an excuse to justify a cheaper, weaker design, it is a dangerous abuse - which is one more reason it belongs with a qualified, accountable fire engineer.

For you as the architect, the practical takeaway is diagnostic. If your building sits comfortably inside the prescriptive provisions for its occupancy and height, you can lead it - verifying every figure against the current NBC and the AHJ as always. The moment the building pushes past those provisions, or a prescriptive solution would be absurd or impossible for its form, you are in performance-based territory, and that is the signal to bring in the fire engineer rather than to improvise your own 'alternative'.

Some features of a building are reliable signals that its fire problem has outgrown prescriptive design. Height is the clearest: once a building is tall enough that people cannot simply walk out and the fire service cannot reach every floor from the ground, the strategy shifts to firefighting shafts, phased evacuation and refuge floors, and the analysis behind those is specialist work (Module 7.4). Large assembly - a hall, stadium, cinema, place of worship or mall with big crowds - raises crowd-egress questions that reward modelling rather than rules of thumb.

An atrium or any large connected open volume defeats ordinary compartmentation, because a fire on one level shares its smoke with many, so smoke-control design and its verification usually need an engineer. So does complex geometry or unusually long travel that no standard layout resolves. A phased or stay-put evacuation strategy - common in tall residential and in hospitals - is an engineered decision, not a default, and must be justified. Any alternative or performance-based solution you are contemplating is, by definition, specialist territory. And hazardous processes, high fuel loads, or heritage and retrofit constraints that make full compliance impossible all point the same way.

A useful habit is to run this list at the concept stage, not at the end. If any item is ticked - or if you simply find yourself unsure whether the prescriptive route fits - treat that as the trigger. The cost of a short early conversation with a fire engineer is tiny next to the cost, in money and in risk, of discovering at approval stage that the whole massing is unworkable, or worse, of building something unsafe because nobody flagged the question in time.

Be honest, too, about the grey zone. Plenty of buildings sit near the edge - a mid-sized building just under a height threshold, a moderately complex layout - and judgement is genuinely required. The safe default in the grey zone is to ask. A fire engineer can often confirm in one meeting that a prescriptive approach is fine, which costs little and buys certainty; whereas guessing wrong in the grey zone is exactly the kind of quiet error that produces a building that passes its inspection and still fails its people.

Bringing in a fire engineer pays off only if you do it early and openly. Early, because a specialist engaged at the concept stage can shape the plan - where the cores go, how the atrium is zoned, how the crowd flows - whereas one handed a fixed scheme near approval can only patch it, often expensively and imperfectly. The single most common waste in fire engineering is the late appointment: the architect designs in isolation, the scheme proves unworkable, and weeks are lost redesigning what an early conversation would have got right the first time.

Openly, because the engineer can only work from a truthful brief. Tell them the real occupancy and occupant numbers, the client's actual intentions for how the space will be used, the constraints you are under, and the parts of the design that are fixed versus negotiable. Share your draft fire strategy and your assumptions so they can test them rather than guess at them. A fire engineer fed an optimistic or incomplete brief will produce a confident-looking analysis of the wrong building - which is worse than no analysis at all.

Understand what the engineer delivers and where the boundary of responsibility sits. They typically provide the fire strategy's quantitative backbone - smoke-control design, evacuation timing, structural fire analysis, the justification for any performance-based approach - and help carry it through the authority's acceptance. You remain the lead designer who integrates all of it into a coherent, buildable, usable building, and who coordinates the engineer's requirements with everyone else's. Agree clearly, in the appointments, who is responsible for what, so there are no gaps of the kind Module 10.1 warned about.

Finally, treat the relationship as a dialogue, not a handover. When the engineer asks for something that complicates your plan - a wider shaft, a pressurised lobby, a limit on an opening - push for the why and understand the life-safety reason, rather than resenting the constraint or quietly value-engineering it away later. The best fire-engineered buildings come from an architect and an engineer who argue well together early and arrive at a strategy that is both safe and good architecture. That collaboration, more than any single calculation, is what keeps people alive.