Updated 21 September 2026

Environmental data buying guide

Water management software: trace a corrected reading through the report

A corrected meter reading changes a site's monthly water total. Then a laboratory amends a sample result after the reporting pack has been reviewed. Can your water management software show both changes, preserve the earlier evidence and keep missing information visible? Use this case to compare quantity tracking, quality records and reporting workflows.

Jump to the 11 products

Editorial responsibility: Dimitris Mitsios (Founder of The QHSE Standard; product marketing at Tekmon) · Tekmon pays for sponsored placements on this site (disclosure) · How pages are made · LinkedIn

Sources reviewed 21 September 2026. This is a documentation review and proposed software demonstration, not hands-on product testing or a site-specific water reporting method. Evaluation methodology.

TekmonAd

Explore its published safety, quality and maintenance workflows. Confirm modules and pricing in a scoped proposal.

Choose the water records your team needs

Workflow	Record to demonstrate	Separate decision
Quantities and movements	Source, meter, units, period, site boundary, withdrawals, transfers, discharge and storage	A quantity or unexplained balance does not establish water quality or compliance.
Samples and quality	Sample location/time, method, parameter, units, qualifier, laboratory file and amendments	One sample is not evidence for every outfall, period or reporting parameter.
Discharge and permit review	Applicable permit/version, monitoring point, relevant conditions, reviewer and supporting records	A dashboard or generated report does not itself establish fulfilment of the site's obligations.
Water-risk screening	Location, indicator, dataset/version, time horizon, assumptions and local follow-up	A mapped water-stress score is not a discharge assessment or a measured sample result.

Documented water software scopes to investigate

The linked profiles are broader than water. Their prices, offline fields and evidence dates do not describe equivalent water packages or establish the capabilities of every named application; ask to demonstrate the original file, amended result and reviewer decision together in the quoted configuration.

Compare the first listed profiles side by side

Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

Same rule for every product: tagged “Environmental Management”, “Environmental Monitoring”, “Sustainability Data” or “ESG Reporting”, with a sourced water capability in its record, or one the vendor stated to us, labelled as vendor-stated. 11 qualify; the first 8 are shown, then the other 3.

ERA-EHS
Documented: Water discharge and refrigerant compliance records. Source: era-environmental.com
Microsoft Sustainability Manager
Documented: Water quantity analytics. Source: learn.microsoft.com
Tekmon
Vendor-stated: Water Management. Not yet confirmed in public documentation; ask to see it in a demo.
Cority
Cority describes collecting laboratory, inspection and SCADA data, tracking water permits and thresholds, generating reports and viewing water-use indicators. Name each laboratory or SCADA connection and demonstrate its format, validation and owner; the page does not establish that every connector, historical version or report approval is included. Source: cority.com
IsoMetrix
Documented: Environmental performance. Source: isometrix.com
Sphera
Sphera documents sampling data associated with water permits, water-discharge calculations, validation rules, form entry and spreadsheet imports, including the effect of data errors. Demonstrate the chosen calculation, parameter mapping, source units and reporting period, and retain the earlier reviewed calculation after an amendment; this scope does not establish a utility-meter network or water-risk mapping. Source: sphera.com
VelocityEHS
Documented: Environmental compliance and obligation tracking. Source: ehs.com
Diligent ESG
Documented: Licensed Activity Data and Reports APIs (conditional). Source: developer.diligent.com

Also meet the rule, in the same order (3)

Demo case: correct a meter and a laboratory result after review

Use fictional site SITE-017 and the complete July 2026 reporting period, 1 July 00:00 to 1 August 00:00 in the recorded site time zone. METER-017 measures incoming third-party water at the defined site boundary. Its cumulative start reading is 10,000 m³ and its initially recorded end reading is 11,200 m³, giving a period withdrawal of 1,200 m³. Save both source readings and their timestamps in RPT-017 revision 1.

Introduce evidence that the end reading was transcribed incorrectly. METER-017 revision 2 records 11,250 m³, so the period withdrawal becomes 1,250 m³. Retain the earlier 1,200 m³ result, the corrected evidence, author, reason and review. For this synthetic calculation, explicitly confirm the same meter and period and that no reset or rollover occurred; those cases need their own rules.

