Who signs it off? A clear policy approval process, in the right order
A good policy approval process answers one question: who has to say yes before staff see the new wording? CareStream lets you set that order, with a care manager step and an optional external reviewer. It sits inside training built from your own policies, so the approved policy can then reach staff.
14 day free trial · Set up in a day · UK data residency
The policy is rewritten. Then nobody is sure who has to say yes.
A scenario we see in many care settings.
A registered manager rewrites the falls policy after an incident and emails the draft to the deputy. The deputy likes it and replies with a thumbs up. The owner wants the provider's external consultant to look at it too, but that email gets buried. Three weeks on, the old version is still in the shared folder and the new one is in an inbox. Staff are following whichever one they find first. Nobody can say who approved what, or in what order, and the manager has to piece it together from messages.

The manager rewrites the falls policy after an incident.
The deputy reads it and replies with a thumbs up.
The owner asks for the external consultant to see it too.
The consultant's email is buried. Nobody chases it.
The old version is still in the shared folder.
Staff use whichever version they find first.
No one can say which version was live on a given date.
"Who approved this policy, and when did staff see it?"
The policy was never the problem. The gap is the order of approval and the record of it. Here is how CareStream sets that order, keeps the history and then helps you brief staff.
An example scenario, not a named service.
A thumbs up in an email is not a policy approval process
Good policy governance means everyone knows who approves, in what order, and where the proof is.
Approval lives in inboxes
A yes by email, a comment on a printout and a verbal word in the corridor are all real decisions. None of them is easy to find later.
Two versions run side by side
Without policy version control, an old file and a new file can both look current. Staff cannot tell which one the service actually stands behind.
The external step gets lost
If a consultant or provider lead has to review a policy, the request needs a clear route in, a clear answer and a note when changes are asked for.
One policy approval process, from draft to live.
This is part of the Training built from your own policies feature. For finding what needs changing in the first place, see policy gap detection.
Set who approves policies, and in what order
- Suggested fixes and wording changes are only suggestions until an admin adopts them. Adopted text becomes tracked changes on a draft, and your uploaded original is untouched
- After the admin approves, the draft can go to a care manager step, and then to an optional external reviewer, or straight to live, depending on your settings
- The approval chain is on the Professional and Enterprise plans, and nothing changes for staff until the chain finishes
Illustration based on the Training screen. Example questions.
Brief staff once the new version is live
- Once the policy is live, allocate an adhoc training module on the topic. It is built from your own policies where they cover it, with general good practice as the fallback, and you can edit and preview it first
- Staff complete it in the Staff Hub. A wrong answer goes into their Follow-up tab and they get an email, at most once a day
- They choose Learn & retry for a short lesson and a fresh question, or Just retry the same one. Nothing alerts you on each wrong answer
A few things to revisit. Learn the point, then answer, or just retry. Either way it clears from here.
The senior on shift needs to know at once so the resident can be checked and the right people informed.
Remember- Stay with the resident and call for help
- Do not move them until checked
- Record what you saw and did
You find a resident on the floor at the start of a night shift.
Illustration based on the Staff Hub Follow-up tab. Example content.
Staff can ask about the approved policy in their own language
- Staff ask the hub assistant a question and it replies in the language they asked in, while the policy stays in English underneath
- The answer draws on your own approved policies, so it follows the version you published
- Translation is part of the paid plans
Always communicate in their first language
All messages CareStream sends are translated into English.
Allow switching a set to their second language
In the hub they can flip any single training, induction or CQC set into Polish, just for that set, if they are struggling in their first language.
Let them suggest better translations
They can propose improvements to translated content. Changes need your approval before going live.
Illustration based on the staff record Language settings. Translation is on the paid plans.
See which parts of the new policy people miss
- The Knowledge gaps view shows the most missed questions and the weakest topics after a policy briefing
- See how gaps are being closed, so a rewrite that confuses people shows up fast
- A Monday digest email brings the picture to you
Illustration based on the Knowledge gaps view. Example figures.
The questions managers ask, and how CareStream answers them
Read this as a conversation. The questions are the ones we hear most.
Who approves policies in CareStream?
You decide. An admin adopts the change as a draft. It can then go to a care manager step and, if you switch it on, to an external reviewer. If neither is switched on, it can go straight to live. The care manager step is on by default.
What does an external reviewer see?
They get a one off emailed link, with no account needed. They can approve or ask for changes, and a note is required when they ask for changes. The link runs out after 30 days, and you can revoke it or send a new one.
What if someone only fixes a typo?
Minor edits such as typos can be applied without the full chain. They are recorded as a tracked change and go straight into the published text.
Do I get a record of who approved what?
Yes. You get a version history, with each published edit saved as a read only version. Edited policies move to 2.0, 3.0 and so on. This is the policy version control most managers want when asked which version was live.
Does it write or change policies on its own?
No. Gap fixes, wording rewrites and regulation updates are suggestions. They only reach staff after an admin adopts them and the approval chain finishes. Example wording is drafted by our own machine learning, so review it carefully.
Is it a signed register of who read the policy?
No. CareStream records reading sessions, which show time spent, how far someone scrolled and whether they pressed Mark as read. It does not collect signatures.
Once the policy is live, how do staff learn it?
You allocate an adhoc training module on the topic from the Training screen. Staff complete it in the Staff Hub, and a wrong answer becomes a short lesson they open themselves. You see the picture in Knowledge gaps.
How do I try it, and what does it cost?
You can try it free for 14 days by creating a free account. The pricing page shows which plan includes the approval chain.
A clear order of approval, not a decision maker
It does not decide for you
Suggestions are guidance to review, adapt and approve for your service. It is not legal advice and cannot guarantee compliance or a CQC rating.
It does not collect signatures
You get a version history and reading sessions. There is no signed register and no policy version number recorded against each read.
The approval chain needs a higher plan
The care manager and external steps are on Professional and Enterprise. Nothing alerts you on each wrong answer in the training that follows.
Training built from your own policies
Everything on this page is part of the product. Here is where to read more.
Training built from your own policies
Policies you approve become the source for short training and staff questions.
See the featurePolicy gap detection
Find missing, out of date and conflicting policies, then adopt suggested fixes through approval.
See gap detectionPolicy changed, who needs a briefing?
Turn a policy change into short adhoc training for the staff it affects.
See the use caseGuides on this subject

