Guideline, Policy & SOP
Documents people actually follow
Evidence-based guidelines, policies and SOPs with change control, review and an implementation plan baked in.
Our process
From draft to adoption
- Scope & evidenceDefine purpose and ground it in authoritative guidance.
- Draft & reviewStakeholder review with version control.
- Approve & controlSign-off and a change-control log.
- Implement & trainRollout support so it's used in practice.
The shelf-ware problem
A document only protects you if people follow it
Healthcare organisations are rich in documentation and poor in adoption. Folders fill with guidelines that contradict each other, policies written for a structure that no longer exists, and SOPs that staff have never read. When something goes wrong, the question an investigator or regulator asks is not whether a document existed but whether it was current, controlled and actually used. A policy nobody follows offers no protection — it can even worsen the position, because it shows the organisation knew the right approach and did not embed it.
We write guidelines, policies and SOPs to be used, which changes how they are built. Each is pitched at the correct level — advisory guidance, mandatory policy or step-by-step procedure — grounded in authoritative sources such as NICE and royal college standards, and wrapped in the version control, review dates and ownership that keep it defensible. Crucially, the work does not stop at sign-off: we plan the rollout and training that turn a document into routine practice. This sits within our wider clinical advisory and governance offering.
What you get
A controlled, adoptable document set
- A guideline, policy or SOP pitched at the right level for its purpose
- Referenced grounding in NICE, royal college and other authoritative guidance
- A version-control and change-control framework with a documented review date
- A named owner and an approval and sign-off route
- A stakeholder-review record showing who contributed and approved
- An implementation and training plan so the document is embedded, not filed
Where this is needed
Common triggers for commissioning the work
New service or pathway
You are standing up a service and need the governing documents in place before it goes live, written to satisfy clinical governance from day one.
Inspection or audit gap
A review has flagged out-of-date, missing or uncontrolled documents and you need them brought to a defensible standard quickly.
Digital tool rollout
A new device or software needs SOPs and safe-use policies so staff adopt it consistently and the clinical-safety case holds together.
Where a new policy supports introducing technology into clinical use, pair this with our NHS pilot design and evaluation work, and for AI-enabled tools with AI validation and clinical safety.
Keeping it alive
Documents that stay current
The value of a clinical document erodes the moment the evidence beneath it moves on. A policy that cited the right guidance two years ago can become a liability if that guidance has since changed and the document was never revisited. This is why we treat a guideline, policy or SOP as something to be maintained rather than delivered once and forgotten. Every document leaves our hands with a named owner, a review date and a change-control log, so that updates are deliberate, recorded and traceable when an inspector or auditor asks how the document has been kept current.
That discipline also makes future revisions cheaper. When NICE or a royal college updates its position, you are amending a well-structured, controlled document rather than rebuilding from a tangle of conflicting versions. We can hand the maintenance to your team with a clear framework, or stay involved to refresh documents as guidance evolves. Either way, the goal is the same: documentation that genuinely governs practice and continues to protect both patients and the organisation, as part of our wider clinical advisory and governance support.
Answers
Frequently asked questions
How do you ensure documents get adopted?
We build in stakeholder review, version and change control, and an implementation/training step — so the SOP is used, not shelved.
Do you align to recognised guidance?
Yes — we ground policies in NICE, royal college and other authoritative guidance, and reference sources clearly.
What is the difference between a guideline, a policy and an SOP?
A guideline advises on best clinical practice and allows professional judgement; a policy sets the rules an organisation requires; and an SOP gives the precise, repeatable steps for a task. We make sure each document is written at the right level so it neither over-constrains clinicians nor leaves critical steps ambiguous.
How do you keep documents current?
Every document is given a review date, an owner and a version history. When underlying guidance changes, the change-control log shows what was amended and why, which is what auditors and inspectors look for.
Can you convert an existing document rather than start from scratch?
Yes. We frequently take a legacy policy or a draft an organisation already has, check it against current authoritative guidance, restructure it for clarity and add the control and implementation elements that were missing.
Need a guideline or SOP?
Tell us the topic and we'll scope the work.