Water Resources Board

Tell us what to change or add.

1. Check a decision

Open a decision below. Check the area, period, inputs, result and proposed next step.

2. Try the inputs

Use Example input to change a sample. Use Source input to check the fields and source details. The land-use change decision has its own comparison views.

Record your corrections below, then download your answers or print them.

3. Check each decision

1. Check wells showing sustained drawdownDEC-DP21-001 · Groundwater depletion · Suggested priority: High
Try this decision

Investigate wells showing sustained drawdown.

Validation required

Observed value — fictional 2025 examples

Method. Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean.

Next step. Review evidence. Investigate persistent changes, review the operating plan, or extend monitoring.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Groundwater head relative to the stated datum [m]; Datum, pumping state and measurement convention

Other required evidence. Well ID; groundwater level; datum; pumping history; rainfall; observation dates.

Fictional worked example · 2025

Laggala Pallegama — groundwater depletion · Laggala Pallegama

Input or resultValueUnit
Groundwater head relative to the stated datum104m
Datum, pumping state and measurement conventionSample common head datum; static measurement
Observed value104m

Groundwater head and depth below ground have opposite directional meanings. Match datum, pumping state and seasonal context; observed drawdown is not itself a safe-yield estimate.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Trend and uncertainty after action using the same definition.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
2. Adjust monitoring to seasonal groundwater variationDEC-DP21-002 · Seasonal groundwater · Suggested priority: High
Try this decision

Adjust monitoring to seasonal groundwater variation.

Validation required

Difference — fictional 2025 examples

Method. Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive.

Next step. Review evidence. Verify the observation, refer a confirmed exception, or retain it with explanation.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Comparable reference value [m]; Later/comparison value [m]

Other required evidence. Well ID; water levels; season; abstraction; rainfall; comparable baseline.

Fictional worked example · 2025

Laggala Pallegama — seasonal groundwater · Laggala Pallegama

Input or resultValueUnit
Comparable reference value100m
Later/comparison value90m
Difference-10m
Relative change-10%

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Validated exceptions, response time and resulting outcome.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
3. Check wells exceeding applicable use-specific limitsDEC-DP21-003 · Groundwater quality · Suggested priority: High
Try this decision

Investigate wells exceeding applicable use-specific limits.

Validation required

Measured value — fictional 2025 examples

Method. Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status.

Next step. Outside example comparison bounds. Refer a confirmed nonconformance for authorized response, resample, or investigate the method.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Parameter and applicable use; Measured result [mg/L]; Example lower comparison bound [mg/L]; Example upper comparison bound [mg/L]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis

Other required evidence. Well sample; parameter; result; unit; laboratory method; applicable limit.

Fictional worked example · 2025

Laggala Pallegama — groundwater quality · Laggala Pallegama

Input or resultValueUnit
Parameter and applicable useWell-water chloride for selected use
Measured result230mg/L
Example lower comparison bound0mg/L
Example upper comparison bound200mg/L
Original and limit unitmg/L
Sampling and analytical method/versionSample laboratory method
Limit source, version and useFictional comparison bounds; not a regulatory limit
Parameter, unit, use and averaging period matchYes
Result is below a reporting/detection limitNo
Averaging interval, sampling depth or process basisSample stated sampling/averaging basis
Measured value230mg/L

Example bounds establish no compliance or diagnosis. Ambient, drinking-water, effluent, crop, food, air and noise standards are not interchangeable. A censored result is not an exact zero.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Follow-up compliance, exposure/service condition and corrective closure.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
4. Select groundwater areas needing observation wellsDEC-DP21-004 · Monitoring coverage · Suggested priority: High
Try this decision

Select groundwater areas needing observation wells.

Validation required

Verified coverage — fictional 2025 examples

Method. 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown.

Next step. Review evidence. Select eligible underserved units for outreach, investigate missing coverage, or revise the verified frame.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Required eligible frame [aquifer units]; Distinct members of that frame covered [aquifer units]; Frame members with unknown coverage [aquifer units]

