// Environmental testing labs · Electronic data deliverables
Electronic data deliverables, drafted from your signed reports in each client's format.
One consultant wants its EQuIS format, a state program wants its own valid values, and a water system's results go to the state through a portal. Someone in your data group rebuilds the same results for each. In a free AI proof of concept, AI drafts the EDD for 20 to 30 jobs you already delivered, from the signed report and in the format that job called for. Your reviewer, the person on your team who knows your deliverables best, sets each draft beside the EDD you sent.
- Jobs tested
- 20 to 30, already delivered
- EDDs loaded or sent
- None
- Results changed
- None
// The one job
From a signed report to an EDD in the client's format
Today a data specialist exports results from the LIMS, maps them onto the client's template, fills in the codes the format demands, fixes whatever the checker rejects and sends the file with the report. Each format has its own columns, codes and rules, and the work starts over when a project moves to a new version.
In the proof of concept, AI reads copies of the signed report, your LIMS export and the client's format files, and drafts the EDD row by row: sample codes, methods, analytes with CAS numbers, results, units, limits and lab qualifiers, each carried from your report. Any row it can't place goes on a short list for your data group, with the reason. Nothing is loaded or sent.
for your data group
// What makes it hard
Where an EDD breaks between the report and the checker
The format belongs to the agency; the file usually belongs to the consultant. New York DEC takes remediation and materials management data in a standard EDD format built on EarthSoft's EQuIS, and says labs and subcontractors hand their data to the primary consultant, who prepares the EDD. DEC's checking tool is the EQuIS Data Processor, version 7.24.2 for the current format, and a common error DEC names is a value missing from the valid values list. A merge EDD goes through DEC's automated data loading; an update or replace EDD goes to DEC's EQuIS team to be reviewed and loaded by hand, and a file over 25 MB needs the team's help to split. So the draft uses the consultant's codes, not yours, and lists every value it couldn't find on the list.
Sample identity has rules of its own. DEC's EDD manual keeps the sample code the consultant or DEC assigns apart from your lab sample ID. A field duplicate or matrix spike must name the sample it came from as its parent, trip blanks and field blanks carry no location, waste characterization samples are typed WC and clean fill CF, and characters such as # or @ stay out of sample names. The draft ties each row to the client sample ID on your report and flags any sample whose parent or type it can't pin down.
One reportable result per chemical, per sample. The same manual wants every initial run and every retest in the file, with exactly one result for each chemical in each sample marked reportable. Its example is a benzene result of 1,000 flagged E, over the calibration range and not reportable, followed by a dilution at 650 that is. Selected ion monitoring runs and second-column results raise the same question. The draft never makes that choice: it marks reportable the result your signed report issued, and lists any sample where the report leaves two candidates.
Non-detects and qualifiers have exact places. For a non-detect the result value stays empty, the detect flag reads N, and the sample-specific reporting limit carries the number, alongside the method detection limit and the quantitation limit. Labs fill in their own lab qualifiers; the interpreted qualifier is filled only when the lab itself submits to DEC, and the validation level stays blank in raw lab data. Fractions are coded total, dissolved, TCLP, SPLP or SEM, solids are reported wet or dry, and the lab's sample delivery group ties each row to the hard-copy report. The draft copies each qualifier exactly as your report prints it and never adds, drops or converts one.
Other receivers, other rules. EPA's Staged Electronic Data Deliverable is a hierarchical file created by a lab's LIMS, with stages that add sample-related QC results, then instrument QC, then instrument output detailed enough to recalculate results; its specification 5.2 dates from March 2019, and the Contract Laboratory Program's statement of work sets the stage. Virginia's Office of Drinking Water takes every lab result through EPA's Compliance Monitoring Data Portal, by Excel, XML or web entry, after at least three successful test files, while positive coliform results and MCL exceedances also go to a field office within 24 hours. That alert stays with your staff. Your reviewer will check codes against the valid values, parent links, reportable flags, limits and units, and that every row matches the signed report.
// What you send
What the test needs from your data group
20 to 30 delivered jobs
For each, the signed report, the LIMS export behind it and the EDD you sent, plus any checker error list or correction request that came back. Include a job with a dilution and one with field QC samples.
The formats you deliver to
Each consultant's or agency's format description and valid values file as they stood when the jobs went out, and any client code list layered on top.
No logins
We never sign in to your LIMS, EQuIS, a state portal or a client's database. Copies come to us, and the originals and every submission stay with your team.
NDA first, then look-alikes if needed
Client results, site names and coordinates stay with you until the NDA is signed. If a client's data can't leave at all, your reviewer helps us build look-alike jobs.
// Before it starts
Agreed before the first file moves
A wrong code in an EDD can stall a client's submission, so the owner settles who decides what first.
- Your reviewer
- Named by the owner, often the data management lead or EDD specialist
- Formats
- Which client and agency formats the sample covers, with their versions
- Reportable results
- Taken from the signed report, never chosen by the AI
- Success criteria
- Written first: codes valid, rows complete, values identical to the report
- Price
- A range for running EDDs live
- NDA
- Signed before any client data moves
// How it's judged
Each draft EDD beside the one you delivered
| On the same 20 to 30 jobs | The EDD you sent | The AI draft |
|---|---|---|
| Every result on the signed report present, and nothing extra | Filled from your jobs | Filled from your jobs |
| Sample codes, parent samples and field QC types right | Filled from your jobs | Filled from your jobs |
| Values, units and limits identical to the report | Filled from your jobs | Filled from your jobs |
| Non-detects with an empty result and the right limit | Filled from your jobs | Filled from your jobs |
| Lab qualifiers carried exactly as printed | Filled from your jobs | Filled from your jobs |
| One reportable result per chemical in each sample | Filled from your jobs | Filled from your jobs |
| Codes found on the format's valid values list | Filled from your jobs | Filled from your jobs |
| Rows held back for your data group, and why | Filled from your jobs | Filled from your jobs |
// After a yes
About 30 days on new deliverables
With a yes against the success criteria, new jobs get draft EDDs the same way for about 30 days.
Each file is checked and released by your data group before it goes to a consultant or an agency, and every load or submission stays with your team or the client.
The side-by-side scoring continues through the month. Adding another job waits until this one is judged, and it gets its own price.
// What could come next
Possible next jobs, ranked
- 01Next
Checker errors read back
The error list an agency's checker returns, matched to the rows it names, with the likely fix noted for your data group to make.
- 02Then
DMR data for permit clients
A permittee's results for the monitoring period worked up into DMR values, for the client's signatory to review.
- 03Later
Case narratives
The narrative for a data package drafted from QC summaries and nonconformance notes, for your QA officer to rewrite and sign.
// One hard limit
It never reports, qualifies or changes a result.
It copies what your signed report already says into the format a client or agency asked for, on copies only, and stops there. It never picks the reportable result, never decides whether a sample or a permit limit passes, never loads, signs or submits a report, an EDD or a DMR, and never contacts a client or an agency. Your qualified staff decide, sign and release every file.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
The range depends on how many EDD formats you deliver to, how many jobs a month need one, and how many rows a typical job runs.
// Questions
What data managers ask about EDDs
Can it work from our LIMS export instead of the PDF report?
Will it pick which result is reportable after a dilution or a rerun?
Does it run our files through the agency's EDD checker?
Each consultant wants a slightly different version of the same format. Is that a problem?
Does it submit drinking water results to the state for us?

Rob Eason, founder
// Book a call with Rob
Bring the formats that cause the most rework.
Half an hour with Rob. Be ready with your lab and role, the EDD formats you deliver most, and roughly how many jobs a month need one. Client data stays with you until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
