Grama Niladhari Officers

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. Submit overdue required village reportsDEC-DP31-001 · Field reporting · Suggested priority: High
Try this decision

Submit overdue required village reports.

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. Report type; GN area; due date; submission; acceptance; correction request.

Fictional worked example · 2025

Laggala Pallegama — field reporting · 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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
2. Find households needing consented follow-up or referralDEC-DP31-002 · Community observations · Suggested priority: High
Try this decision

Identify households needing consented follow-up or referral.

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 [households]; Distinct members of that frame covered [households]; Frame members with unknown coverage [households]

Other required evidence. Household reference; reported need; observation date; consent; referral criteria.

Fictional worked example · 2025

Laggala Pallegama — community observations · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100households
Distinct members of that frame covered65households
Frame members with unknown coverage5households
Verified coverage65%
Known uncovered30households
Unknown coverage5households

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
3. Resolve incomplete or inconsistent village case reportsDEC-DP31-003 · Case corrections · Suggested priority: Medium
Try this decision

Resolve incomplete or inconsistent village case reports.

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. Case ID; required evidence; conflicting fields; verification; correction history.

Fictional worked example · 2025

Laggala Pallegama — case corrections · Laggala Pallegama

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
4. Check missing or uncertain locations of community assetsDEC-DP31-004 · Asset locations · Suggested priority: Medium
Try this decision

Verify missing or uncertain locations of community assets.

Validation required

Location separation — fictional 2025 examples

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

Next step. Review evidence. 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. Measured separation between reported locations [m]; Reported source positional accuracy [m]; Reported comparison positional accuracy [m]; Coordinate reference and transformation evidence

Other required evidence. Asset ID; submitted location; GPS accuracy; field evidence; official boundary.

Fictional worked example · 2025

Laggala Pallegama — asset locations · Laggala Pallegama

Input or resultValueUnit
Measured separation between reported locations32m
Reported source positional accuracy10m
Reported comparison positional accuracy15m
Coordinate reference and transformation evidenceSample matching CRS; transformation check required
Location separation32m

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
5. Choose what to handle first: rapid verification of local disaster impactsDEC-DP31-005 · Disaster impacts · Suggested priority: High
Try this decision

Prioritize rapid verification of local disaster impacts.

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; household reference; household reference evidence reference; observed damage; observed damage evidence reference; date; date evidence reference; location; location evidence reference; assessment protocol; assessment protocol evidence reference

Other required evidence. Event; household reference; observed damage; date; location; assessment protocol.

Fictional worked example · 2025

Laggala Pallegama — disaster impacts · Laggala Pallegama

Input or resultValueUnit
EventMissing
Event evidence reference
household referenceDocumented
household reference evidence referenceSample Laggala Pallegama field register / 2025
observed damageDocumented
observed damage evidence referenceSample Laggala Pallegama field register / 2025
dateDocumented
date evidence referenceSample Laggala Pallegama field register / 2025
locationDocumented
location evidence referenceSample Laggala Pallegama field register / 2025
assessment protocolDocumented
assessment protocol evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
6. Prepare evidence for authorized relief decisionsDEC-DP31-006 · Relief referrals · Suggested priority: High
Try this decision

Prepare evidence for authorized relief decisions.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Household; Household evidence reference; verified impact; verified impact evidence reference; scheme rules; scheme rules evidence reference; documents; documents evidence reference; existing support; existing support evidence reference; consent; consent evidence reference

Other required evidence. Household; verified impact; scheme rules; documents; existing support; consent.

Fictional worked example · 2025

Laggala Pallegama — relief referrals · Laggala Pallegama

Input or resultValueUnit
HouseholdMissing
Household evidence reference
verified impactDocumented
verified impact evidence referenceSample Laggala Pallegama field register / 2025
scheme rulesDocumented
scheme rules evidence referenceSample Laggala Pallegama field register / 2025
documentsDocumented
documents evidence referenceSample Laggala Pallegama field register / 2025
existing supportDocumented
existing support evidence referenceSample Laggala Pallegama field register / 2025
consentDocumented
consent evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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

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

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. Flag possible repeated assistance for divisional reviewDEC-DP31-007 · Duplicate assistance · Suggested priority: High
Try this decision

Flag possible repeated assistance for divisional review.

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. Recipient identifier; programme; support purpose; dates; quantity; evidence.

Fictional worked example · 2025

Laggala Pallegama — duplicate assistance · Laggala Pallegama

Input or resultValueUnit
Permitted recipient/service referenceLaggala Pallegama — duplicate assistance
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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
8. Schedule verification of reported household changesDEC-DP31-008 · Household updates · Suggested priority: High
Try this decision

Schedule verification of reported household changes.

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. Household record; reported change; evidence; verification date; officer capacity.

Fictional worked example · 2025

Laggala Pallegama — household updates · 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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
9. Check required evidence before referring certificate requestsDEC-DP31-009 · Certificate evidence · Suggested priority: Medium
Try this decision

Check required evidence before referring certificate requests.

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. Request; Request evidence reference; documentary evidence; documentary evidence evidence reference; verification; verification evidence reference; current criteria; current criteria evidence reference; authorized issuer; authorized issuer evidence reference

Other required evidence. Request; documentary evidence; verification; current criteria; authorized issuer.

Fictional worked example · 2025

Laggala Pallegama — certificate evidence · Laggala Pallegama

Input or resultValueUnit
RequestMissing
Request evidence reference
documentary evidenceDocumented
documentary evidence evidence referenceSample Laggala Pallegama field register / 2025
verificationDocumented
verification evidence referenceSample Laggala Pallegama field register / 2025
current criteriaDocumented
current criteria evidence referenceSample Laggala Pallegama field register / 2025
authorized issuerDocumented
authorized issuer evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
10. Refer unmet needs through approved support channelsDEC-DP31-010 · Vulnerable residents · Suggested priority: High
Try this decision

Refer unmet needs through approved support channels.

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 [households]; Distinct members of that frame covered [households]; Frame members with unknown coverage [households]

Other required evidence. Consented needs; eligibility frame; accessible services; referral; follow-up.

Fictional worked example · 2025

Laggala Pallegama — vulnerable residents · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100households
Distinct members of that frame covered65households
Frame members with unknown coverage5households
Verified coverage65%
Known uncovered30households
Unknown coverage5households

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
11. Escalate unresolved local complaints within jurisdictionDEC-DP31-011 · Community complaints · Suggested priority: High
Try this decision

Escalate unresolved local complaints within jurisdiction.

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. Complaint; date; issue category; responsible office; response; approved deadline.

Fictional worked example · 2025

