Compliance8 min read

Awaab's Law: A Proof Problem, Not a Repair Problem

Awaab's Law has shifted the question for housing leaders. It is no longer whether you take damp and mould seriously - it is whether you can prove it, case by case, within the clock.

By Jamie Lee Goodchild•

The question for housing leaders is no longer, "Do we take damp and mould seriously?"

It is, "Can we prove which homes were made safe within the clock, which cases are still exposed, and where the next breach is likely to come from?"

Since 27 October 2025, landlords have been working to fixed Awaab's Law timescales for emergency hazards and significant damp and mould hazards, with further hazards due to come into scope through 2026. The pressure is now operational and evidential.

For most landlords, this is not a policy problem. It is a proof problem.

Awaab's Law is exposing a proof gap, not just a repair gap

The sector's challenge is not only doing the work. It is proving, end-to-end, when risk was identified, how it was classified, what was done, and whether the home was made safe in time.

The Housing Ombudsman's recent decision against the London Borough of Lambeth is the cleanest example. The Ombudsman noted that the landlord provided very limited records - missing inspection reports, completed works records, repair records, and contractor correspondence - and explicitly said it could not determine key facts about inspections and works.

That is not a story about whether the right thing happened. It is a story about whether anyone could prove it had.

The same pattern shows up across the sector. The inspection happened. A mould wash happened. Follow-on work was raised somewhere else. But nobody can evidence the statutory chain end-to-end.

Reactive case handling cannot manage portfolio-level risk

A case-led model starts when the resident reports the problem. That is too late to be your only control model.

The risk has usually been building for months through earlier repairs, access failures, complaint contact, partial fixes, and quietly accumulating signals. By the time the formal complaint arrives, the home has been telling you something for a long time.

The Ombudsman's March 2026 severe maladministration report calls damp and mould a "grey rhino" - a visible, foreseeable risk that was still overlooked. It also warns that roofs, windows, overheating, and heating loss could become the next major drivers as Awaab's Law expands.

The scale is in the Ombudsman's own numbers from the Repairing Trust spotlight:

474%
more complaints about poor living conditions vs 2019–20
72%
of those linked to poor practice by the landlord
27 Oct 2025
Awaab's Law fixed timescales came into force

The shift the regulator is asking for is not "respond faster". It is "see earlier".

A property has had two damp jobs, one leak, one missed access attempt, and a complaint contact over twelve months. Each event looks manageable on its own. Together, they describe a developing risk profile - and the signals were all sitting in your systems before the breach.

Most landlords already hold the signals - they are just fragmented

The barrier here is rarely the absence of data. It is the fragmentation of it.

The Ombudsman's Knowledge and Information Management report makes this point directly. It says landlords need databases that capture residents' vulnerabilities, repairs history, and property information such as stock condition - and that those systems must be easy to interrogate so the data can actually be used. It also highlights cases where systems were not effectively speaking to each other.

In practice, the same tenancy story is split across half a dozen places:

  • The housing record sits in something like Civica, NEC, MRI, or Orchard
  • Contractor scheduling sits somewhere else
  • Stock condition sits in an asset tool, a survey file, or a spreadsheet
  • Complaints sit in CRM or casework
  • Vulnerabilities sit in a tenancy or safeguarding record
  • Reporting sits in Power BI or Excel

Each system is doing its job. None of them, on their own, can tell you that a single home has been quietly escalating for nine months.

This is the structural problem. The data exists. The judgement is missing because the picture is missing.

Repeatable workflow beats heroics

One strong surveyor, one experienced manager, or one person who "knows the stock" is not a control model. It is a single point of failure.

The Ombudsman's special investigation into Hackney found exactly this kind of weakness - issues in risk assessment and prioritisation, in knowledge and information management, and in the use of performance data to drive improvement.

In other words, activity was visible, but control was weaker than it looked.

“

The sheer number of plans and actions created the impression of activity, but did not translate into an ability to get the basics right consistently.

”
— Housing Ombudsman, Hackney Special Investigation

The pattern is recognisable across the sector. The surveyor knows which blocks worry them. The manager knows which contractor codes hide repeat damp cases. But that knowledge lives in people, not in a repeatable process. The day one of them leaves, visibility drops.

A control model needs four things that do not depend on individuals:

  • Triage - clear rules for how a signal becomes a case, and who owns it
  • Prioritisation - a defensible, repeatable view of which homes warrant attention now
  • Escalation - ownership that moves up the chain when timescales slip
  • Auditability - the chain of action evidenced end-to-end, by default, not on request

Done properly, this pays back beyond compliance

The same control layer that helps you respond effectively under Awaab's Law sharpens the rest of the operation too.

The Ombudsman's Spotlight on Repairs and Maintenance does not just call for better complaint handling - it explicitly recommends moving from reactive to predictive maintenance models. The KIM report makes the same case from the other direction: organised systems reduce the cost of responding and improve the ability to identify patterns and shortfalls.

Joined-up insight on property and resident risk supports planned maintenance decisions, reduces repeat visits, helps prevent complaints before they escalate, and gives leaders a clearer view of where trust is starting to break down.

It turns compliance work into something more valuable: a clearer operating view of stock risk, service failure, and emerging resident harm.

Compliance is the floor. The ceiling is a housing organisation that knows what is going on across its stock, can explain why it acted, and can show its workings.

"But we tried a dashboard project two years ago"

This is the objection worth taking seriously. It is the one a Director of Property would actually raise - and they would be right to.

That scepticism is fair. A dashboard is not a control model.

The problem with the last dashboard project was probably not that the data was useless. It was that the workflow stayed the same:

  • Triage rules did not change
  • Ownership and escalation did not change
  • Case coding did not improve
  • Live risk lists did not exist
  • Nobody became accountable for intervention before complaint escalation

Without those things changing, a dashboard is just a prettier window onto the same problem. The Ombudsman's repeated focus on weak prioritisation, poor knowledge management, and the underuse of performance data makes the point bluntly: better visibility only matters if the operating model changes alongside it.

The work is not building a dashboard. The work is closing the loop between signal, decision, action, and evidence - and making that loop default behaviour, not a project.

The organisations that struggle most will not be the ones that care least. They will be the ones who cannot see risk building early enough to act with confidence.

Where JDynamics fits

JDynamics helps housing organisations join up fragmented property, resident, and operational data so they can move from reactive case handling to proactive attention and stronger evidence.

Today, that work is consulting-led: reviewing the data you already hold, identifying proof and control gaps, designing the workflow logic, and producing usable outputs such as joined-up reporting, exception views, and risk lists.

In parallel, we are building a reusable data layer for this exact challenge: earlier warning, clearer prioritisation, and stronger evidence across homes and residents.

This is not a claim to a finished platform. It is about being clear-eyed on what Awaab's Law is actually asking for - and helping housing leaders close the gap between the data they hold and the proof they need.

Awaab's Law is raising the bar on response, but the deeper challenge is visibility, consistency, and proof.

If your team is wrestling with proof gaps, fragmented systems, or the shift from reactive response to proactive attention, JDynamics would be glad to talk it through with you - and help you identify the next sensible step.

Sources & further reading

Want to discuss this further?

We'd love to hear how this lands with your organisation's challenges. Get in touch for a no-pressure conversation.

Get In Touch