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 what happened on the night of the 14th, who was on shift and what we did about it, the answer exists, but putting it together means a senior manager spending an evening digging through four systems.
In safeguarding terms that matters. An incident that was handled and an incident that can be shown to have been handled are two different things. If the evidence takes a week to put together, the assurance is weaker, whatever happened on the night.
Building it
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 work as it is: referrals, placements, young people, properties, staffing, incidents, and the reporting that ties each 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 sits in a single record in date order. When a social worker asks what happened on the 14th, the full answer takes minutes.
Reporting that doesn't depend on memory. Our reporting commitments to each Local Authority are built into the system: how often, to whom, and a record of 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 is what makes sure that happens.
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 puts more of the burden on the provider, and record-keeping is where it lands first.
A sector that runs on spreadsheets and separate form tools will keep doing good work it cannot evidence. We built our way out of that. The platform is now available to other providers who want the same, but that is 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.