Regulations and compliance · Practical guide

Part 11 operational checks for the permitted sequence of steps

A workflow can appear orderly while allowing an invalid sequence. An import might set a status before its prerequisites are met. A correction might leave an earlier review mark in place. To test operational checks under Part 11, define the permitted states, transitions and order of events for the actual process.

Table of contents

At a glance

What operational checks does Part 11 require for the permitted sequence of steps?

Section 11.10(f) requires appropriate operational system checks to enforce permitted sequences of steps and events. Define the prerequisites for each relevant transition and test alternative entry paths. A permitted role alone does not prove that a sequence was allowed. The process determines the sequence. Part 11 does not prescribe a universal four-stage workflow or an electronic signature for every transition.

  • Check authorized sequence and personal authorization separately.
  • Include alternative pathways and controlled exceptions in the state model.
  • Retrospective changes must not misleadingly imply the validity of a prior inspection.

1. Describe the order in which the decision is protected

§11.10(f) addresses the permissible sequence of steps and events, as appropriate. Therefore, begin with the technical sequence: Which decision would be incorrect if a step occurred too early, without prerequisites, or on an outdated basis? Not every screen navigation constitutes a regulatorily relevant procedural step.

The process under consideration must be assigned to the appropriate record scope prior. In a Drug CGMP example, necessary testing and documentation steps can provide relevant prerequisites. The exact sequence is derived from the specific procedure, not from a general product template containing arbitrary status names.

Sources: [1] [2] [3]

2. Audit trail control is not the same as authorization or signature

A qualified individual may still perform an action at the incorrect time. Section 11.10(g) addresses authorization; Section 11.10(f) addresses appropriate enforcement of the permitted sequence. Both controls may interact, but they address different questions. Therefore, a test conducted by an unauthorized role does not automatically validate the workflow sequence.

Similarly, a status change is not an electronic signature solely because of its name. If such a signature is provided, its specific controls are added. The state model should show intelligibly whether a transition documents a work progress, an examination or a personal explanation.

Sources: [1]

3. Define prerequisites and results for each transition

The following own work help uses an electronic test order P-64. The four states are an example design, not a statutory sequence of steps. The concrete obligation for the technical examination is assumed for this sample process.

Example: Status model for inspection task P-64
TransitionPrerequisite in the own desired modelResultControlled Exception
Recorded → complete Required data fields and associated records are available. Current completeness status. Missing information remains open; no implied confirmation.
Fully → verified The review of this data status is completed. Test basis on the actually assessed status. Correction requirement results in a return to review.
Reviewed → ready for use Further specific criteria are met. Permitted use in the example process. This status alone does not establish that a batch may be released for any use.
Reviewed → in correction Justified correction with a verifiable reason. The updated status will be re-evaluated for its effect. Old audit report is not misleadingly transferred to new data.

Sources: [1] [3]

4. Consider surface and alternative pathways

A review of the visible button alone may miss gaps. Relevant status changes can also occur via import, interface, background processing, or administrative tools. Document the actual pathways and verify where the condition is reliably controlled.

The requirement is not a claim that every product possesses all of these pathways. Select the existing and relevant routes. If a supplier certificate covers a central rule check, it may be useful; however, its statement must align with your configuration and approved transitions.

Sources: [1] [2] [3]

5. Specifically test authorized and unauthorized transitions

Example scenario: P-64 is initially in the "recorded" state; a required result record is missing. An authorized person attempts to perform the review transition. Later, the record is completed and the intended review is carried out. Additionally, the same early transition is attempted via the actually existing interface.

The matrix defines what the intended model expects. Alerts, status, and recorded actions must be consistent: an displayed error would be of limited value if a prohibited state transition is still logged in the background.

Own transition validation with specific target observations
TestStarting pointExpected effectLimits of the evidence
Premature inspection of the surface P-64 is recorded; the required record is missing. The transition to the target rule is not effectively validated. Verify the error message and the actual stored state.
Premature testing via interface Identical incomplete starting condition. An unauthorized transition is also not effectively achieved through this means. Only the actually existing interface is considered.
Permissible Transition Data complete; intended testing performed. Checked specifically refers to this version. No statement regarding other untested processes.
Change after review The result is controlled and corrected. Test sample and further procedure will be handled according to the change. No blanket requirement for new signature authorization.
Repeatedly reviewed requirement The current processing stage requires a transition. An outdated basis must not misleadingly represent the current status. Define conflict handling for the particular project.

Sources: [1] [2]

6. Explicitly describe backlogs and exceptions

Real processes may occasionally require correction, recall, or reprocessing. A state model that only recognizes the direct path to success can inadvertently drive these actions into uncontrolled administrative workarounds. Therefore, define relevant exceptions with clear justification, authorization, and demonstrable impact on existing records.

An exemption pathway is not automatically a weakening of control. It must, however, be aligned with the specific scientific and technical purpose and must not inadvertently remove essential prerequisites. Documentation should clearly indicate what has been changed and which prior evaluations remain valid or require further review.

Sources: [1] [3]

7. Evaluate rules rather than merely status labels

A "complete" status does not prove actual completeness. Therefore, compare the underlying conditions against the required records. The FDA Data Integrity Guidance states that a qualified system alone does not demonstrate whether the specific CGMP workflow, including calculations, functions correctly.

