White paper · 14 min read
Switching your lab system without stopping the lab
A vendor-neutral guide to defining requirements, testing candidates, moving data and cutting over in stages.
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.
Who it is for: Lab managers and owners at commercial environmental and building testing labs who are replacing Excel, paper or an older LIMS.
Hent whitepaperet
Enter your details and we send the PDF by email. You can download it straight away too.
What is inside
- Why labs switch, and why the trigger is strain, not size
- Write down how the lab works today, before you look at any product
- Separate must-haves from preferences, and score before the demos
- Configuration, customization and who keeps it running
- Test on your own samples, talk to similar labs, and ask what the quote leaves out
- Moving the data: what to migrate, what to archive, what to leave behind
- Cutting over in stages while samples keep arriving
- Validation, sign-off and retiring the old system
- Switching checklist for a testing lab
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.
Can you show your work? Result integrity and audit trails in a testing lab
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.