Guide

How AuditSafe Meets 21 CFR Part 11 and EU Annex 11, Clause by Clause

AuditSafe meets 20 of the 29 requirements in 21 CFR Part 11 Subparts B and C directly in the software. One more (11.300(c), lost credentials) is shared. The remaining eight are procedures that sit with your organization or do not apply to a closed, password-based system. This page shows how AuditSafe handles each one, what your organization still owns, and how the same controls map to EU Annex 11.

Regulated labs and instrument partners ask us the same two questions: exactly what does AuditSafe cover, and exactly which points of Part 11 does it comply with? The answers are below, clause by clause. If you need them as a signed document for a supplier audit, request the AuditSafe Regulatory Compliance Guide.

At a glance: what AuditSafe covers

Every one of the 29 requirements in 21 CFR Part 11 Subparts B and C, grouped by area. The full matrix explains each one.

AreaAuditSafe complies (in the software)SharedYour organization owns, or not applicable
System controls: validation, copies, record protection, access, audit trails, workflow and authority checks, documentation11.10(a), (b), (c), (d), (e), (f), (g), (k)11.10(h) hardware qualification, 11.10(i) training, 11.10(j) accountability policy
Open systems11.30 does not apply: AuditSafe is a closed system
Signature content and linking to records11.50(a), 11.50(b), 11.70
Signature uniqueness and certification11.100(a)11.100(b) identity verification, 11.100(c) FDA certification letter
Signature components and use11.200(a)(1), (a)(1)(i), (a)(1)(ii), (a)(2), (a)(3)11.200(b) does not apply: no biometric signatures
User ID and password controls11.300(a), (b), (d)11.300(c) lost or compromised credentials11.300(e) does not apply: no tokens or cards
Total2018

Nothing in the right-hand column is a gap in AuditSafe. Those requirements are met by your organization's procedures, or they cover technology (open systems, biometrics, tokens) that AuditSafe does not use.

Using AuditSafe in your lab? The left-hand column covers your instruments, Excel, third-party software and TotalLab software as soon as they run inside AuditSafe. The right-hand column is what your SOPs and validation cover.

Instrument maker or software developer? Read the left-hand column as what your product gains when AuditSafe is built in. We take the software or instrument you already have and make it compliant, without you building audit trails, electronic signatures or user management yourself. The right-hand column stays with the regulated lab that buys your product, as it would for any Part 11 system. That is how World Precision Instruments took its EVOM Auto from research use only to a global CDMO's GMP site: read the WPI story, or see how AuditSafe OEM integration works.

Quick answers: how AuditSafe handles the common questions

How does AuditSafe handle audit trails?

AuditSafe builds the audit trail automatically from the moment data enters the system. Every action is time-stamped and recorded with the user who took it, and AuditSafe keeps the project data as it stood at each timestamp. Users cannot switch the audit trail off or edit it. Check-ins record a reason, and changes in Excel are logged cell by cell with the old and new values. Audit trails export as PDF for read-only inspection. (21 CFR 11.10(e), Annex 11 §9 and §12.4)

Can anyone delete data in AuditSafe?

No. AuditSafe has no function for deleting data. Each commit creates a new revision, earlier revisions stay available read-only, and raw files sit in a protected folder. A change never overwrites what was recorded before it. (11.10(c), 11.10(e))

How are electronic signatures applied and linked to the record?

A user needs sign-off privileges to sign, and signing requires the password to be entered again. Each signature shows the signer's printed name, the date and time, and the meaning of the signature (for example, review or approval). Once applied, a signature is bound to that record inside AuditSafe. No user, including an administrator, can edit, delete, copy or move it to another record. Signatures appear in human-readable form in the PDF audit report. (11.50, 11.70, Annex 11 §14)

How do you control who can access the system and what they can do?

Every user has an individual account with a unique username and a password. Duplicate usernames are blocked. Role-based permissions separate analysts, reviewers and administrators, and actions such as sign-off need an extra privilege. Accounts can come from Active Directory (LDAP), OpenID or AuditSafe's own user list. Inactive sessions time out after a period your administrator sets, and the user must log in again. (11.10(d), 11.10(g), 11.100(a), Annex 11 §12)

What happens when a user has left or is on leave and someone needs their account?

AuditSafe has an emergency login. Two users with the required privileges must act together to open the absent user's account, so no single person can use someone else's signature. The access is written to the system audit trail, and every action taken in that session is tagged with both users. (11.200(a)(3))

