A GxP document management system (DMS) is software that controls regulated documents, such as SOPs, batch records, validation protocols and training records, through their whole life: draft, review, approval, effective use, periodic review, retirement and archiving. To be acceptable to an inspector it must keep a secure audit trail of every change, apply electronic signatures that meet 21 CFR Part 11 and EU GMP Annex 11, show only the current version at the point of use, and keep every record retrievable for its full retention period.
Many life sciences companies still run these documents on generic SharePoint sites, shared drives or older DMS platforms that were not built for regulated work. Document control then takes a lot of QA time and still produces inspection findings. This guide covers what a GxP DMS has to do, how to run one in the cloud, how to share controlled documents safely, the main products and the findings inspectors write most often.
What a GxP DMS must do that a generic DMS does not
A GxP DMS controls the document lifecycle and the approvals behind it, not just file versions. The controls below are the ones an inspector tests; Part 11 section 11.10 and Annex 11 clauses 9, 12 and 14 set most of them.
- Version control with full audit trail. Every document version — draft, review, approved, effective, superseded, obsolete — must be tracked with timestamps and user attribution. Generic DMS tools track file versions; GxP DMS must track document lifecycle states and the approvals that moved them between states.
- Controlled distribution. When a new SOP version becomes effective, the system must ensure that only the current version is available at the point of use, that all affected personnel are notified, and that acknowledgement of receipt is recorded. This is not a "notification feature" — it is a regulatory requirement under EU GMP Chapter 4.
- 21 CFR Part 11 electronic signatures. Document approvals must be signed with compliant e-signatures that capture identity, date/time, and meaning. A checkbox or "approve" button without re-authentication is not compliant.
- Review cycles. Every GxP document must be periodically reviewed — typically every two to three years — with the review decision (confirm, revise, obsolete) recorded and attributed.
- Retention and archival. Documents must be retained for their defined retention period and retrievable throughout that period. The DMS must enforce retention policies and prevent premature deletion.
GxP records management in the cloud
GxP records can be managed in a cloud DMS. No regulation requires on-premise storage; what the rules require is that the records stay protected, attributable and retrievable, and that the cloud provider's responsibilities are written down.
- A formal agreement with the provider. Annex 11 clause 3.1 requires formal agreements with third parties that provide, maintain or retain a computerised system or service, with clear statements of their responsibilities. For a cloud DMS that means hosting, backup, security patching, incident notification and data return at exit.
- Protected, readable data for the whole retention period. Part 11 section 11.10(c) asks for protection of records so they can be accurately and readily retrieved throughout the retention period. Annex 11 clause 7.1 adds that stored data should be checked for accessibility, readability and accuracy.
- Tested backups and restores. Annex 11 clause 7.2 asks for regular backups and for the ability to restore to be checked during validation and monitored periodically. Ask the provider for restore test evidence, not only a backup schedule.
- Archives that survive system changes. Annex 11 clause 17 says archived data should be checked for accessibility, readability and integrity, and that retrieval should be tested when the system changes. Plan for the day you leave the vendor. Our GxP archiving and data retention guide covers retention periods and migration.
Company size changes the scale of this work, not the requirements. Annex 11 clause 3.2 says the need for a supplier audit should be based on a risk assessment, so the depth of the check on a cloud provider follows the criticality of the records it holds.
Secure sharing of GxP documents with partners
Share controlled GxP documents from inside the controlled system, with named access and an audit trail, instead of emailing copies. Once a copy leaves the system, nobody can prove it is the current version or who has seen it.
- Named, limited access. Part 11 section 11.10(d) requires access limited to authorised individuals, and Annex 11 clause 12.1 asks for physical or logical controls to restrict access. Give each CRO, CDMO or consultant user their own account, scoped to the documents they need, and remove it when the work ends.
- Know whether the system is open. Part 11 defines an open system as one where access is not controlled by the people responsible for the records. If partners reach your records through a system you do not control, section 11.30 asks for extra measures to protect authenticity, integrity and, where needed, confidentiality, such as encryption.
- Controlled copies only. Read-only viewing, watermarked or logged downloads, and a record of who received which version keep shared copies inside your control.
For the full evaluation of sharing and collaboration tools, see how to evaluate GxP-compliant collaboration platforms.
The vendor landscape
GxP document management is sold in two forms: as a module of an eQMS suite and as a standalone DMS or content platform. The table gives a short view; confirm current capability with each vendor in a scripted demo.
| Platform | Type | Part 11 | Best For | Limitation |
|---|---|---|---|---|
| Cybroscape eQMS (Document Control M1) | Agentic eQMS + DMS | Full (hash-chained audit trail + re-auth e-sig) | Biotech, mid-market pharma, CDMOs | Newer platform; includes controlled print numbering, effective-date gating, version-bound training auto-assignment & Validation Bridge to GxP Copilot |
| Veeva Vault QualityDocs | Enterprise eQMS module | Full | Large pharma | Cost and effort at smaller scale |
| MasterControl Docs | Enterprise eQMS module | Full | Mid-to-large | Broad suite to configure |
| Qualio | Cloud-native eQMS | Strong | Startups, small biotech | Less deep workflow customisation |
| OpenText Documentum | Enterprise DMS | Full | Legacy-heavy orgs | Heavyweight, expensive |
| Egnyte | Cloud content platform | Partial | Hybrid cloud/on-prem | Not purpose-built for GxP |
The market splits between full eQMS suites (where document management is a module) and standalone DMS platforms. For most regulated companies, the eQMS module approach is preferable because it integrates document control with CAPA, deviation, and change control workflows. Standalone DMS makes sense only when you need document control before you are ready for a full eQMS — a common situation for early-stage biotechnology companies.
Where AI changes document management
AI changes who writes the first draft, not who approves it. Document management has always controlled documents people write; AI tools now draft documents that people review, sign and then control in the DMS like any other record.
Cybroscape Cybroscape TraceDraft drafts clinical documents such as clinical study reports and safety narratives, and links every sentence to the source data behind it. Cybroscape Cybroscape GxP Copilot drafts validation deliverables such as requirements, risk assessments, protocols and traceability matrices. Document control in Cybroscape eQMS takes SOPs, work instructions and forms through draft, review, approval, effective and retired states with Part 11 signatures. In each case the AI does the structural drafting and qualified people provide the judgement, review and approval.
Common 483 observations in document management
Test these five document control gaps before an inspector does: old versions still in use, missed periodic reviews, thin change history, uncontrolled copies and training that does not follow the new version.
- Obsolete documents available at point of use. The most common finding. The DMS must actively remove or flag superseded documents, not just mark them.
- Missing or incomplete document review cycles. Periodic reviews are not optional. The DMS must enforce review dates and escalate overdue reviews.
- Inadequate change history. Inspectors expect to see a full change history for every document, including the reason for each change. A simple version number is not sufficient.
- Uncontrolled copies. Printed or exported copies that bypass the DMS lifecycle. The system should log and control all distribution, including physical copies.
- Training not linked to document versions. When an SOP is revised, all affected personnel must be retrained on the new version. The DMS should trigger retraining workflows automatically.
audit readiness includes a document control mock-audit that tests for all five of these common findings before an inspector arrives.
Where to go next
Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.