A policy is only worth the system behind it
Most care providers have the policies they need. The harder question is whether those policies are live: owned by a real person, reviewed on a schedule, and evidenced when someone asks. A safeguarding policy written in 2022 and never opened since is a document, not a safeguard. The gap between having a policy and running one is where regulatory risk lives.
We Are Care runs its own governance on Baton, the care operating software it built and gives to its partners. The aim was a policy estate that runs itself: every policy with an owner, a review date, and the evidence trail to prove it is doing its job. Three principles shape how it works.
Lived, not filed
A policy that no one reads changes nothing. Each policy is tied to the workflows it governs, so it shows up where the work happens. The safer recruitment policy runs as the checks that run before a carer reaches a shift. The medication management policy is the protocol attached to the placements that need it. Policy and practice are the same thing.
Owned, not orphaned
Every policy has a named owner and a review date held in Baton. Each policy is set using Baton's RACI roles, so the right people are responsible, accountable, consulted and kept informed. When a review falls due, the owner is prompted; nothing drifts quietly out of date. Directors sign the policies that need director sign-off, and the record of who approved what, and when, is kept at the time. If a policy changes, the version history shows what changed and why.
Tested, not assumed
Each policy is treated as a claim to be checked. Compliance and quality assurance run against the live estate, so a gap surfaces as a flag before it becomes an inspection finding. When We Are Care tells a partner their evidence is ready, it is because its own is too, run the same way through the same system.
Why this matters for partners
We Are Care does not ask partners to run their governance in a way it does not run its own. Every compliance promise made on a staffing engagement, that checks are closed before a shift, that the evidence is ready when an inspector asks, is one it holds itself to first. The policies hub is public proof that the system works on the company that built it. Each month, Baton Compliance looks ahead and surfaces the reviews coming due. It prompts; the policy owner decides. Responsibility stays with the named person.
Why it runs this way
Evidence by default
Owners, review dates and version history are captured as the work happens, not assembled the night before an inspection.
People stay accountable
Baton prompts and records; a named person reviews, decides and signs. The judgement stays human.
The same system, for everyone
We Are Care runs its governance on the software it gives partners, so every promise is already proven on itself.