SI 2025/1042 · 10 / 3 / 5 working days · 24 calendar hours
The deadline starts whether or not anyone opened the message.
Awaab's Law counts from the day after you became aware — not from the day somebody read the report, assigned it, or came back off leave. Evidix starts the clock at the moment of awareness and counts it properly.
Last updated 9 October 2026
The pain
What this feature fixes.
Awareness is the trigger, not attention.
A tenant reports damp at 11pm on a Friday. Nobody opens it until Monday. The statutory clock began on Saturday, and by the time it is triaged you have spent two of your ten working days doing nothing.
Working days are not days.
Ten working days is not two weeks. It depends on which weekend falls inside it and whether a bank holiday lands in the middle. Counted by hand, on a calendar, that arithmetic goes wrong quietly and in the wrong direction.
The emergency clock plays by different rules.
Twenty-four hours for an emergency is calendar hours. It does not pause at 5pm, it does not pause on Saturday, and it does not care that the investigation clock beside it does both.
How it works
What you get when you turn this on.
- 10 working days to investigate, from the day after the landlord becomes aware — extended correctly when the tenant asks for a physical inspection
- 3 working days after each investigation to give the written summary, issued as a PDF with every part the regulations require, by email, in the tenant portal and with an SMS notice
- 5 working days to make the property safe where the hazard is significant
- 24 calendar hours for an emergency — gas, electrical, structural and the rest, not only damp — counted in real time, not working time
- After making safe: keep safe, begin preventative work within 5 working days, and the 12-week limit — each tracked as its own duty
- Alternative accommodation and written safety advice when a home cannot be made safe in time
- Weekends and bank holidays excluded automatically, from an officially synced calendar
- No clock pauses, as the law requires — every access attempt, consent request and reason for delay recorded as evidence of reasonable endeavours
- Applied where they are statutory — social tenancies, per section 10A — and tracked as an internal service standard everywhere else
- Every action stamped onto the same record as the original report, with who did it
[ Hazard Clocks — screenshot Wave 1.5 ]
With and without
The operating-day difference.
Without Evidix
- The clock starts when somebody notices the message
- Ten working days counted on a wall calendar, including the bank holiday
- The emergency and investigation clocks treated the same way
- A hazard on agent-managed stock you learn about on Tuesday
- Proving your response after the fact, from four systems
- The case closed when the mould was wiped, with the preventative work forgotten
With Evidix
- The clock starts the day after the report lands, automatically
- Counted against a synced working-day calendar
- 24 calendar hours and 10 working days tracked as the different things they are
- One inbox across your managing-agent network, with the clock visible from the start
- Report, investigation, summary, works and outcome on one dated trail
- Keep safe and preventative work tracked to the 12-week limit, and a case that cannot close while a duty is open
Available on
Which plans include this.
Basic
Included
Professional
Included
Business
Included
Enterprise
Included
Hazard tracking is on every plan. The statutory Awaab clocks apply where they are statutory — social tenancies — and the same response trail is kept everywhere else.
A clock you did not start is still running.
See it start itself, from the message the tenant actually sent.