The same pack contains a separately measured discharge of 800 m³, an internal recirculation record of 300 m³, and storage readings of 100 m³ at the start and 150 m³ at the end. A possible additional outflow remains unquantified. Keep those records separate: recirculation within the boundary is not another external withdrawal. Do not label the difference between selected meters as consumption, a leak or compliance; the boundary, completeness, storage context and applicable reporting method still need review.

Sample SAMPLE-017 belongs to OUT-017 and has its own sampling timestamp, method and units. Fictional parameter P is reported as 4 mg/L in LAB-017 revision 1. An amended laboratory report, LAB-017 revision 2, changes that result to 6 mg/L. Preserve both laboratory files, qualifiers, the amendment reason and the affected report references. These invented values are sample results, not discharge limits; they do not establish a pollutant load without the appropriate method and supporting data.

A separate expected result, LAB-018, is still unavailable. Keep it missing, with an owner and follow-up status; do not substitute zero or copy SAMPLE-017. Prepare RPT-017 revision 2 as a new draft, showing the meter correction, laboratory amendment and unresolved evidence. Preserve the earlier reviewed pack and ask the responsible reviewer to determine the reporting impact. This exercise does not supply a submission or compliance decision.

Keep the calculation, sample and report histories connected

Synthetic record	Original and changed evidence	Demonstration outcome
METER-017	10,000 → 11,200 m³, then corrected end reading 11,250 m³	Reproduce period withdrawals of 1,200 m³ and 1,250 m³ with source readings, period and correction history.
SITE-017 water movements	800 m³ discharge; 300 m³ internal recirculation; storage 100 → 150 m³; another outflow unquantified	Separate boundary crossings, internal movement and a 50 m³ storage increase. Keep the incomplete reconciliation visible.
SAMPLE-017 / LAB-017	Fictional parameter P: 4 mg/L in laboratory revision 1 → 6 mg/L in revision 2	Preserve sampling context, methods, qualifiers, original/amended files and reviewer decision.
LAB-018	Expected result unavailable	Show missing evidence and follow-up ownership; no invented zero, copied result or automatic compliant status.
RPT-017 revision 1 → revision 2	Earlier reviewed pack → draft with corrected quantity and amended sample	Both versions remain reproducible, with affected inputs, outstanding evidence and an explicit review status.

Agree the quantity method and reporting boundary

The GRI 303 standard distinguishes withdrawal, discharge and consumption, asks for the basis of reported data, and addresses changes in storage where significant. Use its definitions when that is your reporting basis. A software total needs the chosen period, boundary, source coverage and documented treatment of estimates; do not mix a corporate disclosure calculation with an operational reconciliation without explaining the method.

In the demo, import one volume in litres and show the original unit and conversion to cubic metres. Then attempt to import a flow rate in m³/hour into the volume field. Show that it needs a defined duration and calculation rather than being treated as the same quantity. Test duplicate imports, meter resets, estimated intervals and late corrections separately.

Ask how the configuration distinguishes measured, estimated, calculated and missing values. Include transfers between sites and internal recycling in the boundary review so consolidated totals do not count the same movement twice. Keep any incomplete stream and the person responsible for resolving it visible.

Give permit review and risk screening their own evidence

The US EPA NPDES overview describes permits with discharge conditions, monitoring and reporting requirements. Treat that as a US example, not a rule for every site. Ask the responsible specialist to identify the applicable permit or other obligation, effective version, monitoring points and review basis. A water report template does not determine which duties apply.

WRI explains that Aqueduct's baseline water-stress indicator gives a broad view of competition for water and does not account for water quality or environmental needs; local conditions can differ. Retain the selected location, indicator, dataset and time horizon, then assign local follow-up. Ask whether that assessment is performed externally, imported or connected through a specifically supported integration.

A mapped risk score does not close the missing LAB-018 result or establish discharge compliance. For the obligation and applicability workflow, continue to the Legal Register guide. For laboratory validation and amendments, use the Environmental Data Management guide.

Six demonstrations before choosing water management software

Define one complete reporting boundary

Create SITE-017, its water sources, meter/outfall IDs, internal transfers, storage, time zone and July period. Identify missing streams and the chosen calculation basis before displaying a consolidated result.

Correct a meter without rewriting history