Laggala Pallegama — community complaints · 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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
12. Find residents missing authorized emergency messagesDEC-DP31-012 · Public warnings · Suggested priority: High
Try this decision

Identify residents missing authorized emergency messages.

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 [households]; Distinct members of that frame covered [households]; Frame members with unknown coverage [households]

Other required evidence. Official warning; affected area; household frame; delivery evidence; accessibility.

Fictional worked example · 2025

Laggala Pallegama — public warnings · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100households
Distinct members of that frame covered65households
Frame members with unknown coverage5households
Verified coverage65%
Known uncovered30households
Unknown coverage5households

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
13. Ensure relevant residents can participate in consultationsDEC-DP31-013 · Community meetings · Suggested priority: Medium
Try this decision

Ensure relevant residents can participate in consultations.

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. Issue; stakeholder frame; invitations; attendance; responses; accessibility needs.

Fictional worked example · 2025

Laggala Pallegama — community meetings · 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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
14. Refer damaged public assets to responsible maintainersDEC-DP31-014 · Local infrastructure · Suggested priority: Medium
Try this decision

Refer damaged public assets to responsible maintainers.

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; observed defect; users affected; location; maintenance owner.

Fictional worked example · 2025

Laggala Pallegama — local infrastructure · 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. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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
15. Report land-use concerns without making ownership determinationsDEC-DP31-015 · Land observations · Suggested priority: High
Try this decision

Report land-use concerns without making ownership determinations.

Validation required

Spatially matched share — fictional 2025 examples

Method. 100×distinct spatially matched receptors / receptors in the same frame. Count a receptor once across overlapping areas; do not invent hectare areas from points.

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

Inputs, example and sources

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

Analysis inputs. Distinct receptors/observations in the defined frame [units]; Distinct receptors matching the stated spatial relation [units]; Boundary edition and spatial predicate; Hazard/constraint/source class and observation period

Other required evidence. Observed activity; location; date; registered references; uncertainty; referral authority.

Fictional worked example · 2025

Laggala Pallegama — land observations · Laggala Pallegama

Input or resultValueUnit
Distinct receptors/observations in the defined frame75units
Distinct receptors matching the stated spatial relation18units
Boundary edition and spatial predicateSample within/overlap predicate1
Hazard/constraint/source class and observation periodSample dated source class
Spatially matched share24%
Distinct matched receptors18units

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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

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

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. Plan feasible household and site follow-up routesDEC-DP31-016 · Field visits · Suggested priority: Medium
Try this decision

Plan feasible household and site follow-up routes.

Validation required

Estimated travel time — fictional 2025 examples

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

Next step. Resolve access/capacity evidence. Choose a permitted feasible route, postpone, or request updated access evidence.

Inputs, example and sources

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

Analysis inputs. Verified route distance [km]; Estimated route travel time [minutes]; Usable vehicle/team capacity [units]; Required capacity [units]; Access, closures and operating conditions; Operating and service window

Other required evidence. Visit locations; urgency; access; travel time; visit duration; officer availability.

Fictional worked example · 2025

Laggala Pallegama — field visits · Laggala Pallegama

Input or resultValueUnit
Verified route distance24km
Estimated route travel time65minutes
Usable vehicle/team capacity18units
Required capacity15units
Access, closures and operating conditionsUnresolved
Operating and service windowSample operating window
Estimated travel time65minutes
Capacity minus demand3units

Straight-line distance is not a road route. Example routes establish no current road status, emergency clearance or safe evacuation instruction.

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

After the action. Verified travel time, deliveries and unresolved access needs.

  • 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. Track referrals to verified service outcomesDEC-DP31-017 · Programme follow-up · Suggested priority: Medium
Try this decision

Track referrals to verified service outcomes.

Validation required

Verified completion share — fictional 2025 examples

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

Next step. Review evidence. Address stage bottlenecks, follow up dropouts, or revise service delivery.

Inputs, example and sources

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

Analysis inputs. Unique original cohort entrants [cases]; Entrants reviewed [cases]; Entrants with verified completion [cases]; Entrants with unknown follow-up [cases]

Other required evidence. Referral; receiving institution; response; delivery evidence; follow-up date.

Fictional worked example · 2025

Laggala Pallegama — programme follow-up · Laggala Pallegama

Input or resultValueUnit
Unique original cohort entrants180cases
Entrants reviewed132cases
Entrants with verified completion96cases
Entrants with unknown follow-up12cases
Verified completion share53.333%
Not verified complete84cases

Attendance, receipt, adoption, delivered service and outcomes are distinct stages. Repeated visits must not become new people.

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

After the action. Verified progression, waiting times and outcomes for the same cohort.

  • 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
18. Check permitted use before sharing household informationDEC-DP31-018 · Record privacy · Suggested priority: High
Try this decision

Check permitted use before sharing household information.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Fields; Fields evidence reference; purpose; purpose evidence reference; consent or lawful basis; consent or lawful basis evidence reference; recipient; recipient evidence reference; scope; scope evidence reference; approval; approval evidence reference

Other required evidence. Fields; purpose; consent or lawful basis; recipient; scope; approval.

Fictional worked example · 2025

Laggala Pallegama — record privacy · Laggala Pallegama

Input or resultValueUnit
FieldsMissing
Fields evidence reference
purposeDocumented
purpose evidence referenceSample Laggala Pallegama field register / 2025
consent or lawful basisDocumented
consent or lawful basis evidence referenceSample Laggala Pallegama field register / 2025
recipientDocumented
recipient evidence referenceSample Laggala Pallegama field register / 2025
scopeDocumented
scope evidence referenceSample Laggala Pallegama field register / 2025
approvalDocumented
approval evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

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

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

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. Correct local records assigned to inconsistent geographic codesDEC-DP31-019 · Boundary codes · Suggested priority: Lower
Try this decision

Correct local records assigned to inconsistent geographic codes.

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. Approve a documented mapping, keep it Draft, or create a governed concept after review.

Inputs, example and sources

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

Analysis inputs. Record location; Record location evidence reference; official GN code; official GN code evidence reference; boundary edition; boundary edition evidence reference; source date; source date evidence reference; crosswalk; crosswalk evidence reference

Other required evidence. Record location; official GN code; boundary edition; source date; crosswalk.

Fictional worked example · 2025

Laggala Pallegama — boundary codes · Laggala Pallegama

Input or resultValueUnit
Record locationMissing
Record location evidence reference
official GN codeDocumented
official GN code evidence referenceSample Laggala Pallegama field register / 2025
boundary editionDocumented
boundary edition evidence referenceSample Laggala Pallegama field register / 2025
source dateDocumented
source date evidence referenceSample Laggala Pallegama field register / 2025
crosswalkDocumented
crosswalk evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

