What it is
Inspections are the scheduled checks that keep a site honest — the walk-around against a checklist that confirms things are as they should be. The register shows what is coming up and what has been done, with a count of findings against each completed inspection. Open one and you work its findings: each gets a severity and moves open to actioned to closed, and any finding can spawn a corrective action that lives in the shared actions register.
Regular inspection is how small problems get caught before they become incidents. Scheduling them, completing them on time and closing out the findings is the rhythm of a well-run site — and the inspection history is clean evidence that the checks happened and the issues were fixed.
When to use it
- A scheduled inspection is coming up and you want to see what is due
- You have completed an inspection and need to record its findings
- A finding needs a fix with an owner and a due date
- A client or auditor asks what was inspected and what it found
How it works
Step by step.
- 1
Check what is scheduled
The upcoming panel shows inspections due. Pick the one you are about to run.
- 2
Complete the inspection
Work through the checklist on site and record the result. The inspection moves to completed with its date.
- 3
Record each finding
For anything not right, add a finding with a description and a severity. Findings start open.
- 4
Action the findings
Move a finding to actioned once someone is on it, and spawn a corrective action where a tracked fix is needed.
- 5
Close the findings
When a finding is resolved, close it. The inspection’s findings count winds down as you go.
- 6
Review the history
Completed inspections stay on the register with their findings, building the evidence trail over time.
Worked example
Follow it through.
The scenario
A monthly site inspection at Docklands Distribution Centre is due, and Priya Nair walks it for Coastline Logistics.
- 1 Open the inspections register; the "Monthly warehouse inspection" shows due Tue 10 Jun.
- 2 Complete it against the checklist and record the date walked.
- 3 Add finding 1 — "Fire extinguisher signage missing in Aisle 6", severity Medium.
- 4 Add finding 2 — "Eyewash station tag overdue", severity High, and spawn a corrective action to Jack Mason, due Thu 12 Jun.
- 5 Move both findings to actioned, then close them as they are resolved.
The result
The monthly inspection is recorded as complete with two findings closed, one of them tracked as a corrective action, and the next inspection visible on the schedule.
Tips & notes
Good to know.
- Severity on a finding drives the urgency of the fix — be honest, so the high-risk items rise to the top.
- Spawn a corrective action for anything that cannot be fixed on the spot; it then carries an owner and a due date.
- A clean inspection history is gold in a tender — keep completing them on schedule even when findings are nil.
- Findings that recur across inspections are a signal to log an underlying hazard, not just keep fixing the symptom.
When you’re done
The inspection is completed and its findings are tracked to closure, with the result on the permanent record.