Applications · Quality
Document Management System
Every DMS stores documents. Quickflow eDMS knows what each one governs. Change an SOP and the Digital Scientist traces every form, template, method and course that depends on it, drafts the follow-on changes and summarises the redline. Your team reviews, approves and signs.
Quickflow eDMS · SOP-QC-021 HPLC operation · v5 effective
Alert- Edit
- Redline
- Impact
- Review
- Approve
- 6Point of use
QC lab 3 · bench 2 · 17 Oct
SOP-QC-021 · HPLC OPERATION · v4
- 6.1 Equilibrate the column for 30 min…
- 6.2 Set the column oven to 25 to 40 °C…
- 9 Instruments: HPLC-03, HPLC-05…
Copy 07 of 12 · code 7Q4-K2Issued to QC lab 3 · 12 Jan
What this SOP governs In step with v5
- eLogbook · HPLC-07 usage logRange check to 28–32 °CUpdated
- eSheet · Assay template AT-114Suitability step addedUpdated
- MVS · Method MV-0932Reference to v5Updated
- Training · 42 QC analystsCheck on §6.2 and §7.4Assigned
- SOPs · SOP-QC-004, SOP-QC-033Cite §6.2, wording draftedUpdated
- eQMS · Change control CC-0231Linked, impact recordedLinked
Superseded copy: v4 was replaced 3 days ago. v5 is effective.
The analyst is shown v5 instead. QA is notified, and copy 07 is listed for retrieval in print reconciliation.
- Scan logged: user, time, place
- Copy 07 flagged
- v5 opened
Quickflow eDMS at a glance
GxP document control that knows which forms, methods and training each SOP governs.
- Who uses it
- Document control
- QA approvers
- Document owners
- IT
- What is included
- Controlled lifecycle
- Word authoring in the DMS
- Impact tracing
- Training on change
- Print and copy control
- Periodic review
- Works with
- LMS
- eQMS
- LIMS
- eLogbook
- eBMR / MES
- ERP
- Built for
- 21 CFR Part 11
- EU Annex 11
- EU GMP Chapter 4
- ISO 13485
- GAMP 5
Not a filing cabinet
Every DMS stores documents. Ours knows what they govern.
An SOP is not just a file. It sets the range on a logbook form, the steps in a calculation template, the content of a training course and the wording of the SOPs that cite it. Quickflow eDMS keeps those links, so a change to one document shows everything it touches.
A filing cabinet with workflows
Quickflow eDMS
What a document is
A file with a version number and an owner
A controlled record linked to the forms, templates, methods, courses and SOPs it governs
When it changes
The approver emails the people they remember
Every dependent record is traced and its follow-on change drafted
Training
“I have read and understood”
A short check on what actually changed
Paper copies
A watermark and a hope
A code that says, at the bench, whether the copy is current
Periodic review
A reminder that the date has come
A pre-read against live master data, with stale content flagged
Search
File names, tags and folders
Answers that cite the clause and the version
Linked, not filed
Each controlled document knows which records depend on it. The links are made when a form, template or course cites it, and kept up to date.
Reasoned, not routed
A workflow moves a file from inbox to inbox. A Digital Scientist reads the change, works out what it means and drafts what has to follow.
Checked where it is used
The question that matters is asked at the bench, not in the archive: is this the version I should be following?
The problem
An SOP changes. Which version is on the floor?
Approving a new version is the easy part. The hard part is everything it touches: the forms, templates, methods, courses and paper copies that still say what the old version said. By hand, that depends on someone remembering.
SOP-QC-021 v5 is approved. The oven range is now 28 to 32 °C.
By hand
6 steps- 1The approver emails the lab heads
- 2Someone remembers the logbook form uses the old range
- 3The calculation template is updated weeks later
- 4Training goes out as “read and understood”
- 5Printed v4 copies stay in bench drawers
- 6An inspector finds v4 at the bench
Quickflow eDMS
4 steps- 1Every dependent record traced on approval
- 2Follow-on changes drafted for each owner
- 3Retraining checks what changed
- 4Old prints flagged the moment they are scanned
Step comparison, illustrative. Not a measured result.
Half paper, half digital
Masters in one system, working copies on paper and shared drives. Finding the right one is a manual job, and mistakes come from habit.
Prints nobody can trace
Anyone can print. Nobody can say how many copies of a version exist, or where they are.
Superseded copies in use
Old versions are not retired automatically, and nothing on the paper says they are out of date.
Documents in islands
No link to training, quality events, the lab or the shop floor. Traceability is rebuilt by hand before every audit.
“Read and understood” proves little
A signature shows someone opened the document. It does not show they know what changed.
Reviews by the calendar
Periodic reviews re-approve text that still names retired instruments and forms that were replaced months ago.
How it works
5 steps. Every one recorded.
- Step 1Author in Word, inside the DMSHuman decision
- Step 2Impact traced, follow-ons draftedSystem
- Step 3Parallel review with the redlineHuman decision
- Step 4Approve and e-signHuman decision
- Step 5Release, verify copies at point of useSystem
Document lifecycle
Draft to archive, every step controlled
One lifecycle for every controlled document. Who can see it, edit it, sign it and print it changes with its state, and the state changes only when a named person signs.
Draft
- Written in Word inside the DMS, never on a desktop
- Editing limited to named authors
- Every save kept in the audit trail
SOP-QC-021 · HPLC operation
Owner R. Shah · QC
- Who can see it
- Authors only
- v4
- Effective
- v5
- Draft
Impact map
One change. Every record it touches.
When SOP-QC-021 moves from v4 to v5, the Digital Scientist traces everything that depends on it and drafts the change each one needs. Every owner approves their own change, so the SOP and its records move together.
eLogbook · HPLC-07 usage log
Oven range check 25–40 → 28–32 °C
eSheet · Assay template AT-114
System suitability step per bracket of six
MVS · Method MV-0932
Procedure reference updated to v5
Training · 42 QC analysts
Three-question check on §6.2 and §7.4
SOPs · SOP-QC-004 and -033
Citations of §6.2 reworded
eQMS · Change control CC-0231
Impact assessment filled from the map
Each owner reviews and approves their own change.
Illustrative.
Traced from real links
Links are recorded when a form, template, method or course cites a document. The Digital Scientist also reads other documents for citations nobody linked.
Drafted, not decided
It writes the follow-on change and explains why. The owner of each record edits, approves or rejects it.
Nothing out of step
The new version and its follow-on changes can take effect on the same date, so the floor never runs a new SOP with an old form.
Training on the change
Not “I have read it”. “I know what changed.”
From the redline, the Digital Scientist writes a short check on the changes themselves. QA approves the questions. Each person answers before the new version is effective for them.
The usual way
I have read and understood SOP-QC-021 v5 (14 pages).
Proves the document was opened. Says nothing about the three lines that changed.
Questions come from the redline
Only the clauses that changed are tested, so a small change means a short check.
QA approves the questions
The Digital Scientist drafts. QA edits and approves before anyone is asked.
A wrong answer points to the clause
The person sees the changed text again and tries once more. Results go to your training records.
1. What is the column oven range for assay on HPLC?§6.2
- 25 to 40 °C
- 28 to 32 °C
- 30 °C ± 5
2. When is the system suitability standard injected?§7.4
- Once per sequence
- Before each bracket of six
- Only after a failure
3. Which instrument is no longer listed?§9
- HPLC-03
- HPLC-05
- HPLC-07
Illustrative.
Print control
Every paper copy knows whether it is still current
Paper will stay on the floor for a long time. So every print is issued, watermarked, coded and accounted for, and anyone can scan a copy at the bench to see whether it is still the one to follow.
Finalise
Version and approval details fixed on the document.
Lock
The version is frozen; the one before it is marked superseded.
Issue
Print rights by role and site, with a watermark and a code on every copy.
Distribute
Copies go to named holders, who acknowledge receipt.
Reconcile
Every issued copy is returned, destroyed or accounted for.
A watermark for every purpose
SOP-QC-021 · v5
Copy 02 · M8R-3T
Issued to a named holder and tracked until it is retrieved.
- Printed by, when and where on every page
- Unique code per copy, not per document
- Reprints need a reason and are logged
SOP-QC-021 · v5
Copy 02
M8R-3T
Scanning copy 02…
Illustrative. Every scan is logged with user, time and place.
Document types
Five families of documents, one set of controls
Quality, manufacturing, the QC lab, engineering and regulatory documents follow the same lifecycle, audit trail and print control, and each one carries its links to the records it governs.
The procedures and records the quality system runs on.
- SOPs with version control and periodic review
- Change control records with approval workflows
- Training records linked to each version
- Superseded and obsolete copies retired and retrieved
Example · what it governs
- Change control form in eQMS
- QA curriculum, 18 people
- SOP-QA-012 cites §5
A Digital Scientist for your documents
It pre-reads the review. It answers with the clause.
Agentic AI would route the document. A Digital Scientist reads it: it checks an SOP due for review against live master data and flags what has gone stale, and it answers questions from your controlled documents with the clause and version. The owner decides; a named person signs.
Reading against eLogbook, forms and linked SOPs…
- §4.1 Names HPLC-03, retired in eLogbook on 2 Mar
- §8 Refers to form F-QC-008/02; /03 has been effective since June
- §5.3 Cites SOP-QC-021 §6.2, whose range changed in v5
- §1–3 Match current practice and master data
Recommends: revise. The owner decides.
Answers come only from controlled documents, with the clause and version.
Illustrative.
Legacy paper, made searchable
Scanned SOPs and records are read by OCR, so a document from before the DMS answers questions like any other.
Questions, not keywords
Ask the way you would ask a colleague. Answers cite the clause, the version and whether it is effective.
Ready for the inspector
Every version, approval, training record and print for a document, pulled together in minutes when an inspector asks.
Only what you may see
Search respects access rights. A draft or a restricted document never appears in an answer for someone without access.
It never signs, releases or makes a document effective. See the Digital Scientist Trust Charter.
Connected
The links are real because the systems are connected
A document can only know what it governs if it can see the systems that use it. Quickflow eDMS connects to training, quality, the lab, production and enterprise systems, and to the Quickflow applications natively.
- Training (LMS)Training needs from each new version, and completion checked before it is effective for a person.
- eQMSChange controls that open a revision, and deviations, CAPAs and audit findings linked to the document.
- RIMSRevisions triggered by regulatory commitments and findings.
- LIMSTest procedures and specifications behind each test code.
- eLogbookThe SOP behind each logbook form, its version and its limits.
- eSheetThe procedure each calculation template follows.
- Cleaning validationCleaning SOPs and the protocols that validate them.
- eBMR / MESMaster batch and packaging records, issued under control.
- CalibrationEquipment manuals and calibration SOPs.
- ERPMaterials, specifications and sites, kept in step with master data.
One set of users and roles. Sign-in, roles and sites come from your user management, so who may author, review, approve and print is defined once.
Already on Quickflow? Quickflow eQMS, Quickflow eLogbook and Quickflow eSheet connect out of the box.
Regulatory compliance
Built for the rules inspectors read your documents against
Document control is one of the first things an inspector checks. The controls each framework expects are part of the application, not a project of their own.
21 CFR
Part 11
Electronic records and signatures: audit trails, controlled access, and signatures that show the name, time and meaning.
21 CFR
211.100
Written procedures for production and process control, reviewed and approved by the quality unit before use.
EU GMP
Annex 11
Computerised systems in GMP: validation, data integrity, audit trails and electronic signatures.
EU GMP
Chapter 4
Documents approved, signed and dated by authorised people, kept up to date, with superseded versions kept out of use.
ISO 13485
§4.2.4
Control of documents: approval before issue, current revision identified, relevant versions available at points of use, obsolete ones prevented from use.
ICH
Q10
Change management and knowledge management in the pharmaceutical quality system: changes evaluated for impact before they are made.
MHRA · PIC/S
Data integrity
ALCOA+ records, from the first draft to the end of the retention period.
ISPE
GAMP 5
A risk-based approach to validating the system, with the documents to support it.
Industries
Wherever a procedure has to be the right version
Across life sciences: quality, the QC lab, production, engineering and regulatory affairs.
Pharmaceuticals
SOPs, test procedures and batch records from R&D to commercial supply.
Biotechnology
Process and analytical documents for biologics, where one change reaches many suites.
Cell and gene therapy
Fast-changing procedures in small teams, where training on each change matters most.
Medical devices
Drawings, specifications and procedures under ISO 13485 document control.
API manufacturers
Master records and specifications across multi-step synthesis plants.
CDMOs
Client-specific documents kept apart, with shared site procedures linked to each.
Questions
Frequently asked
What QA, document control and IT teams usually ask first.
What does a document management system do in life sciences?
It controls the documents a GMP operation runs on, such as SOPs, test procedures, batch records, specifications and protocols, through drafting, review, approval, release, supersession and archive, with an audit trail and electronic signatures at each step.
How is Quickflow eDMS different from other document systems?
Each controlled document is linked to the records it governs: logbook forms, calculation templates, methods, training and the SOPs that cite it. When it changes, the Digital Scientist traces those records and drafts the follow-on changes, writes a training check on what changed, and flags stale content at periodic review.
Does the Digital Scientist approve or release documents?
No. It reads, summarises, traces impact, drafts and recommends. A named person reviews, approves and e-signs every document and every follow-on change. It never signs, releases or makes a document effective.
Does it meet 21 CFR Part 11 and EU Annex 11?
Yes. It has an audit trail that cannot be edited, electronic signatures bound to their records with a stated meaning, role-based access and validation documents.
How are superseded and obsolete versions kept out of use?
The previous version is superseded automatically on the effective date and its holders are notified. Obsolete documents are blocked from use in active forms and templates. Paper copies carry a code, so a superseded copy raises an alert when scanned, and issued copies are reconciled.
Can documents be linked to change controls, deviations, CAPAs, audits and training?
Yes. A change control can open a revision, deviations, CAPAs and audit findings can be linked to the document concerned, and each version drives the training that goes with it.
Does it track expiry and periodic review?
Yes. Review dates, expiry and alerts are configured per document type. Before a review, the Digital Scientist pre-reads the document against live master data and linked records, and the owner decides whether to revise or re-approve.
Can it read our scanned legacy documents?
Yes. Scanned documents are read by OCR, so they can be searched and questioned like native ones. Answers cite the document, clause and version, and respect each user’s access rights.
Full overview: A document that knows what it governs
A controlled document is more than a file. An SOP sets the range on a logbook form, the steps in a calculation template, the content of a training course and the wording of other SOPs that cite it. Quickflow eDMS keeps those links, so every document knows which records depend on it.
Documents follow one controlled lifecycle: drafted in Word inside the DMS with no local copies, reviewed by several functions in parallel, approved by e-signature with a stated meaning, released with a version number, superseded automatically on the effective date and archived read-only when withdrawn. Obsolete versions are blocked from use in active forms, templates and batch records.
When a document changes, a Digital Scientist does the reasoning work around the change. It summarises the redline in plain words, traces every dependent record, drafts the follow-on change each one needs and writes a short training check on what actually changed. The owner of each record approves its own change, QA approves the questions, and a named person signs every approval. It never signs, releases or makes a document effective.
Paper copies stay under control. Each print is issued by role and site, watermarked as controlled, uncontrolled, training or draft, and given its own code. Scanning a copy at the bench shows whether it is still current, and issued copies are reconciled. Before a periodic review, the Digital Scientist pre-reads the document against live master data and flags stale content for the owner to decide on.
Quickflow eDMS covers quality, manufacturing, QC laboratory, technical and regulatory documents, reads scanned legacy documents by OCR and answers questions with the clause and version. It connects to training, eQMS, RIMS, LIMS, eBMR and MES, calibration and ERP systems and to Quickflow eLogbook and eSheet, with 21 CFR Part 11 and EU GMP Annex 11 controls built in.
Quality
Related applications
See Quickflow eDMS on your own process.
Tell us how this runs in your organisation today and we will walk through the application against it, with your QA and IT teams in the room.