After the action. Unmapped/conflicting concepts and history preserved across revisions.

  • 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. Find recurring local service problems from feedbackDEC-DP31-020 · Service feedback · Suggested priority: Medium
Try this decision

Identify recurring local service problems from feedback.

Validation required

Feedback case count — fictional 2025 examples

Method. Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale.

Next step. Review evidence. Investigate material differences and redirect planning or field verification where justified.

Inputs, example and sources

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

Analysis inputs. Distinct feedback cases in category [cases]; Cases still unresolved [cases]; Feedback service/category

Other required evidence. Feedback category; period; resolution; repeat issue; service; respondent coverage.

Fictional worked example · 2025

Water supply · Laggala Pallegama reporting frame

Input or resultValueUnit
Distinct feedback cases in category25cases
Cases still unresolved8cases
Feedback service/categoryWater supply
Feedback case count25cases
Share of recorded feedback4.762%

Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.

Proposed checking role. Grama Niladhari officer with divisional supervisor and relevant service reviewer.

After the action. Change in the approved composition indicator with coverage disclosed.

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

Gram Niladhari Divisions · Administrative & Planning Areas

Existing form reference: 6ffaab5927d760f2

FieldUnitRequired
GND NameConfirm if neededNo
GND CodeConfirm if neededNo
GND NumberConfirm if neededNo
GND Name GazettedConfirm if neededNo
DS Division NameConfirm if neededNo
DS Division CodeConfirm if neededNo
District NameConfirm if neededNo
District CodeConfirm if neededNo
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
MC UC PC NameConfirm if neededNo
GND Officer NameConfirm if neededNo
DisputeConfirm if neededNo
Province Census CodeConfirm if neededNo
District Census CodeConfirm if neededNo
DS Division Census CodeConfirm if neededNo
GND Census CodeConfirm if neededNo
GND No CensusConfirm if neededNo
GND Name CensusConfirm if neededNo
Admin CodeConfirm if neededNo
CM IndexConfirm if neededNo
GND Number GazettedConfirm if neededNo
Year CreatedConfirm if neededNo
Data SourceConfirm if neededNo
Method Of CreationConfirm if neededNo
ExtentConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Divisional Secretariat Boundary · Administrative & Planning Areas

Existing form reference: 38b3db2354e6f075

FieldUnitRequired
DS Division NameConfirm if neededNo
DS Division CodeConfirm if neededNo
District NameConfirm if neededNo
District CodeConfirm if neededNo
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
Adjusted AreaConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
District Boundary · Administrative & Planning Areas

Existing form reference: 3e275a626091b924

FieldUnitRequired
District NameConfirm if neededNo
District CodeConfirm if neededNo
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
Adjusted AreaConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Province Boundary · Administrative & Planning Areas

Existing form reference: c2c98ee086137a9b

FieldUnitRequired
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
ISO Alpha 2 CodeConfirm if neededNo
Area TrueConfirm if neededNo
Area AdjustConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Provinces · Administrative & Planning Areas

Existing form reference: 34b688f04ba12422

FieldUnitRequired
idConfirm if neededNo
nameConfirm if neededNo
codeConfirm if neededNo
Districts · Administrative & Planning Areas

Existing form reference: f25025b360be4121

FieldUnitRequired
idConfirm if neededNo
nameConfirm if neededNo
codeConfirm if neededNo
province DTO / idConfirm if neededNo
province DTO / nameConfirm if neededNo
province DTO / codeConfirm if neededNo
Ds divisions · Administrative & Planning Areas

Existing form reference: b89e70ac83fb5930

FieldUnitRequired
idConfirm if neededNo
codeConfirm if neededNo
nameConfirm if neededNo
district DTO / idConfirm if neededNo
district DTO / nameConfirm if neededNo
district DTO / codeConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
Gn divisions · Administrative & Planning Areas

Existing form reference: 8f42b4909736031c

FieldUnitRequired
idConfirm if neededNo
nameConfirm if neededNo
codeConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
land AreaConfirm if neededNo
agricultural Land AreaConfirm if neededNo
non Agricultural Land AreaConfirm if neededNo
crop AreaConfirm if neededNo
agro Ecological Zone DTO / idConfirm if neededNo
agro Ecological Zone DTO / ae Zone IdConfirm if neededNo
agro Ecological Zone DTO / nameConfirm if neededNo
agro Ecological Zone DTO / average RainfallConfirm if neededNo
ai Regions DTO / idConfirm if neededNo
ai Regions DTO / region IdConfirm if neededNo
ai Regions DTO / descriptionConfirm if neededNo
ai Regions DTO / asc Region IdConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / idConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / province Segment IdConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / descriptionConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / idConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / provincial Dd IdConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / descriptionConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / idConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / pro Director IdConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / descriptionConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / cityConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / latitudeConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / longitudeConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / cityConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / latitudeConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / longitudeConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / cityConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / latitudeConfirm if neededNo
ai Regions DTO / provincial Ada Segment DTO / longitudeConfirm if neededNo
ds Division DTO / idConfirm if neededNo
ds Division DTO / codeConfirm if neededNo
ds Division DTO / nameConfirm if neededNo
ds Division DTO / district DTO / idConfirm if neededNo
ds Division DTO / district DTO / nameConfirm if neededNo
ds Division DTO / district DTO / codeConfirm if neededNo
ds Division DTO / district DTO / province DTO / idConfirm if neededNo
ds Division DTO / district DTO / province DTO / nameConfirm if neededNo
ds Division DTO / district DTO / province DTO / codeConfirm if neededNo
arpa DTO / idConfirm if neededNo
arpa DTO / arpa IdConfirm if neededNo
arpa DTO / nameConfirm if neededNo
arpa DTO / asc Dto / idConfirm if neededNo
arpa DTO / asc Dto / asc IdConfirm if neededNo
arpa DTO / asc Dto / nameConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / idConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / district Comm IdConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / nameConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / do Agrarian Development DTOConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / created DateConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / modified DateConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / cityConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / latitudeConfirm if neededNo
arpa DTO / asc Dto / district Commissioner Level DTO / longitudeConfirm if neededNo
arpa DTO / asc Dto / created DateConfirm if neededNo
arpa DTO / asc Dto / modified DateConfirm if neededNo
arpa DTO / asc Dto / cityConfirm if neededNo
arpa DTO / asc Dto / latitudeConfirm if neededNo
arpa DTO / asc Dto / longitudeConfirm if neededNo
arpa DTO / created DateConfirm if neededNo
arpa DTO / modified DateConfirm if neededNo
arpa DTO / cityConfirm if neededNo
arpa DTO / latitudeConfirm if neededNo
arpa DTO / longitudeConfirm if neededNo
gn Division TypeConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / idConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / segment IdConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / descriptionConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / idConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / dd IdConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / descriptionConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / idConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / doa IdConfirm if neededNo
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / descriptionConfirm if neededNo
mahaweli Unit DTO / idConfirm if neededNo
mahaweli Unit DTO / unit IdConfirm if neededNo
mahaweli Unit DTO / descriptionConfirm if neededNo
ds Division DTO / district DTO / province DTO / created DateConfirm if neededNo
ds Division DTO / district DTO / province DTO / modified DateConfirm if neededNo
scs Sub Region IdConfirm if neededNo
scs Sub Region Dto / idConfirm if neededNo
scs Sub Region Dto / codeConfirm if neededNo
scs Sub Region Dto / descriptionConfirm if neededNo
scs Sub Region Dto / scs RegionConfirm if neededNo
Provincial director divisions · Administrative & Planning Areas

