YEMIX
Skip the story
Somewhere in the stock, a clock is already running. Scroll, and watch the software take it apart.
The Awaab's Law clock starts the second the resident registers the report — not when someone gets round to reading it.
Hazard type, HHSRS severity indicators and recorded vulnerability, scored against a readable matrix — and the statutory deadlines that follow from it, set automatically.
Every slot it offers sits inside the statutory window. It cannot offer one that breaches.
The moment the inspection is saved, the work that normally takes a fortnight of emails is already done.
The findings letter meets the three-working-day obligation, the works order is costed and dispatched, and a failed visit re-books itself and stays on the record.
Every timestamp, photograph and hand-off captured as it happened — an audit trail built in real time, not reconstructed from an inbox eighteen months later.
One case, one place,
every clock.
Automate every hand-off. Confirmation is a dial, not a switch.
Every hazard in the stock carries its own ring, its own clock, its own deadline. This is what a repairs team is actually holding.
Yemix sorts every open hazard by how close it is to breaching its statutory deadline: four are imminent, eighteen are past halfway, seventy are comfortable, and sixty-six are closed and confirmed.
Try it
This is the real scoring logic, running in your browser — a readable points matrix, not a black box. Tick what a surveyor would tick and watch the lane and the deadlines change. Then tell us the weightings are wrong, because calibrating them against your own stock is the first week of the pilot.
Severity indicators — damp and mould
Recorded vulnerability — stated, never inferred
Thresholds: Emergency ≥ 70 · Significant ≥ 40. Thirteen hard overrides force Emergency regardless of score — mould in a sleeping room where someone has a respiratory condition is one of them.
Send us a handful of your own anonymised cases and we will run them through Yemix and show you, side by side, the lane it proposes against the decision your team actually made. Request a demo and we will send you a short template for exactly the information we need.
10–20 anonymised historic cases with their outcomes. We return a side-by-side against your team's own decisions. No fee, no commitment.
Running on real cases. Measured weekly: agreement rate, over-escalations, and missed emergencies — the number that has to stay at zero.
What it caught, what it cost, what it saved — written up as your business case. If it doesn't earn the next step, you keep the data and the report.
Awaab's Law, answered plainly
Section 10A of the Landlord and Tenant Act 1985 places statutory time limits on social landlords for investigating and fixing prescribed hazards. Emergency hazards require action within 24 hours of the landlord being made aware. Significant hazards require investigation within 10 working days, written findings to the resident within 3 working days of that investigation, and safety works begun within 5 working days of the findings.
It extends those timescales beyond damp and mould — to excess cold and heat, falls, structural collapse, fire and electrical hazards, carbon monoxide, and hygiene, sanitation and water supply. Each hazard on a case carries its own clock, so the number of deadlines multiplies even where the case count does not. One property with a leak near a light fitting is two hazards, two workstreams and two sets of clocks.
No — and you can verify that above. The lane comes from a deterministic points matrix plus hard overrides for known dangerous combinations. The matrix is readable, auditable and configurable, every decision stores its score and its reasoning, and the weightings are tuned against your own stock during the pilot. It is deliberately biased to over-call rather than under-call.
Vulnerability is special-category data under Article 9 of the UK GDPR. Yemix records it only where the resident has stated it or it sits on the tenancy record — never inferred from photographs, names or patterns. A DPIA and processor agreement are completed before any real tenant data enters the system, with UK data residency, role-based access and a retention schedule agreed with you.
In front of it, not on top of it — the triage-and-clock layer between the call handler or portal and the system you already pay for. The integration is a formal piece of work involving API credentials and a data-sharing agreement, which we scope properly with your account manager rather than promise casually.