Loading...
compliance

USP 795 Compounding Record and Beyond-Use Dating

A USP 795 Compounding Record and Beyond-Use Dating template for documenting nonsterile compounding, ingredient traceability, water activity, and the assigned beyond-use date in one reviewable record.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Pharmacy · Compounding Pharmacy · Healthcare

Overview

This template documents one nonsterile compounding event from prescription reference through final release, with a dedicated section for water activity and beyond-use dating. It is built for pharmacies that need a clear record of what was compounded, which ingredients were used, what process was followed, and why the assigned BUD was chosen.

Use it when you need a repeatable record for USP 795-aligned compounding, especially for preparations where water activity affects stability or storage decisions. The structure supports traceability: record identification, formulation basis, ingredient details, compounding steps, in-process checks, and reviewer certification all stay in one place. That makes it easier to answer internal quality questions and to reconstruct the event later if a complaint, discrepancy, or audit comes up.

Do not use this template as a generic dispensing log or for sterile compounding workflows. It is also not the right fit when you do not need a formal BUD rationale or when the preparation is so simple that your SOP uses a different record type. If you collect patient identifiers, keep the field limited to what you actually need and avoid unnecessary PII. The form works best when required fields are clearly marked, conditional logic hides irrelevant prompts, and the final review confirms that the release status matches the documented evidence.

Standards & compliance context

  • This template supports USP 795 documentation by capturing the formulation basis, compounding process, and BUD rationale in a single record.
  • The form should follow data minimization principles by collecting only the patient and prescription details needed for the compounding event.
  • If the record is used in a public-facing or shared workflow, fields should meet WCAG 2.1 AA expectations with clear labels, validation, and keyboard-friendly controls.
  • For health-related records, keep the minimum-necessary principle in mind and avoid collecting sensitive information that is not needed for the preparation or release decision.
  • If your workflow includes electronic signatures or audit trails, preserve who completed, reviewed, and released the record so the approval path is traceable.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Record Identification

This section anchors the event so the compounding record can be matched to the prescription, date, time, and patient or internal reference.

  • Record Number

    System-generated unique identifier for this compounding record.

  • Compounding Date (required)

    Date the nonsterile compounding event was performed.

  • Compounding Time (required)

    Time the compounding event started or was completed.

  • Compounding Type (required)

    Select the dosage form being prepared.

  • Prescription or Order Reference (required)

    Internal prescription, order, or batch reference used for traceability.

  • Patient Identifier

    Use the minimum necessary patient identifier required by your workflow. Avoid collecting full PII unless needed.

Formulation and Basis

This section explains what was compounded and why, which is essential for traceability and for defending the formulation choice during review.

  • Formulation Name (required)

    Name of the compounded preparation.

  • Basis for Compounding (required)

    Select the basis used to prepare the compound.

  • Reference Sources

    List any references consulted during compounding.

  • Intended Route of Administration (required)

    Select the intended route for the nonsterile preparation.

  • Special Handling Notes

    Document any handling precautions, storage constraints, or formulation-specific considerations.

Ingredients and Traceability

This section captures the materials used and any lot or source notes needed to reconstruct the batch later.

  • Ingredients (required)

    Enter each ingredient used in the compound, including lot traceability and quantity.

  • Ingredient Notes

    Document substitutions, reconstitution details, or any ingredient-specific observations.

Compounding Procedure

This section documents the actual preparation steps, equipment, deviations, and checks so the process is reproducible and auditable.

  • Equipment Used (required)

    Select the equipment used during compounding.

  • Compounding Steps (required)

    Describe the compounding steps performed in sequence, including any critical manipulations.

  • Deviations or Variances

    Document any deviations from the master formulation record, procedure, or expected process.

  • In-Process Checks

    Select any in-process quality checks performed.

Water Activity and Beyond-Use Dating

This section records the evidence behind the assigned BUD, including whether water activity was measured and how the date was determined.

  • Was Water Activity Measured? (required)

    Indicate whether a water activity measurement was performed for this preparation.

  • Water Activity Value

    Enter the measured water activity value if available.

  • Water Activity Method

    Document the instrument or method used to determine water activity.

  • Beyond-Use Date Basis (required)

    Select the rule used to assign the beyond-use date.

  • Assigned Beyond-Use Date (required)

    Date after which the compounded preparation should not be used.

  • BUD Rationale (required)

    Explain how the beyond-use date was determined, including any water activity threshold or policy basis used.

Review, Release, and Certification

This section confirms that a qualified reviewer verified the record and approved release only after the documentation was complete.

  • Final Quality Review Completed (required)

    Confirm that the final preparation was reviewed before release.

  • Release Status (required)

    Select the disposition of the compounded preparation.

  • Reviewer Name (required)

    Name of the person performing the final review.

  • Reviewer Signature (required)

    Electronic signature of the responsible reviewer.

  • Review Date (required)

    Date the record was reviewed and approved.

