Water testing is regulated, time-sensitive work: methods to follow, holding times to honour, and reports built to stand up to the regulators reading them. LabRelations builds LIMS for that work: field collection, chain of custody, preservation, holding-time enforcement, method execution, QA/QC, and regulatory reporting in one place. QMS sits alongside for ISO 17025 accreditation: documents, training, deviations, supplier qualification, and CAPA.
The bench team works in software designed for the bench, and QA works in software designed for quality. They share data where it counts (a deviation linked to the sample that triggered it, an SOP read by the analyst logged the same way as the test), but each system stays focused on the team using it.
LIMS for the bench. QMS for accreditation. Used independently. Connected where it counts.
Field samples are registered against the site, tap, or sampling point at the moment of collection, with barcode, timestamp, sampler, and conditions captured up front. Chain of custody follows the sample to the bench, through preservation and transport, and into the report. The CoC is exportable for the regulator without re-typing.
Each method's holding time and preservation rules are configured against the analyte. The system flags samples approaching their hold, blocks tests run outside it, and routes them to the right re-collection or deviation workflow. The clock isn't kept in someone's head.
Methods, detection limits, and regulatory limits are version-controlled. The right version applies to the right sample automatically. Changes go through a controlled change with electronic approvals before they're live.
QC samples are scheduled at the batch level. Acceptance criteria are checked automatically. Failed QC blocks reporting on the affected samples and opens an investigation. The QC summary lands in the report as part of the package.
Documents, SOPs, training, deviations, supplier qualification, internal audits, and CAPA. The records the assessor wants (proficiency tests, equipment records, method validation files) are organised the way the standard expects.
Reporting templates are configured per jurisdiction, per client, and per method. EDD outputs for state databases are built once and reused. Regulatory limits can differ by sampling location, and the right version applies automatically.
A mix of people who've actually worked in the industry supported by technical people for configuration needs inside the platform itself.
