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 Change example to try different values. Use Data needed to check the fields and sources. 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. Investigate wells showing sustained drawdownDEC-DP21-001 · Groundwater depletion
Try this decision

Review comparable groundwater-head observations before planning a well investigation.

Validation required

Fictional default example · 2025.

Fictional case / areaObserved value [m]Next check
Laggala Pallegama — groundwater depletion / 2025100.9Check source and period comparability before using the trend
Rattota — groundwater depletion / 202588.8Check source and period comparability before using the trend
Panvila — groundwater depletion / 2025148.7Check source and period comparability before using the trend

What the selected record shows. Observed value: 100.9 m.

Next step. Check source and period comparability before using the trend. Prepare trend report in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Head, datum and pumping state must match; a short series does not establish sustainable abstraction.

Inputs, method and sources
Supplied inputValueUnit
Groundwater head relative to the stated datum100.9m
Datum, pumping state and measurement conventionSample common head datum; static measurement

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

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. Heads refer to an arbitrary stated datum. Compare pumping state, season and measurement method; do not calculate relative percentage or infer sustainable abstraction.

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

Calculation appendix

  • 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.
Your checks for this decision
2. Adjust monitoring to seasonal groundwater variationDEC-DP21-002 · Seasonal groundwater
Try this decision

Compare groundwater head with the supplied matching seasonal reference.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m]Next check
Laggala Pallegama — seasonal groundwater / 2025-1.5Check the unusual observation and its comparison basis
Rattota — seasonal groundwater / 20250.2Check the unusual observation and its comparison basis
Panvila — seasonal groundwater / 2025-1.4Check the unusual observation and its comparison basis

What the selected record shows. Difference: -1.5 m.

Next step. Check the unusual observation and its comparison basis. Prepare investigation brief in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A departure does not by itself identify recharge change or pumping effects.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Comparable seasonal groundwater head on the stated datum102.4m
Observed groundwater head on the same datum100.9m
Datum, pumping state and seasonal referenceFictional common datum / static non-pumping observation / matching seasonal window

Head difference = observed head − comparable seasonal reference head, in metres on the same datum. The datum has an arbitrary zero; a relative percentage is not reported.

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

Calculation appendix

  • 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.
Your checks for this decision
3. Investigate wells exceeding applicable use-specific limitsDEC-DP21-003 · Groundwater quality
Try this decision

Check the reported well-water sample against its use-specific comparison bounds.

Validation required

Fictional default example · 2025.

Fictional case / areaObserved resultSupplied comparison boundsNext check
Laggala Pallegama — groundwater quality / Laggala Pallegama230 mg/L0 to 200 mg/LObtain the missing evidence listed below
Rattota — groundwater quality / Rattota216 mg/L0 to 200 mg/LReview the sample, analytical method and comparison basis
Panvila — groundwater quality / Panvila85 mg/L0 to 200 mg/LReview the sample, analytical method and comparison basis

What the selected record shows. The supplied Well-water chloride for selected use result is 230 mg/L. Its stated comparison range is 0 to 200 mg/L. Outside example comparison bounds.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Exact sample and site reference
  • Sample observation date

The fictional bounds do not establish water safety or legal compliance.

Inputs, method and sources
Supplied inputValueUnit
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
Sample and site referenceNot provided
Sample observation dateNot provided

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

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. Physical concentrations and magnitude measurements are non-negative. Signed raw instrument signals need laboratory interpretation; do not silently replace them with zero.

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

Calculation appendix

  • 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.
Your checks for this decision
4. Select groundwater areas needing observation wellsDEC-DP21-004 · Monitoring coverage
Try this decision

Find aquifer units without confirmed observation-well coverage.

Validation required

Fictional default example · 2025.

Fictional case / areaVerified coverage [%]Known uncovered [aquifer units]Unknown coverage [aquifer units]Next check
Laggala Pallegama — monitoring coverage / 202565305Check the records behind the uncovered and unknown groups
Rattota — monitoring coverage / 202585150Check the records behind the uncovered and unknown groups
Panvila — monitoring coverage / 2025454015Check the records behind the uncovered and unknown groups

What the selected record shows. 30 aquifer units are known to be uncovered; 5 have unknown coverage. 65% are confirmed covered.

Next step. Check the records behind the uncovered and unknown groups. Prepare coverage follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Coverage does not establish well placement, condition or representativeness.

Example chart
Verified coverage — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Required eligible frame100aquifer units
Distinct members of that frame covered65aquifer units
Frame members with unknown coverage5aquifer units

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
5. Shortlist sites requiring detailed groundwater investigationDEC-DP21-005 · Borehole siting
Try this decision

