Fire Alarm Zoning Is About Finding Fires

A fire detection zone is not a folder.

It isn't there to make the panel configuration look tidy. It isn't there because you've got spare zones available. It isn't there because splitting every corridor, cupboard and riser into its own zone makes the programming easier to follow.

Its job is much simpler than that.

It helps somebody find the fire.

That somebody might be the building manager. It might be security. It might be an engineer attending a callout.

More importantly, it might be a firefighter who has never stepped foot in the building before.

BS 5839-1:2025 is pretty clear on this. The commentary to Clause 12 says fire detection zones are there to direct those responding to a fire alarm signal, particularly the fire and rescue service, towards the area of the fire.

It also makes a point that often gets forgotten on addressable systems: zone indication is still required because it can provide a quicker, broader indication of where the fire is than an individual addressable device description.

So why do we keep designing zones around what looks nice on the panel?

A Fire Detection Zone Is About Location

BS 5839-1 defines a fire detection zone as a subdivision of the protected premises where a fire can be indicated separately from a fire in another subdivision.

The accompanying note explains why: to assist with locating the fire, evacuation and firefighting.

That's the point.

It's geographical information.

There are some basic rules around that principle too.

Where the total floor area of the building exceeds 300 m², a fire detection zone should normally be restricted to a single storey.

For zones containing automatic detectors, the zone should not normally exceed 2,000 m².

For non-addressable automatic detection, the search distance should not exceed 60 m.

Enclosed stairwells, lift wells and similar enclosed flue-like structures containing automatic detectors are treated as separate fire detection zones.

There is logic behind all of that.

The person responding to the alarm needs to be able to work out where they're going and find the fire without wandering around half the building.

Addressable Detection Didn't Make Zoning Redundant

This seems to be where some of the confusion starts.

On an old conventional system, the zone was pretty much all you had.

You got:

FIRE
ZONE 3

and off you went to Zone 3.

Addressable systems changed that.

Now you might get:

FIRE
ZONE 03 - LEVEL 3

OPTICAL SMOKE DETECTOR
LEVEL 3 EAST CORRIDOR
OUTSIDE FLAT 312
LOOP 2 ADDRESS 147

That's obviously much better.

You know the general area and you know exactly which device has operated.

But those are two different pieces of information doing two different jobs.

The zone tells you the geographical area.

The device text narrows it down.

BS 5839-1:2025 actually goes out of its way to preserve that distinction. Clause 12.4 requires zone indication at the CIE even where addressable text information is available.

So no, the fact that your panel can tell you exactly which detector has activated doesn't mean fire detection zoning has suddenly become pointless.

If anything, addressable systems give us less excuse for abusing zones, because we already have another mechanism for providing the fine detail.

Zone 47 Probably Didn't Need to Exist

Take a fairly ordinary residential building.

Level 3 has a protected corridor serving a number of flats. It is comfortably within the permitted zone area and the layout is straightforward.

You could have:

ZONE 03 - LEVEL 3

Then your devices could say:

L03 EAST CORRIDOR OUTSIDE FLAT 312
L03 WEST CORRIDOR OUTSIDE FLAT 326
L03 LIFT LOBBY
L03 ELECTRICAL CUPBOARD

Simple.

Anyone looking at the panel knows the fire is on Level 3. The address text then tells them where on Level 3.

Instead you sometimes find this:

ZONE 31 - L03 EAST CORRIDOR
ZONE 32 - L03 WEST CORRIDOR
ZONE 33 - L03 LIFT LOBBY
ZONE 34 - L03 ELECTRICAL CUPBOARD
ZONE 35 - L03 RISER

There might be a perfectly good design reason for doing that.

But there also might not be.

And "it makes the panel easier to navigate" isn't, by itself, a good design reason.

Easier for who?

The person programming it?

The service engineer?

Because neither of those people are necessarily the person standing in front of that panel during a fire.

Device Text Exists for a Reason

If Detector 147 is outside Flat 312, write that in the device text.

You don't need:

