Keeping Untested Sites Out of the Green Audit-Readiness Status
Separate reviewed, failed and untested asset evidence in management reports so missing site responses do not become a misleading green readiness rating.
How should audit-readiness reporting show sites that have not submitted evidence?
Use an explicit untested or awaiting-evidence status and keep those sites in the stated reporting population. Reserve a satisfactory rating for work actually reviewed against defined criteria. Show overdue responses, failed checks and completed reviews separately so management can assign the right next action to each group.
A readiness spreadsheet asks departments to confirm that their asset evidence is complete. Several respond; others leave their rows blank. If the summary ignores blanks, the overall indicator can turn green while entire sites remain unassessed. The issue is not the colour itself but the logic used to convert missing information into a management conclusion.
Define the evidence behind each status
Write a short rule for satisfactory, exception found, awaiting evidence and not applicable. State who performs the review and which evidence is checked. A department’s self-declaration can be recorded as received without being treated as a completed review. Keep the distinction visible if the readiness exercise depends on both stages.
Define the scope at the start: named sites, asset classes or control areas. A not-applicable status should have a reason and reviewer, rather than provide a convenient way to remove difficult rows. Where a site has closed or merged, preserve the scope change so the management pack explains why the population differs from the previous period.
Report counts before applying a summary rating
Show the total population and counts in each status. Identify how many have supplied evidence, how many have been reviewed and how many remain overdue. This gives management a more useful picture than an average score that combines complete reviews with missing responses.
If an overall rating is needed, document its rule and make untested coverage a visible condition. For example, the organisation might require all critical sites to be reviewed before reporting a satisfactory overall position. That is a locally chosen management rule, not a universal audit requirement. Explain it consistently rather than changing it to fit the desired colour.
Turn uncertainty into an assigned task
For each untested site, record the missing evidence, responsible contact, request date and next action. Distinguish a non-response from a submission that cannot be opened or lacks the relevant period. Each should have a specific follow-up so the site knows what is needed to move forward.
When evidence arrives, record the receipt date and review result instead of backdating the site’s status. Retain the earlier snapshot if it was already reported to management. The revised pack can then explain progress accurately: uncertainty reduced because more sites were reviewed, rather than because the scoring model stopped counting them.
Practical Example
Illustrative example: an entity has ten sites. Six submit evidence that passes the defined internal review, one submits evidence with an unresolved exception and three have not responded. The pack reports six satisfactory, one exception and three awaiting evidence. It does not report six out of seven as the organisation’s complete readiness position. Management assigns follow-up owners to the three sites and keeps the unresolved exception on a separate action track.
Action Checklist
- 1.Define satisfactory, exception, awaiting-evidence and not-applicable statuses in writing.
- 2.Keep non-responding sites inside the stated reporting population.
- 3.Separate evidence received from evidence reviewed and accepted.
- 4.Disclose the rule used to turn detailed results into any overall rating.
- 5.Date new review outcomes and retain earlier snapshots already reported to management.
For readiness reporting that keeps untested evidence visible, explore Audit-Ready Asset Management.