Table of contents
At a glance
Can DocuWare be used for controlled GMP documents?
DocuWare can support controlled GMP documents when the configured process demonstrably provides the controls required for its intended use. Document management, versioning and workflows contribute to those controls. Test approval and effective status, access to the right version, critical index changes, signature handovers and retention. A version status or approval workflow alone does not establish suitability.
- Record the cloud, on-premises, release, and specifically used client in the inspection setup.
- Separate the document content, index data, and professional release status, and jointly evaluate them.
- Versioning, trash functionality, and long-term archiving serve distinct purposes.
- Include signature service and interfaces including licensing scope and return pathway.
Which DocuWare variant is being assessed?
DocuWare provides document management and document-based workflows as a cloud and on-premises system. A published reference version is 7.14. The manufacturer's information from September 2026 describes the rollout of Cloud 7.15 as a phased update starting mid-October and lasting approximately two months. Consequently, the existing documentation page detailing new features does not yet reflect the activation of this version within your organization.
Capture the operating model, release or customer standing, used client, archives, workflow designer, desktop components, and integrations. The documentation should distinguish between the classic and the new cloud client; for example, manual versioning is not yet supported in the new client. Review the interface and functions that your staff actually use, rather than mixing instructions from different versions.
The reference implementation includes guided SOPs and associated records in human medicinal product manufacturing. DocuWare is not to be classified as a fully implemented pharmaceutical QMS. Whether features such as training management, deviations, or CAPA are included in your solution must be individually determined based on the agreed implementation. For FDA-related electronic records and signatures, the Part 11 applicability scope must also be established.
Four levels of document control securely integrate
Begin with a document model prior to configuring release steps. Distinguish between the file itself, descriptive metadata, technical versioning, and subject-matter approval. Chapter 4 requires, among other things, unique identifiability, authorized approval, and a clearly defined expiry date for instruction documents. How this is implemented in DocuWare represents a specific configuration task.
The work matrix serves as a draft for your requirements. Define for each field and status who is authorized to set it and under what conditions it may be changed. Primarily describe the transitions: a rejection must not have the same consequence as an approval; a future approved version must not prematurely override a currently valid instruction.
| Level | To be defined in the project | Verifiable effect |
|---|---|---|
| Document content | Which file or compilation constitutes the specific SOP version? | The released and actually displayed content is consistent. |
| Document identity | How are SOP number, document ID, and subject matter revision linked? | A decision can be assigned to a clear formulation. |
| System data index | Which values control search, validity, responsibility, or retention? | Unauthorized changes neither alter access nor status undetected. |
| Workflow | Who reviews and approves, and what occurs upon rejection or substitution? | Only the defined positive release permits the next state. |
| Effectiveness | When does the version apply, and what must be completed beforehand? | As of the cut-off date, the previously intended version remains available. |
| History and Storage | Which prior contents and decision records remain required? | Previous decisions are traceable to the original documentation. |
Technically current is not automatically professionally valid
The archival documentation describes technical statuses such as Current, In Progress, and Out of Date. Furthermore, the document ID remains unchanged across versions of a document. Therefore, the document ID alone should not be used as evidence of which version has been approved. The assignment must include the relevant version or revision status.
When the automated versioning feature is enabled, new document versions are generated upon editing. The documentation for the new Cloud client also describes recovery options using either the original index values or solely the document content. This choice may have professional implications: an older content version and current metadata might no longer be consistent.
Define how users can access the current SOP during an ongoing revision. Work with your system partner to verify that your document model, user permissions, and release logic accurately represent this state. Test search results, stored links, print output, and associated applications. A new technical version must not become a binding work instruction solely due to versioning.
Treat index fields and histories as part of the control process
Index values are more than search aids as soon as they carry, for example, document type, release status or validity date. The DocuWare documentation describes that changed index values of the current version are not automatically transferred to older versions. Thus, it is also necessary to check whether historical views reflect the context at that time correctly.
Investigate changes by user, workflow, and integration separately. A UI with hidden fields is insufficient evidence that the same value cannot be modified through an alternative authorized pathway. Define for critical fields user rights, allowable values, and traceable change records. Also verify whether an incorrect document type inadvertently triggers a different retention rule.
DocuWare logs audit reports at document, archive, organizational, and system levels, along with corresponding access rights and CSV exports. Clarify which events your configuration actually captures and who reviews them. A meaningful test involves applying a predefined change and verifying the resulting entry. During evaluation, inspect author, timestamp, and professionally relevant details, rather than treating the mere existence of a report as sufficient evidence of completeness.
Review the release workflow up to workplace usage
Workflow Manager integrates process design with assigned tasks within the Web Client. However, you must define the operational SOP logic yourself: author role, review, approval, rejection, return for editing, and controlled delegation. Clarify the difference between technical administration and functional release authorization.
Consider the period following approval. Must training be conducted prior to efficacy? Which positions require printouts? How are old distributed containers handled? The required implementation may extend beyond the DocuWare workflow. Completion of a task entry does not automatically confirm that all affected personnel are using the correct instructions.
Review changes to ongoing processes with particular diligence. If a document or a critical assignment is modified during processing, the release must remain clearly aligned with the reviewed content. Define when a process must be restarted or re-evaluated. This is a requirement for your workflow, not a claimed universal default setting in DocuWare.
Signatory partners and interfaces form part of the validation evidence.
The DocuWare Signature Service integrates external providers such as Validated ID or DocuSign as a workflow web service. According to the vendor, documents are transmitted and returned with signed documents together with the signature certificate. However, this does not constitute confirmation that your specific identity verification, signature validity, and linkage fully meet all applicable requirements.
The public license overview up to version 7.14 distinguishes cloud and on-premises: For on-premises, additional licenses for signature integration and workflow managers are called; also, a separate client license for the service and signature volume is to be considered. Let the actual scope, including external costs and responsibilities, confirm.
Investigate a failed or delayed return flow: Which document remains locked, which process is repeated, and how are duplicates identified? URL integrations are also relevant. DocuWare, for example, can integrate Viewers, lists, and document histories into other applications. A link to the allegedly current SOP must still display the technically intended version. A visible stamp cannot be equated with an appropriate electronic signature without further verification.
Sources: [7] [8] [9] [14] [13]
Plan separate storage, trash bin, and backup procedures
DocuWare provides configurable retention rules. The appropriate retention period, start date, and potential reasons for extended retention stem, however, from your document type and applicable requirements. Do not confuse the configuration of a retention rule with an already justified retention strategy. Also verify the selection filter using intentionally incorrect or missing index values.
For the classic client, DocuWare provides a trash bin with automatic deletion after 30 days; authorized users can perform permanent deletion prior to this period. According to the documentation, document restoration does not trigger any workflows, automations, or notifications. Therefore, a mistakenly deleted document must be professionally reclassified after restoration before it can be considered a valid instruction for reuse.
Versioning alone does not prevent deletion of the entire document by appropriately authorized users. Therefore, retention, deletion rights, and recovery responsibilities must be jointly defined. For both cloud and on-premises environments, specific backup strategies, recovery procedures, and ownership responsibilities must be explicitly agreed upon. A trash bin does not ensure long-term readability nor provide full protection against complete system failure; during migration, content, metadata, and required traceability evidence must be considered together.
Example: SOP revision with future expiration date
This example serves as a working guide, not a completed DocuWare test. A GMP SOP is revised from Revision 3 to Revision 4. Revision 3 remains valid until the specified date. Revision 4 requires review and approval; an external signature will be obtained through the established service.
Acceptance criteria are defined in advance of testing with Quality Assurance and the relevant department. Representative user roles and the actual intended search and access paths shall be used. The matrix evaluates the combined impact of file data, metadata, and process; it does not specify a particular technical architecture.
| Test approach | Expected technical result | Suitable evidence |
|---|---|---|
| Edit draft version 4 | Readers continue to receive the current revision 3. | Comparison of search, workplace link, and authorized roles. |
| Reject the inspection | The new version is not effective. | Decision, resulting status and renewed read access. |
| Unauthorized modification of release index | No unauthorized publication or concealed status change. | Attempt, permissions and resulting history entry. |
| Interrupt signature loop | A technical error is not considered approval. | Defect state, repetition, and assignment of the signed document. |
| Date of attainment reached | The intended release version will be available. | Content, revision, date, and reader view comparison. |
| Restore an earlier version | Content and index values are assessed; no unintended validity. | Selected Restore Type and controlled status decision. |
| Retrieve test document from paper bin | Required technical evaluation is initiated despite the absence of workflow initiation. | Restore, post-processed procedure and documented closure. |
KMU-Project: Responsible Parties, Documentation, and Modifications
Name a subject-matter document owner responsible in Quality Assurance, IT, and the assigned DocuWare partner. External service providers may be added for signature purposes. Roles may overlap in a small company; however, responsibility for requirements, configuration, review, and release should remain clearly defined.
Prepare document types, life cycles, roles, critical index fields, and distribution pathways. Then request appropriate architecture and configuration documentation, available supplier certifications, and operational support information. Significant effort arises particularly due to inconsistent legacy systems, numerous custom workflows, signature routes, and integrations. The existence of an existing license provides little insight into this clarification need. Explicitly plan for departmental time and deviation handling.
Maintain the approved operational state. Changes to workflow, client applications, or identity services may impact usage. A specific example is the announced SSO adjustment for Cloud 7.15; the vendor identifies a required preparation prior to the customer update. Evaluate such notifications deliberately and review affected processes. The general system release remains a justified business decision.
Checklist for Your DocuWare Audit Scope
Use this workbook for the joint project kickoff. For each open question, assign a responsible party and a verifiable outcome. Start with a critical document type and expand the scope once the interaction among content, metadata, and process is understood.
- Operational model, release, client, and installed components documentation.
- Document types and GxP applicability are justified by demarcation.
- Assign a unique identifier, revision, release, and date of validity to each document.
- Secure critical index fields and all change pathways with appropriate rights.
- Draft, rejection, representation, and publication to be fully played through.
- Valid version regarding search, linking, and workplace verification.
- Include signature partner, licensing scope, return and error handling.
- Review entries in history for content, access, and appropriate evaluation.
- Plan separately for storage, deletion, recycle bin, and restoration.
- Evaluate deviations, define the scope for release, and assign subsequent changes.
Project experience and collaboration
Trace an SOP revision through to the point of use
To define the DocuWare test scope, we examine an actual SOP revision with document owners, QA and IT. We trace approval, intended effective date and workplace access, including critical index changes and any signature handovers. A well-defined approval route may need only a few targeted additions to existing evidence. If multiple repositories, paper workflows or interfaces are involved, we first map the entire document path. Requirements and tests then reflect your actual operations.
Frequent Questions About DocuWare in the GMP Process
Is DocuWare a ready-made pharmaceutical QMS?
DocuWare provides document management and workflow technology. A pharmaceutical lifecycle, including your defined roles, release authorizations, and usage rules, must be specifically implemented and validated. Additional features such as training management or CAPA should not be derived from the product name. The key factor is the agreed-upon and actually implemented solution for your intended use.
Do the same evidence apply to both cloud and on-premises systems?
The technical implementation and operational responsibility may differ, even if the intended objectives are the same. The specific client version used must also be documented. Manufacturer documentation, for example, describes different functional versions for the classic and new cloud client. Therefore, validation evidence must be based on the specific combination; a test of an alternative variant is not automatically sufficient.
How do we determine the correct DocuWare release for validation?
The documentation includes the actually operated customer or installation site, together with the client, modules, and configuration. DocuWare distributes cloud updates in a phased manner and provides the customer with their individual update schedule. Therefore, the publication of a release or the launch of a new documentation page does not constitute activation within your organization. Please determine the current state of operation and assign the appropriate documentation accordingly.
Does "Current" mean that a SOP has been released?
No. Current indicates the technical version status. The professional approval, the approved version, and the expiry date must be clearly defined in your document model. Pay particular attention to what readers see during the editing of a new version. The current technical version must not inadvertently replace the still valid work instruction.
What role do index data play in validation?
Index data can control search, assignment, release status, or retention. The significance and changes to these data are just as relevant as the content of the file itself. Verify allowed values, rights, and automated write procedures. Additionally, note that modified index data from the current version do not automatically update older versions as specified in the documentation.
Can version control replace immutable retention?
No. The manufacturer states that duly authorized users can delete a document including its versions. Versioning makes edit states traceable, but does not replace an appropriate rights and retention policy. Establish time limits, protection against premature deletion, and future readability tailored to the document type.
Does release automatically resume after restoration?
For the recovery from the classic client's recycle bin, DocuWare explicitly does not support the initiation of workflows, automations, or notifications. Therefore, regulate the professional handling of such documents. A recovery action must neither implicitly re-establish an older SOP as valid nor bypass necessary checks. Other recovery methods must be evaluated separately.
Is the signing service already fully included in every license?
The published overview distinguishes between cloud and on-premises deployments and lists additional requirements. These include, depending on the variant, signature integration, workflow manager, a separate client license for the service, and external signature volume. Confirm the current scope of the agreement. Furthermore, a technically integrated provider does not necessarily validate the suitability of your specific signature workflow.
Which assessment is most justified to begin with an existing installation?
Select a key SOP undergoing active revision and verify actual user access. Compare file, revision, index values, and release documentation through standard work processes. Include one rejection and one unauthorized change attempt. This proposed approach provides concrete references for the risk-based scope of further evaluation.
What remains despite cloud operation within the company?
Your organisation must define the intended use, professional guidelines, responsibilities, and acceptance criteria. This includes appropriate roles, document distribution, training, and evaluation of changes. Manufacturers and partners can support operations and implementation. Review their documentation for scope and supplement the usage evidence, which can only be assessed by your organisation.
Sources and review date
Status: October 6, 2026. Manufacturer information distinguishes between cloud, on-premises, and client variants. Version 7.14 is a published reference release; the cloud rollout 7.15 is announced for research purposes. Regulatory reference application: Human Medicinal Product-GMP; FDA requirements apply only within the relevant scope. Matrices, example, and checklist are standalone work aids.
- DocuWare: Version 7.14 is now available
- DocuWare: SSO and Tiered Cloud Update 7.15, September 2026
- DocuWare: File cabinets – general
- DocuWare: Version control in the new Cloud client
- DocuWare: Workflow Manager – Overview
- DocuWare: Audit reports
- DocuWare: Electronic signatures with DocuWare
- DocuWare: Licensing Requirements for Electronic Signature Services
- DocuWare: Introduction URL integration
- DocuWare: Deletion policies
- DocuWare: Trash Bin – Restoring Documents
- European Commission: EU GMP Chapter 4 – Documentation, January 2011
- European Commission: EU GMP Annex 11, January 2011 revision
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic Signatures
Sources checked: .
Ensure traceability of the internal document process in DocuWare
We support you in integrating the document model, workflow, and technical evidence. Daniel Herrmann Consulting begins with your specific SOPs, roles, and existing documentation.
- 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.

