Standard Operating Procedure: Good Documentation Practices (GDP)

Purpose and Scope

This Standard Operating Procedure (SOP) outlines the requirements for Good Documentation Practices (GDP) to ensure the integrity, accuracy, and traceability of all organizational records. Adherence to these guidelines is mandatory for maintaining compliance with internal quality standards, regulatory requirements, and industry best practices. This SOP applies to all employees, contractors, and third-party partners who generate, maintain, or archive records within the organization.

Section 1: Fundamental Principles of Documentation

• ALCOA+ Principle: Ensure all documentation is Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, and Available.
• Ink Usage: All manual records must be completed in permanent, non-erasable blue or black ink. Never use pencil or felt-tip markers that bleed through paper.
• Erasures and Alterations: Never use correction fluid (White-out), tape, or over-writing to obscure data. If a mistake is made, draw a single line through the error, enter the correct data, and initial/date the change with a brief reason code (e.g., "Correction," "Error").
• Blank Spaces: Avoid leaving large gaps on forms. Use a single diagonal line to strike through empty sections and initial/date the end of the line to prevent unauthorized retrospective entries.

Section 2: Data Entry and Integrity

• Timeliness: Document all actions at the time they are performed. Do not rely on memory to update records later in the shift.
• Legibility: Handwriting must be clear and readable. Use standard date formats (DD-MMM-YYYY) to avoid ambiguity across international sites.
• Identification: Every record must clearly identify the person who performed the action. Use legible initials or a full signature as dictated by the document control system.
• Data Verification: When peer-reviewing or auditing documentation, verify that the entry is logical, follows the workflow, and does not contain unauthorized deviations.

Section 3: Review and Approval

• Authorization: Ensure that all documents are signed off by the appropriate personnel as designated in the signature delegation log.
• Second-Person Review: For critical data (e.g., test results, batch records), perform a mandatory secondary review to ensure technical accuracy and strict adherence to the SOP.
• Document Versioning: Always use the current, approved version of forms. Discard or archive obsolete templates immediately upon the release of an updated document.

Section 4: Storage and Retrieval

• Environment: Store physical documents in climate-controlled, secure, and fire-rated areas to prevent environmental degradation.
• Digital Records: Ensure digital files are saved in approved, read-only formats (e.g., PDF/A) to prevent unauthorized tampering.
• Retention: Follow the official Records Retention Schedule. Documents must be retrievable within a reasonable timeframe (typically 24 hours for audit requests).

Pro Tips & Pitfalls

• Pro Tip: Treat every document as if an auditor is reading it over your shoulder. Clarity and context are your best defenses against non-compliance.
• Pro Tip: If the document doesn't have space for a comment, attach a note or reference an investigation report. Never squeeze data into the margins.
• Pitfall - The "Reconstruction" Trap: Never try to "reconstruct" a document after an audit notice. This is viewed as fraud by regulatory bodies and leads to severe disciplinary action.
• Pitfall - Ambiguous Time: Always include time zones or AM/PM indicators when documenting critical timestamps to ensure the sequence of events is clear.

Frequently Asked Questions (FAQ)

Q: Can I use digital signatures? A: Yes, provided the digital signature system is compliant with 21 CFR Part 11 (or equivalent local regulations) and has been validated for use within the organization’s secure network.

Q: What should I do if I find a blank space on a record that someone else left? A: Do not fill in information you did not witness. Mark the space with a single line, initial, and date it. If the information is critical, report it to the Quality Assurance department for a formal investigation.

Q: Is it acceptable to use abbreviations? A: Only use approved, organization-wide standard abbreviations. If an abbreviation is specific to a department, it must be defined in the document footer or an associated glossary. When in doubt, spell it out.