Set the frequency each device category is held to, and the schedule generates itself across the year — broken down by building, floor and area, assigned to named competent auditors, approved before it runs, and pushed out as reminders before the due date rather than after the lapse.
The plan is generated from the frequency each device category carries on the register, not typed in row by row. Slipping one date does not break the rest of the year.
A full year of rounds generated from the frequency each category carries — the whole schedule in one action rather than a spreadsheet row per check.
The same engine scoped to the near term, so auditors work from the current month instead of a year-long list they scroll past.
Plans break down to building, floor and area, which is also how the compliance percentage is later reported back.
An authorised-auditor matrix by device category, so only qualified people can be assigned — and you can prove that to an inspector.
Plans are raised in draft and released only after sign-off, with the approval itself part of the record.
Your existing check points are imported rather than rewritten, so the round matches the format your team and your auditor already know.
Email, SMS and WhatsApp reminders before the date, and escalation to the next level when one passes.
Closing a check sets the next due date from the interval, so the cycle cannot quietly lapse between rounds.
How many rounds were planned against how many actually landed, month by month — the report management should be reading.
A schedule in a spreadsheet drifts the moment one date slips, and nobody finds out until the audit.
It is generated rather than typed. Each device category on the register carries its own inspection frequency; you pick the site and area scope, and the plan produces the rounds for the year with due dates spaced by that frequency. The monthly plan is the same engine scoped to the near term so auditors work from the current month.
Yes. Frequency is held per device category, and the plan is scoped by building, floor and area, so a solvent store and an admin block can run on completely different cycles within the same site. Multi-site groups can hold one standard across every location and still report each site separately.
It is a record of which auditors are qualified to sign off which category of check. The system will not let an unqualified name be assigned to a check that requires competence. It matters because an inspector may reasonably ask not just whether a check happened, but whether the person who made it was competent to make it.
No. Existing check points are imported from your Excel formats, so the round your auditor walks matches the one your standards, insurer and fire authority already expect. You can refine them afterwards, but nothing has to be rebuilt to get started.
The due date passes into overdue, the device shows as overdue on the dashboard and by area, and the reminder escalates to the next level rather than simply repeating. Because the next due date is set on closure rather than by a fixed calendar, one missed round does not silently shift the rest of the year.
It can. Statutory obligations that recur — the twice-yearly certification cycle, the annual audit, refill and hydrotest dates — are configured as their own requirements with their own frequencies, so they appear on the same due list and the same dashboard as the routine in-house rounds.
Bring your device categories and the frequencies you are held to. We will generate the plan on the call.
