Web of Pharma · Data Integrity · ALCOA+
Enduring Principle in ALCOA+
How pharmaceutical records remain protected, readable, retrievable, and trustworthy from creation through the entire retention period.
answer
The Enduring Principle in ALCOA+ means that data and records remain protected from loss, damage, unauthorized change, and technological obsolescence while staying readable and retrievable for the required retention period. An enduring record preserves its content, context, metadata, and audit history—not merely its final appearance.
A record is not enduring simply because it was saved once. It must remain secure, intact, readable, and usable years after the original activity—when the people, instruments, software, storage media, and systems may have changed.
Enduring controls connect data integrity to document retention, archival strategy, backup, disaster recovery, cybersecurity, migration, access management, and periodic retrieval testing. They apply to paper records, electronic raw data, batch files, laboratory systems, stability records, validation evidence, and quality-system workflows.
For the broader framework, see the ALCOA data-integrity guide. This article explains how to make pharmaceutical data durable and inspection-ready over time.
What Does Enduring Mean in ALCOA+?
Data are enduring when they remain protected, accessible, readable, and meaningful for the complete approved retention period. The record should survive routine handling, storage failures, media degradation, system upgrades, personnel changes, and reasonable technology obsolescence.
Protected from loss
Records are safeguarded against accidental deletion, corruption, destruction, environmental damage, and uncontrolled disposal.
Protected from alteration
Access, permissions, audit trails, versioning, and security controls prevent unauthorized changes to retained data.
Readable over time
Paper, electronic files, reports, metadata, and dynamic records remain understandable with the available viewing tools.
Retrievable when needed
Authorized users can locate and retrieve the record within a reasonable, defined time during an audit or investigation.
Meaning preserved
Migration, conversion, compression, or archiving does not remove context, metadata, audit history, formulas, or relationships.
Retention defined
Retention periods, ownership, access, disposition, and preservation responsibilities are documented and approved.
Technology managed
Software, hardware, file formats, readers, media, and dependencies are assessed before they become obsolete.
Recovery tested
Backups, archives, restores, and disaster-recovery procedures are tested rather than assumed to work.
Authorized access
Named, trained users can review records while unauthorized access and changes remain prevented and detectable.
Why Enduring Records Matter in Pharmaceuticals
Pharmaceutical records may be needed long after manufacturing or testing is complete. They support batch investigations, complaints, recalls, stability conclusions, regulatory inspections, product lifecycle decisions, validation review, and legal or scientific questions.
If a record fades, becomes unreadable, loses its metadata, or depends on obsolete software, the organization may no longer be able to prove what happened. Enduring controls protect the evidence needed to make decisions fairly and defend the quality system.
FDA guidance describes data retention expectations that records remain protected, enduring, readily retrievable, and readable through the retention period. The retention strategy should preserve the data and the context necessary to understand it.
These expectations operate within cGMP document control, computerized-system validation, data governance, backup and archive procedures, security, disaster recovery, and quality-unit oversight.
Enduring Paper Records
Paper records need protection from physical deterioration and loss. A controlled archive should preserve the original pages, attachments, signatures, corrections, and indexes while allowing authorized retrieval and review.
| Paper-record risk | Enduring control | Failure to avoid |
|---|---|---|
| Fading or smearing | Use durable paper and permanent ink appropriate for the environment; inspect archived records periodically. | Thermal printouts, pencil, unstable ink, or solvents that make entries disappear. |
| Physical damage | Use controlled storage with protection from moisture, heat, light, insects, dust, and unauthorized removal. | Unindexed boxes, damaged pages, missing attachments, or storage in uncontrolled areas. |
| Loss of order | Maintain pagination, file indexes, attachment references, and chain-of-custody controls. | Loose pages that cannot be linked to the batch, sample, study, or approval. |
| Access uncertainty | Define authorized users, retrieval responsibilities, check-out processes, and return verification. | Records removed from the archive with no location or access history. |
| Migration to scans | Use a verified scanning process that preserves every page, entry, signature, annotation, and identifier. | Low-resolution, cropped, incomplete, or unverified scans replacing the original. |
Enduring Electronic Records
Electronic records require a lifecycle plan that considers file format, software, hardware, storage, access, metadata, audit trails, security, migration, backup, and retrieval. A record may be present on a server but not enduring if it cannot be opened or understood.
- Define the official record, retention period, owner, archive location, and authorized users.
- Retain raw data, metadata, audit trails, methods, calculations, signatures, and associated attachments.
- Use validated formats or preserve the original system and a suitable reader for dynamic data.
- Control permissions, encryption, access logs, change detection, and secure deletion.
- Test backup, restore, archive, migration, and disaster-recovery processes at defined intervals.
- Monitor media health, storage capacity, software support, certificates, and system dependencies.
- Document migrations and verify that content, context, relationships, and audit history remain intact.
- Provide a retrieval process that delivers readable records within the quality system’s required time.
Enduring Data Examples in Pharmaceutical Operations
HPLC and chromatography
Retain raw data, methods, sequences, integrations, audit trails, metadata, calculations, reports, and software context. A readable PDF without the dynamic source or processing history may not be enough for long-term review.
Batch and manufacturing records
Preserve executed records, printouts, labels, equipment logs, reconciliation, deviations, approvals, and release evidence in a controlled archive that remains readable and retrievable.
Stability programs
Maintain protocols, chamber records, sample pulls, results, trends, excursions, investigations, and approvals for the required study and product lifecycle period.
Validation and qualification
Keep protocols, raw readings, calculations, test outputs, deviations, change assessments, reports, and approvals with a clear index and usable viewing capability.
Environmental and microbiology records
Protect location maps, plates, counts, incubator conditions, photographs, worksheets, results, investigations, and trend reviews from loss or media degradation.
Quality-system records
Deviation, CAPA, change control, training, audit, complaint, and management-review records should retain versions, comments, attachments, approvals, and audit history throughout their lifecycle.
Common Enduring-Principle Failures
Faded paper records
Ink or thermal output disappears before the retention period ends, removing critical evidence.
Unsupported software
Original files remain stored but cannot be opened, searched, rendered, or meaningfully reviewed.
Unreadable media
Disks, tapes, drives, or removable media degrade or require unavailable hardware.
Unverified migration
Data are moved to a new system without checking content, metadata, relationships, formulas, or audit trails.
Backup confusion
A temporary recovery copy is treated as a controlled archive without retention, indexing, or integrity checks.
Broken links
Reports, raw files, attachments, or metadata are separated so the complete record cannot be reconstructed.
Untested restore
Organizations assume backups can be restored but discover missing permissions, files, or software during an emergency.
Access loss
Records depend on former employees, shared credentials, expired certificates, or undocumented administrator accounts.
Premature disposal
Records are destroyed before the approved retention period or before investigations and regulatory holds are complete.
How to Implement the Enduring Principle
Define retention needs
Identify record classes, retention periods, legal or regulatory holds, owners, access, and disposition rules.
Assess technology risk
Review file formats, software, hardware, media, vendors, certificates, dependencies, and obsolescence risk.
Choose preservation method
Decide whether data remain in the original system, move to a validated archive, or use a verified true copy.
Protect and monitor
Apply access, security, integrity, environmental, backup, media, and change-control measures.
Test retrieval
Periodically restore and review representative paper and electronic records using the tools available for inspection.
Improve the system
Investigate failures and use CAPA when preservation or retrieval weaknesses are systemic.
Enduring controls should be risk-based but demonstrable. A written retention procedure is not enough if the organization cannot produce a readable, complete, and authorized record when requested.
Enduring Principle Audit Checklist
Use these questions during self-inspection, archive review, batch review, or computerized-system assessment:
- Are record classes, retention periods, owners, access rules, and disposition requirements defined?
- Are original data, metadata, audit trails, attachments, calculations, and signatures preserved?
- Are paper, media, servers, cloud storage, and archives protected from loss, damage, and unauthorized change?
- Can records still be read with available software, hardware, readers, and permissions?
- Are migration, conversion, scanning, and true-copy processes validated or verified?
- Are backup and archive functions clearly distinguished and appropriately controlled?
- Are restore, retrieval, disaster-recovery, and media-integrity tests performed and documented?
- Are access logs, administrator rights, certificates, encryption, and security controls reviewed?
- Are obsolete systems, formats, vendors, media, and dependencies assessed before support ends?
- Are preservation or retrieval failures investigated and escalated through a documented quality process?
Support each answer with evidence such as archive indexes, retrieval records, restore tests, migration validation, access reports, media checks, and approved procedures.
How Enduring Fits Into ALCOA+
Enduring is one of the ALCOA+ principles. It works with attributable, legible, contemporaneous, original, accurate, complete, consistent, and available records. A record may be complete today but fail the enduring principle if it cannot be read, retrieved, or interpreted several years later.
For example, a chromatographic file can be original and complete but not enduring if its software is retired, its metadata are lost, or the archive cannot render the audit trail. A paper batch record can be accurate but not enduring if fading ink makes critical entries unreadable.
Key Takeaways
- Enduring records remain protected, readable, meaningful, and retrievable throughout retention.
- Enduring controls cover paper, electronic data, metadata, audit trails, formats, media, access, and software.
- Backup is not automatically the same as an official archive.
- Migration, scanning, conversion, and restoration must preserve content and context.
- Retrieval and restore testing prove that preservation controls work.
- Recurring preservation failures should be risk-assessed and managed through CAPA when needed.
Conclusion
The Enduring Principle in ALCOA+ protects pharmaceutical evidence over time. It ensures that records created today can still be read, understood, retrieved, and trusted when a batch is investigated, a product is recalled, a stability trend is reviewed, or an inspector requests historical data.
Enduring data integrity is built through risk-based retention, secure archives, durable media, validated migrations, tested backups and restores, controlled access, readable formats, and clear ownership. When organizations plan for the full life of a record—not just its creation—they preserve the foundation of a reliable pharmaceutical quality system.
Frequently Asked Questions
1. What is the Enduring Principle in ALCOA+?
It means that records remain protected, readable, meaningful, and retrievable for the complete approved retention period.
2. Is enduring the same as available?
They are related but different. Enduring focuses on long-term preservation and durability; available focuses on being accessible when needed. A record should satisfy both.
3. What makes an electronic record enduring?
Protected storage, retained metadata and audit trails, readable formats, controlled access, validated migration, supported software or readers, and tested retrieval.
4. Is a backup an archive?
Not automatically. A backup supports recovery after a failure, while an archive is the controlled record retained for the required period with indexing, access, integrity, and retrieval controls.
5. How can paper records remain enduring?
Use durable materials, controlled storage, environmental protection, page indexing, access control, periodic inspection, and verified scanning or reproduction where appropriate.
6. What happens when software becomes obsolete?
Use a documented technology-risk and migration plan. Preserve the original data, metadata, context, and audit history in a validated system or readable equivalent before support ends.
7. How often should archive retrieval be tested?
The frequency should be risk-based and defined by the quality system. Representative records, formats, systems, permissions, and recovery processes should be tested and documented.
8. What is a common enduring-principle failure?
Common failures include faded paper, corrupted media, unsupported file formats, untested backups, lost metadata, broken attachments, and inaccessible legacy systems.
9. How do auditors assess enduring records?
They request historical records, test retrieval, inspect readability, review archive controls, compare source and migrated data, and assess access, security, and restoration evidence.
10. When does an enduring failure require CAPA?
Escalate when records cannot be produced or understood, preservation failures recur, migration loses context, or the archive lacks a systemic control.
.webp)
