Sub-Watershed Integrated Delivery Teams

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. Follow up assignments lacking accepted field evidenceDEC-DP13-001 · Field assignments
Try this decision

Identify field assignments whose evidence or response is overdue.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — field assignments / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — field assignments / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — field assignments / 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 task record does not establish accepted completion.

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: Assignment ID; expected observation; submitted record; review status; due date.

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. Schedule visits to unobserved monitoring sitesDEC-DP13-002 · Monitoring coverage
Try this decision

Identify required monitoring visits not confirmed complete or still unknown.

Validation required

Fictional default example · 2025.

Fictional case / areaVerified coverage [%]Known uncovered [visits]Unknown coverage [visits]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 visits 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.

Visit coverage does not establish the quality of an observation.

Example chart
Verified coverage — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Required eligible frame100visits
Distinct members of that frame covered65visits
Frame members with unknown coverage5visits

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: Site frame; required visits; completed accepted visits; access; staff; season.

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. Review overdue community cases and urgency evidenceDEC-DP13-003 · Community cases
Try this decision

Review overdue community cases alongside their documented urgency evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — community cases / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — community cases / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — community cases / 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

Days overdue alone do not establish an urgency ranking.

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: Case ID; received date; urgency evidence; due date; response; accountable institution.

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. Check conflicting field-location recordsDEC-DP13-004 · Spatial verification
Try this decision

Compare supplied location separation, positional accuracies and reference evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaLocation separation [m]Next check
Laggala Pallegama — spatial verification / 202532Reconcile the original records using their source references
Rattota — spatial verification / 202532Reconcile the original records using their source references
Panvila — spatial verification / 202532Reconcile the original records using their source references

What the selected record shows. Location separation: 32 m.

Next step. Reconcile the original records using their source references. Prepare source comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The page does not calculate geometry or confirm a site from its name.

Inputs, method and sources
Supplied inputValueUnit
Measured separation between reported locations32m
Reported source positional accuracy10m
Reported comparison positional accuracy15m
Coordinate reference and transformation evidenceSample matching CRS; transformation check required

Display supplied location separation with the two reported accuracies and coordinate-reference evidence. Do not treat a matched name or boundary overlap as confirmed identity.

Other required records: Activity ID; submitted coordinates; site boundary; GPS accuracy; field confirmation.

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. Compare community priorities for sub-watershed actionsDEC-DP13-005 · Watershed plans
Try this decision

Compare sub-watershed actions using community priorities, resources and safeguards.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Protect stream-bank vegetation / Laggala PallegamaProtect the stated stream-bank vegetation.Needs the applicable boundary, rights, community agreement and maintenance.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Improve soil cover on cultivated slopes / Laggala PallegamaImprove cover on the specified cultivated slopes.Needs crop compatibility, materials, farmer agreement and erosion evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Repair community water structures / Laggala PallegamaRepair the stated community water structures.Needs engineering, rights, water-availability, access and maintenance 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: Sites; needs; costs; water links; safeguards; community preferences; constraints
  • Applicable conditions, what was checked and the supporting reference

A cost comparison does not establish community consent or a preferred action.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionProtect the stated stream-bank vegetation.
Resource needs and adverse effectsNeeds the applicable boundary, rights, community agreement and maintenance.
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.

A cost comparison does not establish community consent or a preferred action.

Other required records: Sites; needs; costs; water links; safeguards; community preferences; constraints.

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. Coordinate field works around seasonal and resource limitsDEC-DP13-006 · Intervention scheduling
Try this decision

Check field-work timing, resource bookings and prerequisites.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — intervention scheduling / 202538Resolve overlapping resource bookings
Rattota — intervention scheduling / 202538Resolve overlapping resource bookings
Panvila — intervention scheduling / 202538Resolve overlapping resource bookings

What the selected record shows. Planned duration: 3 days. Resolve overlapping resource bookings.

Next step. Resolve overlapping resource bookings. Prepare schedule review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The example schedule does not send assignments or authorise works.

Inputs, method and sources
Supplied inputValueUnit
Required resourceWatershed field team
Task start2025-06-01
Task end2025-06-04
Earliest permitted start2025-05-28
Latest permitted finish2025-06-08
Required resource effort16hours
Available resource effort24hours
Predecessor task referenceNone
Mandatory permits and prerequisitesMet