Other required evidence. Aquifer units; existing wells; observation dates; abstraction areas; coverage need.

Fictional worked example · 2025

Laggala Pallegama — monitoring coverage · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100aquifer units
Distinct members of that frame covered65aquifer units
Frame members with unknown coverage5aquifer units
Verified coverage65%
Known uncovered30aquifer units
Unknown coverage5aquifer units

Count each eligible unit once for the selected service and period. Received messages, attendance, adoption and outcomes are separate measures.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Verified eligible units receiving service and remaining unmet need.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
5. Shortlist sites requiring detailed groundwater investigationDEC-DP21-005 · Borehole siting · Suggested priority: High
Try this decision

Shortlist sites requiring detailed groundwater investigation.

Validation required

Evidence gaps — fictional 2025 examples

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Shortlist technically feasible alternatives, reject exclusions, or request site evidence.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Geology; Geology evidence reference; geophysics; geophysics evidence reference; nearby wells; nearby wells evidence reference; demand; demand evidence reference; contamination risks; contamination risks evidence reference; land access; land access evidence reference

Other required evidence. Geology; geophysics; nearby wells; demand; contamination risks; land access.

Fictional worked example · 2025

Laggala Pallegama — borehole siting · Laggala Pallegama

Input or resultValueUnit
GeologyMissing
Geology evidence reference
geophysicsDocumented
geophysics evidence referenceSample Laggala Pallegama field register / 2025
nearby wellsDocumented
nearby wells evidence referenceSample Laggala Pallegama field register / 2025
demandDocumented
demand evidence referenceSample Laggala Pallegama field register / 2025
contamination risksDocumented
contamination risks evidence referenceSample Laggala Pallegama field register / 2025
land accessDocumented
land access evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Field-verified limiting factors and observed performance.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
6. Refer pumping-test results for safe-abstraction assessmentDEC-DP21-006 · Pumping tests · Suggested priority: High
Try this decision

Refer pumping-test results for safe-abstraction assessment.

Validation required

Difference — fictional 2025 examples

Method. Reproduced minus expected result, within an explicitly supplied absolute tolerance, using the same exact input/method versions and a separate checker. Retain originals, code, parameters and environment evidence.

Next step. Investigate reproduction difference. Accept reproducible evidence for review, investigate differences, or withhold an unsupported result.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [m³/day]; Independently reproduced value [m³/day]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m³/day]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Pumping rate; drawdown; recovery; test duration; aquifer model; uncertainty.

Fictional worked example · 2025

Laggala Pallegama — pumping tests · Laggala Pallegama

Input or resultValueUnit
Earlier/source value100m³/day
Independently reproduced value90m³/day
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable m³/day measure; same input scope
Documented absolute comparison tolerance0.01m³/day
Expected input/method versionSample input1 /method1
Reproduced input/method versionSample input1 /method1
Original result creatorPreparation officer
Independent reproducerIndependent checking officer
Difference-10m³/day
Relative change-10%

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Independent reproduction within the approved tolerance.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
7. Compare recorded abstraction with reviewed aquifer budgetsDEC-DP21-007 · Abstraction balance · Suggested priority: High
Try this decision

Compare recorded abstraction with reviewed aquifer budgets.

Validation required

Calculated closing storage — fictional 2025 examples

Method. Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing.

Next step. Reconcile closing balance. Investigate unexplained balances and propose revised measurement or operating action.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Opening storage [m³]; Recharge and external groundwater inflow [m³]; Abstraction and groundwater outflow [m³]; Other identified non-overlapping water outflow [m³]; Independently observed closing storage [m³]

Other required evidence. Recharge estimate; abstraction; inflows; outflows; storage change; uncertainty.

Fictional worked example · 2025

Laggala Pallegama — abstraction balance · Laggala Pallegama

Input or resultValueUnit
Opening storage160,000m³
Recharge and external groundwater inflow48,000m³
Abstraction and groundwater outflow35,000m³
Other identified non-overlapping water outflow9,000m³
Independently observed closing storage163,500m³
Calculated closing storage164,000m³
Observed minus calculated closing-500m³

