Factory Acceptance Testing Versus Site Acceptance Testing

ICH regulatory guidelines pharmaceutical quality illustration

Factory Acceptance Testing Versus Site Acceptance Testing is an important element of pharmaceutical quality systems. Factory testing does not replace verification under installed conditions. This article explains the objective, key evidence and a practical approach to review. It is a general guide, not a replacement for a site-approved procedure.

Illustration of Factory Acceptance Testing Versus Site Acceptance Testing in a pharmaceutical quality system

Purpose and risk-based context

The objective is to provide documented evidence that the relevant system, process or control is suitable for its intended use. This requires a clear scope, appropriate scientific rationale, defined responsibilities and traceable data. Controls should be proportionate to potential effects on patient safety, product quality and record integrity.

Implementation strategy

Identify what can be tested at the vendor and what must be repeated or supplemented on site. Establish requirements and acceptance criteria before performing formal work. Distinguish design assumptions from tested facts and document how exceptions are assessed. Where a supplier provides evidence, evaluate its relevance and reliability instead of assuming it replaces local verification.

  1. Define intended use, system boundaries and critical functions or process attributes.
  2. Assess quality risks and select controls and tests with a documented rationale.
  3. Confirm approved protocols, trained personnel, configuration and prerequisites.
  4. Execute testing or review, retaining contemporaneous raw evidence and metadata.
  5. Investigate discrepancies, evaluate impact and repeat only justified tests.
  6. Approve conclusions and establish ongoing monitoring, change control and periodic review.

Illustrative pharmaceutical example

Consider a critical system introduced into a GMP workflow. During verification, a configuration difference is found between the approved requirement and the installed state. The team should record the discrepancy, assess whether regulated decisions or records could be affected, and determine whether configuration correction, additional testing or formal change control is needed. An unexplained pass result should not replace a documented resolution.

Evidence expected during QA review

Reviewers should be able to trace requirements to tests, results and final decisions. Evidence may include risk assessments, approved protocols, supplier documents, test scripts, raw records, deviation assessments, training and approval history. Retention and access arrangements should support later inspections and investigations.

Common weaknesses

Weaknesses include vague requirements that cannot be tested, missing acceptance criteria, excessive reliance on vendor declarations, undocumented changes and incomplete closure of discrepancies. Another recurring problem is treating qualification or validation as a one-time event while ignoring subsequent changes, maintenance, incidents and system retirement.

Practical checklist

  • Intended use and scope are approved
  • Critical risks and requirements are documented
  • Evidence is complete, attributable and retrievable
  • Discrepancies are investigated and resolved
  • Review and approval responsibilities are clear
  • Lifecycle controls and reassessment triggers are defined

FAQ

Is a vendor certificate sufficient?

Not automatically. Its adequacy depends on supplier qualification, the system’s intended use, applicable risks and whether the evidence addresses the actual installed or configured state.

When is requalification or revalidation required?

Use documented change impact assessment and periodic review to determine whether a modification, failure or new use requires additional verification.

Related articles and regulatory resources

See the Validation Master Plan guide, Process Validation SOP and Installation Qualification: Utilities, Materials and Documentation. For primary regulatory context review EU GMP Volume 4.

Leave a Comment

Your email address will not be published. Required fields are marked *