Civil Defence approval is the critical path, not the closing task

On most projects the life safety systems are drawn early, procured in the middle and thought about seriously at the end. That order works until the approval, at which point the programme discovers that a decision taken in month three cannot be undone in month eighteen without opening ceilings.

The UAE Fire and Life Safety Code of Practice governs detection, alarm, voice evacuation and the interfaces that make them act on the building. Civil Defence approval conditions occupancy, so the building does not open until the system is accepted. That single fact should determine when the design decisions are made, and usually does not.

The three decisions taken too late

Which authority approves the work. It depends on where the building sits. Dubai Municipality, Trakhees for certain Dubai free zones, and the authorities in Abu Dhabi and the northern emirates each run their own permitting sequence with their own submission requirements. The route is confirmed at design, from the site's actual jurisdiction, rather than carried over from the last project the team delivered.

Whether the product is approved. Products and installers working on life safety systems are subject to approval in their own right. A specification that names an excellent device with no local approval is a programme risk long before it is a technical question, and substituting late means resubmitting. Approval status belongs in the procurement check alongside lead time, not in the commissioning phase.

What the system is supposed to do. The cause and effect matrix is the document the approval turns on: what happens to each door, damper, lift, shutter and ventilation zone on each alarm condition. It is agreed with the approving authority, not settled between subcontractors in the weeks before witness testing. When it is written late, it is written by whoever is available rather than by the people who own the systems it commands.

Where the interfaces get lost

A single controlled door can involve ironmongery, an electrical supply, an access control head and a fire alarm interface, supplied under three or four separate packages. On the drawings it is one door. In the contract it is a boundary, and boundaries are where responsibility for the interface quietly fails to sit with anyone.

The same pattern repeats at lift controllers, at ventilation and smoke control, at shutters and at any integration between the alarm and a building management system. What makes them survive is not technical difficulty. It is naming an owner for each interface, in writing, at design, and testing each one as an interface rather than testing each system separately and assuming the join works.

What witnessed testing actually needs

Demonstration, not documentation. Every line in the cause and effect matrix, proved on the installed system, with the result recorded against the line it belongs to. Preparing for that late produces the familiar sequence of partial tests, retests and a handover pack assembled after the event.

Preparing for it early costs almost nothing: the matrix exists, each line has an owner, and the tests are run once as construction completes rather than three times under programme pressure.

What to agree before the design is fixed

• The approving authority for this specific site, and its submission requirements.
• Approval status confirmed for every life safety product named in the specification.
• A cause and effect matrix agreed with the authority, not drafted for it.
• A named owner for every interface between packages, in the contract rather than in a meeting.
• The witnessed test schedule, mapped line by line to the matrix.

None of that is difficult. All of it is much cheaper in month three than in month eighteen, and the building opens on the date it was supposed to.