Change a policy, approve it properly, prove it happened

When CareStream suggests a fix to close a gap in one of your policies and you accept it, the platform does not rewrite the document behind your back. It applies the suggested wording as tracked changes, highlighting every insertion and alteration against your existing text. This works exactly like the tracked changes you know from editing a document. You can see the before and after in context, understand precisely what the fix does, and confirm it only when you are satisfied. The change becomes part of the live policy only after that point.

No. That is the whole purpose of showing accepted fixes as tracked changes rather than silent edits. Nothing is merged into the live version of a policy until you have reviewed the marked-up change and confirmed it. This keeps policy owners firmly in control of policies and procedures in health and social care. Because a change to something like a safeguarding or medication policy carries real weight, CareStream makes sure you understand every inserted or altered word before it takes effect.

Yes. Seeing a fix as tracked changes means you can treat it as a starting point rather than a fixed instruction. If the suggested wording is close but not quite right for your service, you can refine it so it fits your home precisely before it becomes live. This matters because every service has its own context, and a good policy reflects how your care is genuinely delivered. Tracked changes give you the room to shape the improvement, keeping the speed of an AI suggestion while preserving your authorship of the final text.

Tracked changes are about visibility of the change itself: what an accepted gap fix inserts or alters, shown clearly in context within the policy. It answers the question of what is changing. The review and approval step is about who signs the change off before it goes live. The two work together, so you first see exactly what the tracked change does, and then it moves through the controlled adoption path where a responsible person approves it as the current, live policy.

No. This is the core of the controlled adoption path. A suggested change is held as pending and cannot affect the live policy until a responsible person has reviewed it and approved it. That deliberate stop is what keeps your policies and procedures in health and social care trustworthy. Because nothing reaches your staff without sign-off, you can always be sure that the version they are working to has passed through a proper checkpoint.

The responsible person is whoever your service has designated to sign off policy changes, typically a registered manager, nominated individual or quality lead. They examine the proposed change, understand its impact and decide whether it should be adopted. By attaching a named, accountable person to every approval, CareStream ensures each change carries a clear moment of ownership. This is exactly the kind of governance inspectors expect to see behind your care home policies and nursing home policies.

The two features work hand in hand but answer different questions. Tracked changes show you what is changing, highlighting every insertion or alteration in context so the reviewer understands the proposed update clearly. Review and approval then govern whether that change goes live and who signs it off. So a reviewer first sees the marked-up change, and then the controlled adoption path requires a responsible person to approve it before it becomes the current policy.

Inspectors look not just at what your policies say but at how they are governed. A change that appeared without oversight suggests weak control, whereas a change that was reviewed and signed off demonstrates that your service manages its policies and procedures deliberately. By making review and approval the required route for every update, CareStream gives you a clear, defensible story: no policy change reached your staff without a responsible person reviewing and approving it first. That is strong evidence of sound governance and inspection readiness.

The feature is built around the responsible roles that care policies actually reference, such as the registered manager, nominated individual and named leads like the infection prevention lead, alongside the other role holders your documents depend on. Wherever a policy points to a person by their role, that is where a real name can be merged in. The aim is to make sure every duty that names a role also shows the real person who holds it. That turns a document full of generic labels into one where accountability is visible and specific, which is exactly what an inspector is looking for when they ask who is responsible for something.

Because names are linked to the role rather than typed into each document, you update the role holder once and every affected policy reflects the new person automatically. There is no need to open dozens of files and find and replace an old name, and no risk of one being missed in a document you forgot about. This is the part that saves the most work and prevents the most embarrassment. Staff changes are frequent in care, and manually keeping names correct across a whole library is exactly the sort of task that slips. Tying the name to the role means your documents simply stay current as your team changes.

Filling placeholders by hand fixes a document once, at that moment. The instant a role holder changes, the name you typed is wrong again, and you are back to editing files one by one. It also does nothing to stop the same blank reappearing in a new policy you add later. Merging role-holder names is a living link between your people and your documents. The names are always the current ones because they flow from the role, so the policies stay right as your team evolves. It replaces a repeated manual chore with something that maintains itself, which is why the names actually stay accurate over time rather than drifting out of date.

Yes, in a direct and practical way. Inspectors routinely want to know who is responsible for a given area, and a policy that names a real, current person answers that immediately. A policy that leaves the responsible person blank, or still shows a generic label, invites the opposite impression: that the document was never truly adopted. By ensuring your registered manager, nominated individual and named leads appear by name where they are accountable, the feature turns your policies into clear evidence of ownership. It is a small detail that quietly reinforces the message that your service knows who does what and keeps its documents alive.

No. Versioning is fully automatic. Every time a policy is edited or an approved change is made, CareStream captures that as a new version and keeps the previous one intact, so there is nothing for you to save, rename or file manually. This is a deliberate move away from the fragile habit of renaming files on a shared drive. Because the platform handles it every time, your version history is always complete, and you never have to worry that a change slipped through without a record.

