The wrong version of the SOP stops circulating.
Ask your team which version of the sampling SOP is current. If the answer takes a beat, you already see the problem. Here the master list is single, every document is born with a standardized code and a controlled version, and the second you publish a new version the previous one goes obsolete on its own. It is document control the way 17025 demands, with the approval flow and read confirmation already inside. The auditor asks for the master list, you open it and it already points to what's valid.
No duplicate codes, no numbering by hand.
The system generates each document's code in a single pattern (type, sector and sequence, like SOP-LAB-001). The master list stays organized on its own.
The current version is always obvious.
A document moves through draft, review, approval and publication. Publish the new one and the old one goes obsolete instantly, with the full history preserved.
Approval with owner and deadline on record.
You define who reviews and who approves, with mandatory steps and deadlines. Every approval and rejection is logged with date and name, the way the auditor wants it.
You prove who read each SOP.
Distribute the document to whoever must read it and the system chases the confirmation, marking it pending, confirmed or overdue. Come audit, the training evidence is ready.
Never miss a review deadline again.
The dashboard alerts 30, 60 and 90 days before each document is due for review. The deadline stops living in the quality manager's head.
Controlled copies you can actually recall.
Controlled and uncontrolled copies, digital or printed, with receipt tracking and recall. You know who holds each copy and you can call it back.
History doesn't vanish when the document changes.
Every version stays stored and searchable. You show the auditor a revision from two years ago without digging through a backup folder.
Import what you already have in PDF.
The SOPs that live in a network folder today come into the system with a code and a version. You start from what you already have, no documenting from scratch.
The document lifecycle, from draft to recall
A controlled document isn't just an approved PDF. It's knowing what stage it's in, who needs to read it, and when it expires.
States that make sense.
Draft, in review, approved, published, obsolete. Each document knows where it is, and the transition is logged with who did it and when.
Targeted distribution, not a mass email.
You choose who receives each document. Read confirmation stays pending until the person opens and confirms, and overdue shows up on the dashboard.
Scheduled review, not forgotten.
Each document has a review cadence. The system raises the alert before expiry, so review happens on time, not the night before the audit.
Frequently asked questions
Can I import the SOPs I already have in PDF?
You can. You upload the documents that live in a network folder today and they enter the master list with a code, a version and a review cadence. The work isn't retyping, it's organizing once and never again doubting which version is current.
How does the system keep anyone from using the old version?
When you publish a new version, the previous one goes obsolete on the spot. The master list always points to the version in force, and the history of old ones stays preserved for reference, not for use.
Does read confirmation count as training evidence?
It counts as proof that the person received and confirmed reading the document, with date and name. It's the record the auditor asks for when they question whether the team knows the procedure in force.
Does the system warn me when a document needs review?
It does. Each document has a review cadence and the dashboard raises the alert 30, 60 and 90 days before it's due. You review on time instead of finding the expired document mid-audit.
Want to see the QMS running with your lab’s routine?
Get through the next audit without burning a weekend night hunting for PDFs. Book a demo and see document control, CAPA and Westgard working with a case similar to your lab's.