Inspections & audits
Inspections that finish the job
Templates, conduct, signatures, approval and the report — one flow from "walk the floor" to "here is the evidence", with every finding turned into an action someone owns.
Included free — like the rest of the platform.
How it works
- 1
Build the template
Sections, question types, response sets and conditional logic, so the form only asks what applies. Publish when it is ready — every published version is frozen, so you always know exactly which questions an old report answered.
- 2
Run it on site
Conduct on a phone, tablet or laptop. Progress saves as you go, so a part-finished inspection survives interruptions and shift changes. Each inspection stamps its own document number automatically.
- 3
Flag it, sign it, approve it
Flag failing responses and raise corrective actions from the exact question they came from. Collect signatures against named signer slots, then route the completed inspection to an approver if your process needs one.
- 4
Share the result
Export a polished PDF or Word report, download the register as CSV, or send a revocable public link that opens without an account.
What it does
Template builder
Question sections, shared response sets, scoring and signature slots — with logic that shows and hides questions based on earlier answers.
Version control
Publishing freezes the version. Inspections pin the version they started on, so editing a template never rewrites history.
Approvals
Send completed inspections for approval; every approve and reject decision is logged against the record.
Recurring schedules
Set the rhythm and the assignees; upcoming occurrences materialise on their queues with reminder emails before the due date.
Findings become actions
Raise an action from any response. Recurring inspections de-duplicate, so the same broken door does not become five actions.
Reports & sharing
PDF and Word exports, CSV registers, and revocable share links for people outside the platform.
Scheduling that runs itself
Decide once that the fire-point check happens every Monday, and stop carrying it in your head.
- Occurrences appear on each assignee’s queue and the schedules calendar ahead of time
- Reminder emails chase before the due date — once, not endlessly
- Archiving a template pauses its schedules in the same breath, so nothing fires for a retired checklist
Guides for this module
Build and publish an inspection template
From a blank template to a published checklist your team can run — sections, response sets, logic and signatures.
8 min read
Conduct an inspection
Run a checklist on a phone or laptop, flag what fails, raise actions from the finding, and sign it off.
6 min read
Schedule recurring inspections
Put a checklist on a rhythm — daily, weekly, monthly — with assignees, reminders and a calendar of what is due.
5 min read
Approve inspections and share the report
Run the approval step where your process needs one, then get the report to the people who asked for it — PDF, Word, CSV or a link.
4 min read
Works with
Actions
One board for everything that must get done — wherever it was raised, whoever owes it.
Hazards & observations
Anyone can report what they see — from a QR code, no login — and it lands somewhere it gets dealt with.
Assets
A register of the kit work happens on — typed, site-assigned, nested, and linked to the checks and actions that concern it.