Document Control
Enforced revision history, approval workflows and effective dates. Only the current approved version circulates; every superseded one stays retrievable.
The Compliance plan in full. For each module: what it does, and what it hands an auditor when they ask.

Controlled documents move through enforced states. Only the current approved revision is in circulation, superseded revisions stay retrievable, and the history records every content edit, change request and approval transition.
Training is tied to the documents and roles that require it, so the matrix stays true as documents change rather than being rebuilt by hand before an audit.
Deviations are numbered per workspace, risk-assessed at logging, investigated with structured root cause analysis, and dispositioned. Where the investigation warrants it, a CAPA is raised with the linkage preserved.
Corrective and preventive actions carry owned action items and due dates, and cannot close until an effectiveness review is complete. That review is the artefact auditors ask for and the one most commonly missing.
The audit programme, its plans, checklists and findings, through to closure evidence. External auditors can be given scoped, time-limited access rather than a copy of your quality system.

Controlled access. Four roles, tenant-isolated. An external auditor sees only what you scope to them.
| Control | Specification | Status |
|---|---|---|
| Electronic signatures | 21 CFR Part 11, with meaning statements | Included |
| Signature invalidation | Soft-invalidation with reason; never hard-deleted | Included |
| Audit trail | Append-only, attributed, timestamped | Included |
| Tenant isolation | Every query scoped; cross-tenant access impossible by construction | Included |
| Authentication | Passwordless one-time code by email | Included |
| Roles | Admin, QA Team, User, Auditor — all tenant-scoped | Included |
| Data export | Full export in open formats, on request and on exit | Included |
| Retention | 10 years post decommission by default | Included |
Not separate products bolted together. This is the chain an inspector follows.
Logged, numbered, risk-assessed and owned in the system, not in an inbox.
Root cause recorded against the deviation. Every edit attributed and timestamped.
Raised from the investigation with named owners and due dates, linked to source.
The CAPA cannot close until this is done. It is the evidence auditors ask for.
The same chain runs from an audit finding. Every step attributed, timestamped, append-only.
Enforced revision history, approval workflows and effective dates. Only the current approved version circulates; every superseded one stays retrievable.
Role-based matrices, assignment straight from a controlled document, quizzes, and requalification tracked per person.
Logged, risk-assessed, investigated and dispositioned, with a controlled path into CAPA when the investigation warrants one.
Owned action items, due dates, and an effectiveness review that must complete before closure.
Programme planning, checklists, findings and closure evidence. Findings raise CAPAs directly; external auditors get scoped access.
Tell us who you are and we will be in touch before the trial opens.
We use analytics cookies (page views, clicks, scroll and mouse movement) to understand how visitors use this site. Nothing is tracked until you accept. See our Cookie Notice for what each cookie is for.