Laboratory Record Review and Record Locking: Practices That Protect Integrity
Laboratory record review and record locking are the twin practices that protect the integrity of experiment documentation: review confirms that each record is complete, correct, and understandable before it is relied on; locking prevents approved records from being silently altered after review. Together, they are what make a lab's documentation trustworthy rather than merely current.
Labs often have a review step but treat it as a formality, or have locking configured but never verified, and discover during an audit or a reproducibility failure that the controls were weaker than they appeared. This guide covers how to design laboratory record review and locking practices that genuinely protect integrity, what a reviewer should check, and how to handle corrections after locking.
Why Review and Locking Are a Pair
Review without locking is incomplete protection, because a record that passes review can still be changed afterward, and the reviewer's approval becomes meaningless if the record that was reviewed is not the record that stands. Locking without review is equally weak, because a locked record that was never checked may contain errors, and locking only preserves those errors permanently. The two practices are a pair: review confirms the record is correct, and locking preserves that correct state against subsequent alteration.
This pairing is also what GLP, GxP, and other quality frameworks expect. An approved record must be demonstrably the record that was reviewed, and the system must prevent the original author from editing it after approval. A lab that has review but no locking, or locking but no review, fails this expectation in different ways.
What a Reviewer Should Check
Review is not a rubber stamp. A useful review checks whether the record is complete, correct, and understandable to someone who did not run the experiment. This means the reviewer looks for missing context, such as an unstated deviation or a skipped field, that would make the record unusable later. A reviewer who only confirms the record exists is not reviewing; they are countersigning.
Specific checks include: are the materials identified by stable identifiers, not just by name? Are protocol deviations recorded and explained? Are raw data links present and working? Is the record's conclusion supported by the data presented? And is the record written clearly enough that a future reader can understand what was done and why? A reviewer who asks these questions and expects answers before approving produces records that hold up under later use.
Record Locking and the Correction Workflow
| Practice | What it enforces | What breaks without it |
|---|---|---|
| Locking on approval | Approved record cannot be edited by author | Silent changes after review |
| Correction as new version | Fixes create a new entry, not an overwrite | Original lost, history broken |
| Reason required for correction | Every change has an explanation | Unexplained alterations |
| Reviewer-only unlock | Only a reviewer can initiate a correction | Author circumvents review |
Locking on approval means the author cannot edit the record once it is approved. If a correction is needed, it flows through a formal change process: the reviewer initiates the correction, the change creates a new version rather than overwriting, and the reason for the correction is recorded. This workflow preserves the original approved record while allowing legitimate corrections, which is the balance that maintains both integrity and practicality.
A common failure is a system where the author can reopen a locked record by simply clicking "edit." This is not locking; it is a soft gate that the author can pass at will. True locking requires that only a reviewer or a separate role can initiate a correction, so the author-reviewer separation that GLP expects is maintained through the correction cycle.
Designing a Review Workflow That Works
A review workflow should be fast enough that records do not pile up unreviewed, and thorough enough that the review actually catches issues. This requires defining who reviews which records, setting an expectation for review turnaround, such as within one business day, and making the review step simple enough that it is not a burden. A review workflow that is slow or burdensome will be bypassed, which is worse than having no formal workflow at all because it creates the appearance of control without the substance.
The workflow should also flag records that fail review, sending them back to the author with specific feedback rather than leaving them in limbo. A record returned with "please fix" and no specifics stalls; a record returned with "add the primer sequences and confirm the construct identifier" can be fixed promptly. Specific, actionable review feedback is what makes the review cycle productive rather than frustrating.
How Zettalab Supports Review and Locking
For labs that need structured review, record locking, and correction workflow in one workspace, Zettalab connects molecular biology tools with ELN-style documentation and review. ZettaNote supports review states, role-based permissions, and record locking on approval, so a team can design a review workflow where approval locks the record and corrections create visible new versions. To design review and locking practices inside a connected lab workspace, explore Zettalab's cloud-based R&D lab platform.
FAQ
What should a lab record reviewer check?
A reviewer should check that the record is complete, with all required fields filled and materials identified by stable identifiers; that protocol deviations are recorded and explained; that raw data links are present and working; that the conclusion is supported by the data; and that the record is written clearly enough for a future reader to understand. Review that only confirms the record exists is not review; it is countersigning. Specific, actionable checks are what make review protect record integrity.
What is record locking and why does it matter?
Record locking prevents an approved record from being edited by its original author, so the record that was reviewed is the record that stands. Without locking, a record can be changed after review, and the reviewer's approval becomes meaningless because the record may no longer reflect what was reviewed. For GLP and other quality frameworks, locking is the mechanism that preserves the integrity of the approved state. A system where the author can unlock and edit at will is not locked.
How should corrections be handled after a record is locked?
Corrections should flow through a formal change process: only a reviewer or a separate role can initiate a correction, the change creates a new version rather than overwriting the approved original, and the reason for the correction is recorded. This preserves the original approved record while allowing legitimate corrections. A system where the author can silently edit an approved record breaks the locking protection entirely.
How fast should lab record review be?
Review should be fast enough that records do not accumulate unreviewed, typically within one business day for routine records. A slow review workflow causes records to pile up, which creates backlog pressure that leads to rushed, superficial reviews. Defining a clear expected turnaround, assigning review responsibility explicitly, and making the review step simple are what keep the workflow moving without sacrificing thoroughness.
What makes a review workflow effective rather than burdensome?
An effective workflow is fast, specific, and enforced. It defines who reviews which records with a clear turnaround expectation. It returns records that fail review with specific, actionable feedback rather than vague instructions. And it is enforced by the system, approved records are locked, corrections are visible, so the workflow is not optional. A workflow that is slow, vague, or bypassable becomes a burden that degrades rather than protects record quality.
Conclusion
Laboratory record review and record locking are the paired practices that protect data integrity: review confirms correctness, and locking preserves that correct state. Together with a formal correction workflow that creates visible new versions, they make a lab's documentation trustworthy under later use, audit, and reproducibility demands. A connected R&D workspace that supports structured review and system-enforced locking, such as Zettalab, fits labs whose records must hold up over time. To design review and locking practices inside a structured lab workspace, explore Zettalab's cloud-based R&D lab platform.
Related Articles