PIC/S Annex 1 Alignment: Sterile Manufacturing GMP

PIC/S Annex 1 is Annex 1, “Manufacture of sterile medicinal products”, of the PIC/S GMP Guide (PE 009-18) Annexes. For the broader reference, see Annex 1; this article focuses on the PIC/S guide context, the comparison method and evidence-based site alignment.

For this article, alignment means a scoped, documented comparison between relevant Annex 1 guidance and the site’s processes, controls and supporting records, including identified gaps and decisions. This is an operational working definition—not a regulatory definition or a declaration of compliance.

The following terms occupy different places in that comparison. The document rows identify references; the strategy and simulation rows identify site-level work. Their detailed guidance and assessment criteria belong in their dedicated discussions.

A useful review therefore starts with a defined product, process and facility boundary. For each relevant topic, record the reference, the site arrangement, the supporting record and any unresolved gap or decision. This gives reviewers a traceable comparison rather than a checklist of document titles.

PIC/S Annex 1, section 1 and EU GMP Annex 1, section 1 both connect sterile-product manufacturing with Quality Risk Management (QRM). That shared framing provides a starting point for comparing the guidance, not proof that every paragraph, legal obligation or implementation date is interchangeable.

PIC/S itself describes the relationship. The PIC/S GMP Guide Introduction (PE 009-18) says that since 1989 the EU and PIC/S GMP Guides "have been developed in parallel and whenever a change has been made to one, the other has been amended so that both Guides are practically identical." Its revision history records "Revision of Annex 1" in PE 009-17, dated 25 August 2023, and the current edition, PE 009-18, dated 24 September 2026, revised Annex 19 rather than Annex 1.

The same Introduction lists the differences between the two guides. The PIC/S Guide retains the Pharmaceutical Inspection Convention definition of Pharmaceutical Product (called Medicinal Product in the Guide); references to EU Directives and MRAs are deleted; "the expression “authorised person” (see Glossary) is used in the PIC/S Guide while the expression “Qualified Person” is used in the EU Guide"; and mentions of the European Pharmacopoeia read "European or other relevant Pharmacopoeia". For an Annex 1 crosswalk, these differences matter mainly in release and pharmacopoeial references rather than in the technical contamination-control content.

As a document-control practice, compare provisions individually and record the document edition and paragraph used in each assessment. Keep four categories separate: binding local law, official guidance, site practice and software records. A record showing completion of a site check should not substitute for a legal-applicability decision.

Use an applicability register such as the following. PIC/S is a guide context here, not a jurisdiction; each row still needs a defined product, process and market.

For food, supplements, devices and chemicals, begin with product classification and the applicable local framework rather than treating an Annex 1 crosswalk as the legal basis. The sterile/aseptic supplement boundary is a useful classification checkpoint.

Assign the current applicability decision to a competent site reviewer. Record the decision, rationale and review trigger; do not infer authority adoption or effective dates from similarities between guidance texts.

PIC/S Annex 1, section 1 describes sterile product types including active substances, excipients, primary packaging materials and finished dosage forms. The scope is therefore broader than finished medicines alone. For the wider terminology and control framework, see the Annex 1 overview.

Section 1 also identifies potential use of selected principles for certain non-sterile liquids, creams, ointments and low-bioburden biological intermediates where controlling microbial, particulate and endotoxin/pyrogen contamination is important. These are examples of selective application, not a universal requirement for all non-sterile manufacturing. Where a manufacturer elects to apply this guidance, section 1 says the manufacturer "should clearly document which principles have been applied and acknowledge that compliance with those principles should be demonstrated." Selective use therefore still carries an evidence burden for whatever principles the site chooses to adopt.

Section 1 treats specified limits, frequencies or ranges as minimum requirements. This is a statement within the guidance; it should not be read as an optional target for an alignment assessment.

As a practical scoping method, define the assessment boundary before reviewing individual controls: product family, process route, rooms, equipment, utilities, personnel groups and outsourced activities. Name both included operations and exclusions, with reasons. For an aseptic fill line, for example, identify its supporting utilities and personnel groups rather than treating the filling machine as the entire boundary. This makes the assessment’s coverage explicit and avoids implying that unexamined operations have been assessed.

The PIC/S Annex 1 document map organises the guidance into eleven sections. Use the table to locate a topic before assessing individual provisions. The site review column offers practical assessment questions, not additional regulatory requirements.

For a working assessment index, give each finding a primary section reference and cross-reference related topics rather than copying the finding into several lists. For example, a question about a utility connection can be indexed under utilities, with a link to the equipment assessment. This keeps navigation compact while preserving the connection between subjects. Use the glossary to resolve terminology before assigning an action; a shared label helps reviewers discuss the same issue.