Existing form reference: 2337b92f31770ba9

FieldUnitRequired
idConfirm if neededNo
pro Director IdConfirm if neededNo
descriptionConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Provincial deputy director level · Administrative & Planning Areas

Existing form reference: ca12c4d677b5003c

FieldUnitRequired
idConfirm if neededNo
provincial Dd IdConfirm if neededNo
descriptionConfirm if neededNo
pro Director Level DTO / idConfirm if neededNo
pro Director Level DTO / pro Director IdConfirm if neededNo
pro Director Level DTO / descriptionConfirm if neededNo
pro Director Level DTO / cityConfirm if neededNo
pro Director Level DTO / latitudeConfirm if neededNo
pro Director Level DTO / longitudeConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Doa divisions · Administrative & Planning Areas

Existing form reference: eb2b3109790a85b0

FieldUnitRequired
idConfirm if neededNo
doa IdConfirm if neededNo
descriptionConfirm if neededNo
Inter-provincial ada divisions · Administrative & Planning Areas

Existing form reference: 3c4b7ca01eae2c96

FieldUnitRequired
idConfirm if neededNo
segment IdConfirm if neededNo
descriptionConfirm if neededNo
inter Province Deputy Director Level DTO / idConfirm if neededNo
inter Province Deputy Director Level DTO / dd IdConfirm if neededNo
inter Province Deputy Director Level DTO / descriptionConfirm if neededNo
Mahaweli authorities · Administrative & Planning Areas

Existing form reference: a928ea0c164539db

FieldUnitRequired
idConfirm if neededNo
authority IdConfirm if neededNo
descriptionConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Mahaweli systems · Administrative & Planning Areas

Existing form reference: 8e71c080613ac3a4

FieldUnitRequired
idConfirm if neededNo
system IdConfirm if neededNo
descriptionConfirm if neededNo
mahaweli Authority DTO / idConfirm if neededNo
mahaweli Authority DTO / authority IdConfirm if neededNo
mahaweli Authority DTO / descriptionConfirm if neededNo
mahaweli Authority DTO / cityConfirm if neededNo
mahaweli Authority DTO / latitudeConfirm if neededNo
mahaweli Authority DTO / longitudeConfirm if neededNo
cityConfirm if neededNo
latitudeConfirm if neededNo
longitudeConfirm if neededNo
Mahaweli blocks · Administrative & Planning Areas

Existing form reference: 1b6608ff1b096b55

FieldUnitRequired
idConfirm if neededNo
codeConfirm if neededNo
mahaweli System DTO / idConfirm if neededNo
mahaweli System DTO / system IdConfirm if neededNo
mahaweli System DTO / descriptionConfirm if neededNo
mahaweli System DTO / mahaweli Authority DTOConfirm if neededNo
mahaweli System DTO / cityConfirm if neededNo
mahaweli System DTO / latitudeConfirm if neededNo
mahaweli System DTO / longitudeConfirm if neededNo
descriptionConfirm if neededNo
land AreaConfirm if neededNo
cultivated AreaConfirm if neededNo
irrigated AreaConfirm if neededNo
non Irrigated AreaConfirm if neededNo
created DateConfirm if neededNo
modified DateConfirm if neededNo
district DTO / idConfirm if neededNo
district DTO / nameConfirm if neededNo
district DTO / codeConfirm if neededNo
ds Division DTO / idConfirm if neededNo
ds Division DTO / codeConfirm if neededNo
ds Division DTO / nameConfirm if neededNo
ds Division DTO / created DateConfirm if neededNo
ds Division DTO / modified DateConfirm if neededNo
Mahaweli units · Administrative & Planning Areas

Existing form reference: b2dbe12695570d5c

FieldUnitRequired
idConfirm if neededNo
unit IdConfirm if neededNo
descriptionConfirm if neededNo
mahaweli Block DTO / idConfirm if neededNo
mahaweli Block DTO / descriptionConfirm if neededNo
mahaweli Block DTO / land AreaConfirm if neededNo
mahaweli Block DTO / cultivated AreaConfirm if neededNo
mahaweli Block DTO / irrigated AreaConfirm if neededNo
mahaweli Block DTO / non Irrigated AreaConfirm 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
Population Information by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: 3758c98eb50413af

FieldUnitRequired
Province CodeConfirm if neededNo
Province NameConfirm if neededNo
District CodeConfirm if neededNo
District NameConfirm if neededNo
DS_Division CodeConfirm if neededNo
DS_Division NameConfirm if neededNo
GN_Division CodeConfirm if neededNo
GN_Division NameConfirm if neededNo
GN_Division NumberConfirm if neededNo
Sex / TotalpersonsNo
Sex / MalepersonsNo
Sex / FemalepersonsNo
Age_Group / TotalpersonsNo
Age_Group / 0 - 14personsNo
Age_Group / 15 - 59personsNo
Age_Group / 60 - 64personsNo
Age_Group / 65 and abovepersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Occupied Housing Units by Grama Niladhari Division · Population & Households

Existing form reference: 8372d13713031913

FieldUnitRequired
Province CodeConfirm if neededNo
Province NameConfirm if neededNo
District CodeConfirm if neededNo
District NameConfirm if neededNo
DS_Division CodeConfirm if neededNo
DS_Division NameConfirm if neededNo
GN_Division CodeConfirm if neededNo
GN_Division NameConfirm if neededNo
GN_Division NumberConfirm if neededNo
Occupied Housing UnitsConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Information on Occupied Housing Units by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: e7e1c2657503020f