Change the ending reading from 11,200 to 11,250 m³. Reproduce the 1,200 and 1,250 m³ withdrawals and show evidence, units, timestamps and review. Test a duplicate or flow-rate import separately.

Amend a laboratory result

Load LAB-017 revision 2 with the invented 6 mg/L result. Keep the earlier 4 mg/L file, method, units and qualifiers available, and identify each affected report without silently replacing its reviewed evidence.

Expose missing evidence and incomplete movements

Show LAB-018 as unavailable and the additional outflow as unquantified. Keep internal recirculation and storage visible; neither a blank result nor an unexplained difference becomes zero or compliant.

Review the changed reporting pack

Prepare RPT-017 revision 2 as a draft. Trace the applicable permit or reporting basis, the changed records and the responsible review. Keep generation, review, issue and recipient acknowledgement distinct where required.

Export a reproducible record

Deliver meter readings, units, calculation basis, boundary, laboratory versions, missing-data status and report history. Include the separate water-risk assessment and identify any connection that needs additional configuration.

Put the water data responsibilities in the quote

Name the water applications, sites, meters, monitoring points, laboratory programmes and reporting outputs in scope.

List source formats, laboratory systems, SCADA or meter connections, supported versions, update intervals and integration owners.

Assign responsibility for units, conversions, meter events, data-quality rules, reporting boundaries and calculation changes.

Demonstrate permissions, laboratory amendments, source documents, reviewer decisions and preservation of earlier reports.

Separate mobile field capture, disconnected work, synchronization and server calculations; a platform claim does not establish every step.

Price historical-data migration, validation, report maintenance, water-risk data access and complete evidence export.

Shortlist around the water records you must explain

Explore environmental applications, then ask each vendor to demonstrate the named water scope with one corrected meter, one amended sample and the complete review history.

Browse Environmental Management applications

Sources and limits of this guide

7 sources

Vendor pages establish documented scope, not a tested configuration. GRI supplies one reporting framework; EPA supplies US permit context; WRI explains risk indicators. None establishes a universal reporting obligation. All exercise records and values are fictional. No operating discharge limit, missing-data substitution, site-specific calculation method or live filing instruction is prescribed.

Software categories to explore

Use this Process to define the work, then explore these software types. Confirm the exact workflow and module with each vendor.

See all software categories

ISO 14001 Implementation Guide: A 12-Step EMS Roadmap
Article on ISO 14001 implementation.
EMS (Environmental Management System) — definition, software & FAQs
Definition of an environmental management system.
Spill or Release Incident Report Template
Free template for a spill or release incident report.

Frequently Asked Questions

What is the difference between water quantity and water quality software?

Quantity records describe volumes, flows, sources, transfers, discharge and storage within a defined period and boundary. Quality records describe samples, parameters, methods, units, qualifiers and laboratory results. A programme can need both, but a meter total cannot substitute for a sample result or establish permit compliance.

Can withdrawal minus one discharge meter be reported as consumption?

Not without checking the reporting definition, boundary, period and completeness of the inputs. The guide's case includes storage change and an unquantified outflow, so it does not calculate consumption from the selected meter difference. Retain assumptions, missing streams and the approved reporting method; internal recirculation also needs separate treatment.

What should happen when a laboratory amends a result?

Preserve the original and amended source files, sample context, units, methods, qualifiers and reason. Identify affected calculations and reports, retain the earlier reviewed pack and demonstrate the responsible review of a new revision. An unavailable result remains a visible gap, not zero or a copied sample.

Does a water-risk score establish discharge compliance?

No. Risk screening has its own indicator, geography, time horizon and limitations. WRI describes baseline water stress as a broad indicator with local limitations, not a water-quality result. Keep the assessment separate from sampling evidence and the site's applicable permit review.

Is water reporting mandatory for every organisation?

This guide does not establish a universal duty. The responsible specialist must identify the obligations and reporting basis applicable to the organisation, site and activity. A named framework or a vendor's report template does not by itself determine applicability, required content, review or submission acceptance.

Do water software packages include every meter and laboratory connection?

Do not assume so. Confirm the named applications, source formats, supported versions, licenses and integration owner. Demonstrate validation, duplicate handling, amendments and delayed data in the proposed configuration. Existing broader profile prices and offline evidence do not prove every water workflow or connector is included.