How to Write SOPs for Healthcare: A Step-by-Step Guide
Healthcare SOPs must satisfy regulators and be usable at the bedside. Here's how to write procedures that do both.
The people who build PathPilot
Healthcare SOPs must meet clinical and regulatory requirements while being written clearly enough for staff to follow under pressure. The key steps are: define the regulatory scope, map every decision point before writing prose, use numbered steps in plain language, add the required compliance header, pilot with non-authors, and publish at the point of care — not in a folder no one opens during a procedure.
Healthcare SOPs carry consequences that SOPs in most other industries don't. A missing step in a patient handover procedure, an undocumented contraindication in a medication protocol, a decision branch that doesn't account for an allergic reaction — any of these becomes a patient safety incident or a CQC enforcement action.
The challenge is writing procedures that satisfy regulatory requirements without becoming so long and complex that staff skip them under time pressure. Most healthcare SOPs fail at one end or the other: compliant but ignored, or followed but under-documented.
This guide covers how to write healthcare SOPs that do both: meet the regulatory standard and get followed at the point of care.
Why healthcare SOPs are harder to write than other SOPs
Three things make clinical procedure documentation harder than documentation in most other domains.
Conditional complexity. Most business processes have some decision points. Clinical procedures are almost entirely decision points. The correct action at step 4 depends on what the patient presented at step 2, what their baseline reading was before the procedure started, whether they disclosed a specific medication history, and what the clinician observed at step 3. Flat numbered lists cannot represent this structure honestly.
Multiple audience levels. The same SOP may need to be usable by a band 5 nurse, a bank staff member covering their second shift, and a senior clinician reviewing it for accuracy. These three users have different knowledge bases. Writing at the wrong level for any one of them creates risk.
Regulatory audit trail. Healthcare SOPs are not just operational tools — they are evidence in an inspection. Every version must be traceable. Every approval must be attributed. Every review must be documented. This documentation requirement is non-negotiable and adds significant overhead to the authoring process.
Step 1: Define scope and regulatory context before writing a single word
Healthcare procedures are governed by overlapping regulatory frameworks. Before writing, identify which ones apply to this specific SOP:
- CQC Key Lines of Enquiry (KLOEs): Relevant for all registered providers in England. Safe, Effective, Caring, Responsive, Well-led. Your SOP should be traceable to the KLOEs it supports.
- NICE guidelines: Where a clinical guideline exists, your SOP should reference it and explain any local deviations.
- COSHH (Control of Substances Hazardous to Health): Mandatory for any procedure involving chemical hazards, disinfectants, or laboratory materials.
- ISO 15189: Applies to medical laboratories. Has specific requirements for document control, validation, and review cycles.
- NHS Trust or ICB policies: Many Trusts have a standard SOP template and document control policy that all departmental SOPs must follow. Check before starting.
If you don't know which frameworks apply, speak to your governance or compliance team before writing. Retrofitting compliance requirements to a completed SOP is significantly harder than designing for them from the start.
Step 2: Interview the person who actually does the procedure
The most reliable source of procedure content is the person who performs it most often — not the person who manages it, not the person who designed the protocol, not the training material from five years ago.
Conduct a structured interview with one or two experienced practitioners. Ask:
- Walk me through the procedure from trigger to completion. What is the very first thing you do?
- Where do things most often go wrong or require a judgment call?
- What do you do if the patient can't complete step X?
- What are the two or three situations where a junior member of staff would need to escalate?
- Is there anything the written protocol says that doesn't match what you actually do? If so, why?
That last question surfaces the gap between documented procedure and actual practice — which is often significant in healthcare settings. If experienced staff have developed a better approach, the SOP should capture it, not the outdated protocol.
Step 3: Map the decision branches before writing prose
Once you have the procedure captured from your interview, map the decision points before you write a single numbered step.
A decision branch in a clinical SOP looks like: "If the patient's blood pressure reading is above 180/120 before the procedure, do not proceed — follow the hypertensive emergency protocol." That is a branch. Every "if" in a clinical procedure is a branch.
List every branch point. For each one, identify:
- What is the condition being evaluated?
- What are the possible outcomes (usually two, occasionally three)?
- For each outcome: what is the correct next action?
- Does the staff member performing this step have the authority and competence to make this decision, or does it require escalation?
This map is your SOP's skeleton. Writing the prose steps before doing this means writing them twice.
Step 4: Write numbered steps in plain clinical language
Healthcare SOPs should be written at approximately the reading level of a secondary school leaver entering the profession. This is not because clinical staff are not intelligent — it is because procedures need to be usable under time pressure, in poor lighting, during an emergency, by someone who hasn't performed this procedure in six months.
Rules for writing SOP steps:
- One step = one action. "Wash hands and don PPE" is two steps. Separate them.
- Start each step with a verb. "Confirm patient identity using two identifiers." Not "Patient identity should be confirmed."
- State the success criterion. Don't just say "check the reading" — say "check the reading and confirm it is within the acceptable range of X–Y."
- Make decision points visible. If a step requires a yes/no decision with different next actions, format it explicitly: "If [condition], proceed to step 7. If not, proceed to step 9."
- Avoid abbreviations not universally known. Spell out the first instance; abbreviate thereafter only if the term appears 5+ times.
Target word count for a standard clinical procedure: 600–1,200 words for the procedural steps (not including the compliance header). If the procedure genuinely requires more, consider whether it should be split into sub-procedures.
Step 5: Include the required compliance header
Every healthcare SOP — regardless of the regulatory framework — should have a structured header that documents the administrative metadata. This header is what inspectors look for first, and what audit trails are built from.
Required header fields:
- Document reference number — unique, consistent with your document control system
- Version number — version 1.0, 1.1, 2.0, etc.
- Effective date — the date from which this version is in force
- Review date — the date by which this version must be reviewed
- Author — name and role of the person who wrote it
- Approver — name and role of the person who approved it (typically clinical lead or governance lead)
- Applicable staff roles — which staff grades and roles this applies to
- Regulatory references — which standards or guidelines this SOP satisfies
- Document history — a table showing version, date, author, and summary of changes
If your Trust has a document control system (e.g., Datix, Ulysses, or a SharePoint-based system), the SOP must be submitted through that system to get a reference number. Do not publish a healthcare SOP without one.
Step 6: Pilot the SOP with non-authors
The author of an SOP is the worst person to review it. They know what they meant to write, so they read what they meant rather than what they wrote. They know the implicit context, so they don't notice the missing assumptions.
Before submitting the SOP for formal approval, run a structured pilot with three to five staff members who were not involved in writing it. Ask them to follow the procedure step by step and report:
- Any step where they were uncertain what to do
- Any assumption the SOP makes that they don't share
- Any edge case the procedure doesn't cover that they have encountered
- Any step that felt redundant or unnecessarily detailed
Document the feedback systematically. Every change made in response to pilot feedback should be logged in the document history table.
Step 7: Publish at the point of care
A healthcare SOP that lives in a document management system three clicks from the clinical area will not be used during a procedure. It will be used during training and then forgotten.
Effective point-of-care publication methods:
- QR codes on equipment: Laminated QR codes on the relevant equipment that link directly to the SOP. Particularly effective for equipment-specific procedures.
- EHR integration: Embed links to the SOP in the relevant section of your electronic health record. When the clinician opens the relevant order or assessment, the procedure is one click away.
- Interactive flows: Tools like PathPilot's healthcare SOP software let you build the procedure as an interactive decision tree that staff navigate step by step on a tablet or workstation. This format handles branching logic better than any flat document.
- Printed quick reference cards: For procedures where digital access is impractical, a one-page laminated quick reference card summarising the key steps is better than nothing.
Step 8: Set a review cycle and assign a named owner
An SOP without a named owner will not get reviewed. "The department" is not an owner. A job title without a specific named person attached to it is not an owner. The owner must be a named individual who appears on the document.
Review frequency guidance by procedure type:
- High-risk clinical procedures (medication administration, invasive procedures, emergency protocols): review annually
- Infection control and COSHH procedures: review annually or when guidance changes
- Standard clinical procedures: review every 2–3 years
- Administrative procedures (patient check-in, appointment booking): review every 3 years
Build the review date into your governance calendar. The owner should receive a reminder 3 months before the review date. A procedure that passes its review date without renewal cannot be used and must be withdrawn until it is reviewed — which creates operational risk. Do not let review cycles slip.
Healthcare SOP template structure
Use this structure as your starting point for any healthcare SOP:
- Document header (reference number, version, dates, author, approver, scope, regulatory references, document history)
- Purpose — one paragraph: what this procedure achieves and why it exists
- Scope — which staff roles, clinical settings, and patient groups this applies to
- Definitions — any clinical or technical terms that may not be universally understood
- Equipment and materials required — complete list, with any substitutions that are and are not acceptable
- Safety precautions — any PPE requirements, contraindications, or safety warnings that must be confirmed before starting
- Procedure steps — numbered, one action per step, with decision branches marked explicitly
- Post-procedure actions — documentation requirements, equipment disposal, follow-up
- Escalation and emergency actions — when to escalate, to whom, and what to do in an emergency
- References — clinical guidelines, regulatory standards, related SOPs
- Appendices — any supporting documents, recording forms, or quick reference materials
Common healthcare SOP mistakes
Writing to satisfy an inspection rather than guide a procedure. SOPs written primarily to demonstrate compliance tend to be comprehensive on paper and useless at the bedside. The test is not "does this satisfy the inspector" but "can a band 5 nurse on their first shift follow this safely?"
Capturing ideal practice rather than actual practice. If the documented procedure doesn't match what experienced staff actually do, the SOP will be ignored. The more it diverges from real practice, the more likely staff are to decide the document is "out of date" and not worth following.
Missing the handover and escalation steps. A high proportion of patient safety incidents in healthcare occur at handovers — shift changes, transfers, discharges. SOPs that cover the clinical procedure but not the handover and documentation steps leave a significant gap.
No version control. In a CQC inspection, being unable to demonstrate that staff are following the current version — not a version from 2022 — is a significant finding. Version control is non-negotiable.
Making your healthcare SOPs interactive
The most significant improvement most healthcare teams can make to their SOP adoption is moving from document-based SOPs to interactive ones.
An interactive SOP presents one step at a time, asks the staff member to confirm completion, branches based on what they observe, and routes them to the escalation path when it's needed. It functions like a clinical decision support tool rather than a document.
This format is particularly effective for: complex procedures with multiple branches, infrequently-performed procedures where staff need prompting, induction and training pathways, and any procedure where step completion needs to be audited.
PathPilot's SOP software for healthcare lets you build interactive clinical procedures without any coding. The flows can be published as a QR code, embedded in your intranet or EHR, or accessed via a direct link on any device. Each step is tracked, so you have a completion audit trail as a side effect of normal use.
Frequently asked questions
What must a healthcare SOP include?
A healthcare SOP must include: a unique reference number, version number, effective date, review date, the name and role of the approving clinician or manager, scope, numbered procedural steps, decision branches for significant edge cases, safety warnings, references to relevant regulatory standards, and a document history table.
How often should healthcare SOPs be reviewed?
Most regulatory bodies require review every 1–3 years. High-risk procedures (medication administration, emergency protocols, infection control) should be reviewed annually. The review date must appear on the document and a named owner must be accountable for completing the review.
How do you write a clinical SOP that staff actually follow?
Staff follow SOPs when they are written at the right complexity level for the role performing them, accessible at the point of care, explicit about edge cases, and updated promptly when practice changes. Interactive SOP tools that present one step at a time and branch based on patient presentation significantly improve adherence compared to PDF procedures.
What is the difference between a clinical guideline and a healthcare SOP?
A clinical guideline provides evidence-based recommendations with professional discretion. A healthcare SOP is a prescriptive procedure for how a specific task is performed in your specific setting. SOPs reference guidelines and translate their recommendations into the exact steps your staff follow given your facility's equipment and patient population.
Can healthcare SOPs be interactive rather than document-based?
Yes. Interactive SOPs that present one step at a time, branch based on patient presentation, and confirm step completion are increasingly used in clinical settings — particularly for complex procedures, infrequent high-stakes tasks, and staff induction pathways. Tools like PathPilot support this format without coding.
Build interactive healthcare SOPs with PathPilot
Turn your clinical procedures into interactive decision trees your staff can navigate at the point of care — on a tablet, workstation, or via QR code. No coding required.
See PathPilot for healthcare →Build interactive flows with PathPilot
Turn your SOPs, decision trees, and knowledge base into navigable flows — free to start.
Start free — no credit card needed →Ready to build your first flow?
Start free — no credit card required. Your first flow can be live in under 10 minutes.
Start building free →