Recorded access needs are not a note somebody might read. They stop the send, in front of the officer, before the message is written — and the confirmation records what was read.
Rent is the lifeblood of the organisation, and arrears is where most residents meet it at its least flexible moment. It is also the process that generates the complaints, the Ombudsman findings and the perception scores.
Which makes collection a customer-experience function whether or not it reports to you. A team that knows nothing about a tenant cannot treat them fairly — and it will not be the team that gets named.
Before the message is written
Not a link to another system, and not a note field somebody has to think to open. The household, the income picture and the recorded access needs are on the case, read together with your policy and the ledger.
Equality Act 2010 s.20 · Pre-Action Protocol
Where a resident carries a recorded communication requirement, the email will not go until somebody confirms they have read it — and the confirmation stores what they read, with an optional note on what is being done differently.
It stops counting if the needs change, so a confirmation made two years ago against a different record does not stand in for one made today.
Post only. Braille. Large print. An interpreter. A named advocate who should be contacted instead. These are not useful in a report at the end of the quarter — they are useful at the moment somebody is about to write to a person who cannot read it.
Every requirement on file is shown, not a subset. A panel that lists two of five needs is worse than no panel, because it reads as the whole record.
Household, income, life events and access needs read together with company policy, the regulation and the ledger, into a contextual answer about what to do next — that an officer can ask questions of.
It does not contact residents, and it does not choose who gets chased. A person presses send, on a draft they can rewrite.
Along with Breathing Space, a mental-health crisis moratorium, a Debt Relief Order and bankruptcy. Not a flag an officer is expected to notice — the account leaves the worklist, at the queue itself.
Chasing somebody for rent while they are inside a complaint about the same tenancy is how a service failure becomes a finding.
A case whose cause has gone away closes itself and says so. The tenant paid, the claim landed, the arrangement started — and nobody writes to them about arrears they have already cleared.
The cheapest complaint to handle is the one caused by a letter that was never sent.
When it goes wrong anyway
Where this stops
The honest boundaries, because the ones that get discovered in a complaint investigation are expensive.
A communication need nobody captured cannot stop a send, and a vulnerability held only in an officer’s memory is not on the case. The product enforces your record; it does not improve it.
No autonomous outbound, no chatbot on the tenant side. A person presses send on every message. That is a deliberate limit, and it means this reduces bad contact rather than contact volume.
Tenant perception is a survey, not a system output. This changes what happens before a contact; whether that shows up in a TSM perception measure is a question your survey answers, not this.
The rest of the committee
Written separately because these are genuinely different questions, not the same pitch with the job title swapped.
One patch, one team, your own data loaded. Tell us your account volumes and which housing management system you run, and we will put a number to it.
Tell us about your organisation and what you are trying to fix. It goes straight to the team, and a person replies.