A storage-change calculation needs a defined aquifer boundary and compatible volume estimates. Groundwater head in metres is not a storage volume; uncertainty and safe-abstraction review remain separate.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Reconciled balance residuals and verified operating results.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
8. Check contamination sources near supply wellsDEC-DP21-008 · Well protection · Suggested priority: High
Try this decision

Investigate contamination sources near supply wells.

Validation required

Documented separation — fictional 2025 examples

Method. Display measured separation with hydrogeological direction, source type and the reviewed protection criterion. Distance alone cannot determine contamination, safety or a statutory protection area.

Next step. Review evidence. Refer affected sites for technical/legal review, revise the footprint, or request a field survey.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Documented source-to-well separation [m]; Potential contamination source and observation reference; Hydrogeological flow-direction evidence; Use-specific reviewed protection criterion

Other required evidence. Well coordinates; land uses; hazard sources; protection criteria; flow direction.

Fictional worked example · 2025

Laggala Pallegama — well protection · Laggala Pallegama

Input or resultValueUnit
Documented source-to-well separation150m
Potential contamination source and observation referenceSample documented source
Hydrogeological flow-direction evidenceNot provided
Use-specific reviewed protection criterionNot provided
Documented separation150m

Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Resolved constraints and independently checked site conditions.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
9. Choose what to handle first: coastal groundwater salinity investigationsDEC-DP21-009 · Saline intrusion · Suggested priority: High
Try this decision

Prioritize coastal groundwater salinity investigations.

Validation required

Observed value — fictional 2025 examples

Method. Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean.

Next step. Review evidence. Investigate persistent changes, review the operating plan, or extend monitoring.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Comparable observation [µS/cm]

Other required evidence. Conductivity; chloride; groundwater head; pumping; location; tidal influence.

Fictional worked example · 2025

Laggala Pallegama — saline intrusion · Laggala Pallegama

Input or resultValueUnit
Comparable observation104µS/cm
Observed value104µS/cm

Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Trend and uncertainty after action using the same definition.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
10. Refer industrial groundwater requests for determinationDEC-DP21-010 · Industrial abstraction · Suggested priority: High
Try this decision

Refer industrial groundwater requests for determination.

Validation required

Evidence gaps — fictional 2025 examples

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Submit a recommendation to the appointed authority, request evidence, or record an appeal.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Demand; Demand evidence reference; hydrogeological report; hydrogeological report evidence reference; abstraction proposal; abstraction proposal evidence reference; permits; permits evidence reference; monitoring conditions; monitoring conditions evidence reference

Other required evidence. Demand; hydrogeological report; abstraction proposal; permits; monitoring conditions.

Fictional worked example · 2025

Laggala Pallegama — industrial abstraction · Laggala Pallegama

Input or resultValueUnit
DemandMissing
Demand evidence reference
hydrogeological reportDocumented
hydrogeological report evidence referenceSample Laggala Pallegama field register / 2025
abstraction proposalDocumented
abstraction proposal evidence referenceSample Laggala Pallegama field register / 2025
permitsDocumented
permits evidence referenceSample Laggala Pallegama field register / 2025
monitoring conditionsDocumented
monitoring conditions evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Documented determinations, processing time and appeal outcomes.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
11. Compare managed-recharge alternativesDEC-DP21-011 · Recharge options · Suggested priority: High
Try this decision

Compare managed-recharge alternatives.

Validation required

Budget remaining after option — fictional 2025 examples

Method. Budget minus option cost. Compare benefits, adverse effects and mandatory constraints separately; no weighted score or automatic best option.

Next step. Compare feasible trade-offs. Choose a feasible alternative with rationale and conditions, commission evidence, or defer.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Expected benefit and its evidence; Resource needs and adverse effects

Other required evidence. Site geology; source-water quality; recharge volume; costs; controls; feasibility.

Fictional worked example · 2025