ZONE 47 - OUTSIDE FLAT 312

just to tell somebody that Detector 147 is outside Flat 312.

That's what addressable location text is for.

A sensible arrangement might be:

ZONE 03 - LEVEL 3

SMOKE DETECTOR
EAST CORRIDOR OUTSIDE FLAT 312

Now you've got both levels of information.

The fire is on Level 3.

More specifically, the detector outside Flat 312 in the east corridor has operated.

That's useful.

Turning every room, corridor section and cupboard into another fire detection zone often isn't adding useful information. You're just moving information that belongs in the device description into the zoning structure.

The 60 Metre Rule Makes the Point Even Better

There is an interesting difference in BS 5839-1:2025 between addressable and non-addressable systems.

For non-addressable automatic detection, the recommended maximum search distance within a zone is 60 m.

On an addressable system that particular restriction doesn't have to apply, but only where some important conditions are met.

The CIE needs to display clear location information for at least the first detector to operate, without somebody having to dig through menus.

And crucially, that information, together with anything provided at or next to the panel, needs to be good enough for firefighters unfamiliar with the building to proceed to the location of the fire.

Read that again.

Not:

"Good enough for the commissioning engineer to understand."

Not:

"Good enough if you've worked on the site for five years."

Not:

"Good enough once somebody explains what Core B means."

Firefighters unfamiliar with the building.

That's a pretty good test for your entire approach to fire alarm zoning and device descriptions.

Your Cause and Effect Isn't an Excuse Either

This is probably the one that annoys me most.

Some panels make cause and effect really easy to program by zone.

So somebody thinks:

I'll just create another fire detection zone for these devices because they need to do something different.

No.

Or at least, not automatically.

If that area genuinely needs to be a separate geographical fire detection zone, fine.

If you're only creating the zone because it makes your cause and effect easier to write, you're using the wrong tool for the job.

Most decent addressable systems give you other ways of grouping things.

Depending on the manufacturer that might be:

• input groups;
• output groups;
• action groups;
• sectors;
• logic groups;
• virtual groups;
• dependencies;
• rules.

That's what those functions are there for.

A group used to trigger an AOV isn't automatically a fire detection zone.

A set of detectors used to ground a lift isn't automatically a fire detection zone.

Devices involved in the same smoke control sequence aren't automatically a fire detection zone.

The geography of the building shouldn't change because your programming software is easier to use that way.

Loops Aren't Zones

Same problem, different flavour.

ZONE 1 - LOOP 1
ZONE 2 - LOOP 2
ZONE 3 - LOOP 3

Why?

A loop is an engineering concept.

It's useful when you're servicing the system, fault finding or looking through the configuration.

It means absolutely nothing to a firefighter trying to find a fire.

If Loop 2 happens to serve Level 2 exclusively, then fine, the two might happen to align.

But the geographical zoning should exist because Level 2 is the geographical area you're trying to identify, not because somebody happened to wire it onto Loop 2.

The panel already knows which loop the device is connected to.

You don't need to sacrifice useful operational information to tell an engineer something they can already find.

Fire Detection Zones and Alarm Zones Aren't the Same Thing

This gets muddled surprisingly often too.

A fire detection zone tells you where the fire signal has originated.

An alarm zone is an area where the fire alarm warning can be controlled independently from another area.

They're both geographical divisions, but they're doing different jobs.

Alarm zoning becomes particularly relevant in buildings using staged or phased evacuation, where one part of the building might receive an Evacuate signal while another receives an Alert signal or remains unaffected at that stage.

BS 5839-1 even deals with how the two relate. A fire detection zone shouldn't contain more than one alarm zone, although an alarm zone can contain several fire detection zones.

Again, separate concepts.

Trying to use one universal set of "zones" for detection, alarm operation, smoke control, lift interfaces, output programming and whatever else the system happens to control is where configurations start becoming a mess.

Think About the Person Standing at the Panel

Engineers naturally look at systems like engineers.

We know what loops are.

We understand addresses.

We know what nodes, sectors, groups and outputs are.

