Fire Alarm Testing Logs: What Dubai Civil Defence Actually Wants to See

Every building manager we speak to in Dubai knows the 2023 UAE Fire and Life Safety Code requires weekly testing of fire detection and alarm systems. Far fewer know what a Civil Defence inspector actually opens when they ask to see the log. It is not a folder of PDFs. It is not a spreadsheet someone updates on a Friday afternoon before the auditor arrives. It is a specific set of fields, tested at a specific frequency, retained for a specific period, and signed off by a specific person — all in digital format. Get any one of those wrong and the entire log can be rejected, which means every test behind it counts for nothing.

Why the Log Itself Is Now the Compliance Instrument

Under the 2018 code, the fire alarm test log was a maintenance record. Under the 2023 code, it is an audit exhibit. The distinction matters. A maintenance record just needs to show the work happened. An audit exhibit needs to prove, to a third party who was not present, that the work happened correctly, on time, on every device, and that the results were reviewed by someone accountable. That is a much higher bar, and it is why paper logs and ad hoc spreadsheets are now routinely flagged during third-party fire safety audits — the ones the code requires every 12 months for commercial buildings and every 24 months for residential.

The financial exposure is real. We have seen audit reports come back with a "non-conformance" flag purely on log format, triggering a 30-day remediation window before resubmission to Civil Defence. Miss that window and you are into compliance notice territory, with fines starting around AED 10,000 per violation. None of that requires an actual fire safety failure — it just requires a log that does not hold up.

What a Compliant Digital Log Actually Contains

Strip away the paperwork and a defensible weekly fire alarm test log needs seven things, every single week, for every device or zone:

• Unique device or panel ID. Not "3rd floor detector" — the actual asset tag or panel address, matched to your as-built fire alarm schematic.
• Test date and time, machine-stamped. A manually typed date is not evidence. The system that generates the log must timestamp the entry itself.
• Test type and result. Functional test, smoke test, or manual call point activation — and whether the device responded within spec.
• Technician identity and license reference. Civil Defence wants to know a qualified person performed the test, not just that "a test happened."
• Evidence photo or system export. A photo of the panel readout or an automated export from the fire alarm control unit, not a hand-written note.
• Fault status and remediation timestamp. If a device fails, the log must show when it failed and when it was fixed — an open fault with no closure date is an automatic red flag.
• Sign-off by a named, accountable individual. Usually the facilities manager or a designated fire safety officer, not the technician who ran the test. This separation of duties is what auditors look for first.

Retention is not negotiable either. The code requires these records to be kept for a minimum of five years, and they must be producible on request — not "we'll dig it out of an old inbox," but retrievable within the same working day.

The Five Mistakes That Fail an Audit

We review a lot of test logs during onboarding, and the same five failures show up on almost every building that has never used a dedicated compliance platform.

• Gaps in the weekly cadence. A missed week with no explanation is worse than a failed test with a documented fix. Auditors read gaps as evidence the testing simply did not happen.
• Non-standardised formats across buildings. If your portfolio spans five towers and each one logs tests differently — one in Excel, one in a WhatsApp group, one on paper — Civil Defence treats that as an absence of a functioning compliance system, not five separate compliant ones.
• Missing or inconsistent device IDs. Without a stable ID scheme, an auditor cannot confirm every detector on the as-built drawing was actually tested. This is the single most common reason a log gets sent back.
• No evidence photos or exportable proof. A log entry that just says "Zone 4 – Pass" with no supporting image or system export is functionally a paper log wearing a digital costume.
• No documented sign-off chain. If the same person tests, records, and approves their own work, the log fails the separation-of-duties test built into the code's intent, even if every individual test genuinely passed.

How This Ties Into the RERA Digital-Records Mandate

Fire alarm testing logs do not exist in isolation. RERA's digital-records mandate requires Dubai property managers to maintain all compliance and maintenance records — fire safety included — in a digital, auditable format accessible to both the owner and the regulator. A building that satisfies the 2023 Fire Code's weekly testing requirement but keeps that data in a format RERA cannot ingest or verify is still exposed. We have seen buildings pass their Civil Defence fire audit and still receive a RERA compliance notice in the same quarter, because the underlying records lived in two disconnected systems with two different formats.

The practical implication is that your fire alarm test log cannot be a standalone tool. It needs to sit inside the same digital record of the building that covers maintenance work orders, contractor evidence, and prior audit findings, so that a single export satisfies both Civil Defence and RERA without reformatting anything.

How Herman Automates the Weekly Log

This is precisely the gap a platform like Herman is built to close. Herman assigns every fire alarm device a permanent ID linked to your as-built schematic, prompts the assigned technician for the weekly test on schedule, requires a photo or system export before the entry can be submitted, and routes every completed test to a named approver for sign-off — automatically flagging any device that has gone more than seven days without a logged test. Faults are tracked from detection to remediation with timestamps on both ends, and the entire five-year retention requirement is handled without anyone needing to remember where last year's file is stored. When a Civil Defence inspector or RERA auditor asks for the record, it is one export, already in the format they expect, because it was built to that format from the first test onward — not reformatted the week before the audit.

If you are still reconciling a spreadsheet against a WhatsApp group of technician photos, the fix is not more discipline. It is removing the manual steps where gaps and inconsistencies get introduced in the first place. Talk to the HermanWa team about auditing your current fire alarm testing process against both the 2023 code and the RERA digital-records mandate.

— The HermanWa Team