Why I started asking questions about software
I came into this article with a perspective that most software guides do not have: I used to work in a residential family centre, and the tools we relied on were a constant source of frustration.
The work itself was rewarding. But the administration around it was fragmented in a way that made everything harder than it needed to be. We had one system for tasks, a separate one for parenting assessment documentation, and then a mix of Microsoft Teams, Word documents and paper files holding everything else together. Nothing talked to anything else. Information lived in multiple places, and keeping it all current was a job in itself.
The moment that crystallised it for me was a software update to our task management system. It arrived unannounced and was, to put it maybe a little dramatically, visually catastrophic. A colleague and I laughed about it, but underneath the humour was a genuine frustration. I raised it with my manager and realised the uncomfortable truth: there simply was not a better option. Centres like ours were bending general tools to meet highly specific needs, and the tools were not designed to bend that way.
That is why I left to build FamilyAxis. I want to be transparent about that upfront. This article is published on our company blog, so it would be dishonest to pretend otherwise. But the questions I will work through here are ones I genuinely asked before building anything, and they are the right questions for any centre manager to ask.
What makes this setting different
Residential family assessment centres carry out some of the most consequential work in the social care system. The assessments produced here directly inform court decisions about whether children remain with their families. The documentation must be accurate, complete, evidenced to court standard, and maintained under Regulation 19 of the Residential Family Centres Regulations 2002, which requires providers to keep a comprehensive record for each family.
At the same time, centres operate in a high-pressure environment where staff are stretched. A mixed methods study by the British Association of Social Workers found that social workers spend an average of 29 hours per week on computers or completing paperwork, out of a 45-hour working week, leaving just 11 hours for direct contact with children and families. While this research covers the broader sector, the pattern is familiar to anyone who has worked in a residential family setting.
Staff turnover adds another layer of complexity. According to the Department for Education's Children's Social Work Workforce statistics, there were 4,300 child and family social worker leavers in the year to September 2025, with around one in three social workers having less than two years' service at their current organisation. Centres regularly onboard new staff who need to get up to speed quickly on both the work and the systems that support it. Software that is hard to learn or poorly designed does not just frustrate experienced staff, it actively slows down new starters at exactly the moment they need to be effective.
What to look for
Purpose-built versus adapted
The most important question to ask any software provider is whether their software was designed for residential family assessment, or adapted from something built for a different setting. In my experience, the difference is significant. Adapted systems require workarounds that become embedded in daily practice. They use terminology from other contexts. They organise information in ways that do not map to how assessment work actually flows. Purpose-built tools embed the right frameworks from the start, which means staff spend less time navigating the system and more time doing the work.
Observation and direct work logging
The foundation of any residential family assessment is the ongoing recording of parenting. Software should make it quick and easy for staff at every level to log observations with appropriate structure and detail. If logging takes more than a few minutes, staff will defer it. Deferred documentation is incomplete documentation, and in a court-evidenced setting, that matters enormously.
Safeguarding workflows
Safeguarding concerns can emerge at any point during a placement. Software must support immediate escalation: concerns should be logged, flagged to the relevant manager, and visible to the whole team without delay. Automatic notifications, active risk logs and audit trails are not optional. Ofsted has identified failures in settings where significant incidents were not notified promptly, and the absence of clear oversight processes is in itself a concern during inspection.
Report generation
Producing court-ready reports is one of the most time-consuming parts of assessment work. Software that pulls together observations, direct work records and commentary into a structured, professionally formatted document saves significant time and reduces the risk of gaps. Look for customisable templates that meet court formatting requirements without requiring staff to rebuild documents from scratch each time.
Collaboration and real-time access
One of the most underappreciated problems in centre software is what happens when more than one person tries to update a record at the same time. In my previous role, we lost work regularly because two staff members were editing the same document simultaneously. Proper collaboration tools, where changes are synced and conflicts prevented, are not a luxury. They are a basic requirement for a team working across shifts.
The child's voice
Standard 2 of the National Minimum Standards for Residential Family Centres requires centres to listen to and take into account the wishes and feelings of children. This should be reflected in the software. There should be a dedicated space for recording the child's individual experience, kept separate from the parenting assessment, so that it is never deprioritised when time is short.
Staff experience and motivation
This one is less obvious but genuinely matters. Centres deal with high staff turnover and emotionally demanding work. Software that is ugly, slow or frustrating adds to the cumulative weight of the job. When we built FamilyAxis, we made a deliberate decision to invest in design, clean interfaces, progress animations, elements of gamification. It might sound trivial compared to compliance requirements, but the effect on team morale is real. Software that people actually enjoy using gets used consistently, and consistent use is what produces reliable records.
Onboarding and support
Because turnover is high and centres are time-poor, onboarding support cannot be a PDF booklet. At minimum, look for a vendor who provides a comprehensive help centre, training videos, and a recorded version of their demo that new staff can access in their own time. The standard for onboarding has shifted considerably in recent years, and a company still relying on static documentation is not keeping pace.
A note on newer versus established software
There is a tendency in procurement to favour established software providers on the basis that longevity signals reliability. That instinct is understandable, but it is worth examining carefully when it comes to software.
Older systems carry what developers call technical debt: the accumulated cost of past design decisions that makes them progressively harder to update. As software ages, adding new features or responding to user feedback becomes more complex and more expensive. Systems built on older code often cannot integrate cleanly with modern tools, and updates that should take days can take months.
Newer companies, by contrast, are building on modern foundations. They can respond to customer feedback more quickly, ship updates more frequently, and integrate with other tools more easily. The question to ask is not just how long a vendor has been around, but how actively they are developing their product and how responsive they are to the specific needs of their users.
Questions to ask any software provider
Before committing to a product, work through the following:
- Was this software built specifically for residential family assessment work, or adapted from another setting?
- Can it support the full assessment cycle, from initial observations through to court report generation?
- How does it handle safeguarding escalation and audit trails?
- Is there a dedicated space for recording the child's experience?
- How does the system handle simultaneous editing by multiple staff members?
- Where is data hosted, how is it encrypted, and what happens to our data if we end our contract?
- How frequently is the product updated, and how do you gather feedback from users?
- What does onboarding look like for new staff, and is there a help centre or recorded training available?
Final Thoughts
Choosing the right software is not just an operational decision, it is a strategic one. The right tool reduces administrative burden, supports consistent documentation, and frees your team to focus on what they came into this work to do. Taking the time to ask the right questions before committing to a product is always time well spent.
References
- British Association of Social Workers. (2018). 80-20 Campaign Final Report. Retrieved from https://basw.co.uk/sites/default/files/2023-08/FINAL%2080-20%20report.pdf
- Department for Education. (2025). Children's social work workforce 2025. Retrieved from https://explore-education-statistics.service.gov.uk/find-statistics/children-s-social-work-workforce/2025
- Department for Education. (2013). Residential Family Centres National Minimum Standards. Retrieved from https://assets.publishing.service.gov.uk/media/5a7574c7ed915d731495a184/2013_Residential_Family_Centres_NMS.pdf
- The Residential Family Centres Regulations 2002, Regulation 19. Retrieved from https://www.legislation.gov.uk/uksi/2002/3213/regulation/19
- IBM. (2025). What is technical debt? Retrieved from https://www.ibm.com/think/topics/technical-debt
