← Back to blog

Part 11 Workflow: How to Build One That Holds Up

November 3, 2026
Part 11 Workflow: How to Build One That Holds Up

A Part 11 workflow is the documented sequence of decisions, controls and evidence that makes your electronic records and signatures acceptable to FDA. It starts with which records are covered, moves through validation, access, audit trails and signatures, and continues through change control and inspection readiness. This guide walks a biotech or life sciences team through that sequence in the order you would actually build it.

Haiphai
Make Regulatory Workflows More Efficient
HaiPhai partners with life sciences teams to identify operational bottlenecks and integrate AI into processes such as regulatory drafting.
Visit HaiPhai

TL;DR

  • Part 11 applies to electronic records and signatures that FDA rules require, or that you submit to FDA. Start by deciding, record by record, whether it applies, and write the decision down.
  • Build the workflow around predicate rules first and software second. The records your underlying FDA rules require determine which controls you need.
  • The core controls are validation, authorized access, secure time-stamped audit trails, accurate copies and signatures tied to one accountable person.
  • Compliance is a life-cycle activity. Change control, corrective actions and inspection-ready documentation keep it intact after go-live.
  • If substantial Part 11 deviations exist, FDA will not accept your electronic records and signatures to meet the underlying requirement.

Table of Contents

What a Part 11 workflow actually has to do

21 CFR Part 11 sets the criteria under which FDA treats electronic records and electronic signatures as trustworthy, reliable and generally equivalent to paper records and handwritten signatures. The current eCFR text of Part 11 says it applies to records in electronic form that are created, modified, maintained, archived, retrieved or transmitted under FDA recordkeeping requirements. It also applies to electronic records submitted to FDA under the FD&C Act or the PHS Act. A paper record that is merely sent electronically does not trigger it.

That definition shapes what a "workflow" means here. Part 11 is not a software feature you switch on. It is a property of how a record is created, changed, signed, stored and retrieved across people, systems and procedures. A compliant workflow therefore has to answer six questions:

  1. Which of our records are in scope?
  2. Which FDA rules (the predicate rules) make them required?
  3. Are the systems that hold them validated for their intended use?
  4. Who can do what, and is every action attributable and logged?
  5. How do signatures bind to records?
  6. What happens when the system, the process or the people change?

The sections below follow those questions in order.

Step 1: Scope your records and systems

Teams often start by listing software. Start with records instead. FDA's Scope and Application guidance says records are subject to Part 11 in three situations:

  • Predicate rules require the record, and you keep it electronically in place of paper.
  • You keep the record electronically alongside paper, and you rely on the electronic version for regulated activities.
  • You submit the record to FDA electronically under a predicate rule.

For clinical work, FDA's October 2024 guidance on electronic systems, records and signatures in clinical investigations describes Part 11 records in similar terms: records needed to reconstruct an investigation that are maintained or retained electronically, records relied upon for regulated activities, and records submitted electronically under predicate rules.

Build a record inventory

A practical inventory has one row per record type, not per application. For each row capture:

  • The record (for example, a monitoring visit report, a batch record, a regulatory submission draft, a training record).
  • The predicate rule that requires it.
  • The system or systems where it is created, edited, stored and signed.
  • Whether you rely on the electronic version or a paper version as the official record.
  • The owner and the retention period.

The last step matters more than it looks. The Scope and Application guidance says teams should decide from the predicate rules whether each record is a Part 11 record, and document that decision. An undocumented assumption is the first thing an inspector will probe.

Handle real-world data carefully

Source systems at clinical sites create a common scoping question. In the October 2024 guidance, FDA says it generally does not intend to assess the source electronic health record system for Part 11 compliance. Once the record enters the sponsor's EDC system, FDA intends to assess Part 11 compliance there. The sponsor stays responsible for the quality and integrity of the data it submits. Your workflow should therefore mark the hand-off point where data moves from a site's source system into your controlled environment, and treat that boundary as a control point.

Step 2: Use a documented risk assessment to set the depth of control

Part 11 does not ask for the same effort on every system. FDA's Part 11 guidance advises assessing how a system affects the accuracy, reliability, integrity, availability and authenticity of required records and signatures. It does not treat compliance as a purely technical checklist. Use that framing to tier your systems.

A simple three-tier model works for most teams:

TierTypical exampleEffect on record integrityControl depth
HighEDC, eTMF, QMS, regulatory publishing, electronic signature platformsDirectly creates or holds records used to support a submission or a regulated decisionFull validation, full audit trail review, formal change control
MediumDocument management for working drafts, training systems, project trackers feeding regulated decisionsIndirectly affects regulated recordsRisk-based testing, access controls, periodic review
LowGeneral productivity tools that never hold a regulated recordNo effect on required recordsConfirm and document that they are out of scope

