ALCOA+ Explained

Pharmaceutical quality systems depend on decisions made from recorded information.

Before regulators evaluate a GMP record, they first evaluate whether the underlying data can be trusted.

ALCOA+ provides the principles used to assess that trust.

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, ALCOA+ becomes a practical lens for evaluating documentation, audit trails, laboratory records, batch records, and electronic data.

This article explains each ALCOA+ principle using realistic GMP examples, clarifies how ALCOA+ differs from Good Documentation Practices (GDP), and shows how inspectors interpret weak data behaviors during record review.

What ALCOA+ Actually Represents

ALCOA stands for:

• Attributable

• Legible

• Contemporaneous

• Original

• Accurate

The “+” commonly includes:

• Complete

• Consistent

• Enduring

• Available

Together, these principles describe the characteristics of reliable GMP data. They help determine whether records are trustworthy, traceable, and reconstructable.

The broader regulatory context is discussed in GMP Documentation & Data Integrity.

ALCOA+ Is Not the Same as Good Documentation Practices

ALCOA+ and GDP are closely related, but they are not the same.

ALCOA+ describes the characteristics that make data reliable.

GDP describe the behaviors and controls used to create, correct, review, and maintain records that demonstrate those characteristics.

In practice:

• ALCOA+ defines what trustworthy data looks like.

• GDP define how records should be created and maintained to support trustworthy data.

Inspectors often evaluate both together. A record may appear complete, but if it is not attributable, contemporaneous, or original, its reliability may still be questioned.

Attributable - Who Performed the Action?

Data must clearly identify who performed an action and, where applicable, who reviewed or approved it.

Compliant example:

A laboratory analyst signs and dates a test result. Reviewer signature and date are clearly recorded. Electronic systems record user ID and timestamp.

Inspection concern:

Entries appear in handwriting that cannot be matched to a defined individual, or shared login credentials are used in an electronic system.

Attribution establishes accountability. It helps inspectors determine whether the record accurately represents the work performed.

Legible - Can the Record Be Read and Understood?

Records must be readable and understandable without requiring verbal explanation from the person who created them.

Compliant example:

Entries are clear, corrections remain readable, and abbreviations are defined in approved procedures.

Inspection concern:

Illegible handwriting, unclear units of measure, or entries that require someone to explain what was meant.

Legibility is not only about handwriting. A record must be interpretable over time by reviewers, investigators, auditors, and inspectors. If the record cannot be understood independently, it becomes less reliable as evidence.

Contemporaneous - Was It Recorded at the Time of Activity?

Data should be recorded when the activity is performed.

Compliant example:

Manufacturing operators record in-process parameters during production as each activity occurs.

Inspection concern:

Multiple entries appear completed at once, or timestamps suggest that data was entered significantly after the work was performed.

Delayed recording increases reliance on memory rather than direct observation. Even if the values are accurate, inspectors may question whether the record reflects what occurred at the time of activity.

Contemporaneous recording is especially important in batch records, laboratory worksheets, environmental monitoring records, and logbooks where sequence and timing matter.

Original - Is This the First Capture of the Data?

Original data refers to the first capture of information or a verified true copy.

Compliant example:

Electronic raw data is preserved in its native format. Paper records are retained without replacement. Scanned copies are controlled and verified where used as true copies.

Inspection concern:

Only transcribed summaries are retained, while original worksheets, instrument printouts, or electronic raw data cannot be produced.

When original data is unavailable without justification, inspectors may question whether the reported results can be reconstructed and verified.

Originality is especially important when data moves between formats, such as from paper to electronic systems, or from instruments into spreadsheets or reports.

Accurate - Does the Data Reflect What Actually Occurred?

Accuracy means that records reflect true observations and are not altered, rounded, selectively reported, or corrected without control.

Compliant example:

An incorrect entry is corrected using a single-line strike-through, the original entry remains visible, and the correction is signed, dated, and explained.

Inspection concern:

Data overwritten, erased, backfilled, selectively excluded, or corrected without explanation.

Accuracy depends on both the value recorded and the integrity of the correction process. Errors can occur in GMP documentation. What matters is whether the correction remains transparent and traceable.

Correction practices are discussed further in Redlining, Corrections & Audit Trails.

