How to write clinical SOPs for UK telehealth: a practical operator's guide

Clinical SOPs (Standard Operating Procedures) are the documented operational substrate that keeps a UK telehealth service safe, compliant, and inspection-ready. They are also the operational artifact that most often goes underbuilt or under-maintained — usually because founders treat them as paperwork rather than as the actual practice manual. This piece is the operator's guide to writing SOPs that work in production and survive inspection.

What SOPs actually are — and what they're not

An SOP is a written description of how a specific clinical or operational process is performed in your service. It documents who does what, in what sequence, under what conditions, with what documentation, and with what escalation routes. SOPs are the operational substrate that GPhC, CQC, MHRA, and ICO inspections review — and the practical reference team members use when handling edge cases.

SOPs are not compliance paperwork. They are the practice manual. Brands that treat them as compliance theatre (write them once, file them, don't refer to them) discover at inspection that the documented practice differs from the actual practice. That gap is the single most common inspection finding. SOPs that match practice protect the service; SOPs that don't expose it.

Which SOPs every UK telehealth service needs

Foundational SOPs that every UK telehealth service needs: clinical pathway end-to-end (intake to ongoing care), prescriber sign-off and prescription handling, dispensing handover (if relying on a partner pharmacy) or full dispensing process (if in-house), identity verification, adverse event capture and Yellow Card reporting, complaint handling, safeguarding triage, data protection and DPIA alignment, incident response, and controlled drugs handling (if applicable to the category).

Category-specific SOPs as the operation grows: GLP-1 cold-chain handling, mental health crisis escalation, ADHD shared care, isotretinoin Pregnancy Prevention Programme adherence, etc. Build foundational first; layer category-specific as the service expands.

Anatomy of a good SOP

A good SOP has six elements. 1) Scope — what process this covers and what it doesn't. 2) Ownership — the named individual (or role) accountable for the SOP. 3) Procedure — the step-by-step description of how the process is performed. 4) Escalation — what to do when the procedure encounters a case outside its scope. 5) Documentation — what records are kept and where. 6) Version control — date, version number, change log.

Length follows substance: a simple SOP can be one page; a complex one (controlled drugs, clinical pathway) may be 5-10 pages. Resist the temptation to pad. Inspectors and team members both prefer concise, decisive SOPs over verbose, hedging ones.

Writing SOPs that match actual practice

The most important SOP writing principle: document what actually happens, not what should happen in theory. The gap between practice and documentation is the inspection failure mode. Two practical techniques. First, write SOPs collaboratively with the team that performs the process — they know the edge cases the founder doesn't. Second, walk through the SOP with the team monthly and update it where reality differs.

A SOP that doesn't match practice is worse than no SOP. Inspectors interpret the gap as either operational drift (the process changed and the SOP wasn't updated) or compliance theatre (the SOP was written for the file, not for the team). Neither interpretation works in the operator's favour.

Maintenance cadence — annual review is not enough

Many brands review SOPs annually as a compliance ritual. This is necessary but not sufficient. SOPs need updating whenever the process actually changes — new dispensing partner integration, new clinical pathway category, new prescriber sign-off tooling, new safeguarding pattern surfaced by an incident.

Practical cadence: monthly SOP review on a rolling schedule (one or two SOPs per month), event-triggered updates when material change happens, full annual review as a backstop. This keeps SOPs aligned with reality without overwhelming the team. The named SOP owner runs the review; the clinical lead approves; the version log records the change.

Inspection readiness — how SOPs are reviewed

GPhC inspections review SOPs by request. CQC inspections review them as part of the Well-led and Safe domains. MHRA inspections review them for the regulated activities (dispensing, pharmacovigilance) the SOP covers. ICO engagement may reference DPIA-aligned SOPs.

Inspectors typically: ask for the SOP register, request specific SOPs by topic, interview team members about how the process actually runs, and look for alignment between SOP and practice. Brands with well-maintained SOPs that match practice navigate inspection cleanly. Brands without struggle through every inspection regardless of the underlying clinical quality.

How PExpo handles SOPs for brand and clinic customers

PExpo's brand model includes the clinical and dispensing SOPs that cover the regulated layers — pharmacist sign-off, dispensing process, adverse event capture, pharmacovigilance, controlled drug handling, GDP-compliant cold-chain. Brand customers receive the SOP framework as part of the operational stack rather than building it from scratch.

The brand still owns brand-side SOPs (consultation experience, support escalation, patient communication, marketing review). The split is documented in the contractual relationship. See our [brand model page](../brands.html) for the operational scope or our [GPhC inspection preparation guide](preparing-for-gphc-inspection-clinic.html) for the broader inspection readiness context.

SOPs are not compliance paperwork. They are the practice manual. Brands that treat them as compliance theatre discover at inspection that the documented practice differs from the actual practice.

Clinical SOPs are the operational substrate of a UK telehealth service — the documented description of how the practice actually runs. Operators that maintain SOPs that match practice navigate inspection cleanly and operate consistently. Operators that treat SOPs as paperwork struggle through every inspection regardless of underlying clinical quality. See our brand model page for PExpo's operational stack including the regulated-layer SOPs, our GPhC inspection preparation guide, or our CQC registration guide.

Frequently asked questions