D6 ยท Publication Volume 22

Water and Catchments

water balance, quality, groundwater and surface water

Learning objectives

By the end of this lesson, the learner should be able to frame a defensible decision about water balance, quality, groundwater and surface water; distinguish observation, interpretation, assumption, obligation and decision; construct a causal pathway with explicit spatial and temporal boundaries; use quantitative evidence without false precision; identify distributional and long-duration consequences; specify controls with triggers and accountable responses; and design a versioned evidence package that can be independently reviewed.

The objective is transferable reasoning, not memorisation of a jurisdiction, organisation or operating procedure. A learner must state where current law, rights, permits, engineering authority or specialist review governs a real decision. The tutorial supplies no universal threshold and authorises no field activity, disclosure, facility or closure outcome.

Decision context

The decision is whether a proposed water system can meet quantity, quality, ecological, operational and closure objectives across wet, dry, average and changed conditions. Begin with catchments and connected aquifers rather than infrastructure alone. State the control volume, time step, water types, external users, environmental functions and the conditions under which transfer, storage, discharge or abstraction is permitted.

Write a decision contract before analysis. It should name the decision owner as a role rather than a person, affected systems, lifecycle phase, spatial and temporal support, applicable authority to be verified, evidence cut-off, alternatives, uncertainty, dependencies, irreversible choices and review trigger. Separate what the analysis can inform from what it cannot approve. If the boundary excludes a pathway or affected group, record the reason and the evidence needed to reconsider it.

Core concept: system and boundary

Water and Catchments: simplified institution-neutral teaching model
Water and Catchments: simplified institution-neutral teaching model

A water balance is a conservation model with uncertain fluxes and storage, not a decorative flow diagram. Rainfall, runoff, seepage, groundwater exchange, entrained water, evaporation, abstraction, return, treatment, discharge and inventory must use compatible units and periods. Connectivity may change after excavation, dewatering, lining failure, rehabilitation or extreme events.

Map the system as linked objects rather than a flat issue list. For every object, ask what state can change, which process causes the change, how quickly it propagates, what feedback exists and which observations could distinguish competing explanations. Keep physical, ecological, social, legal and governance relationships connected without pretending that one discipline can decide for another.

Core concept: pathways and obligations

Water quality is multivariate and pathway-dependent. Concentration, load, speciation, acidity, salinity, turbidity, temperature and biological response answer different questions. A low concentration at high flow can carry a large load; a small seepage with persistent exposure can matter locally. Mixing calculations do not capture reactions, settling, sorption, redox change or ecological thresholds unless those processes are represented.

Obligations and controls also have a lifecycle. Record their origin, exact wording, intended outcome, affected interest, responsible role, dependencies, start condition, evidence, review point and release condition. Do not convert a conditional commitment into an unconditional claim, or a professional recommendation into an approved requirement. Where rights or consent apply, preserve the conditions and authority attached to them.

Quantitative reasoning

For a declared control volume and time step, Delta S=P+I+G_{in}-Q-E-O-G_{out}, where terms represent precipitation, imported water, groundwater inflow, controlled release, evaporation, other outflows and groundwater outflow. Constituent load is L=QC only when flow Q and concentration C are time-aligned and use compatible units. Residuals must be reported rather than silently forced to zero.

Before calculating, declare system boundary, support, units, time zone, reporting period, denominator, treatment of missing and censored data, uncertainty model and rounding. Compare raw, adjusted and modelled values rather than overwriting one with another. Sensitivity analysis should vary plausible drivers jointly where they are dependent. A neat number is not evidence that the underlying model is complete.

Evidence and uncertainty

Evidence includes gauged flow, stage, rainfall, evaporation, water level, hydraulic head, chemistry, field parameters, sampling support, analytical qualifiers, pumping, transfer records and storage geometry. Rating curves, ungauged inflows and extreme-event estimates carry model uncertainty. Non-detects require method limits and an explicit calculation rule; they are not zeros.

Classify evidence as direct observation, laboratory result, derived value, model output, stakeholder or rights-holder input, requirement, expert judgement or assumption. Attach method, date, location or population support, quality state, access restriction and lineage. Confidence should explain both variability in the system and knowledge uncertainty. Conflicting evidence remains visible until a documented decision resolves or bounds it.

Lifecycle controls

Controls may separate clean and contact water, reduce exposed source areas, manage storage freeboard, maintain conveyance, collect seepage, treat water, stage release, protect receiving flows and define contingency capacity. Each control needs an operating envelope and a response to forecast exceedance, observed exceedance, sensor failure and loss of access. Closure must address declining supervision and long-duration maintenance.