Well rehabilitation · Laggala Pallegama

Input or resultValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Expected benefit and its evidenceCompare managed-recharge alternatives; Site geology and source-water quality evidence needed
Resource needs and adverse effectsSample water, labour, access and safeguard trade-offs
Budget remaining after option300,000LKR

Affordability does not prove feasibility or scientific suitability. A missing mandatory condition keeps an option unresolved.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Verified benefits, costs and adverse effects versus the agreed baseline.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
12. Check groundwater changes around extraction sitesDEC-DP21-012 · Mining impacts · Suggested priority: High
Try this decision

Investigate groundwater changes around extraction sites.

Verified published formula · Difference-in-differences arithmetic

Difference in changes — fictional 2025 examples

Method. (Treatment after−before) − (comparison after−before), using the same outcome definition and periods.

Next step. Supply study-design evidence. Continue, adapt, expand or stop a programme based on defensible outcome evidence.

Inputs, example and sources

World Bank · Impact Evaluation in Practice Second Edition
Institution publication · Chapter 7, table 7.2, printed page 140, PDF page 170

The formula is verified. Causal interpretation still requires a defensible study design, comparison and assumptions.

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Treatment Groundwater head at common datum before [m]; Treatment Groundwater head at common datum after [m]; Comparison Groundwater head at common datum before [m]; Comparison Groundwater head at common datum after [m]; Study design and comparability evidence; Outcome definition, method and reference basis

Other required evidence. Mine activity; well levels; water quality; baseline; comparison wells; geology.

Fictional worked example · 2025

Laggala Pallegama — mining impacts · Laggala Pallegama

Input or resultValueUnit
Treatment Groundwater head at common datum before42m
Treatment Groundwater head at common datum after59m
Comparison Groundwater head at common datum before39m
Comparison Groundwater head at common datum after46m
Study design and comparability evidenceMissing
Outcome definition, method and reference basisGroundwater head at common datum /example matching definition1
Difference in changes10m

The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Verified outcomes, costs, distributional effects and evidence strength.

  • World Bank Impact Evaluation in Practice Second Edition — Institution publication. Chapter7 difference-in-differences. Published difference-in-differences estimator and study assumptions; aggregate examples do not establish causation.
  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
13. Choose what to handle first: rehabilitation of poorly performing wellsDEC-DP21-013 · Well rehabilitation · Suggested priority: Medium
Try this decision

Prioritize rehabilitation of poorly performing wells.

Validation required

Open days past due — fictional 2025 examples

Method. Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.

Next step. Follow up overdue case. Authorize feasible repair through the proper work process, inspect further, or restrict unsafe use.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed

Other required evidence. Well condition; yield; sand production; failure history; repair options; costs.

Fictional worked example · 2025

Laggala Pallegama — well rehabilitation · Laggala Pallegama

Input or resultValueUnit
Received or defect observed2025-04-01
Recorded due date2025-06-01
Assessment date2025-06-30
Case/work closedNo
Documented critical unresolved conditionUnknown
Responsible office or maintainerProposed responsible office
Actual closure date when closed
Open days past due29days
Calendar age90days

Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Verified defect closure, service availability and repeat failures.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
14. Clear delayed groundwater laboratory analysesDEC-DP21-014 · Laboratory turnaround · Suggested priority: Medium
Try this decision

Clear delayed groundwater laboratory analyses.

Validation required

Open days past due — fictional 2025 examples

Method. Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.

Next step. Follow up overdue case. Assign the next permitted case, escalate an overdue case, request evidence, or close with proof.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed

Other required evidence. Sample ID; receipt; required tests; holding time; due date; lab capacity.

Fictional worked example · 2025

Laggala Pallegama — laboratory turnaround · Laggala Pallegama

Input or resultValueUnit
Received or defect observed2025-04-01
Recorded due date2025-06-01
Assessment date2025-06-30
Case/work closedNo
Documented critical unresolved conditionUnknown
Responsible office or maintainerProposed responsible office
Actual closure date when closed
Open days past due29days
Calendar age90days

Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Response time, aged cases, completion and reopened cases.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
15. Compare feasible groundwater contingency suppliesDEC-DP21-015 · Drought supply · Suggested priority: High
Try this decision

