Lab data & LIMS
We configure, integrate or replace your LIMS, build the pipelines that turn instrument exports into validation statistics, and generate the certificate of analysis each state requires. The software is written by a scientist who has worked the bench.
Free, 30 minutes, with the people who do the work. No pitch deck.
The problemIn the lab’s own words
Between the instrument and the signed COA, results get exported, pasted, recalculated and retyped. Every copy is a chance for a transcription error and a gap in the audit trail. The fix is software that carries the result, and a record of everyone who touched it.
“Every validation report means a day of copying peak areas out of the instrument software into spreadsheets.”
“Our LIMS can’t produce the COA the state wants, so someone retypes every result.”
“The state changed its COA rules, and our LIMS vendor quoted months to catch up.”
“When the assessor asks who approved a result, we open three systems and a binder.”
What we doLab data & LIMS
Start with the LIMS you have. Most retyping comes from missing connections and templates, not a bad system. When replacement is the answer, we’ll say so and show why.
We map how samples, results and approvals actually move, configure what your LIMS can already do, connect the instruments it can’t see, and write the requirements for a replacement when it can’t be saved.
Instrument exports in; accuracy, precision, linearity and detection limits out, formatted for the validation report. No peak areas copied by hand.
One source of results and a template per state: required analytes, units, limits and pass/fail logic, rendered the same way every time. You enter each result once, and the certificate comes from a template you own and can edit, not one locked inside a vendor’s app.
Who ran the sample, on which instrument, from which file, who reviewed it and when, recorded as the work happens instead of reconstructed the week before an audit.
How it worksFrom the first call to go-live
Nothing goes live until it reproduces what you’ve already reported.
From login to signed COA, we write down every export, paste, calculation and signature along the way.
Configure, integrate, build or replace. You get the options with their cost and risk before anything is built.
The pipeline or integration runs against batches you’ve already reported, and every difference is explained before go-live.
Documentation and training, so your team runs it without us. A change in state rules becomes a template edit, not a project.
ProofFigures from our published record
We built the validation pipeline for LC-MS, GC-MS and ICP-MS data, and a COA system in Google Sheets and Apps Script that replaced a lab’s LIMS subscription. We also build GIMS, an open-source database and workflow platform, and the GIMS Compliance Relay, which captures instrument files and records who did what with them.
Try itSample data
Every line on a COA traces back to an instrument result, a limit and a signature. The explorer walks through a sample certificate; on the call, we walk through yours.
A fictional flower certificate, explained in 12 notes: ND against <LOQ, the 0.877 arithmetic, and limits that change at the state line.
Open the COA explorer →QuestionsBefore you book
Usually not. Most of the retyping we see comes from missing instrument connections and COA templates, not a bad LIMS. When replacement is the answer, we write the requirements from your real workflow and compare vendors against them.
We start from the one you run. The work is in the data flow around it: instrument exports, calculations, approvals and the COA. If it can’t do what your state requires, we’ll tell you plainly.
In your systems. We build pipelines and templates to run where your data already lives, and we don’t keep copies of client results after the work ends.
We run batches you’ve already reported through it and compare every number with what went out on the COA. Differences are explained and fixed before anything goes live.
Yes. Each jurisdiction gets its own template: required analytes, units, action limits, pass/fail logic and signature blocks. One set of results feeds all of them, so a rule change means editing a template, not retyping reports.
Start with one problem
If the answer is more than zero, bring one sample’s path to a 30-minute call. We’ll show you where the copies can go.