Twenty-five years in NHS data, and I never once treated a patient. Every piece of work sat one step removed, sometimes several, a workflow redesign here, a records process there, a piece of reporting somewhere else. The purpose of each one stayed the same throughout. Someone's care got better because the system behind it did, whether or not I ever met them. A lot of my contemporaries felt the same way about their roles.
The same instinct, moved into housing
When housing became the work, the same instinct carried straight across. A tenant's outcome should not depend on how well they can operate the system sitting around a complaint or a repair, any more than a patient's outcome should depend on how well they can navigate a hospital corridor.
Two versions of the same gap, in my own family
My daughter's shower leaked for weeks. It wasn't the tap or the seal that caused the problem; it was understanding the system. She didn't know who to contact, what to say or when to follow up after her initial message went unanswered. However, once she understood the process, the repair was fixed within a fortnight.
A version of the same gap, at far higher stakes, ran through what happened to my mother the year my father passed away. Dementia meant she was unable to raise, or even open, a Section 21 eviction notice served against her. By the time the family understood what had happened, the deadline was almost up, and we had to scramble to negotiate an extension. Nobody had written down what she understood, or when, at any stage most of us would find hard enough with a clear head.
What TenantSafe is for
TenantSafe carries the same instinct as every system I built inside the NHS. It does not put the repair right or replace a tenant's agency. It gives a resident, or a family member acting for someone unable to manage it themselves, a place to log what happened as it happens, dated as it goes, so their account stands on the same footing as the landlord's. Nobody needs intimate, under the bonnet knowledge of the system for the problem to be resolved.
Where ScoreView came from
ScoreView came from a different conversation, repeated so often it stopped feeling like coincidence. Ask a Director of Operations, a Chief Executive, or a Chair what stands between their organisation and better performance, and the answer is rarely ambition. It is data. Every one of these conversations eventually reaches the same admission: the records behind their compliance, their repairs, their satisfaction measures are not good enough to defend in a board paper, let alone a regulatory inspection.
Why a data problem is a tenant's problem
The connection between fixing a data problem and a tenant's actual day feels indirect, and I will not pretend otherwise. But it runs on the same logic as every NHS system I ever built. Nobody's care improved because I touched it directly. It improved because the system behind the person who did was better than it had been before. A housing provider with a clean, trustworthy record of its stock and its residents makes better decisions about both, and those decisions land, eventually, on a tenant's actual life. A repair scheduled before it becomes a hazard. A risk caught before Awaab's Law required it. A complaint resolved at stage one instead of dragging on to the Ombudsman.
The question worth asking
Every system I have built has sat between me and the person it was meant to help. The question worth asking of any system in your organisation is the one I ask of mine. If the resident, or the patient, never meets the person who built it, do they still feel the difference it makes?