BUILDING CONDITIONS
Damp and mould risk monitoring
Identify persistent conditions that need attention, prioritise property investigations and assess whether remedial work improves the environment.
Housing and property teams need more than a reading taken during one visit. Connected monitoring can show how temperature and humidity change over time, supporting a fuller understanding alongside residents’ reports, inspections and building history.
ON THIS PAGE
What we monitor
Real-world example: MuirCroft Housing Association
Illustrative application scenario
What your team sees in NesosIQ
What a pilot should establish
From pilot to portfolio
01
What we monitor
Temperature and relative-humidity sensors can highlight prolonged humidity and changing room conditions. Where the investigation calls for it, suitable surface-temperature or moisture measurements can add context. Calculated dew point and condensation-risk indicators depend on the measurements and assumptions used.
02
Illustrative application scenario
For example, a resident reports recurring mould in a bedroom. The housing team acts on the report, inspects the property and uses monitoring to understand the pattern. After repairing a defect or improving ventilation, it compares conditions and follows up with the resident.
Environmental sensors do not confirm that mould is present, identify its species or establish the cause of damp. Monitoring must support prompt investigation; it should never delay repairs or be used to assign blame to occupants.
REAL-WORLD EXAMPLE
MuirCroft Housing Association
MultiTech describes a deployment with MuirCroft Housing Association and Cherry & White using 102 environmental sensors and two gateways. Temperature and relative-humidity readings help the housing team identify conditions that warrant investigation and prioritise maintenance. The example demonstrates how connected monitoring can support an earlier conversation and a targeted property visit; the measurements do not themselves confirm the presence or cause of mould.
Third-party project featured in the LoRa Alliance success-story directory. This is not a Nesos IoT deployment; reported results relate to this project.
03
What your team sees in NesosIQ
Review room and property trends, duration of agreed threshold conditions and comparisons before and after work. Portfolio views can help prioritise inspections and identify properties with recurring patterns. Data can be shared through scoped integrations with existing housing or repairs processes.
04
What a pilot should establish
Agree the purpose with residents and explain what is collected and who can see it. Choose representative properties, validate placement and coverage, and combine data with survey findings. Measure time to investigation, follow-up completion and recurrence after repairs, rather than treating a dashboard score as proof of a healthy home.
Access, retention and response responsibilities are agreed at the outset. Device-agnostic selection allows the measurements to match the property and the survey question.
Further guidance: Government guidance on damp and mould (England; local requirements should be assessed separately).
FAQS
Frequently asked questions
Quick answers about how this works, what your team sees and how a deployment starts. For anything else, talk to us.
-
Temperature and relative-humidity sensors can highlight prolonged humidity and changing room conditions. Where the investigation calls for it, suitable surface-temperature or moisture measurements can add context. Calculated dew point and condensation-risk indicators depend on the measurements and assumptions used.
-
Review room and property trends, duration of agreed threshold conditions and comparisons before and after work. Portfolio views can help prioritise inspections and identify properties with recurring patterns. Data can be shared through scoped integrations with existing housing or repairs processes.
-
Agree the purpose with residents and explain what is collected and who can see it. Choose representative properties, validate placement and coverage, and combine data with survey findings. Measure time to investigation, follow-up completion and recurrence after repairs, rather than treating a dashboard score as proof of a healthy home. Access, retention and response responsibilities are agreed at the outset.
-
No. Nesos IoT deployments use LoRaWAN, a low-power wireless standard designed for monitoring across buildings and estates, so devices do not rely on building Wi-Fi. Network design, gateway connectivity and a site survey are confirmed for each project so coverage fits the environment.
-
Your organisation does. Nesos IoT does not manage alerts or operational responses: your team defines the thresholds, notification routes and response procedures, and NesosIQ can connect to your existing systems through APIs and agreed integrations.
-
Yes. Suitable applications can share the same estate network and NesosIQ platform, so you can start with one challenge and add further monitoring as your needs grow. Our device-agnostic approach selects compatible equipment for each task.
-
We follow Discover, Survey, Pilot, Deploy, Integrate and Scale, starting with a focused pilot that validates measurements, coverage and the operational response. Nesos IoT is based in St Helier, Jersey, and works across the Channel Islands and beyond. Call +44 (0) 1534 753225 or email info@nesos.co.uk.
NEXT STEPS
From pilot to portfolio
We follow Discover, Survey, Pilot, Deploy, Integrate and Scale: agree the operational need, validate devices and coverage, commission the solution and connect it to the people who will act. Device choice, reporting intervals and integrations are confirmed for each project. Suitable applications can share the estate network and NesosIQ platform.