Not a link to another system, and not a note field somebody has to think to open.
What it does
Household, income, life events and recorded access needs read together with your 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.
Where a resident carries a recorded communication requirement, the email will not go until somebody confirms they have read it — and the confirmation stores a snapshot of what they read, with an optional note on what is being done differently.
It stops counting if the needs change afterwards, and says which of the two reasons applies.
Post only. Braille. Large print. An interpreter. A named advocate to contact instead. A panel that lists two of five needs is worse than no panel, because it reads as the whole record.
Needs an email cannot meet are flagged as the wrong channel; needs it can meet appear as guidance.
The equality impact assessment and every reasonable adjustment offered are held dated and attributed, and the database grants no DELETE on either — so a record that later becomes inconvenient cannot be quietly removed.
Where this stops
A need held in an officer's memory cannot stop a send. The product enforces your record; it does not improve it.
The confirmation records that somebody read the needs. Nothing checks the letter, so it cannot tell you the notice went out in large print.
An officer pressing send is stopped; the overnight templated run is not. That run has no officer in the loop, which makes it the higher-risk path of the two. It is not built, and we would rather you read it here.
Tell us about your organisation and what you are trying to fix. It goes straight to the team, and a person replies.