Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Independent pharmacies run on repetition—counting, verifying, documenting, calling, entering, and double-checking. If you’re the one who knows how it’s “supposed to be done,” your business is tied to your availability. That’s where Standard Operating Procedures (SOPs) come in.

SOPs are the step-by-step instructions that keep your pharmacy working the same way every day, even when you’re sick, on vacation, or tied up with a queue of patients. The goal is simple: create a system where a new tech or floater can be about 80% effective on day one by following written instructions.

Think about a pharmacy task that must be consistent—like processing a controlled prescription refill, handling an insurance rejection, or completing a transfer request. Your SOP doesn’t just “explain”; it reduces mistakes by making the process predictable.

The Importance of Brain-Dumping

Brain-dumping is the process of getting everything in your head out onto paper or a document your team can use. If it stays only in your head, your operations can’t grow beyond your personal capacity.

In an independent pharmacy, this often shows up as “tribal knowledge.” For example, you might know exactly what to say to an insurance plan when you hit an error code, or which steps prevent you from submitting the same claim twice. Your team might learn it by watching you—or they might guess and cause a delay.

Brain-dumping turns those hidden steps into a repeatable workflow.

Creating Effective SOPs

A useful SOP is built for real work at the counter and in the workflow system.

1. Why: Start with why the task matters. In pharmacy, the “why” often connects to patient safety, accuracy, and compliance. Your team should understand the risk you’re preventing.
2. What: Write the exact steps your staff should follow. Include what to click, what to check, and what to document.
3. Outcome: Define what success looks like. In pharmacy terms, this could mean: the claim goes through correctly, the patient receives the right quantity, documentation is complete, and the chart shows the right notes.

Example (Controlled refill workflow):
- Why: “We must verify patient identity, dosing, and authorization because controlled medications require extra accuracy.”
- What: “Check the patient profile, confirm last fill date, verify quantity and directions, review authorization status, submit per system rules, document the verification steps, and flag anything unusual to the pharmacist.”
- Outcome: “Refill is processed without rework; notes are complete; any exceptions are handled the same day.”

Example (Handling insurance rejections):
- Why: “Rejections cause patient delays and cash-flow interruptions.”
- What: “Check rejection reason, verify formulary requirements, confirm eligibility, run alternate NDC options if allowed, submit with correct diagnosis/plan requirements, and document the outcome.”
- Outcome: “Rejection cleared or documented with a clear next action: call prescriber, request prior auth, or prepare patient call-back.”

Organizing Your SOPs

All SOPs need one central home where your team can find them fast—because in pharmacy you don’t have time to “look around.” Store them in one place like Notion, Google Drive, or your team’s shared wiki.

Set up a folder structure that matches your pharmacy reality. For example:
- Dispensing SOPs
- Refills & Controlleds
- Transfers
- Insurance & Billing
- Patient Calls & Follow-ups
- Returns & Credits

Add a short naming rule so staff can search quickly. For instance: “INS-01 Rejection Workflow (Common Codes)” and “TRN-03 Transfer Intake Call Script.”

The Loom-First Approach

Writing every SOP from scratch is slow. Instead, record yourself doing the task with a screen recording.

Use Loom (or similar) to capture:
- Your screen steps (what you click)
- What you check (patient profile, prescriber details, last fill dates)
- What you document (where notes go)
- How you handle exceptions

A video is powerful for pharmacy because many tasks depend on what you see and how you verify. Your SOP becomes easier to learn when your team can watch your exact workflow.

Building a Culture of Self-Reliance

Once SOPs exist, train your team to use them before guessing. When someone asks, “How do we do this?” the process should be: check the SOP vault first, then ask questions if the SOP doesn’t cover it.

This matters because pharmacy work is high-stakes. The fastest teams aren’t the ones with the most questions—they’re the ones with the best access to the right procedure.

By brain-dumping your knowledge, turning it into SOPs, and building a team habit of using them, you create a pharmacy that runs the same whether you’re there or not. That’s how you free up hours for better patient care, better staffing, and smarter growth—without sacrificing accuracy.