Regulations and compliance · Practical guide

21 CFR 211.68 vs Part 11: automated systems in drug CGMP

A Part 11 checklist cannot cover every aspect of a computerised drug manufacturing process. Section 211.68 establishes separate drug CGMP requirements for automatic, mechanical and electronic equipment, including computers. Check scheduled controls, authorised changes and the accuracy of input and output. Evidence of Part 11 controls alone does not establish that the process has been adequately tested.

Table of contents

At a glance

What does 21 CFR 211.68 require in addition to Part 11?

In the applicable drug CGMP context, § 211.68 addresses the use of automated equipment and specified controls for computer systems. Part 11 covers the electronic records and signatures within its scope. Neither provision replaces the other. Assess inputs, formulas and outputs alongside access, change history and retention. Under § 211.68, the extent and frequency of input and output checks depend on system complexity and reliability.

  • Drug-CGMP-Predicate-Rules and Part 11 Controls have different responsibilities.
  • Section 211.68 does not require a blanket manual double-check of each entry.
  • The specific automation rule in subsection (c) applies only to named processes and includes further verification of proper execution.

1. Specify the Drug-CGMP linkage explicitly

Part 211 establishes minimum requirements for pharmaceutical products within its scope of application and includes specific exclusions. This guide addresses an assumed human drug manufacturing process for which this section was established. It does not generically apply §211.68 to all research, medical device, or administrative applications.

Name the activity and its records. For example, §211.188 requires batch manufacturing and testing records containing the information specified therein. If such records are maintained or used electronically, an appropriate Part 11 evaluation is also required. A software trademark or a general FDA promotional notice does not satisfy this assignment.

Sources: [1] [2] [3] [4]

2. Assign the requirements to different questions

§211.68 asks, among other things, whether the equipment used performs its function properly and whether entered or transmitted formulas, records, or data have been verified for accuracy. Part 11 addresses the applicable electronic record and signature implementation. Appropriate evidence can support both questions if its coverage is demonstrable.

Own assignment matrix of requirement levels
QuestionPrimary referenceExample of an appropriate justification
Does the equipment in use perform its function reliably within the intended process flow? §211.68(a) Written program and records for the corresponding scheduled controls.
Are modifications to production or testing records authorized only for designated personnel? §211.68(b); additionally §11.10(d),(g) Roll rule and review of permitted and prohibited modifications.
Does the application process formulas and data accurately? §211.68(b) Independent target values, input/output comparison, and justified inspection depth.
Are relevant electronic changes and records traceable and retained? Applicable Part 11 controls, in particular §11.10(c), (e) Appropriate records, history, and documentation pertaining to the intended storage process.
Is the actually used electronic signature adequately implemented? Applicable §§11.50–11.300 Identity, significance, representation, and binding evidence.

Sources: [5] [3]

3. Calibrate, inspect, or verify: as appropriate for the equipment

Clause (a) permits the use of appropriate automatic, mechanical, or electronic equipment, including computer systems. When such equipment is used, regular calibrations, inspections, or tests according to a written procedure shall be performed; the associated written records shall be maintained. The activities must be appropriate to the specific equipment and function.

It does not follow that every software component would need to be calibrated in a metrological sense. For example, distinguish between a relevant measurement pathway and a calculation function or an automated data transfer. In your own software, describe which control ensures proper functionality and how deviations are handled.

Sources: [5]

4. Justify the review of inputs and outputs

Clause (b) addresses the accuracy verification of inputs and outputs, including formulas and other records or data. The extent and frequency should be aligned with the complexity and reliability of the system. A fixed number of samples or a universal manual two-eyes approach therefore does not follow.

Define which errors you must detect: incorrect unit, inappropriate reference value, missing data point, or unauthorized formula modification. Verify not only that the system produces a value, but also that the result is plausible—plausibility does not guarantee accuracy, as erroneous data sources can still yield seemingly reasonable outcomes. Therefore, the rationale for your control depth should explain the significance of the result and known dependencies.

Sources: [5]

5. A fully calculated theoretical yield in the event of a complete failure

Example: For a production step, the theoretical yield is 125.00 kg, and the documented actual yield is 118.75 kg. The required formula is actually calculated as actual divided by theoretical, multiplied by 100. Independently computed, 118.75 / 125.00 × 100 yields exactly 95.00 percent.