Yes. You can open any two versions of a policy and compare them, so you can see exactly what was added, removed or reworded rather than just knowing that something changed. This makes it easy to review the impact of an update or to explain a change to a colleague or inspector. Each version also carries the date it was created and the person who made the change, so alongside seeing what moved, you can see who was responsible and when. Together that gives you the full picture behind any policy revision.

Because previous versions are preserved rather than overwritten, you can restore an earlier version and make it the live policy again whenever a change needs to be rolled back. Nothing is ever truly lost, so a mistaken or premature edit is easy to undo. The restore is itself captured in the history, so the record stays honest. You can see that a previous version was brought back, when and by whom, which keeps your policy trail transparent even when you have had to reverse a decision.

Inspectors often want to understand not just what a policy says now but how it has evolved, when it was last reviewed and who signed changes off. Automatic versioning gives you a clear, dated history for every policy, so you can answer those questions immediately instead of searching through drives or emails. This strengthens your governance evidence considerably. Being able to show a continuous, attributed history behind your policies and procedures in health and social care demonstrates that your document control is deliberate and well managed, which is exactly the kind of assurance inspection looks for.

For every change to a policy, CareStream stores a distinct version along with the approval attached to it, so you can see who approved that version and precisely when. Every previous version is retained too, giving each policy a complete and unbroken lineage. This turns your care home policies and nursing home policies into traceable records rather than single current files. Whether you need to answer an inspector, investigate a complaint or simply understand how a policy evolved, the full history is there to show exactly what happened and when.

Yes. Because the full version history is retained and nothing is overwritten, you can restore an earlier approved version if a change needs undoing. You do not have to reconstruct the old wording by hand or hunt for a copy, because it is already stored. This is a real safeguard for governance. If a change turns out to have been a mistake or no longer fits your service, rolling back is fast and clean, and the rollback itself becomes part of the traceable history of the policy.

Yes. Admin approval is the point at which a change takes effect, so every version that goes live has been signed off by an administrator. That approval, including who gave it and when, is recorded against the version. This matters because governance depends on accountability. By requiring admin sign-off for each change, CareStream ensures there is always a named person and a moment behind every version of your policies and procedures in health and social care, which is exactly what strong control looks like.

Inspectors want to see that your policies are controlled, not just present. Being able to show who approved each version and when, and to produce any earlier wording on request, is powerful evidence that your service governs its policies deliberately and carefully. A full version history also lets you demonstrate exactly what changed and why over time. Rather than presenting a single current document with no memory, you present a traceable lineage, which strengthens your inspection readiness and your wider approach to quality care.

No, it is entirely optional. You decide whether your service requires a care manager to sign off a policy change before it is adopted. Services that want that extra layer can enable it, and those that prefer a simpler route can leave it off. This flexibility exists because governance should fit the service. A larger provider may want a care manager to review changes as an added safeguard, while a smaller team may find a single approval sufficient, and CareStream supports both without forcing one model on everyone.

Turning it on adds a second pair of eyes to the adoption of any policy change. For services that manage many policies, operate across multiple sites, or simply want extra assurance on sensitive documents, that additional review can be valuable. With the step enabled, a care manager reviews and approves each change before it can move forward, which strengthens oversight without abandoning the controlled adoption path. It is a way to build more governance into the process precisely where a service feels it is warranted.

Yes, and many will. A small team often has a single responsible person who is entirely sufficient to approve policy changes, and adding a second required step would only introduce delay without adding real control. By leaving the care manager approval step off, those teams keep a leaner route where changes follow the standard approval path. The controlled adoption path still applies, so nothing goes live without sign-off, but the process stays proportionate to the size and structure of the service.

Yes. The care manager approval step is a setting you can adjust as your service evolves. A home that starts small and later becomes part of a group, or one that decides it wants more oversight on its policies, can enable the step when the time is right. Changing the setting does not disrupt your existing policies or their version history. It simply adjusts the adoption path that future changes follow, so your governance can grow and adapt alongside your service.

It is a dedicated view built for care managers to review pending policy changes, see exactly what changed in each one, and approve them, all in one place. Instead of tracking changes across separate documents or messages, everything awaiting a decision is gathered together. The hub exists to make responsible approval straightforward. Because you can clearly see what a change alters before you sign it off, approving your care home policies and nursing home policies becomes a confident decision rather than a chore, and nothing waiting for approval slips through the cracks.

When you open a pending change in the hub, a clear view shows you exactly what was altered in that policy. You are not left to compare documents yourself or guess at the difference, because the change is presented plainly for you to review. This is central to the hub's purpose. Approval only carries weight if the person giving it understands the change, so the see what changed view ensures every care manager can sign off knowing precisely what they are approving before it becomes the live policy.

