ALCOA+ Explained
ALCOA+ is frequently cited during GMP inspections but rarely explained clearly. Inspectors do not assess whether an organization can define ALCOA+. They assess whether records and data reflect its principles in practice.
ALCOA+ is not a regulation by itself. It is a widely accepted framework used by regulators to evaluate whether data can be trusted. During inspections, it becomes a lens through which documentation, audit trails, and records are examined.
This article explains each ALCOA+ principle using realistic GMP examples and shows how inspectors interpret failures when reviewing records.
What ALCOA+ Actually Represents
ALCOA stands for:
Attributable
Legible
Contemporaneous
Original
Accurate
The “+” commonly includes:
Complete
Consistent
Enduring
Available
These principles align with regulatory expectations for data reliability, traceability, and reconstructability. Inspectors use them to assess whether records reflect what actually occurred.
The broader regulatory context is discussed in GMP Documentation & Data Integrity.
Attributable - Who Performed the Action?
Data must clearly identify who performed an action and, where applicable, who reviewed or approved it.
Example - Compliant:
A laboratory analyst signs and dates a test result. Reviewer signature and date are clearly recorded. Electronic systems record user ID and timestamp.
Example - Inspection Concern:
Entries appear in handwriting that cannot be matched to a defined individual, or shared login credentials are used in an electronic system.
Inspectors interpret unclear attribution as a breakdown in accountability, not just a documentation issue.
Legible - Can the Record Be Read and Understood?
Records must be readable and interpretable over time.
Example - Compliant:
Entries are clear, corrections are readable, and abbreviations are defined in SOPs.
Example - Inspection Concern:
Illegible handwriting, unclear units of measure, or unexplained shorthand requiring verbal clarification.
If inspectors cannot understand the record independently, they question whether it can serve as reliable evidence.
Contemporaneous - Was It Recorded at the Time of Activity?
Data should be recorded at the time the activity is performed.
Example - Compliant:
Manufacturing operators record in-process parameters during production, not afterward.
Example - Inspection Concern:
Multiple entries appear completed at once, or timestamps indicate data entry significantly later than execution.
Inspectors treat back-filled records as potential data integrity risks because they undermine confidence in timing accuracy.
Original - Is This the First Capture of the Data?
Original data refers to the first capture or a verified true copy.
Example - Compliant:
Electronic raw data is preserved in its native format, and paper records are maintained without replacement.
Example - Inspection Concern:
Only transcribed summaries are retained, and original worksheets cannot be produced.
When original data is unavailable without justification, inspectors question the integrity of derived conclusions.
Accurate - Does the Data Reflect What Actually Occurred?
Accuracy requires that records reflect true observations without alteration.
Example - Compliant:
Corrections are made with single-line strike-through, explanation, signature, and date.
Example - Inspection Concern:
Data overwritten, erased, or corrected without explanation.
Improper correction practices often escalate quickly during inspections.
Complete - Is All Relevant Data Retained?
Complete means no unexplained omissions.
Example - Compliant:
All required process steps are recorded, including deviations and rework.
Example - Inspection Concern:
Missing logbook pages, deleted electronic records, or selective retention of favorable results.
Inspectors view selective omission as a systemic control failure.
Consistent - Is the Data Chronological and Logical?
Data should follow a logical sequence without gaps.
Example - Compliant:
Batch records reflect sequential operations with consistent timestamps.
Example - Inspection Concern:
Time gaps without explanation, inconsistent sequence of approvals, or mismatched dates.
Inconsistency often leads inspectors to expand their review.
Enduring - Is the Record Preserved Over Time?
Records must remain durable and protected from deterioration.
Example - Compliant:
Controlled archival practices preserve both paper and electronic records.
Example - Inspection Concern:
Faded thermal printouts or unsupported electronic formats.
Lifecycle governance is addressed in Document Lifecycle: Creation to Archival.
Available - Can the Data Be Retrieved When Needed?
Data must be retrievable and explainable during inspections.
Example - Compliant:
Requested records are retrieved consistently and presented with context.
Example - Inspection Concern:
Difficulty locating records, reliance on personal knowledge, or inconsistent retrieval.
Retrieval expectations are discussed further in Documentation Retrieval Protocols.
How Inspectors Use ALCOA+ in Practice
Inspectors do not conduct an “ALCOA+ audit”. Instead, they:
Review records
Identify anomalies
Use ALCOA+ principles to evaluate reliability
ALCOA+ becomes visible when something appears inconsistent, incomplete, or unexplained.
If records withstand review under these principles, inspectors gain confidence. If multiple ALCOA+ elements fail simultaneously, concerns escalate from isolated documentation errors to broader data integrity findings.
Audit trail evaluation is addressed in Audit Trails in GMP.
Regulatory Perspective
ALCOA+ is not a checklist to memorize. It is a framework inspectors use to assess whether data can be trusted.
Organizations do not demonstrate compliance by citing ALCOA+. They demonstrate it by producing records that are attributable, legible, recorded at the time of activity, preserved in original form, accurate, complete, consistent, enduring, and retrievable. When these attributes are visible in daily operations, inspections proceed efficiently. When they are absent, data integrity becomes the central focus.