Find missing geological, geophysical and access evidence for a groundwater investigation.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — borehole siting / Laggala PallegamaGeology: MissingObtain the missing evidence listed below
Rattota — borehole siting / Rattotageophysics: MissingObtain the missing evidence listed below
Panvila — borehole siting / Panvilanearby wells: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this borehole siting case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Geology: Missing

Checklist completeness does not establish drilling suitability or yield.

Inputs, method and sources
Supplied inputValueUnit
GeologyMissing
Geology evidence referenceNot provided
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

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
6. Refer pumping-test results for safe-abstraction assessmentDEC-DP21-006 · Pumping tests
Try this decision

Check whether supplied pumping-test values can be independently reproduced.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³/day]Relative change [%]Next check
Laggala Pallegama — pumping tests / 2025-10-10Investigate reproduction difference
Rattota — pumping tests / 202555Investigate reproduction difference
Panvila — pumping tests / 2025-2-2Investigate reproduction difference

What the selected record shows. Difference: -10 m³/day. Investigate reproduction difference.

Next step. Investigate reproduction difference. Prepare reproduction-check note in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A matching calculation does not establish a safe abstraction rate.

Inputs, method and sources
Supplied inputValueUnit
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

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.

Reproducing a supplied pumping-test result does not establish sustainable yield or authorize abstraction. Drawdown, recovery, duration, interference and water-quality evidence remain necessary.

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

Calculation appendix

  • 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.
Your checks for this decision
7. Compare recorded abstraction with reviewed aquifer budgetsDEC-DP21-007 · Abstraction balance
Try this decision

Reconcile the supplied aquifer inflows, outflows and closing-storage observation.

Validation required

Fictional default example · 2025.

Fictional case / areaCalculated closing storage [m³]Observed minus calculated closing [m³]Next check
Laggala Pallegama — abstraction balance / 2025164,000-500Reconcile closing balance
Rattota — abstraction balance / 2025164,000-500Reconcile closing balance
Panvila — abstraction balance / 2025164,000-500Reconcile closing balance

What the selected record shows. Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference.

Next step. Reconcile closing balance. Prepare balance review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A balance does not establish sustainable yield without a reviewed aquifer model.

Inputs, method and sources
Supplied inputValueUnit
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 = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing.

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.

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

Calculation appendix

  • 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.
Your checks for this decision
8. Investigate contamination sources near supply wellsDEC-DP21-008 · Well protection
Try this decision

Review documented source-to-well separation with flow-direction and protection evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaDocumented separation [m]Next check
Laggala Pallegama — well protection / 2025150Check the matching footprint, source boundary and applicable conditions
Rattota — well protection / 2025150Check the matching footprint, source boundary and applicable conditions
Panvila — well protection / 2025150Check the matching footprint, source boundary and applicable conditions

What the selected record shows. Documented separation: 150 m.

Next step. Check the matching footprint, source boundary and applicable conditions. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Distance alone does not establish contamination or a safe protection zone.

Inputs, method and sources
Supplied inputValueUnit
Documented source-to-well separation150m
Potential contamination source and observation referenceSample documented source
Hydrogeological flow-direction evidenceNot provided
Use-specific reviewed protection criterionNot provided

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

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.

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

Calculation appendix

  • 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.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
9. Prioritize coastal groundwater salinity investigationsDEC-DP21-009 · Saline intrusion
Try this decision

Review comparable conductivity observations for a salinity investigation.

Validation required

Fictional default example · 2025.

Fictional case / areaObserved value [µS/cm]Next check
Kalpitiya — saline intrusion scenario / 20251,800Check source and period comparability before using the trend
Puttalam — saline intrusion scenario / 20252,300Check source and period comparability before using the trend
Trincomalee — saline intrusion scenario / 20251,600Check source and period comparability before using the trend

What the selected record shows. Observed value: 1,800 µS/cm.

Next step. Check source and period comparability before using the trend. Prepare trend report in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Conductivity alone does not identify seawater intrusion or its cause.

Inputs, method and sources
Supplied inputValueUnit
Comparable observation1,800µS/cm

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

Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend. These are fictional coastal examples outside Knuckles. Conductivity is not a chloride concentration or proof of saline intrusion; sampling and hydrogeological evidence are needed.

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

Calculation appendix

  • 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.
Your checks for this decision
10. Refer industrial groundwater requests for determinationDEC-DP21-010 · Industrial abstraction
Try this decision

Find missing demand, hydrogeological and permit evidence for an industrial request.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — industrial abstraction / Laggala PallegamaDemand: MissingObtain the missing evidence listed below
Rattota — industrial abstraction / Rattotahydrogeological report: MissingObtain the missing evidence listed below
Panvila — industrial abstraction / Panvilaabstraction proposal: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this industrial abstraction case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Demand: Missing

The prototype does not authorise groundwater abstraction.

Inputs, method and sources
Supplied inputValueUnit
DemandMissing
Demand evidence referenceNot provided
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

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

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

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

