Good Documentation Practices (GDP)
Good Documentation Practices (GDP) are often treated as a checklist of do’s and don’ts. Inspectors, however, do not evaluate GDP as a list of formatting rules. They evaluate whether documentation reliably reflects what actually occurred.
GDP is not a standalone regulation. It is the practical application of data integrity and documentation control principles in daily operations. When GDP is weak, inspectors often identify issues that escalate beyond individual records and into systemic findings.
This article explains how inspectors interpret GDP during audits, provides practical examples, and highlights the behaviors that separate compliant documentation from inspection risk.
What GDP Actually Covers
GDP governs how information is recorded, corrected, reviewed, and retained.
In practice, GDP ensures that documentation is:
Clear and readable
Traceable to the individual performing the task
Recorded at the time the activity occurs
Protected from inappropriate alteration
Retained in a controlled manner
GDP supports the ALCOA+ framework discussed in ALCOA+ Explained. Where ALCOA+ defines principles, GDP defines day-to-day execution.
Clear and Permanent Recording
Inspectors expect documentation systems to ensure that entries are clear, permanent, and understandable without verbal explanation.
Compliant Example:
Blue or black ink used consistently
Units of measure defined
Abbreviations aligned with approved SOPs
Inspection Concern:
Pencil entries
Unclear shorthand
Overwritten values
When inspectors cannot interpret a record independently, they question whether it can serve as reliable evidence.
Recording clarity expectations are also discussed in Good Recording Practices.
Recording at the Time of Activity
GDP requires that documentation controls enforce contemporaneous recording and enable detection of delayed or reconstructed entries.
Compliant Example:
An operator documents process parameters immediately during production.
Inspection Concern:
Multiple entries completed simultaneously after the fact, or timestamps that suggest delayed recording.
Inspectors interpret delayed recording as a data integrity risk because it weakens trust in timing accuracy.
Proper Corrections and Transparency
Errors are inevitable. GDP establishes controlled correction practices that preserve transparency and traceability.
Compliant Example:
Single-line strike-through
Original entry remains visible
Reason for correction documented
Signature and date included
Inspection Concern:
Erased entries
Correction fluid
Overwritten data without explanation
Improper corrections often escalate quickly during inspections.
Correction mechanics are addressed in Redlining, Corrections, and Audit Trails.
Completeness and Omission Risks
GDP requires that records capture all required information - not just favorable data.
Compliant Example:
Deviation details documented fully, even when outcomes are undesirable.
Inspection Concern:
Missing fields, skipped steps, or selective recording.
Inspectors interpret omissions as systemic weaknesses, not clerical errors.
Consistency Across Documents
Consistency is a recurring inspection focus.
Inspectors assess whether:
Terminology matches SOP language
Dates and signatures align logically
Sequential activities are recorded in order
Inconsistent documentation behavior is explored in Batch Records: What Auditors Look For.
Review and Oversight
GDP includes meaningful review.
Inspectors expect:
Review signatures to reflect evaluation, not routine sign-off
Discrepancies to be identified and addressed
Documentation to support accountability
When review appears mechanical rather than evaluative, inspectors question whether oversight is functioning.
Common GDP Failures Observed in Inspections
Certain GDP weaknesses recur frequently:
Missing dates or signatures
Incomplete corrections
Illegible entries
Inconsistent record formats
Uncontrolled copies in circulation
Many FDA 483 observations originate from these patterns. A deeper analysis of inspection trends is covered in Common Documentation Errors Observed in FDA 483s.
GDP as a Daily Discipline
Inspectors do not expect perfection. They expect consistency. That consistency must be reinforced through documented procedures, training, and oversight mechanisms - not informal expectations.
When GDP is embedded in daily operations, documentation withstands scrutiny without reconstruction or explanation. When GDP is treated as a compliance formality, inspection findings often extend beyond individual records to question system governance.
Regulatory Perspective
GDP is not about formatting - it is about reliability.
Inspectors use GDP principles to determine whether documentation can be trusted as evidence of GMP activities. When records are clear, timely, complete, and properly corrected, inspections proceed efficiently. When GDP weaknesses are systemic, documentation becomes the focal point of regulatory concern.
