Farmer Organizations

Tell us what to change or add.

1. Check a decision

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

2. Try the inputs

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

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

3. Check each decision

1. Coordinate support for underused member farmlandDEC-DP32-001 · Land use · Suggested priority: High
Try this decision

Coordinate support for underused member farmland.

Validation required

Verified coverage — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Member plots; usable hectares; cultivated hectares; season; inactivity reason.

Fictional worked example · 2025

Laggala Pallegama — land use · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100ha
Distinct members of that frame covered65ha
Frame members with unknown coverage5ha
Verified coverage65%
Known uncovered30ha
Unknown coverage5ha

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
2. Review potentially overlapping assistance to membersDEC-DP32-002 · Support fairness · Suggested priority: High
Try this decision

Review potentially overlapping assistance to members.

Validation required

Overlapping days — fictional 2025 examples

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

Next step. Review possible overlap. Resolve duplicate identity or overlapping support and decide permitted complementary assistance.

Inputs, example and sources

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

Analysis inputs. Permitted recipient/service reference; Support purpose; Earlier support period begins; Earlier support period ends; Other support period begins; Other support period ends; Same purpose and qualifying unit

Other required evidence. Member ID; programme; purpose; support quantity; period; entitlement.

Fictional worked example · 2025

Laggala Pallegama — support fairness · Laggala Pallegama

Input or resultValueUnit
Permitted recipient/service referenceLaggala Pallegama — support fairness
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
Overlapping days61days

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Confirmed unique support and unresolved overlap cases.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
3. Prepare evidence-based seasonal water requestsDEC-DP32-003 · Irrigation requests · Suggested priority: High
Try this decision

Prepare evidence-based seasonal water requests.

Verified published component · Crop evapotranspiration ETc component

Gross daily irrigation requirement — fictional 2025 examples

Method. ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency.

Next step. Review evidence. Propose crop demand, scheduling or allocation alternatives for authorized review.

Inputs, example and sources

Food and Agriculture Organization of the United Nations · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration
Institution publication · Chapter 5, Crop coefficient approach, equation 56

This verifies the ETc component only. Local water-balance allowances, coefficients and operating decisions still need confirmation.

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

Analysis inputs. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction]

Other required evidence. Crop areas; growth stages; rainfall; soil water; percolation; efficiency.

Fictional worked example · 2025

Laggala Pallegama — irrigation requests · Laggala Pallegama

Input or resultValueUnit
Irrigated crop area85ha
Reference evapotranspiration4.5mm/day
Crop coefficient1.1ratio
Rainfall reaching the field after runoff1.6mm/day
Deep percolation and paddy allowance2mm/day
Capillary contribution0mm/day
Desired change in stored soil water0mm/day
Field application efficiency0.68fraction
Gross daily irrigation requirement6,687.5m³/day
Net field requirement5.35mm/day

The full local balance, rooting depth, stress, crop stage and operating constraints still matter. The paddy allowance is explicit and must be zero where inapplicable. This is not an authorized reservoir release.

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Delivered water, crop stress, unmet demand and downstream conditions.

  • FAO 56: crop evapotranspiration — Institution publication. FAO 56 Chapter 5 equation 56; ETc = Kc × ETo. Institutional context; does not establish the calculation or local approval.
  • FAO56 root-zone water balance — Institution publication. Chapter8 equation85 and ETc = Kc ETo. Daily water balance components; local coefficients and operating assumptions still need review.
  • FAO Irrigation Water Management Training Manual 3 — Institution publication. Chapter 4.4 Irrigation water need of rice; steps 1 to 8. Institutional context; does not establish the calculation or local approval.
  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
4. Escalate overdue collective farming requestsDEC-DP32-004 · Service coordination · Suggested priority: Medium
Try this decision

Escalate overdue collective farming requests.

Validation required

Open days past due — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Request; institution; receipt; due date; response; responsible coordinator.

Fictional worked example · 2025

Laggala Pallegama — service coordination · Laggala Pallegama

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

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
5. Propose workable water rotations for member areasDEC-DP32-005 · Water rotations · Suggested priority: High
Try this decision

Propose workable water rotations for member areas.

Validation required

Planned duration — fictional 2025 examples

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

Next step. Resolve overlapping resource bookings. Assign a feasible timetable, redistribute resources, or escalate the blocked dependency.

