Read in

21 CFR 211.68 on the floor: who did it, what changed and what cannot be lost

GxPData IntegrityAudit Trail21 CFR Part 11
21 CFR 211.68 on the floor: who did it, what changed and what cannot be lost21 CFR 211.68 on the floor: who did it, what changed and what cannot be lost

21 CFR 211.68 is often read as an IT requirement: access control, backup, validation. In practice, it answers three questions any batch reviewer asks every day. Who changed this data? What was written before? If the server stops today, does the record still exist?

What the regulation asks, in three parts

Paragraph (b) of 211.68 brings together three requirements that are often handled by different teams:

  1. Only authorized personnel change master records and other records. This applies to the master recipe, to process limits and to the batch record in execution.
  2. Input to and output from the system checked for accuracy, with a frequency and extent that depend on the complexity and reliability of the system.
  3. A backup of the data entered, kept so that the data is exact, complete and secure from alteration, inadvertent erasure or loss.

For electronic records, Part 11 adds to this: 11.10(d) calls for "limiting system access to authorized individuals," and 11.10(e) for "secure, computer-generated, time-stamped audit trails" that record operator entries and actions that create, modify or delete electronic records, where "record changes shall not obscure previously recorded information."

Who did it: access is part of the record

A common pattern is a shared login at the weighing room terminal, or a generic user per shift. The record is complete, but it does not say who did the work. For 211.68, the question is not only whether access is password-protected. It is whether each change can be attributed to one person, with the role that person held at that moment.

It is also worth looking at the periodic access review: does anyone who left the company or changed roles still have an active profile? This review is routine, not inspection preparation.

What changed: the audit trail has to be read

Having the audit trail switched on is not enough. 11.10(e) asks that the trail show who changed what and when, without obscuring the previous value. The reason for the change is not in the text of Part 11, but EU GMP Annex 11 (item 9) and, in Brazil, ANVISA IN 134/2022 (Art. 33, §1) ask for it to be documented, and data integrity guidance treats it as good practice. And someone has to review the trail. In its question-and-answer guidance on data integrity (December 2018), FDA recommends that audit trail review follow the same frequency as the review of the data: for the batch record, that means reviewing relevant changes before batch release, not in an annual audit.

Where this tends to fail is configuration: trails that record only system events, without the reason for the change, or audit trail reports that nobody can filter by batch.

What cannot be lost: a tested backup

The regulation asks for an exact and complete copy. A backup that has never been restored proves neither. The control that matters is a restore test, with a record: pick a batch, restore it in a separate environment and check that the record, the audit trail and the signatures came back intact and readable.

This includes the source data that feeds the batch, such as readings from the process historian and the scale, not only the MES database.

Credentials and signatures together

If the electronic signature uses the same credentials as system access, both have to be handled together. For electronic signatures based on an identification code and password, 21 CFR 11.300 calls for controls such as: a unique combination per person (a), periodic checking or revision of issued credentials (b), a procedure to deauthorize lost or compromised cards, tokens and other devices (c) and safeguards against unauthorized use, with immediate reporting of attempts (d). A shared credential compromises, at the same time, the "who did it" of the trail and the value of the signature.

Questions for your plant

  • Does any terminal on the floor still use a shared or per-shift login?
  • Does the batch record audit trail show the reason for the change, and is it reviewed before batch release?
  • When was the last recorded restore test, and did it include the audit trail and the signatures?
  • Does a change to an access profile go through change control?

References (checked against eCFR, 10/26/2026): 21 CFR 211.68(b); 21 CFR 11.10(d) and (e); 21 CFR 11.300(a)–(d). EU GMP Annex 11 (Computerised Systems), item 9. FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers — Guidance for Industry (December 2018), questions 7 and 8. ANVISA, Instrução Normativa nº 134, of March 30, 2022, Art. 33, §1 (DOU of 03/31/2022, Section 1, p. 361).

Newsletter

Practical writing on GxP, MES, data integrity and shop-floor systems. A few times a month, no noise.

Almost there

We will send the newsletter to . Tell us who you are.

By subscribing you agree to receive T2 Software content by email. Unsubscribe at any time from any message.

More from the blog

All articles →