FieldUnitRequired
Province CodeConfirm if neededNo
Province NameConfirm if neededNo
District CodeConfirm if neededNo
District NameConfirm if neededNo
DS_Division CodeConfirm if neededNo
DS_Division NameConfirm if neededNo
GN_Division CodeConfirm if neededNo
GN_Division NameConfirm if neededNo
GN_Division NumberConfirm if neededNo
Occupied Housing UnitsConfirm if neededNo
Type of Housing unit Structure / Single house - single storeyedConfirm if neededNo
Type of Housing unit Structure / Single house - two storeyedConfirm if neededNo
Type of Housing unit Structure / Single house - more than two storeyedConfirm if neededNo
Type of Housing unit Structure / Attached house - 1st FloorConfirm if neededNo
Type of Housing unit Structure / Attached house - 2nd FloorConfirm if neededNo
Type of Housing unit Structure / Attached house - From 3 to 4 FloorsConfirm if neededNo
Type of Housing unit Structure / Attached house - From 5 to 10 FloorsConfirm if neededNo
Type of Housing unit Structure / Attached house - From 11to 19 FloorsConfirm if neededNo
Type of Housing unit Structure / Attached house - From 20 Floors or moreConfirm if neededNo
Type of Housing unit Structure / OtherConfirm if neededNo
Principal material of construction of the Walls / BricksConfirm if neededNo
Principal material of construction of the Walls / Cement blockConfirm if neededNo
Principal material of construction of the Walls / Granite/ Cube stonesConfirm if neededNo
Principal material of construction of the Walls / CabookConfirm if neededNo
Principal material of construction of the Walls / Pressed soil bricksConfirm if neededNo
Principal material of construction of the Walls / Warichchi / MudConfirm if neededNo
Principal material of construction of the Walls / Cadjan/ PalmyrahConfirm if neededNo
Principal material of construction of the Walls / Planks/ Metal Sheets/ AsbestosConfirm if neededNo
Principal material of construction of the Walls / Zink Aluminium SheetsConfirm if neededNo
Principal material of construction of the Walls / Other (specify)Confirm if neededNo
Principal material of construction of the Walls / Not relaventConfirm if neededNo
Principal material of construction of the Floor / CementConfirm if neededNo
Principal material of construction of the Floor / Terrazzo/Tile/Granite/Wood (Finished)Confirm if neededNo
Principal material of construction of the Floor / ConcreteConfirm if neededNo
Principal material of construction of the Floor / MudConfirm if neededNo
Principal material of construction of the Floor / WoodConfirm if neededNo
Principal material of construction of the Floor / SandConfirm if neededNo
Principal material of construction of the Floor / Other (specify)Confirm if neededNo
Principal material of construction of the Floor / Not relaventConfirm if neededNo
Principal material of construction of the Roof / TileConfirm if neededNo
Principal material of construction of the Roof / AsbestosConfirm if neededNo
Principal material of construction of the Roof / ConcreteConfirm if neededNo
Principal material of construction of the Roof / Zink Aluminium SheetConfirm if neededNo
Principal material of construction of the Roof / Metal SheetConfirm if neededNo
Principal material of construction of the Roof / Cadjan/ Palmyrah/ StrawConfirm if neededNo
Principal material of construction of the Roof / Other (specify)Confirm if neededNo
Principal material of construction of the Roof / Not relaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Household Information by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: da744a0cfc8f5c9f

FieldUnitRequired
Province CodeConfirm if neededNo
Province NameConfirm if neededNo
District CodeConfirm if neededNo
District NameConfirm if neededNo
DS_Division CodeConfirm if neededNo
DS_Division NameConfirm if neededNo
GN_Division CodeConfirm if neededNo
GN_Division NameConfirm if neededNo
GN_Division NumberConfirm if neededNo
Number of HouseholdsConfirm if neededNo
Main Source/way of drinking water / Ground Water / Protected wellConfirm if neededNo
Main Source/way of drinking water / Ground Water / Semi protected wellConfirm if neededNo
Main Source/way of drinking water / Ground Water / Unprotected wellConfirm if neededNo
Main Source/way of drinking water / Ground Water / Tube wellConfirm if neededNo
Main Source/way of drinking water / Ground Water / Spring/ FountainConfirm if neededNo
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - National water supply & drainage boardConfirm if neededNo
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Local AuthorityConfirm if neededNo
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Community base organiziationConfirm if neededNo
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Private water supply projectConfirm if neededNo
Main Source/way of drinking water / Other / Tank/ River/StreamsConfirm if neededNo
Main Source/way of drinking water / Other / Rain waterConfirm if neededNo
Main Source/way of drinking water / Other / Bottled waterConfirm if neededNo
Main Source/way of drinking water / Other / Filter water (R.O. Plant)Confirm if neededNo
Main Source/way of drinking water / Other / BowserConfirm if neededNo
Main Source/way of drinking water / Other / Other (specify)Confirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Fire woodConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / KeroseneConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / GasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / ElectricityConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy huskConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Bio gasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Other (Specify bellow )Confirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Not relaventConfirm if neededNo
Main source of Lighting / Electricity - from National grid/rural hydro power projectConfirm if neededNo
Main source of Lighting / Kerosene lampConfirm if neededNo
Main source of Lighting / Solar power (grid connected)Confirm if neededNo
Main source of Lighting / Solar power (stand alone)Confirm if neededNo
Main source of Lighting / Bio gasConfirm if neededNo
Main source of Lighting / GeneratorConfirm if neededNo
Main source of Lighting / Other (Specify bellow )Confirm if neededNo
Toilet facilities / Within the unit / Within the housing unit - Exclusively for the householdConfirm if neededNo
Toilet facilities / Within the unit / Within the housing unit - Sharing with another householdConfirm if neededNo
Toilet facilities / Outside the unit / Within Premises - Exclusively for the householdConfirm if neededNo
Toilet facilities / Outside the unit / Within Premises - Sharing with another householdConfirm if neededNo
Toilet facilities / Other / No toilet but sharing with another housing unit/unitsConfirm if neededNo
Toilet facilities / Other / Common/ Public toiletConfirm if neededNo
Toilet facilities / Other / Not using a toilet (use jungle, beach and open ground)Confirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
GN Level Population by Ethnic Group, CPH 2024 · Population & Households

Existing form reference: e5112accd6912288

