GxP Assessment Form
Frequently Asked Questions

A GxP assessment form is a controlled document that evaluates whether a system, application, or piece of equipment has a direct or indirect impact on product quality, patient safety, or data integrity — and therefore requires formal validation or qualification.

It is the gateway document that prevents two failure modes: validating systems that do not need it (wasting resources) and failing to validate systems that do (creating compliance gaps). Every system entering a GxP environment should pass through a completed, approved assessment before a validation approach is assigned.

The terms are used interchangeably in most quality systems — both refer to the same structured evaluation that classifies a system as direct impact, indirect impact, or no GxP impact.

Some organisations use "GxP assessment" for the initial screening evaluation and "impact assessment" for the more detailed follow-on analysis that specifies which functions within a confirmed GxP system require formal testing. Where both exist as separate documents, the assessment form should explicitly reference its relationship to the deeper impact analysis.

EU GMP Annex 11 Clause 4 requires that validation efforts and resources be commensurate with risk — which presupposes a documented, risk-based evaluation determining what level of validation each system needs.

FDA does not prescribe a specific "GxP assessment form" by that name, but its data integrity guidance and computer software assurance guidance both require that organisations determine a system's GxP relevance before deciding on validation scope. GAMP 5 formalises this as the "Impact Assessment" step that precedes category assignment.

A GxP assessment must be completed before the system is procured or developed, so that the classification drives the purchase specification, vendor selection, and contract terms rather than being retrofitted after the decision is made.

In practice, completing the assessment after procurement is a common finding. A system purchased without a GxP assessment may have been selected without audit trail capability, without validation documentation from the vendor, or without the contractual right to conduct a supplier audit — all of which are difficult to remediate after contract signature.

The system owner or project lead completes the assessment using their knowledge of the system's intended use; Quality Assurance reviews and approves it to confirm the classification is appropriate and consistent with site-level GxP criteria.

IT involvement is valuable for understanding technical architecture and data flows. Regulatory Affairs input may be needed for systems that interact with submission data. QA's approval is non-negotiable — the assessment is a controlled GMP document, and QA's signature confirms the compliance decision rather than just the factual description of the system.

A direct-impact system directly controls, monitors, or generates data used in product quality decisions or regulatory submissions. An indirect-impact system supports a direct-impact system without itself touching product or GxP records. A no-impact system has no connection to product quality, patient safety, or data integrity.

• Direct impact examples: LIMS, batch management system, electronic batch record, process historian, MES, QMS for quality events.
• Indirect impact examples: building management system monitoring (not controlling) temperature, IT monitoring tools alerting on GxP server availability, backup infrastructure.
• No impact examples: HR systems, general office productivity tools, internal scheduling tools with no product quality data.

The assessment should work through a structured decision tree covering the system's relationship to product, data, and regulatory obligations.

• Does the system create, modify, store, or transmit data used in batch release, quality decisions, or regulatory submissions?
• Does the system directly control a critical process parameter or quality attribute?
• Does the system generate electronic records that serve as the primary GMP record?
• Does the system interface with a direct-impact system in a way that could affect that system's data integrity?
• Is the system used in GLP, GCP, or GDP activities that affect product safety or regulatory data?
• Does failure of the system create a patient safety or product quality risk that would not be detected before product release?

When a system sits on the boundary between classifications, the decision should be made conservatively — erring toward higher classification when the potential consequence of underclassification (undetected data integrity failure affecting product quality) is more serious than overclassification (unnecessary validation effort).

For the training record example: if the HR system is the system of record for GxP training completion that directly determines whether an operator is authorised to perform a GMP task, it has direct GxP impact and requires validation. If it only holds payroll and leave records while a separate QMS holds training records, it is no-impact. The assessment must document the specific data flow and the classification rationale, not just apply a label.

Every system requires a GxP assessment regardless of vendor size, reputation, or documentation package — because the assessment evaluates how the organisation uses the system, not what the vendor intended it for.

A vendor's qualification documentation addresses the vendor's own use and test environment. It does not assess whether your specific configuration, your data flows, your integration with other systems, and your business process make the system GxP-relevant in your context. A major enterprise system used purely for HR at one site may be a direct-impact GxP system at another site if configured to generate batch records.

GxP impact classification and GAMP 5 category are two separate dimensions that together determine the validation approach — impact classification answers "does this need validation?", while GAMP category answers "how complex and configurable is the software?"

A Category 3 off-the-shelf system with direct GxP impact requires a full validation lifecycle tailored to its configuration, but with less complexity than a Category 5 custom system. A Category 5 system with no GxP impact requires no pharmaceutical validation regardless of its technical complexity. The GxP assessment form should capture both the impact classification and the GAMP category as inputs to the Validation Plan.

An inspection-ready GxP assessment form must contain enough information to explain the classification decision to someone with no prior knowledge of the system — the assessor's conclusion alone without supporting reasoning is not sufficient.

