What this article helps you consider
- Define the complete record
- Map how the result is created
- Control access and changes
Define the complete record
An analytical record can include sample receipt, preparation observations, weights, instrument files, acquisition settings, processing methods, calculations and review. Metadata provide the context needed to interpret these records. A printed chromatogram or PDF may omit information retained in the original electronic system.
FDA’s drug-CGMP data-integrity guidance supports risk-based strategies for reliable and accurate data. These pharmaceutical expectations should be identified with their scope. Other laboratory sectors can apply similar principles through their own accreditation, regulatory and contractual frameworks. R52
Map how the result is created
Follow the actual workflow from sample registration to approval and retention. Identify manual transcription, spreadsheets, interfaces and points where information can be altered or lost. The illustration presents this lifecycle and shows that record retention begins when data are generated, rather than after a report is signed.
A report is supported by a complete record set
Traceable originals + relevant change history + review rationale
Preserve identity, actual weights, preparation observations and relevant timing.
Conceptual explanation. No product result, acceptance criterion or universal regulatory sequence is established by this illustration.
A hypothetical laboratory might preserve final instrument files but overwrite a spreadsheet used to calculate the result. The report would then lack part of its supporting record. Assess each system according to the role it plays in the quality decision, including apparently simple utilities.
Control access and changes
Use individual accounts and roles appropriate to responsibilities. Shared credentials weaken attribution. Separate routine analytical permissions from administrative functions where appropriate, and manage account creation, changes and removal. A technically available audit trail provides little value if users can disable it without control.
Define which changes require explanation and review. Reprocessing, altered integration and changed sample sequences can be legitimate, but their history must remain available. A clean final chromatogram should not conceal discarded attempts, deleted data or unexplained processing decisions.
Review the underlying evidence
The reviewer should assess the relevant original records and changes, not only the final reported numbers. Review procedures should identify which audit trails and metadata are relevant, how they are examined and what findings trigger investigation. The depth of review should reflect data criticality and system risk.
An outlying injection cannot be omitted solely because it makes a batch average less convenient. If an injection or preparation is invalidated, preserve the evidence and the scientific rationale. Consistent records allow legitimate laboratory problems to be distinguished from selective reporting.
Demonstrate retention and retrieval
Backups support recovery after failure, while archives preserve records for the required retention period. The two functions overlap but are not identical. Test whether retained data can be restored and interpreted with the necessary software, methods and metadata.
Electronic signatures and access controls also depend on system configuration, validation, procedures and training. Purchasing software described as compliant does not by itself establish compliance with 21 CFR Part 11 or other applicable requirements. Evaluate the actual implementation and record scope. R53
Make good practice workable
Timely recording requires practical forms, suitable equipment access and realistic staffing. A system that encourages unofficial notebooks or later reconstruction creates avoidable risk. Provide clear escalation routes when an error occurs so that corrections remain traceable and analysts do not feel pressure to hide a problem.
Stabicon can support complete analytical records and clearly defined reporting packages within the agreed project scope. Clients should establish data ownership, access, retention and review responsibilities in their laboratory and quality agreements.
References & further reading
Read the source in its stated scope. Requirements, amendments and compendial editions depend on the product and target market. Draft guidance is identified separately.
- R52FDA Data Integrity and Compliance with Drug CGMP
Final questions and answers, December 2018. Pharmaceutical scope.
- R53FDA Part 11 Electronic Records and Electronic Signatures
Final scope-and-application guidance, August 2003. Apply together with underlying record requirements.
From insight to a defined programme
Bring your next technical question.
Share your formulation, testing objective or development challenge. Stabicon can review the context and define a suitable scope of work.
Discuss this topic with Stabicon






