Compliance by area, devices overdue and by how long, findings ageing by owner, and plan versus actual month by month. Plus the one that matters most when somebody arrives unannounced: the complete record pack for a block, assembled and exported while they are still in reception.
Different people need different views. A safety officer runs the week from the due list; a plant head reads the trend; a fire officer wants the record.
Reported at the level someone can act on, and rolled up for multi-site groups so a head office can see which location is actually behind.
What falls due this week, what is already overdue, and which refill, hydrotest and certificate expiries are approaching.
Open findings by age bucket and by owner, with average closure time tracked over quarters rather than guessed.
Rounds planned against rounds completed, month by month — the gap being the number management should be reading.
Who is completing their assigned rounds and who is not, which is usually a workload problem rather than a discipline one.
The devices and areas that keep producing the same finding, surfaced as a pattern instead of as unrelated notes.
Device register, inspection records, open and closed findings, certificates, statutory filings and competency records, in one export.
Any view leaves the system in the format the person asking for it actually wants.
Plain-English questions against your own history, for the things a fixed report was never designed to answer.
A report describes last month. A board tells you what is uncovered while you can still do something about it.
It is the complete evidence set for a block or a site: the device register, every inspection record for the period with its auditor, timestamp and photograph, open findings with target dates, closed findings with their verification, refill and hydrotest certificates, statutory certification history, auditor competency records and escape route checks. It assembles from data already in the system, so it is produced on the spot rather than compiled over three days.
Yes, and you should. A site-level percentage is usually the least useful number in the building because it averages a fully compliant admin block with a tank farm that is badly behind. Compliance is reported by building, floor and area, and rolled up only where a roll-up is genuinely what is wanted.
Devices whose required checks are current against the total devices in scope. Because frequency is held per device category, a device that needs a monthly check and one that needs an annual check are each judged against their own cycle rather than against a single site-wide rule.
Yes. The same exports serve an internal review, an insurer at renewal and a group EHS audit, which is usually the point — most of the effort in fire compliance reporting goes into rebuilding the same facts in three different formats for three different audiences.
No. Every figure computes from checks, findings and closures already recorded during rounds. Nobody types a compliance percentage into a spreadsheet at month end, which also means nobody can quietly adjust one.
For the questions a fixed report cannot answer: which area is falling behind, what keeps coming back as the same finding, whether you are ready for the next certification, and how long findings are really taking to close. It reads your own data, read-only, and it also clusters the free-text remarks auditors write into recurring themes.
We will build the areas, load the categories and show you the record pack assembling — on the call.
