Compounding Risk Assessment Records: How to Implement Structure at Pharmacy Scale

Looking at the Ontario College of Pharmacists new template, what the growing volume of documentation means for compounding supervisors and how I am making this sustainable in my pharmacy.

Before we dive in, I will share a short video near the end showing how I restructured risk assessments inside my own system to make this sustainable in practice.

Risk assessments are not just paperwork. At least, they are not supposed to be.

In a compounding pharmacy, a risk assessment is the intellectual blueprint behind your operation. It answers the uncomfortable but necessary question: "What could go wrong, and how are we preventing it?"

• The level of compounding facility requirements (A, B, or C)
• How we protect staff
• How we protect the preparation
• Whether our facility is actually fit for what we are doing
• Whether we are compounding with intention, or vibes

The Ontario College of Pharmacists released a revised Non-Sterile Compounding Risk Assessment Template with a Companion Guide (February 2026). It is not presented as a mandatory replacement for every current process, but as a reference point for reflection and improvement opportunities.

And it is thorough, so let's talk about it.

What the Companion Guide makes very clear

The Guide states plainly that a risk assessment is a documentation tool to ensure registrants are considering both risk to the preparation and risk to the person. In other words: will this get contaminated and potentially harm the patient, and will this harm the compounder?

• One risk assessment per preparation, including different strengths of the same compound
• Review of each Risk Assessment Record every 12 months
• Assessment of cumulative risk across all compounds
• Risk Assessment Records for all existing preparations

Essentially, if you compound 120 formulations, you must maintain 120 different Risk Assessment Records.

Where the template really shines

Using the Progesterone 400 mg suppository sample, the template removes guesswork. It forces a structured pass through hazard identification, including SDS references, NIOSH considerations, WHMIS health hazard classifications, reproductive toxicity, ventilation requirements, microbial contamination risk, and cross-contamination risk.

In the sample documentation, progesterone is identified as a NIOSH Table 2 drug with reproductive toxicity and carcinogenicity concerns, requiring mechanical ventilation. That level of traceability moves teams from opinion to documented reasoning.

The Companion Guide also reinforces that NIOSH is not exhaustive. A substance missing from the list is not automatically safe. The expectation is not to follow a table blindly, but to understand the hazard.

The section on occasional small quantity intentionally avoids rigid numeric thresholds and pushes facilities to justify interpretation based on intensity, frequency, and cumulative exposure. That supports professional judgment while still requiring defensible reasoning.

The Guide also prompts facilities to evaluate cumulative risk across all preparations. That elevates review from single-preparation safety to systems-level oversight.

Complexity guidance is another strength. It reintroduces simple, moderate, and complex preparation definitions from NAPRA (historically rooted in earlier USP <795> framing), and reframes complexity as operational infrastructure, not just formulation difficulty.

Finally, the hierarchy of controls is emphasized clearly: PPE is the least effective control. The Guide pushes supervisors to prioritize elimination, substitution, engineering controls, and administrative safeguards before defaulting to more PPE.

Practicalizing this at the pharmacy level

This is where implementation pressure shows up. The requirements are clear that different strengths of the same preparation require separate risk assessments. Same ingredient, same hazard profile, same room. Change the strength, and you still start a new document.

I understand the logic. Exposure intensity can change. But in daily operations, scale multiplies quickly. Three strengths of one formulation can mean three near-identical assessments to maintain.

Then there is repeated documentation. Across dozens of preparations, teams repeatedly write the same ventilation controls, PPE rationale, and environmental safeguards. The thinking is essential, but the duplication load is heavy.

Add the 12-month review expectation for each record, and governance work becomes an ongoing logistics operation: tracking cycles, updating SDS references, managing revisions, archiving history, and collecting signatures.

The part we do not talk about

The template itself is strong. The real issue is behavior under volume. When supervisors are balancing cumulative exposure tracking, MFR updates, environmental logs, staff training, and quality control, the mindset can shift from reasoning quality to checklist completion.

That is human. And that is the operational risk: governance that looks complete but loses clarity under documentation pressure.

How I am handling this

When I read the template and Companion Guide, my reaction was not frustration. It was: this logic is good, but the format needs evolution.

Inside Compounded (my digital compliance system), I restructured risk assessments so the same governance logic stays rigorous while repetitive work is reduced.

• Ingredient hazards are stored once and reused across relevant system components.
• Completing a Master Formulation Record auto-triggers a Risk Assessment Record with key fields pre-populated for review.
• NIOSH and hazardous status tags are applied automatically on chemicals.
• PPE recommendations populate based on hazard profile and SOP logic.
• Cumulative risk dashboards are being built to rationalize risk levels facility-wide.
• 12-month reminders trigger automatically.
• Version history is clean and auditable without paper stacks.

The thinking stays rigorous. The repetition drops. And handoff from one supervisor to the next becomes more reliable.

Final thought

The new OCP template reinforces demonstrable reasoning, supervisor accountability, structured hazard analysis, and ongoing review. Those are appropriate expectations.

But governance has to be executable. If documentation becomes so heavy that it crowds out clarity, we improve the form but not the function.

If you want to streamline documentation and governance in your compounding pharmacy, reach out to learn more about Compounded.