Environmental data management software: follow the sample to the report
A field team collects a sample, the laboratory returns a result and a reviewer prepares a report. Then the lab issues a correction. Your evaluation should show which record changed, which report needs review and whether the original evidence remains available. Compare ESdat, EarthSoft EQuIS and Locus EIM using that complete journey.
Editorial review by Dimitris Mitsios
Founder of The QHSE Standard; product marketing at Tekmon. LinkedIn
Tekmon is a featured commercial partner. Disclosure and review scope
Keep the environmental buying scopes clear
| Scope | Record to evaluate | Buying question |
|---|---|---|
| Environmental data management | Locations, field samples, laboratory results, qualifiers and reviewed outputs. | Can a reviewer trace an exported result back to the sample, source file and correction history? |
| Environmental management | Site obligations, inspections, incidents and assigned actions. | How does a reviewed finding reach the responsible site team and retain its supporting data? |
| ESG and carbon reporting | Consolidated disclosures, activity data and calculation inputs. | How is approved site information transferred into the required reporting method and period? |
Agree what a valid result means before comparing dashboards
Ask your environmental specialist to define sample identifiers, matrices, analytes, units, methods, reporting limits, qualifiers and review states. An Electronic Data Deliverable (EDD) is a structured data file; passing its format checks does not establish that a measurement is suitable for every reporting decision.
Separate import checks, scientific review and comparisons against an approved criterion. Record the chosen criterion's source, version and applicability, plus any unit conversion. Treat an unreviewed result, a non-detect and an actual zero distinctly. Test the configured behavior rather than assuming a colored dashboard explains those decisions.
For adjacent workflows, use the Environmental Management guide or the ESG reporting comparison. This guide focuses on field and laboratory records.
Three product scopes and where to start the demo
The examples below reflect vendor documentation checked on 21 September 2026. The suggested starting points are editorial judgments, not performance rankings or hands-on test results.
ESdat
ESdat describes laboratory exchange, automated data checks, report review and approval. Its field programs connect monitoring plans, sample collection, electronic chain of custody and laboratory requests.
Start here when: the immediate problem is reconciling a recurring field program with your laboratories' deliveries.
Resolve in the quote: the actual laboratory connection and regional package. Advanced eQuote and eCOC integration is described for selected laboratories, so confirm the required exchange with yours.
Read the ESdat laboratory source
EarthSoft EQuIS
EQuIS Data Processor checks EDD formats and allowed values before import. Collect supports field forms with templates, reference values and upload status. These are components of a modular environment.
Start here when: your team needs to examine how several data submitters use a controlled format and how failed submissions return for correction.
Resolve in the quote: Collect, Enterprise, EDP, format development, hosting and the analysis or export modules actually demonstrated.
Read the EQuIS EDP source
Locus EIM
Locus describes EIM for analytical and field data, sample planning, checking, mapping and reporting. Its laboratory page distinguishes an EDD checker, laboratory submission interface and data validation functions.
Start here when: the evaluation must follow a sampling program across field users, laboratories and reviewers with different access needs.
Resolve in the quote: EIM, Mobile and any additional Platform applications. The linked profile covers that broader portfolio; a module name does not establish entitlement.
Read the Locus laboratory sourceCompare the three researched profiles side by side, including evidence, pricing scope and questions still to resolve.
Offline field capture has an online handoff
| Product | Documented field scope | Test before accepting |
|---|---|---|
| ESdat Field App | Offline field/sample capture with synchronization to ESdat. | Prepare the planned samples and attachments, then reconcile device records with accepted server records. |
| EQuIS Collect | Offline capture; internet is needed to upload. Running its server-based chain-of-custody report from the mobile app also needs connectivity. | Inspect received, accepted, rejected and completed upload states, including a deliberately invalid record. |
| Locus Mobile | Field use after provision files are downloaded. Transferring those files and synchronizing results requires cellular or Wi-Fi connectivity. | Check which locations, reference values and forms were provisioned, then review a change made while the crew was disconnected. |
Bring the same deliberately imperfect dataset
Use these fictional records to agree expected outcomes before each demo. They include a repeated result, an unmatched sample, a missing delivery, a non-detect and a later amendment. The analytes and values are invented; no regulatory or health threshold is supplied.
These are neutral CSV examples, not ready-to-import vendor EDDs. Ask each vendor to map them into the proposed format and show that the meaning survives. Perform the tests in an agreed demo environment.
Run five tests from planned sample to reviewed export
Reconcile what was planned, collected and delivered
Import the sample plan and original results. Locate the collected sample with no lab result, the uncollected sample and the result with an unknown field ID. Ask the operator to assign each exception for resolution without inventing a match.
Preserve the meaning of the measurements
Show the repeated result, units, method, reporting limit and ND qualifier. Establish whether duplication is rejected or flagged. Demonstrate how a non-detect remains distinguishable from zero and how any conversion retains the original value and unit.
Process the amendment without losing the original
Load the second version of result R001. Show both versions, the review decision and the affected report. Identify how recipients know that an earlier export is superseded; automatic notification is a requirement to demonstrate, not an assumed feature.
Complete the field-to-server handoff after disconnection
Prepare the proposed mobile app, disconnect and capture a fictional sample with an attachment. Reopen the app, reconnect and inspect upload status. Verify server receipt, record identity, timestamps, attachments and handling of any competing edit.
Export an explainable result under the right permissions
Use separate field, laboratory and reviewer accounts. Check the approved export for identifiers, original units, qualifiers, reporting limits, version and review status. Include the relevant source files and history, then confirm the licenses and services needed for this workflow.
Request a quote for the complete data journey
Record the evidence from all three demos
Open a scorecard with ESdat, EarthSoft EQuIS and the broader Locus profile. It includes five shared questions and three vendor-specific scope questions. Leave results untested until demonstrated.
Start the environmental data demo scorecardSources and scope of this comparison
Sources checked 21 September 2026. Vendor documentation describes advertised scope; it does not establish tested performance, complete license entitlement or regulatory compliance. The dataset and acceptance exercises are editorial examples. Have your environmental team approve the real data model and reporting rules.
- ESdat: laboratory integration and review
- ESdat: field programs and offline capture
- EarthSoft: EQuIS Data Processor (EDP)
- EarthSoft: EQuIS Collect, connectivity and licensing
- Locus: Environmental Information Management scope
- Locus: analytical and laboratory data management
- Locus: field provisioning and synchronization