Inputs, example and sources

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

Analysis inputs. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites

Other required evidence. Approved allocation; outlet capacity; crop stage; delivery windows; member agreement.

Fictional worked example · 2025

Laggala Pallegama — water rotations · Laggala Pallegama

Input or resultValueUnit
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
Planned duration3days
Resource hours remaining8hours

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. On-time completion with verified outputs and resource use.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
6. Check unequal delivery against agreed allocationsDEC-DP32-006 · Tail-end equity · Suggested priority: High
Try this decision

Investigate unequal delivery against agreed allocations.

Validation required

Difference — fictional 2025 examples

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

Next step. Review evidence. Investigate a material deviation, assign correction, or propose a target revision.

Inputs, example and sources

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

Analysis inputs. Planned value [m³]; Observed value [m³]

Other required evidence. Outlet; location; agreed water; actual delivery; hectares; season.

Fictional worked example · 2025

Laggala Pallegama — tail-end equity · Laggala Pallegama

Input or resultValueUnit
Planned value100m³
Observed value90m³
Difference-10m³
Relative change-10%

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Subsequent variance with original and revised targets retained.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
7. Plan joint input purchases against verified member demandDEC-DP32-007 · Collective inputs · Suggested priority: High
Try this decision

Plan joint input purchases against verified member demand.

Validation required

Uncommitted usable stock — fictional 2025 examples

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

Next step. Review replenishment gap. Reorder approved quantities, redistribute stock, or quarantine affected lots.

Inputs, example and sources

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

Analysis inputs. Physical stock [kg input]; Quarantined stock [kg input]; Expired stock [kg input]; Committed usable stock [kg input]; Additional demand [kg input]; Supplier lead time [days]; Remaining shelf life of usable stock [days]

Other required evidence. Input specification; demand; current stock; supplier lead time; commitments; expiry.

Fictional worked example · 2025

Laggala Pallegama — collective inputs · Laggala Pallegama

Input or resultValueUnit
Physical stock1,200kg input
Quarantined stock100kg input
Expired stock50kg input
Committed usable stock740kg input
Additional demand500kg input
Supplier lead time14days
Remaining shelf life of usable stock30days
Uncommitted usable stock310kg input
Additional demand gap190kg input

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Stockouts, expiry, losses and verified lot traceability.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
8. Match aggregated produce with verified buyer requirementsDEC-DP32-008 · Collective marketing · Suggested priority: High
Try this decision

Match aggregated produce with verified buyer requirements.

Validation required

Supply minus demand — fictional 2025 examples

Method. Compare the same specification and unit, uncommitted quantity and overlapping delivery windows. Keep mandatory quality and use conditions explicit.

Next step. Review quantity/capacity gap. Refer a feasible match for negotiation, request revised terms, or retain unmatched demand.

Inputs, example and sources

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

Analysis inputs. Offered product and grade; Required product and grade; Available uncommitted quantity [kg]; Required quantity [kg]; Supply available from; Supply available until; Delivery window begins; Delivery window ends; Required quality, rights and conditions

Other required evidence. Member supply; product; grade; quantity; harvest window; buyer demand.

Fictional worked example · 2025

Laggala Pallegama — collective marketing · Laggala Pallegama

Input or resultValueUnit
Offered product and gradeCleaned dry pepper / whole grain
Required product and gradeCleaned dry pepper / whole grain
Available uncommitted quantity1,200kg
Required quantity1,500kg
Supply available from2025-06-01
Supply available until2025-06-20
Delivery window begins2025-06-05
Delivery window ends2025-06-18
Required quality, rights and conditionsMet
Supply minus demand-300kg

A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract.

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Confirmed fulfilled matches, quality, timeliness and unresolved demand.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
9. Allocate shared machinery without conflicting reservationsDEC-DP32-009 · Machinery sharing · Suggested priority: Medium
Try this decision

Allocate shared machinery without conflicting reservations.

Validation required

Planned duration — fictional 2025 examples

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

Next step. Resolve overlapping resource bookings. Assign a feasible timetable, redistribute resources, or escalate the blocked dependency.

Inputs, example and sources

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

Analysis inputs. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites

Other required evidence. Equipment; condition; member bookings; field access; operation duration; crop window.

Fictional worked example · 2025

Laggala Pallegama — machinery sharing · Laggala Pallegama