The FDA Scope Guidance of 2003 explicitly includes operational system validations within the ongoing control measures. Limited enforcement discretion for other Part 11 aspects must not be generalized to §11.10(f). Specific validation evidence must remain aligned with the appropriate operational procedures and their effectiveness.

Sources: [3] [4] [1]

8. Maintain the operating procedures through the procedure

The functional and IT teams should have a consistent understanding of the permitted transition. Clearly document the key prerequisites in plain language and link them to configuration and testing. This internal reference guide facilitates alignment even when a small team manages multiple responsibilities.

If a mandatory field, an interface, or the meaning of a status changes, re-evaluate the affected transitions. A strict, complete re-execution of all tests is not required; nor is it sufficient to state that only a single field has been modified. What matters is the actual impact on the rule.

  • Relevant decisions and acceptable sequence determine.
  • Specify the requirements for each transition in concrete terms.
  • Assign authority, procedure, and optionally signature separately.
  • Capture existing alternative routes.
  • Review authorized and premature transitions.
  • Correct and review deviations are to be described and controlled.
  • Check retained effect in addition to the screen notification.
  • Trace changes back to the affected rules and validation evidence.

Sources: [1] [2]

Project experience and collaboration

Check the permitted sequence across alternative process paths

With the process owners, we map a critical status transition and its prerequisites. IT then checks whether the same restriction applies to imports, corrections and alternative interfaces. A focused test may demonstrate an existing rule. A gap may require an additional system control or a revised workflow. We record the permitted sequence tested and the failure cases the rule is intended to prevent.

Frequently asked questions about Operational system checks

What does §11.10(f) specifically address?

The procedure specifies appropriate operational system checks that establish acceptable sequences of steps and events. The specific sequence is not provided as a general framework. It must be aligned with the intended use and relevant process requirements.

Sources: [1]

Is a role model already sufficient as a process control?

No. A role defines who is authorized to perform an action; a workflow rule additionally specifies the conditions or sequence under which the action may be performed. An authorized person might otherwise execute a step prematurely. Therefore, review §11.10(f) and (g) separately and in combination.

Sources: [1]

Must every system have four workflow stages?

No. The four states illustrated in this article's example are a deliberate design choice. Other processes may require different states or none at all. What is essential is whether the relevant permitted outcomes are appropriately implemented and the significance of each step is clearly understandable.

Sources: [1]

Must every transition be electronically signed?

Part 11 does not require every status change to be signature-protected solely because of that change. Clarify which personal statement is actually intended or required. If a transition involves electronic signatures, the applicable signature controls must also be considered.

Sources: [1] [4]

Is the button test in the user interface sufficient?

Only when the relevant pathways are actually covered. An import or an interface may employ a different processing approach. Review the existing pathways and their shared or distinct controls. The mere visual blocking of a button does not indicate central control.

Sources: [1] [2]

May a workflow allow controlled returns to an earlier step?

Yes, provided they are compatible with the intended procedure and adequately controlled. Corrections must include a clear rationale, current data status, and reference to prior evaluations. A rollback must not inadvertently delete or negate required records or the significance of a inspection note.

Sources: [1] [3]

Does an error message prove that an unauthorized transition was prevented?

Not solely. Also verify the actually stored state and relevant downstream impacts. An alert may appear correct, while in the background an inappropriate status may have arisen. Therefore, the evidence should demonstrate the intended effect and not merely the surface appearance.

Sources: [1]

Do we need a new end-to-end test package for each exception?

A complete new test package is not automatically required for every exception. Assess which rules and dependencies are affected, and select appropriate validation evidence. The exception must not be accepted without evaluation nor treated solely on the basis of its name as a full-scale new project.

Sources: [2] [3]

Does FDA enforcement discretion apply to expiry control checks?

No. The 2003 Guidance explicitly includes operational system validations within the ongoing controls. Therefore, its limited statements regarding other Part 11 requirements must not be generically applied to operational controls. Predicate rules remain equally applicable.

Sources: [4]

What should the department provide prior to technical implementation?

A clear description of permitted transitions, necessary prerequisites, and relevant exceptions is helpful. Enhance the meaning in the process of the result and define the approach to changes. IT can derive verifiable technical rules therefrom; a list of mere status names is often insufficient.

Sources: [1] [3]

Sources and review date

Source date: 7 October 2026. eCFR notice period until 5 October 2026; separate consideration of binding regulatory text and non-binding FDA Guidance. Examples and tables are internal work aids and do not represent completed product testing.

  1. 21 CFR Part 11 – Electronic Records; Electronic SignatureseCFR display until 05.10.2026; §§11.1–11.300.
  2. 21 CFR §211.68 – Automatic, mechanical, and electronic equipmenteCFR notice until 05.10.2026; paragraphs (a)–(c).
  3. FDA: Data Integrity and Compliance With Drug CGMP – Questions and AnswersFDA Data Integrity Q&A, December 2018: Question 3 on Applicability of Drug cGMP Data Integrity Requirements. The specific operational review is governed by the individually referenced Part 11 sections.
  4. FDA: Part 11 – Scope and ApplicationFinal guidance. The PDF is dated August 2003 and the status page September 2003. See sections I and III.A–C.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Jointly develop the specific evidence process

We support you in translating business requirements into verifiable procedural rules. From this, targeted requirements and meaningful tests for surfaces, interfaces, and controlled corrections can be derived.

  • 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 →