# Lab Notebook Correction SOP Template for Your Lab Team By the end of this guide you will be able to write, roll out, and enforce a correction standard operating procedure (SOP) for your lab's notebooks. You will have a complete template you can paste into your lab's quality documents, a worked correction example you can show every new hire, a set of reason codes that make audits faster, a training plan with a competency sign-off, and a clear picture of how corrections work differently on paper and in an electronic [lab notebook](/knowledge/molecular-biology/lab-notebook) (ELN). To use this guide, you need a bound notebook with pre-numbered pages or administrator access to your ELN, black permanent ink pens for paper records, and about an hour to adapt the template to your lab's needs. If your lab works under a formal quality system such as Good Laboratory Practice (GLP) studies or ISO-accredited testing, review the finished SOP with your quality manager before release. ## Why a Correction SOP Matters A lab notebook is a legal and scientific record. It supports patent filings, reproducibility checks, regulatory inspections, and the everyday question of "what exactly did we do last March?" When an error is corrected poorly, with white-out, erasure, or an unexplained scribble, the record loses credibility. A reviewer can no longer tell what was originally recorded, why it changed, or who changed it. Good correction practice follows one principle: preserve the original entry, make the change visible, and document who made it, when, and why. The original value stays readable. The correction sits next to it. The correction carries initials, a date, and usually a short reason. This is the same logic that underlies audit trails in regulated industries, where the history of a data change is as valuable as the data itself. Most labs already follow some version of these rules informally. The problem is inconsistency. One postdoc draws a neat single line and initials. Another scratches out the number so hard the paper tears. A third uses correction fluid because the page "looks nicer" that way. An SOP removes that variability by putting the expected behavior in writing, training everyone on it, and checking it during periodic reviews. ## The Core Rules of a Proper Correction These rules are the backbone of any lab notebook correction SOP. They apply whether you record data by hand or approve changes in software. 1. **Never erase, scrape, or obscure the original entry.** No erasers, no correction fluid, no correction tape, no writing over the mistake. The original entry must remain readable. 2. **Draw one thin line through the error.** A single horizontal or diagonal strike-through keeps the original value legible. Pressing hard enough to make the entry unreadable defeats the purpose. 3. **Write the correction immediately next to the error.** Above the line for a single value, in the margin, or on the same line after the strike-through. The reader should never have to hunt for the corrected value. 4. **Initial and date the correction.** Use the date you make the correction, not the date of the original entry. Many labs require a witness initial for corrections in regulated work. 5. **Add a short reason when the error could confuse a reader.** A one-line explanation such as "transposed digits, timer log confirms 45 min" prevents misreading. 6. **Use permanent ink and treat late entries honestly.** Record data at the time of the experiment. If you must enter something later, write it as a late entry that states both the date you are writing and the date the observation actually occurred. 7. **Never remove pages.** Torn-out pages, deleted rows, or renumbered pages make the whole notebook suspect. If a page is wrong in its entirety, void it visibly and move on, as described below. 8. **Correct your own entries.** If someone else must correct an entry, the correction should be initialed by the person making it, with a note identifying whose entry was corrected and why. ## Lab Notebook Correction SOP Template Copy the template below into your lab's quality documents and fill in the bracketed fields. This is the full lab notebook correction sop template text, formatted so you can adopt it with minimal editing. ``` STANDARD OPERATING PROCEDURE Title: Correcting Entries in Laboratory Notebooks SOP Number: [LAB-QA-0XX] Version: 1.0 Effective: [DATE] Owner: [PI or Lab Manager] Review: [ANNUAL REVIEW DATE] 1. PURPOSE To define how errors in laboratory notebook entries are corrected so that original data remain legible, attributable, and traceable. 2. SCOPE Applies to all paper laboratory notebooks and to all correction, addendum, and late-entry actions in [ELN NAME] used by personnel in [LAB NAME]. Does not cover sample labeling or raw instrument output files, which are governed by [RELATED SOP]. 3. DEFINITIONS Correction: A change to an existing entry, made by single-line strike-through with the new value written adjacent. Late entry: Information entered after the event it describes, labeled with both the entry date and the event date. Addendum: New information added to a completed entry, dated and initialed at the time it is added. Void page: A page marked as unusable, without removal. 4. PROCEDURE 4.1 Draw a single thin line through the incorrect text or number. The original entry must remain fully legible. 4.2 Write the corrected value immediately adjacent to the error. 4.3 Initial and date the correction with the date the correction was made. 4.4 Enter a reason code (Section 5) and, where the error could be misread, a one-line explanation. 4.5 For paper notebooks, use permanent black ink. Never use pencil, erasable ink, correction fluid, or correction tape. 4.6 Never remove, replace, or renumber pages. To void a page, draw a single diagonal line across the page, write "VOID" with a short reason, then initial and date it. Continue on the next page and cross-reference ("continued on p. XX"). 4.7 For late entries, write "LATE ENTRY" followed by the date of writing, the date of the original observation, and the reason for the delay. 4.8 In [ELN NAME], use the platform's edit or revision function. Enter a reason in the required field. Never edit a signed or witnessed entry without following [WITNESSING SOP]. 4.9 A witness initials and dates corrections when required by [TRIGGER, e.g., GLP studies, release testing]. 5. REASON CODES TR [Transcription error](/knowledge/molecular-biology/transcription-error) CL Calculation error WP Wrong parameter recorded (time, temperature, volume, setting) EQ Equipment malfunction or calibration issue discovered later SA Sample mix-up or labeling error IL Entry illegible (spill, damage), rewritten with cross-reference OT Other (one sentence required) 6. TRAINING All personnel complete correction training (Section 2 of the onboarding plan) before recording data independently. Competency is documented on the sign-off form in [APPENDIX B]. 7. RECORDS AND RETENTION Completed notebooks are stored [LOCATION] for [RETENTION PERIOD]. ELN records are retained per [ELN RETENTION POLICY]. ``` ### Template Format at a Glance This table summarizes the lab notebook correction sop template format, showing what goes in each field and the mistake each field exists to prevent. | Field | What goes in it | Mistake it prevents | |--|--|--| | Strike-through | One thin line through the error, original still readable | Obliteration, torn pages, unreadable history | | Corrected value | New entry written adjacent to the error | Reader cannot find the correct number | | Initials and date | Corrector's initials plus the correction date, not the original date | Unattributable changes, backdating | | Reason code | TR, CL, WP, EQ, SA, IL, or OT from Section 5 | Slow audits, repeated unexplained edits | | Explanation | One sentence when the error could be misread | Guesswork during review or patent examination | | Void handling | Diagonal line, "VOID," reason, initials, cross-reference | Missing pages that undermine the whole notebook | | Late entry label | "LATE ENTRY" with both dates and a reason | Entries that appear backdated | | ELN reason field | Short typed reason saved with the revision | Silent overwrites with no change history | If you want a free lab notebook correction sop template you can redistribute, the text above is written to be copied directly. Replace the bracketed fields, have your quality manager or principal investigator approve it, and assign a version number before release. ## Step-by-Step Walkthrough: Making and Documenting a Correction ![Five steps for correcting a wrong incubation time on page 42, from confirming the error to adding initials, date and reason code.](/article-images/illustrations/lab-notebook-correction-sop-template-correction-steps.webp) This walkthrough doubles as a lab notebook correction sop template example. It shows a realistic error, the correction, and what a reviewer should see afterward. Use it verbatim in your training session. **Scenario.** On 12 March 2026, a team member records an incubation time incorrectly during a growth curve experiment. **Step 1. Freeze the original entry mentally.** Before touching the pen, confirm the error. Compare against the source of truth, in this case the incubator timer log. **Step 2. Draw one thin line through the wrong value.** ``` BEFORE correction (page 42, notebook NB-07, written 12 Mar 2026): Culture S-114 diluted 1:10 in PBS. Abs600 = 0.42 after 15 min incubation. ^^ incorrect value ``` **Step 3. Write the corrected value directly above the struck text.** ``` AFTER correction: Culture S-114 diluted 1:10 in PBS. Abs600 = 0.42 after 45 15 min incubation. --- (45 written above the struck-through 15) ``` **Step 4. Add initials, the correction date, and the reason code.** ``` AFTER correction, complete: Culture S-114 diluted 1:10 in PBS. Abs600 = 0.42 after 45 15 min incubation. --- JT 14 Mar 2026 TR: transposed digits, timer log T-2026-031 confirms 45 min ``` **Step 5. Record the change in the notebook's correction log.** Many labs keep a running correction log in the back of each notebook or in a shared spreadsheet. A filled entry looks like this: ``` CORRECTION LOG Notebook: NB-07, page 42 Entry date: 12 Mar 2026 Error: Incubation time recorded as 15 min Correction: 45 min, confirmed against timer log T-2026-031 Reason: TR (transcription error) By: J. Torres, initials JT, dated 14 Mar 2026 Witness: M. Okafor, initials MO, dated 14 Mar 2026 (required for GLP) ``` **Expected output.** A reviewer opening page 42 sees four things without asking anyone: the original reading of 15, the corrected reading of 45, the identity and date of the person who made the change, and the justification with a pointer to the corroborating timer log. The original value is still legible. Nothing was erased. **Step 6. Verify the correction.** Run through this check before moving on: - Can you still read the original entry? If not, you pressed too hard or used fluid. Start over with a new approach on the page, never by erasing your failed attempt. - Do the initials and date sit next to the correction, not floating elsewhere on the page? - Does the corrected value match the source of truth? - Is the reason code and, if needed, the one-line explanation present? - Does the correction log entry match what is written on the page? ## Special Cases That Need Slightly Different Handling ![Decision path for special correction cases: void a wrong page, rewrite an illegible entry with IL, or redo a faulty calculation.](/article-images/illustrations/lab-notebook-correction-sop-template-special-cases.webp) **A calculation is wrong midway.** Strike through the entire faulty calculation with a single line, write "calculation error, see below," then perform the calculation again from the starting values. Do not patch individual digits inside a formula, because a patched formula is hard to reconstruct later. **A whole page is wrong.** Draw a single diagonal line across the page, write "VOID" with a short reason such as "wrong template used," then initial and date it. Continue on the next page with a cross-reference in both directions ("voided, see p. 43" on the voided page and "continues from p. 42" on the new page). Never remove the page. **An entry is illegible after a spill.** Draw a single line through the damaged text, note "IL: entry damaged by buffer spill," rewrite the affected content below or on the next page with a cross-reference, and initial and date the rewrite. The rewrite is a late entry if significant time has passed, so include both dates. **You discover an error weeks later.** Correct it the same way, using today's date for the correction. If the corrected entry changes a conclusion recorded elsewhere, follow the trail: correct or annotate every downstream entry that depended on the wrong value, and initial each change. **The error is in someone else's entry.** The person who made the original entry corrects it whenever possible. If you must correct it yourself, for example during a review, write the correction with your own initials and date, and add a note such as "correction to entry by J. Torres of 12 Mar." Some labs require the original author to countersign in that situation. Decide the rule in advance and put it in your SOP. ## Training Your Lab Team on Proper Correction Procedures A template changes nothing on its own. Training your lab team on proper correction procedures is what turns the document into practice. A simple four-stage plan works for labs of almost any size. **Stage 1. Orientation (30 minutes).** Walk the whole team, including experienced members, through the SOP. Show the worked example from the previous section. Show one bad correction (obliterated entry) and one good correction side by side. Explain why the rules exist, especially that original entries must stay readable for legal and reproducibility reasons. **Stage 2. Hands-on exercise (20 minutes).** Give every new hire a practice page from an old, non-record notebook containing ten planted errors: a transposed digit, a wrong unit, a spilled and smudged line, an entry that should be voided, and so on. Have them correct each error on paper following the SOP. Review their work together. **Stage 3. Competency sign-off.** The trainer checks the corrected practice page against the checklist below and signs a short form filed with training records. ``` COMPETENCY CHECK: NOTEBOOK CORRECTIONS Name: ____________________ Date: __________ [ ] Original entries remain legible after every correction [ ] Corrected values written adjacent to errors [ ] Initials and correction date present on every change [ ] Reason code used on every correction [ ] One-line explanation given where the error could be misread [ ] Void page performed with diagonal line, reason, and cross-reference [ ] Late entry labeled with both dates [ ] Correction log entry matches the page Trainer: ____________________ Pass / Retrain ``` **Stage 4. Periodic reinforcement.** Fold a correction check into whatever notebook review you already do, such as monthly data reviews or quarterly peer checks. Pick two recent corrections at random and confirm they meet the checklist. Praise good corrections publicly. Quietly retrain anyone whose corrections drift. Two habits sustain the system. First, make correcting easy by keeping the reason codes short and printed inside the notebook cover or pinned in the ELN workspace. Second, never punish honest error reporting. If people fear that a documented correction marks them as careless, they will stop documenting corrections, and your record integrity collapses in a way you cannot see. ## Electronic Lab Notebook Comparison Paper and electronic records handle corrections differently, and the difference affects which platform fits your lab. The comparison below covers how each medium treats the core requirements: preserving the original, attributing the change, and explaining it. | Feature | Bound paper notebook | Loose-leaf or photocopied pages | Electronic lab notebook | |--|--|--|--| | Original entry preserved | Yes, if struck through correctly | Only if the original page is retained | Yes, in revision history by default | | Attribution of changes | Manual initials and date | Manual, easy to omit | Automatic username and timestamp | | Reason for change | Manual note and reason code | Manual, often skipped | Required field in many platforms | | Audit trail | None built in, relies on discipline | Weak | Built in, tamper-resistant when configured | | Voiding bad pages | Diagonal line and "VOID" | Remove risk of missing pages | Mark entry void or supersede it | | Search across corrections | Manual review | Manual review | Searchable revision logs | | Backup and loss risk | Single physical copy, fire and water risk | Copies help | Central backups, depends on vendor | | Training burden | Moderate, rules are physical and visible | High, rules drift easily | Lower for mechanics, higher for configuration | Three practical points emerge from this electronic lab notebook comparison. First, ELNs enforce attribution automatically, which removes the most common paper failure, the unsigned correction. Second, ELNs can still be misused: if a platform allows silent overwrites because versioning or audit trail settings are disabled, your SOP should require an administrator to confirm those settings before roll-out. Third, regulated electronic records carry expectations for signatures and audit trails under frameworks such as FDA 21 CFR Part 11, so labs moving from paper to ELN for regulated work should involve their quality or compliance function in the configuration, not just the science. For most academic labs, a hybrid works well: bound paper notebooks for bench work with the correction SOP above, and the ELN for protocols, shared data, and anything that needs to be searchable across the group. Whichever mix you choose, write the correction rules for that medium into the SOP rather than assuming people will transfer paper habits to software. ## How to Verify Corrections During Reviews and Audits Verification keeps the SOP alive. During your periodic notebook review, sample a handful of pages and confirm the following: 1. Every visible correction has initials and a date. 2. Original entries under the strike-through lines are still readable. 3. Reason codes match the nature of the error. A calculation error coded as TR suggests the codes are not being read. 4. Voided pages still exist in the notebook and carry cross-references. 5. Late entries carry both dates. 6. Correction log entries, if you keep them, match the pages they reference. In an ELN, pull the revision history for three or four entries and confirm that each change carries a username, timestamp, and a reason that a stranger could understand. If reasons read "fix" or "oops" repeatedly, refresh the training with concrete examples of a useful reason sentence. ## Common Mistakes and Limitations The most frequent failures, in rough order of how often they appear during reviews: - **Using correction fluid or tape.** This is the single most damaging habit because it destroys the original entry entirely. Ban it explicitly in the SOP and remove bottles from the bench area. - **Writing in pencil or erasable ink.** Both invite silent revision. Require permanent black ink in the SOP and stock compliant pens at every bench. - **Initialing without a date, or dating with the original entry date.** Both create ambiguity about when the record actually changed. The correction date is the date the pen touched the paper. - **Obliterating the error.** A strike-through so heavy that the original cannot be read is functionally the same as deletion. Train people to press lightly. - **Correcting silently in the margin.** A marginal number with no initials, date, or reason looks like contamination or fraud to an outside reviewer even when it was innocent. - **Voiding pages by removal.** A missing page from a numbered sequence raises questions about everything else in the notebook. Void visibly instead. - **Backdating "to make it tidy."** Never. If data were entered late, the honest late-entry format protects the record. Backdating destroys it. - **SOP and practice drifting apart.** If the SOP requires reason codes and the notebooks show none, either enforce it or amend the SOP. A document nobody follows is worse than none, because it implies a standard the lab then fails. A limitation to state plainly: this template is a starting point, not a compliance verdict. Labs working under GLP, clinical laboratory standards, or an ISO-accredited quality system must align the SOP with their own regulatory requirements and have it approved through their document control process. Individual records also sometimes raise questions that a template cannot answer, for example a disputed authorship or a suspected data integrity issue, and those situations deserve a conversation with your quality office or institutional research integrity staff rather than a spot decision at the bench. ## Frequently Asked Questions ### What is a lab notebook correction SOP? It is a written procedure that tells everyone in a lab exactly how to fix mistakes in notebook entries so the original data stay legible, attributed, and dated. A good SOP covers strike-through technique, initials and dates, reason codes, voided pages, late entries, and the equivalent actions in an electronic lab notebook. ### Can I use white-out or correction tape in a lab notebook? No. Correction fluid and tape hide the original entry, which makes the record unverifiable and can invalidate the notebook for patent or regulatory purposes. Draw a single line through the error, write the correction adjacent, and initial and date it. ### How do I correct an error in an electronic lab notebook? Use the platform's edit or revision function rather than deleting and rewriting, enter a meaningful reason in the change field, and let the software's audit trail capture your username and the timestamp. If the entry is already signed or witnessed, follow your lab's procedure for amending signed records. ### Who should initial a correction, the original author or a witness? The person who made the original entry should correct and initial it whenever possible. A witness initial is added when your SOP requires it, typically for regulated work or corrections made by a reviewer to someone else's entry. ### What do I do if I find an error weeks after the original entry? Correct it now, using today's date on the correction, and add a short reason. If the error affected later conclusions, trace through the notebook and correct or annotate every downstream entry that depended on the wrong value. ### Is a correction the same as an addendum? No. A correction changes an existing entry and replaces a wrong value, while an addendum adds new information to an entry that was already correct. Both are dated and initialed at the time they are made, but they serve different purposes and your SOP should define both terms. ### How do I handle an entire page of wrong entries? Draw a single diagonal line across the page, write "VOID" with a short reason, initial and date it, and continue on the next page with cross-references in both directions. Never remove the page, because a gap in the page numbering undermines the credibility of the whole notebook. ### How long should we keep corrected lab notebooks? Follow the retention period your institution, funder, or quality system requires, which often runs several years past the end of a project and longer for regulated or patent-relevant work. Your SOP should state the location and retention period explicitly so anyone can find the rule without asking.