InnerWeb
Skip to main content

Use case: hall walk audit and report progress

A safety inspector returns from a hall walk with ten reports and wants to know how many of them are already closed. In InnerWeb, reports raised during one walk are grouped into an audit, and progress is shown as a fraction, for example 7/10. Below is a scenario based on the report audit feature.

7/10
sample audit progress: resolved plus rejected out of all
Source: report audit documentation
3
audit statuses: Open, In progress, Completed
Source: report audit documentation

Situation: a walk ends with a list of scattered issues

A safety inspector walks through the hall and raises ten issues along the way: a damaged guard, a blocked emergency exit, missing signage, spilled oil. Each report goes to a different person and takes its own course. A week later the inspector wants to answer a simple question from the manager: how many issues from this walk are already resolved.

Without grouping, the answer requires scrolling through the list of reports and counting by hand. With several walks a month, counting becomes impractical, and so is control over whether a walk actually led to improvement.

Solution: the audit as a container for reports from one walk

Reports raised during one hall walk are grouped into an audit with a name, date, hall and auditor. A report belongs to at most one audit at a time, so the same issues are not counted twice and there is no dispute over which walk they were assigned to.

Status calculated on every read

The audit status is not entered by hand but calculated each time it is read. An audit is Open while it is still collecting reports. Once closed, it moves to In progress when some reports remain unresolved. The Completed status means that all reports are resolved or rejected.

  • Open: the audit is still collecting reports
  • In progress: the audit is closed, some reports are unresolved
  • Completed: all reports are resolved or rejected

Progress as a fraction

Audit progress is the number of resolved and rejected reports divided by the total. It is shown, for example, as 7/10. A rejected report counts toward progress because the matter has been settled: someone assessed that no action is needed and recorded that decision.

Sample state of reports in an audit after a hall walk

Sample state of reports in an audit after a hall walkDonut chart: 7 reports resolved or rejected and 3 unresolved in an audit of 10 reports.Resolved or rejected: 7 reports (70%)Unresolved: 3 reports (30%)10reportsResolved or rejected7 reports (70%)Unresolved3 reports (30%)
Source: Illustrative example consistent with the audit progress definition: 7 of 10 reports

How it looks from the inspector's perspective

After the walk the inspector closes the audit, and from that moment sees one row instead of ten separate issues. The row shows the name, date, hall, auditor, status and progress. When after a few days the progress reads 7/10, it is clear that three issues are still waiting and the responsible people can be asked about deadlines.

The audit summary is available as a PDF. It is a convenient document for a meeting with the hall manager or for the archive: it contains the set of reports from one walk in one place, without the need to compile them by hand.

Reports in the recurring report

Audits complement the report on reports from the reporting module. The report shows the number of reports created and closed, the median reaction time and resolution time, and tables by category, status, location and type. The audit answers the question about one walk, while the report answers the question about the whole period.

Combining both views gives a fuller picture. The audit shows whether a specific walk brought improvement, and the report shows whether the reaction time to reports is shrinking or growing. The median is robust to extreme values, so a single report waiting a long time does not distort the whole period.

Conclusions and practical notes

Name the audit so that after a month it is clear what it covered: hall, date and scope of the walk. Close the audit on the same day, because the In progress status and the progress figure only make sense once report collection has ended.

Decide who settles the rejection of a report. Rejected reports raise progress, so without a rule it is easy to close an audit without resolving the issues. A good practice is to record the reason for rejection in the report itself.

InnerWeb works as an independent system that complements the client's existing systems. Audits cover reports collected in InnerWeb, so they do not replace the quality management system or a corrective action plan kept elsewhere.

Video

Frequently asked questions

Can a report belong to two audits at once?

No. A report belongs to at most one audit at a time, so the same issues are not counted twice.

When does an audit have the Completed status?

When all reports are resolved or rejected. The status is calculated on every read, so it does not need to be changed by hand.

Can a document be generated from an audit?

Yes, the audit summary is available as a PDF and suits a meeting or the archive.

We will show the walk audit using an example from your hall

See how reports from one walk gather into an audit with progress and a PDF summary. Book a short demo.

Let's talk