FieldUnitRequired
District CodeConfirm if neededNo
District NameConfirm if neededNo
DSD CodeConfirm if neededNo
DSD NamepersonsNo
GND CodeConfirm if neededNo
GND NamepersonsNo
Ethnic Group / TotalpersonsNo
Ethnic Group / SinhalesepersonsNo
Ethnic Group / Sri Lanka TamilpersonsNo
Ethnic Group / Indian Tamil/ Malaiyaga ThamilarpersonsNo
Ethnic Group / Sri Lanka Moor/MuslimpersonsNo
Ethnic Group / BurgherpersonsNo
Ethnic Group / MalaypersonsNo
Ethnic Group / Sri Lanka ChettypersonsNo
Ethnic Group / BharathapersonsNo
Ethnic Group / VeddahspersonsNo
Ethnic Group / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
GN Level Population by Five Year Age Group, CPH 2024 · Population & Households

Existing form reference: bb924a4e93f0a33d

FieldUnitRequired
District CodeConfirm if neededNo
District NameConfirm if neededNo
DSD CodeConfirm if neededNo
DSD NamepersonsNo
GND CodeConfirm if neededNo
GND NamepersonsNo
Age Group / TotalpersonsNo
Age Group / 0 - 4personsNo
Age Group / 5 - 9personsNo
Age Group / 10-14personsNo
Age Group / 15-19personsNo
Age Group / 20-24personsNo
Age Group / 25-29personsNo
Age Group / 30-34personsNo
Age Group / 35-39personsNo
Age Group / 40-44personsNo
Age Group / 45-49personsNo
Age Group / 50-54personsNo
Age Group / 55-59personsNo
Age Group / 60-64personsNo
Age Group / 65-69personsNo
Age Group / 70-74personsNo
Age Group / 75-79personsNo
Age Group / 80-84personsNo
Age Group / 85-89personsNo
Age Group / 90-94personsNo
Age Group / 95 and abovepersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
GN Level Population by Local Government Area, CPH 2024 · Population & Households

Existing form reference: 05d85f4e809f399c

FieldUnitRequired
District CodeConfirm if neededNo
District NameConfirm if neededNo
DSD CodeConfirm if neededNo
DSD NamepersonsNo
GND CodeConfirm if neededNo
GND NamepersonsNo
Sector / TotalpersonsNo
Sector / Municiple CouncilpersonsNo
Sector / Urban CouncilpersonsNo
Sector / Pradeshiya SabhapersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
GN Level Population by Religion, CPH 2024 · Population & Households

Existing form reference: 9fe44f410d52a912

FieldUnitRequired
District CodeConfirm if neededNo
District NameConfirm if neededNo
DSD CodeConfirm if neededNo
DSD NamepersonsNo
GND CodeConfirm if neededNo
GND NamepersonsNo
Religion / TotalpersonsNo
Religion / BuddhistpersonsNo
Religion / HindupersonsNo
Religion / IslampersonsNo
Religion / Roman CatholicpersonsNo
Religion / Other ChristianpersonsNo
Religion / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
GN Level Population by Sector, CPH 2024 · Population & Households

Existing form reference: a96d28bdb2a7a507

FieldUnitRequired
District CodeConfirm if neededNo
District NameConfirm if neededNo
DSD CodeConfirm if neededNo
DSD NamepersonsNo
GND CodeConfirm if neededNo
GND NamepersonsNo
Sector / TotalpersonsNo
Sector / Urban*personsNo
Sector / RuralpersonsNo
Sector / Estate Rural**personsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by sex and age according to districts, 2024 · Population & Households

Existing form reference: e937770c5212a493

FieldUnitRequired
DistrictConfirm if neededNo
Total number of personspersonsNo
Sex / MalepersonsNo
Sex / FemalepersonsNo
Age / Less than 15 yearspersonsNo
Age / 15 ‐ 59 YearspersonsNo
Age / 60-64 YearspersonsNo
Age / 65 years and overpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by ethnic group according to districts, 2024 · Population & Households

Existing form reference: 5830f8c01719d23d

FieldUnitRequired
DistrictConfirm if neededNo
Total number of personspersonsNo
Ethnic Group / SinhaleespersonsNo
Ethnic Group / Sri lanka TamilpersonsNo
Ethnic Group / Indian Tamil/ Malaiyaga ThamilarpersonsNo
Ethnic Group / Sri Lanka Moor/MuslimpersonsNo
Ethnic Group / BurgherpersonsNo
Ethnic Group / MalaypersonsNo
Ethnic Group / Sri Lanka ChettypersonsNo
Ethnic Group / BharathapersonsNo
Ethnic Group / VeddhaspersonsNo
Ethnic Group / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by religion according to districts, 2024 · Population & Households

Existing form reference: 596bd468dd17458f

FieldUnitRequired
DistrictConfirm if neededNo
Total number of personspersonsNo
Religion / BuddhistpersonsNo
Religion / HindupersonsNo
Religion / IslampersonsNo
Religion / Roman CatholicpersonsNo
Religion / Other ChristianpersonsNo
Religion / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Migrant population by reason for migrating according to districts, 2024 · Population & Households

Existing form reference: 322c7e6af73ccfe3

FieldUnitRequired
DistrictConfirm if neededNo
Total migrant populationConfirm if neededNo
Main reason for migration / MarriageConfirm if neededNo
Main reason for migration / Employment / Searching for a jobConfirm if neededNo
Main reason for migration / EducationConfirm if neededNo
Main reason for migration / Accompanied a family memberConfirm if neededNo
Main reason for migration / Returning for permanentConfirm if neededNo
Main reason for migration / Development projectConfirm if neededNo
Main reason for migration / Resettled after displacementConfirm if neededNo
Main reason for migration / A disaster / a displaced happened in the prior placeConfirm if neededNo
Main reason for migration / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by sex, age according to Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 010da3c91df400eb

FieldUnitRequired
District and Divisional Secretary's DivisionConfirm if neededNo
Total number of personspersonsNo
Sex / MalepersonsNo
Sex / FemalepersonsNo
Age / Less than 15 yearspersonsNo
Age / 15 ‐ 59 YearspersonsNo
Age / 60-64 YearspersonsNo
Age / 65 years and overpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by ethnicity according to Divisional SSecretariat Divisions, 2024 · Population & Households

Existing form reference: 7053ac00629aeff8

FieldUnitRequired
District and Divisional Secretary's DivisionConfirm if neededNo
Total number of personspersonsNo
Ethnic Group / SinhaleespersonsNo
Ethnic Group / Sri lanka TamilpersonsNo
Ethnic Group / Indian Tamil/ Malaiyaga ThamilarpersonsNo
Ethnic Group / Sri Lanka Moor/MuslimpersonsNo
Ethnic Group / BurgherpersonsNo
Ethnic Group / MalaypersonsNo
Ethnic Group / Sri Lanka ChettypersonsNo
Ethnic Group / BharathapersonsNo
Ethnic Group / VeddhaspersonsNo
Ethnic Group / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Population by religion according to Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 36222798f483fabe