Input or resultValueUnit
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
Planned duration3days
Resource hours remaining8hours

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. On-time completion with verified outputs and resource use.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
10. Choose what to handle first: common tank and canal maintenance requestsDEC-DP32-010 · Irrigation upkeep · Suggested priority: High
Try this decision

Prioritize common tank and canal maintenance requests.

Validation required

Open days past due — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Asset condition; defects; command area; users affected; work options; costs.

Fictional worked example · 2025

Laggala Pallegama — irrigation upkeep · Laggala Pallegama

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

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
11. Compare and correct differences in organization receipts expenses and balancesDEC-DP32-011 · Group finance · Suggested priority: High
Try this decision

Reconcile organization receipts expenses and balances.

Validation required

Calculated closing balance — fictional 2025 examples

Method. Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume.

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

Inputs, example and sources

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

Analysis inputs. Opening cash/receivable balance [LKR]; Receipts and documented additions [LKR]; Payments and documented reductions [LKR]; Other documented non-overlapping adjustments [LKR]; Independently recorded closing balance [LKR]

Other required evidence. Opening balance; member contributions; sales; authorized spending; bank statements.

Fictional worked example · 2025

Laggala Pallegama — group finance · Laggala Pallegama

Input or resultValueUnit
Opening cash/receivable balance160,000LKR
Receipts and documented additions48,000LKR
Payments and documented reductions35,000LKR
Other documented non-overlapping adjustments9,000LKR
Independently recorded closing balance163,500LKR
Calculated closing balance164,000LKR
Recorded minus calculated closing-500LKR

Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss.

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
12. Resolve inconsistent or duplicate member recordsDEC-DP32-012 · Membership · Suggested priority: Medium
Try this decision

Resolve inconsistent or duplicate member records.

Validation required

Unresolved equivalence items — fictional 2025 examples

Method. Compare original definitions, identifiers, units and versions against documented equivalence evidence. Preserve conflicts and unresolved mappings; do not subtract category labels or silently merge records.

Next step. Resolve source disagreement. Assign discrepancies to the custodian, accept documented corrections, or retain unresolved versions.

Inputs, example and sources

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

Analysis inputs. Original source value/definition; Comparison source value/definition; Original version; Comparison version; Documented equivalence evidence

Other required evidence. Member identifier; membership evidence; active status; plot linkage; consent.

Fictional worked example · 2025

Laggala Pallegama — membership · Laggala Pallegama

Input or resultValueUnit
Original source value/definitionMember identifier: primary register entry
Comparison source value/definitionMember identifier: conflicting source return
Original versionSample version1
Comparison versionSample version2
Documented equivalence evidenceUnresolved
Unresolved equivalence items1items

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Discrepancies resolved with evidence and repeat error rate.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
13. Address missing meetings audits and required disclosuresDEC-DP32-013 · Governance · Suggested priority: High
Try this decision

Address missing meetings audits and required disclosures.

Validation required

Evidence gaps — fictional 2025 examples

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

Next step. Complete the evidence. Request correction, refer mandatory failures, or accept the inspected item with conditions.

Inputs, example and sources

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

Analysis inputs. Rules; Rules evidence reference; meeting records; meeting records evidence reference; election evidence; election evidence evidence reference; audit findings; audit findings evidence reference; approved obligations; approved obligations evidence reference

Other required evidence. Rules; meeting records; election evidence; audit findings; approved obligations.

Fictional worked example · 2025

Laggala Pallegama — governance · Laggala Pallegama

Input or resultValueUnit
RulesMissing
Rules evidence reference
meeting recordsDocumented
meeting records evidence referenceSample Laggala Pallegama field register / 2025
election evidenceDocumented
election evidence evidence referenceSample Laggala Pallegama field register / 2025
audit findingsDocumented
audit findings evidence referenceSample Laggala Pallegama field register / 2025
approved obligationsDocumented
approved obligations evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Evidence-backed corrective closure and recurring nonconformances.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
14. Target member training to verified skill gapsDEC-DP32-014 · Training · Suggested priority: Medium
Try this decision

Target member training to verified skill gaps.

Validation required

Verified coverage — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Member needs; prior training; practice adoption; crop; participation.

Fictional worked example · 2025

Laggala Pallegama — training · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100members
Distinct members of that frame covered65members
Frame members with unknown coverage5members
Verified coverage65%
Known uncovered30members
Unknown coverage5members

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
15. Compare collective responses to forecast water shortagesDEC-DP32-015 · Drought plans · Suggested priority: High
Try this decision

Compare collective responses to forecast water shortages.

Validation required

Budget remaining after option — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Approved forecasts; available water; crop choices; loss estimates; member consultation.

Fictional worked example · 2025

Joint procurement · Laggala Pallegama

Input or resultValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Expected benefit and its evidenceCompare collective responses to forecast water shortages; Approved forecasts and available water evidence needed
Resource needs and adverse effectsSample water, labour, access and safeguard trade-offs
Budget remaining after option300,000LKR

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
16. Coordinate verification of shared crop-damage reportsDEC-DP32-016 · Crop-loss evidence · Suggested priority: High
Try this decision

Coordinate verification of shared crop-damage reports.

Validation required

Evidence gaps — fictional 2025 examples

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

Next step. Complete the evidence. Request correction, refer mandatory failures, or accept the inspected item with conditions.

Inputs, example and sources

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

Analysis inputs. Event; Event evidence reference; member plot; member plot evidence reference; damaged hectares; damaged hectares evidence reference; crop stage; crop stage evidence reference; inspection; inspection evidence reference; claim reference; claim reference evidence reference

Other required evidence. Event; member plot; damaged hectares; crop stage; inspection; claim reference.

Fictional worked example · 2025

Laggala Pallegama — crop-loss evidence · Laggala Pallegama

Input or resultValueUnit
EventMissing
Event evidence reference
member plotDocumented
member plot evidence referenceSample Laggala Pallegama field register / 2025
damaged hectaresDocumented
damaged hectares evidence referenceSample Laggala Pallegama field register / 2025
crop stageDocumented
crop stage evidence referenceSample Laggala Pallegama field register / 2025
inspectionDocumented
inspection evidence referenceSample Laggala Pallegama field register / 2025
claim referenceDocumented
claim reference evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Evidence-backed corrective closure and recurring nonconformances.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
17. Compare collective storage and handling investmentsDEC-DP32-017 · Storage · Suggested priority: Medium
Try this decision

Compare collective storage and handling investments.

Verified published formula · Discounted cash-flow NPV

Five-year net present value — fictional 2025 examples

Method. NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5.

Next step. Review evidence. Compare feasible investments, adjust the scope, or defer pending finance/evidence.

Inputs, example and sources

Food and Agriculture Organization of the United Nations · Guidelines for defining financial economic environmental and social information
Institution publication · Sections 2.2.2 and 2.2.3, discounting and Net Present Value

The five-year horizon, discount rate and cash assumptions are local settings. Verification does not approve an investment or loan.

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

Analysis inputs. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%]

Other required evidence. Supply volume; losses; storage capacity; cost; market timing; finance.

Fictional worked example · 2025

Laggala Pallegama — storage · Laggala Pallegama

Input or resultValueUnit
Initial investment2,400,000LKR
Net cash flow year1400,000LKR
Net cash flow year2550,000LKR
Net cash flow year3680,000LKR
Net cash flow year4720,000LKR
Net cash flow year5760,000LKR
Residual value at end of year5120,000LKR
Example discount rate8%
Five-year net present value109,847.353LKR

Match currency, price year, real/nominal basis and cash-flow timing. The example rate and five-year horizon are assumptions, not institutional financing terms; no credit approval follows.

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Realized cash flows, benefits and costs versus the approved appraisal.

Institution and data context

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

Your checks for this decision
18. Resolve member objections to collective plansDEC-DP32-018 · Participation · Suggested priority: High
Try this decision

Resolve member objections to collective plans.

Validation required

Response share — fictional 2025 examples

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

Next step. Resolve participation barriers and issues. Address concerns, revise the proposal, seek required responses, or escalate unresolved conditions.

Inputs, example and sources

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

Analysis inputs. Distinct relevant people invited [people]; People who responded [people]; Unresolved issues [issues]; Proposal/version being discussed; Required participation channels accessible

Other required evidence. Plan version; members; consultation responses; water rights; unresolved issues.

Fictional worked example · 2025

Laggala Pallegama — participation · Laggala Pallegama