Use a control record with unwanted event, causal pathway, prevention or mitigation function, performance requirement, leading and lagging indicators, verification frequency, trigger, immediate response, escalation authority, recovery action and evidence of effectiveness. Controls must survive foreseeable change in climate, schedule, staff, contractors, data availability and lifecycle phase. A monitoring point without a response rule observes risk but does not control it.

Interfaces and data

Use a network model linking catchments, aquifers, nodes, storages, transfers, monitoring points, receptors and permissions. Store raw observations separately from approved time series and model inputs. Every value needs timestamp, timezone, unit, datum, method, location, quality flag and transformation lineage. A monthly average should never overwrite the events from which it was derived.

The minimum exchange contract specifies identifier, geometry or population support, coordinate and vertical reference where relevant, time basis, unit, vocabulary, null semantics, method, uncertainty, quality status, sensitivity, licence or use condition, version and checksum. Preserve raw evidence and make transformations reproducible. A dashboard, map or report is a view of controlled evidence; it must not become the only surviving record.

Integration checkpoint

The lesson checkpoint passes only when another reviewer can follow the chain from decision and affected interest through water balance, quality, groundwater and surface water, evidence, uncertainty, alternatives, control and residual obligation. Every claimed control must have an observation that can test it, and every material observation must have a pre-agreed response path.

Ask four integration questions: What can change the conclusion? Who experiences the outcome and who has authority? Which lifecycle handover could lose the evidence or obligation? What remains after the proposed control succeeds? If any answer is hidden in narrative, convert it to a controlled record before advancing.

Synthetic worked example

A synthetic monthly balance receives 92 units of precipitation, 18 of imported process water and 7 of groundwater inflow. Measured release is 34, evaporation 21, other outflow 12 and groundwater outflow is estimated as 8; observed storage rises by 36. The arithmetic predicts a rise of 42, leaving a residual of 6. The learner tests meter bias, ungauged runoff, storage-curve error and timing mismatch before changing any flux.

The numbers and labels are synthetic and intentionally incomplete. Recalculate them from the stated basis, show any residual, and create at least two plausible explanations before selecting an action. Mark the evidence that would discriminate among explanations. Do not transplant the illustrative quantities, triggers or acceptance language to real work.

Practice task

Construct a node-and-link water balance for a fictional catchment containing an undisturbed diversion, an operational storage, a seepage collection point and a downstream receptor. Reconcile one period, calculate two constituent loads, mark uncertain fluxes, and define a trigger-response record for both excess water and insufficient environmental flow.

Submit the artefact with a one-page decision statement, data dictionary, assumptions register, alternative explanation, control table and change log. A peer should be able to locate every input and challenge every conditional step. The task is incomplete if it relies on an unnamed rule, a private conversation, an unexplained score or a figure that cannot be traced to versioned evidence.

Common failure modes

Common failures are mixing daily and monthly terms, confusing depth with volume, ignoring groundwater, using one concentration to represent a variable discharge, treating modelled flux as measured, hiding balance residuals, selecting monitoring points for convenience rather than pathways, and assuming a closure landform has the same infiltration and routing as its design drawing.

A cross-cutting failure is institutional storytelling: wording that implies a named organisation, person or website owns, endorses or supplies the tutorial or its conclusions. Another is site mimicry, where an invented example looks like a real property and borrowed parameters appear authoritative. Keep examples explicitly synthetic, roles anonymous, external names in source notes only and every real application dependent on current local evidence and authority.

Lesson summary

Defensible water management joins catchment and aquifer connectivity, conservation, quality processes, ecological and human receptors, operating controls and closure. The balance remains useful only when boundaries, units, uncertainty, residuals and versioned inputs are visible.

The durable output is not a final-looking score. It is a reviewable chain connecting purpose, affected systems, evidence, uncertainty, alternatives, decisions, controls, responsibilities and remaining obligations. That chain must be capable of change without erasing the earlier state.

Review questions

  1. What boundary and decision contract are required for water balance, quality, groundwater and surface water?
  2. Which observations would distinguish the two most plausible causal explanations?
  3. Which quantities can be conserved or reconciled, and which judgements cannot be reduced to a score?
  4. How can a missing observation differ from a confirmed absence or zero?
  5. Which control has the earliest useful trigger and what action follows it?
  6. What evidence and obligation must survive the next lifecycle handover?
  7. How would you communicate the residual consequence without implying approval or certainty?

Sources