See damp and mould coming and prove you did something about it.
Sensors and risk prediction spot a mould-risk home weeks early, alert your team, and build the evidence record as you work - all plugged into your own systems and run by your own people and contractors. You keep control.
Same sensors, same record. Switch whenever you like.
Built around the Awaab's Law workflow.
Portfolio dashboard
Every property at a glance - how much of the time each home is at risk of mould, a colour-coded map of your whole portfolio, and an alerts list sorted by which deadline is closest.
Property-level view
Open any property to see its Mould Risk Score over time, the sensor readings behind it, every alert, and a log of the repairs done.
Alerts with the clock attached
Every alert opens with the Awaab's Law deadline showing (England). You can see at a glance how much time is left - for example, 6 hours into the 24-hour emergency response, or day 8 of the 10 working days to investigate.
Evidence pack export
One click produces a dated PDF with everything the Housing Ombudsman would ask to see if a case is challenged - the sensor readings over time, what the investigation found, the work done, and proof it was finished.
Integrations
MouldWatch connects to the systems you already use - your disrepair, case-management, and CRM software - and can export data as a spreadsheet. (Technical detail: webhook, REST API, and CSV.)
Vulnerable resident flags
Priority tags for households with vulnerable occupants (age, health, pregnancy) so your team routes and communicates accordingly.
This is preventative maintenance, not a fire alarm.
The first question every operations team asks: "will this flood us with alerts?" No. Three lines of defence sit between a sensor reading and your team's workload - and you decide where the last one lives.
The model is slow to cry wolf.
Mould risk is not a binary event. It builds over weeks, and the platform tracks it the same way: a graduated risk state per room, not a siren per reading. One bad reading never fires - only a pattern that holds. Most homes sit green most of the time.
The routing is yours.
Alerts are configurable by property group, team, and time window - your out-of-hours rota is not woken for an amber trend. And every alert keeps its own audit trail: who was notified, when, and what was done. That trail is evidence you can put in front of the Ombudsman.
A red alert today is a complaint that never gets made next winter.
Nothing. The home is monitored and the record builds quietly. This is where most rooms sit, most of the time.
A nudge, not a dispatch. Fold it into the next routine visit or a resident call - ventilation advice, a heating check. Early, cheap, and usually enough.
Now someone goes. The case arrives with the sensor history, the likely cause, and the statutory clock attached - so the visit that follows is the right one.
Or route the noise away entirely.
If the worry is capacity, make alert-handling someone else's job. On full service, every alert lands with the Quidos Protect operations centre: a staffed triage desk in Cardiff, on call 24/7/365, already handling more than 80,000 calls and visits a year. Trained handlers grade each alert, act inside the statutory window, and escalate only what genuinely needs your decision.
Your team reads the morning summary, not the 3am alert.
Prefer to keep triage in-house? Everything above stays yours - the desk is an option, not a default.
See the full serviceAn alert becomes a job in your system. Nobody re-keys anything.
MouldWatch is built to feed the systems you already run, not replace them. The pattern is simple, and it is the same whether you use a housing management system, a repairs platform, or a council IoT stack.
The alert fires
A sustained risk state triggers an event carrying the property, the room, the risk history, and the statutory deadline already counting. One bad reading never fires - only a pattern that holds.
Your systems hear it
Webhooks and a REST API for event-driven integration. MQTT for councils already running IoT platforms. CSV export - any date range, any time - for everything else.
A job is raised
The work order lives in your repairs workflow, where your team already works. MouldWatch keeps its own audit trail of the alert, the response, and the readings after the fix.
Integration questions from your IT team? The trust and security page covers the API surface, the network, and where the data lives.
"The Mould Risk Score is an algorithmic indication of conditions conducive to mould growth. It is not a confirmation that mould is present. A high score without visible mould is a normal and expected outcome."
Run it yourself. See the live dashboard.
Prefer we ran it - the work, the fix, the report? See the full service. Nothing's locked in - same record, same clock, switch when you like.