How do you manage password expiry and failed logins?

Administrators can set timed password expiry, force a password change and deactivate accounts. If you sign in through Active Directory, your directory's password, expiry, lockout and MFA rules apply. Every failed login attempt is recorded in the system audit trail, and a warning count appears on the Users tab of the AuditSafe server webpage so your administrators can investigate. (11.300(b), 11.300(d))

Can users work outside the approved workflow?

No. Workflows are defined in the software, users cannot take actions outside them, and every step appears in the audit trail. (11.10(f))

How do inspectors get copies of records?

AuditSafe keeps every revision of a project and generates date- and time-stamped audit trails. Reports, original files and audit trails can be exported in their native formats and as PDF, so an inspector can review a human-readable copy. (11.10(b), Annex 11 §8)

How are backups and archiving handled?

All AuditSafe records sit in one secure folder and one SQLite database file on your AuditSafe server. Server administrators can include them in your existing enterprise backup or copy revisions to another storage system for archiving. Your IT team owns the backup schedule and restore testing; TotalLab provides guidance. (11.10(c), Annex 11 §7 and §17)

Does AuditSafe cover software that isn't from TotalLab?

Yes. Any Windows program that launches from an executable can run inside AuditSafe, including Microsoft Excel, instrument control software and third-party analysis packages. AuditSafe tracks the files the program saves without changing the program. That is how one AuditSafe system brings a mix of instruments and software under the same audit trail, signatures and user management, so your team validates and learns one compliance system instead of several.

21 CFR Part 11 compliance matrix

Status key: Compliant means the AuditSafe software provides the control. Partially compliant means AuditSafe provides the tools and your procedures complete the control. Customer procedure and Not applicable mean the requirement is met outside the software or does not apply to AuditSafe.

Subpart B: Electronic records

ClauseWhat it requiresHow AuditSafe meets itYour organizationStatus
11.10(a)Validated systems that are accurate, reliable and can show invalid or altered recordsAll TotalLab software is tested and built under a documented life-cycle process. TotalLab supplies an IQ/OQ protocol and runs it with you, remotely or on site.Validate the system for its intended use in your environment (URS, risk assessment, PQ).Compliant
11.10(b)Accurate, complete copies in human-readable and electronic form for inspectionHistorical copies of projects are kept as they change, with read-only access to earlier revisions. Date- and time-stamped audit trails export as PDF.Restrict access to the AuditSafe system.Compliant
11.10(c)Records protected and retrievable for the whole retention periodRecords are stored on the AuditSafe server; each commit creates a new revision. Users open read-only copies of revisions through the AuditSafe client.Restrict access to the server and secure folder, set retention periods for your domain, and back up project data.Compliant
11.10(d)System access limited to authorized individualsAccess requires individual username and password credentials.Decide who has access and with which permissions.Compliant
11.10(e)Secure, computer-generated, time-stamped audit trails that never obscure earlier entriesTime-stamped records of every user action, with the user and the project data at each timestamp. Data is never deleted.Keep records for the defined retention period, including through hardware, software and operating system updates. Lock and synchronize the server clock through your domain policy.Compliant
11.10(f)Operational checks that enforce the permitted sequence of stepsWorkflows are defined in the software and users cannot act outside them. Actions are visible in the audit trail.Validate the software for its intended purpose.Compliant
11.10(g)Authority checks on who can use the system, sign, or alter a recordCredentials limit access; extra privileges are needed for actions such as sign-off, which also requires password re-entry. Sessions time out after a period set on the server.Grant access and privileges to individual users.Compliant
11.10(h)Device checks on the validity of data input sourcesUsers can visually check the text and files they add to AuditSafe.Qualify your hardware.Not applicable
11.10(i)People who build, maintain or use the system are trained and qualifiedTotalLab staff have extensive, relevant experience in development, testing and the other functions they are responsible for.Train and qualify your users.Not applicable
11.10(j)Written policies that hold people accountable for their electronic signaturesAuditSafe supports this by limiting access to records and recording each person's actions.Write and enforce the accountability policy.Customer procedure
11.10(k)Control over system documentation and its revisionsUser documentation ships with the installation package, with updated versions and signed release notes for each new release.Control supplied manuals and your operation and maintenance procedures internally.Compliant
11.30Extra controls for open systemsAuditSafe is a closed system under the definition in 11.3(b)(4), so this section does not apply.None.Not applicable
11.50(a)Signed records show the signer's printed name, date and time, and meaningAudit reports show all three, clearly associated with each signature.Configure user names and the correct privileges for each user.Compliant
11.50(b)Signature details are controlled like records and included in human-readable outputSignatures are linked to their records inside the software and cannot be edited, deleted or reassigned. They appear in PDF audit reports.Configure user names and privileges.Compliant
11.70Signatures linked to records so they cannot be excised, copied or transferredSignatures are permanently attached within AuditSafe and no user can delete, alter or transfer them. Only privileged users can sign.Assign the correct privileges. You cannot alter how signatures are attached.Compliant

