The prospect of a regulatory inspection can make every reporting gap feel urgent. Suddenly, disconnected systems, missing contractor updates and inconsistent records become part of a much bigger question: can we demonstrate that we are managing hazards effectively?

The Regulator of Social Housing expects landlords to evidence how they deliver the outcomes of its standards. With Awaab’s Law setting requirements for responding to hazards, providers should be prepared to explain both their performance and the evidence behind it.

After 20 years working with social housing interfaces, integrations and repairs systems, my starting point is practical, and based around understanding where you are, addressing the most important gaps and making your progress visible.

Today: establish what you can actually evidence

Start with a small sample of live and recently closed hazard cases. Follow each one from the initial report through investigation, action and communication with the resident.

Can you establish when the organisation became aware of the issue? Can you identify the relevant deadlines, who owns the next action and what evidence supports the recorded outcome?

Include cases involving contractors. Their activity needs to be visible alongside work delivered internally.

Record where the trail breaks. Perhaps an inspection sits outside the case record, or a completed repair has no supporting information attached.

The immediate task is to establish what you know and act on any urgent safety concerns. Don’t wait for a reporting project to address a resident’s risk.

Within a week: agree the gaps, owners and priorities

Bring together repairs, compliance, customer services, IT and the people managing contractors. Use those sample cases to discuss the actual process, rather than how everyone assumes it works.

Agree the key information needed to manage a case and report its progress. Define what important milestones mean, particularly terms such as “investigated”, “made safe” and “complete”.

Then create a prioritised action log. Each gap should have an owner, a target date and a clear description of what resolving it will achieve.

Separate immediate operational controls from longer-term system improvements. A missing escalation route may need attention today, while improving an interface may require planned development.

In this initial window, you should have a shared view of the problem and an accountable plan, not just a list of technology requests.

Within a month: improve one complete information journey

Choose a manageable priority and improve it from end to end.

That might mean ensuring inspection findings link reliably to the original case, bringing contractor updates into reporting, or making approaching deadlines easier to identify.

From a Microsoft Dynamics perspective specifically, I would look at how records, workflows and interfaces support that journey. Are people entering the same information twice? Are essential fields clear? Does the next team receive enough information to act?

Test changes with the people using them. A process that looks logical in a workshop may still be difficult to follow during a busy working day.

Establish a reporting baseline, including missing information and exceptions. An honest view of incomplete records is more useful than a reassuring dashboard that excludes them.

Within a quarter: demonstrate a repeatable improvement cycle

The aim over a quarter should be to move beyond isolated fixes towards a process you can sustain.

Repeat the case-sampling exercise. Check whether the original gaps have reduced, whether new controls are being used and whether contractor information is arriving as agreed.

Report progress against the baseline. Explain what has improved, what remains unresolved and how outstanding risks are being managed.

Keep evidence of those changes: tested workflows, agreed definitions, quality checks and completed actions.

An improvement plan is not a substitute for meeting existing duties. This timetable is a way to organise stronger systems and reporting, not a signal to delay action required under Awaab’s Law.

Connect the information, without losing sight of the service

This is where iLumen8 fits into the wider picture: connecting repairs, asset and compliance information to support clearer reporting on hazards, response times and case progress.

The reporting layer should help teams understand their position. The underlying processes and integrations should help keep that position accurate.

Neither works well in isolation.

When scrutiny comes, you need more than an ambition to improve. You need to explain your current position, show the action being taken and support that account with evidence.

Start with one case, one broken handover or one missing connection. Make the improvement, test it and build from there.