What an audit is in the system
An audit is a collective view of the findings raised during one hall patrol. It has a name, date, hall and auditor, and the findings the inspector adds during the patrol become its items.
Instead of a dozen separate findings with no shared context, the manager gets one list from one patrol and can see how many matters need attention in their hall.
Three audit statuses and when they change
The audit status is calculated on every read and is never set by hand. This means there is no mismatch between what the list of findings shows and what the audit shows.
- Open: the audit is still collecting findings, the patrol is ongoing
- In progress: the audit has been closed, but some findings are still unresolved
- Completed: all findings are resolved or rejected
Example: findings in an audit with 7/10 progress
When an audit has the In progress status
The In progress status appears after the audit is closed, when at least one finding has not yet been resolved or rejected. Closing the audit therefore means the end of collecting remarks from the patrol, not the end of fixing defects.
This distinction is practical: the inspector can close the patrol on the same day, while the hall manager has a week or two to clear the remarks. The audit stays visible as In progress until the last finding receives the status resolved or rejected.
Can a finding be in two audits
No. A finding belongs to at most one audit at a time. The rule prevents the same defect being counted twice in two summaries, and prevents a situation where two managers each believe the other one is handling it.
When the inspector finds the same defect during a later patrol, they do not add it to a new audit in place of the previous one. Instead they check whether the finding in the old audit has been resolved. If not, they return to it with a remark.
Rejected findings and 7/10 progress
Audit progress is the number of findings resolved or rejected, divided by all findings in the audit. It is displayed, for example, as 7/10: seven of the ten findings are closed, three are waiting.
A rejected finding counts towards progress, because the decision to reject it closes the matter. It is still worth giving the rejection a short justification, because during an external audit the question of why remarks were not acted on is asked most often.
The PDF summary and what to do with it
The audit summary is available as a PDF. It is suitable for attaching to the patrol protocol, handing over to the hall manager, and filing in the OHS document archive.
In practice it is worth downloading the PDF twice: once after the audit is closed, as a record of what was found, and once after the status changes to Completed, as proof that the remarks have been closed. Two documents create a trail from finding to fixing the defect.
Video
Frequently asked questions
Does the audit status have to be changed by hand?
No. The status is calculated on every read from the state of the audit and its findings, so it never drifts out of step with the list of findings.
Does a rejected finding block the audit from being completed?
No. The audit is Completed when all findings are resolved or rejected. A rejection counts towards progress.
Can a finding be moved to another audit?
A finding belongs to at most one audit at a time. In practice a defect stays in the audit where it was found until it is resolved.
Where do I find the summary for the hall manager?
The audit summary is available as a PDF. It can be attached to the patrol protocol or sent to the hall manager.
Collect patrol remarks in one audit
We will show an audit with progress and a PDF summary using a hall similar to yours. Book a demonstration with InnerWeb.
Let's talk