YEMIX
Skip the story
Somewhere in the stock, a clock is already running. Scroll, and watch a system take it back.
No login. No app. No hold music. A resident describes the mould in her bathroom and mentions her mother is 81 with COPD. The moment it arrives, the landlord is legally made aware — and that timestamp, not the triage, is what every deadline is measured from.
Yemix reads the report and proposes a lane from a points matrix anyone can read — severity indicators, recorded vulnerability, and hard overrides for known dangerous combinations. Then a named officer confirms it inside a time window. Miss the window and the case escalates. There is no route by which it quietly downgrades.
A surveyor is assigned automatically and the resident is texted a link showing his real availability — every slot offered sits inside the statutory window. No call centre, no waiting on hold, no appointment that quietly breaches the deadline because nobody checked the date against the law.
Property details, moisture readings room by room, photographs, HHSRS category, remedy — captured on site in the structure a proper inspection already follows. Then one press, and the work that normally takes a fortnight of emails happens before he has left the building.
The findings letter is approved and sent — the three working-day duty, discharged. The same link now shows the contractor's availability, and she books the repair herself. If nobody is home when he arrives, the system re-books it automatically and puts the failed attempt on the record where it belongs.
Mould treated, the wall coated, a humidistat extractor fitted. The contractor checks in on site, photographs the finished work and signs it off from his phone. Every timestamp, every photograph, every hand-off is already on the case — not reconstructed from an inbox eighteen months later.
This is the only thing that closes a case. Not the contractor's sign-off — the resident's own confirmation. If she says it isn't fixed, the case reopens on the spot and the clock she was owed comes back with it. Where the hazard was Category 1, a re-inspection is booked automatically.
Now zoom out
Every hazard in the stock carries its own ring. The ones about to breach are the only ones that ask for your attention — which is the entire point.
Break it yourself
This is the real scoring logic, running in your browser. Tick what a surveyor would tick and watch the lane 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 anonymised historic cases. We'll show you the lane Yemix proposes against the decision your team actually made — before anything is signed, and at no cost.
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, two sets of clocks, and one resident who made one phone call.
No — and you can verify that above. The lane comes from a deterministic points matrix plus hard overrides for known dangerous combinations. AI may pre-fill the triage form from the report wording, but a person confirms Emergency and Significant inside a defined window. If the window passes the case escalates. The matrix 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. Every triage decision stores its score, its reasoning and the person who confirmed it. A DPIA and processor agreement are completed before any real tenant data enters the system.
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.