Check start/end order, operating window, effort, predecessor completion and overlapping bookings for the same resource. A conflict is flagged; no optimal schedule is invented.

Other required records: Works; dependencies; rainfall windows; farming calendar; labour; approvals.

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. Target visits to restoration cohorts with uncertain survivalDEC-DP13-007 · Restoration follow-up
Try this decision

Identify original restoration cohorts with failed or unknown follow-up.

Validation required

Fictional default example · 2025.

Fictional case / areaConfirmed survival lower bound [%]Survival upper bound [%]Unknown follow-up [plants]Next check
Laggala Pallegama — restoration follow-up / 20257884.44429Check unknown follow-up separately from confirmed survival and failure
Rattota — restoration follow-up / 20257884.44429Check unknown follow-up separately from confirmed survival and failure
Panvila — restoration follow-up / 20257884.44429Check unknown follow-up separately from confirmed survival and failure

What the selected record shows. Confirmed survival lower bound: 78 %.

Next step. Check unknown follow-up separately from confirmed survival and failure. Prepare cohort follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Unknown follow-up is not mortality; replacements remain separate.

Inputs, method and sources
Supplied inputValueUnit
Original cohort450plants
Known surviving original members351plants
Known failed original members70plants
Original members with unknown follow-up29plants
Replacements in a separate cohort18plants

Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it.

These bounds account for unknown status; they are not statistical confidence intervals. Use actual follow-up dates and distinguish cohort membership from repeated visits.

Other required records: Planting cohort; counts; survival; replacements; last visit; follow-up date.

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. Verify completed soil and water conservation treatmentsDEC-DP13-008 · Conservation works
Try this decision

Check treatment measurements and inspection evidence before verification.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — conservation works / Laggala PallegamaWork ID: MissingObtain the missing evidence listed below
Rattota — conservation works / Rattotadesign: MissingObtain the missing evidence listed below
Panvila — conservation works / Panvilameasured dimensions: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this conservation works 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
  • Work ID: Missing

Recorded activity is not verified soil or water improvement.

Inputs, method and sources
Supplied inputValueUnit
Work IDMissing
Work ID evidence referenceNot provided
designDocumented
design evidence referenceSample Laggala Pallegama field register / 2025
measured dimensionsDocumented
measured dimensions evidence referenceSample Laggala Pallegama field register / 2025
locationDocumented
location evidence referenceSample Laggala Pallegama field register / 2025
inspectionDocumented
inspection evidence referenceSample Laggala Pallegama field register / 2025
acceptance conditionsDocumented
acceptance 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: Work ID; design; measured dimensions; location; inspection; acceptance 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.
Your checks for this decision
9. Review local water-shortage recordsDEC-DP13-009 · Water problems
Try this decision

Compare local water requirement and supply records before a referral.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³/day]Relative change [%]Next check
Laggala Pallegama — water problems / 2025-10-10Check the matching records and reasons for the difference
Rattota — water problems / 202555Check the matching records and reasons for the difference
Panvila — water problems / 2025-2-2Check the matching records and reasons for the difference

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

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A shortfall does not identify its cause or establish an authorised response.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Planned value100m³/day
Observed value90m³/day

Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

Other required records: Location; demand; supply observation; affected households; dates; source verification.

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. Follow up adoption after field demonstrationsDEC-DP13-010 · Farmer practice uptake
Try this decision

Check stages between field demonstration and verified adoption.

Validation required

Fictional default example · 2025.

Fictional case / areaVerified completion share [%]Not verified complete [cases]Original cases awaiting review [cases]Reviewed cases not confirmed complete [cases]Next check
Laggala Pallegama — farmer practice uptake / 202553.333844836Check the original cases that have not reached a verified outcome
Rattota — farmer practice uptake / 202553.333844836Check the original cases that have not reached a verified outcome
Panvila — farmer practice uptake / 202553.333844836Check the original cases that have not reached a verified outcome

What the selected record shows. Verified completion share: 53.333 %.

Next step. Check the original cases that have not reached a verified outcome. Prepare progress follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Participation is not evidence of adoption or benefit.

Inputs, method and sources
Supplied inputValueUnit
Distinct original sub-watershed site in the stated cohort180cases
Those original cohort members with documented review132cases
Those reviewed members meeting the stated completion definition96cases
Original cohort members whose follow-up is unknown12cases