The values and formula constitute a standalone test aid. 95 percent is neither specified as an acceptable yield nor as a release limit. §211.188 provides yield information at relevant process stages; product-specific evaluation remains a separate responsibility. The test question is solely whether the correct reference value is processed using the correct formula.

Worked example with expected inputs and outputs
CaseInput and ProcessingExpected resultSignificance of the finding
Normal case 118.75 kg / 125.00 kg × 100 95.00 percent The calculation path and assignment to the two input values are correct.
Incorrect reference value 118.75 kg / 100.00 kg × 100 Mathematically 118.75 percent, technically incorrect basis for this intended scenario Not only verify the plausibility of the display; check the record linkage of the denominator.
Unit not converted 118750 g is incorrectly divided by 125.00 kg as if it were kg. Error calculation 95000 percent; correct conversion yields 95.00 percent Unit handling and error detection are specifically to be verified.
Reference value is missing or zero No valid theoretical yield available No technically valid result; defined error handling Own specified requirements; no specific product behavior claimed.

Sources: [5] [2]

6. Read the backup section carefully and thoroughly

§211.68(b) requires a backup of entered data and specifies protection against modification, accidental deletion, or loss. The backup data shall be accurate and complete. Therefore, a successful copy job confirmation does not fully address all questions regarding content and protection.

The section also addresses a limited case of certain data that are eliminated due to computerization or other automated processes, such as calculations associated with laboratory analyses. For this, it requires a written program record together with appropriate validation data. However, no authorization is granted to delete generated raw data or any further required records.

Do not derive a universal backup frequency or equate backup with archiving. Clarify which records remain required in the specific process and how accuracy, completeness, protection, and appropriate retention are addressed.

Sources: [5] [3]

7. Paragraph (c) does not replace human testing without conditions

§211.68(c) expressly refers to operations in §§211.101(c) or (d), 211.103, 211.182 and 211.188(b)(11). Under the aforementioned conditions, automated equipment can fulfil the performance described therein by a person and inspection by another person. The condition remains, inter alia, that a person checks whether the equipment has performed the operation properly.

The statement must not be shortened to "automation creates all duplicate controls." Review the specific process and the relevant referenced regulation. Section 211.188(b)(11) specifies, in the context of automated execution, the identification of the person performing the inspection. A particular type of electronic signature or general QA authority does not automatically follow from this.

Sources: [5] [2]

8. Close evidence gaps at the appropriate level

The FDA Guidance from 2003 outlines limited enforcement discretion regarding certain Part 11 requirements. The underlying predicate rules remain in effect. Therefore, reliance on this Guidance does not automatically eliminate a gap in controls under §211.68.

For a small project, a clear list comprising data flow, formula version, responsible parties, existing evidence, and pending reviews is sufficient as an initial step. The functional and IT departments must jointly be able to trace the origin of any result. The extent of additional work depends primarily on unknown formulas, interfaces, changes, and the quality of existing documentation.

  • Identify the drug and specify the CGMP scope and relevant records affected.
  • Align written control program with the respective equipment.
  • Authorize and control changes to records and relevant formulas.
  • Rationale for input/output verification based on complexity and reliability.
  • Calculate target values independently and verify error cases with units.
  • Evaluate backup requirements and required record retention separately.
  • Clause (c) to be applied only for actually recorded events.
  • Assign additional controls under Part-11 and close outstanding justifications.

Sources: [5] [4]

Project experience and collaboration

Assess the equipment and its records separately

We start with a specific use. What does the application do in manufacturing or the laboratory, and which records does it create? We clarify this with process owners before comparing IT features against checklists. Equipment requirements and additional electronic record rules can both apply to one application. Existing equipment qualification may provide useful evidence but does not automatically cover every data path. We map tests to what they actually demonstrate and plan targeted work for remaining gaps.

Frequently asked questions about 21 CFR 211.68 vs Part 11

Is §211.68 merely an alternative designation for Part 11?

No. §211.68 falls under Drug CGMP requirements and addresses automatic, mechanical, and electronic equipment, including computer systems. Part 11 covers relevant electronic records and signatures. A joint oversight can support both, but the regulations do not replace one another.

Sources: [5] [3]

Does 211.68 apply to any pharmaceutical software?

No. § 211.68 applies to automatic, mechanical, or electronic equipment—including computers—used in the manufacture, processing, packaging, or storage of a drug product within the scope of Part 211 (§ 211.68(a), § 211.1(a)). Membership in the pharmaceutical industry alone is not sufficient. Assign the use to its actual function; for laboratory and batch records, additional provisions such as § 211.194 or § 211.188 may apply.

