SOURCE · MEASUREMENT · EVENT · DESTINATION · BALANCE

Farm Water
Accounting

Farm water accounting connects observations about water sources, transfers, storage, pumping, irrigation events, and destinations into a reviewable record. It is not the same as an exact physical water balance, a water-right determination, an irrigation schedule, or proof that measured water reached a crop uniformly.

SOURCEWELL · SURFACE · STORAGE · DELIVERY
MEASUREDEVICE · TIME · UNITS · QUALITY
RECONCILEFIELD · EVENT · TRANSFER · LOSS
BOUNDARYACCOUNT ≠ LEGAL DETERMINATION
EVIDENCECorroborated
BRIEFING FLIGHT PLAN / VISUAL READING ROUTE
5CHAPTERS4VISUAL BLOCKS6GRAPH LINKS2SOURCES
HOW TO READ THIS PAGE

Visual explanationA diagram or operating scene makes the relationship visible.

Structured modelA flow, comparison, capability set, or boundary map organizes the idea.

Guided explanationOriginal prose connects the concept to its operating context.

This route describes the briefing's editorial structure. It is not an implementation sequence, maturity score, compatibility claim, or field recommendation.

A water record
needs a chain of custody.

Utah State University Extension provides irrigation-flow measurement context, while University of Minnesota Extension provides broader irrigation-management context. Together they support an accounting workflow built from qualified measurements and explicit assumptions.

Useful accounting keeps the measurement device and method, units, timestamp, source and destination identity, event linkage, calibration or maintenance context, gaps, estimates, transformations, and reconciliation period visible.

Identify, measure,
reconcile, review.

01IDENTIFY / 01Define sources and destinationsWater source and authority, storage and transfer points, pump and delivery system, field or zone identity, period, and accounting boundary
02MEASURE / 02Capture qualified observationsDevice and method, timestamp, units, location, calibration and maintenance context, operating range, raw record, flags, and gaps
03RECONCILE / 03Link water to eventsIrrigation or transfer event, system runtime and state, measured and estimated values, transformations, duplicates, missing intervals, and uncertainty
04REVIEW / 04Explain the accounting differenceOpening and closing context, transfers, measured use, storage change where relevant, unexplained difference, corrections, and follow-up
Read left to right as an explanatory evidence path. Arrows do not encode a protocol, automatic control sequence, compatibility claim, or operating instruction.

A precise total
can still hide uncertainty.

LayerCan supportCannot establish alone
Flow measurementA water observation at a defined point and timeDistribution or crop use across a field
Event recordOperational linkage to field or system activityExact physical delivery without measurement context
ReconciliationA transparent difference and uncertainty reviewA legal water-right conclusion
Management reviewQuestions about efficiency or operationsA universal irrigation prescription

Make uncertainty
part of the ledger.

BOUNDARY

Define what is being accounted

State source, destination, field or zone, time period, water authority, storage and transfer boundary, and excluded flows.

PROVENANCE

Keep measurement context

Retain device, method, location, units, timestamps, calibration or maintenance, range, flags, and original records.

RECONCILE

Separate measured and estimated values

Label estimates, missing intervals, conversions, corrections, assumptions, and unexplained differences rather than combining them silently.

REVIEW

Use totals as questions

Compare records with system condition, irrigation events, field observations, and qualified water-management review before acting.

Accounting is not
water-rights advice.

No flow-measurement procedure is reproduced.Use current device, extension, safety, and qualified professional guidance for installation, calibration, and measurement.

A farm ledger is not a legal determination.Water rights, allocations, reporting, and compliance require the applicable authority and jurisdiction-specific advice.

Measured input does not prove crop use or uniform delivery.Distribution, storage, losses, soil-water status, crop response, and return flows require separate evidence.

See the system around this concept.

Follow incoming and outgoing relationship records to understand what supplies, informs, enables, coordinates with, or extends this technology in the published knowledge graph.

Relationship radar / published edges6 records / 6 neighboring systems
Incoming04records point toward this concept
decide roleFarm Water AccountingSelected technology
Outgoing02records point from this concept

06connections visible

01incoming
observe / Agricultural environmental sensingEdge-of-Field Water-Quality Monitoring adds measured outflow evidence to

Qualified event and outlet-flow observations can contribute to a bounded farm water record when field, period, method, units, gaps, and uncertainty remain explicit.

Corroborated2 sources
02outgoing
decide / Water managementIrrigation Decision Support provides measured delivery context to

Water-accounting records can inform irrigation review by keeping source, flow measurement, time, area, delivery event, uncertainty, and reconciliation visible.

Verified2 sources
03incoming
observe / Irrigation managementCenter-Pivot Uniformity Testing adds distribution evidence to

Center-pivot testing can add spatial delivery evidence to water accounting while source flow, operating time, field area, machine state, sampling method, and uncertainty remain visible.

Verified3 sources
04outgoing
act / Irrigation controlVariable Rate Irrigation provides measured water-use context to

Water accounting can inform VRI review by preserving source, flow measurement, time, field or zone, command context, event linkage, distribution evidence, estimates, and uncertainty.

Verified3 sources
05incoming
act / Irrigation controlIrrigation Pump Control adds runtime and hydraulic context to

Pump-control records can inform water accounting when source, device and method, flow and pressure evidence, timestamps, valves, operating state, overrides, faults, estimates, and calibration context remain explicit.

Corroborated3 sources
06incoming
decide / Water managementIrrigation Scheduling Workflows provides intended-event context to

Scheduling records can supply planned timing, target, field, zone, assumptions, and authorization context to water accounting, while measured delivery and reconciliation remain separate.

Verified3 sources
LEARNING ROUTE BRIDGE / THIS NODE IN MOTION
2CONNECTED ROUTES45STEP POSITIONS14ROUTE SOURCE LINKS
Operating practice

Build an accountable water-delivery record

Move from a physical drip-system check through qualified flow, pump context, scheduling, accounting, and field water-balance reconciliation.

CURRENT POSITION05
05 / ACCOUNT

Create the water account

Preserve source, measured delivery, time, field or zone, intended event, estimates, adjustments, exceptions, uncertainty, and reconciliation status.

Open the complete route ↗
Routes are editorial learning sequences, not implementation orders, product rankings, or field prescriptions. Select a route to see how this technology concept connects to the decisions around it.

Primary sources.

This original briefing uses Utah State University Extension flow-measurement material and University of Minnesota irrigation-management context. It makes no legal, measurement-procedure, water-right, efficiency, or scheduling claim.

01
Accurate Irrigation Water Flow Measurement in PipesUtah State University Extension · Accessed 2026-07-23
02
Irrigation managementUniversity of Minnesota Extension · Accessed 2026-07-12
NEXT / TEST THE SYSTEM

Compare accounting records with a measured center-pivot distribution review.

Open center-pivot uniformity testing