Subpart C: Electronic signatures

ClauseWhat it requiresHow AuditSafe meets itYour organizationStatus
11.100(a)Each signature unique to one person, never reused or reassignedEach individual gets their own username and password pair; duplicate usernames are blocked.Keep procedures that ensure credentials stay unique.Compliant
11.100(b)Identity verified before a signature is issuedRelies on your internal procedures.Verify each person's identity before creating their account.Customer procedure
11.100(c)Certification to FDA that electronic signatures are legally bindingRelies on your internal procedures.Submit the signed certification letter to FDA before or when you start using electronic signatures.Customer procedure
11.200(a)(1)Two distinct components, such as user ID and passwordCredentials are a unique user identifier plus a secret password.Create user credentials.Compliant
11.200(a)(1)(i)In one continuous session, first signing uses all components; later signings use at least one private componentUsers enter both components on first access. Later signatures in the session require the password.Configure electronic signatures for users.Compliant
11.200(a)(1)(ii)Signings outside a continuous session use all componentsAfter logout or timeout, users must enter username and password again; signatures then require the password.Configure electronic signatures for users.Compliant
11.200(a)(2)Signatures used only by their genuine ownersAdministrators configure user access and duplicate user IDs are not allowed.Configure Windows and AuditSafe accounts correctly.Compliant
11.200(a)(3)Using someone else's signature requires two or more people to collaborateEmergency login needs two users with the required privileges. The access is logged and every action in that session is tagged with both users.Assign emergency-access privileges to suitable people (for example, supervisors) under your policy.Compliant
11.200(b)Biometric signatures usable only by their ownersAuditSafe does not use biometric signatures.None.Not applicable
11.300(a)No two people share the same ID and password combinationAuditSafe prevents duplicate usernames.Assign each user ID to one person only.Compliant
11.300(b)IDs and passwords checked, recalled or revised periodicallyTimed password expiry, forced password expiry and account deactivation. Directory password policies apply when you use Active Directory.Configure expiry rules to match your policy.Compliant
11.300(c)Lost or compromised credentials deauthorized and replaced under controlAuditSafe supports deactivating accounts and creating new ones.Run the loss-management procedure for account creation and deactivation.Partially compliant
11.300(d)Safeguards that detect and report unauthorized use attemptsEvery failed login is recorded in the system audit trail, with a warning count on the Users tab of the server webpage.Configure accounts and review failed-login warnings under your security procedures.Compliant
11.300(e)Testing of tokens or cards that carry credentialsAuditSafe does not use tokens or cards.Generate IDs and passwords under your own procedures.Not applicable

Summary: 20 compliant, 1 partially compliant, 3 customer procedures, 5 not applicable. Source: AuditSafe Regulatory Compliance Guide v1.1, TotalLab.

EU Annex 11 mapping

Part 11 is a binding FDA regulation. Annex 11 is the EU GMP guideline for computerized systems and covers similar ground with more weight on lifecycle and risk management. This table maps AuditSafe to the 2011 Annex 11 clauses that apply to the software. For how the two rules differ, and what the 2025 draft revision changes, read EU Annex 11 vs 21 CFR Part 11.