Calculation appendix

  • 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.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
11. Compare managed-recharge alternativesDEC-DP21-011 · Recharge options
Try this decision

Compare managed-recharge choices using geology, water quality and site constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Infiltration basin under investigation / Laggala PallegamaInvestigate an infiltration basin.Needs geology, source-water quality, rights, clogging and groundwater-response evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Recharge well under investigation / Laggala PallegamaInvestigate a recharge well.Needs aquifer compatibility, water quality, design and monitoring evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Catchment infiltration treatment / Laggala PallegamaImprove catchment infiltration conditions.Needs site hydrology, rights, vegetation and downstream-effect evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

What the selected record shows. There is not enough information to choose this option. Obtain the records and evidence about conditions listed below. The supplied budget less cost is 300,000 LKR.

Next step. Obtain the missing records before choosing. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Records needed: Site geology; source-water quality; recharge volume; costs; controls; feasibility
  • Applicable conditions, what was checked and the supporting reference

Budget and descriptive benefits do not establish recharge feasibility or safety.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionInvestigate an infiltration basin.
Resource needs and adverse effectsNeeds geology, source-water quality, rights, clogging and groundwater-response evidence.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

Compare each alternative's stated benefit, adverse effects, domain evidence and mandatory constraints. Where cost and budget are supplied, budget balance = budget − option cost. A budget balance alone does not determine domain feasibility or select an option.

Budget and descriptive benefits do not establish recharge feasibility or safety.

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

Calculation appendix

  • 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.
Your checks for this decision
12. Investigate groundwater changes around extraction sitesDEC-DP21-012 · Mining impacts
Try this decision

Compare groundwater-head changes around extraction and comparison observations.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [m]Next check
Laggala Pallegama — mining impacts / 202510Obtain the missing evidence listed below
Rattota — mining impacts / 202510Obtain the missing evidence listed below
Panvila — mining impacts / 202510Obtain the missing evidence listed below

What the selected record shows. Treatment change: 17; comparison change: 7; difference in changes: 10 m. This comparison alone does not establish causation or benefit.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Study design and evidence that the treatment and comparison records are comparable

A difference in changes does not establish an extraction effect.

Inputs, method and sources
Supplied inputValueUnit
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

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

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

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

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.

Calculation appendix

  • 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.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
13. Prioritize rehabilitation of poorly performing wellsDEC-DP21-013 · Well rehabilitation
Try this decision

Identify well-rehabilitation cases past their recorded response date.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — well rehabilitation / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — well rehabilitation / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — well rehabilitation / 20252990Follow up overdue case; confirm the missing condition evidence

What the selected record shows. Open days past due: 29 days. Follow up overdue case.

Next step. Follow up overdue case; confirm the missing condition evidence. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Documented critical unresolved condition: Unknown

Age alone does not establish the best repair or its urgency.

Inputs, method and sources
Supplied inputValueUnit
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 closedNot provided

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
14. Clear delayed groundwater laboratory analysesDEC-DP21-014 · Laboratory turnaround
Try this decision

Identify groundwater laboratory cases past their recorded response date.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — laboratory turnaround / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — laboratory turnaround / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — laboratory turnaround / 20252990Follow up overdue case; confirm the missing condition evidence

What the selected record shows. Open days past due: 29 days. Follow up overdue case.

Next step. Follow up overdue case; confirm the missing condition evidence. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Documented critical unresolved condition: Unknown

A deadline does not establish sample validity or the cause of delay.

Inputs, method and sources
Supplied inputValueUnit
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 closedNot provided

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
15. Compare feasible groundwater contingency suppliesDEC-DP21-015 · Drought supply
Try this decision

Compare tested contingency supplies using yield, quality, rights and delivery constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Rehabilitate a tested supply well / Laggala PallegamaRehabilitate the tested supply well.Needs yield, quality, engineering, rights and operating-cost evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Use a permitted alternative borehole / Laggala PallegamaUse a permitted alternative borehole.Needs verified yield, quality, abstraction conditions and supply connections.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Provide a temporary transported supply / Laggala PallegamaArrange a temporary transported supply.Needs safe-source, transport, quantity, access and continuity evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

What the selected record shows. There is not enough information to choose this option. Obtain the records and evidence about conditions listed below. The supplied budget less cost is 300,000 LKR.

Next step. Obtain the missing records before choosing. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Records needed: Demand; verified yields; water quality; transport; costs; authorized abstraction
  • Applicable conditions, what was checked and the supporting reference

Cost alone does not establish a dependable or safe supply.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionRehabilitate the tested supply well.
Resource needs and adverse effectsNeeds yield, quality, engineering, rights and operating-cost evidence.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

Compare each alternative's stated benefit, adverse effects, domain evidence and mandatory constraints. Where cost and budget are supplied, budget balance = budget − option cost. A budget balance alone does not determine domain feasibility or select an option.

