Building the data foundations for Awaab's Law compliance reporting

A practical checklist for housing providers preparing for phase two and beyond

The operational demands of Awaab’s Law phase two are quite rightly taking centre-stage as the 30th of November deadline approaches. Housing providers are focused on meeting the rising demand on triage, managing response times, ensuring that reported hazards are being investigated properly, and much more.

The ability to evidence that all of those things are being achieved is vital, and being able to demonstrate compliance to the regulator, or even internally, cannot be ignored.

What hazard was reported? How was it categorised? Was the tenant situation considered to assess risk? Have we communicated with the tenant throughout the process? Exactly what action took place and how were those decisions made?

Answering these questions confidently requires more than records showing that repairs were completed. They need a complete and reliable evidence trail from start-to-finish.

From completed jobs to complete case histories.

A completed repair tells you something important, but it does not tell you everything about how a hazard was managed.

The wider picture includes the original report, triage decisions, relevant resident circumstances, inspections, communications, safety measures, remedial works, and the reasons for closing the case.

In many cases this information already exists, however it may be in one spreadsheet, or a different spreadsheet, some is in the data management system, or in contractor systems.

When that data is disconnected, building that thread of evidence becomes a data scavenger hunt. Time gets wasted as teams search for data and build that evidence thread backwards.

The priority is therefore not simply to collect more data. It is to make existing information consistent, connected, and usable.

Five practical steps to strengthen your reporting foundations

1. Map the evidence trail you have today

Start by following a reported hazard through your organisation, from first contact to case closure.

Which teams become involved? Which systems do they use? Where are decisions recorded, and how does responsibility move between colleagues or contractors? What event starts the clock, and can you reliably identify it from the data? Can information from one stage be reliably linked to the next?

Look beyond the intended process. Understanding what happens in practice will help identify where evidence becomes difficult to retrieve or where important context is lost.

2. Agree what every case needs to record

Consistent reporting depends on shared definitions and expectations.

Your teams need a common approach to hazard classification, relevant risk factors, key dates, applicable deadlines, case status, ownership, actions and outcomes and the information required at each stage. Where relevant to assessing risk and prioritisation, appropriate information about resident circumstances needs to be available to those making those decisions.

Set clear expectations for recording actions, communications, and delays, including their causes and the steps being taken to resolve them.

Without that consistency, seemingly comparable reports may be measuring different things.

3. Find the gaps and establish why they happen

Missing information is not always a system problem. It may reflect an unclear responsibility, an inconsistent process or a handover that does not capture enough detail.

Check whether you can evidence triage decisions, explain delays, trace resident communications, and justify case closure.

Where information is missing, establish who should provide it and what needs to change. A reporting gap is not always something a new dashboard can solve. If an inspection outcome is not recorded, a delay reason is inconsistent or communication activity cannot be linked back to the case, reporting can expose the problem, but it cannot manufacture the missing evidence.

4. Create a connected, trusted reporting view

Different users need different levels of detail, but they should be working from a consistent picture.

Officers need to see what needs attention today.

Managers need visibility of cases approaching deadlines, stalled, incomplete or potentially outside the expected process.

Boards and executives need a view of where the organisation is seeing risk, recurring issues, or systemic weaknesses.

At an organisational level, connected data can also help reveal repeated hazards, property or geographic patterns, recurring causes of delay and areas where processes are creating avoidable risk. It also reduces reliance on spreadsheets passed between inboxes to explain what is happening.

5. Test the evidence, not just the reporting

A dashboard can look reassuring while the supporting records remain incomplete.

Select a sample of cases and try to reconstruct them without relying on the people who managed them. Can you determine what was reported, how the risk was assessed, what deadlines applied, what action was taken, what the resident was told, where delays occurred and why the case was closed?

Use those checks to improve workflows and reporting standards. Readiness should be something you review continuously, rather than a one-off exercise.

Better foundations, more useful reporting

Being able to evidence your position after the fact is absolutely crucial, but reporting should also be useful while cases are ongoing. Spending time digging for information isn’t helping your organisation, and it isn’t helping your residents.

A connected view can help teams identify approaching deadlines, understand outstanding actions, and recognise where information is missing.

This is the thinking behind iLumen8. Rather than viewing repairs, hazards, assets, and compliance information in isolation, we bring data together to create a clearer picture of each case and the wider organisational position.

That means reporting can support both sides of Awaab’s Law readiness: helping operational teams understand where attention may be needed now, while giving management and boards a clearer evidence base for understanding compliance, risk, and emerging trends.

Technology alone cannot create compliance. Clear processes, ownership, and good-quality source data remain essential. But once those foundations exist, reporting can become much more than a retrospective assurance exercise.

I’ll leave you with two simple questions. If you were asked today which hazard cases need attention, which are approaching key deadlines and why, could your data give you the answer?

And if your board or the regulator then asked you to evidence the full journey of one of those cases, could you do that just as confidently?

If you're assessing whether your current data can provide that level of visibility, talk to us. We can help you identify where the reporting foundations are strong, where the gaps sit and what a more connected view could look like.