← Guides

Good documentation practice: how should corrections be made in batch records?

By Savi C., Co-Founder · Published Nov 16, 2026

The principle

A batch record is evidence of what happened. A correction is allowed, but it must not destroy that evidence. A reader, whether a QA reviewer or an inspector, should be able to see what was first written, what it was changed to, who changed it, when, and why if the reason is not obvious.

EU GMP Chapter 4 paragraph 4.9 says any alteration made to an entry should be signed and dated, should permit the reading of the original information, and, where appropriate, should record the reason. PIC/S PI 041-1 section 8.7 expects corrections to be made in a way that maintains full traceability. FDA’s data integrity guidance describes the same goal through ALCOA: data that is attributable, legible, contemporaneously recorded, original or a true copy, and accurate.

How to make a correction on paper

Do

  • Draw a single line through the incorrect entry so it remains readable
  • Write the correct entry next to it, not on top of it
  • Initial and date the correction
  • Record the reason where it is not self-evident, and always for critical data
  • Use indelible ink, the same as for the original entry
  • Make the correction as soon as the error is noticed
  • Follow your site procedure for who may correct an entry and when a second check is needed

Do not

  • Overwrite the original value
  • Use correction fluid, tape or erasers
  • Scribble out the original so it cannot be read
  • Correct someone else’s entry without following your procedure for that case
  • Remove or rewrite a page to tidy the record

What reviewers check, and why

Reviewer check

The original entry is still readable

What it protects

The ability to see what was first recorded

Reviewer check

Each correction has initials and a date

What it protects

Attribution and timing of the change

Reviewer check

A reason is recorded for changes to critical data, with supporting evidence

What it protects

That the change was justified, not convenient

Reviewer check

No overwriting, correction fluid or pencil

What it protects

That the record is enduring and has not been altered silently

Reviewer check

No unexplained symbols or marks

What it protects

That every mark on the record has a known meaning

Reviewer check

The correction is consistent with the source

What it protects

That the new value matches the printout, label or log it came from

Common edge cases

Blank fields are not corrections, but they are handled the same way: PIC/S PI 041-1 expects unused fields to be voided, for example crossed out, and signed and dated. Late entries are different again. Records are expected to be completed at the time of each action, so most GDP procedures require an entry made after the event to be marked as late, with the date it was actually written, rather than dated as though it were contemporaneous. Your GDP procedure should cover both, along with when a correction needs a second person’s verification. Train on real examples from your own records, both good and bad, because a picture of an acceptable correction is easier to follow than a written rule.

Attached printouts and labels need the same care. A glued-in printout should never be written over. Most site procedures put any correction in the batch record entry that refers to the printout, signed, dated and explained, rather than on the printout itself. Where printouts are on thermal paper that fades, PIC/S PI 041-1 expects signed and dated true copies to be made and kept.

In electronic records the same principle is enforced by the system. 21 CFR 11.10(e) requires computer-generated, time-stamped audit trails, and record changes must not obscure previously recorded information.

How Litewave fits

Litewave reads paper or electronic records, checks every entry against your master record and specifications, and shows QA only the exceptions, each linked to the page it came from. Corrections that lack initials, a date or a reason are flagged for the reviewer with the source page alongside. Litewave proposes, qualified people approve.

Questions we get asked

Does every correction need a reason?

EU GMP Chapter 4 asks for the reason where appropriate. PIC/S PI 041-1 expects a reason to be recorded where appropriate and verified if the data is critical. Most site procedures require a reason for any change to critical data and allow obvious slips, such as a misspelling, to be corrected without one.

Can an operator correct another person’s entry?

Only as your procedure allows. Most sites require the person who made the entry to correct it, or require a documented reason and an approver when that is not possible, so the change remains attributable.

Is correction fluid ever acceptable?

No. It obscures the original entry, which is exactly what EU GMP Chapter 4 paragraph 4.9 and PIC/S PI 041-1 are written to prevent.

Sources

  1. EudraLex Volume 4, EU GMP Chapter 4, Documentation
  2. PIC/S PI 041-1, Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments
  3. FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers (2018)
  4. 21 CFR 11.10, Controls for closed systems, including audit trails (eCFR)