We can probably look at the configuration and work out why Zone 46 exists.

The person responding to a fire shouldn't need to do any of that.

Imagine walking into a building you've never seen before and finding this:

FIRE
ZONE 46
L2 CORE B SD 2047

There is technically information there.

But where are you actually going?

What's Core B?

Does L2 mean Level 2 or Loop 2?

Where is Zone 46?

Which staircase gets you there?

Is the detector in a corridor, room, riser or cupboard?

Now compare it with:

FIRE
ZONE 08 - LEVEL 8 EAST

SMOKE DETECTOR
EAST CORRIDOR OUTSIDE FLAT 812

You don't need to be a fire alarm engineer to understand the second one.

That's the whole point.

The Zone Plan Isn't Decoration

This is another area where the 2025 standard is pretty blunt.

The primary indication of where a fire signal has come from should be the zone indication.

The CIE should also be accompanied by a diagrammatic representation showing the building entrances, main circulation areas and division into zones. That can be an illuminated mimic, an appropriate VDU arrangement or a correctly orientated printed zone plan.

The commentary explains exactly why.

The purpose is to give people responding to the alarm, including staff and firefighters, unambiguous information about the location of the fire.

It even notes that investigations into fatal fires have identified cases where the absence of a suitable zone plan contributed to the outcome.

So the zone plan isn't something you knock up at the end because the commissioning certificate needs one.

It's part of the operational interface.

If the panel says:

ZONE 12 - LEVEL 4 WEST

you should be able to look at the zone plan, immediately find Level 4 West and understand how that relates to the building.

If your zone plan looks like somebody emptied a packet of highlighters over an architectural drawing because you've created 96 tiny zones, ask yourself whether you've actually made anything safer.

More detail isn't always more useful.

Sometimes it's just more shit to process while something is on fire.

There Is Such a Thing as Too Little Zoning

This isn't an argument for making every floor one zone and calling it a day.

Obviously not.

A huge floorplate with several wings, compartments and complicated circulation might need several fire detection zones.

Large industrial buildings can need significant subdivision.

Stairwells and lift wells have specific considerations.

A hospital, shopping centre or large commercial complex clearly isn't going to be treated the same way as a straightforward ten-storey residential block.

BS 5839-1 gives us sensible limits for exactly that reason.

The question isn't:

How few zones can I get away with?

It's:

What zoning makes the location of a fire clear to the people who actually need to find it?

Sometimes that's one zone per floor.

Sometimes it's five.

The building should answer that question, not the configuration software.

There Is Such a Thing as Too Much Zoning Too

We have a weird habit in this industry of assuming that more granularity must mean better engineering.

It doesn't.

You can take:

LEVEL 4

and split it into:

LEVEL 4 EAST
LEVEL 4 WEST

Then:

LEVEL 4 EAST NORTH CORRIDOR
LEVEL 4 EAST SOUTH CORRIDOR

Then:

LEVEL 4 EAST NORTH CORRIDOR SECTION A
LEVEL 4 EAST NORTH CORRIDOR SECTION B

Keep going and eventually the zoning system itself becomes something the user has to decipher.

What have you achieved?

On an addressable system, the individual detector was already identifiable.

The zone is there to provide geographical context.

If the zone description becomes as detailed as the individual device location, you've probably just duplicated information while making the system harder to understand.

The Fire Alarm System Has More Than One User

This is the bit engineers need to think about more often.

The system wasn't installed solely for the person commissioning it.

The commissioning engineer needs addresses, loops, cause and effect, groups, outputs and dependencies.

The maintenance engineer needs sensible circuit information, good device descriptions and useful fault information.

Building management needs understandable controls and clear indications.

Security staff need to know what has happened and where.

The fire and rescue service needs to work out where the fire is and how to get there.

Those requirements overlap, but they aren't the same.

A configuration can be lovely to work on as an engineer and still be awful to use during an actual fire.

Keep Different Things Separate

A good addressable system can have several different structures sitting over the same devices.

For example:

