- Contractor approval and the 24x7 connected monitoring are two separate arrangements, often held by two different companies.
- Verify approval by reference number and validity date, check the scope, and confirm the approved legal entity matches your invoices.
- A dropped monitoring link produces no fault at the panel, because the panel cannot see the far end of the path.
- Only an end-to-end test with confirmation from the receiving end proves the signal arrives.
- Approval is a floor, not a ranking; it says nothing about panel-brand authorisation, measurement or defect recording.
"Are you DCD approved?" is the question every building asks a contractor, and it is not specific enough to be useful. Approval is not one thing. A company can hold approval to maintain fire systems and hold nothing at all in relation to the 24x7 connected monitoring, and both answers are honestly described as "yes, we are approved".
Approved for what, exactly.
That ambiguity is where buildings get caught. The maintenance contract is in place with an approved contractor, the alarm panel works, and the connection to Dubai Civil Defence's round-the-clock monitoring is either not live or belongs to a provider nobody in the building can name.
In short: contractor approval and the 24x7 connected monitoring are two separate arrangements, frequently held by two different companies. Verify approval by reference number and validity rather than by certificate image, and prove the monitoring signal end to end rather than accepting that the system is connected. A dropped link produces no fault on the panel.
Two different things called approval
Contractor approval is permission to design, install or maintain fire protection systems in the emirate. This is what most people mean, and it is what your AMC depends on.
The 24x7 connected monitoring is a separate arrangement. Dubai's fire alarm systems are linked to Civil Defence so an alarm reaches the authority directly rather than waiting on a phone call. That link runs through a gateway or communicator at your panel, over a subscribed service, and it is provided and maintained under its own arrangement.
A building needs both. They are frequently held by different companies, and the seam between them is where responsibility goes missing. The panel is the alarm contractor's. The communicator is the monitoring provider's. The signal path crosses both, and when it drops, each can reasonably say the part they own is working.
QSERV tests the signal end to end, confirms it arrives, and tells you in writing who owns each part of the path.
How to verify an approval rather than believe one
Approval claims are easy to make and easy to check, and almost nobody checks.
- Ask for the approval reference number, not a certificate image. A number can be verified; a PDF can be old.
- Check the validity date. Approvals expire. Work carried out under a lapsed approval is a problem you inherit.
- Check the scope. Approval covers defined activities. A company approved for extinguisher servicing is not thereby approved for alarm system work.
- Check the name matches. The approved entity and the company on your contract and invoices should be the same legal name, not an affiliate.
- Confirm it again at renewal, because the approval you verified two years ago is not evidence about today.
That list takes one email. It removes most of the risk in this category.
| What you are checking | Weak evidence | Adequate evidence |
|---|---|---|
| Contractor approval | A logo on a letterhead | Reference number, current validity date, matching legal entity |
| Scope of approval | "We do everything" | The listed activities, compared against your actual scope |
| Monitoring connection | "It is connected" | An end-to-end signal test with confirmation from the receiving end |
| Who owns the communicator | Assumed to be the alarm contractor | Named provider, named contract, known renewal date |
| Subscription status | Never discussed | Current, with a diarised renewal owner inside your organisation |
The failure nobody sees
Here is the stance, from the buildings we are called into. A dropped monitoring connection is the most common serious fire safety failure we find, and it is completely invisible from inside the building.
The reason is structural rather than negligent. Your fire alarm panel is designed to tell you about faults on its own loops and devices. The path from the communicator onward to Civil Defence is not something the panel can see the far end of. The panel says normal because, as far as the panel is concerned, everything is normal.
So a link can lapse through a subscription that quietly expired, a communications change during a building IT upgrade, or a fit-out that disturbed a cable, and nothing in the building announces it. The alarm still sounds locally. It simply stops reaching anybody.
> A fire alarm panel showing no faults is telling you about the panel. It is not telling you the signal arrives.
The only reliable answer is periodic end-to-end testing, where somebody triggers the path and somebody at the receiving end confirms arrival. That should be a named line in your maintenance scope with a stated interval, and if it is not in your current contract, that is the gap.
Building the verification into your own calendar
Approval and connection are both live states rather than permanent facts, which means checking them once at appointment is not enough.
A short annual routine, owned by somebody in the building rather than the contractor:
- Re-verify the approval reference and its validity, and confirm the approved entity still matches the company invoicing you. Contractors restructure, and the entity on the paperwork can quietly stop being the entity attending.
- Request the monitoring end-to-end test result in writing, dated. Not a statement that the link is fine, but a record of a signal sent and received.
- Confirm the subscription renewal date and who pays it. Where the monitoring provider invoices separately from the maintenance contractor, this is the item most likely to lapse unnoticed.
- Check the panel event log for communication faults over the preceding year. Repeated communication events are the early warning that the link is unstable rather than dead.
Fifteen minutes annually, and it closes the gap that produces the most serious findings we see. The reason it goes undone is not difficulty but ownership: everybody assumes the contractor is watching it, and the contractor is watching the part they were contracted for.
Approved does not mean interchangeable
There is a real trade-off in how much weight to put on approval as a selection criterion.
Approval is a floor, not a ranking. It confirms a company is permitted to do the work. It says nothing about whether they hold authorisation for your panel brand, whether they measure or merely inspect, whether they record defects, or whether they will still be your contractor in three years. Buildings that select on approval alone tend to select on price next, because everything else has been treated as equal.
At the same time, treating approval as a formality is worse. An unapproved contractor's maintenance does not count, whatever the quality of the work, and discovering that at an inspection is an expensive way to learn it. Verify the floor properly, then choose on the things that actually differ. Our guide to choosing a DCD-approved fire AMC company covers those.
Explore the DCD Approval & Monitoring Cluster
Each page below covers one part of approval and connected monitoring in Dubai.
Related reading: what keeps a Hassantuk maintenance contract live, and what an inspector checks at a DCD inspection.
Next step, and it takes ten minutes: find out who owns your monitoring communicator and when that subscription renews. If nobody in the building can name the provider, the renewal date, or the last time the signal was tested end to end, you have found the single most likely gap in your fire compliance, and it will not appear on any panel display.