The PIC/S Annex 1 glossary, section 11 defines a Contamination Control Strategy (CCS) as a planned set of controls addressing microorganisms, endotoxin/pyrogen and particles, derived from current product and process understanding to assure process performance and product quality. Its examples span facility and equipment operating conditions, in-process controls, finished-product specifications, and monitoring methods and frequency. The CCS therefore connects the rationale for a control strategy with the records used to assess it.

The Annex 1 glossary in the PIC/S annexes defines the Contamination Control Strategy as "A planned set of controls for microorganisms, endotoxin/pyrogen and particles, derived from current product and process understanding that assures process performance and product quality."

Annex 1, section 1 states that quality risk management (QRM) applies throughout the document, even where individual paragraphs do not mention it. In practical site assessment, this means asking why each selected control suits the contamination risk, rather than treating the CCS as a catalogue of procedures.

Build a risk-to-evidence chain

A useful working record follows this chain: process step → contamination hazard → potential entry route → preventive control → verification or monitoring record → responsible owner → unresolved gap. This is a suggested assessment method, not a prescribed Annex 1 template. A document inventory can identify an approved procedure but cannot, by itself, explain which hazard it addresses or whether its assumptions still match operations.

Illustration: material transfer

Assume wrapped materials cross into a cleaner processing area, creating an opportunity for contamination on external surfaces to travel inward. The site selects staged removal of wrapping and a surface-treatment step appropriate to those materials. These are scenario-dependent choices, not universal prescribed designs.

Link the transfer procedure to the qualification or verification record supporting the selected method under its intended conditions. Identify observations that feed review: damaged wrapping, missed treatment steps, handling deviations and relevant monitoring trends. Assign a transfer-process owner and record any unresolved question, such as whether a new packaging material remains covered by the supporting assessment.

Keep the rationale connected

Connect these actions to change control, with review prompted by relevant changes, deviations or evidence that challenges the existing rationale.

Suggested alignment lifecycle: define scope → map hazards → select controls → link evidence → assign owners → resolve gaps → review effectiveness. This seven-step workflow is a proposed site method, not an Annex 1-prescribed sequence.

PIC/S Annex 1, paragraph 2.1(i) says facilities, equipment and processes should be appropriately designed, qualified and/or validated. For a site review, translate that guidance into questions about how the installation protects product throughout its operating sequence—not just whether equipment has a qualification file.

The same paragraph names RABS, isolators, robotic systems, rapid/alternative methods and continuous monitoring systems as technologies to consider. Considering appropriate technology is not the same as declaring that every site must use a particular barrier type. Record the selection rationale alongside the design qualification assessment.

Follow exposure and operating states

As a practical review method, walk an aseptic fill line or other operation in sequence and ask:

• Product exposure: where are product or product-contact surfaces exposed, and what protects them?
• Movement: how do material transfers and personnel routes intersect with exposed operations?
• Equipment states: what changes during setup, stops, restart and maintenance compared with steady production?
• Utility interfaces: where do connections, disconnections or utility interruptions affect the process?
• Interventions: what access is needed for adjustments, and how is protection maintained or restored?

Use an assessment register with four linked fields: operation, risk rationale, selected control and evidence reference. Link relevant operating instructions, personnel qualification records and technical assessments; connect operating-state tests to operational qualification where appropriate. These are suggested review practices, not additional Annex 1 specifications.

For example, assume an operator clears a jam to correct an aseptic process while it is executing. This fits the glossary meaning of a corrective intervention in Annex 1, section 11: an intervention performed to correct or adjust an aseptic process during execution. Assess the access and adjustment, not merely the machine's normal running condition. Keep unresolved questions visible in the register so a satisfactory steady-production assessment does not conceal unassessed setup, maintenance, stops or interventions.

The Annex 1 production section lists terminally sterilised products and aseptic preparation and processing as distinct topics. Its technology-specific navigation also covers filter sterilisation of products that cannot be sterilised in their final container, form-fill-seal, blow-fill-seal, lyophilization, closed systems and single-use systems. For a site review, use these headings to locate relevant guidance, then examine how the operations connect rather than treating each technology as an isolated checklist.

For lyophilization, paragraph 8.121 treats all activities that can affect product or material sterility as extensions of aseptic processing. It also says that all control measures in place should be determined by the site’s contamination control strategy (CCS). This makes the filling-to-lyophilization interface a useful focus for a practical alignment review.

Worked case: a changed loading route

Assume one aseptic filling line, one lyophilizer and one proposed loading-route change. These are equipment and change counts, not regulatory limits. As a practical assessment method, trace the proposed route from filling through transfer and loading to completion of lyophilization:

1. Mark exposure points at filling discharge, transfer, staging and loading; distinguish unchanged points from those introduced or altered by the route.
2. Record equipment states at each handoff, including the status of transfer equipment and the receiving lyophilizer. Identify interventions and who performs them.
3. Map each affected point to its CCS control reference and relevant procedure or equipment record. Flag assumptions that need assessment rather than treating them as established controls.
4. Link the route drawing, risk assessment, affected instructions and assessment decisions to the same change identifier. Use consistent production context tagging to keep the equipment and operation references unambiguous.