FIRE DETECTION ZONE
Level 06 East

DEVICE TEXT
Smoke Detector - East Corridor Outside Flat 612

LOOP
Panel 2 / Loop 1

INPUT GROUP
Level 06 Residential Detection

CAUSE AND EFFECT GROUP
Level 06 Smoke Control

OUTPUT GROUP
Level 06 AOV Sequence

ALARM ZONE
Levels 06 and 07

None of those things need to be identical.

They answer different questions.

Where is the fire?

Fire detection zone.

Exactly what operated?

Device address and text.

How is it connected?

Loop and address.

What logic does it participate in?

Input or cause and effect group.

What equipment should operate?

Output group.

Where should a particular alarm warning be given?

Alarm zone.

Once you start forcing all of those jobs into the fire detection zoning, you aren't simplifying the system.

You're just making one bit of the configuration do five different things badly.

Don't Design the Building Around the Panel

There is a line right at the beginning of BS 5839-1:2025 that applies far beyond zoning.

The fire alarm system is supposed to support the building's fire evacuation strategy.

The evacuation strategy isn't supposed to be designed around a predetermined fire alarm system.

The same principle applies here.

The building comes first.

The fire strategy comes next.

The fire alarm design supports that.

Then the panel configuration implements the design.

Not the other way around.

You shouldn't end up with:

This panel is easier to program if I split these areas into separate fire detection zones, so these areas are now separate fire detection zones.

That's backwards.

If you need additional groups to implement the cause and effect, create additional groups.

If you need different output logic, configure different output logic.

If the equipment genuinely can't implement the required design without mangling the geographical zoning, maybe the equipment isn't right for the job.

The panel is a tool.

It doesn't get to redesign the building.

Bad Zoning Gets Worse With Age

This stuff becomes even more obvious ten years later.

The original commissioning engineer knew exactly why everything was set up the way it was.

Then they left.

The maintenance company changed.

Then it changed again.

Rooms got renamed.

Devices were replaced.

Another panel was added.

Somebody changed the cause and effect.

Nobody updated half the drawings.

The original design information disappeared into a filing cabinet somewhere.

What's left?

The panel configuration and the zone plan.

Simple geographical descriptions survive that quite well.

LEVEL 5 WEST

will probably still mean Level 5 West in twenty years.

Some bizarre zoning arrangement created because it made a particular version of some manufacturer's programming software easier to work with probably won't.

Sometimes Boring Is Better

Not every building needs clever zoning.

If you've got a straightforward ten-storey building and the design permits a straightforward arrangement such as:

ZONE 01 - GROUND FLOOR
ZONE 02 - LEVEL 01
ZONE 03 - LEVEL 02
ZONE 04 - LEVEL 03
ZONE 05 - LEVEL 04
ZONE 06 - LEVEL 05
ZONE 07 - LEVEL 06
ZONE 08 - LEVEL 07
ZONE 09 - LEVEL 08
ZONE 10 - LEVEL 09
ZONE 11 - LEVEL 10

with the necessary separate zones for stairs, lift wells and any other areas that require them, that's not lazy engineering.

It's understandable.

It's easy to put on a zone plan.

It's easy for building staff to understand.

It's easy for the next engineer to understand.

And, most importantly, it's easy for somebody who has never seen the building before to understand.

That's a far better measure of whether the zoning is good than how tidy the configuration looks on your laptop.

Ask the Right Question

When you're designing or reviewing fire alarm zoning, don't start with:

How do I want to organise these devices on the panel?

Start with:

If this detector goes into fire at 03:00, can somebody who doesn't know this building work out where to go?

Can they understand the zone description?

Can they find it immediately on the zone plan?

Can they work out how to physically get there?

Does the zone represent a sensible geographical area?

Does the addressable device text then narrow that location down properly?

That's what matters.

Because if your zoning makes perfect sense to the engineer who programmed the panel but needs explaining to the person responding to the fire, you've designed it for the wrong person.

A fire detection zone is there to help somebody find a fire, not to make your panel screen look neat.