There is a distinction baked into ISO/IEC 17025:2017 that many laboratories read past during implementation and then pay for during audits. The standard separates the control of documents — Clause 8.3 — from the control of records — Clause 8.4. Two clauses, two different compliance obligations, two very different sets of system requirements. Labs that treat them as variations of the same thing tend to discover the difference the hard way: a nonconformity notice from an assessor, or worse, a data integrity finding that calls results into question.
The confusion is understandable. Both involve paperwork. Both live in shared folders or software platforms. Both get reviewed during audits. But document control and record control are not the same activity, and conflating them in practice, using the same tools, the same permissions, the same workflows, creates compliance gaps that no amount of preparation covers up when an auditor walks through the door.
This article is for lab managers, QA leads, and document control owners who are either preparing for ISO 17025 accreditation or shoring up their systems ahead of a surveillance audit. The goal is to be precise about what each obligation actually requires, where laboratory information management systems fit versus where a quality management system fits, and why the gap between the two tools matters more than most labs realize until it is too late.
The Standard’s Actual Distinction
ISO 17025 Clause 8.3 covers the control of management system documents. Read it closely and the requirements are all about documents as living, controlled artifacts: they must be approved before issue, reviewed periodically, uniquely identified, kept current, and protected against unintended use once they become obsolete. The standard is describing things that change- standard operating procedures, test methods, work instructions, forms, policies, the quality manual itself. A document under Clause 8.3 has a version, a review cycle, and an authorization path. At any given point, there is one current version and every prior version is either archived with controlled access or withdrawn.
Clause 8.4 is different in kind, not just degree. It covers the control of records- the evidence that the management system is actually functioning. Records do not have versions because they are not revised. The test result from last Tuesday is what it is. A signed calibration certificate, a chain-of-custody log, a training completion record- these are completed artifacts. They document that something happened, and once created, they cannot change. The Clause 8.4 requirements reflect this: records must be legible, identifiable, retrievable, protected against modification, backed up, stored for defined retention periods, and eventually disposed of in a controlled way.
The conceptual gap is clean. Documents tell personnel what to do and how to do it. Records prove that they did it. But the operational gap- in terms of systems, access controls, and workflows- is where labs consistently get into trouble.
Where Labs Fail Audits
The most common manifestation of this confusion is not dramatic. It does not look like fraud or negligence. It looks like a lab that has built a reasonable documentation system but applied it uniformly to both document types.
Consider what happens when a lab manages its test reports inside the same document control platform it uses for SOPs. If that platform allows documents to be edited, revised, and re-issued under a new version number, the same functionality is technically available for records. An analyst who needs to correct a transcription error in a completed test report might reach for the same revision workflow used to update a procedure. To the analyst, it feels like a reasonable fix. To an ISO 17025 assessor, it is a record integrity violation. Completed records cannot be edited. Corrections, when necessary, must be documented as separate entries with traceability back to the original.
The inverse failure is also common. Labs sometimes treat controlled documents like records — stable, filed away, rarely revisited. An SOP that was written three years ago for a method that has since been refined sits in a shared drive, still being referenced by analysts who don’t know there was a change. No version control. No review cycle. No indication that the document is current. When an auditor asks whether laboratory personnel are working from current, approved procedures, the answer is technically yes — but only because no one has updated the document to say otherwise. Labs working through accreditation prep often find it useful to work from an ISO 17025 compliance checklist to catch these gaps before an assessor does
Both scenarios trace back to the same underlying problem: the lab has not separated the infrastructure for document control from the infrastructure for record control. These require different tools with different capabilities and different access models.
What Document Control Actually Requires
Under Clause 8.3, the lab’s document control system needs to do several things well. Every document must be approved by an authorized individual before it is released. Changes to documents must be tracked, with the current revision status clearly visible. Obsolete versions must be pulled from active use and either disposed of or retained in a clearly marked archive with access controls that prevent their unintended use.
Beyond the individual document, the system needs to manage distribution. When an SOP is updated and re-issued, the right people need to know. Personnel working from a prior version of a test method need to be notified that the method has changed. In a large laboratory or multi-site operation, this distribution problem compounds quickly.
Document control also requires periodic review. Most laboratories define review cycles in their quality manual — annually is common, though the standard does not specify a frequency. What matters is that reviews happen on schedule, that they result in either a formal re-approval or a documented update, and that the evidence of that review is retained.
The access model for documents is governed by role and need-to-know. Not everyone who needs to read an SOP needs to be able to edit it. The system should enforce the difference between read access, authoring rights, and approval authority.
What Record Control Actually Requires
Clause 8.4 requires something fundamentally different: immutability, retention, and retrievability. The standard asks labs to define and implement controls for the identification, storage, protection, backup, archiving, retrieval, retention time, and disposal of records. Every item on that list is about protecting evidence that already exists, not managing content that will be revised.
The immutability requirement is worth dwelling on. ISO 17025 does not use that word, but the requirement is embedded in the logic of the clause. A record that can be altered after the fact is not a reliable record. It cannot serve as evidence of what happened. Labs operating under 21 CFR Part 11 encounter this obligation even more explicitly in the FDA’s requirements for electronic records- audit trails, timestamp integrity, controlled access- but the principle is present in ISO 17025 regardless of sector.
Retention periods must be defined. Different record types carry different regulatory obligations depending on the lab’s sector and the nature of its work. Technical records supporting test results are often required to be retained for minimum periods defined in the lab’s contracts, its accreditation body’s requirements, or applicable regulatory frameworks. The system managing records needs to support defined retention schedules and flag records approaching their disposal date.
Retrieval speed matters too. An assessor who asks to see the chain-of-custody record for a specific sample from eight months ago expects to get it within minutes, not hours. If the lab’s record management depends on manual searches through shared drives organized by date and analyst name, retrievability under audit conditions is already a risk. The system should enforce the difference between read access, authoring rights, and approval authority. Labs operating inside larger manufacturing organizations often need to reconcile this with ISO 9001 document control requirements as well, since the two standards share much of the same logic around controlled documents
Where LIMS Is the Right Tool
A laboratory information management system is designed for exactly the record control problem. LIMS is purpose-built to capture, manage, and protect the operational evidence that laboratories generate at volume: sample receipt records, chain-of-custody logs, instrument data, test results, analyst sign-offs, environmental condition records, and the audit trails that tie all of it together. LIMS is purpose-built to capture, manage, and protect the operational evidence that laboratories generate at volume: sample receipt records, sample chain-of-custody tracking, instrument data, test results, analyst sign-offs..
The record types that belong in a LIMS are those created in real time during laboratory operations. When a sample arrives and is logged, that receipt record is immutable from the moment it is created. When an analyst runs a test and the instrument pushes results into the system, those results are captured with a timestamp, user attribution, and a complete audit trail. When custody transfers from one analyst to another, that handoff is recorded with the same permanence. None of this is edited through a revision workflow. When custody transfers from one analyst to another, that handoff is recorded with the same permanence. For a closer look at how a LIMS supports ISO 17025 method version control, particularly around keeping test workflows aligned with approved procedure versions, see the related discussion below. If a result needs to be challenged, that challenge is documented as a separate entry. If a result needs to be challenged, that challenge is documented as a separate entry- an observation, a retest request, a deviation- not an overwrite of the original.
LIMS handles the Clause 8.4 requirements for records in a way that a generic document management system cannot. It automates the generation of records as a byproduct of normal workflow, rather than requiring analysts to manually create and file documentation after the fact. Retention schedules can be built into the system at the record type level. Access controls can be set so that analysts can create records but cannot modify records they did not create, and so that completed records require supervisor-level access to even view the underlying data in its raw form.
The audit trail itself is a record. Every action a user takes in a LIMS- viewing, entering, approving, querying- is logged with a timestamp and user identity. That log is one of the things assessors look for when evaluating whether a lab’s electronic record system meets the requirements of Clause 8.4.
Where a QMS Is the Right Tool
A quality management system is built for the document control problem. SOPs, work instructions, policies, forms, method descriptions- these are authored content with lifecycles. They need to be drafted, reviewed, approved, version-controlled, distributed to relevant personnel, and periodically re-evaluated.
A QMS provides the workflow infrastructure that document control under Clause 8.3 requires. When a test method is updated, the QMS routes the draft through review and approval before it can be released. It notifies the relevant personnel, tracks acknowledgment, and retires the previous version in a controlled archive. It maintains a log of who approved what and when. It manages review cycles and sends alerts when documents approach their scheduled review date.
Change management is also a QMS function. When a procedure changes, the system can initiate a workflow that includes impact assessment, communication, and sign-off before the updated document goes live. That workflow creates records- approvals, acknowledgments, review decisions- which the QMS also retains. This is a place where the two systems’ responsibilities overlap: the change management process produces records of its own, which must be retained under Clause 8.4 even though the documents being managed live under Clause 8.3.
Policies and quality objectives, training curricula and competency frameworks, supplier qualification documentation and external audit schedules- these belong in the QMS because they are documents that govern the laboratory’s management system rather than its operational output. They are living content, subject to revision.
Why Integration Between the Two Matters
Running a LIMS and a QMS as independent systems introduces a gap that labs frequently discover during audits. The scenario plays out like this: the QMS has been updated with a revised version of a test method- new reagent concentrations, adjusted incubation time, updated acceptance criteria. The change was properly managed. The revision was approved. Personnel were notified. But the LIMS still routes samples through the workflow configured for the previous method version. For some period of time, the procedure the lab says it follows and the procedure the LIMS actually enforces are not the same thing.
This is not a theoretical risk. It is a documented source of nonconformities in laboratories that treat LIMS and QMS as parallel but disconnected systems. When an assessor reviews the test reports generated during the gap period and then asks to see the procedure in force at the time, the versions do not match.
Integration closes this gap. When the QMS releases a new version of a method, that release can trigger a corresponding update in the LIMS workflow- automatically, without requiring a manual intervention that is easy to miss in a busy lab. The current approved method in the QMS is the method the LIMS enforces. The two systems agree, and the audit trail across both confirms it.
Integration also supports the Clause 7.5 requirements for technical records. ISO 17025 requires technical records to include sufficient information to allow a competent person who was not involved in the original work to replicate the test under conditions as close to the original as possible. That means the record of a test result needs to reference the procedure version under which the test was conducted. If the LIMS captures the result and the QMS holds the procedure, integration is what makes it possible to link the specific procedure version to the specific test record — creating the traceable connection an assessor needs to verify that the work was performed correctly.
Making the Architecture Work
The practical implication is straightforward even if the implementation is not. Labs preparing for ISO 17025 accreditation- or tightening their systems ahead of a surveillance audit- need to answer two questions honestly.
First: which of our controlled content is a document and which is a record? The answer determines where each type belongs. SOPs, methods, forms, policies, work instructions, and training materials are documents. Test results, chain-of-custody logs, instrument data, calibration certificates, audit findings, and training completion records are records. If the same system holds both, look carefully at whether it enforces the different controls each type requires.
Second: are our LIMS and QMS connected, or do updates in one require a separate manual action in the other? If the answer is manual action, the integration gap is a compliance risk every time a procedure changes.
QISS LAB and QISS QMS: Built for This Division of Responsibility
QISS addresses this architecture directly through two products designed to work together. QISS LAB handles record control at the operational level- sample tracking, chain-of-custody, instrument data capture, audit trails, and compliance reporting- with the immutability, access controls, and retention management that Clause 8.4 requires. Every record is generated in real time as a byproduct of the workflow itself, timestamped, attributed, and protected.
QISS QMS manages the document control layer- version-controlled SOPs and work instructions, review cycles, approval workflows, change management, and controlled distribution to the personnel who need current procedures. When a procedure changes in QISS QMS, that update doesn’t just sit in the document system waiting to be noticed. Authorized personnel with LIMS access get notified right within the same screen they’re already working in, no logging out or switching systems required. From there, it’s one click back to QMS to see exactly what changed. The lab isn’t left operating on the old version while the new one quietly exists somewhere else; QMS and LIMS stay connected on the same interface, so the update reaches the people who need it instead of staying isolated in a separate document system.
For labs operating under ISO 17025 or ISO 15189, the compliance architecture ISO requires maps directly onto the system architecture QISS provides. The distinction the standard draws between documents and records is the distinction the platform enforces. Auditors see a system that understands the difference- which is, ultimately, the point. Book a demo to learn more.