Compare feasible groundwater contingency supplies.

Validation required

Budget remaining after option — fictional 2025 examples

Method. Budget minus option cost. Compare benefits, adverse effects and mandatory constraints separately; no weighted score or automatic best option.

Next step. Compare feasible trade-offs. Choose a feasible alternative with rationale and conditions, commission evidence, or defer.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Expected benefit and its evidence; Resource needs and adverse effects

Other required evidence. Demand; verified yields; water quality; transport; costs; authorized abstraction.

Fictional worked example · 2025

Well rehabilitation · Laggala Pallegama

Input or resultValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Expected benefit and its evidenceCompare feasible groundwater contingency supplies; Demand and verified yields evidence needed
Resource needs and adverse effectsSample water, labour, access and safeguard trade-offs
Budget remaining after option300,000LKR

Affordability does not prove feasibility or scientific suitability. A missing mandatory condition keeps an option unresolved.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Verified benefits, costs and adverse effects versus the agreed baseline.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
16. Review unsuccessful drilling and cost patternsDEC-DP21-016 · Drilling performance · Suggested priority: Medium
Try this decision

Review unsuccessful drilling and cost patterns.

Validation required

Cost per drilled metre — fictional 2025 examples

Method. Drilling cost / completed depth. Display tested yield and the stated success definition separately; cost per metre does not determine safe abstraction.

Next step. Review evidence. Investigate low productivity, compare practices, or improve the input/output measurements.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Drilling cost [LKR]; Completed drilled depth [m]; Tested sustainable-yield evidence [L/s]; Outcome under the stated success definition

Other required evidence. Borehole ID; depth; yield; geology; drilling cost; success definition.

Fictional worked example · 2025

Laggala Pallegama — drilling performance · Laggala Pallegama

Input or resultValueUnit
Drilling cost1,800,000LKR
Completed drilled depth60m
Tested sustainable-yield evidence2.4L/s
Outcome under the stated success definitionUnknown
Cost per drilled metre30,000LKR/m
Reported pumping-test yield2.4L/s

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Output per relevant input alongside quality and resource impacts.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
17. Restore failed groundwater loggers and calibrationDEC-DP21-017 · Monitoring devices · Suggested priority: High
Try this decision

Restore failed groundwater loggers and calibration.

Validation required

Completeness — fictional 2025 examples

Method. Completeness = 100 × valid / expected. Age = assessment date − latest valid observation; compare with the explicitly supplied interval.

Next step. Check overdue observation. Repair missed observations, contact the owner, or suspend stale evidence from current decisions.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Expected observations in the window [observations]; Distinct valid observations [observations]; Latest valid observation; Assessment date; Required observation interval [days]

Other required evidence. Logger ID; expected cadence; last valid reading; calibration; power; access.

Fictional worked example · 2025

Laggala Pallegama — monitoring devices · Laggala Pallegama

Input or resultValueUnit
Expected observations in the window30observations
Distinct valid observations24observations
Latest valid observation2025-06-28
Assessment date2025-06-30
Required observation interval1days
Completeness80%
Age of latest observation2days
Missing observations6observations

A recent observation does not fill earlier gaps. Unknown schedule or observation time cannot establish freshness.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Valid observations received on time and recurring gaps.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
18. Prepare permitted groundwater information releasesDEC-DP21-018 · Public evidence · Suggested priority: Medium
Try this decision

Prepare permitted groundwater information releases.

Validation required

Evidence gaps — fictional 2025 examples

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Grant only scoped authorized access, aggregate/redact, refuse, or request approval.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Dataset; Dataset evidence reference; location sensitivity; location sensitivity evidence reference; ownership; ownership evidence reference; intended use; intended use evidence reference; license; license evidence reference; approval; approval evidence reference

