Veterinary SOP Management: Templates and Best Practice for Practice Compliance

What an SOP is, and why it matters in a vet practice

A standard operating procedure (SOP) is a written description of how a recurring task is done in your practice. It exists for three reasons:

1. Consistency — the task is done the same way regardless of who is on shift
2. Training — new staff can be brought up to speed without watching someone for weeks
3. Compliance evidence — auditors (RCVS PSS, VMD, HSE) want to see that practice activities are controlled, not improvised

The RCVS Practice Standards Scheme doesn't dictate which SOPs you must have, but it does expect practices to have SOPs covering medicines management, infection control, anaesthesia, radiation, and clinical pathways. The VMD's controlled drugs guidance likewise expects documented procedures for controlled drugs handling.

If you don't have written procedures, you can't demonstrate compliance — the inspector's working assumption will be that the practice is uncontrolled.

Which SOPs are typically expected

A small animal practice operating to RCVS PSS Core Standards (or higher) is generally expected to have written procedures covering:

Medicines and pharmacy

• Procurement and ordering
• Receipt and stock control
• Dispensing (POM-V, POM-VPS, NFA-VPS)
• Controlled drugs handling — separate SOP, often required by VMD
• Out-of-date stock management and disposal
• Cold chain management (vaccines)
• Returns to manufacturer
• Off-licence (cascade) prescribing record-keeping

Infection control and biosecurity

• Hand hygiene
• Personal protective equipment (PPE)
• Cleaning and disinfection of consult rooms, surgery, and isolation
• Sterilisation and autoclave use
• Sharps handling and disposal (cross-references clinical waste SOP)
• Isolation procedures for infectious patients
• Reportable diseases and notifications

Clinical safety

• Anaesthesia checklist (pre-op, intra-op, recovery)
• Patient identification and consent
• Surgical site preparation
• Post-operative monitoring
• Critical incident reporting

Health and safety

• Risk assessment procedure (how risk assessments are conducted, reviewed, and stored)
• COSHH assessment procedure
• Ionising radiation Local Rules (separate document under IRR17)
• Manual handling
• Fire emergency procedure
• First aid arrangements
• Lone working

Practice operations

• Client communication and complaints
• Consent for treatment
• Estimates and itemised invoicing (now also a CMA pricing transparency requirement)
• Out-of-hours and emergency cover
• Confidentiality and data protection
• Staff induction and ongoing training records
• Clinical waste handling
• Equipment maintenance and calibration

This is a starter list. Depending on your practice scope (referral, exotic, equine, farm), additional SOPs may be needed.

SOP template structure

A workable SOP template covers:

Section	Content
Title	Specific, action-oriented (e.g., "Controlled Drugs Receipt and Register Entry")
Document control	Version number, author, approval date, review date, owner
Purpose	One sentence — what does this procedure achieve?
Scope	Who does this apply to? Which patients/situations/areas?
Definitions	Acronyms and terms used
Responsibilities	Who does what (named role, not named individual)
Procedure	Step-by-step actions, in order
Records	What records this procedure generates and where they are kept
References	Linked SOPs, regulations, guidance documents
Training	What training is required to perform this procedure
Review history	Version log — date, change, author

The RCVS Code of Professional Conduct supporting guidance and HSE good practice on procedure management both align with this structure.

Version control: the bit that fails inspections

The most common SOP failing isn't bad procedure content — it's poor version control. Patterns that fail inspection:

• No version number on the document — auditor can't tell which version is current
• Multiple versions in circulation — old printed copies pinned to walls, current version on a network drive nobody opens
• No review date — SOP written 6 years ago, no evidence of review since
• No record of staff acknowledgement — staff "have read" the SOP but no signature, no dated record
• Procedure has clearly changed in practice — staff doing it differently from the SOP, but the SOP wasn't updated

Practical version control:

1. Version number on every page in the footer (e.g., "v2.3 — reviewed 12/04/2026 — owner: Practice Manager")
2. Review cycle — annual minimum, immediately on regulatory change or incident
3. Single source of truth — one master copy, ideally digital, with print copies clearly marked as "uncontrolled when printed"
4. Acknowledgement record — staff signature/date when SOP issued or updated; tracked in training records
5. Change log — every version change captured: what changed, why, when, by whom

Staff training and acknowledgement

An SOP without an acknowledgement record is half a control. The audit chain looks like:

SOP exists → staff have read it → staff have been trained on it → staff are competent to do it → competence is documented → re-assessment happens periodically

Each link needs evidence. The most common gap is "staff have read it" — practices distribute SOPs by email or share-drive but don't track that staff have actually read and understood. A simple SOP register tracks:

| SOP title | Version | Issue date | Staff member | Signed acknowledgement | Trained (date) | Re-acknowledged (current version) |

In a digital system, the acknowledgement is a checkbox tied to the staff member's account. In paper, it's a signature on a printed sheet. Either is acceptable — what matters is that you can produce it.

Common SOP failures and how to avoid them

"We do it but it's not written down"

The hardest gap to close because it requires pulling a procedure out of practice habit and into writing. Approach: shadow the experienced staff member doing the task, write down what they actually do (not what they say they do), then iterate.

Inconsistent SOPs across the practice

Different staff have written different SOPs over the years. Audit shows three different procedures for the same task. Approach: assign one owner per SOP topic; consolidate to a single version; retire the duplicates.

SOPs that don't match practice

The SOP says "the duty vet checks all CD entries before close of business." In practice, this happens once a week. Audit finding. Approach: either change the SOP to reflect actual practice (if the actual practice is acceptable), or change the practice to match the SOP.

Locked-down PDF nobody can update

The SOP was written 4 years ago, the original Word file is lost, and no one can edit the PDF. Approach: extract the content, create a new editable master, version it as v2.0 with a note about the recovery.

How SOP management connects to other compliance

SOPs are the connective tissue between regulatory requirements and day-to-day practice activity:

• Controlled drugs compliance — at least 1 SOP, often more
• COSHH — chemical handling SOPs reference COSHH assessments
• Risk assessments — controls in risk assessments often require an SOP to be operational
• Clinical waste compliance — segregation and disposal procedure
• RCVS PSS — assessor will sample SOPs across multiple standard areas
• CMA pricing transparency — itemised billing and consent procedures

A well-managed SOP system is the foundation that several other compliance streams sit on.

Getting started

If your SOPs are out of date, scattered, or partially missing:

1. Map the SOPs you should have — use the list above as a starting checklist
2. Identify which exist — gather every SOP currently in circulation
3. Triage by risk — start with the highest-risk areas (CDs, anaesthesia, radiation, infection control)
4. Standardise the template — pick one structure and apply it
5. Set version control conventions — version numbers, review cycles, acknowledgement
6. Build the staff acknowledgement register — even if retroactively for current SOPs
7. Schedule the review cycle — calendarise annual reviews

You don't need to do all of it in one go. Practices that try to overhaul every SOP simultaneously usually stall. Triage by risk, work through the highest-risk areas first, and accept that the system will evolve over months rather than weeks.

---

This guide is general compliance information for UK veterinary practices, not legal advice. For specific regulatory queries, consult the RCVS Practice Standards Scheme framework, VMD guidance notes, and your defence body.