Until recently, TIFA Life ran on the same patchwork most providers in this sector run on: a workforce app for rotas and team messaging, a forms tool for incident reports and daily logs, spreadsheets for everything in between, and email stitching it all together.
Each tool was fine on its own. The problem was the gaps between them. A support worker logs an incident in one system. The rota lives in another. The young person's placement record is a document in a folder. The escalation email sits in someone's inbox. When a commissioner asks a reasonable question, "what happened on the night of the 14th, who was on shift, and what did you do about it?", the answer exists, but assembling it means a senior manager spending an evening playing archaeologist across four systems.
In safeguarding terms, that's not a filing inconvenience. The quality of a provider's answer under scrutiny is the difference between an incident that was handled and an incident that can be shown to have been handled. If the evidence takes a week to assemble, the assurance is weaker, whatever actually happened on the night.
Build, not buy
We looked for software built for 16+ supported accommodation and didn't find it. Children's home systems assume a regulated residential model that doesn't match how this sector works. Generic housing systems understand properties but not young people. Workforce apps understand shifts but not placements.
So we built it. TIFA Connect is a placement management platform designed around the actual shape of this work: referrals, placements, young people, properties, staffing, incidents, and the reporting thread that ties every one of those to the Local Authority that commissioned the placement.
We built it for ourselves first. Our own teams have now moved off the old patchwork and onto Connect, and every claim in this post is something we tested by running our own placements on it.
What changes for the Local Authorities we work with
One timeline per young person. Every log entry, incident, escalation, and update in a single chronological record. When a social worker asks what happened on the 14th, the answer is minutes away, not days, and it's complete.
Reporting that doesn't depend on memory. Our reporting commitments to each Local Authority are built into the system rather than carried in someone's head. Defined cadence, named recipients, and an audit trail showing what was sent and when.
Incidents that escalate by design. An incident logged at shift level follows a defined route: it cannot quietly sit in a form queue over a weekend. The escalation path the allocated worker was given on day one is the path the system enforces.
Evidence on demand. Due diligence used to mean assembling a pack. Now it means showing a commissioner the record as it stands. We have always said that when something goes wrong, you hear about it from us quickly and in writing. The platform makes that promise structural instead of cultural.
Why this matters beyond us
16+ supported accommodation sits outside CIW registration in Wales. We've written before about what that means: the assurance commissioners rely on has to come from the provider's own governance, because no inspector is coming to check. That places a higher burden on providers in this space, not a lower one, and record-keeping is where the burden lands first.
A sector that runs on spreadsheets and disconnected form tools will keep producing the same failure: good work, badly evidenced, indefensible under scrutiny. We built our way out of that. The platform now also exists for other providers who want the same footing, but that's a conversation for another page. The point of this post is simpler: when a commissioner asks us a hard question, the answer is already written, timestamped, and one search away. That's the standard this sector should hold itself to, with or without a regulator in the room.