Input or resultValueUnit
Distinct relevant people invited95people
People who responded68people
Unresolved issues16issues
Proposal/version being discussedSample proposal1
Required participation channels accessibleUnknown
Response share71.579%
Unresolved issues16issues

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

After the action. Resolved concerns, participation and compliance with recorded commitments.

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
19. Follow up members missing agreed information updatesDEC-DP32-019 · Member communication · Suggested priority: Lower
Try this decision

Follow up members missing agreed information updates.

Validation required

Verified coverage — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Member frame; preferred channel; message; delivery evidence; consent; date.

Fictional worked example · 2025

Laggala Pallegama — member communication · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100members
Distinct members of that frame covered65members
Frame members with unknown coverage5members
Verified coverage65%
Known uncovered30members
Unknown coverage5members

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision
20. Compare benefits and costs of group farming servicesDEC-DP32-020 · Collective outcomes · Suggested priority: Medium
Try this decision

Evaluate benefits and costs of group farming services.

Verified published formula · Difference-in-differences arithmetic

Difference in changes — fictional 2025 examples

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

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

Inputs, example and sources

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

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

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

Analysis inputs. Treatment Member enterprise gross margin before [LKR/ha]; Treatment Member enterprise gross margin after [LKR/ha]; Comparison Member enterprise gross margin before [LKR/ha]; Comparison Member enterprise gross margin after [LKR/ha]; Study design and comparability evidence; Outcome definition, method and reference basis

Other required evidence. Member baseline; service uptake; margins; follow-up; comparison; market conditions.

Fictional worked example · 2025

Laggala Pallegama — collective outcomes · Laggala Pallegama

Input or resultValueUnit
Treatment Member enterprise gross margin before420,000LKR/ha
Treatment Member enterprise gross margin after590,000LKR/ha
Comparison Member enterprise gross margin before390,000LKR/ha
Comparison Member enterprise gross margin after460,000LKR/ha
Study design and comparability evidenceMissing
Outcome definition, method and reference basisMember enterprise gross margin /example matching definition1
Difference in changes100,000LKR/ha

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

Proposed checking role. Farmer-organization committee and relevant agriculture/water adviser.

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

  • World Bank Impact Evaluation in Practice Second Edition — Institution publication. Chapter7 difference-in-differences. Published difference-in-differences estimator and study assumptions; aggregate examples do not establish causation.
  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Institution and data context

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

Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Irrigation Offices · Land Suitability

Existing form reference: b5701ed646f0f063

FieldUnitRequired
nameConfirm if neededNo
categoryConfirm if neededNo
district_nConfirm if neededNo
AgroEcological Zones Point · Land Suitability

Existing form reference: cc316b77dd9398f9

FieldUnitRequired
fid_1Confirm if neededNo
leftConfirm if neededNo
bottomConfirm if neededNo
rightConfirm if neededNo
topConfirm if neededNo
xConfirm if neededNo
yConfirm if neededNo
fid_2Confirm if neededNo
join_countConfirm if neededNo
target_fidConfirm if neededNo
idConfirm if neededNo
gridcodeConfirm if neededNo
final_idConfirm if neededNo
zoneConfirm if neededNo
climatic_zConfirm if neededNo
agro_eco_zConfirm if neededNo
agro_eco_rConfirm if neededNo
terrainConfirm if neededNo
major_soilConfirm if neededNo
land_useConfirm if neededNo
anualrfmmConfirm if neededNo
ASC Locations · Land Suitability

Existing form reference: a64b0a6754afd4ed

FieldUnitRequired
ASC NumberConfirm if neededNo
ASC NameConfirm if neededNo
XCOORDConfirm if neededNo
YCOORDConfirm if neededNo
Location CodeConfirm if neededNo
DescriptionConfirm if neededNo
Agro Ecological Zones · Land Suitability

Existing form reference: 592c3b578787edcd

FieldUnitRequired
ZoneConfirm if neededNo
Climatic_ZoneConfirm if neededNo
Agro_Eco_ZoneConfirm if neededNo
Agro_Eco_RConfirm if neededNo
Final_IDConfirm if neededNo
TerrainConfirm if neededNo
Major_SoilConfirm if neededNo
Land_UseConfirm if neededNo
AnualRFmmConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Irrigation Schemes · Land Suitability

Existing form reference: 648a6f28a711dfa9

