Run the home
One staff file per person, built as the job moves.
A children's home's staff files are the first thing an inspector asks for and the last thing anyone has time to maintain. Careframe builds each file from your own forms and checklists as the person moves from applicant to interview to induction to probation to supervision — so the file is current because the work happened, not because somebody remembered to file it.
See Run the home on the homepageSet the forms once. Every file is built from them.
You decide what a staff file at your home has to contain: which checks, which forms, which evidence, at which stage. Careframe turns that into a checklist and generates it for every new person, so there is no blank file waiting for someone to remember what goes in it.
The form builder is the same one that runs the rest of the file. You build the form, choose where it belongs in the lifecycle, and Careframe creates it, sends it, chases it and files the answer against the right person.
Template packs per stage
Separate packs for interview and for onboarding, so an applicant is not sent an induction form and a new starter is not re-sent an interview one.
Forms people outside the app can fill
A candidate or a referee gets a link and fills the form without an account. The answer lands in the file, not in an inbox.
Evidence three ways
Upload a document, link one that is already in the file, or record an external check that lives somewhere else — each satisfies the checklist item it belongs to.
Chasing, from inside the file
Send the outstanding item to the person who owes it, with the wording you set, and see what is still out.
Checks and expiries, named the way your nation names them.
The background check on a staff file is a DBS in England and Wales, a PVG in Scotland and an AccessNI check in Northern Ireland. Careframe uses your nation's name for it, because you picked your regulator when you set the home up.
Anything with an end date — a check, a right-to-work document, a training certificate — is held with that date, and an expiring one shows up in the home's compliance picture and on the Inspection ready page before it lapses rather than after.
Who may see whose file.
A staff file holds some of the most sensitive material in the home. Access is decided per person, per home and per module on a permissions grid, and the boundary is enforced in the database itself, not only in the screens. Confidential material inside a file carries its own marker and its own step before it opens.
What this does not do
- Careframe does not run the DBS, PVG or AccessNI check for you and is not an umbrella body. It records the check, its number and its date, and tells you when it is due again.
- It does not decide whether someone is safe to employ. It shows you what is missing and who has signed off what.
- Training delivery is not built. A training certificate is held on the file with its expiry; the course library and training matrix are on the roadmap and are not available today.
Read next
See it on your own home's shape.
A short demo, with a straight answer about what is built and what is not.