Redlining, Corrections & Audit Trails
Errors occur in GMP documentation. Inspectors do not expect perfection. They expect transparency.
How corrections are made - on paper or in electronic systems - often determines whether an issue remains minor or escalates into a data integrity concern. Redlining, correction practices, and audit trail review are not cosmetic requirements. They are mechanisms that demonstrate whether documentation can be trusted.
This article explains how inspectors interpret corrections, how redlining should be handled, and how audit trails support controlled changes in electronic systems.
Why Correction Practices Matter in Inspections
Inspectors review corrections to determine whether:
The original data remains visible
Changes are attributable
The timing of corrections is clear
Reasons for changes are documented
Correction practices are evaluated through the lens of ALCOA+ principles, particularly Attributable, Contemporaneous, Original, and Accurate, as discussed in ALCOA+ Explained.
Improper corrections suggest more than a documentation error - they suggest potential concealment or weak control.
Redlining in Paper-Based Records
In manual systems, corrections must preserve the integrity of the original entry.
Acceptable Practice:
Single-line strike-through
Original data remains legible
Correction entered adjacent to original
Date and signature of person making correction
Brief explanation where appropriate
Inspection Concerns:
Erasure or correction fluid
Complete overwrite of data
Multiple strike-throughs obscuring original value
Corrections without signature or date
Inspectors interpret erased or obscured entries as potential data integrity risks, even when no intent to mislead is evident. Correction practices are evaluated at the record level, not in isolation from the surrounding documentation context.
Recording expectations are discussed further in Good Documentation Practices (GDP).
Corrections in Electronic Systems
Electronic systems handle corrections differently. Data may not be physically visible once modified. Instead, control relies on audit trails.
Inspectors expect:
Original entries to remain retrievable
Changes to be automatically timestamped
User identification linked to changes
Rationale documented where required
Electronic corrections are not judged by appearance, but by reconstructability.
Audit trail interpretation is explored further in Audit Trails in GMP.
Timing of Corrections
Timing often determines inspection interpretation.
Acceptable:
Corrections made promptly after identifying an error, with explanation.
Escalation Risk:
Large numbers of corrections entered simultaneously, particularly close to inspection dates.
Inspectors may question whether entries were back-filled or reconstructed. Even when legitimate, poor explanation invites scrutiny.
Distinguishing Corrections from Data Manipulation
Not all corrections indicate misconduct. Inspectors distinguish between:
Legitimate error correction
Inappropriate alteration
Data manipulation
Factors influencing inspector interpretation include:
Transparency of correction
Frequency and pattern
Alignment with procedural controls
Audit trail consistency
Patterns matter more than isolated incidents.
Review and Oversight of Corrections
Correction control does not end with the person making the change.
Inspectors assess whether:
Supervisory review evaluates corrections
Repeated correction patterns are monitored
Audit trail reviews occur periodically
If corrections are frequent but never questioned, inspectors infer weak oversight.
Common Inspection Signals Related to Corrections
Recurring inspection triggers include:
Excessive corrections in critical fields
Corrections without explanations
Audit trail entries that cannot be reconciled with records
Shared electronic credentials
Manual and electronic records that conflict
These signals often appear in FDA 483 observations when inspectors question data reliability.
Redlining During Inspections
A frequent error occurs when organizations attempt to “clean up” documentation immediately before or during inspections.
Inspectors interpret last-minute corrections cautiously. Documentation should reflect routine behavior, not inspection preparation.
Regulatory Perspective
Regulators do not prohibit corrections. They require that corrections be transparent, attributable, and explainable.
When original entries remain visible, changes are clearly documented, and audit trails support reconstructability, inspectors view corrections as part of normal operations. When entries are obscured, unexplained, or inconsistent, documentation becomes a focal point for deeper review. In inspections, correction practices are assessed not for perfection, but for integrity.
