Validation requires a traceable boundary, baseline, measurement chain, counterfactual, uncertainty statement, and rule against double counting.

Basin-scale conservation claims can lose meaning when allocation, diversion, delivery, application, and beneficial outcome are treated as the same quantity.

That distinction matters because irrigation decisions cross several boundaries: a water record becomes a physical delivery, a delivery becomes a hydraulic condition, and that condition becomes a root-zone response. A number at one boundary cannot automatically prove performance at the next.

The mechanisms to keep visible.

01

A reduced diversion is not automatically a consumptive-use saving.

02

Field efficiency changes can alter return flows and downstream accounting.

03

Modeled and measured values must remain visibly distinct.

Turn the pain point into a defined operating question.

State exactly where in the water chain the claimed change occurs and who can review the supporting record.

Start with the decision the analysis must support. Then identify the smallest set of inputs capable of changing that decision. Keep source facts, calculations, model outputs, estimates, and operator observations distinct throughout the workflow.

Make the result reviewable.

Document baseline period, meters, transformations, missing data, field operation, and the disposition of conserved water.

Define the boundaryName every input and unitPreserve source and timestampExpose assumptionsClassify the evidenceRecord missing information

What this analysis cannot establish by itself.

Basin accounting and legal determinations require applicable agency methods and qualified review.

SIM treats an honest limitation as part of the result. Where evidence is incomplete, the correct status is inconclusive or unverified—not a more confident sentence.