• System name, version, vendor, and intended business use in plain language.
• Description of the data the system creates, processes, or stores and how it connects to product quality or patient safety.
• Explicit answer to each impact classification criterion with brief rationale.
• Final GxP impact classification: direct, indirect, or no impact — with a clear conclusion statement.
• GAMP 5 software category with rationale.
• Reference to the resulting validation approach (Validation Plan or equivalent) for direct and indirect impact systems.
• Signature blocks for author, technical reviewer, and QA approver with dates.

A no-impact classification still requires a controlled, signed document — because the classification is itself a compliance decision that an inspector may question, and an undocumented "no impact" determination cannot be defended.

The no-impact assessment can be brief: two to three paragraphs explaining the system's function, why it has no connection to product quality or GxP data, and who approved the decision. The document should be retained in the GxP inventory entry for that system so that if the system's use later changes, the original baseline classification is on record.

The GxP assessment determines whether a system needs validation and at what level. The Functional Risk Assessment operates within an already-confirmed GxP system and determines which individual functions require formal testing and to what depth.

The assessment form comes first and is completed once per system entry. The FRA comes second and is completed as part of the active validation project. A strong GxP assessment feeds the FRA by identifying which aspects of the system's intended use are most critical — the FRA then translates that criticality into test protocol scope.

The GxP assessment form is the source document that creates the system's entry in the GxP inventory — the classification it establishes determines the inventory fields for impact level, GAMP category, and required validation approach.

Without the assessment form, the inventory entry has no documented basis for its classification. Without the inventory entry, the assessment form sits in a project file without being visible as part of the site's overall compliance posture. Both must exist and reference each other: the inventory entry should cite the assessment form document ID, and the assessment form should note where it will be filed.

A GxP assessment form is a controlled GMP record and must be retained for at least the operational life of the system plus the applicable regulatory retention period — typically a minimum of five years after the system is retired in EU GMP and FDA cGMP environments.

Retaining the assessment form after system retirement matters because it provides evidence that the organisation had a compliant basis for the validation decisions made during the system's operational life. If a regulatory inspection reviews historical batch data processed by a retired system, the assessor needs to confirm that the system was appropriately classified and validated at the time the data was produced.

A new GxP assessment is not required for every change — but any change that materially alters how the system is used, what data it processes, or how it interacts with other GxP systems should trigger a reassessment of whether the original classification remains valid.

• Adding a new module that creates GxP records where none existed before — reassessment required.
• Expanding use to a new manufacturing site with different regulatory scope — reassessment required.
• Integrating the system with a direct-impact GxP system for data exchange — reassessment required.
• Updating software version within the same functional scope — change control assessment, not a new GxP assessment.
• Changing the number of user accounts — no reassessment needed.

A misclassified system found to be processing GxP data without validation is a compliance deviation and must be formally raised, investigated, and remediated — it cannot be silently corrected by issuing a new assessment form.

The deviation investigation should determine: how long the system has been in GxP use without validation, what data has been produced during this period, and whether that data's integrity can be assured through alternative means such as source data comparison or parallel process verification. A remediation plan is then developed to validate the system retrospectively and assess whether any GxP records produced during the unvalidated period need to be flagged or reviewed.

Yes — a system's classification can escalate (no impact to indirect, indirect to direct) or de-escalate over time as the system's use or the regulatory environment changes, and each direction has different implications for the validation package.

Escalation requires additional validation work: a system reclassified from indirect to direct impact may need additional qualification testing, a more rigorous data integrity assessment, and enhanced audit trail controls. De-escalation does not eliminate existing validation documentation but may reduce the scope of future periodic reviews. Both changes require a formal reassessment form, a change control record, and an update to the GxP inventory entry.

Inspectors test two things: whether every system in active GxP use has an assessment form, and whether the rationale in the form is genuinely system-specific rather than a generic template answer.

A common finding is an assessment form where every question is answered identically across different systems — suggesting the form was completed without genuine analysis. Inspectors will pick two or three systems and compare their assessment rationales: if a LIMS and an HR system have identical reasoning, the assessment process lacks credibility. They also check whether systems discovered during the facility walk-through appear in the assessment register at all.

A structured decision tree produces more consistent, defensible classifications than a free-text form — because it forces every assessor through the same questions rather than allowing the quality of the assessment to depend on the individual author's knowledge.

Best practice combines both: a decision tree that guides the assessor through classification criteria with yes/no questions and auto-scored outcomes, followed by a required narrative section explaining the specific rationale for the system being assessed. The tree ensures completeness; the narrative ensures the reasoning is system-specific rather than a pattern of answers that looks the same for every system.

A digital platform enforces the assessment workflow — requiring completion of all fields, routing for QA approval with an audit trail, and automatically creating the GxP inventory entry from the assessment data — eliminating the manual linkage gaps that paper or Word-based forms routinely produce.

The practical compliance improvement is in consistency and traceability: every system in the inventory has a traceable, approved assessment form as its source document, the classification is locked after approval and cannot drift silently, and the platform surfaces systems that need reassessment when triggered by a change or a periodic review finding. This is the difference between a compliance programme and a compliance filing exercise.