Other required evidence. Dataset; location sensitivity; ownership; intended use; license; approval.

Fictional worked example · 2025

Laggala Pallegama — public evidence · Laggala Pallegama

Input or resultValueUnit
DatasetMissing
Dataset evidence reference
location sensitivityDocumented
location sensitivity evidence referenceSample Laggala Pallegama field register / 2025
ownershipDocumented
ownership evidence referenceSample Laggala Pallegama field register / 2025
intended useDocumented
intended use evidence referenceSample Laggala Pallegama field register / 2025
licenseDocumented
license evidence referenceSample Laggala Pallegama field register / 2025
approvalDocumented
approval evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Permitted use, expiry compliance and investigated disclosure incidents.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
19. Validate aquifer-model predictions before planning useDEC-DP21-019 · Aquifer models · Suggested priority: Medium
Try this decision

Validate aquifer-model predictions before planning use.

Validation required

Difference — fictional 2025 examples

Method. Reproduced minus expected result, within an explicitly supplied absolute tolerance, using the same exact input/method versions and a separate checker. Retain originals, code, parameters and environment evidence.

Next step. Investigate reproduction difference. Accept reproducible evidence for review, investigate differences, or withhold an unsupported result.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Earlier/source value [m]; Independently reproduced value [m]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer

Other required evidence. Model; boundary conditions; pumping; calibration levels; independent validation; uncertainty.

Fictional worked example · 2025

Laggala Pallegama — aquifer models · Laggala Pallegama

Input or resultValueUnit
Earlier/source value100m
Independently reproduced value90m
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable m measure; same input scope
Documented absolute comparison tolerance0.01m
Expected input/method versionSample input1 /method1
Reproduced input/method versionSample input1 /method1
Original result creatorPreparation officer
Independent reproducerIndependent checking officer
Difference-10m
Relative change-10%

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Independent reproduction within the approved tolerance.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision
20. Resolve inconsistent well identifiers and construction metadataDEC-DP21-020 · Well registry · Suggested priority: Lower
Try this decision

Resolve inconsistent well identifiers and construction metadata.

Validation required

Evidence gaps — fictional 2025 examples

Method. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.

Next step. Complete the evidence. Accept a fit source for a defined use, restrict it, or request metadata/schema correction.

Inputs, example and sources

Keep the same place, observation period, definitions, units and source versions.

Analysis inputs. Well ID; Well ID evidence reference; location; location evidence reference; depth; depth evidence reference; screen interval; screen interval evidence reference; datum; datum evidence reference; construction date; construction date evidence reference; source; source evidence reference

Other required evidence. Well ID; location; depth; screen interval; datum; construction date; source.

Fictional worked example · 2025

Laggala Pallegama — well registry · Laggala Pallegama

Input or resultValueUnit
Well IDMissing
Well ID evidence reference
locationDocumented
location evidence referenceSample Laggala Pallegama field register / 2025
depthDocumented
depth evidence referenceSample Laggala Pallegama field register / 2025
screen intervalDocumented
screen interval evidence referenceSample Laggala Pallegama field register / 2025
datumDocumented
datum evidence referenceSample Laggala Pallegama field register / 2025
construction dateDocumented
construction date evidence referenceSample Laggala Pallegama field register / 2025
sourceDocumented
source evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.

Proposed checking role. Hydrogeologist and water-quality specialist.

After the action. Resolved interoperability issues and current verified metadata.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context
  • Water Resources Board hydrogeology — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • Water Resources Board services — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • WHO water safety planning — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.

Confirm local scope, data rights, parameters and responsible roles in this Institution review. Published components retain their source; they do not approve the local application.

Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Ground Water Prospect · Water Systems

Existing form reference: ce5ed1b99bb3102f

FieldUnitRequired
IDConfirm if neededNo
AquifierConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Ground Water · Water Systems

Existing form reference: 8d60801843516765

FieldUnitRequired
IDConfirm if neededNo
AquifierConfirm if neededNo
Original FIDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Village Tank · Water Systems