Annex 11 clause Topic How AuditSafe meets it
§4 Validation TotalLab supplies an IQ/OQ protocol and executes it with you. AuditSafe with off-the-shelf software is GAMP 5 Category 3, which keeps validation effort well below that of a custom system.
§7 Data storage and backup Records sit in one secure folder and one SQLite database file, covered by your enterprise backup.
§8 Printouts Reports, original files and audit trails export in native formats and as PDF.
§9 Audit trails Date- and time-stamped audit trail of every change, with the user and a reason at check-in. Always on, not editable, exportable as PDF.
§10 Change and configuration management Updates install only when you choose. Signed release notes let QA decide what to retest.
§12.1 Security and access Access limited to authorized users by username and password; extra privileges needed for actions such as sign-off; configurable inactivity timeout.
§12.4 Operator identity on data changes Every entry and change records the user and the date and time, with the project data at each timestamp.
§14 Electronic signatures Signatures are restricted to privileged users, permanently linked to their record, and include the date and time applied.
§17 Archiving Project revisions stay on the server and administrators can copy them to another storage system.

What stays with your organization

No software is 21 CFR Part 11 compliant on its own. Compliance comes from a validated system plus your procedures. AuditSafe provides the technical controls; your organization owns the rest:

  • Validating AuditSafe for its intended use (URS, risk assessment, PQ) and any spreadsheet templates or third-party software you run inside it
  • Deciding who gets access and which privileges, and verifying each person's identity first
  • Training users and writing the policy that holds people accountable for their signatures
  • Certifying your use of electronic signatures to FDA
  • Setting retention periods, running backups and restore tests, and keeping the server clock locked and synchronized
  • Qualifying hardware and controlling your internal documents and SOPs

TotalLab helps with each of these. We return a signed, line-by-line response to your URS or supplier questionnaire, supply and run the IQ/OQ, train analysts, reviewers and administrators, and support your supplier audit. See exactly what we hand your validation team.

Frequently asked questions

Is AuditSafe 21 CFR Part 11 compliant?

AuditSafe provides the technical controls Part 11 requires: audit trails, electronic signatures, access control and password management. It meets 20 of the 29 requirements in Subparts B and C directly. Like any software, it becomes part of a compliant system once you validate it and run it under your own procedures.

Which Part 11 requirements are the customer's responsibility?

Identity verification (11.100(b)), the FDA certification letter (11.100(c)), accountability policies (11.10(j)), hardware qualification (11.10(h)), user training (11.10(i)) and the loss-management procedure for credentials (11.300(c)). You also validate the system and set retention and backup policies.

Is AuditSafe an open or a closed system under Part 11?

Closed. AuditSafe is a closed system under 21 CFR 11.3(b)(4), so the extra open-system controls in 11.30 do not apply.

Does AuditSafe record the reason for a change?

Yes. A reason is recorded when work is checked in, alongside the user, date and time.

Does AuditSafe work with Active Directory?

Yes. AuditSafe supports Active Directory (LDAP), OpenID or its own internal accounts. With a directory, your existing password, expiry, lockout and MFA rules apply.

What GAMP 5 category is AuditSafe?

AuditSafe with off-the-shelf software is GAMP 5 Category 3, a configurable off-the-shelf product.

Does AuditSafe store data in the cloud?

No. AuditSafe runs on premises on your own server or in Docker, and works fully offline, including license activation. TotalLab never holds your data.

Can I get this mapping as a signed document for our supplier audit?

Yes. Request the AuditSafe Regulatory Compliance Guide, or send us your URS and we will return it completed and signed, with each requirement accepted or rejected and a comment.

References

  1. 21 CFR Part 11, Electronic Records; Electronic Signatures. US Code of Federal Regulations. https://www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-11
  2. EudraLex Volume 4, Annex 11: Computerised Systems (2011). European Commission. https://health.ec.europa.eu/system/files/2016-11/annex11_01-2011_en_0.pdf
  3. AuditSafe Regulatory Compliance Guide v1.1. TotalLab Ltd, 2026. Available on request.

This page gives TotalLab's interpretation of 21 CFR Part 11 and EU Annex 11. TotalLab does not represent any regulator and is not a legal practitioner; use it alongside your own regulatory and legal advice. Organizations developing medical devices should also refer to ISO 13485:2016 clause 4.1.6, ISO/TR 80002-2 and FDA's General Principles of Software Validation (2002).

See every control working on your own data

One AuditSafe system brings your instruments, Excel and analysis software under one audit trail, one set of signatures and one validation. Book a 30-minute demo and we will walk through the clauses that matter most to your next audit.

Follow a project from raw data to e-signature →

AuditSafeVendor-neutral overlay adding audit trails, e-signatures and access control to existing lab software.

Your software won't do what you need? Ask TotalLab →Tell us the problem; we reply within two working days.