How Pharmacy Accreditation Works: A Coordinator's Guide

You're about to start a pharmacy accreditation cycle — or you're a few months into one and trying to figure out where you actually are in it. Either way, what you need first is the process itself, clearly: what happens, in what order, who does what, and where the real work lives.

This is a practical guide to how pharmacy accreditation works. It covers the two bodies that accredit pharmacy programs — ACPE in the US and CCAPP in Canada — what each expects from the self-study, what happens on site-visit day, and the part that surprises most coordinators: the evidence itself, and how much of the cycle is spent just finding it.

If you've come to pharmacy from CEAB, ABET, or CAAHEP, some of this will feel familiar. Some of it won't. The differences are exactly where cycles go sideways — so we'll flag them as we go.

Hands completing a self-study document at a desk

The Two Bodies to Know: ACPE and CCAPP

Pharmacy accreditation runs through two main bodies, depending on where your program sits.

ACPE — the Accreditation Council for Pharmacy Education — is the primary accreditor for pharmacy programs in the United States. Its current standards, Standards 2025 (effective July 1, 2025), are organized into seven standards with numbered key elements, and the self-study demonstrates how the program meets each one. ACPE also handles the path from new-program status to full accreditation, and the periodic re-evaluation that maintains it.

CCAPP — the Canadian Council for Accreditation of Pharmacy Programs — accredits professional pharmacy degree and pharmacy technician programs in Canada. It operates on a similar evidence-backed self-study model, with its own set of standards and its own visit process.

Why does the distinction matter to you? Because everything you'll do in the coming months is set by the body that accredits your program. The standards you'll map against, the self-study template you'll use, the visit schedule you'll work against — all of it is body-specific. The first step of any pharmacy accreditation cycle, before writing a word, is knowing which body covers your program and what that body requires.

The Self-Study Is Where the Work Lives

The self-study is the centerpiece of the cycle — and it is not a form you fill in once. It is a reflective, evidence-backed review of your entire program against the standards. Done well, it makes your program look hard at its own practice: what you do, how you know it works, and where you fall short.

For each standard and key element, the self-study doesn't just claim compliance — it points to evidence. That's the part that takes the hours. The evidence behind a single indicator might live in:

a course syllabus and its assessment rubrics (in the LMS or a course folder),
student outcomes or program-level assessment results (in a spreadsheet or an assessment tool),
faculty qualifications and continuing professional development records (in HR files),
curriculum maps and committee minutes (in shared drives — sometimes on one person's laptop).

The self-study is only as good as the evidence behind it — and that evidence is rarely in one place. That's the real work of the cycle: not writing the narrative, but assembling, verifying, and organizing the proof.

A professional writing in a notebook at an office desk

What the Evidence Actually Looks Like

Here's the shape of it, because it's the same shape whether your body is ACPE or CCAPP. Three levels of the program connect to the standards:

Indicators — the checkpoints in a standard (ACPE calls them key elements; your accreditor's term may differ). Each one needs supporting evidence.
Courses — each course (PHAR 401, say) contributes to one or more indicators. The same course can support several; the same indicator is often supported by several courses.
Programs — a program (the PharmD, cohort 2024) is a collection of courses, and its overall compliance is the sum of how well each course maps to each indicator.

The question every coordinator faces, usually in the weeks before a visit: for each indicator, can I show which courses and which documents support it — and where are the gaps? If the answer requires opening six systems and three spreadsheets, you don't have a map. You have a hunt.

The Site Visit: What the Team Actually Does

A visiting team comes in, reviews the self-study and the evidence behind it, interviews faculty and students, and checks that the program meets the standards. The visit goes well when the evidence is organized and findable — the team asks for the support behind an indicator, and it's there, in seconds.

The visit goes badly when the team has to hunt. Every "let me go find that" is a small loss of confidence in the program's self-knowledge. The program that gets through the visit calmly is almost always the one that had its evidence mapped before the team arrived — not the one that assembled it in the three weeks before.

A professional organizing accreditation records at a desk

Where Cycles Go Sideways

Three patterns show up again and again, and none of them are about the standards themselves:

The evidence chase. Many hours, every cycle, chasing evidence across systems that don't talk to each other. The coordinator becomes a human router between the LMS, the assessment tool, HR, and a master spreadsheet.
The single point of failure. The map lives in the coordinator's head and a set of files. When they leave — promotion, retirement, a new job — the institutional knowledge leaves with them, and the next cycle starts from scratch.
The spreadsheet ceiling. Spreadsheets work until the program grows, or a course is renamed, or an indicator is renumbered. Then every connection has to be re-verified by hand, and the map quietly drifts out of sync with reality.

What "Ready" Looks Like Before the Visit

Ready isn't a finished document. It's a state you can check at any time: for every indicator, you can see what supports it, what's missing, and where the evidence lives — without opening six systems.

That's the difference between a map and a hunt. One connected view, where you can start from any course, program, or standard and every connection follows automatically. Gap detection by indicator, so you know exactly what's ready for the visit and what still needs a document. And an export, so the evidence package for the team is one action, not a week.

None of this requires changing how your program teaches or what it assesses. It requires stopping the hunt and starting to point at the evidence you already have.