Document control software — every SOP, signed, trained and current.
Every SOP, work instruction, form and specification in V5 has a controlled lifecycle: draft → review → e-sign approval → effective → training assignment → periodic review. Operators only ever see the current effective version on the kiosk.
What breaks without this.
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.
Records-by-execution. Compliance, by design.
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.
What to look for when you're buying.
Doc control fails when 'effective' and 'trained' aren't the same event. Criteria below expose it.
Effective ↔ trained linkage
What it tests: Does the doc go effective only when required training is complete?
Why it matters: Otherwise the shop reads the old SOP for days after go-live.
V5: Effective date gated on training completion.
Periodic review
What it tests: Does the system schedule periodic reviews per doc type with reminders and escalation?
Why it matters: Stale SOPs are their own finding.
V5: Native periodic review with review-by-exception.
Controlled print
What it tests: Are physical prints watermarked, expiring and traceable?
Why it matters: Uncontrolled prints are a documented failure mode.
V5: Controlled print with expiry stamp and print log.
Revision history and diff
What it tests: Can the reviewer see the exact diff between versions?
Why it matters: Redlines lost in email cause rework.
V5: Inline diff between any two versions.
Superseding and obsolescence
What it tests: Are superseded versions locked, watermarked and inaccessible to production?
Why it matters: Access to obsolete SOPs = deviation risk.
V5: Superseded versions removed from production surface.
Spreadsheet vs legacy QMS vs V5.
V5 doc control vs SharePoint vs legacy DMS.
| Capability | Spreadsheet | Legacy QMS | V5 Ultimate |
|---|---|---|---|
| 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 |
The clauses, verbatim — and how V5 answers each.
Doc control clauses and V5's answer.
There shall be written procedures for production and process control...
V5: Controlled lifecycle for every SOP; obsolete versions not visible to the floor.
Each manufacturer shall establish and maintain procedures to control all documents...
V5: Change, approval, distribution and obsolescence controlled.
The organization shall document procedures to define the controls needed for the identification, storage, security and integrity...
V5: Same lifecycle governs every doc type.
Documents should be designed, prepared, reviewed and distributed with care.
V5: Native review workflow with e-signature and version diff.
Step by step on the floor.
Doc lifecycle in V5.
- 1Draft
Author drafts
Template-driven, versioned.
- 2Review
Review with diff
Reviewers see inline diff and comment in-record.
- 3Approve
E-signature
Attributable signatures under Part 11.
- 4Train
Assignments emitted
Curriculum re-assigned; effective date gated on completion.
- 5Effective
Only new version visible
Kiosk shows current; obsolete withdrawn.
- 6Review
Periodic review
Scheduled with escalation.
The math, with the assumptions visible.
Doc-control ROI is felt in audits and in reduced re-work.
Obsolete-SOP incidents
Withdrawal is a system event.
Training-doc disconnect findings
Effective date gated on training.
Time to prep doc audit
Signed exports on demand.
Doc control usually pays for itself in the first avoided training-doc finding.
What changed on the floor.
Setting
A pharma site with 1,400 controlled SOPs.
Before
Effective date and training rarely coincided; two consecutive audits cited §211.100 + §211.25 disconnect.
After
Post-cutover: effective date gated on training; finding class closed for six consecutive audit cycles.
Proof points
- Part 11 e-signed approval workflow
- Kiosk-enforced current revision
- Retraining auto-triggered by revision change
- Redline diff and full change history on every doc
Built to satisfy
- 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)
Frequently asked questions
Is V5 a Part 11 compliant document control system?+
Yes — every approval, revision and read-receipt uses Part 11 e-signatures with meaning, user, time and reason captured in an immutable audit trail.
How does training stay in sync with SOP revisions?+
A new effective revision automatically assigns retraining to everyone on that SOP. Operators are locked out on the kiosk until they've signed off the new revision.
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.
See V5 on your own line.
Free trial, no card. Live in 7 days with guided onboarding.