The table is a planning aid, not an FDA classification. The point is that the risk assessment is written, signed and traceable, and that it drives your validation plan.

Step 3: Validate for intended use

FDA recommends risk-based validation documented from design through decommissioning or migration. According to the October 2024 guidance, the evidence should address:

  • Intended use and requirements
  • Functionality and configuration
  • Customizations
  • Interfaces and data transfers
  • Testing and acceptance
  • Data integrity
  • Change control
  • Documentation from a qualified service provider, where relevant

In practice that translates into a validation package with a short list of documents: a user requirements specification, a configuration specification, a test plan with executed scripts, a traceability matrix linking requirements to tests, and a release memo. If a vendor hosts the system, collect the vendor's qualification documentation and decide what you still need to test yourself. Configuration choices, such as role definitions and signature meanings, are yours to validate even when the platform is not.

Common validation gaps

  • Testing the vendor's standard product rather than your configured instance.
  • Validating the system but not the interfaces that move records between systems.
  • Treating decommissioning and data migration as an IT task rather than a validated change to regulated records.

Step 4: Design access, audit trails and copies

This is where the regulation gets specific. 21 CFR 11.10 lists the controls for closed systems. They include system validation, the ability to generate accurate and complete copies in human-readable and electronic form, protection of records so they can be retrieved throughout the retention period, limiting access to authorized individuals, and secure, computer-generated, time-stamped audit trails. It also requires operational system checks, authority checks and device checks, plus controls that ensure signers cannot readily repudiate signed records.

Key controls for Part 11 closed systems

Access control

Build role definitions from the record inventory. Each role should map to specific actions on specific record types: create, edit, review, approve, sign, administer. Keep administrator rights separate from content rights, and review the list on a schedule you define in a procedure. Shared logins break attribution, so prohibit them in the same procedure.

Audit trails

The eCFR requires that audit-trail changes not obscure previously recorded information, that the trail be retained at least as long as the associated electronic records, and that it be available for FDA review and copying. The October 2024 guidance adds practical expectations: capture every change to an electronic record, who made it, the date and time, and the reason when applicable. It also says audit trails should be protected from modification and disabling.

FDA recommends keeping audit trails in searchable and sortable form when practical. Where that is not possible, static files such as PDFs should clearly correspond to the relevant records, be complete and understandable, and identify old and new values. That affects archiving decisions: if your retirement plan exports records but leaves audit trails behind, your retention workflow has a gap.

For a deeper look at mapping predicate rules to audit-trail design, including tamper-evidence techniques, see our piece on FDA audit trail requirements.

Copies for inspection

Test the "accurate and complete copies" requirement before an inspector does. Pick a record, export it with its audit trail, and have someone outside the system team confirm it is readable and complete. Put that test in your periodic review schedule.

Step 5: Tie signatures to people and meaning

A signature workflow has to make the signer identifiable, accountable and unable to readily repudiate the signed record. FDA inspection guidance on this topic stresses accountability: FDA's bioresearch monitoring attachment calls for ensuring individuals are held accountable for actions taken under their electronic signatures.

Practical design choices:

  • Define the meaning of each signature (author, reviewer, approver) in the workflow, and display it with the signed record.
  • Link the signature to the specific version of the record so later edits cannot silently carry over an old approval.
  • Write a short signer accountability statement into onboarding and training, and keep proof that each user acknowledged it.
  • Decide how you handle delegation, leave and departures so access never outlives employment.

Step 6: Train, change-control and stay inspection-ready

Validation on go-live day is the easy part. The October 2024 guidance says to maintain compliance through appropriate access controls, inspection-ready documentation, documented change control, and risk-based evaluation and validation of system changes throughout the life cycle. It also says to document changes and corrective and preventive actions for errors or noncompliance that may affect data integrity or participant protection.

Turn that into four recurring routines:

  1. Change control. Every configuration change, patch, vendor release or interface change gets a risk assessment and a decision on how much re-testing it needs.
  2. Periodic review. Review user lists, role assignments, audit-trail samples and open deviations on a fixed cycle.
  3. CAPA. When an error or gap could affect data integrity or participant protection, open a corrective and preventive action, document it and close it with evidence.
  4. Training. Train users on the procedure, not just the software screens, before they receive access. Retrain when procedures change.

If you want an end-to-end preparation model for the QA and regulatory side, our 8 to 12 week inspection readiness sprint lays out how teams organize this work.

What happens when the workflow fails