Complete - Is All Relevant Data Retained?

Complete data includes all required and relevant information, not only favorable or passing results.

Compliant example:

All required process steps are recorded, including deviations, rework, repeat testing, and failed attempts where applicable.

Inspection concern:

Missing logbook pages, deleted electronic records, unexplained gaps, incomplete worksheets, or selective retention of favorable results.

Completeness allows reviewers to understand the full sequence of events. Incomplete records can make records weaker because the factual basis is missing or fragmented.

Inspectors often view selective omission as a system-level concern rather than a simple documentation error.

Consistent - Is the Data Chronological and Logical?

Data should follow a logical sequence and remain consistent across related records.

Compliant example:

Batch records reflect sequential operations with timestamps that align with equipment logs, laboratory results, and review records.

Inspection concern:

Time gaps without explanation, approval dates that do not align with execution dates, mismatched batch information, or conflicting records across systems.

Consistency allows activities to be reconstructed. When related records do not align, inspectors often expand their review to determine whether the issue is isolated or systemic.

Batch record consistency is discussed further in Batch Records: What Auditors Look For.

Enduring - Is the Record Preserved Over Time?

Records must remain durable, protected, and readable throughout the required retention period.

Compliant example:

Paper records are archived under controlled conditions. Electronic records are retained in validated systems with appropriate backup and access controls.

Inspection concern:

Faded thermal printouts, damaged records, unsupported electronic formats, or electronic data that cannot be retrieved because the system is obsolete.

Enduring records protect the ability to reconstruct decisions years after the original activity occurred. This is especially important for batch release, stability, validation, and investigation records.

Lifecycle governance is addressed in Document Lifecycle: Creation to Archival.

Available - Can the Data Be Retrieved When Needed?

Data must be retrievable, reviewable, and explainable when needed.

Compliant example:

Requested records can be retrieved in a timely manner and presented with supporting context.

Inspection concern:

Records are difficult to locate, require personal knowledge to retrieve, or exist in systems without clear ownership.

Availability is not only about storage. It includes indexing, retrieval, system access, and record organization. If data exists but cannot be produced when needed, its practical value is limited.

Retrieval expectations are discussed further in Documentation Retrieval Protocols.

ALCOA+ Summary Table

ALCOA+ Principle	Weak Behavior	Better GMP Behavior
Attributable	Shared logins or unclear initials	Unique user IDs, clear signatures, defined reviewer approval
Legible	Illegible handwriting or undefined shorthand	Readable entries using approved terminology
Contemporaneous	Recording values later from memory	Recording information as the activity occurs
Original	Retaining only summaries or transcriptions	Preserving original records or verified true copies
Accurate	Overwriting, erasing, or unexplained corrections	Transparent corrections with reason, signature, and date
Complete	Missing pages or selective retention	Retain all required records, including deviations and repeat testing
Consistent	Conflicting dates or records	Logical sequence across related records
Enduring	Faded printouts or obsolete file formats	Controlled archival with protected records
Available	Difficult to retrieve records	Timely retrieval with clear organization

How Inspectors Use ALCOA+ in Practice

Inspectors do not usually conduct an “ALCOA+ audit”. Instead, they review records and use ALCOA+ principles to evaluate reliability.

They may examine:

• batch records

• laboratory worksheets

• audit trails

• logbooks

• deviation records

• stability data

• electronic system outputs

ALCOA+ becomes visible when something appears inconsistent, incomplete, delayed, overwritten, missing, or unexplained.

If records satisfy ALCOA+ principles, inspectors gain confidence that activities were performed and reviewed as required. If multiple principles fail together, concerns may shift from individual record errors to broader data integrity weaknesses.

Audit trail evaluation is addressed in Audit Trails in GMP.

Regulatory Perspective

ALCOA+ is not a checklist to memorize.

It is a framework for evaluating whether data can be trusted.

Organizations do not demonstrate data integrity by citing ALCOA+.

They demonstrate it by producing records that are attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available.

When these attributes are visible in daily operations, records support decisions.

When they are absent, data integrity becomes the focus of regulatory concern.

Explore more on Documentation & Data Integrity

Browse VerethiQ resources on documentation control, data integrity expectations, ALCOA+ principles, record review, SOP governance, and inspection readiness.