100 × verified completed members / original unique cohort. Keep unknown follow-up separate; stages are nested, not independent populations.

Attendance, receipt, adoption, delivered service and outcomes are distinct stages. Repeated visits must not become new people. The original cohort and nested review/completion stages must match; an uncompleted record is not automatically overdue. Unknown follow-up is a subset, not an extra stage.

Other required records: Participant cohort; attendance; practice; adoption evidence; follow-up date.

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
11. Check hazard evidence before an institutional referralDEC-DP13-011 · Local hazards
Try this decision

Check hazard observations and the referral evidence for a competent authority.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — local hazards / Laggala PallegamaObservation: MissingObtain the missing evidence listed below
Rattota — local hazards / Rattotalocation: MissingObtain the missing evidence listed below
Panvila — local hazards / Panvilatime: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this local hazards 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
  • Observation: Missing

The prototype does not issue a warning or determine hazard severity.

Inputs, method and sources
Supplied inputValueUnit
ObservationMissing
Observation evidence referenceNot provided
locationDocumented
location evidence referenceSample Laggala Pallegama field register / 2025
timeDocumented
time evidence referenceSample Laggala Pallegama field register / 2025
photographsDocumented
photographs evidence referenceSample Laggala Pallegama field register / 2025
exposed assetsDocumented
exposed assets evidence referenceSample Laggala Pallegama field register / 2025
escalation protocolDocumented
escalation protocol evidence referenceSample Laggala Pallegama field register / 2025
Documented unresolved critical conditionUnknown
Evidence observation date2025-06-30
Existing control and its evidenceSample documented control
Competent recipientResponsible specialist / duty authority

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

Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.

Other required records: Observation; location; time; photographs; exposed assets; escalation protocol.

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. Redistribute assignments where field workload exceeds capacityDEC-DP13-012 · Team workload
Try this decision

Compare field demand with usable staff hours.

Validation required

Fictional default example · 2025.

Fictional case / areaUsable capacity minus demand [staff hours]Usable capacity [staff hours]Next check
Laggala Pallegama — team workload / 2025-15135Review capacity shortfall
Rattota — team workload / 2025-15135Review capacity shortfall
Panvila — team workload / 2025-15135Review capacity shortfall

What the selected record shows. Usable capacity minus demand: -15 staff hours. Review capacity shortfall.

Next step. Review capacity shortfall. Prepare capacity review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A capacity gap does not appoint staff or establish travel feasibility.

Inputs, method and sources
Supplied inputValueUnit
Demand in the selected period150staff hours
Rated capacity for that period180staff hours
Unavailable or restricted capacity45staff hours

Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand.

Match peak/average basis, time window, skill, staffing, accessibility and other binding constraints. One aggregate capacity does not override a safety constraint.

Other required records: Task hours; travel time; staff skills; available hours; due 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
13. Check safeguards before starting field interventionsDEC-DP13-013 · Safeguard conditions
Try this decision

Identify missing safeguard evidence before field-work review.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — safeguard conditions / Laggala PallegamaSite approval: MissingObtain the missing evidence listed below
Rattota — safeguard conditions / Rattotaconsent: MissingObtain the missing evidence listed below
Panvila — safeguard conditions / Panvilasafeguards: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this safeguard conditions 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
  • Site approval: Missing

A checklist does not grant clearance or authorise starting work.

Inputs, method and sources
Supplied inputValueUnit
Site approvalMissing
Site approval evidence referenceNot provided
consentDocumented
consent evidence referenceSample Laggala Pallegama field register / 2025
safeguardsDocumented
safeguards evidence referenceSample Laggala Pallegama field register / 2025
unresolved conditionsDocumented
unresolved conditions evidence referenceSample Laggala Pallegama field register / 2025
evidenceDocumented
evidence evidence referenceSample Laggala Pallegama field register / 2025
responsible reviewerDocumented
responsible reviewer 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: Site approval; consent; safeguards; unresolved conditions; evidence; responsible reviewer.

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. Plan shared field equipment and supply availabilityDEC-DP13-014 · Equipment logistics
Try this decision

Compare usable field kits and commitments with the stated requirement.

Validation required

Fictional default example · 2025.

