Department of Agrarian Development

Sri Lanka decision proposal

Tell us what to change or add.

Archived decisions

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. Prioritize service areas with unmet crop water needsDEC-DP04-003 · Minor irrigation
Try this decision

Compare matching crop-water requirement and supply records.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³]Relative change [%]Next check
Laggala Pallegama — minor irrigation / 2025-21,000-24.706Review the delivery shortfall and allocation constraints
Rattota — minor irrigation / 20255,0005.882Review the delivery shortfall and allocation constraints
Panvila — minor irrigation / 2025-7,000-8.235Review the delivery shortfall and allocation constraints

What the selected record shows. Difference: -21,000 m³. Review the delivery shortfall and allocation constraints.

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

A shortfall alone does not establish an authorised allocation.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Recorded crop-water requirement for this period85,000m³
Recorded water supplied in the same period64,000m³

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

Other required records: Tank command hectares; crop water demand; dependable supply; season; service boundary.

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. Follow up delayed farmer-service requestsDEC-DP04-004 · Agrarian services
Try this decision

Identify open farmer-service cases that have passed their due date.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — agrarian services / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — agrarian services / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — agrarian services / 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 describe delay, not case severity.

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: Request ID; service type; receipt date; due date; pauses; responsible officer.

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. Screen paddy conversion requests for formal determinationDEC-DP04-007 · Land conversion
Try this decision

Check a paddy-conversion application before referring it for formal determination.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — land conversion / Laggala PallegamaParcel status: MissingObtain the missing evidence listed below
Rattota — land conversion / Rattotaproposed use: MissingObtain the missing evidence listed below
Panvila — land conversion / Panvilaapplication evidence: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this land conversion 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
  • Parcel status: Missing

Application completeness is not conversion permission.

Inputs, method and sources
Supplied inputValueUnit
Parcel statusMissing
Parcel status evidence referenceNot provided
proposed useDocumented
proposed use evidence referenceSample Laggala Pallegama field register / 2025
application evidenceDocumented
application evidence evidence referenceSample Laggala Pallegama field register / 2025
current rulesDocumented
current rules evidence referenceSample Laggala Pallegama field register / 2025
inspection findingsDocumented
inspection findings 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: Parcel status; proposed use; application evidence; current rules; inspection findings.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
4. Compare minor-tank rehabilitation alternativesDEC-DP04-008 · Tank rehabilitation
Try this decision

Compare minor-tank repair choices using engineering evidence and resources.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Repair the sluice and leaks / Laggala PallegamaAddress the recorded sluice or leakage problem.Needs an engineering inspection, operating window and competent construction.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Rehabilitate selected canal reaches / Laggala PallegamaAddress the documented conveyance defects in selected canal reaches.Needs surveys, access, crop-season coordination and maintenance arrangements.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Stage the bund and canal works / Laggala PallegamaSequence bund and canal repairs within resources.Needs engineering priorities, compatible stages and a safe operating plan.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: Tank condition; command hectares; sediment survey; repair cost; demand; safeguards
  • Applicable conditions, what was checked and the supporting reference

Cost alone does not establish the safest or most effective repair.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionAddress the recorded sluice or leakage problem.
Resource needs and adverse effectsNeeds an engineering inspection, operating window and competent construction.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

Cost alone does not establish the safest or most effective repair.

Other required records: Tank condition; command hectares; sediment survey; repair cost; demand; safeguards.

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. Follow up unreconciled farmer-organization fundsDEC-DP04-010 · Organization finance
Try this decision

Reconcile receipts, payments and the recorded closing fund balance.

Validation required

Fictional default example · 2025.

Fictional case / areaCalculated closing balance [LKR]Recorded minus calculated closing [LKR]Next check
Laggala Pallegama — organization finance / 2025164,000-500Reconcile closing balance
Rattota — organization finance / 2025164,000-500Reconcile closing balance
Panvila — organization finance / 2025164,000-500Reconcile closing balance

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

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

A residual is not proof of theft or a measured loss.

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

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.

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

Other required records: Opening cash; receipts; authorized expenditure; bank balance; supporting vouchers.

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. Plan timely distribution of approved farm inputsDEC-DP04-013 · Input distribution
Try this decision

Compare usable input stock and delivery commitments with the distribution requirement.

Validation required

Fictional default example · 2025.

Fictional case / areaUncommitted usable stock [kg input]Additional demand gap [kg input]Next check
Laggala Pallegama — input distribution / 2025310190Review replenishment gap
Rattota — input distribution / 2025310190Review replenishment gap
Panvila — input distribution / 2025310190Review replenishment gap

What the selected record shows. Uncommitted usable stock: 310 kg input. 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 item, season and delivery window.

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

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: Approved demand; usable stock; committed stock; delivery date; input expiry.

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. Allocate staff to agrarian centres with workload gapsDEC-DP04-014 · Service centres
Try this decision

Compare agrarian-centre workload 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 — service centres / 2025-15135Review capacity shortfall
Rattota — service centres / 2025-15135Review capacity shortfall
Panvila — service centres / 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 demonstrate the required skills.

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: Open requests; handling time; available staff hours; service targets; travel requirements.

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. Schedule communal minor-irrigation maintenanceDEC-DP04-015 · Canal maintenance
Try this decision

