Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures, or SOPs, are the written instructions for how your independent pharmacy works. They help the team provide safe, consistent service whether you are in the building or away. A strong SOP should allow a trained new hire to perform a task correctly with limited coaching on the first day.

For example, your pharmacy should not depend on the owner remembering how to handle a refill-too-soon rejection, receive a controlled substance order, process a manufacturer recall, or enroll a patient in a medication synchronization program. Each process should be clear enough for an authorized team member to follow while staying within state law, board rules, payer requirements, and your pharmacist-in-charge's policies.

The Importance of Brain-Dumping

Brain-dumping means moving the knowledge in your head into a format the team can use. Independent pharmacy owners often carry years of practical knowledge: which prescriber's office prefers electronic requests, how to resolve a difficult third-party rejection, when to call a long-term patient, or how to spot a questionable prescription.

That knowledge is valuable, but it becomes a business risk when only one person knows it. If you are sick, on vacation, or focused on buying inventory, the pharmacy should still be able to serve patients safely.

Real-World Example: You may be the only person who knows how to work a Medicare Part D rejection for a high-cost inhaler. Record the exact steps, including what information to gather, when to contact the prescriber, how to document the call, and when to escalate to the pharmacist. The team can then handle the next similar rejection without waiting for you.

Creating Effective SOPs

Use the same three-part structure for every procedure:

1. Why: Explain why the task matters. This may involve patient safety, legal compliance, timely service, inventory control, or a better patient experience.
2. What: List the exact steps in order. Include the pharmacy system screen, required fields, phone numbers, forms, approval points, and documentation standards.
3. Outcome: Define what completed work looks like. State who reviews it, what record must be saved, and what exception requires pharmacist or owner attention.

Real-World Example: An SOP for processing a medication recall should explain why recalled products must be removed quickly, show how to identify affected NDCs and lot numbers, describe quarantine and documentation steps, and define how patients and prescribers are contacted when needed.

Do not write policies that authorize unlicensed staff to make clinical decisions. Separate technician duties from pharmacist-only decisions, and have the pharmacist-in-charge review procedures before use.

Organizing Your SOPs

Store every SOP in one searchable location, such as a controlled Google Drive folder, Microsoft SharePoint site, or pharmacy operations workspace. Organize folders by work area: prescription intake, dispensing, pickup, inventory, billing, clinical services, compliance, and opening or closing.

Use consistent names such as “SOP - Controlled Substance Receiving - Version 1.2.” Add an owner, review date, and version number. Retire outdated copies so a technician does not follow an old process after a software, payer, or state-law change.

The Loom-First Approach

For tasks that are hard to explain in writing, record yourself performing the work on screen or with a phone. Show how you process a refill request, print a daily will-call report, reconcile a wholesaler invoice, or document a vaccine service. Do not record patient names, prescription numbers, dates of birth, or other protected health information. Use a training account or redact the screen first.

A short recording gives a team member a practical starting point. Convert it into a written checklist with screenshots only when those images are safe to store.

Building a Culture of Self-Reliance

Teach staff to check the SOP library before interrupting the pharmacist or owner for routine process questions. This does not replace professional judgment or required escalation. It reduces repeated questions and keeps work consistent.

When a team member asks how to handle a routine delivery exception or return-to-stock task, ask, “Which SOP did you check?” If the answer is that no SOP exists, capture the process and add it to the library. Review procedures during huddles, onboarding, and annual competency checks.

The goal is not paperwork for its own sake. The goal is a pharmacy that can protect patients, train people faster, reduce owner dependence, and deliver the same reliable service every day.