How to use this template

  1. Enter the record identification details first, including the compounding date, time, type, prescription reference, and only the patient identifier your workflow requires.
  2. Document the formulation name, basis, reference sources, intended route, and any special handling notes so the reviewer can see why this preparation was made.
  3. List each ingredient with traceability notes, then record the equipment used, the compounding steps, any deviations, and the in-process checks performed.
  4. Complete the water activity section by noting whether a measurement was taken, the value, the method, the BUD basis, and the rationale for the assigned beyond-use date.
  5. Perform the final quality review, set the release status, and capture the reviewer name, signature, and review date before archiving the record.
  6. If anything is incomplete or inconsistent, return the form for correction and do not release the preparation until the record supports the assigned BUD.

Best practices

  • Mark required fields clearly and use conditional logic so users only see water activity prompts when they apply.
  • Use a date picker for compounding date and review date, and use numeric input for water activity values instead of free text.
  • Record the formulation basis and reference sources exactly as used so the BUD rationale can be traced back to the source material.
  • Capture ingredient lot numbers or other traceability details in the ingredient notes when your SOP requires them.
  • Document deviations and in-process checks at the time they occur, not after the batch is finished.
  • Keep patient identifiers to the minimum necessary for the workflow and avoid collecting extra PII that is not needed for compounding.
  • Require a final quality review before release so the assigned BUD is not separated from the evidence that supports it.

What this template typically catches

Issues teams running this template most often surface in practice:

The formulation basis is missing or too vague to explain why the preparation was compounded.
Ingredient entries do not include enough traceability to match the actual materials used.
The assigned BUD is entered without a documented rationale or water activity basis.
Deviations from the intended procedure are not recorded, which leaves the batch history incomplete.
In-process checks are skipped or written after the fact instead of during the compounding event.
The final review is signed before the record is complete, creating a release gap.
Patient or prescription details are over-collected when the workflow only needs a limited identifier.

Common use cases

Community Pharmacy Oral Liquid Record
A community pharmacist compounds an oral liquid from a prescription and uses the template to document the formulation basis, ingredient traceability, and the assigned BUD. The record helps the team confirm storage and release decisions later.
Hospital Outpatient Cream Preparation
A hospital outpatient pharmacy prepares a topical cream and needs a clean audit trail for the ingredients, equipment, and in-process checks. The water activity section supports the BUD decision when the formulation includes moisture-sensitive components.
Independent Pharmacy Capsule Batch
An independent pharmacy compounds a small capsule batch with a defined formula and wants a consistent record for each event. The template captures deviations, reviewer approval, and the final release status in one place.
Compounding QA Review Workflow
A quality reviewer uses the form to verify that the compounding steps, source references, and BUD rationale match the pharmacy’s SOP. The structured fields make it easier to spot missing documentation before release.

Frequently asked questions

What is this template used for?

This template records a single nonsterile compounding event and the basis for the assigned beyond-use date. It captures the formulation, ingredients, procedure, water activity data, and final release review in one place. Use it when you need a repeatable record that supports USP 795 documentation and internal quality review.

When should a pharmacist use this form?

Use it for each compounded preparation that needs a documented record and a beyond-use date assignment. It is especially useful when the formulation includes water activity considerations or when the compounding process needs traceability for later review. It is not a general patient intake form and should not be used for dispensing without compounding.

Who should complete and sign the record?

The compounding pharmacist or designated compounder should complete the preparation details, and a qualified reviewer should perform the final quality review and release. The reviewer should confirm the formulation basis, ingredient traceability, procedure notes, and the BUD rationale before signing. If your workflow separates preparation and release, keep both roles visible in the record.

Does this template replace USP 795 requirements?

No. It is a documentation template that helps you capture the information needed for a USP 795-aligned record, but it does not replace your organization’s SOPs, stability data, or professional judgment. You still need to follow your pharmacy’s policies for formulation selection, sanitation, labeling, storage, and release.

How does the water activity section affect the beyond-use date?

The water activity section records whether a measurement was taken, the value, the method used, and the basis for the assigned BUD. That makes the date assignment traceable instead of relying on memory or a free-text note. If water activity was not measured, the form still prompts you to document the alternative basis used for the BUD.

What are the most common mistakes when using this template?

Common mistakes include leaving out the formulation basis, using vague ingredient descriptions, and assigning a BUD without documenting the rationale. Another frequent issue is skipping in-process checks or failing to note deviations from the intended procedure. Those gaps make the record harder to defend during review or audit.

Can this template be customized for different dosage forms?

Yes. You can adapt the fields for creams, suspensions, capsules, oral liquids, or other nonsterile preparations while keeping the same core structure. If a dosage form needs additional checks, add conditional fields rather than overloading every record with irrelevant questions. That keeps the form usable and aligned with data minimization.

How should this template fit into a pharmacy system or workflow?

It can be used as a standalone record, attached to a prescription workflow, or linked to inventory and quality review systems. The key is preserving traceability from prescription reference to ingredients, procedure, and final release. If you integrate it with other systems, make sure the audit trail shows who entered or approved each section.

What should happen after the form is submitted?

After submission, the record should move to quality review, release approval, and archival according to your SOP. The reviewer should confirm that the assigned BUD matches the documented basis and that any deviations were assessed before release. If the record is incomplete, it should be returned for correction rather than released.

Go deeper on the topic

Related concepts
  • Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
  • AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
Related guides

Ready to use this template?

Get started with MangoApps and use USP 795 Compounding Record and Beyond-Use Dating with your team — pricing built for small business.

Get Started