21 CFR Part 11US FDA · electronic records & signatures

21 CFR Part 11 compliant software — what it really takes.

Looking for 21 CFR Part 11 compliant software? Part 11 compliance is achieved by your validated system and your procedures together. Swat iQua Suite is designed to comply with 21 CFR Part 11: secure audit trails, electronic signatures with re-authentication and access controls are built into every module.

  • Audit trail with a reason for every change
  • E-signatures with name, designation, meaning and time
  • Role-based access, MFA and lockout
  • Segregation of duties in 25 modules
Batch release dossier with each critical check signed by a named QA reviewer

Real product footage

See the Part 11 controls in the product.

The regulation

What 21 CFR Part 11 requires for electronic records and signatures.

Part 11 sets the conditions under which the FDA considers electronic records and electronic signatures trustworthy, reliable and equivalent to paper records and handwritten signatures.

Title 21 of the US Code of Federal Regulations, Part 11, applies to records that FDA predicate rules require you to keep — batch records, laboratory records, complaint files and so on — when you create, modify, maintain, archive, retrieve or transmit them electronically. It also applies to electronic signatures used in place of handwritten ones. Part 11 does not add new record-keeping duties; it governs how the records you already must keep are controlled once they are electronic.

Subpart B — electronic records

Section 11.10 lists the controls expected for closed systems. In summary: validation of systems to ensure accuracy, reliability and consistent intended performance (11.10(a)); the ability to produce accurate and complete copies in human-readable and electronic form (11.10(b)); protection of records so they can be retrieved accurately throughout the retention period (11.10(c)); limiting system access to authorised individuals (11.10(d)); secure, computer-generated, time-stamped audit trails that record the date and time of entries and actions that create, modify or delete records, without obscuring previously recorded information (11.10(e)); operational system checks to enforce the permitted sequencing of steps (11.10(f)); authority checks (11.10(g)); device checks (11.10(h)); training of the people who develop, maintain or use the system (11.10(i)); written policies that hold individuals accountable for actions under their signatures (11.10(j)); and controls over system documentation (11.10(k)).

Section 11.50 requires signed electronic records to show the printed name of the signer, the date and time of signing and the meaning of the signature — such as review, approval or responsibility. Section 11.70 requires signatures to be linked to their records so that they cannot be excised, copied or otherwise transferred to falsify a record.

Subpart C — electronic signatures

Section 11.100 requires each electronic signature to be unique to one individual and not reused by or reassigned to anyone else, and the organisation to verify a person’s identity before assigning one. Organisations must also certify to the FDA that their electronic signatures are intended to be the legally binding equivalent of handwritten signatures. Section 11.200 requires non-biometric signatures to use at least two distinct identification components, such as a user ID and a password. Section 11.300 covers controls for identification codes and passwords — uniqueness, periodic revision, handling of lost credentials and safeguards against unauthorised use.

How the FDA reads it today

The FDA’s 2003 guidance on Part 11 scope and application explains that the agency interprets the rule narrowly and applies enforcement discretion to some requirements — validation, audit trails, record retention and record copying — while still expecting predicate rules to be met and audit trails to be justified by risk. In practice, investigators expect controlled access, attributable actions, audit trails on GMP-relevant data and meaningful signatures. Data integrity findings remain a common theme in FDA Form 483 observations and warning letters.

Requirement → control

How Swat iQua Suite supports each Part 11 control.

Every capability below is enforced by the platform on the server, not left to user discipline.

  • 11.10(e) — Audit trail

    Every write and its audit-trail entry commit in one transaction: old value, new value, user, site, time and a mandatory reason for the change.

    • Cross-module audit trail report
    • Filter by site, module, user, date and activity
    Audit trail
  • 11.50 — Signature manifestation

    Signed records show the signer’s name, their designation at the time of signing, the meaning of the action and the date and time.

    • Designation frozen at signing
    • Historical signature block on controlled prints
  • 11.70 — Signature linking

    A signature is the authenticated actor and timestamp recorded with an immutable log row of the action itself — bound to that record and that step.

  • 11.200 — Signature components

    Signing re-authenticates with the user’s ID and password. Where configured, a one-time code is added. Levels are set per module and per site.

    • 3 e-signature levels
  • 11.10(d), (g) — Access & authority

    A role-based permission matrix controls every action, per site. Changes to the matrix need their own permission and are logged.

    Security & access
  • 11.300 — Credential controls

    Forced password change at first login and on expiry, a password policy per site, MFA, and time-limited lockout after repeated failed logins or codes.

  • 11.10(f) — Operational checks

    Workflow stages are enforced: a batch step cannot start while an earlier hold point is open, and a sample cannot be approved before review.

  • Accountability — SoD

    Segregation of duties in 25 modules: the preparer cannot review, the reviewer cannot approve, the batch operator cannot release.

  • 11.10(b), (c) — Copies & protection

    Controlled PDF prints and Excel exports, with each export logged. Encrypted connections, scheduled backups and automatic log archiving.