Check maintenance tasks against shared resources and prerequisite windows.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — canal maintenance / 202538Resolve overlapping resource bookings
Rattota — canal maintenance / 202538Resolve overlapping resource bookings
Panvila — canal maintenance / 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 draft schedule does not book staff or operate irrigation assets.

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: Canal reach; defects; work duration; cultivation calendar; labour availability; 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
9. Check reported encroachment evidenceDEC-DP04-017 · Tank reservations
Try this decision

Check reported overlap before referring an encroachment concern.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlap share [%]Overlapping area [ha]Next check
Laggala Pallegama — tank reservations / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — tank reservations / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — tank reservations / 20252418Check the matching footprint, source boundary and applicable conditions

What the selected record shows. The supplied overlap is 18 ha within the 75 ha assessed footprint, or 24%. Check the cited boundary and source records before interpreting the overlap.

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

A supplied overlap does not determine ownership or unlawful occupation.

Inputs, method and sources
Supplied inputValueUnit
Assessed footprint or frame75ha
Reported common overlap, counted once18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional matched survey return / edition 1

100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.

Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries.

Other required records: Reservation boundary; observed activity geometry; map edition; inspection 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.
Reference map image
Matale District location in Sri Lanka — published static reference map
Reference map image — not live. Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.
Your checks for this decision
10. Review head-end and tail-end water-delivery differencesDEC-DP04-018 · Irrigation equity
Try this decision

Compare documented head-end and tail-end delivery in the same period.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³]Relative change [%]Next check
Laggala Pallegama — irrigation equity / 2025-6,000-25Investigate the comparable head-end and tail-end delivery difference
Rattota — irrigation equity / 2025-1,500-6.25Investigate the comparable head-end and tail-end delivery difference
Panvila — irrigation equity / 2025-3,000-12.5Investigate the comparable head-end and tail-end delivery difference

What the selected record shows. Difference: -6,000 m³. Investigate the comparable head-end and tail-end delivery difference.

Next step. Investigate the comparable head-end and tail-end delivery difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Unequal volumes need comparable areas, needs and operating conditions.

Example chart
Difference — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Head-end delivered volume for a matching eligible area24,000m³
Tail-end delivered volume on the same area and period basis18,000m³

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

Compare equivalent command areas, delivery windows and measurement methods. This is not a planned-versus-actual comparison.

Other required records: Outlet ID; position; delivered cubic metres; agreed allocation; service hectares.

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. Schedule outdated farmer and land record checksDEC-DP04-019 · Registry updates
Try this decision

Plan checks of outdated farmer and land records within available staff windows.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — registry updates / 202538Resolve overlapping resource bookings
Rattota — registry updates / 202538Resolve overlapping resource bookings
Panvila — registry updates / 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.

A schedule does not verify the records or send assignments.

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: Record ID; last verification; reported change; officer capacity; review 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
12. Evaluate whether agrarian support improved cultivationDEC-DP04-020 · Service outcomes
Try this decision

Compare cultivation changes in supported and comparison observations.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

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

What the selected record shows. Treatment change: 17; comparison change: 7; difference in changes: 10 %. 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 comparison alone does not establish that support caused the change.

Inputs, method and sources
Supplied inputValueUnit
Treatment Verified cultivated share before42%
Treatment Verified cultivated share after59%
Comparison Verified cultivated share before39%
Comparison Verified cultivated share after46%
Study design and comparability evidenceMissing
Outcome definition, method and reference basisVerified cultivated share /example matching definition1

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

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

Other required records: Supported plots; baseline cultivation; follow-up cultivation; comparable plots; weather.

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
13. Check the seasonal paddy production return before submissionDEC-DP04-021 · Published method
Try this decision

Source. Sri Lanka publication.

Data needed. Season, reporting area, net extent harvested, matching average yield and reported production.

Method. Calculate production from net harvested hectares times the matching average yield in tonnes per hectare. Reconcile any unexplained difference with the return.

Worked example. A Yala return lists 24 ha harvested and 4.2 t/ha. The calculated production is 100.8 t. Check the area or yield if the return shows 100 t.

Next step. Return records with incompatible areas, units or unexplained differences to the reporting officer.

Department of Census and Statistics, Statistical Abstract agriculture chapter. Explanatory notes under Paddy yields and Paddy production.

Confirm the reporting boundary, net harvested extent and rounding rules.

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
Paddy area by irrigation scheme, 2015–2024 · Crop Production

Existing form reference: a12dececef469dda

FieldUnitRequired
YearConfirm if neededNo
Published season labelConfirm if neededNo
Source blockConfirm if neededNo
MeasureConfirm if neededNo
Irrigation schemeConfirm if neededNo
AreahaNo

5. Documents and images

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

Department of Agrarian Development Documents and images prototype screen
Department of Agrarian Development. 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.

Department of Agrarian Development Data structure management prototype screen
Department of Agrarian Development. 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.

Department of Agrarian Development Users and access prototype screen
Department of Agrarian Development. 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.