Existing form reference: ba56f4a118b8defb

FieldUnitRequired
NumberConfirm if neededNo
IDConfirm if neededNo
DataConfirm if neededNo
SheetConfirm if neededNo
XConfirm if neededNo
YConfirm if neededNo
XCOORDConfirm if neededNo
YCOORDConfirm if neededNo
Sheet NumberConfirm if neededNo
QuantityConfirm if neededNo
DescriptionConfirm if neededNo
Village Anicut · Water Systems

Existing form reference: f173e69599dc5331

FieldUnitRequired
Serial NumberConfirm if neededNo
XCOORDConfirm if neededNo
YCOORDConfirm if neededNo
CodeConfirm if neededNo
DescriptionConfirm if neededNo
Basin · Water Systems

Existing form reference: aab19eb1fe26e99f

FieldUnitRequired
Basin NameConfirm if neededNo
NumberConfirm if neededNo
BoundaryConfirm if neededNo
River BasinConfirm if neededNo
areaConfirm if neededNo
PerimeterConfirm if neededNo
WatershedConfirm if neededNo
IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Water Shed · Water Systems

Existing form reference: f0192290b75919c0

FieldUnitRequired
Watershed_TypeConfirm if neededNo
Watershed_NameConfirm if neededNo
Catchment_NameConfirm if neededNo
Basin_NameConfirm if neededNo
Region_NameConfirm if neededNo
DescriptionConfirm if neededNo
PerimeterConfirm if neededNo
areaConfirm if neededNo
Watershed_NumberConfirm if neededNo
HectaresConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Dam · Water Systems

Existing form reference: ccd11935ddd740eb

FieldUnitRequired
Dam NameConfirm if neededNo
Dam_TypeConfirm if neededNo
Dam Storage CapacityConfirm if neededNo
Hydraulic Head Size meterConfirm if neededNo
Dam SizeConfirm if neededNo
Dam Construction TypeConfirm if neededNo
Dam Construction MaterialConfirm if neededNo
Dam Structural BehaviourConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
Hydro Point IDConfirm if neededNo
DescriptionConfirm if neededNo
st_length(shape)Confirm if neededNo
River Mouth Locations · Water Systems

Existing form reference: 8123426118305c93

FieldUnitRequired
NameConfirm if neededNo
Capture_TypeConfirm if neededNo
WB_NumberConfirm if neededNo
Point_XConfirm if neededNo
Point_YConfirm if neededNo
Zone_NameConfirm if neededNo
Stream · Water Systems

Existing form reference: 46072ad6caa5f83d

FieldUnitRequired
Stream TypeConfirm if neededNo
Stream NameConfirm if neededNo
Length In KmConfirm if neededNo
Width In MetersConfirm if neededNo
Hydro Line IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_length(shape)Confirm if neededNo
Pond · Water Systems

Existing form reference: 66361481a1066277

FieldUnitRequired
Pond_TypeConfirm if neededNo
Pond_NameConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Perimeter_kmConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Spill_Level_MLSConfirm if neededNo
Catchment_AreaConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Canal · Water Systems

Existing form reference: f38ab955cf2f6bd4

FieldUnitRequired
Canal TypeConfirm if neededNo
Canal NameConfirm if neededNo
Length In KmConfirm if neededNo
Width In MetersConfirm if neededNo
Hydro Area IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Lake · Water Systems

Existing form reference: 1bb76fa1770b0049

FieldUnitRequired
Lake_TypeConfirm if neededNo
Lake_NameConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Perimeter_kmConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Spill_Level_MLSConfirm if neededNo
Catchment_AreaConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
River · Water Systems

Existing form reference: d15540e8ecb12c69

FieldUnitRequired
River TypeConfirm if neededNo
River NameConfirm if neededNo
Length_In_KmConfirm if neededNo
Width_In_MetersConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Lagoon · Water Systems

Existing form reference: 0f0d24cef4bd6481