Fictional case / areaUncommitted usable stock [field-instrument kits]Additional demand gap [field-instrument kits]Next check
Laggala Pallegama — equipment logistics / 202532Review replenishment gap
Rattota — equipment logistics / 202532Review replenishment gap
Panvila — equipment logistics / 202532Review replenishment gap

What the selected record shows. Uncommitted usable stock: 3 field-instrument kits. Review replenishment gap.

Next step. Review replenishment gap. Prepare stock review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Availability must match the instrument, condition and visit window.

Inputs, method and sources
Supplied inputValueUnit
Field-instrument kits physically held12field-instrument kits
Kits held for examination1field-instrument kits
Unserviceable or retired kits; separate from held kits0field-instrument kits
Usable kits already booked8field-instrument kits
Additional kits required5field-instrument kits
Supplier lead time14days
Remaining serviceability window365days

Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available).

Stock must be compatible by item, lot, condition, expiry and delivery window. Do not allocate quarantined/expired stock or silently erase overcommitment.

Other required records: Equipment ID; reservations; condition; usable stock; field schedule; lead time.

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. Resolve objections to sub-watershed implementation plansDEC-DP13-015 · Community consultation
Try this decision

Identify unresolved objections to a sub-watershed plan.

Validation required

Fictional default example · 2025.

Fictional case / areaUnresolved issues [issues]Response share [%]Next check
Laggala Pallegama — community consultation / 20251671.579Obtain the missing evidence listed below
Rattota — community consultation / 20251671.579Obtain the missing evidence listed below
Panvila — community consultation / 20251671.579Obtain the missing evidence listed below

What the selected record shows. 16 unresolved issue(s). 71.579% responded; response is not consent. Review the issue references and participation barriers.

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
  • Issue-register references for the 16 unresolved issues
  • Evidence about participation barriers

Participation or response is not agreement with the plan.

Inputs, method and sources
Supplied inputValueUnit
Distinct relevant people invited95people
People who responded68people
Unresolved issues16issues
Proposal/version being discussedSample proposal1
Required participation channels accessibleUnknown
Reference for unresolved issues and their progressNot provided
Evidence about participation barriersNot provided

100 × distinct respondents / invited people. Record unresolved issues individually; one respondent may raise several issues.

Response, attendance and silence are not consent. Participation does not transfer decision authority or settle rights.

Other required records: Plan version; affected groups; responses; objections; commitments; resolution.

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. Investigate deviations from agreed field work plansDEC-DP13-016 · Progress exceptions
Try this decision

Compare planned and recorded work packages within the same scope.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [work packages]Relative change [%]Next check
Laggala Pallegama — progress exceptions / 2025-4-20Check the matching records and reasons for the difference
Rattota — progress exceptions / 202500Check the matching records and reasons for the difference
Panvila — progress exceptions / 2025-2-10Check the matching records and reasons for the difference

What the selected record shows. Difference: -4 work packages.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A difference does not establish cause or accepted completion.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Agreed conservation work packages20work packages
Matching packages with accepted completion evidence16work packages

Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.

A work package must have the same agreed scope; counts do not combine unequal work quantities.

Other required records: Task target; actual quantity; period; unit; delay reason; evidence.

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. Compare supplied journeys for field visitsDEC-DP13-017 · Access routes
Try this decision

Compare documented journeys for monitoring visits.

Validation required

Fictional default example · 2025.

Fictional case / areaSupplied journey duration [minutes]Capacity minus demand [units]Next check
Laggala Pallegama — access routes / 2025653Obtain the missing evidence listed below
Rattota — access routes / 2025653Obtain the missing evidence listed below
Panvila — access routes / 2025653Obtain the missing evidence listed below

What the selected record shows. The supplied journey is 24 km and 65 minutes. Usable capacity is 18 against 15 required in the stated service units. Access and operating conditions: Unresolved.

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
  • Access, closures and operating conditions: Unresolved

No route is calculated and no safe-access determination is made.

Inputs, method and sources
Supplied inputValueUnit
Supplied journey distance from a documented route survey24km
Supplied journey duration; not calculated here65minutes
Usable vehicle/team capacity18units
Required capacity15units
Access, closures and operating conditionsUnresolved
Operating and service windowSample operating window

Compare supplied route times/distances, usable capacity and documented access/window constraints. Display feasible candidates; no route optimization is implied.

