Closing the loop on corrective actions

An audit that finds problems and never confirms they were fixed has done only half a job. The finding is the easy, satisfying part: the inspector walks the building, spots what is wrong, writes it down, and the report lands looking thorough and useful. What happens next is where most of the value is won or lost, and where a great deal of real-world compliance quietly falls apart. A finding raised is not a problem solved. It is a problem identified, and the gap between the two is where buildings get hurt and managers get exposed.

Closing the loop on corrective actions, taking each finding from raised to genuinely resolved and confirmed, is unglamorous and easy to skimp on. It is also the part that determines whether an audit programme actually improves a building or merely documents its faults in ever-growing lists.

The open list is the failure mode

The characteristic failure is not that nobody acts on findings. It is that the acting becomes detached from the finding, so nobody can say with confidence what is done and what is still open. A finding is raised in one report. The work is arranged through a separate email. The contractor does the job and mentions it in passing. The audit report, meanwhile, still says the problem exists, because nothing went back and changed its status. Six months later, the building's record shows an open finding that was actually fixed, sitting beside another open finding that genuinely was not, and no one can tell them apart without re-walking the building.

That ambiguity is corrosive. It means the list of open actions becomes untrustworthy, and an untrustworthy list gets ignored, which is how real, unresolved hazards hide among the noise of stale entries that were dealt with long ago. The open list that nobody believes is worse than no list, because it gives the appearance of control without the substance.

What "closed" should actually mean

The fix begins with insisting that "closed" mean something specific and evidenced, not merely "someone says it is done". A finding should not be closeable on assertion alone. It should require the same rigour going out that it took coming in.

A defensible closure has a few elements:

• A clear record of what the finding was, with its location and its severity.
• Evidence that the corrective work was actually done, not just instructed, a photograph, a certificate, a contractor's confirmation tied to the specific finding.
• The date it was completed and who confirmed it.
• A change of status that is visible and dated, so the record now reads "resolved" with a trail behind it rather than silently still showing "open".

The point is that closing a finding should leave evidence behind, exactly as raising it did. A finding that was opened with a photograph and a severity, and closed with a photograph and a date, tells a complete story that holds up later. One that was opened formally and closed by someone quietly deleting it from a spreadsheet tells nothing.

Severity drives urgency, not just record-keeping

Not all findings deserve the same clock. A cracked floor tile and a wedged fire door both go on the list, but they should not sit there with the same urgency. Closing the loop properly means severity drives the timescale, so the serious findings are chased and confirmed quickly while the cosmetic ones take their place in an orderly queue.

The principle is familiar from the regulatory regime around hazards. Awaab's Law, whose Phase 1 came into force on 27 October 2025 for damp and mould and all emergency hazards, sets out exactly this kind of severity-driven clock: investigate a potential damp or mould hazard within 10 working days, begin to act within 5 working days of finding a significant hazard, and make safe emergency hazards within 24 hours, according to the Housing Ombudsman. Whether or not a given building falls under that regime, the logic is sound for any corrective-action process: the more serious the finding, the shorter the time to act and confirm. We have written about scoring and ranking audit findings, and the score is only useful if it actually drives how fast a finding is closed.

The loop has to live with the finding

The reason loops stay open is almost always that the action lives somewhere other than the finding. The moment a corrective action moves into a separate email thread, a different spreadsheet or a contractor's own system, the connection back to the audit weakens, and weak connections break. The finding and its resolution have to live in the same place, so that closing the action and updating the finding are the same act rather than two acts that have to be remembered separately.

When they live together, the building's record answers the only questions that matter at any moment: what was found, what is still open, how serious it is, and what proof exists that the rest was fixed. That single, trustworthy view is what turns an audit from a snapshot of problems into a record of problems resolved. It is the same thinking behind keeping the whole audit trail in one place, covered in keeping an audit trail that holds up, and it is why we build corrective actions into the audits record rather than treating them as a separate afterthought, tracked against the compliance calendar so the deadlines for closing them do not slip.

A short, practical close

A finding raised is not a problem solved, and an audit that cannot show its findings were closed has done half a job. The discipline is to make "closed" mean something, evidenced, dated and confirmed, to let severity drive how fast each finding is chased, and above all to keep the corrective action living with the finding so that closing one updates the other. Do that, and the open list becomes trustworthy, which is the only kind of list worth keeping. SAMRISK tracks corrective actions against the findings that raised them, with evidence and dates attached, so the loop actually closes rather than quietly staying open. This is general information rather than a compliance standard, and the timescales for acting on particular hazards should be checked against the rules that apply to your buildings.