FieldUnitRequired
District and Divisional Secretary's DivisionConfirm if neededNo
Total number of personspersonsNo
Religion / BuddhistpersonsNo
Religion / HindupersonsNo
Religion / IslampersonsNo
Religion / Roman CatholicpersonsNo
Religion / Other ChristianpersonsNo
Religion / OtherpersonsNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by housing unit structure at district level 2024 · Population & Households

Existing form reference: a2103035c8ce0bac

FieldUnitRequired
DistrictConfirm if neededNo
Number of housing unitsConfirm if neededNo
Structure of housing unit / Single house - Single storeyedConfirm if neededNo
Structure of housing unit / Single house - Two storeyedConfirm if neededNo
Structure of housing unit / Single house - more than two storeyedConfirm if neededNo
Structure of housing unit / Attached House - 1st FloorConfirm if neededNo
Structure of housing unit / Attached House - 2nd FloorConfirm if neededNo
Structure of housing unit / Attached House - 3rd or 4th FloorsConfirm if neededNo
Structure of housing unit / Attached House - 5th to 10th FloorsConfirm if neededNo
Structure of housing unit / Attached House - 11th to 19th FloorsConfirm if neededNo
Structure of housing unit / Attached House - From 20th Floors or moreConfirm if neededNo
Structure of housing unit / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for walls construction at district level, 2024 · Population & Households

Existing form reference: 41eb1069e9c9c17d

FieldUnitRequired
DistrictConfirm if neededNo
Number of housing unitsConfirm if neededNo
Main material of construction of the roof / BrickConfirm if neededNo
Main material of construction of the roof / Cement blockConfirm if neededNo
Main material of construction of the roof / Granite/Cube stonesConfirm if neededNo
Main material of construction of the roof / CabookConfirm if neededNo
Main material of construction of the roof / Pressed soil bricksConfirm if neededNo
Main material of construction of the roof / Mud/WarichchiConfirm if neededNo
Main material of construction of the roof / Kadjan/ PalmyrahConfirm if neededNo
Main material of construction of the roof / Plank/ Metal Sheet/AsbestosConfirm if neededNo
Main material of construction of the roof / Zink Aluminium SheetsConfirm if neededNo
Main material of construction of the roof / OtherConfirm if neededNo
Main material of construction of the roof / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for roof construction at district level, 2024 · Population & Households

Existing form reference: 74f863b697ebe277

FieldUnitRequired
DistrictConfirm if neededNo
Number of housing unitsConfirm if neededNo
Main material of construction of the roof / TileConfirm if neededNo
Main material of construction of the roof / AsbestosConfirm if neededNo
Main material of construction of the roof / ConcreteConfirm if neededNo
Main material of construction of the roof / Zink Aluminium SheetConfirm if neededNo
Main material of construction of the roof / Metal SheetConfirm if neededNo
Main material of construction of the roof / cadjan/ Palmyrah/StrawConfirm if neededNo
Main material of construction of the roof / OtherConfirm if neededNo
Main material of construction of the roof / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for floor construction at district level, 2024 · Population & Households

Existing form reference: 78b642444e82761a

FieldUnitRequired
DistrictConfirm if neededNo
Number of housing unitsConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / CementConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Terrazzo/Tile/Granite/Wood(finished)/TitaniumConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / ConcreteConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / MudConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / WoodConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / SandConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / OtherConfirm if neededNo
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by main source of drinking water at district level, 2024 · Population & Households

Existing form reference: ef0674489fe2bdc3

FieldUnitRequired
DistrictConfirm if neededNo
Number of householdsConfirm if neededNo
Main source of drinking water / Ground Water / Protected wellConfirm if neededNo
Main source of drinking water / Ground Water / Semi Protected wellConfirm if neededNo
Main source of drinking water / Ground Water / Unprotected wellConfirm if neededNo
Main source of drinking water / Ground Water / Tube WellConfirm if neededNo
Main source of drinking water / Ground Water / Spring/FountainConfirm if neededNo
Main source of drinking water / Pipe Borne water / National Water Supply &drainage boardConfirm if neededNo
Main source of drinking water / Pipe Borne water / Local AuthorityConfirm if neededNo
Main source of drinking water / Pipe Borne water / Community base OrganiziationConfirm if neededNo
Main source of drinking water / Pipe Borne water / Private Water Supply ProjectConfirm if neededNo
Main source of drinking water / Other / Tank/River/StreamsConfirm if neededNo
Main source of drinking water / Other / Rain WaterConfirm if neededNo
Main source of drinking water / Other / Bottled waterConfirm if neededNo
Main source of drinking water / Other / மீள் வடிகட்டல் ஆலை (R.O. Plant) Filter water(R.O.plant)Confirm if neededNo
Main source of drinking water / Other / BowserConfirm if neededNo
Main source of drinking water / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by Main Source of EnergyFuel Used for Cooking at District, 2024 · Population & Households

Existing form reference: 018e27b1cfd72a36

FieldUnitRequired
DistrictConfirm if neededNo
Number of householdsConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Fire woodConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / KeroseneConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / GasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / ElectricityConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy huskConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Bio gasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / OtherConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Not relaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by source of lighting at district level 2024 · Population & Households

Existing form reference: d3aec442e748e54b

FieldUnitRequired
DistrictConfirm if neededNo
Number of householdsConfirm if neededNo
Main type of lighting / Electricity - from National Grid / from rural electrification projectConfirm if neededNo
Main type of lighting / Kerosene lampConfirm if neededNo
Main type of lighting / Solar power (grid connected)Confirm if neededNo
Main type of lighting / Solar power (stand alone)Confirm if neededNo
Main type of lighting / Bio gasConfirm if neededNo
Main type of lighting / GeneratorConfirm if neededNo
Main type of lighting / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households using toilet facilities at district level 2024 · Population & Households

Existing form reference: 1776b9ac25ff6b34

FieldUnitRequired
DistrictConfirm if neededNo
Number of householdsConfirm if neededNo
Toilet facilities / Within the unit / Exclusively for the householdConfirm if neededNo
Toilet facilities / Within the unit / Sharing with another householdConfirm if neededNo
Toilet facilities / Outside the unit / Exclusively for the householdConfirm if neededNo
Toilet facilities / Outside the unit / Sharing with another householdConfirm if neededNo
Toilet facilities / Other / No toilet but sharing with another housing unit/ unitsConfirm if neededNo
Toilet facilities / Other / Common/ public toiletConfirm if neededNo
Toilet facilities / Other / Not using a toiletConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by housing unit structure at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: 512d4139dfc4438e

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of housing unitsConfirm if neededNo
Type of housing unit / Single house - Single storeyedConfirm if neededNo
Type of housing unit / Single house - two storeyedConfirm if neededNo
Type of housing unit / Single house - more than two storeyedConfirm if neededNo
Type of housing unit / Attached House - 1st FloorConfirm if neededNo
Type of housing unit / Attached House - 2nd FloorConfirm if neededNo
Type of housing unit / Attached House - 3rd or 4th FloorsConfirm if neededNo
Type of housing unit / Attached House - 5th to 10th FloorsConfirm if neededNo
Type of housing unit / Attached House - 11th to 19th FloorsConfirm if neededNo
Type of housing unit / Attached House - From 20th Floors or moreConfirm if neededNo
Type of housing unit / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for walls construction at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: 083d1e12fbf4e056

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of housing unitsConfirm if neededNo
Main material of construction of the wall / BrickConfirm if neededNo
Main material of construction of the wall / Cement blockConfirm if neededNo
Main material of construction of the wall / Granite/Cube stonesConfirm if neededNo
Main material of construction of the wall / CabookConfirm if neededNo
Main material of construction of the wall / Pressed soil bricksConfirm if neededNo
Main material of construction of the wall / Mud/WarichchiConfirm if neededNo
Main material of construction of the wall / Kadjan/ PalmyrahConfirm if neededNo
Main material of construction of the wall / Plank/ Metal Sheet/AsbestosConfirm if neededNo
Main material of construction of the wall / Zink Aluminium SheetsConfirm if neededNo
Main material of construction of the wall / OtherConfirm if neededNo
Main material of construction of the wall / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for roof construction at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: e1b26edc2e6a0e5e

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of housing unitsConfirm if neededNo
Main material of construction of the roof / TileConfirm if neededNo
Main material of construction of the roof / AsbestosConfirm if neededNo
Main material of construction of the roof / ConcreteConfirm if neededNo
Main material of construction of the roof / Zink Aluminium SheetConfirm if neededNo
Main material of construction of the roof / Metal SheetConfirm if neededNo
Main material of construction of the roof / cadjan/ Palmyrah/StrawConfirm if neededNo
Main material of construction of the roof / OtherConfirm if neededNo
Main material of construction of the roof / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Housing units by main material used for floor construction at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 9a5782101a90d9fe

FieldUnitRequired
DistrictConfirm if neededNo
Number of housing unitsConfirm if neededNo
Main material of construction of the floor / CementConfirm if neededNo
Main material of construction of the floor / Terrazzo/Tile/Granite/Wood(finished)/TitaniumConfirm if neededNo
Main material of construction of the floor / ConcreteConfirm if neededNo
Main material of construction of the floor / MudConfirm if neededNo
Main material of construction of the floor / WoodConfirm if neededNo
Main material of construction of the floor / SandConfirm if neededNo
Main material of construction of the floor / OtherConfirm if neededNo
Main material of construction of the floor / Not RelaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by Main Source of EnergyFuel Used for Cooking at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: dafbcc0869c20819

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of householdsConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Fire woodConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / KeroseneConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / GasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / ElectricityConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy huskConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Bio gasConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / OtherConfirm if neededNo
Main Source of Energy/Fuel Used for Cooking / Not relaventConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by main source of drinking water at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: ce89abd871f197b0

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of householdsConfirm if neededNo
Main source of drinking water / Ground Water / Protected wellConfirm if neededNo
Main source of drinking water / Ground Water / Semi Protected wellConfirm if neededNo
Main source of drinking water / Ground Water / Unprotected wellConfirm if neededNo
Main source of drinking water / Ground Water / Tube WellConfirm if neededNo
Main source of drinking water / Ground Water / Spring/FountainConfirm if neededNo
Main source of drinking water / Pipe Borne water / National Water Supply &drainage boardConfirm if neededNo
Main source of drinking water / Pipe Borne water / Local AuthorityConfirm if neededNo
Main source of drinking water / Pipe Borne water / Community base OrganiziationConfirm if neededNo
Main source of drinking water / Pipe Borne water / Private Water Supply ProjectConfirm if neededNo
Main source of drinking water / Other / Tank/River/StreamsConfirm if neededNo
Main source of drinking water / Other / Rain WaterConfirm if neededNo
Main source of drinking water / Other / Bottled waterConfirm if neededNo
Main source of drinking water / Other / மீள் வடிகட்டல் ஆலை (R.O. Plant) Filter water(R.O.plant)Confirm if neededNo
Main source of drinking water / Other / BowserConfirm if neededNo
Main source of drinking water / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households by source of lighting at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: bc8a342569a5c0ac

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of householdsConfirm if neededNo
Main type of lighting / Electricity - from National Grid / from rural electrification projectConfirm if neededNo
Main type of lighting / Kerosene lampConfirm if neededNo
Main type of lighting / Solar power (grid connected)Confirm if neededNo
Main type of lighting / Solar power (stand alone)Confirm if neededNo
Main type of lighting / Bio gasConfirm if neededNo
Main type of lighting / Rural water supply projectConfirm if neededNo
Main type of lighting / OtherConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm if neededNo
Households using toilet facilities at district level and divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 2dbde244619e1052

FieldUnitRequired
District and Divisional Secretary DivisionConfirm if neededNo
Number of householdsConfirm if neededNo
Toilet facilities / Within the unit / Exclusively for the householdConfirm if neededNo
Toilet facilities / Within the unit / Sharing with another householdConfirm if neededNo
Toilet facilities / Outside the unit / Exclusively for the householdConfirm if neededNo
Toilet facilities / Outside the unit / Sharing with another householdConfirm if neededNo
Toilet facilities / Other / No toilet but sharing with another housing unit/ unitsConfirm if neededNo
Toilet facilities / Other / Common/ public toiletConfirm if neededNo
Toilet facilities / Other / Not using a toiletConfirm if neededNo
Geography levelConfirm if neededNo
Measure basisConfirm if neededNo
Area labelConfirm if neededNo
Source rowConfirm 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.

Grama Niladhari Officers Documents and images prototype screen
Grama Niladhari Officers. 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.

Grama Niladhari Officers Data structure management prototype screen
Grama Niladhari Officers. 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.

Grama Niladhari Officers Users and access prototype screen
Grama Niladhari Officers. 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.