Straight-line distance is not a road route. Example routes establish no current road status, emergency clearance or safe evacuation instruction. This decision view compares supplied journeys. It does not calculate a route or run a coordinate-based analysis.

Other required records: Site coordinates; roads; closures; travel time; visit duration; team 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
18. Review overlapping field support to the same participantsDEC-DP13-018 · Support duplication
Try this decision

Review field-support records whose participant, purpose and dates overlap.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlapping days [days]Next check
Laggala Pallegama — support duplication / 202561Review possible overlap
Rattota — support duplication / 202561Review possible overlap
Panvila — support duplication / 202561Review possible overlap

What the selected record shows. Overlapping days: 61 days. Review possible overlap.

Next step. Review possible overlap. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

An overlap does not establish duplicate entitlement.

Inputs, method and sources
Supplied inputValueUnit
Permitted recipient/service referenceLaggala Pallegama — support duplication
Support purposeSample seasonal input support
Earlier support period begins2025-01-01
Earlier support period ends2025-06-30
Other support period begins2025-05-01
Other support period ends2025-08-31
Same purpose and qualifying unitYes

Compare the same permitted entity, purpose and qualifying unit. Intersect dated support intervals; overlapping support is a review flag, not proof of duplicate entitlement.

Other required records: Participant ID; support purpose; programme; period; prior support; authorization.

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. Correct incomplete field records before reviewDEC-DP13-019 · Field form quality
Try this decision

Find missing field-record metadata and supporting references.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — field form quality / Laggala PallegamaRecord ID: MissingObtain the missing evidence listed below
Rattota — field form quality / Rattotarequired fields: MissingObtain the missing evidence listed below
Panvila — field form quality / Panvilaunits: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this field form quality 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
  • Record ID: Missing

A complete record does not establish a reliable field observation.

Inputs, method and sources
Supplied inputValueUnit
Record IDMissing
Record ID evidence referenceNot provided
required fieldsDocumented
required fields evidence referenceSample Laggala Pallegama field register / 2025
unitsDocumented
units evidence referenceSample Laggala Pallegama field register / 2025
timestampsDocumented
timestamps evidence referenceSample Laggala Pallegama field register / 2025
sourceDocumented
source evidence referenceSample Laggala Pallegama field register / 2025
attachmentsDocumented
attachments evidence referenceSample Laggala Pallegama field register / 2025
validationDocumented
validation 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: Record ID; required fields; units; timestamps; source; attachments; validation.

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. Assess whether completed interventions improved local outcomesDEC-DP13-020 · Local outcomes
Try this decision

Compare outcomes in treated and comparison observations.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [percentage points]Next check
Laggala Pallegama — local outcomes / 202510Obtain the missing evidence listed below
Rattota — local outcomes / 202510Obtain the missing evidence listed below
Panvila — local outcomes / 202510Obtain the missing evidence listed below

What the selected record shows. Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. 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

The difference alone does not establish that the works caused an improvement.

Inputs, method and sources
Supplied inputValueUnit
Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before42%
Intervention group households with the stated functioning soil-and-water conservation measure at follow-up after59%
Comparison group households with the stated functioning soil-and-water conservation measure at follow-up before39%
Comparison group households with the stated functioning soil-and-water conservation measure at follow-up after46%
Study design and comparability evidenceMissing
Outcome definition, method and reference basisFictional measure: Households with the stated functioning soil-and-water conservation measure at follow-up / matching frame, method and before-after windows

(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. This named fictional indicator illustrates the calculation. Design evidence, adverse effects and attribution remain separate; a difference in changes does not establish causation.

Other required records: Baseline; follow-up; intervention dates; comparison sites; weather; community feedback.

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.
Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

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
FP124 financing · Programme Delivery

Existing form reference: e6af681e07c8efdc

FieldUnitRequired
Funding itemConfirm if neededNo
InstrumentConfirm if neededNo
AmountUSDNo
CurrencyConfirm if neededNo
DateConfirm if neededNo
BasisConfirm 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.

Sub-Watershed Integrated Delivery Teams Documents and images prototype screen
Sub-Watershed Integrated Delivery Teams. 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.

Sub-Watershed Integrated Delivery Teams Data structure management prototype screen
Sub-Watershed Integrated Delivery Teams. 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.

Sub-Watershed Integrated Delivery Teams Users and access prototype screen
Sub-Watershed Integrated Delivery Teams. 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.