Without an owner and a target date, a finding is a sentence in a report. Every not-OK check becomes a non-conformity against that exact device and location, carrying its evidence photograph, escalating as the date approaches, and closable only after someone other than the person who fixed it has verified the fix.
The sequence is what makes a finding end. Remove any one step and it becomes a note that reappears in the next audit report.
A non-conformity points at one device in one area, not at a building — so the person fixing it knows where to walk.
Every finding has somebody responsible and a date it is due by, both visible on the dashboard from the moment it is raised.
Cause is recorded rather than assumed, using the device's own history — which is usually what makes the cause obvious.
What was actually done, by whom, and when, with agency certificates attached where external work was involved.
Reminders escalate to the next level as the target date approaches, instead of repeating quietly to the same inbox.
The person who did the work cannot be the person who closes the finding. Closure needs a second, named verification.
Open findings grouped by age, area, category and owner — the tail past 30 days is the number that matters.
The same finding on the same device across rounds surfaces as a pattern rather than as unrelated notes in four reports.
The photograph taken when the check failed, plus anything added during the fix, stays attached for as long as the record exists.
Most organisations can produce a list of findings. Far fewer can show that each one ended, and who confirmed it.
It is a recorded gap between what a fire safety check required and what the auditor actually found: an extinguisher below pressure, an obstructed escape route, a missing signage board, a detector that failed its test. In Fast Fire Audit it is raised against one specific device and location, carries the evidence photograph taken at the time, and stays open until it is fixed and verified.
The severity rule, configured once. A blocked escape route and a scuffed signage board should not carry the same deadline, and leaving that judgement to whoever is on shift is how the serious ones drift. The rule sets the date; escalation follows it automatically.
Because the point of the record is that somebody independently confirmed the fix. Closure requires a second named person to verify — often by scanning the same device tag again at the device. It is a small piece of friction that is the difference between a closure an inspector accepts and one they question.
When a device is taken out of service, the area it protected is exposed until it returns. Recording the standby unit placed — and when — shows that cover was maintained rather than merely that a unit was missing for three weeks. It is one of the more useful things a paper register cannot show, and one of the first things an inquiry looks for.
Two ways. Findings are held against the device rather than the round, so a second occurrence on the same unit is visibly a repeat rather than a fresh note. And Dhruv AI clusters the free-text remarks auditors write, which surfaces themes — obstructed routes, low pressure, missing signage — that no fixed report column was ever going to show.
Yes. Findings raised by a licensed agency, an insurer's surveyor or a corporate EHS audit can be logged against the same devices and run through the same owner, target date and verified-closure cycle, so you are not tracking external findings in a separate spreadsheet from your own.
Live on the call, on your own device categories — including the verification step that stops self-signed closures.