Sources: [1] [5]

Must computer systems be calibrated pursuant to §211.68?

The text refers to calibration, inspection, or testing according to a written procedure. The appropriate activity depends on the equipment and function involved. Therefore, a metrological calibration obligation does not follow for every software function; rather, appropriate controls and records are required to ensure proper performance.

Sources: [5]

Must every entry be verified by a second person?

Clause (b) requires accuracy verification of inputs and outputs, but assesses the extent and frequency based on complexity and reliability. It does not include a general manual double-check requirement for each field. Additional applicable regulations and the specific process shall also be considered.

Sources: [5]

Is it sufficient to test a calculation formula once using normal values?

This depends on the intended use and relevant failure modes. A single normal case may result in incorrect units, missing values, or inappropriate reference data going undetected. Justify test depth and frequency based on the system; the cases presented here serve as a standalone reference guide.

Sources: [5]

Is a 95 percent yield in the example of this article a GMP release limit?

No. The number arises exclusively from 118.75 divided by 125.00 multiplied by 100. It verifies correct data processing in the example provided for this article. Whether an actual yield is technically acceptable requires the relevant product-specific specifications and a separate evaluation.

Sources: [5] [2]

Does the exception in the backup section permit the deletion of raw data?

No. The exception in § 211.68(b) relates to backup files for certain data that are no longer generated due to computerization or other automated processes, such as calculations in laboratory analyses. For such cases, a written program record and appropriate validation data must be maintained. The provision does not include authorization to delete generated raw data or other required records.

Sources: [5] [3]

Does §211.68 require daily backups?

No. § 211.68(b) does not specify a general daily backup frequency. It requires the relevant backup file and precise, complete backup data that are protected against modification, unintended deletion, or loss. Establish a justified practical implementation for your process and additionally consider applicable documentation obligations.

Sources: [5]

Does the second check always become obsolete upon automation?

No. Paragraph (c) addresses particular operations and conditions. A person must still check that the equipment performed the operation correctly. The provision cannot be generalised to any approval, other check or automated process.

Sources: [5] [2]

Can we justify a gap under §211.68 using FDA Enforcement Discretion?

The Part 11 Guidance of 2003 does not withdraw the predicate rules. Therefore, assess at which requirement level the gap exists. A statement of compliance with specific Part 11 controls does not automatically satisfy the obligation to implement appropriate controls for data processing under §211.68.

Sources: [4] [5]

Sources and review date

Source date: October 6, 2026: 21 CFR §§211.1, 211.68, 211.188 and Part 11, eCFR display up to October 2, 2026; FDA Scope and Application 2003. The example scope pertains to human drug manufacturing within the applicable Drug-CGMP domain. Specific product areas and additional predicate rules require individual mapping. Computational and testing cases are considered work aids.

  1. 21 CFR 211.1 — ScopeeCFR Display Date: 02.10.2026; Sections (a)–(c) reviewed. References: §211.1(a)–(c)
  2. 21 CFR §211.188: Batch production and control recordseCFR updated as of 02.10.2026; displayed on 06.10.2026. Citations: §211.188(a); §211.188(b)(1)–(13)
  3. 21 CFR Part 11 — Electronic Records; Electronic SignatureseCFR: Title 21 consolidated through 02.10.2026; Title 21 last amended on 30.09.2026. The display does not constitute a claim of a Part 11 amendment on this date. Citations: §11.1(a)–(e) and sector-specific exemptions (f)–(p); §11.2; §11.3(b)(4),(5),(6),(7),(9); §11.10(a)–(k); §11.30; §§11.50, 11.70, 11.100, 11.200, 11.300
  4. FDA: Part 11 — Scope and Application, Original-PDFOriginal cover page August 2003, Pharmaceutical CGMPs; Contains nonbinding recommendations. Currently listed by FDA as Final. Reference locations: I. Introduction, printed pages 1–2; III.A, page 4; III.B.1–2, pages 5–6; III.C.1–5, pages 6–8
  5. 21 CFR 211.68 — Automatic, mechanical, and electronic equipmenteCFR Display Date: 02.10.2026; fully reviewed (a)–(c). References: §211.68(a); §211.68(b); §211.68(c)

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Applicability and targeted review of evidence

Daniel Herrmann Consulting supports you in defining your specific process and the appropriate documentation requirements. The scope and responsibilities are aligned with actual needs.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →