White paper · 12 min read
Can you show your work? Result integrity and audit trails in a testing lab
How to keep every result traceable, controlled and verifiable by the people who rely on it.
Accreditation, insurers, contractors and now regulators all ask the same question about a result: can the lab show where it came from and prove it has not been changed? This paper sets out where integrity is lost in practice, what ISO/IEC 17025 asks of your information systems, how to control spreadsheets and validate systems, and a self-check you can run this quarter.
Who it is for: Quality leads, lab managers and owners at commercial environmental and building testing labs preparing for accreditation assessments or client scrutiny.
Hent whitepaperet
Enter your details and we send the PDF by email. You can download it straight away too.
What is inside
- Why result integrity is now a client question, not only an auditor question
- What integrity means in a testing lab
- Where integrity is lost in practice
- What ISO/IEC 17025 asks of your information systems
- Spreadsheets: not forbidden, but they must be controlled
- Validating what you use, in proportion to the risk
- Results other people can verify
- A self-check you can run this quarter
- Result integrity self-check
More documents
From requisition to receipt: what must be true when a sample arrives
Most intake problems start before the sample reaches the bench: an incomplete requisition, a label that does not match the form, a sample that arrived warm or late. This paper sets out what to capture, what to check, what to do when a sample fails the check, and how to keep clients informed without a phone call.
Switching your lab system without stopping the lab
Most lab software projects go wrong before the first demo and after the contract is signed, not during the demo itself. This paper walks through how to write down your current workflow, score candidates fairly, decide what data to move, and cut over one workflow at a time while samples keep arriving.