Table of contents
At a glance
Does an eIDAS-compliant signature automatically meet 21 CFR Part 11?
No. eIDAS and Part 11 have different scopes and objectives. Under Article 25(2) of the eIDAS Regulation, a qualified electronic signature has the same legal effect as a handwritten signature. This does not give the system or process blanket Part 11 approval. Assess the relevant recordkeeping obligations, system controls, identity, signature meaning, record link and actual approved workflow.
First determine which record is signed off
Begin with the process and the leading documentation. Is a SOP approved, a test result confirmed, or another legally relevant statement issued? Verify which regulations and form requirements actually apply. Part 11 specifically relates to electronic records under applicable FDA record-keeping obligations or specific electronic submissions. The use of signature software alone does not constitute a Part 11 process.
For the EU-GMP application of computerized systems, Annex 11 must be considered separately. Other GxP areas and legal issues may have distinct requirements. Therefore, capture record type, intended use, stakeholders, jurisdiction, and required validation evidence. This guide outlines the differentiation between system and process evaluation. It does not determine individual contractual or form-related questions and does not replace the necessary legal review. A universal signature class for all enterprise documents would not constitute an appropriate starting point.
What eIDAS says about signature types and legal effect
The eIDAS Regulation distinguishes between electronic, advanced, and qualified electronic signatures. Article 26 outlines requirements for an advanced electronic signature, including unique attribution, identifiability, and detectability of subsequent modifications to the associated data. A qualified electronic signature has additional requirements. Article 25(2) assigns it the same legal effect as a handwritten signature. This statement is not extended to constitute a general technical validation confirmation.
Article 25 paragraph 1 simultaneously provides that an electronic signature shall not lose legal effect or admissibility in evidence solely because of its electronic nature or the absence of qualification. However, this does not imply that any arbitrary electronic confirmation automatically fulfils any required form or any GxP process. Distinguish legal effect, admissibility in evidence, specific form requirements, and operational suitability. The regulation has been amended; refer to the designated consolidated text and the currently applicable provisions.
Sources: [3]
Part 11 evaluates more than just the signature mechanism
Part 11 contains requirements for electronic records and signatures within its scope of application, including system controls and suitability of the systems used. Sections 11.50 and 11.70 address, among other things, visible signature information and its linkage to the corresponding record. Therefore, the name, timestamp, and significance of a signature are distinct audit objectives from the simple display "certificate valid." Identity and access controls must align with the actual signature process employed.
The signature may, for example, represent a review, approval, or another predefined action. The user must be able to identify the action they are performing and the content to which it relates. Assess whether post hoc content modifications are detectable and how a revised status is reprocessed. A signature graphic or a manually entered name does not automatically demonstrate these attributes. Similarly, a technically robust signature service does not guarantee full control over a preceding or succeeding system.
Sources: [1]
Annex 11 as an additional process perspective
For electronic signatures, Annex 11 Section 14 mentions, among other things, their connection to the recording and information on date and time as well as their corresponding effect in the corporate context. These requirements are considered in connection with the other system controls. The verification scope does not end at the signature dialog. Document version, responsibility, workflow, storage and later readability can influence the statement of a release. Therefore, check the entire relevant chain.
eIDAS, Annex 11, and Part 11 are not to be considered interchangeable quality seals. Depending on the specific application, different requirements may be relevant simultaneously. The following internal matrix assists in aligning the applicable requirements. It is neither a comprehensive legal comparison nor a general certification framework. Ultimately, the key factor remains the traceable evaluation of the actually applicable requirements and the specific system, including its configuration.
| Assessment question | Typical source or perspective | Required concrete evidence |
|---|---|---|
| What legal signature type or form is required? | eIDAS and other relevant regulatory requirements | Document the rationale for classifying the transaction |
| Is Part 11 applicable to electronic records? | 21 CFR 11.1 and related recordkeeping obligations | Assignment of Record and Intended Use |
| What does the signatory confirm? | Process definition and significance of signature | Clear dialogue and unambiguous recorded actions |
| Which content was signed off? | Record binding and version control | Identifiable location including required appendices |
| Is the responsible person clearly identified? | Identity, account, and access procedures | Appropriate controls over the actual execution process |
| Is the signature later understandable and verifiable? | Storage and System Operation | Complete, legible connection from record and signature |
Sources: [2]
Example: correct signature, incorrect document status
A SOP version 3 is submitted to a signature service. The responsible reviewer signs exactly this file. However, in the document portal, an updated version 4 is now present under a very similar file name. The interface continues to display a green release status from the previous process. The original signature may still be technically valid; it does not automatically reflect the new file. The error lies in the assignment and in the process handover.
The audit case therefore traces the content from the source system through transfer, handover, and back to publication. It includes a targeted modification after signature and a swapped appendix. A clear separation of roles and appropriate reprocessing is expected. The example does not indicate a weakness of any specific supplier. It illustrates why a statement regarding the signature function alone does not constitute complete release of the entire document process.
Design a verifiable signature pathway
First, define the approved scope: document types, roles, signature sequence, significance, and versions. Then review the normal workflow and key exceptions. What occurs in case of rejection, expiration of an invitation, representation, or interrupted session? Can the wrong individual perform a procedure? Is a previously issued signature traceable after withdrawal or following a new document version? The expected handling must be defined prior to testing.
Consider package and annex boundaries. A signed title page does not automatically render compelling evidence for any subsequently archived annex. Verify which components the signature actually binds and how the user recognizes this binding. Consolidated releases or multiple signatures must have appropriate reference to individual records. A green overall status must not conceal any open or rejected components. The technical design aligns with the professionally defined release purpose.
Test separate identity, login, and signature actions
A successful registration first addresses an access question. It is not automatically equivalent to an electronic signature applied to a specific document content. Evaluate the transition from session state to intentional signing action. Which identity is recorded? What authentication is confirmed? What authentication is required for the employed procedure and its scope of validity? Part 11 also distinguishes between biometric and non-biometric methods; therefore, general statements regarding any technical login would be inappropriate.
In addition, review role changes, deactivated accounts, and representatives. A technically available function must not automatically permit a professionally inappropriate authorization. Organizational permissions and technical access must operate in the intended manner. When an external identity or signature service is used, its capabilities and limitations shall be assessed. The user remains responsible for the suitability decision regarding their own regulated process.
Sources: [1]
Store and prepare for subsequent inspection.
Define the signature information and technical justifications required for subsequent evaluation. Review the output for readers, auditors, and potentially receiving systems. Any subsequent transfer or conversion must not inadvertently lose the required linkage. The required scope may include additional information beyond the document. A decorative signature block is not a substitute for the actual connection.
Consider what happens when access to the provider ends. Can you still use the required records and signature information? Which technical checks remain possible and what must a reviewer still be able to establish independently? Assess long-term cryptographic evidence for the specific case. Do not assume a certificate will remain available indefinitely. A controlled export and retrieval test can show what evidence the process actually needs.
Sources: [4]
Project experience and collaboration
Distinguish legal form requirements from the internal signature function
We start with the action to be signed and establish its operational meaning and required form with the people responsible. With IT, we then check which identity, version and declaration the signing process links together. Internal GMP approval may require a different assessment from an external transaction subject to formal requirements. Legal questions about form are assessed separately. We include export and subsequent retrieval so that a signature remains intelligible beyond the contract with a particular supplier.
Frequently asked questions about Distinguishing eIDAS and Part 11
Do we need a QES for each GMP batch release?
No. Annex 11, Section 14 requires electronic signatures to have the same legal effect as handwritten signatures within the organisation, a permanent link to the record, and inclusion of date and time. The specific eIDAS signature class is not prescribed. Whether additional form requirements apply to a particular action must be determined based on the relevant regulatory provisions.
Is a QES automatically compliant with Part 11?
No. The legal effect of eIDAS does not replace the assessment of Part 11 applicability and the other requirements relating to records, systems, and processes. Specifically evaluate identity, signature significance, record retention obligations, and required controls. A technically sound signature mechanism may still be integrated into an inadequately controlled end-to-end chain.
Can a simple electronic signature have legal effect?
Article 25 paragraph 1 protects electronic signatures from rejection solely on the grounds of their electronic form or lack of qualification. This is not a blanket assurance that every signature meets each specific form requirement. The particular process and other relevant provisions must be assessed individually.
Sources: [3]
Is a visible signature image sufficient in a PDF?
The image alone does not establish a clear identity, intentional action, or controlled linkage to the correct record. Review the actual creation and release process. An image may constitute part of the documentation; however, the required controls and evidence must be aligned with the signature trail used.
Must a modified document be re-signed?
If the content of the signed document changes, the previous signature only validates the state of the document at the time of signing. The updated version requires a new evaluation and release in accordance with your approval procedure. A mere format change without content modification must be assessed under the controlled change procedure. The linkage between the signature and the approved version must remain clearly traceable.
Can we retain all documentation solely with the signing supplier?
Only if necessary access, retention, readability, and the possibility of a supplier change can be demonstrably secured. Verify a controlled export together with the required context and subsequent retrieval. A contractual commitment alone does not demonstrate that the documentation remains usable following a system or service provider change.
Sources and review date
As of October 15, 2026. Regulatory provisions and GMP guidelines are to be separately categorized. Comparison table and review questions are to be provided as standalone reference tools; the specific form of any required action is to be determined separately.
- eCFR: 21 CFR Part 11, Electronic Records; Electronic SignaturesScope and in particular Sections 11.50, 11.70, 11.100, and 11.200. No general obligation arises solely from the use of a registration. Reviewed on 15.10.2026.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 15.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
- EU Regulation (EU) No 910/2014, consolidated textConsolidated German text as of 18.10.2024, serving as the current consolidated version in EUR-Lex. Articles 2, 3, 25, and 26 verified in original. PDF downloaded via the official browser interface.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
Sources checked: .
How we can support you
Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.
- 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.