The consequence is direct. According to FDA's inspection guidance, when substantial and significant Part 11 deviations exist, FDA will not accept electronic records and electronic signatures to meet the applicable predicate-rule requirements. The same guidance calls for a corrective-action plan to reach full compliance and timely progress against it. For a company working toward a filing, losing the acceptability of electronic records is not a paperwork problem. It can stall the evidence behind a submission.

The guidance also says firms should determine Part 11 compliance case by case and, at minimum, ensure a corrective-action plan, accurate and complete electronic and human-readable copies, and accountability for electronic-signature actions. Those three items make a good minimum bar for any internal audit of your workflow.

Where AI fits, and where it needs governance

Biotech teams increasingly use AI to draft regulatory documents, summarize site records and route approvals. Any of those tools that create or modify a regulated record sit inside your Part 11 scope. The same logic applies as for any other system: define intended use, validate the configuration, control access, keep an attributable audit trail and put changes through change control. A drafting assistant whose output is reviewed and approved by a named person, with the approved version captured in a validated system, is a different risk profile from one that edits records directly. Write that distinction into your risk assessment before the tool goes live.

Our view on the human and machine split in regulatory work is covered in where AI can help in regulatory affairs and what must stay human. For workflow redesign on the regulatory side, see the 90 day pilot for regulatory affairs workflow design.

A starter checklist

Use this as a first-pass audit of any Part 11 workflow:

  • Record inventory exists, with predicate rule and Part 11 decision documented for each record type.
  • Each system has a written risk assessment and a validation package that matches its intended use.
  • Interfaces and data migrations are validated, not assumed.
  • Roles map to actions, no shared accounts, access reviewed on a schedule.
  • Audit trails capture who, what, when and why, cannot be disabled by ordinary users and are retained as long as the records.
  • Signatures show meaning, bind to a record version and tie to a single accountable person.
  • Export of a record with its audit trail has been tested by someone outside the system team.
  • Change control, periodic review, CAPA and training are written procedures with evidence of execution.

Perspective: why workflow comes before software

We see the same pattern in biotech teams. The software is purchased, the validation package is written, and the compliance gap is still there, because the records move through people and handoffs the software never touched. A draft starts in one tool, gets commented in another, and is approved in a third.

That is why we start from your strategic goal, such as a filing date or a site activation target, and work backward to the operational bottlenecks. Part 11 controls belong inside that map, not bolted on afterward. When a regulatory drafting step or a site activation step is redesigned, the record, the signer, the audit trail and the change control are designed with it.

Our approach is to embed a senior team in your live operations, build AI-enabled workflows around your regulatory and scientific needs, and keep governance and adoption running after launch. The aim is a workflow your team can explain to an inspector, and that frees time instead of consuming it.

John

Work with an operational partner on your Part 11 workflow

If your team is redesigning regulatory, clinical or executive workflows and wants Part 11 controls built in from the start, HaiPhai works as an embedded operational partner. We begin with a diagnostic of where time and risk accumulate, then redesign the workflows, integrate AI under governance and monitor performance and compliance as operations run.

Haiphai

To see how an engagement is structured, read about our operational partnership or start from the HaiPhai home page.

FAQ

Does Part 11 apply to every electronic record we create?

No. It applies to electronic records that FDA requirements call for, or that you submit to FDA, as set out in 21 CFR Part 11. FDA's scope guidance asks you to decide from the predicate rules whether each record is a Part 11 record and to document that decision. Records that no FDA rule requires and that you never submit are outside that test.

What is a predicate rule?

A predicate rule is an underlying statutory or regulatory requirement outside Part 11 that says a record must be created or kept, such as requirements for clinical investigation or manufacturing records. FDA's scope guidance uses predicate rules to decide whether a record is subject to Part 11. Mapping each record to its predicate rule is the first step of your workflow.

What should an audit trail capture?

FDA's clinical-investigation guidance recommends capturing every change to an electronic record, the person who made it, the date and time, and the reason when applicable. Audit trails should be protected from modification and disabling. FDA also recommends keeping them searchable and sortable when practical.

How often do we need to revalidate a system?

Part 11 does not set a fixed interval. FDA recommends risk-based evaluation and validation of system changes throughout the life cycle, with documented change control. In practice, you re-test in proportion to what changed and how much it affects record integrity, and you review the system periodically on a schedule your procedures define.

Can we use AI tools in a Part 11 environment?

Yes, if the tool is treated like any other system that creates or modifies regulated records. Define its intended use, validate the configuration, control access, keep attributable audit trails and route changes through change control. Confirm the approach with your QA and regulatory leads for your specific records.

Sources