Care Policy Version Control: How to Know Which Version Is Current (Without Buying New Software)
The most dangerous document in your care service is not the one that is missing. It is the one that looks current but is not. Managing policy...
Read article
Policy Changed. Who Needs Retraining? A Four-Question Framework for Care Managers
A policy update lands in your inbox at 4.45pm on a Friday. Your first instinct is to retrain everyone, because retraining everyone feels safe. It...
Read article
How Often Should Care Policies Be Reviewed? The Honest Answer for UK Care Providers
The sector baseline has settled on annual review for most core policies. That is the defensible starting point, but it is not the whole answer. The...
Read articlePolicy sign off in care services, answered
The approval order
What is a policy approval process in a care service?
It is the agreed order of steps a policy change goes through before staff rely on it. In CareStream that can be an admin, a care manager step and an optional external reviewer. See how CareStream works.
Who approves policies in a care home?
That is a decision for the provider. Many services have the registered manager, a senior or the owner involved, and some add an outside consultant. CareStream lets you set the steps to match.
Can policy sign off be skipped for small changes?
Minor edits such as typos can bypass the chain and are recorded as tracked changes. Real changes to meaning should go through the full order.
Does the external reviewer need a login?
No. They receive an emailed link that lasts 30 days. They can approve or request changes, and must add a note if they request changes.
Records and training
How do I keep policy version control without a shared folder?
Each time an edit is published, CareStream saves a read only version and the policy moves to a new major version. The old version stays in the history. Read our guide to version control.
Is approval the same as staff reading it?
No. Approval is the leadership decision. Reading is recorded separately as sessions, and training questions show whether staff understood the policy. See adhoc training.
What does good policy governance look like to an inspector?
Under Regulation 17 on good governance, systems and processes must be established and operated effectively. Clear approval, kept records and evidence staff understood the policy all support that.
Is it free to try?
Yes, you can try CareStream free for 14 days. Create a free account to see the approval chain in your own settings.
A practical way to set up policy sign off
You do not need a heavy system. You need an order that people follow and a place where the record sits.
Write down who signs what
Start with a one page note that lists each type of policy and who approves it. Clinical and safeguarding policies might need the registered manager and an external reviewer. A housekeeping procedure might need only a manager. Under Regulation 17 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014, a registered person must establish and operate systems to assess, monitor and improve the quality and safety of the services. A written order of approval is one simple part of that.
Staff also need to be ready to follow the result. Regulation 18 says staff must receive the support and training they need to carry out their duties, which is why a briefing after approval matters.
Four steps for a clean policy change
- Draft: adopt or write the change as a draft and leave the live policy alone.
- Review: send it through the care manager step and, where needed, the external reviewer.
- Publish: check the new version is live and the old one sits in the history.
- Brief: allocate a short adhoc module on the topic and look at Knowledge gaps a week later.
For the inspector. Keep the approval order, the version history and the briefing results together, so you can show how a policy became live and whether staff understood it.