One signed approval

What the inspector sees behind a single signature.

Take a specification approval. Each step is attributable, sequenced and signed by a different person — and all of it is in the audit trail.

  1. PrepareDraft v3 r0

    Specification drafted

    Changes recorded with old and new values and the reason for each edit.

    Draft
  2. ReviewReviewer ≠ preparer

    Reviewed and signed

    The reviewer re-authenticates; name, designation, meaning and time are recorded.

    Signed
  3. ApproveApprover ≠ both

    Approved and frozen

    Approval freezes a version snapshot that cannot be changed.

    Approved
  4. UseSample registered

    Version applied

    Each sample freezes the specification version in force at registration.

    Traceable

Every action, signature and change — one audit trail, reportable across modules.

Shared responsibility

What remains your responsibility under Part 11.

Part 11 places obligations on the regulated company. Swat iQua Suite gives you the technical controls; these items are yours to own, and our team supports each of them.

  • Validation (11.10(a)) — validating your installation for its intended use, with a risk-based approach. We support it with requirements traceability in the CSA register and evidence of the Part 11 controls.
  • Written policies (11.10(j)) — SOPs that hold individuals accountable for actions under their electronic signatures, and that describe how the system is used and administered.
  • Training (11.10(i)) — making sure users and administrators are trained. Training Management in Swat iQua Suite records SOP-based training with read-and-accept, server-graded exams and certificates.
  • Identity and certification (11.100) — verifying each person’s identity before issuing an account, and submitting your certification to the FDA that electronic signatures are the legally binding equivalent of handwritten ones.
  • Documentation control (11.10(k)) — controlling your system documentation, SOPs and change records. SOP & Document Control keeps controlled copies that cannot be altered once effective.
  • Periodic review — reviewing audit trails, access rights and configuration on a schedule you justify by risk. The periodic audit trail review module helps your QA team do it.

Software cannot be “Part 11 compliant” on its own. A validated installation, used under your procedures by trained people, is what demonstrates compliance.

FAQ

Frequently asked questions

Can’t find your answer? Talk to our team — we reply within one business day.

Is Swat iQua Suite 21 CFR Part 11 compliant software?

Swat iQua Suite is designed to comply with 21 CFR Part 11. It provides the technical controls — audit trails, electronic signatures, access and authority checks, sequencing and segregation of duties. Compliance itself is demonstrated by your organisation, through validation of your installation, your procedures and trained users.

How do electronic signatures work?

At signing, the user re-authenticates with their ID and password, or with password plus a one-time code where that level is configured. The signed record shows the signer’s name, designation at the time, the meaning of the signature and the date and time. Signature levels are set per module and per site.

Can an administrator change records without a trace?

Changes go through the application with a mandatory reason, and each write commits together with its audit-trail entry. Privileged changes, deletions and changes after approval are flagged automatically for your periodic audit trail review.

Does it support the audit trail review the FDA expects?

Yes. A cross-module audit trail report filters by site, module, user, date and activity and exports to PDF and Excel. The periodic audit trail review module freezes risk signals when a review starts, records findings and can raise a CAPA, with QA approval by e-signature.

Does Part 11 apply to hybrid paper and electronic records?

Where electronic records are used to meet a predicate rule, Part 11 applies to them. For batch records run partly on paper, Swat iQua Suite controls issued paper copies — one-shot print with a checksum, reconciliation against the electronic record, and a close gate until the copy is reconciled.

Do you provide validation documents?

We support your validation: requirements traceability in the CSA register, evidence of the Part 11 controls, and our implementation team working alongside your QA and CSV leads. The validated state belongs to your organisation, for your installation.

Ready to see Swat iQua Suite in action?

Book a free, personalised demo and see how Swat iQua Suite takes your plants, labs and quality teams from paper to inspection-ready.

Download the brochure →