Record a pharmacist and a dispenser talking through how the task is really done, paste that transcript into AI with the exact wording of your regulator's standards and your SOP template, and ask for a draft where every "must" cites a source. Then gap-check it, test it on the bench, and have the pharmacist in charge sign it off.
The trap is letting AI supply the rules. Ask a chat assistant for "a controlled drugs SOP" and it will write something fluent that blends requirements from several countries and several decades. The legal and professional content has to come from documents you paste in; AI's job is structure, plain wording and spotting gaps. Done that way, a typical SOP takes about two hours of staff time instead of most of a day.
What AI does in an SOP, and what it never does
- AI does: turn a rambling spoken walk-through into numbered steps; apply your template consistently; rewrite for a newly qualified dispenser's reading level; compare a draft against source documents and list what's missing; produce a one-page quick-reference version.
- AI never does: decide what the law or your professional standards require; decide who is accountable for a step; set clinical thresholds; approve the SOP. Those stay with the superintendent or pharmacist in charge.
If you want the broader reasoning on which pharmacy jobs should stay entirely human, pharmacy tasks you should never hand to AI covers it. This workflow assumes the task itself stays human and only the document is AI-assisted.
Stage 1: Capture how the task is actually done (15-20 minutes)
Old SOPs often describe how a task was done five years ago, or how someone thought it should be done. Start from reality. Sit the person who does the task most with the person who checks it, put a phone on the counter, and record them talking it through, including the awkward bits ("if the fridge alarm goes off at the weekend, the owner gets a text and...").
Transcription is cheap now. Otter.ai Pro lists at $8.33 per user a month billed annually, the Gemini app accepts uploaded audio, and Gemini Notebook transcribes an audio file when you add it as a source. Keep patient names out of the recording; use invented examples if you need to talk through a case.
A captured snippet, before any tidying:
"...so first thing, before we open, whoever's in first reads the
fridge. Min, max and current off the digital thermometer, writes it
on the sheet, initials it, then presses reset. Same at close. If it's
out of range you don't use anything from that fridge, you tell the
pharmacist, and we put a sign on the door. Then, um, the pharmacist
rings the manufacturer or the wholesaler, depends on the product..."That's messy, but it contains the real sequence, the real roles and a real exception. It's far better raw material than a blank page.
Compare it with the SOP it replaces. The illustrative old version said: "Fridge temperatures are recorded daily by the pharmacist and any deviations are managed in line with requirements." The recording shows three differences. Readings are taken twice a day, not once; whoever opens or closes takes them, not the pharmacist; and there is a specific response to an out-of-range reading (stop supplying, sign on the door, pharmacist phones the supplier) that the old wording hid behind "in line with requirements". A model asked to "update" the old SOP would have polished that sentence. Starting from the recording gets the three real steps written down.
Stage 2: Gather the rules the SOP has to meet (20 minutes)
Collect the exact wording that applies: the relevant section of your pharmacy regulator's standards, your professional body's guidance, any contract requirements for services you provide, and manufacturer or wholesaler instructions. Copy the text into a single document and number each source: S1, S2, S3. Note the version date of each, because the SOP's reference section will need it.
Put these files, your SOP template and your house style into a Project on a business plan (ChatGPT Business, Claude Team, or Copilot with the files in SharePoint). Business plans don't train on your content by default. SOPs contain no patient data, but they do describe your security arrangements for controlled drugs and cash, so treat them as internal documents.
Stage 3: Draft against a fixed template (10 minutes)
Use the same template for every SOP, so staff always know where to find the exception route or the record-keeping step. A workable structure:
SOP TEMPLATE
Header: title, SOP number, version, author, approver, effective
date, review date
1. Purpose (one sentence)
2. Scope (who and what this covers; what it does NOT cover)
3. Roles and responsibilities (by job title, not name)
4. Procedure (numbered steps, one action per step)
5. Critical points (steps where an error could harm a patient)
6. Records kept (what, where, how long)
7. Exceptions and escalation (what to do when X goes wrong)
8. References (source, section, version date)
9. Training and sign-off recordThe drafting prompt does the heavy lifting:
Using the transcript below, draft an SOP in our template.
Rules:
- Every requirement ("must", "always", "never") must cite a source
from S1-S4 in brackets, e.g. [S2 s.3.1]. If the transcript describes
a practice with no source, keep it but mark it [OWNER DECISION].
- Do not add any requirement that is not in the transcript or sources.
- One action per numbered step. Job titles, not names.
- If the transcript and a source disagree, flag it as
[CONFLICT: ...] and do not resolve it.
- Plain English for a dispenser in their first month.
Transcript: ...The [OWNER DECISION] and [CONFLICT] tags are what make this safe. They turn every assumption into something the pharmacist has to look at.
A conflict tag earns its place the first time it fires. In an illustrative returned-medicines SOP, the dispenser's transcript said "returns go straight in the blue bin under the dispensing bench", while the waste contractor's instructions (S4) required returned medicines to be kept in a sealed container in a designated area, separate from dispensing stock. The draft came back with:
4.2 Place the returned item in the returns container. [CONFLICT: transcript says the blue bin under the dispensing bench; S4 s.2 requires a designated area separate from dispensing stock. Not resolved.]
Without the instruction not to resolve conflicts, the model would have quietly picked one version, probably the source's, and the SOP would have described a storage arrangement the shop didn't actually have. With the tag, the pharmacist saw that the practice was the problem, moved the container to a labelled shelf in the back room, and the step now describes where it really is. An SOP that matches the rules on paper but not the shop floor is the kind an inspector spots in minutes.
A worked example: the fridge temperature SOP
Take an illustrative independent pharmacy with two pharmacists and four dispensing staff. From the transcript above plus three sources (the regulator's premises standard, the wholesaler's cold-chain guidance, and the fridge manufacturer's manual), the model produced a draft whose procedure section began like this (illustrative output):
4.1 At opening, the first trained staff member on site reads the minimum, maximum and current temperature on the fridge's digital thermometer. [OWNER DECISION]
4.2 They record all three readings, the time and their initials on the Fridge Temperature Record. [S2 s.4]
4.3 They press the reset button so the next reading covers the following period. [S3 p.12]
4.4 If any reading is outside the required range (2 to 8°C) [S2 s.4], they must not supply any product from that fridge, and must inform the pharmacist in charge immediately. [OWNER DECISION]
4.5 The pharmacist contacts the manufacturer within one hour for advice on affected stock.
The pharmacist's review took 25 minutes and changed four things:
- Step 4.5 had no source tag. The model had invented "within one hour". The source said to seek advice before using the stock, with no time limit, so the timing was removed and the step now names both the manufacturer and the wholesaler, as the transcript did.
- The draft left out the sign on the fridge door. Added as 4.6: quarantine the stock with a "Do not use" label.
- The transcript's weekend alarm text never made it into the draft. Added to the exceptions section, with who receives the alert.
- Two
[OWNER DECISION]steps were confirmed as house policy and the tag was replaced with "Pharmacy policy".
Total staff time: 20 minutes recording, 20 gathering sources, 10 drafting, 25 reviewing, 15 bench testing and 10 on sign-off. Roughly 1 hour 40 minutes. The previous version of this SOP had been rewritten by hand a year earlier and, by the owner's estimate, took most of an afternoon.
Stage 4: Make AI hunt for gaps in its own draft
Open a fresh chat so the model isn't defending its earlier work, and ask it to act as a critical reviewer:
Compare the SOP below against sources S1-S4.
Produce two tables:
A) Requirements in the sources that the SOP does not cover.
Columns: source + section, requirement (quoted), suggested step.
B) Statements in the SOP with no support in the sources or
transcript. Columns: SOP step, statement, why unsupported.
Quote the sources exactly. Do not paraphrase requirements.An illustrative result for a dispensing accuracy-check SOP:
| Table | Finding | What the pharmacist did |
|---|---|---|
| A | Source requires a record of who performed the final check; SOP only says "check and bag" | Added initials on the bag label as step 4.9 |
| A | Source requires near misses to be recorded and reviewed | Added a link to the near-miss log SOP rather than repeating it |
| B | "Checks must be completed within 10 minutes of dispensing" | Deleted: invented, and a target like that encourages rushing |
| B | "Refer to the prescriber if the dose exceeds the maximum" | Kept, re-sourced to the professional guidance, and moved to Critical points |
Treat the output as a list of leads, not a verdict. The model can miss a requirement in a long source document, so the pharmacist still reads the sources once. What the gap check does well is catch the invented rules, which are the ones that cause trouble at inspection.
Stage 5: Test it on the bench with your newest person
Give the draft to the least experienced team member and ask them to follow it literally while someone watches. Every hesitation is an edit. In the accuracy-check example, a dispenser in their second month stopped at step 4.3 and asked, "What if the prescriber hasn't signed it?" The SOP assumed a valid prescription; the exception now points to the prescription-receipt SOP.
Deliveries make a good second bench test because the exceptions happen away from the shop. For an illustrative home-delivery SOP, the pharmacy asked its delivery driver to walk through the draft with three made-up cases: patient not in, patient not in with a fridge item, and a neighbour offering to take the parcel. The first case was covered. The second exposed a gap the transcript had skipped: the draft said "return undelivered items to the pharmacy" but not how quickly a fridge line has to go back into the fridge, or who records it. That became an [OWNER DECISION] for the pharmacist, answered with a time limit and a line in the fridge record. The third case, leaving medicines with a neighbour, the pharmacist decided was never allowed, and the SOP now says so in one sentence rather than leaving the driver to judge it on a doorstep.
After the bench test, ask AI for a one-page quick-reference card from the approved SOP (steps and critical points only) to keep at the workstation. Staff will read a card; they won't read nine pages at the bench.
Check the card against the approved SOP line by line, because this is where an old draft can creep back in. In one illustrative case, the Project still held the first draft of the fridge SOP alongside the approved version 3.0, and the card came back with "Pharmacist contacts the manufacturer within one hour", the invented deadline the review had deleted. The model had drawn on both files. The fix was dull and effective: move superseded drafts out of the Project into an archive folder, name the approved file with its version number, and start the card prompt with "Use only PH-07 v3.0. Ignore any other version."
Stage 6: Sign-off, version control and review dates
The document header is where AI-written SOPs most often look unfinished. A filled-in example:
Title: Refrigerated medicines: temperature monitoring
SOP number: PH-07
Version: 3.0 (replaces 2.1)
Author: Pharmacy technician, with AI drafting assistance
Approved by: Superintendent pharmacist
Effective date: 06/10/2026
Review date: 06/10/2027, or sooner after any incident
Changes in 3.0: weekend alarm route added; stock quarantine step addedA read-and-signed record shows that staff have seen the SOP, not that they understood it. A short check helps: ask AI for five multiple-choice questions based only on the approved SOP, each with one correct answer and the step it tests. An illustrative question from the fridge SOP:
Q3. The maximum reading this morning is 9.1°C. What do you do first?
a) Press reset and check again in an hour
b) Stop supplying anything from that fridge and tell the pharmacist
c) Ring the wholesaler
d) Move the stock to the second fridge
Answer: b (step 4.4)That one is sound. Another question in the same set offered "label the stock Do not use" and "tell the pharmacist" as separate options when the SOP requires both, so either could be argued as correct. The pharmacist rewrote it. Five questions take about three minutes for a dispenser to answer, and a wrong answer shows which step to talk through, which is more useful than a signature alone.
Store the approved version where version history is automatic (SharePoint or Google Drive both keep it) and keep a read-and-signed record for every staff member. Keep the prompts and source list in the Project, so next year's review starts from the same inputs rather than from scratch.
How long a full SOP set takes with this workflow
A rough budget for an illustrative community pharmacy rewriting its core set, with estimates for the old way alongside:
| SOP | With this workflow | Writing from scratch | Notes |
|---|---|---|---|
| Prescription receipt and clinical check | 2.5 hours | 5-6 hours | Long sources; allow extra review |
| Dispensing and accuracy check | 2 hours | 4-5 hours | Bench test is essential |
| Controlled drugs: receipt, storage, register | 3 hours | 5-6 hours | Highest scrutiny; pharmacist writes critical points |
| Refrigerated medicines | 1.7 hours | 3-4 hours | As in the worked example |
| Near misses and dispensing errors | 1.5 hours | 3 hours | Link to incident reporting route |
| Returned and waste medicines | 1.5 hours | 3 hours | Contractor instructions are a key source |
| Deliveries to patients' homes | 1.5 hours | 3 hours | Include failed-delivery exceptions |
| Owings and out-of-stock items | 1 hour | 2 hours | Mostly house policy |
These are planning estimates, not measurements. The saving comes mostly from not having to structure and word each document yourself; the review time barely shrinks, and it shouldn't.
How AI-drafted pharmacy SOPs fail, and the tell for each
- Borrowed rules from elsewhere. The draft mentions a form, register format or retention period you've never heard of. Tell: a requirement with no source tag, or a tag pointing to a source that doesn't say it.
- Filler instead of steps. "Ensure all activities comply with applicable legislation." Tell: a sentence nobody could act on. Delete it.
- Ideal order, not real order. The draft sequences steps logically, but your shop labels before it assembles. Tell: the bench tester does steps out of order. Change the SOP or change the practice, deliberately.
- Roles blurred. "Staff should check..." Tell: nobody can say who. Every step needs a job title.
- Twelve pages. Tell: nobody has read it a month later. Keep the SOP complete and give staff the one-page card.
Two related workflows fit alongside this one. For procedures that live on a screen, like ordering or patient medication record tasks, building SOPs from screen recordings saves the capture stage. And the general version of this process, for non-clinical businesses, is in writing SOPs with AI from rough notes. Once the SOPs are in place, the same Project makes a good base for shortening phone queues and judging whether AI stock ordering pays off, because the house rules are already written down.
Further reads
- How to Classify Business Data Before Using AI Tools — Decide which pharmacy documents can go into which AI tools.
- How to Write a Health and Safety Policy With AI and What to Check — The same draft-then-verify approach for your health and safety policy.
- A Five-Minute Fact-Check Routine for AI Output Before It Goes Out — A five-minute routine for checking any AI draft before it's used.
- How to Set Up Human Review for AI Work Without Slowing Down — Designing a review step that doesn't stall the whole SOP programme.
- AI Hallucinations Explained for Business Owners: Causes and Fixes — Why the model invents confident rules, and how to spot them.
- How to Use ChatGPT Projects to Keep Client Work Separate — Keeping SOP source documents in one tidy workspace.
- How to Build a Kitchen Training Manual With AI — Capture how your kitchen really works, let AI shape it into station cards and quizzes, and keep every temperature and allergen under the head chef's control.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: pricing pages for Microsoft 365 Copilot Business, ChatGPT Business, Claude Team and Otter.ai (checked September 2026). SOP examples are illustrative; confirm every requirement against your own regulator's standards and professional guidance.