What to Look for in Awaab's Law Compliance Software

If you are evaluating compliance software for Awaab's Law, you have probably noticed that every vendor says they solve the problem. The demos are polished. The feature lists are long. But housing management platforms built for 50,000-unit landlords solve a different problem than the one facing a 2,000-unit housing association with two people in the repairs team.

This guide is not a product comparison. It is a checklist of the features that actually matter for Awaab's Law compliance — and the features you can safely ignore.

The 8 Features That Matter

1. Automatic working-day deadline calculation

This is the single most important feature. Awaab's Law deadlines run on working days (excluding weekends and England and Wales bank holidays). Any tool that requires you to manually enter deadline dates or calculate working days yourself is adding risk, not reducing it.

For background on all the timescales and phases, see The Complete Guide to Awaab's Law.

Test this: Enter a hazard reported on a Friday before a bank holiday weekend. Does the tool correctly skip the weekend and the bank holiday when calculating the 10-working-day investigation deadline? If it gives you a date 10 calendar days later, it does not handle working days. Try it yourself with the free deadline calculator to see what the correct dates should be.

2. Multi-phase hazard type support

Phase 1 covers damp, mould, and emergency hazards. Phase 2 (expected 2026) adds 13 more HHSRS hazard categories — falls, fire, electrical, excess cold/heat, structural collapse, explosions, and hygiene-related hazards. Phase 3 (2027) covers everything except overcrowding.

What to check: Can the system handle multiple hazard types with potentially different deadline configurations? If Phase 2 introduces a different timescale for certain hazard categories, can the tool be updated without replacing it? Many current tools were built exclusively for damp and mould — they may not scale to Phase 2 without a rebuild.

Use the Phase Checker to see all 29 HHSRS categories and their phase assignments.

3. Countdown alerts (not just dashboards)

A traffic-light dashboard is useful when you are looking at it. An email or SMS alert three days before a deadline expires is useful when you are not. The compliance failures that result in Ombudsman findings are rarely about not knowing the rules — they are about not acting on information that was available but not surfaced.

What to check: Does the tool send proactive alerts (email, SMS, or push notification) before deadlines expire? Can you configure the lead time (e.g. 3 days, 1 day)? Are alerts sent to the assigned officer and their manager, or just a generic inbox?

4. Evidence attachment and case timeline

Under Awaab's Law, landlords must keep clear records of all correspondence with the tenant and any contractors. When the Housing Ombudsman requests evidence, you need a single case timeline showing every action, communication, and document — with dates.

What to check: Can you attach photos, contractor reports, and email correspondence to a case record? Is there a chronological timeline view? Can you produce a complete case export (PDF or similar) for an external investigation?

5. Audit-ready export

A tool is only as useful as its output when it matters. The moment you need compliance evidence is during an Ombudsman investigation, a regulatory review, or disrepair litigation. If the tool cannot produce a clean, dated export of a single case — or a portfolio-wide compliance summary — it is not solving the audit problem.

What to check: Can you export a single case as a PDF with dates, actions, and evidence? Can you generate a compliance report across all open cases (e.g. "X cases within deadline, Y approaching, Z overdue")? Does the export include enough detail to stand alone without additional explanation?

6. Low onboarding complexity

As outlined in how small HAs can comply without enterprise software, a housing association with a two-person repairs team cannot afford three months of implementation, data migration, and training. If the tool requires Salesforce, Dynamics 365, or another platform as a prerequisite, the total cost and complexity are far higher than the licence fee suggests.

What to check: How long from sign-up to first case logged? Does it require integration with an existing housing management system, or can it run standalone? Can a new team member start using it within an hour?

7. Pricing that fits a small provider's budget

Enterprise housing management suites typically cost £10,000+ per year. For a housing association managing 2,000 units, that spend needs board-level approval and a business case. Awaab's Law compliance is a legal requirement, not an optional feature — the tool that serves you best is the one you can actually afford to buy and maintain.

What to check: Is pricing transparent (published or available on request without a demo call)? Is it per-user, per-unit, or flat-rate? Are there setup fees or mandatory training costs? What is the minimum contract term?

8. Tenant communication support

Awaab's Law requires a written summary to the tenant within 3 working days of the investigation concluding. Templates or auto-generated communications that include the correct case details and timescale references reduce the risk of non-compliant or delayed correspondence.

What to check: Does the tool include tenant communication templates? Can you generate a written summary from the case record? Are communications logged to the case timeline automatically?

What You Can Safely Ignore

Not every feature on a vendor's list matters for Awaab's Law compliance. These are common in enterprise platforms but unnecessary for a small provider focused on deadline tracking:

• AI-powered risk prediction — useful at scale, but a 2,000-unit HA needs deadline tracking before predictive analytics.
• Integration with national reporting systems — if you do not currently report to the Regulator via API, you do not need this on day one.
• Multi-tenancy and complex permissions — a two-person team does not need role-based access control with five permission levels.
• Custom workflow builders — the Awaab's Law lifecycle is well-defined (report → investigate → make safe → supplementary works → close). A tool that maps this lifecycle natively is more useful than one that lets you build it from scratch.

Before You Buy: The 30-Minute Test

Before committing to any tool, run this test:

1. Log a damp/mould hazard reported on a Friday before a bank holiday.
2. Check that the investigation deadline accounts for the weekend and the bank holiday.
3. Mark the investigation complete. Check the downstream deadlines (written summary, make safe, supplementary works).
4. Attach a test photo and a test document to the case.
5. Export the case as a PDF.
6. Check how long the entire process took.

If you cannot complete this in 30 minutes — including creating your account — the tool is too complex for your team's capacity.

Work through the compliance checklist to see the full case lifecycle that any tool should support.

This is general guidance, not legal advice. Always confirm your compliance approach against the latest GOV.UK guidance.

Sources

• Awaab's Law: Guidance for social landlords — GOV.UK
• Annual Complaints Review 2024-25 — Housing Ombudsman