Environmental lims selection: the method, holding time and chain of custody behaviour that separates an environmental lims from a general laboratory system, and the electronic deliverable that decides whether the data is accepted
An environmental laboratory fails an audit for reasons a research laboratory never encounters: a holding time exceeded by an hour, a batch without its matrix spike, a deliverable in a format the receiving agency rejects. A general purpose laboratory system handles none of these natively. This page covers what an environmental lims has to do differently and how to test a candidate against it.
- the EPA compendium a solid waste method is drawn from
- SW-846
- the approved methods table behind Clean Water Act reporting
- 40 CFR 136
- the competence standard an accredited environmental laboratory holds
- ISO 17025
Figures in this panel are the method compendia and accreditation standards an environmental laboratory reports under, named from the regulations themselves and linked in the sources below. They are identifiers, not prices: BioBricks publishes verified prices for synthesis services only, and does not imply a software price index it has not measured.
- 4 vendor service pages verifiedevery figure matched verbatim to the vendor's page
- Quoted and dated, never estimatedlast verification pass 2026-08-24
- 1 service classes coveredeach with measured search demand behind it
Testing a candidate system
- Holding times computed from collection, and enforced. The clock starts when the sample is taken, not when it is logged. The system must hold the collection timestamp, compute the expiry per analyte and method, and warn before it passes. A system that stores a date without acting on it has not solved the problem.
- Chain of custody as a record, not a printout. Every transfer, with who released, who received and when, held as data and reproducible as a signed document. Custody that exists only as a scanned paper form attached to a record is custody the system cannot check.
- Quality control batching built into the workflow. Method blanks, laboratory control samples, matrix spikes and duplicates belong to the preparation batch and their frequency is set by the method. The system should build the batch with its QC and refuse to report a batch whose QC has not been evaluated.
- The electronic data deliverable in the formats you owe. Different agencies and clients demand different deliverable formats, and producing them by hand is where laboratories lose their margin. Ask which formats ship as standard, which are configurable, and what a new one costs.
- Accreditation evidence the system can produce. Under a national accreditation programme the laboratory must show method scope, analyst competence and traceability on demand. A system that holds these alongside the results turns an assessment into a query; one that does not turns it into a fortnight.
Where implementations usually go wrong
The method library is the project. Configuring a few dozen methods with their preservation, holding times, QC frequencies and reporting limits is weeks of careful work, and it is the part that gets underestimated in every implementation plan.
The second trap is bespoke deliverable formats. Each one is a small piece of development work that has to be maintained as the receiving agency changes its specification, which is why an in-house customisation that nobody owns after the consultant leaves becomes a liability.
Instruments and the data path
Environmental laboratories run a small number of instrument types very hard, so a handful of integrations covers most of the volume. Chromatography data systems and elemental analysers are where the effort belongs, and manual transcription anywhere in that path is both a cost and an audit finding waiting to happen.
Ask specifically how reruns and dilutions are handled, because that is where automatic import usually breaks and where somebody quietly starts pasting values.
Buying it at the size you are
A laboratory running a few thousand samples a year does not need the configuration engine a national network needs, and paying for one buys an implementation project rather than a system. Conversely, a growing laboratory that outgrows a fixed product pays for the migration twice.
The useful test is to ask a vendor for a reference laboratory of your size and accreditation scope, and to ask that laboratory how long implementation actually took against the plan.
Common questions
- What makes an environmental lims different from a general laboratory system?
- Holding times computed from collection, chain of custody as structured data, method-driven QC batching, and electronic deliverables in the formats regulators accept. A general system can be configured towards these; an environmental product starts there.
- Does the system need to know the method?
- Yes, because holding time, preservation, QC frequency and reporting limits all follow from the method. A system where the method is a free text field cannot enforce any of them.
- How important is the electronic deliverable?
- It is often the deciding factor. A rejected deliverable means rework on data that was correct, and the laboratories that lose least time are the ones whose system generates the format directly from the result record.
- Should subcontracted work live in the same system?
- It should. Subcontracted analyses still carry holding times and custody, and a report that combines in-house and subcontracted results has to show which is which without somebody reconciling two systems by hand.
Get a shortlist for your project
Browse by service class
Sources
Cite or embed this figure
The median advertised gene synthesis price per base pair in the US research synthesis services market was $0.11 in August 2026, across 4 verified vendor service pages recorded in BioBricks Synthesis Price Index.
Cite as: "BioBricks Synthesis Price Index", updated 2026-08-24, https://biobricks.org/environmental-lims/.