Document control · SOPs · Change history
Document control for SOPs, forms and specifications.
Draft, review, approve and release documents with signatures, link them to training, and show operators the current version at the station.
Controlled Revisions
Draft, review, sign and release each SOP, form and specification.
Linked to Training
A new revision can create training for the roles that use it.
Current Version at the Station
Operators open the effective version where they work.
What goes wrong today3 common problems
Operators Read Superseded SOPs
Paper SOPs in binders go stale the moment a new revision is approved — and the line keeps running on the old version.
Training Doesn't Follow the SOP Change
When an SOP changes, nobody knows who needs to be retrained — and the next audit finds operators trained on rev 3 still running rev 4.
Approvals can't survive a Part 11 audit
Email-based SOP approvals don't carry the meaning of the signature, the time, or the audit trail FDA expects.
Everything V5 does here5 capabilities
Controlled Lifecycle on Every Document
Draft → review → e-sign approval → effective → periodic review. Every transition is captured with user, time, reason and Part 11 e-signature.
Kiosk only shows the effective version
Operators see the current revision tied to the job. Superseded versions are physically inaccessible on the floor.
Training Assignments Triggered by Revision
A new revision automatically generates retraining tasks for every operator on that SOP — with kiosk lockout until they complete it.
Change History with Redline Diff
Every revision shows what changed, who approved it, why, and which records reference it.
Periodic Review Forcing Function
SOPs flag for review at their defined interval (typically 24 months). Overdue documents trigger a CAPA.
How it works, step by step6 steps
Doc lifecycle in V5.
- Author Drafts. Template-driven, versioned.
- Review with diff. Reviewers see inline diff and comment in-record.
- E-Signature. Attributable signatures under Part 11.
- Assignments Emitted. Curriculum re-assigned; effective date gated on completion.
- Only New Version Visible. Kiosk shows current; obsolete withdrawn.
- Periodic Review. Scheduled with escalation.
What to look for when choosing
Doc control fails when 'effective' and 'trained' aren't the same event. Criteria below expose it.
Effective ↔ trained linkage
Does the doc go effective only when required training is complete? Effective date gated on training completion.
Periodic Review
Does the system schedule periodic reviews per doc type with reminders and escalation? Native periodic review with review-by-exception.
Controlled Print
Are physical prints watermarked, expiring and traceable? Controlled print with expiry stamp and print log.
Revision History and Diff
Can the reviewer see the exact diff between versions? Inline diff between any two versions.
Superseding and Obsolescence
Are superseded versions locked, watermarked and inaccessible to production? Superseded versions removed from production surface.
V5 Compared with Other Approaches
V5 doc control vs SharePoint vs legacy DMS.
| capability | spreadsheet | legacy Qms | v5 |
|---|---|---|---|
| Effective ↔ trained gate | None | Cross-tool | Native |
| Periodic review | Calendar reminder | Native | Native + trend |
| Controlled print | None | Add-on | Native with expiry |
| Inline diff | Compare in Word | Sometimes | Native |
Regulations this supportsYour quality team stays responsible for compliance
Doc control clauses and V5's answer.
21 CFR 211.100(a)
Controlled lifecycle for every SOP; obsolete versions not visible to the floor.
21 CFR 820.40
Change, approval, distribution and obsolescence controlled.
ISO 13485 §4.2
Same lifecycle governs every doc type.
EU GMP Chapter 4
Native review workflow with e-signature and version diff.
Standards Referenced
- 21 CFR 211.100 (Written procedures)
- 21 CFR 211.180 (Records retention)
- 21 CFR 820.40 (Document controls)
- 21 CFR Part 11 (Electronic records and signatures)
- EU GMP Chapter 4 (Documentation)
- ISO 13485 §4.2 (Document requirements)
- ISO 9001 §7.5 (Documented information)
Common questions4 answers
- Does V5 document control support Part 11?
- Approvals, revisions and read-receipts use electronic signatures with meaning, user, time and reason captured in an audit trail. Your team validates V5 for its intended use and determines compliance.
- How does training stay in sync with SOP revisions?
- A new effective revision automatically assigns retraining to everyone on that SOP.
- Can we import existing SOPs?
- Yes — PDF and Word imports are converted into V5 controlled documents with version 1.0 set at import, then put through your normal review/approval cycle.
- How fast can we deploy?
- Document control onboarding is typically 7 days including SOP import and lifecycle configuration.