A knock at the door that went wrong
A contractor arrives at a home for a boiler repair. The tenant is deaf and did not hear the knock, so the job is marked no access. At another home, the operative arrives unannounced at a household with a serious mental health condition who is frightened by unexpected visitors. At a third, a tenant with dementia agrees to work that their family had asked to be told about first.
Your housing officers knew about all three. The information was in their notes, not in the job the contractor received.
Why the information does not reach the door
Vulnerability information is sensitive, so organisations are rightly careful. The safe answer is often to send nothing. But contractors need practical instructions, not full details, and nothing translates one into the other.
- Vulnerability is recorded in free-text notes, not structured flags.
- Records are out of date, with needs recorded years ago.
- Repairs jobs are raised without any flag, or with one generic warning.
- Contractors' systems cannot receive or display sensitive fields safely.
- Operatives do not know what to do differently even when a flag exists.
What it costs when it goes wrong
At worst, distress or harm to a tenant who needed a different approach. Short of that, no-access visits, complaints, and repairs left undone for households who most need them. A generic warning on every job is ignored, which is almost as bad as none. And staff worry about getting data sharing wrong in either direction.
Out-of-date records are their own problem. A flag recorded years ago for a tenant whose circumstances have since changed can lead to a clumsy visit, while a new need recorded last week by a support worker may not be in the system at all. Without review dates, nobody knows which flags to trust.
The need-to-know alerts we build
- Your vulnerability records are organised into structured needs, such as hearing impairment, mobility, mental health, language, or a person to contact first, with a review date on each.
- Each need is linked to practical instructions for visitors, for example call before arrival, text rather than phone, allow extra time, contact the named person, or two operatives required.
- When a repair job is raised in your repairs system, the instructions for that household are attached to the job. The underlying details are not.
- Contractors receive the instructions with the job through their own system where it can take them, or through a secure job link.
- Needs that are due for review are listed for housing officers, so records stay current.
- Access to full vulnerability details stays with your own staff, by role, with every view logged.
| Recorded need | Instruction the contractor sees |
|---|---|
| Deaf tenant | Text before arrival, do not rely on the doorbell |
| Anxiety about visitors | Call the day before and on arrival |
| Named family contact | Contact named person before any work is agreed |
| Mobility needs | Allow extra time to answer the door |
| Interpreter needed | Language noted, arrange through the office |
What you record, what you share and on what basis are decisions for your data protection lead and advisers. We build the translation from records to instructions to match your policy.
What operatives and tenants experience
Operatives arrive knowing what to do differently, in plain words. Tenants with needs are treated in a way that suits them, and fewer visits fail. Housing officers know their records are being used, which gives a reason to keep them current. And your data protection position is clear: contractors receive instructions, not personal details.
Does this happen in your organisation?
- Contractors arrive unaware of a household's needs.
- Vulnerability is recorded in free-text notes.
- Jobs carry either no warning or a generic one.
- You are unsure what can safely be shared with contractors.
- Vulnerability records are rarely reviewed.