A tenant reports mould in a bedroom. It is logged as a repair, categorised as routine, and joins a queue behind a dripping tap and a broken cupboard door. Six weeks later she reports it again, and this time she mentions her son's asthma.
Nothing in the first report told anyone that was relevant, because nobody asked.
The teardown: why these reports go wrong
They are received through a general repairs route, categorised by the type of job rather than the risk, and assessed by whoever is triaging on that day. Nothing in that process surfaces who lives in the property or how bad it is.
Failure one: no vulnerability question
Whether anyone in the household has a respiratory condition, is very young, elderly or has a health condition. This single question changes the priority entirely and is almost never asked at reporting.
Failure two: extent is not captured
One corner of a window reveal and a wall across a bedroom are different situations. Asking for the rooms affected, the approximate area and how long it has been there takes seconds.
Failure three: photographs are not requested
An image lets someone triage properly rather than guessing from a sentence. It also creates a record of the condition at the time of reporting.
Failure four: cause is assumed
Treating every report as condensation caused by the household, without inspecting, is how organisations end up in serious difficulty. Cause must be established, and it may be a defect.
Failure five: cleaning is treated as resolution
Wiping mould away and treating a surface does not address a cause. A case closed on a clean is a case that reopens, and the tenant learns that reporting achieves nothing.
Failure six: there is no follow-up
Checking back weeks later, after treatment and after any works, is what distinguishes a resolved case from a recurring one. It is also the evidence that the landlord acted.
Failure seven: the tenant is blamed in writing
Advice about ventilation and heating, sent to someone who cannot afford to heat their home, is both useless and damaging. Where behaviour is a factor, it is one factor, and it is discussed alongside addressing the property.
Failure eight: reports are not tracked as a category
A block with six reports has a building problem, not six tenant problems. Recording them as a distinct category is what surfaces that, which is the reporting discipline described in reporting questions from marketing clients.
What the reporting route must capture
Address, rooms affected, approximate extent, how long it has been present, photographs, whether anyone in the household is vulnerable, whether it has been reported before and a contact number.
Publish what happens next
Inspection timescale, what the inspection covers, how the cause is determined, what treatment and works follow and when someone checks back. Tenants who know the process chase less and trust more.
Escalate rather than schedule
A report involving a vulnerable household member, or describing significant spread, needs a person the same day and not a slot in a repairs diary.
Routine repairs continue alongside
They are covered in repair request and tenancy questions for housing associations.
Serious reports need the same care elsewhere
The approach matches antisocial behaviour reports and what tenants need to know, and internal visibility is covered in how to report chatbot results to your boss.
Getting started
Publish your inspection timescale and process, capture extent, photographs and vulnerability at any hour, and send anything urgent straight to a person. SpideyChat for property managers answers from your published pages and never assesses a report. Try SpideyChat on your own site, or read about capture on the features page.