FieldUnitRequired
System NameConfirm if neededNo
SystemsConfirm if neededNo
IDConfirm if neededNo
ID_SystemsConfirm if neededNo
MASL_SystemConfirm if neededNo
DSD_NameConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Irrigation Lands · Land Suitability

Existing form reference: e877698582fc591c

FieldUnitRequired
Landuse TypeConfirm if neededNo
Landuse Classification (CropType)Confirm 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
Crops Suitability · Land Suitability

Existing form reference: 54fb1fe96af4f04c

FieldUnitRequired
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
District NameConfirm if neededNo
District CodeConfirm if neededNo
DS Division NameConfirm if neededNo
DS Division CodeConfirm if neededNo
GND NameConfirm if neededNo
GND NumberConfirm if neededNo
MC UC PS NameConfirm if neededNo
MC UC PS CodeConfirm if neededNo
Polling Division NameConfirm if neededNo
Polling Division CodeConfirm if neededNo
idConfirm if neededNo
Area HectareConfirm if neededNo
ASC NameConfirm if neededNo
Area Sq KmConfirm if neededNo
Square KmConfirm if neededNo
Crop TypeConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Agrarian development divisions · Administrative & Planning Areas

Existing form reference: fc991a6c3bc249f6

FieldUnitRequired
idConfirm if neededNo
do Agrarian Development IdConfirm if neededNo
nameConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
District commissioner divisions · Administrative & Planning Areas

Existing form reference: 57c890c642eab82c

FieldUnitRequired
idConfirm if neededNo
district Comm IdConfirm if neededNo
nameConfirm if neededNo
do Agrarian Development DTO / idConfirm if neededNo
do Agrarian Development DTO / do Agrarian Development IdConfirm if neededNo
do Agrarian Development DTO / nameConfirm if neededNo
do Agrarian Development DTO / created DateConfirm if neededNo
do Agrarian Development DTO / modified DateConfirm if neededNo
do Agrarian Development DTO / cityConfirm if neededNo
do Agrarian Development DTO / latitudeConfirm if neededNo
do Agrarian Development DTO / longitudeConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Asc divisions · Administrative & Planning Areas

Existing form reference: 0bb5ed17e5cdc863

FieldUnitRequired
idConfirm if neededNo
asc IdConfirm if neededNo
nameConfirm if neededNo
district Commissioner Level DTO / idConfirm if neededNo
district Commissioner Level DTO / district Comm IdConfirm if neededNo
district Commissioner Level DTO / nameConfirm if neededNo
district Commissioner Level DTO / do Agrarian Development DTOConfirm if neededNo
district Commissioner Level DTO / created DateConfirm if neededNo
district Commissioner Level DTO / modified DateConfirm if neededNo
district Commissioner Level DTO / cityConfirm if neededNo
district Commissioner Level DTO / latitudeConfirm if neededNo
district Commissioner Level DTO / longitudeConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Paddy, OFC & VEG — 2026 Yala - April · Crop Production

Existing form reference: f2c8e1b979a467f1

FieldUnitRequired
CropConfirm if neededNo
DistrictConfirm if neededNo
MeasureConfirm if neededNo
ValuehaNo
UnitConfirm if neededNo
SeasonConfirm if neededNo
Wholesale food prices — 2026-10-28 · Markets & Value Chains

Existing form reference: 5ef25f806a9c3864

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-27 · Markets & Value Chains

Existing form reference: 65fb55fc4bacaeb4

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-26 · Markets & Value Chains

Existing form reference: 3d27791c0b26d5a7

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-23 · Markets & Value Chains

Existing form reference: 362fe913ea87b4d5

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-22 · Markets & Value Chains

Existing form reference: 4c6b93b0f4ec772d

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-21 · Markets & Value Chains

Existing form reference: edf7d040b8bcbc45

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm if neededNo
Wholesale food prices — 2026-10-20 · Markets & Value Chains

Existing form reference: f462aa65988abf9a

FieldUnitRequired
CommodityConfirm if neededNo
MarketConfirm if neededNo
DateConfirm if neededNo
Average priceConfirm if neededNo
UnitConfirm if neededNo
Source pageConfirm 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.

Farmer Organizations Documents and images prototype screen
Farmer Organizations. 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.

Farmer Organizations Data structure management prototype screen
Farmer Organizations. 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.

Farmer Organizations Users and access prototype screen
Farmer Organizations. 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.