The result is a bounded change-assessment package, not a claimed validation outcome. The specific failure mode is retaining a technology checklist while overlooking a changed handoff between two operations. An end-to-end process walk-through, with affected records linked to the same change identifier, addresses that gap.

As the structural map above shows, premises qualification belongs in section 4; section 9 addresses ongoing routine environmental and process monitoring. Keep qualification records separate from routine observations, even when both concern the same room or equipment.

Section 9 has separate headings for total-particle monitoring and viable environmental and personnel monitoring. Use non-viable particle count for measurement terminology. Its aseptic process simulation (APS) topic is also called media fill; see media fill and aseptic process simulation for the specialist explanation. These are distinct review topics, not interchangeable labels for one dataset.

The following is a practical review matrix, not an additional Annex 1 requirement. For each record family, retain location, method, time, operating state, batch or campaign, and control reference where applicable. Consistent production context tagging helps reviewers connect records without erasing their different purposes. QC remains within the structural scope described above.

An isolated result can obscure what was happening when the observation was made. For example, a reviewer examining an environmental result checks the associated equipment state, intervention log and sampling context before documenting an assessment. The reviewer records which events overlap the sampling interval and which connections remain uncertain. A nearby event is a review lead, not proof of causation. This scenario implies no product-quality outcome and does not replace applicable investigation procedures or acceptance criteria.

Use a system-neutral crosswalk to connect applicability decisions, controls, evidence, process events and assessments. The identifiers, versions and relationships below are a practical review model—not a prescribed Annex 1 database schema or a claim about software capabilities.

An illustrative relationship model

Provision reference → applicability decision → control ID/version → evidence reference → source record ID/version Process event ID → evidence reference → assessment ID, reviewer, date and decision

The source record contains the observation, result or activity history; the crosswalk reference locates it rather than replacing it. Let reviewers follow these links to the current record and associated assessment, while retaining which version was assessed. Use event identifiers to connect evidence to the relevant batch, equipment operation or sampling slot.

Interface reconciliation

For laboratory, quality, maintenance and historian interfaces, define source identifiers, event and receipt timestamps, units where applicable, record versions and reconciliation status. Handle exceptions separately:

• Missing: identify expected records and reconcile gaps against the source.
• Repeated: retain duplicate-message history without counting another observation.
• Corrected: link the replacement version to its predecessor and correction reason.
• Late-arriving: preserve event and receipt times; reassess completeness when the record arrives.

Preserve the reason, reviewer and time for each reconciliation decision in the audit trail.

Worked case: messages are not unique records

Assume six monitoring locations, twelve scheduled observation slots per location and one expected record per location-slot pair. Expected records = 6 × 12 = 72. The interface receives 71 messages: 68 unique expected records and 3 duplicate messages. Missing expected records = 72 − 68 = 4. Recovering those four records produces 75 received messages and 72 unique expected records. These counts describe records and messages, not microbiological or particle measurements.

Record the completeness assessment separately from scientific assessment of the measurements. A complete dataset does not establish acceptable product quality; authorised people retain assessment and release decisions.

Use the earlier scope, CCS and evidence explanations to assemble a site review package. The checklist below is a suggested implementation method, not an additional set of Annex 1 requirements or a compliance certificate.

Check the assessment package

• Define the product-market scope, including the operations covered by the assessment.
• Identify current document references and versions; retain a reviewed applicability map with reasons for exclusions.
• Maintain a provision-to-control crosswalk with named control owners and accessible supporting records.
• Include technology-specific records and link relevant external-provider records to the controls they support.
• Document reconciled data exceptions, retaining the original issue, reconciliation evidence and review outcome.
• Record decisions on open gaps, including unresolved questions, interim arrangements and the basis for the chosen action.

Triage gaps before assigning actions

Prioritise through the site's assessment of product exposure, control weakness and uncertainty. Distinguish an evidence-location problem from an absent control or an unresolved technical question: finding a report, establishing a control and commissioning a technical assessment require different responses. Do not substitute invented risk-score cutoffs, universal remediation deadlines or a percentage labelled “regulatory compliance” for that judgement.

Assign each action an owner, a justified target date, required closure evidence and a reviewer. Review whether the completed action adequately addresses the problem separately from whether its administrative task is marked complete.

Keep the assessment current

Suggested reassessment triggers include process or facility changes, new product-market combinations, revised guidance, material monitoring trends, significant incidents and changes in outsourced work. Connect these triggers to change control and relevant review processes rather than inventing a regulatory review calendar.

When evaluating software, ask how it would support record linking, version handling, access controls, review routing and exception visibility, including the site's audit trail review workflow. These are evaluation requirements, not verified product features. Keep approvals and release decisions with authorised people: a completed crosswalk or software status is not the decision itself.