The short version: most compliance files do not fail because the building was bad. They fail because the file cannot answer the question that was asked. The requirement is written in years, percentages of a year, and five-year retention — and the evidence offered is a certificate from one Tuesday. Nobody is lying; the units simply do not match.
This page is about the units. What the requirements actually ask you to be able to show, what makes a record survive being read by someone who was not there, and where a test certificate stops being the answer.
Read these next to each other and the pattern is hard to miss. Every quote below is from the issuing body, linked.
| Requirement | Its unit | Source |
|---|---|---|
| HVAC must provide the stated internal conditions “for 95% of the year” | A percentage of a year | Dubai Building Code (2021), H.4.7 |
| Water consumption recorded per meter; “records must be kept for 5 years”, and “virtual meters using run-hours are not acceptable as sub-meters” | Five years of history | Al Sa'fat, 2nd ed., §602.01 |
| Indoor air quality retesting “within 5 years of last compliant test”, sampled as an “8-hour time-weighted average” | A shift, repeated over years | Al Sa'fat, Table (1) 401.07 |
| Where a BMS is installed, parking CO “shall be monitored to allow real time profiling and management of air quality”; sensors recalibrated every 6 months | Continuous, with a calibration history | Dubai Building Code (2021), H.4.12.11 |
| Metering with data logging, a central system, “hourly, daily, weekly, monthly and annual” consumption, year-on-year trend comparison and out-of-range alerts — plus a written commitment to supply the data on request | A data stream, not a measurement | Estidama PBRS 1.0, PW-R2 (required credit) |
None of those is satisfied by a document describing one day. That is not a criticism of testing — the accredited test is required where it is required, and no record replaces it. It is an observation about arithmetic: a point cannot answer a question phrased as an interval.
For water systems specifically, the shape of a record that holds up is prescribed: see the nine-link legionella evidence chain, clause by clause.
We read other people’s compliance files often. The ones that survive scrutiny share four properties, and the ones that collapse are usually missing the same four.
A record that never shows an exceedance is a record you should distrust. Real buildings drift. A chiller trips, a filter loads, a room fills for an event, a contractor props a door open in August. The file that shows the excursion, how long it lasted and what happened next is more credible than a flat line — and considerably more useful, because the excursion is where the maintenance decision actually lives.
This is also the practical difference between a record kept for the regulator and a record kept for the building. The first is written to look clean. The second is written to be used.
| The question | A test certificate answers | A continuous record answers |
|---|---|---|
| Were conditions held for 95 % of the year? | Not addressed | The actual percentage, with excursions dated |
| What were the water figures per meter over five years? | Not addressed | Per-meter history for the period |
| Was the building compliant on the day it was tested? | Yes — this is what it is for | Corroborates, does not replace |
| Will the building pass the test that is booked for next month? | Not addressed | Tells you in advance, while there is time to fix it |
| What happened in the building last August? | Silence | An answer |
| Has anyone changed a number since it was recorded? | Not addressed | Verifiable, if the export is sealed |
Thirteen properties come up again and again when UAE operators are asked what a compliance record must do. The honest way to read the table below is column three: no single product covers all thirteen, ours included, and a vendor claiming otherwise is selling something else.
| Requirement | What it means on site | Where it is covered |
|---|---|---|
| Immutable, time-stamped audit trail | Each entry carries when it was captured and by whom, and any later edit is visible as an edit rather than silently replacing the original. | Our layer. Readings are time-sealed at capture, and a record that can be quietly back-dated is not evidence. |
| Mobile inspection and checklist forms | A person walks the site with a phone and completes a structured form per asset or area. | Not us. This is what inspection software does, and it does it better than we would. |
| Photos and documents attached to a finding | The cracked seal, the corroded flange, the certificate — bound to the specific finding, not to a folder. | Not us. Inspection software. |
| Electronic signatures and approvals | The named responsible person signs; the approval is attributable. | Partly ours: sign-off sits on the record we produce. Signed inspection forms belong to the checklist tool. |
| Corrective action, assigned and closed with proof | An out-of-range result creates an action with an owner and a due date, and closes only on evidence that it worked. | Ours for anything measured: the action is bound to the exception that triggered it, and a follow-up measurement closes it. |
| Automatic expiry and renewal alerts | Certificates, permits, contracts and calibrations that lapse quietly. | Partly ours for calibration and scheduled testing; permit and licence expiry belongs to document management. |
| Version control of SOPs and policies | Which version of the procedure was in force on the day in question. | Not us. Document management. |
| Role-based access | Duty holder, responsible person, competent person and contractor each see what they should. | Ours, and the contractor's results land in the same record rather than in a separate PDF. |
| Offline capture on site | Basements and roof voids have no signal; readings taken there must still reach the record. | Not us in the checklist sense. Our sensors buffer and forward on their own, which is a different mechanism for the same problem. |
| One-click evidence pack, PDF or Excel | An inspector arrives; the full history for a period comes out in a usable format. | Ours for the measured record, in the format the relevant Dubai Municipality guideline prints. |
| Search by site, asset, person, inspection, permit or finding | Eighteen months later, someone asks what happened on one riser on one date. | Ours by site, asset and reading. By permit or by employee — document management. |
| Arabic and English | Records read by inspectors and by staff, not only by head office. | Ours for reports and interface. Checklist forms in Arabic belong to the inspection tool. |
| Retention and access control | How long the record is kept, and who can reach it, under UAE requirements. | Ours for the measured record; the wider document estate is not our layer. |
This is the part that decides which tools a building actually needs, and it is usually skipped.
An inspection round is a sample. It shows the state of the asset at the moment the person stood in front of it. That is exactly right for the things a round is for — a cracked seal, a missing label, a blocked access panel — and no sensor will ever replace someone walking the plant room with their own eyes.
But some requirements are written about conditions that must hold at all times, and a weekly round cannot evidence those however diligently it is completed. Two examples from documents anyone can open:
So the two layers answer different questions. The checklist answers what did we find when we looked. The continuous record answers what was true when nobody was looking, and what happened when it went wrong. A building with a serious compliance load usually needs both, and the mistake is buying one and assuming it covers the other.
Named, and described in each organisation's own words rather than ours.
Pick one exceedance from last quarter — a temperature that drifted, a chlorine reading out of range, a laboratory result above limit. Ask each vendor to show you, live: the asset it happened on, the scheduled check that should have caught it, the exception it raised, the action someone took, the measurement that verified the action worked, and the signature on the record that went to the authority. Whoever needs a separate spreadsheet, email thread or WhatsApp group to answer any of those six does not hold your evidence chain — somebody's memory does.
We produce the continuous record: temperature, relative humidity, CO₂, PM2.5, TVOC and related parameters, logged around the clock, per zone, with the export sealed so that a reader can confirm later that no value was changed after it was recorded.
What we are not. We are not a certification body, an accredited testing laboratory, or an assessor. Where an accredited test is required, hire an accredited laboratory — the Dubai Building Code is explicit that “air quality testing shall be carried out by specialized companies or laboratories accredited by the Authority”. We describe our output as the record you bring to the accredited test, and to the assessor — not as “accepted evidence of compliance”. Whether any given authority accepts any given document is that authority’s decision and not a claim we will make on their behalf.
Related reading: which UAE certification systems are compulsory and what each asks about air and water · a badge is not a statute · the Legionella regime in Dubai.
| Price | |
|---|---|
| IAQ monitoring | AED 800 per zone per month, dropping to AED 600 per zone from 5 zones and AED 400 per zone from 21 zones. Minimum AED 1,600 per site. 12-month minimum |
| Pool / Legionella monitoring | AED 2,200 per pool per month |
A zone is a space with its own HVAC supply or served by the same air-handling branch — one classroom, one function room, one consult room — not a square-metre charge. Adding a zone never increases your total: where a higher volume tier gives a lower price, that lower price applies.
Yes, and the useful question is narrower than the category. What separates a record that holds up from one that does not is whether it can answer for a period rather than a moment, whether it states its own gaps, and whether someone reading it a year later can confirm it was not edited after a disagreement. Any platform that gives you those three things works. WOLKIS logs temperature, humidity, CO₂, PM2.5 and TVOC per zone continuously and seals the export so it can be verified afterwards. Whether a given authority accepts a given document for a given purpose is that authority's decision, not ours to promise.
It varies by regime, and the units differ more than people expect. Dubai's Building Code sets thermal conditions that HVAC must hold “for 95% of the year” — a percentage of a year, not a reading. Al Sa'fat requires water consumption records per meter to be “kept for 5 years” and states that “virtual meters using run-hours are not acceptable as sub-meters”. Its indoor air quality table for existing buildings runs on retesting “within 5 years of last compliant test”, sampled as an “8-hour time-weighted average”. In Abu Dhabi, Estidama's required credits go further and ask for a written commitment to supply monitoring data to the authority on request.
It is exactly enough for what it covers: the day it was taken. The mismatch appears when the requirement is written in a longer unit. A certificate cannot demonstrate 95% of a year, five years of metering, or a thirty-three-day flush-out, because those are periods and the certificate is a point. Both are needed — the accredited test because it is required, and the record because it covers everything between two tests.
Four things, in our experience of reading other people's files. It states an average without the period it averages. It has silent gaps where the logger was offline and nothing says so. It cannot be tied to a specific location — “the office” rather than a named zone. And nothing about it prevents a number being adjusted after the fact, which means a reader who was not there has to take it on trust.
Yes, and a record that never shows one deserves suspicion rather than confidence. Real buildings drift: a chiller trips, a filter loads up, a room fills for an event. A file that shows the excursion, its duration and what happened next is more credible than a flat line, and far more useful — the excursion is where the maintenance decision lives.
AED 800 per zone per month, dropping to AED 600 per zone from 5 zones and AED 400 per zone from 21 zones, with a minimum of AED 1,600 per site and a 12-month minimum term. Pool and Legionella monitoring is AED 2,200 per pool per month. A zone is a space with its own HVAC supply or served by the same air-handling branch — one classroom, one function room, one consult room — not a square-metre charge.
All sources re-checked 24 August 2026. Confirm requirements with the competent authority for your project. Nothing here is legal advice.
Send us the last compliance file someone asked you for. We will tell you which of the four questions above it survives — and which it does not — before you need it to.