Supported housing is not short of software. It is short of infrastructure.

Councils run their commissioning on spreadsheets and case management systems built for general social care. Care providers manage referrals through inboxes. Housing associations track void properties in one system and compliance in another. Developers and investors assess opportunities using generic property data that was never built with supported housing in mind. Every organisation in the chain has its own tool, and none of those tools talk to each other.

This matters more in supported housing than in most sectors, because the number of parties involved in getting one person into one home is unusually high. Guidance from the Local Government Association on specialised supported housing sets out who typically has to be involved: local authority and NHS commissioners, housing associations or registered providers, separate care and support providers, private investors or developers funding the property through lease arrangements, housing benefit teams assessing rent reasonableness, and the Regulator of Social Housing overseeing standards. That is six or seven distinct organisation types, often with six or seven distinct systems, before a single tenancy has started.

Government's own auditors have made a similar point about the sector as a whole, not just individual placements. The National Audit Office found that at least three central departments, the Department for Work and Pensions, the housing department (formerly DLUHC), and the Department of Health and Social Care, hold overlapping responsibility for supported housing, alongside the Department for Education for care leavers, with local authorities implementing policy on the ground. The same investigation noted something that should concern anyone trying to plan capacity or investment in the sector: there are no good data on the number of supported housing units or the number of people living in them. The last comprehensive estimate, from a 2016 review, put the figure at roughly 651,000 supported homes in Great Britain, with government spending around £3.5 billion a year on the accommodation element through Housing Benefit in England alone. Those numbers are now close to a decade old.

What fragmentation actually costs

None of this is abstract. When a commissioning team, a care provider and a landlord each hold their own version of the truth about a placement, the practical effect is a property sitting void for longer while paperwork is chased between organisations, a needs assessment repeated because the last one lives in a system nobody else can see, and a referral that stalls not because no suitable place exists, but because nobody currently has visibility of all the pieces at once.

Parliament's response to the wider problem was the Supported Housing (Regulatory Oversight) Act 2023, which received Royal Assent after cross-party concern about a "growing minority of rogue landlords" exploiting weak oversight to draw down higher exempt-accommodation Housing Benefit rates while providing minimal support. The Act introduces local licensing, National Supported Housing Standards, and a duty on local authorities to develop supported housing strategies. It is a regulatory fix for a structural problem: poor oversight was possible partly because no one body held a complete, current picture of who was operating, where, and to what standard. A licensing regime helps, but it still depends on local authorities collecting and cross-referencing information that, in most areas, currently sits in disconnected systems held by disconnected organisations. Councils have reported lacking the resources to properly investigate providers in their area, a capacity problem fragmented data makes worse, since every check has to be built manually rather than pulled from a shared source.

Why generic tools don't fit this sector

A general-purpose CRM was built to manage sales pipelines. A generic property portal was built to list units for rent or sale. The actual unit of work in supported housing is a relationship between a person's care needs, a specific property's suitability, a funding route, and a regulatory status, all of which change over time and all of which multiple organisations need visibility of at once, which is not what either kind of tool was designed for.

Bolting a supported housing workflow onto a tool designed for something else tends to produce exactly the pattern the LGA guidance describes: commissioners struggling to see whether rents are reasonable because the financial detail sits with a lease-based investor relationship they cannot inspect directly, and out-of-area placements complicating accountability because the receiving council has no live view of a placement made elsewhere. These are not failures of individual staff. They are failures of infrastructure.

What shared infrastructure requires, and what it doesn't excuse

Other sectors facing similar coordination problems have moved from disconnected tools to shared infrastructure. In the NHS, the long-standing difficulty of a patient's record sitting in different systems across GP practices, hospitals and social care has driven a sustained national programme to build shared care records across integrated care systems, so that authorised professionals see one current picture instead of reconciling several. The comparison only goes so far, though: NHS shared care records is a nationally mandated, government-funded programme with a unique patient identifier and no requirement to persuade participants to join, whereas any platform serving supported housing is asking commercially separate, sometimes competing organisations to opt in voluntarily, with no equivalent statutory mandate behind it. That's a harder problem to solve than infrastructure alone.

It's also not simply a software problem. Tenant care needs are special category data under UK GDPR, and a shared system spanning statutory commissioners, competing care providers, competing housing associations and private investors has to grapple with who has a lawful basis to see what: an investor's legitimate interest is financial (rent, occupancy, lease terms), not the individual care and safeguarding detail a commissioner or care provider needs, and two organisations bidding for the same contract have no business seeing each other's referral pipeline. Shared infrastructure has to be built around those boundaries from the outset, not bolted on afterwards.

This is the argument for treating supported housing as needing its own infrastructure rather than another point solution, built with those constraints in mind rather than around them. OTHRS is being built on that premise, as a platform designed to connect commissioners, care providers, housing associations, developers and investors around shared data, each with access appropriate to their role, rather than as a CRM with a supported housing skin. The sector already has the regulatory push, through the 2023 Act and the National Supported Housing Standards, towards more accountable, better-evidenced decision-making. What it has lacked is the underlying system that makes that easy to do by default rather than heroic to do by exception.

FAQ

Why does supported housing need infrastructure rather than another app?

Because the LGA's own commissioning guidance shows that a single scheme routinely involves commissioners, housing providers, separate care providers, investors, housing benefit teams and a regulator, all needing visibility of overlapping information. A single-purpose app serves one of those parties well and leaves the rest working from stale exports and phone calls.

Is fragmentation in supported housing a documented problem, or just a common complaint?

It is documented. The National Audit Office found overlapping responsibility across at least three central government departments plus local authorities, and stated there are no good data on the number of supported housing units or residents in England, a decade-old evidence base for an estimated £3.5 billion annual spend.

How does the Supported Housing (Regulatory Oversight) Act 2023 relate to this?

It responds to the same underlying problem from a regulatory angle, introducing local licensing and National Supported Housing Standards so councils can refuse or remove poor providers. Licensing works best when the data behind it is current and shared, which is an infrastructure question as much as a legal one.

Doesn't sharing data across commissioners, providers and investors raise privacy concerns?

Yes, and any credible platform in this space has to design for that rather than around it. Tenant care information is special category data under UK GDPR, and different parties have different legitimate reasons to see different things: an investor's legitimate interest is financial, not clinical or safeguarding detail, and competing providers shouldn't see each other's pipeline. Role-appropriate access isn't a feature to add later; it's a precondition for the whole model working.

For every part of the sector

See how OTHRS is being built to connect commissioners, care providers, housing associations, developers and investors around shared data.

Sources