What Software Do Housing Associations Need to Comply with Awaab's Law?
By Crocker Digital Ltd · Published 22 July 2026
Since Awaab's Law Phase 1 came into force in October 2025, housing associations have needed software that does something specific: calculate working-day statutory deadlines, flag cases at risk of breach, and produce an audit trail that survives a Housing Ombudsman investigation.
Most software available to small providers — spreadsheets, general property management platforms, and enterprise housing management suites — was built before this compliance obligation existed. This post sets out what the law actually requires from your systems, where the gaps are in current tools, and what purpose-built compliance software needs to do.
For the regulatory background, see The Complete Guide to Awaab's Law. For a comparison of the main software categories (spreadsheets, general property management, and enterprise suites), see Housing Association Repairs Tracking: Picking a Case Management Approach Without Enterprise Cost.
What Awaab's Law Actually Requires from Your Software
The Hazards in Social Housing (Prescribed Requirements) (England) Regulations 2025 (SI 2025/1042) set out four distinct deadlines per case (emergency hazards have a compressed single 24-hour window):
| Stage | Deadline |
|---|---|
| Investigation | 10 working days from awareness |
| Written summary to tenant | 3 working days from investigation |
| Make-safe works | 5 working days from investigation |
| Supplementary works begin | 5 working days from investigation (steps to begin); 12-week longstop for physical start |
Each deadline: (a) runs from a different start event, (b) uses working days (not calendar days), and (c) requires dated evidence of completion. For supplementary works the operative duty is to "begin, or take steps to begin" the work within 5 working days of the investigation concluding; if steps cannot be taken in that window, the work must be physically started within 12 weeks.
Your software needs to track all four per case — automatically, from the moment awareness is logged — and alert the responsible officer before each one breaches. This is not a bonus feature. It is the core compliance function Awaab's Law creates.
Where Spreadsheets Fall Short
Most housing associations under 5,000 units are still managing Awaab's Law cases in spreadsheets. This can work at very low case volumes, but it fails in three predictable ways:
1. Working-day calculation is manual and error-prone. A "10 working days from 22 April 2026" calculation requires counting forward, skipping weekends, and checking the bank holiday calendar for England and Wales. Multiply that by 50-200 open cases, and manual calculation becomes the source of compliance failures rather than the defence against them.
The deadline calculator handles individual cases correctly — but it does not automatically propagate those calculations to a caseload-level view.
2. There is no proximity alert. A spreadsheet can tell you a deadline exists. It cannot tell you "this case has 2 working days remaining" without someone actively looking at each row and calculating from today's date. By the time you discover a breach in a spreadsheet review, it has already happened.
3. The audit trail is scattered. Investigation reports are in email. Photographs are in a shared drive. Contractor records are in a separate system. The written summary to the tenant was sent by post and never scanned. When a Housing Ombudsman information request arrives — and the Ombudsman made 7,082 determinations in 2024-25 — assembling this is a full-day job per case.
What General Property Management Software Misses
General property management platforms (tools built for rent collection, maintenance logging, and tenant records) were not designed around statutory deadline tracking. Common gaps:
- No working-day deadline engine. These tools often have "due date" fields, but not "10 working days from event X, accounting for bank holidays" logic.
- No proximity alerting. Case reminders are typically date-based ("remind me on [date]"), not deadline-proximity-based ("flag cases within 3 working days of any active deadline").
- No structured evidence capture. Document storage exists, but it is usually attachment-based rather than structured around the Awaab's Law case lifecycle (awareness → investigation → written summary → make-safe → supplementary works).
- No case-level audit export. Producing a chronological evidenced case record for an Ombudsman information request requires manual assembly from multiple modules.
This does not make these tools useless — for rent tracking and maintenance logging they remain appropriate. But they require significant manual work on top to meet Awaab's Law compliance requirements.
What Purpose-Built Compliance Software Needs to Do
The minimum viable feature set for Awaab's Law compliance software — not a wish list, but what the law's requirements actually imply — is:
1. Automatic awareness timestamping
The compliance clock starts when the landlord becomes aware. The software must capture the awareness event automatically, with a timestamp the software controls, not a date the user enters later.
If a housing officer can backfill the awareness date to a later date than it actually occurred, the timestamp is unreliable as an audit artifact. The system should record "report received at [timestamp]" from whichever channel it was received on, and treat that as immutable.
2. Working-day deadline calculation — four deadlines, automatically
From the awareness timestamp, the software should calculate all four statutory deadlines automatically: investigation (10wd from awareness), written summary (3wd from investigation), make-safe (5wd from investigation), supplementary works begin (steps to begin within 5wd from investigation, with a 12-week longstop for physical start).
These should recalculate dynamically when the investigation is logged — the three post-investigation deadlines start from that date, not from awareness.
3. Traffic-light proximity alerting at the caseload level
The responsible officer should open the dashboard and immediately see: how many cases are green (well within deadline), amber (approaching), and red (1-2 working days remaining). Individual case inspection should not be required to identify at-risk cases.
The alert thresholds should be configurable — a provider with a large repairs team may set amber at 5 working days; a smaller team may prefer 3.
4. Structured evidence capture per stage
Each stage in the case lifecycle should have a structured evidence record attached to it:
- Awareness: channel, receiving officer, original report description
- Investigation: date, assessor name, findings, photographs, damp readings if applicable
- Written summary: dated copy of what was sent to the tenant (not just "sent")
- Make-safe works: contractor attendance record, dated
- Supplementary works: works specification, start evidence
"Document storage" is not a substitute for structured capture. The structure is what makes the audit trail producible without manual assembly.
5. One-click case-level audit trail export
When a Housing Ombudsman information request arrives, the officer should be able to pull the complete case history — all stages, all evidence, all dates — in a single export. Not a full-database export: a case-specific chronological record that demonstrates compliance at each stage.
Format matters: a PDF is more defensible than a raw data export, because it shows the timeline as a document rather than requiring the investigator to interpret fields.
6. Pricing proportionate to the unit count
Enterprise housing management suites handle Awaab's Law correctly — they cost £10,000+/year and require multi-month implementations. For a housing association managing 200-2,000 units, the price should be proportionate.
A realistic target for purpose-built SaaS in this segment is under £100/month per compliance user, or £1,000-1,500/year for a typical small-to-medium housing association team.
How to Evaluate Any Tool Against These Requirements
If you are evaluating a tool — whether a repurposed general property management platform or a purpose-built Awaab's Law tool — run through this checklist before committing:
- Awareness timestamping: Can the user backfill the awareness date? If yes, the timestamp is not audit-reliable.
- Deadline calculation: Enter a real case (hazard reported 22 April 2026). Does the tool give you an investigation deadline of 7 May 2026 (accounting for the early May bank holiday)? If it gives you 6 May or 2 May, the calculation is wrong.
- Proximity alerting: Open the main dashboard with 10 hypothetical cases at various stages. Can you immediately see which ones are approaching a deadline — without opening individual records?
- Audit export: Ask the vendor for a sample audit trail export for a single case. Does it contain all stages, all dates, and enough evidence detail to satisfy an Ombudsman information request?
- Implementation time: For a small housing association, implementation should take hours or days, not months. A tool requiring a 6-month implementation is not sized for your organisation.
Use the compliance checklist to walk through the full Awaab's Law case lifecycle — any software you bring in should support each stage of that workflow.
What This Means for Your Current Gap
The segment that does not have good software today is housing associations under 5,000 units — the majority of registered providers who are too small for enterprise housing management suites and whose current general property management software does not meet Awaab's Law requirements.
HazardClock is being built specifically for this gap: deadline tracking, proximity alerting, structured audit trail, and case-level export at a price point that works for providers under 5,000 units. The three free tools on this site — the deadline calculator, the phase checker, and the compliance checklist — are the starting point. The full caseload product is in development.
Join the waitlist to get early access and be notified when HazardClock launches.
This is general guidance for UK housing associations and registered providers, not legal advice or a software recommendation. The regulatory requirements set out above derive from the Hazards in Social Housing (Prescribed Requirements) (England) Regulations 2025 and associated GOV.UK guidance.
Sources
Stop Tracking Deadlines in Spreadsheets
HazardClock calculates every Awaab's Law deadline automatically, sends countdown alerts before they expire, and builds an audit trail for investigations.
Related Articles
How to Comply with Awaab's Law: A Step-by-Step Guide for Housing Associations
A step-by-step compliance framework for housing associations under Awaab's Law — from recording awareness to closing a case with an audit-ready evidence trail.
Awaab's Law Emergency Hazards: The 24-Hour Rule and How to Meet It
Emergency hazards under Awaab's Law must be investigated and made safe within 24 hours — calendar hours, not working days. Here's what counts as an emergency, how the clock runs, and how small providers meet the tightest deadline in the regime.
What Is a Complaint Handling Failure Notice? How Small Providers Can Avoid One
A Complaint Handling Failure Notice is the Housing Ombudsman's enforcement tool for landlords who miss the Complaint Handling Code's timescales or submissions. Here's what triggers one, how it differs from a Failure Order, and how small providers avoid both.