No. The hub is designed so that review and approval happen together in the same place. You see what is pending, open a change to see what was altered, and approve it directly, all without switching between tools or documents. This matters for a busy care manager. Keeping everything in one smooth flow means you can work through pending changes quickly and confidently, moving from one to the next without losing your place or your understanding of what each one involves.

The hub gives you a clear, single place where policy changes are reviewed and signed off by a care manager, with a clear view of what changed in each one. That is exactly the kind of controlled, evidenced process inspectors look for behind your policies and procedures in health and social care. Because every approval follows a review of what actually changed, you can show that sign-off was meaningful rather than a formality. Combined with the wider approval trail and version history, the hub helps you demonstrate that your service governs its policies deliberately and carefully.

No. The whole point of this feature is that trustees, directors and external consultants can review and sign off a policy without ever creating a login. You send them a one-off secure link, they open it, read the policy and record their decision, and that is the entire process for them. This removes the friction that usually delays external sign-off. There is no password to set, no onboarding to complete and nothing for you to administer on their behalf, so occasional reviewers can act quickly whenever a policy needs their approval.

No. The secure link opens only the exact policy and version you chose to send. The reviewer cannot browse your other policies, your staff records, your training data or anything else inside CareStream, because the link is scoped to that single document. This keeps your data protected while still giving the reviewer everything they need to make an informed decision. They see the full policy in context, sign it off or return feedback, and never gain access to anything beyond it.

Yes. When an external reviewer signs off through the link, their approval is written into the same audit trail as your internal approval steps, with their name and the date. So the record shows clearly who reviewed the policy, which version they saw and when they approved it. This means external oversight carries the same evidential weight as internal sign-off. At inspection you can demonstrate that policies requiring board, trustee or consultant approval genuinely received it, with a clean, dated trail behind every one.

Each link is single use and tied to one specific policy version. Once the reviewer has acted on it, the link expires, so it cannot be reopened, and because it is bound to a particular version it will never surface a different or later document. If you need the same person to review a revised version later, you simply send a fresh link for that version. This keeps every approval unambiguous, because there is never any doubt about which version of a policy a reviewer actually signed off.

Two things happen automatically and together. The approval is written into an audit trail, capturing that the change was signed off so you can evidence it later, and the updated policy is re-published to the staff Q&A assistant. Because both steps are automatic, there is no lag between sign-off and distribution. The assistant immediately begins answering staff questions from the latest approved version, so your records and your frontline practice stay perfectly in step.

No. That is the whole point of automatic re-publishing. Once a change is approved, the updated policy is pushed to the staff Q&A assistant on its own, without anyone having to remember to circulate it or update a shared copy. This closes a gap that catches many services out, where a policy is approved but staff carry on acting on the old version because no one distributed the new one. With CareStream, approval and distribution are a single event, so the latest approved wording reaches your team straight away.

Staff use the Q&A assistant to ask questions, and once a change is approved the assistant answers from the newest approved version of the policy. The previous wording no longer drives answers, so staff cannot act on a superseded version by mistake. This means your team always receives guidance that reflects your current, approved care home policies and nursing home policies. There is no window in which a policy has been updated on paper but not yet in the answers your staff are relying on day to day.

The audit trail records that each policy change was approved, so you can show that sign-off genuinely happened and by whom. Combined with the automatic re-publish, it also lets you demonstrate that staff were answering from the latest approved version from that point on. For CQC and your own governance, this is strong evidence. You can produce a clear record that a change was properly approved and that it reached your frontline immediately, which shows an inspector that your policies and procedures in health and social care are both controlled and genuinely embedded in practice.

Yes. When you download a policy, it is produced on your own letterhead, so the finished document clearly belongs to your service rather than looking like a generic export. This gives every printed policy a consistent, professional appearance across your whole document set. That consistency matters when policies are seen by inspectors, auditors or new staff. A branded document signals that your policies and procedures in health and social care are properly controlled and current, which reinforces the impression of a well run service.

Yes. Every print-ready download includes an authorisation and sign-off block, placed on the document ready to be signed or countersigned. So the physical copy shows clearly that the policy is authorised, without you having to add that section yourself. This is particularly useful for staff files and inspection evidence, where a visible sign-off demonstrates that the policy carries proper authorisation. It turns a plain policy into a controlled document that stands up to scrutiny.

No. The download is print-ready, which means headings, spacing and layout are all handled for you. The policy comes out formatted and ready to print, file or share, without the fiddly manual layout work that a raw text export would need. This saves real time whenever a physical or PDF copy is requested. Instead of laying out a document by hand each time, you download a finished version in moments, which keeps your evidence ready and your staff files up to date with far less effort.

Yes. The print-ready format is designed exactly for that. Because each policy comes out on your letterhead with a sign-off block and clean formatting, it is suitable for adding to staff files, placing in an inspection folder or handing directly to an auditor. Having finished, branded copies ready means you are never scrambling to produce a presentable document when it is asked for. Your policies are always available in a form that looks professional and demonstrates proper control, which supports your inspection readiness.