FieldUnitRequired
Lagoon_TypeConfirm if neededNo
Lagoon NameConfirm if neededNo
Primary InflowsConfirm if neededNo
Primary_InflowsConfirm if neededNo
Length_In_KmConfirm if neededNo
Width_In_KmConfirm if neededNo
Capacity_Acre_Per_FeetConfirm if neededNo
Area_In_sqkmConfirm if neededNo
Depth_In_MetersConfirm if neededNo
Hydro_Area_IDConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Spill Point · Water Systems

Existing form reference: dd591850f1e639e2

FieldUnitRequired
TypeConfirm if neededNo
NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
Sluice Point · Water Systems

Existing form reference: 70efb0310e727bec

FieldUnitRequired
Type Hydro pointConfirm if neededNo
NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
hydro_point_idConfirm if neededNo
Cascades · Water Systems

Existing form reference: a23c11282c20ec1d

FieldUnitRequired
RiverBasin NumberConfirm if neededNo
RiverBasin NameConfirm if neededNo
SWS NumberConfirm if neededNo
SWS NameConfirm if neededNo
Tank Cascade NumberConfirm if neededNo
Tank Cascade NameConfirm if neededNo
Number of TanksConfirm if neededNo
Number of Tanks1Confirm if neededNo
Climatic ZoneConfirm if neededNo
RemarksConfirm if neededNo
areaConfirm if neededNo
PerimeterConfirm if neededNo
HectaresConfirm if neededNo
UP CodeConfirm if neededNo
Color CodeConfirm if neededNo
IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Sea Ports · Water Systems

Existing form reference: 7caa76b009c9aa66

FieldUnitRequired
Port NameConfirm if neededNo
IDConfirm if neededNo
Port TypeConfirm if neededNo
DescriptionConfirm if neededNo
GFCODEConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
Water Area · Water Systems

Existing form reference: d89ee67747f1e131

FieldUnitRequired
Type_ClassificationConfirm if neededNo
Water Area NameConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
Hydro_Area_ID Confirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo

5. Documents and images

Your institution has its own document and image library. Use the same library for reports, photos and other evidence.

Water Resources Board Documents and images prototype screen
Water Resources Board. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Documents and images. Check the institution name.
  2. Use All files, Documents or Images to find a file. Open its preview or download the original.
  3. Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
  4. Use Access preview to try the institution reviewer and Public visitor views.

Files added in the prototype stay in this browser. Public sharing is an access preview. Existing public reference links already work online.

What your institution needs to confirm

6. Data structure management

Data structure keeps the existing source tree, records, charts and map. Manage structure adds a place to propose changes to definitions.

Water Resources Board Data structure management prototype screen
Water Resources Board. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Data structure and choose Manage structure.
  2. Use Add base domain for a main information area. Add inside creates a subject area, a nested subject, an entity type or a field under the right parent.
  3. Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
  4. For a field, check the data type, unit, required value, limits and missing-value rule. Save a Draft, then try the separate reviewer view.

An entity type means a kind of thing or event, such as a reservoir or an inspection. Drafts stay in this browser. A demo approval does not change real definitions, data, chart links or sharing rights.

What your institution needs to confirm

7. Users and access

User management shows example profiles for each institution. People and Roles and access let you review the proposed account screens.

Water Resources Board Users and access prototype screen
Water Resources Board. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open User management and choose the institution. The rows are examples, not a list of your staff.
  2. Use View access to check a role. An administrator title alone does not give access to Private files.
  3. Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
  4. Review the example permissions and tell us which job roles should receive each one.

These are interface previews only. They create no account, send no email and change no access. Use example details in the preview. Institution verification does not grant a real permission.

What your institution needs to confirm

8. Can you share data regularly?

We currently use public data and published reports where available. Please confirm whether your institution can provide data directly, so we can avoid retyping or reading figures from PDFs.

Do not enter passwords, access keys or private account details.

9. Anything else we should change?

Use the Download answers button at the top of this page. Share the downloaded file or printed copy through your agreed review channel. Nothing is sent automatically.