Cost alone does not establish a dependable or safe supply.

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

Calculation appendix

  • 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.
Your checks for this decision
16. Review unsuccessful drilling and cost patternsDEC-DP21-016 · Drilling performance
Try this decision

Compare drilling cost per completed metre with documented yield and outcome evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaCost per drilled metre [LKR/m]Reported pumping-test yield [L/s]Next check
Laggala Pallegama — drilling performance / 202530,0002.4Check matching outputs, denominators and operating conditions
Rattota — drilling performance / 202530,0002.4Check matching outputs, denominators and operating conditions
Panvila — drilling performance / 202530,0002.4Check matching outputs, denominators and operating conditions

What the selected record shows. Cost per drilled metre: 30,000 LKR/m.

Next step. Check matching outputs, denominators and operating conditions. Prepare performance comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A low drilling cost does not establish a successful or sustainable well.

Inputs, method and sources
Supplied inputValueUnit
Drilling cost1,800,000LKR
Completed drilled depth60m
Tested sustainable-yield evidence2.4L/s
Outcome under the stated success definitionUnknown

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

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

Calculation appendix

  • 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.
Your checks for this decision
17. Restore failed groundwater loggers and calibrationDEC-DP21-017 · Monitoring devices
Try this decision

Find missing or overdue logger observations before a data-recovery referral.

Validation required

Fictional default example · 2025.

Fictional case / areaCompleteness [%]Age of latest observation [days]Missing observations [observations]Next check
Laggala Pallegama — monitoring devices / 20258026Check overdue observation
Rattota — monitoring devices / 20258026Check overdue observation
Panvila — monitoring devices / 20258026Check overdue observation

What the selected record shows. Completeness: 80 %. Check overdue observation.

Next step. Check overdue observation. Prepare observation request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Reporting completeness does not establish calibration or measurement quality.

Inputs, method and sources
Supplied inputValueUnit
Expected observations in the window30observations
Distinct valid observations24observations
Latest valid observation2025-06-28
Assessment date2025-06-30
Required observation interval1days

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
18. Prepare permitted groundwater information releasesDEC-DP21-018 · Public evidence
Try this decision

Check sensitivity, ownership and use conditions for a groundwater-information request.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — public evidence / Laggala PallegamaDataset: MissingObtain the missing evidence listed below
Rattota — public evidence / Rattotalocation sensitivity: MissingObtain the missing evidence listed below
Panvila — public evidence / Panvilaownership: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this public evidence case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Dataset: Missing

A complete checklist does not permit release of restricted well locations.

Inputs, method and sources
Supplied inputValueUnit
DatasetMissing
Dataset evidence referenceNot provided
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

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

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

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

Calculation appendix

  • 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.
Your checks for this decision
19. Validate aquifer-model predictions before planning useDEC-DP21-019 · Aquifer models
Try this decision

Compare supplied aquifer-model predictions and independently reproduced heads.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m]Next check
Laggala Pallegama — aquifer models / 2025-0.2Investigate reproduction difference
Rattota — aquifer models / 20250.05Difference within supplied tolerance
Panvila — aquifer models / 2025-0.2Investigate reproduction difference

What the selected record shows. Difference: -0.2 m. Investigate reproduction difference.

Next step. Investigate reproduction difference. Prepare reproduction-check note in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Reproduction does not validate predictive performance or model fitness.

Inputs, method and sources
Supplied inputValueUnit
Expected head on the stated model datum101m
Supplied independently reproduced head on that datum100.8m
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable m measure; same input scope
Documented absolute comparison tolerance0.1m
Expected input/method versionSample input1 /method1
Reproduced input/method versionSample input1 /method1
Original result creatorPreparation officer
Independent reproducerIndependent checking officer

Reproduced groundwater head minus expected groundwater head, in metres on the same datum. Compare the stated absolute tolerance and exact versions. No relative percentage or coordinate/model execution is reported.

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

Calculation appendix

  • 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.
Your checks for this decision
20. Resolve inconsistent well identifiers and construction metadataDEC-DP21-020 · Well registry
Try this decision

Find missing well identifiers, datum and construction references.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — well registry / Laggala PallegamaWell ID: MissingObtain the missing evidence listed below
Rattota — well registry / Rattotalocation: MissingObtain the missing evidence listed below
Panvila — well registry / Panviladepth: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this well registry case. The items below identify what must be obtained or reconciled.

Next step. Obtain the missing evidence listed below. Prepare evidence request in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Information still needed
  • Well ID: Missing

Complete metadata do not establish a reliable groundwater measurement.

Inputs, method and sources
Supplied inputValueUnit
Well IDMissing
Well ID evidence referenceNot provided
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

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

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

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

Calculation appendix

  • 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.
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.