District Secretariats

Tell us what to change or add.

Your name (optional)Your roleReview date

Continue a saved review

1. Check a decision

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

2. Try the inputs

Use Change example to try different values. Use Data needed to check the fields and sources. The land-use change decision has its own comparison views.

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

3. Check each decision

1. Escalate overdue district project milestones 2. Prioritize aging district service requests 3. Compare district development priorities within resource limits 4. Allocate district response resources against verified needs 5. Target administrative support to overloaded divisions 6. Resolve inter-agency grievances with clear ownership 7. Schedule district procurements affecting critical works 8. Assess district programme outcomes with stated limitations 9. Resolve district reporting boundary and code mismatches 10. Review district projects where spending and physical progress diverge

1. Escalate overdue district project milestonesDEC-DP29-001 · District projects

Try this decision

Compare district milestone completion dates with the stated plan.

Validation required

Fictional default example · 2025.

Fictional case / area	Calendar date difference [days]	Next check
Laggala Pallegama — district projects / 2025	8	Check the matching records and reasons for the difference
Rattota — district projects / 2025	8	Check the matching records and reasons for the difference
Panvila — district projects / 2025	8	Check the matching records and reasons for the difference

What the selected record shows. Calendar date difference: 8 days.

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

A delay needs dependency and source checks before assigning a cause.

Inputs, method and sources

Supplied input	Value	Unit
Planned milestone/sowing date	2025-06-01
Observed completion/sowing date	2025-06-09

Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar.

Other required records: Project; approved milestone; actual progress; dependencies; funding; verification.

Calculation appendix

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

Your checks for this decisionDoes this decision belong to your institution?Is the required data list complete?Are the sources, places and time periods suitable?Can staff use the proposed entry or upload steps?Are the calculation, units and limits correct?Do the chart and result help you decide?Are the checking officer and decision authority correct?Are the access and sharing limits suitable?

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

2. Prioritize aging district service requestsDEC-DP29-002 · Citizen services

Try this decision

Identify district service requests past their recorded response date.

Validation required

Fictional default example · 2025.

Fictional case / area	Open days past due [days]	Calendar age [days]	Next check
Laggala Pallegama — citizen services / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — citizen services / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — citizen services / 2025	29	90	Follow up overdue case; confirm the missing condition evidence

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

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

Information still needed

Documented critical unresolved condition: Unknown

Age alone does not establish need or priority.

Inputs, method and sources

Supplied input	Value	Unit
Received or defect observed	2025-04-01
Recorded due date	2025-06-01
Assessment date	2025-06-30
Case/work closed	No
Documented critical unresolved condition	Unknown
Responsible office or maintainer	Proposed responsible office
Actual closure date when closed	Not provided

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

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

Other required records: Request; receipt; due date; responsible division; pauses; outcome.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

3. Coordinate investment in areas missing planned servicesDEC-DP29-003 · Intervention coverage

Try this decision

Find planned service catchments with no confirmed service and unknown status.

Validation required

Fictional default example · 2025.

Fictional case / area	Verified coverage [%]	Known uncovered [service catchments]	Unknown coverage [service catchments]	Next check
Laggala Pallegama — intervention coverage / 2025	60	3	1	Check the records behind the uncovered and unknown groups
Rattota — intervention coverage / 2025	80	2	0	Check the records behind the uncovered and unknown groups
Panvila — intervention coverage / 2025	40	4	2	Check the records behind the uncovered and unknown groups

What the selected record shows. 3 service catchments are known to be uncovered; 1 have unknown coverage. 60% are confirmed covered.

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

A catchment count does not establish population access or service quality.

Example chart

Verified coverage — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Defined service catchments in the programme frame	10	service catchments
Those catchments with the specified service	6	service catchments
Catchments whose service coverage is unknown	1	service catchments

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

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

Other required records: Eligible areas; service need; existing interventions; verified coverage; geography.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Follow up missing or outdated divisional returnsDEC-DP29-004 · District reporting

Try this decision

Find missing or overdue divisional returns.

Validation required

Fictional default example · 2025.

Fictional case / area	Completeness [%]	Age of latest observation [days]	Missing observations [observations]	Next check
Laggala Pallegama — district reporting / 2025	80	2	6	Check overdue observation
Rattota — district reporting / 2025	80	2	6	Check overdue observation
Panvila — district reporting / 2025	80	2	6	Check overdue observation

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

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

Timeliness does not establish the accuracy of a return.

Inputs, method and sources

Supplied input	Value	Unit
Expected observations in the window	30	observations
Distinct valid observations	24	observations
Latest valid observation	2025-06-28
Assessment date	2025-06-30
Required observation interval	1	days

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

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

Other required records: Required reports; reporting period; submissions; acceptance; source; deadline.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

3. Compare district development priorities within resource limitsDEC-DP29-005 · District planning

Try this decision

Compare district proposals using service needs, resources and constraints.

Validation required

Fictional default example · 2025.

Fictional case / area	Potential benefit · assumption	Resources and adverse effects	Supporting records / conditions	Next check
Repair an essential local service / Laggala Pallegama	Repair the stated essential service.	Needs condition, user need, rights, engineering and maintenance evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Improve a documented access gap / Laggala Pallegama	Address the documented access gap.	Needs accessibility, service demand, rights and feasible design evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Stage a livelihood-support programme / Laggala Pallegama	Stage the livelihood-support proposal.	Needs eligibility, market, capacity, safeguard and outcome evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing

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

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

Information still needed

Records needed: Needs; project options; costs; benefits; safeguards; dependencies; budget
Applicable conditions, what was checked and the supporting reference

Budget and descriptive benefits do not establish an approved development priority.

Inputs, method and sources

Supplied input	Value	Unit
Option cost	1,500,000	LKR
Available budget	1,800,000	LKR
Mandatory constraints	Met
Potential benefit and its evidence or assumption	Repair the stated essential service.
Resource needs and adverse effects	Needs condition, user need, rights, engineering and maintenance evidence.
Required records available for this option	Not provided
Reference for the required records	Not provided
Applicable conditions, check result and supporting reference	Not provided

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

Budget and descriptive benefits do not establish an approved development priority.

Other required records: Needs; project options; costs; benefits; safeguards; dependencies; budget.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

4. Allocate district response resources against verified needsDEC-DP29-006 · Disaster coordination

Try this decision

Compare usable district response resources with documented workload.

Validation required

Fictional default example · 2025.

Fictional case / area	Usable capacity minus demand [team hours]	Usable capacity [team hours]	Next check
Laggala Pallegama — disaster coordination / 2025	-15	135	Review capacity shortfall
Rattota — disaster coordination / 2025	-15	135	Review capacity shortfall
Panvila — disaster coordination / 2025	-15	135	Review capacity shortfall

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

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

Capacity does not establish skills, readiness or deployment authority.

Inputs, method and sources

Supplied input	Value	Unit
Demand in the selected period	150	team hours
Rated capacity for that period	180	team hours
Unavailable or restricted capacity	45	team hours

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

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

Other required records: Incident needs; teams; supplies; shelters; access; official priorities.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

7. Identify district activities without confirmed financingDEC-DP29-007 · Funding coordination

Try this decision

Reconcile district activity needs with confirmed financing.

Validation required

Fictional default example · 2025.

Fictional case / area	Unfunded need [LKR]	Committed but not disbursed [LKR]	Disbursed but not spent [LKR]	Next check
Laggala Pallegama — funding coordination / 2025	850,000	1,010,000	440,000	Review unfunded need
Rattota — funding coordination / 2025	850,000	1,010,000	440,000	Review unfunded need
Panvila — funding coordination / 2025	850,000	1,010,000	440,000	Review unfunded need

What the selected record shows. Unfunded need: 850,000 LKR. Review unfunded need.

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

A financing gap does not authorise a new commitment.

Inputs, method and sources

Supplied input	Value	Unit
Approved financing need	3,500,000	LKR
Confirmed commitments	2,650,000	LKR
Funds actually disbursed	1,640,000	LKR
Verified eligible expenditure	1,200,000	LKR

Unfunded = need − commitments. Undisbursed = commitments − disbursements. Unspent = disbursements − eligible spending.

Keep commitments, cash receipts, expenditure and verified physical outputs separate. Negative balances flag overcommitment or reconciliation; no automatic accounting adjustment.

Other required records: Approved plan; commitments; disbursements; expenditure; counterpart funding; scope.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

8. Resolve cross-agency land issues delaying public worksDEC-DP29-008 · Land coordination

Try this decision

Follow up unresolved land issues and participation barriers affecting works.

Validation required

Fictional default example · 2025.

Fictional case / area	Unresolved issues [issues]	Response share [%]	Next check
Laggala Pallegama — land coordination / 2025	16	71.579	Obtain the missing evidence listed below
Rattota — land coordination / 2025	16	71.579	Obtain the missing evidence listed below
Panvila — land coordination / 2025	16	71.579	Obtain the missing evidence listed below

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

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

Information still needed

Issue-register references for the 16 unresolved issues
Evidence about participation barriers

Response counts do not settle rights or permit works to begin.

Inputs, method and sources

Supplied input	Value	Unit
Distinct relevant people invited	95	people
People who responded	68	people
Unresolved issues	16	issues
Proposal/version being discussed	Sample proposal1
Required participation channels accessible	Unknown
Reference for unresolved issues and their progress	Not provided
Evidence about participation barriers	Not provided

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

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

Other required records: Parcels; project footprint; claims; agency responses; survey evidence; conditions.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

9. Compare service access across district communitiesDEC-DP29-009 · Infrastructure access

Try this decision

Compare supplied journeys and access conditions for district services.

Validation required

Fictional default example · 2025.

Fictional case / area	Supplied journey duration [minutes]	Capacity minus demand [units]	Next check
Laggala Pallegama — infrastructure access / 2025	65	3	Obtain the missing evidence listed below
Rattota — infrastructure access / 2025	65	3	Obtain the missing evidence listed below
Panvila — infrastructure access / 2025	65	3	Obtain the missing evidence listed below

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

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

Information still needed

Access, closures and operating conditions: Unresolved

The prototype calculates no route or population-wide accessibility result.

Inputs, method and sources

Supplied input	Value	Unit
Supplied journey distance from a documented route survey	24	km
Supplied journey duration; not calculated here	65	minutes
Usable vehicle/team capacity	18	units
Required capacity	15	units
Access, closures and operating conditions	Unresolved
Operating and service window	Sample operating window

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

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

Other required records: Settlements; facilities; roads; travel restrictions; service capacity; travel time.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

10. Review overlapping assistance across district programmesDEC-DP29-010 · Beneficiary overlap

Try this decision

Check potentially overlapping assistance for the same recipient, purpose and period.

Validation required

Fictional default example · 2025.

Fictional case / area	Overlapping days [days]	Next check
Laggala Pallegama — beneficiary overlap / 2025	61	Review possible overlap
Rattota — beneficiary overlap / 2025	61	Review possible overlap
Panvila — beneficiary overlap / 2025	61	Review possible overlap

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

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

Date overlap does not prove duplicate entitlement.

Inputs, method and sources

Supplied input	Value	Unit
Permitted recipient/service reference	Laggala Pallegama — beneficiary overlap
Support purpose	Sample seasonal input support
Earlier support period begins	2025-01-01
Earlier support period ends	2025-06-30
Other support period begins	2025-05-01
Other support period ends	2025-08-31
Same purpose and qualifying unit	Yes

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

Other required records: Recipient ID; programme; purpose; period; entitlement; shared-use permission.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

11. Escalate unresolved safeguards in district investmentsDEC-DP29-011 · Safeguard follow-up

Try this decision

Find missing safeguards evidence before a district-investment referral.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — safeguard follow-up / Laggala Pallegama	Project approval: Missing	Obtain the missing evidence listed below
Rattota — safeguard follow-up / Rattota	safeguard conditions: Missing	Obtain the missing evidence listed below
Panvila — safeguard follow-up / Panvila	inspections: Missing	Obtain the missing evidence listed below

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

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

Information still needed

Project approval: Missing

The example does not grant safeguard clearance or permission to proceed.

Inputs, method and sources

Supplied input	Value	Unit
Project approval	Missing
Project approval evidence reference	Not provided
safeguard conditions	Documented
safeguard conditions evidence reference	Sample Laggala Pallegama field register / 2025
inspections	Documented
inspections evidence reference	Sample Laggala Pallegama field register / 2025
affected groups	Documented
affected groups evidence reference	Sample Laggala Pallegama field register / 2025
due dates	Documented
due dates evidence reference	Sample Laggala Pallegama field register / 2025

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

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

Other required records: Project approval; safeguard conditions; inspections; affected groups; due dates.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

5. Target administrative support to overloaded divisionsDEC-DP29-012 · Divisional capacity

Try this decision

Compare divisional workload with usable administrative staff time.

Validation required

Fictional default example · 2025.

Fictional case / area	Usable capacity minus demand [staff hours]	Usable capacity [staff hours]	Next check
Laggala Pallegama — divisional capacity / 2025	-15	135	Review capacity shortfall
Rattota — divisional capacity / 2025	-15	135	Review capacity shortfall
Panvila — divisional capacity / 2025	-15	135	Review capacity shortfall

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

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

Capacity alone does not establish staff competence or a defensible transfer priority.

Inputs, method and sources

Supplied input	Value	Unit
Demand in the selected period	150	staff hours
Rated capacity for that period	180	staff hours
Unavailable or restricted capacity	45	staff hours

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

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

Other required records: Case volumes; processing time; staff availability; deadlines; complexity.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

6. Resolve inter-agency grievances with clear ownershipDEC-DP29-013 · District grievances

Try this decision

Identify inter-agency grievance cases past their recorded response date.

Validation required

Fictional default example · 2025.

Fictional case / area	Open days past due [days]	Calendar age [days]	Next check
Laggala Pallegama — district grievances / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — district grievances / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — district grievances / 2025	29	90	Follow up overdue case; confirm the missing condition evidence

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

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

Information still needed

Documented critical unresolved condition: Unknown

A proposed office is not an assigned owner or a resolved grievance.

Inputs, method and sources

Supplied input	Value	Unit
Received or defect observed	2025-04-01
Recorded due date	2025-06-01
Assessment date	2025-06-30
Case/work closed	No
Documented critical unresolved condition	Unknown
Responsible office or maintainer	Proposed responsible office
Actual closure date when closed	Not provided

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

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

Other required records: Case; involved agencies; response dates; jurisdiction; outstanding issues; escalation.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

14. Ensure affected groups are heard in district plansDEC-DP29-014 · Public consultation

Try this decision

Follow up unresolved planning comments and participation barriers.

Validation required

Fictional default example · 2025.

Fictional case / area	Unresolved issues [issues]	Response share [%]	Next check
Laggala Pallegama — public consultation / 2025	16	71.579	Obtain the missing evidence listed below
Rattota — public consultation / 2025	16	71.579	Obtain the missing evidence listed below
Panvila — public consultation / 2025	16	71.579	Obtain the missing evidence listed below

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

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

Information still needed

Issue-register references for the 16 unresolved issues
Evidence about participation barriers

Attendance and response rates do not establish agreement with a district plan.

Inputs, method and sources

Supplied input	Value	Unit
Distinct relevant people invited	95	people
People who responded	68	people
Unresolved issues	16	issues
Proposal/version being discussed	Sample proposal1
Required participation channels accessible	Unknown
Reference for unresolved issues and their progress	Not provided
Evidence about participation barriers	Not provided

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

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

Other required records: Plan version; stakeholder frame; participation; responses; unresolved concerns.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

15. Address documented exclusion from district servicesDEC-DP29-015 · Programme inclusion

Try this decision

Find target households without confirmed service access and unknown status.

Validation required

Fictional default example · 2025.

Fictional case / area	Verified coverage [%]	Known uncovered [households]	Unknown coverage [households]	Next check
Laggala Pallegama — programme inclusion / 2025	65	30	5	Check the records behind the uncovered and unknown groups
Rattota — programme inclusion / 2025	85	15	0	Check the records behind the uncovered and unknown groups
Panvila — programme inclusion / 2025	45	40	15	Check the records behind the uncovered and unknown groups

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

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

Coverage does not establish service quality, fairness or benefit.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Eligible households in the defined service frame	100	households
Those households with recorded access	65	households
Households whose access status is unknown	5	households

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

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

Other required records: Eligible population; unique service users; consented attributes; locations; unmet need.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

7. Schedule district procurements affecting critical worksDEC-DP29-016 · Procurement dependencies

Try this decision

Check procurement task dates against dependencies and resource windows.

Validation required

Fictional default example · 2025.

Fictional case / area	Planned duration [days]	Resource hours remaining [hours]	Next check
Laggala Pallegama — procurement dependencies / 2025	3	8	Resolve overlapping resource bookings
Rattota — procurement dependencies / 2025	3	8	Resolve overlapping resource bookings
Panvila — procurement dependencies / 2025	3	8	Resolve overlapping resource bookings

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

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

The example does not approve procurement, select a supplier or commit funds.

Inputs, method and sources

Supplied input	Value	Unit
Required resource	Watershed field team
Task start	2025-06-01
Task end	2025-06-04
Earliest permitted start	2025-05-28
Latest permitted finish	2025-06-08
Required resource effort	16	hours
Available resource effort	24	hours
Predecessor task reference	None
Mandatory permits and prerequisites	Met

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

Other required records: Package; approvals; lead time; dependencies; resource needs; delivery window.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

17. Verify ownership and maintenance of completed public assetsDEC-DP29-017 · Asset handover

Try this decision

Find missing ownership, handover and maintenance evidence for completed assets.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — asset handover / Laggala Pallegama	Asset: Missing	Obtain the missing evidence listed below
Rattota — asset handover / Rattota	acceptance evidence: Missing	Obtain the missing evidence listed below
Panvila — asset handover / Panvila	assigned owner: Missing	Obtain the missing evidence listed below

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

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

Information still needed

Asset: Missing

A completed work item does not establish operational acceptance.

Inputs, method and sources

Supplied input	Value	Unit
Asset	Missing
Asset evidence reference	Not provided
acceptance evidence	Documented
acceptance evidence evidence reference	Sample Laggala Pallegama field register / 2025
assigned owner	Documented
assigned owner evidence reference	Sample Laggala Pallegama field register / 2025
maintenance budget	Documented
maintenance budget evidence reference	Sample Laggala Pallegama field register / 2025
handover conditions	Documented
handover conditions evidence reference	Sample Laggala Pallegama field register / 2025

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

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

Other required records: Asset; acceptance evidence; assigned owner; maintenance budget; handover conditions.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

8. Assess district programme outcomes with stated limitationsDEC-DP29-018 · Outcome reporting

Try this decision

Compare district programme outcomes across the supplied groups and periods.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / area	Difference in changes [percentage points]	Next check
Laggala Pallegama — outcome reporting / 2025	10	Obtain the missing evidence listed below
Rattota — outcome reporting / 2025	10	Obtain the missing evidence listed below
Panvila — outcome reporting / 2025	10	Obtain the missing evidence listed below

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

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

Information still needed

Study design and evidence that the treatment and comparison records are comparable

A difference in changes does not establish programme impact.

Inputs, method and sources

Supplied input	Value	Unit
Intervention group households receiving the stated district programme service within the same window before	42	%
Intervention group households receiving the stated district programme service within the same window after	59	%
Comparison group households receiving the stated district programme service within the same window before	39	%
Comparison group households receiving the stated district programme service within the same window after	46	%
Study design and comparability evidence	Missing
Outcome definition, method and reference basis	Fictional measure: Households receiving the stated district programme service within the same window / matching frame, method and before-after windows

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

The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence. This named fictional indicator illustrates the calculation. Design evidence, adverse effects and attribution remain separate; a difference in changes does not establish causation.

Other required records: Baseline; follow-up; programme exposure; comparison; external conditions; uncertainty.

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

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

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

9. Resolve district reporting boundary and code mismatchesDEC-DP29-019 · Geographic consistency

Try this decision

Compare reporting boundary and code definitions before joining returns.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — geographic consistency / Laggala Pallegama	Source geography: Missing	Obtain the missing evidence listed below
Rattota — geographic consistency / Rattota	official code: Missing	Obtain the missing evidence listed below
Panvila — geographic consistency / Panvila	boundary edition: Missing	Obtain the missing evidence listed below

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

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

Information still needed

Source geography: Missing

Matching codes do not establish the same geographic extent.

Inputs, method and sources

Supplied input	Value	Unit
Source geography	Missing
Source geography evidence reference	Not provided
official code	Documented
official code evidence reference	Sample Laggala Pallegama field register / 2025
boundary edition	Documented
boundary edition evidence reference	Sample Laggala Pallegama field register / 2025
period	Documented
period evidence reference	Sample Laggala Pallegama field register / 2025
crosswalk evidence	Documented
crosswalk evidence evidence reference	Sample Laggala Pallegama field register / 2025

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

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

Other required records: Source geography; official code; boundary edition; period; crosswalk evidence.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

20. Close district coordination cases with unmet dependenciesDEC-DP29-020 · Inter-agency decisions

Try this decision

Find unmet dependencies before a coordination-case closure review.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — inter-agency decisions / Laggala Pallegama	Case and version: Missing	Obtain the missing evidence listed below
Rattota — inter-agency decisions / Rattota	Open inter-agency dependencies: Missing	Obtain the missing evidence listed below
Panvila — inter-agency decisions / Panvila	Responsible institutional roles: Missing	Obtain the missing evidence listed below

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

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

Information still needed

Case and version: Missing

A checklist does not establish that all agencies have accepted closure.

Inputs, method and sources

Supplied input	Value	Unit
Case and version	Missing
Case and version evidence reference	Not provided
Open inter-agency dependencies	Documented
Open inter-agency dependencies evidence reference	Sample Laggala Pallegama field register / 2025
Responsible institutional roles	Documented
Responsible institutional roles evidence reference	Sample Laggala Pallegama field register / 2025
Completion evidence	Documented
Completion evidence evidence reference	Sample Laggala Pallegama field register / 2025
Unresolved conditions	Documented
Unresolved conditions evidence reference	Sample Laggala Pallegama field register / 2025
Closure authority	Documented
Closure authority evidence reference	Sample Laggala Pallegama field register / 2025

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

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

Other required records: Case and version; Open inter-agency dependencies; Responsible institutional roles; Completion evidence; Unresolved conditions; Closure authority.

Calculation appendix

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

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

10. Review district projects where spending and physical progress divergeDEC-DP29-021 · Published method

Try this decision

Source. Sri Lanka publication.

Data needed. Approved budget, eligible expenditure, reporting date, physical milestone targets and verified quantities.

Method. Compare financial progress with physical progress as separate measures. Keep the financial denominator and the basis for physical completion visible.

Worked example. Eligible spending is LKR 2.4 million against a LKR 4 million budget, or 60%. Verified physical progress is 45%. Ask the project team to explain the 15 percentage-point gap.

Next step. Request site or financial verification when the two measures diverge materially.

National Audit Office, Financial Sector Modernization Project audit. §2.1, financial and physical progress reported separately.

Confirm the district reporting format, authorized budgets, progress weights and referral threshold.

What must change? Include corrected fields, rules, limits or words.Who supplies the data, who checks it, and who makes the decision?How often is this decision needed? What would make it urgent?

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

Field	Unit	Required
GND Name	Confirm if needed	No
GND Code	Confirm if needed	No
GND Number	Confirm if needed	No
GND Name Gazetted	Confirm if needed	No
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
MC UC PC Name	Confirm if needed	No
GND Officer Name	Confirm if needed	No
Dispute	Confirm if needed	No
Province Census Code	Confirm if needed	No
District Census Code	Confirm if needed	No
DS Division Census Code	Confirm if needed	No
GND Census Code	Confirm if needed	No
GND No Census	Confirm if needed	No
GND Name Census	Confirm if needed	No
Admin Code	Confirm if needed	No
CM Index	Confirm if needed	No
GND Number Gazetted	Confirm if needed	No
Year Created	Confirm if needed	No
Data Source	Confirm if needed	No
Method Of Creation	Confirm if needed	No
Extent	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Divisional Secretariat Boundary · Administrative & Planning Areas

Existing form reference: 38b3db2354e6f075

Field	Unit	Required
DS Division Name	Confirm if needed	No
DS Division Code	Confirm if needed	No
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

District Boundary · Administrative & Planning Areas

Existing form reference: 3e275a626091b924

Field	Unit	Required
District Name	Confirm if needed	No
District Code	Confirm if needed	No
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
Adjusted Area	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Province Boundary · Administrative & Planning Areas

Existing form reference: c2c98ee086137a9b

Field	Unit	Required
Province Name	Confirm if needed	No
Province Code	Confirm if needed	No
ISO Alpha 2 Code	Confirm if needed	No
Area True	Confirm if needed	No
Area Adjust	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Provinces · Administrative & Planning Areas

Existing form reference: 34b688f04ba12422

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No

Districts · Administrative & Planning Areas

Existing form reference: f25025b360be4121

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No
province DTO / id	Confirm if needed	No
province DTO / name	Confirm if needed	No
province DTO / code	Confirm if needed	No

Ds divisions · Administrative & Planning Areas

Existing form reference: b89e70ac83fb5930

Field	Unit	Required
id	Confirm if needed	No
code	Confirm if needed	No
name	Confirm if needed	No
district DTO / id	Confirm if needed	No
district DTO / name	Confirm if needed	No
district DTO / code	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No

Gn divisions · Administrative & Planning Areas

Existing form reference: 8f42b4909736031c

Field	Unit	Required
id	Confirm if needed	No
name	Confirm if needed	No
code	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
land Area	Confirm if needed	No
agricultural Land Area	Confirm if needed	No
non Agricultural Land Area	Confirm if needed	No
crop Area	Confirm if needed	No
agro Ecological Zone DTO / id	Confirm if needed	No
agro Ecological Zone DTO / ae Zone Id	Confirm if needed	No
agro Ecological Zone DTO / name	Confirm if needed	No
agro Ecological Zone DTO / average Rainfall	Confirm if needed	No
ai Regions DTO / id	Confirm if needed	No
ai Regions DTO / region Id	Confirm if needed	No
ai Regions DTO / description	Confirm if needed	No
ai Regions DTO / asc Region Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / province Segment Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / provincial Dd Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / pro Director Id	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / description	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / pro Director Level DTO / longitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / pro Deputy Director Level DTO / longitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / city	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / latitude	Confirm if needed	No
ai Regions DTO / provincial Ada Segment DTO / longitude	Confirm if needed	No
ds Division DTO / id	Confirm if needed	No
ds Division DTO / code	Confirm if needed	No
ds Division DTO / name	Confirm if needed	No
ds Division DTO / district DTO / id	Confirm if needed	No
ds Division DTO / district DTO / name	Confirm if needed	No
ds Division DTO / district DTO / code	Confirm if needed	No
ds Division DTO / district DTO / province DTO / id	Confirm if needed	No
ds Division DTO / district DTO / province DTO / name	Confirm if needed	No
ds Division DTO / district DTO / province DTO / code	Confirm if needed	No
arpa DTO / id	Confirm if needed	No
arpa DTO / arpa Id	Confirm if needed	No
arpa DTO / name	Confirm if needed	No
arpa DTO / asc Dto / id	Confirm if needed	No
arpa DTO / asc Dto / asc Id	Confirm if needed	No
arpa DTO / asc Dto / name	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / id	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / district Comm Id	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / name	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / do Agrarian Development DTO	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / created Date	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / modified Date	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / city	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / latitude	Confirm if needed	No
arpa DTO / asc Dto / district Commissioner Level DTO / longitude	Confirm if needed	No
arpa DTO / asc Dto / created Date	Confirm if needed	No
arpa DTO / asc Dto / modified Date	Confirm if needed	No
arpa DTO / asc Dto / city	Confirm if needed	No
arpa DTO / asc Dto / latitude	Confirm if needed	No
arpa DTO / asc Dto / longitude	Confirm if needed	No
arpa DTO / created Date	Confirm if needed	No
arpa DTO / modified Date	Confirm if needed	No
arpa DTO / city	Confirm if needed	No
arpa DTO / latitude	Confirm if needed	No
arpa DTO / longitude	Confirm if needed	No
gn Division Type	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / segment Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / description	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / dd Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / description	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / doa Id	Confirm if needed	No
ai Regions DTO / inter Provincial Ada Segment DTO / inter Province Deputy Director Level DTO / director Doa DTO / description	Confirm if needed	No
mahaweli Unit DTO / id	Confirm if needed	No
mahaweli Unit DTO / unit Id	Confirm if needed	No
mahaweli Unit DTO / description	Confirm if needed	No
ds Division DTO / district DTO / province DTO / created Date	Confirm if needed	No
ds Division DTO / district DTO / province DTO / modified Date	Confirm if needed	No
scs Sub Region Id	Confirm if needed	No
scs Sub Region Dto / id	Confirm if needed	No
scs Sub Region Dto / code	Confirm if needed	No
scs Sub Region Dto / description	Confirm if needed	No
scs Sub Region Dto / scs Region	Confirm if needed	No

Provincial director divisions · Administrative & Planning Areas

Existing form reference: 2337b92f31770ba9

Field	Unit	Required
id	Confirm if needed	No
pro Director Id	Confirm if needed	No
description	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Provincial deputy director level · Administrative & Planning Areas

Existing form reference: ca12c4d677b5003c

Field	Unit	Required
id	Confirm if needed	No
provincial Dd Id	Confirm if needed	No
description	Confirm if needed	No
pro Director Level DTO / id	Confirm if needed	No
pro Director Level DTO / pro Director Id	Confirm if needed	No
pro Director Level DTO / description	Confirm if needed	No
pro Director Level DTO / city	Confirm if needed	No
pro Director Level DTO / latitude	Confirm if needed	No
pro Director Level DTO / longitude	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Doa divisions · Administrative & Planning Areas

Existing form reference: eb2b3109790a85b0

Field	Unit	Required
id	Confirm if needed	No
doa Id	Confirm if needed	No
description	Confirm if needed	No

Inter-provincial ada divisions · Administrative & Planning Areas

Existing form reference: 3c4b7ca01eae2c96

Field	Unit	Required
id	Confirm if needed	No
segment Id	Confirm if needed	No
description	Confirm if needed	No
inter Province Deputy Director Level DTO / id	Confirm if needed	No
inter Province Deputy Director Level DTO / dd Id	Confirm if needed	No
inter Province Deputy Director Level DTO / description	Confirm if needed	No

Mahaweli authorities · Administrative & Planning Areas

Existing form reference: a928ea0c164539db

Field	Unit	Required
id	Confirm if needed	No
authority Id	Confirm if needed	No
description	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Mahaweli systems · Administrative & Planning Areas

Existing form reference: 8e71c080613ac3a4

Field	Unit	Required
id	Confirm if needed	No
system Id	Confirm if needed	No
description	Confirm if needed	No
mahaweli Authority DTO / id	Confirm if needed	No
mahaweli Authority DTO / authority Id	Confirm if needed	No
mahaweli Authority DTO / description	Confirm if needed	No
mahaweli Authority DTO / city	Confirm if needed	No
mahaweli Authority DTO / latitude	Confirm if needed	No
mahaweli Authority DTO / longitude	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Mahaweli blocks · Administrative & Planning Areas

Existing form reference: 1b6608ff1b096b55

Field	Unit	Required
id	Confirm if needed	No
code	Confirm if needed	No
mahaweli System DTO / id	Confirm if needed	No
mahaweli System DTO / system Id	Confirm if needed	No
mahaweli System DTO / description	Confirm if needed	No
mahaweli System DTO / mahaweli Authority DTO	Confirm if needed	No
mahaweli System DTO / city	Confirm if needed	No
mahaweli System DTO / latitude	Confirm if needed	No
mahaweli System DTO / longitude	Confirm if needed	No
description	Confirm if needed	No
land Area	Confirm if needed	No
cultivated Area	Confirm if needed	No
irrigated Area	Confirm if needed	No
non Irrigated Area	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
district DTO / id	Confirm if needed	No
district DTO / name	Confirm if needed	No
district DTO / code	Confirm if needed	No
ds Division DTO / id	Confirm if needed	No
ds Division DTO / code	Confirm if needed	No
ds Division DTO / name	Confirm if needed	No
ds Division DTO / created Date	Confirm if needed	No
ds Division DTO / modified Date	Confirm if needed	No

Mahaweli units · Administrative & Planning Areas

Existing form reference: b2dbe12695570d5c

Field	Unit	Required
id	Confirm if needed	No
unit Id	Confirm if needed	No
description	Confirm if needed	No
mahaweli Block DTO / id	Confirm if needed	No
mahaweli Block DTO / description	Confirm if needed	No
mahaweli Block DTO / land Area	Confirm if needed	No
mahaweli Block DTO / cultivated Area	Confirm if needed	No
mahaweli Block DTO / irrigated Area	Confirm if needed	No
mahaweli Block DTO / non Irrigated Area	Confirm if needed	No

Agrarian development divisions · Administrative & Planning Areas

Existing form reference: fc991a6c3bc249f6

Field	Unit	Required
id	Confirm if needed	No
do Agrarian Development Id	Confirm if needed	No
name	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

District commissioner divisions · Administrative & Planning Areas

Existing form reference: 57c890c642eab82c

Field	Unit	Required
id	Confirm if needed	No
district Comm Id	Confirm if needed	No
name	Confirm if needed	No
do Agrarian Development DTO / id	Confirm if needed	No
do Agrarian Development DTO / do Agrarian Development Id	Confirm if needed	No
do Agrarian Development DTO / name	Confirm if needed	No
do Agrarian Development DTO / created Date	Confirm if needed	No
do Agrarian Development DTO / modified Date	Confirm if needed	No
do Agrarian Development DTO / city	Confirm if needed	No
do Agrarian Development DTO / latitude	Confirm if needed	No
do Agrarian Development DTO / longitude	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Asc divisions · Administrative & Planning Areas

Existing form reference: 0bb5ed17e5cdc863

Field	Unit	Required
id	Confirm if needed	No
asc Id	Confirm if needed	No
name	Confirm if needed	No
district Commissioner Level DTO / id	Confirm if needed	No
district Commissioner Level DTO / district Comm Id	Confirm if needed	No
district Commissioner Level DTO / name	Confirm if needed	No
district Commissioner Level DTO / do Agrarian Development DTO	Confirm if needed	No
district Commissioner Level DTO / created Date	Confirm if needed	No
district Commissioner Level DTO / modified Date	Confirm if needed	No
district Commissioner Level DTO / city	Confirm if needed	No
district Commissioner Level DTO / latitude	Confirm if needed	No
district Commissioner Level DTO / longitude	Confirm if needed	No
created Date	Confirm if needed	No
modified Date	Confirm if needed	No
city	Confirm if needed	No
latitude	Confirm if needed	No
longitude	Confirm if needed	No

Population Information by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: 3758c98eb50413af

Field	Unit	Required
Province Code	Confirm if needed	No
Province Name	Confirm if needed	No
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DS_Division Code	Confirm if needed	No
DS_Division Name	Confirm if needed	No
GN_Division Code	Confirm if needed	No
GN_Division Name	Confirm if needed	No
GN_Division Number	Confirm if needed	No
Sex / Total	persons	No
Sex / Male	persons	No
Sex / Female	persons	No
Age_Group / Total	persons	No
Age_Group / 0 - 14	persons	No
Age_Group / 15 - 59	persons	No
Age_Group / 60 - 64	persons	No
Age_Group / 65 and above	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Occupied Housing Units by Grama Niladhari Division · Population & Households

Existing form reference: 8372d13713031913

Field	Unit	Required
Province Code	Confirm if needed	No
Province Name	Confirm if needed	No
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DS_Division Code	Confirm if needed	No
DS_Division Name	Confirm if needed	No
GN_Division Code	Confirm if needed	No
GN_Division Name	Confirm if needed	No
GN_Division Number	Confirm if needed	No
Occupied Housing Units	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Information on Occupied Housing Units by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: e7e1c2657503020f

Field	Unit	Required
Province Code	Confirm if needed	No
Province Name	Confirm if needed	No
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DS_Division Code	Confirm if needed	No
DS_Division Name	Confirm if needed	No
GN_Division Code	Confirm if needed	No
GN_Division Name	Confirm if needed	No
GN_Division Number	Confirm if needed	No
Occupied Housing Units	Confirm if needed	No
Type of Housing unit Structure / Single house - single storeyed	Confirm if needed	No
Type of Housing unit Structure / Single house - two storeyed	Confirm if needed	No
Type of Housing unit Structure / Single house - more than two storeyed	Confirm if needed	No
Type of Housing unit Structure / Attached house - 1st Floor	Confirm if needed	No
Type of Housing unit Structure / Attached house - 2nd Floor	Confirm if needed	No
Type of Housing unit Structure / Attached house - From 3 to 4 Floors	Confirm if needed	No
Type of Housing unit Structure / Attached house - From 5 to 10 Floors	Confirm if needed	No
Type of Housing unit Structure / Attached house - From 11to 19 Floors	Confirm if needed	No
Type of Housing unit Structure / Attached house - From 20 Floors or more	Confirm if needed	No
Type of Housing unit Structure / Other	Confirm if needed	No
Principal material of construction of the Walls / Bricks	Confirm if needed	No
Principal material of construction of the Walls / Cement block	Confirm if needed	No
Principal material of construction of the Walls / Granite/ Cube stones	Confirm if needed	No
Principal material of construction of the Walls / Cabook	Confirm if needed	No
Principal material of construction of the Walls / Pressed soil bricks	Confirm if needed	No
Principal material of construction of the Walls / Warichchi / Mud	Confirm if needed	No
Principal material of construction of the Walls / Cadjan/ Palmyrah	Confirm if needed	No
Principal material of construction of the Walls / Planks/ Metal Sheets/ Asbestos	Confirm if needed	No
Principal material of construction of the Walls / Zink Aluminium Sheets	Confirm if needed	No
Principal material of construction of the Walls / Other (specify)	Confirm if needed	No
Principal material of construction of the Walls / Not relavent	Confirm if needed	No
Principal material of construction of the Floor / Cement	Confirm if needed	No
Principal material of construction of the Floor / Terrazzo/Tile/Granite/Wood (Finished)	Confirm if needed	No
Principal material of construction of the Floor / Concrete	Confirm if needed	No
Principal material of construction of the Floor / Mud	Confirm if needed	No
Principal material of construction of the Floor / Wood	Confirm if needed	No
Principal material of construction of the Floor / Sand	Confirm if needed	No
Principal material of construction of the Floor / Other (specify)	Confirm if needed	No
Principal material of construction of the Floor / Not relavent	Confirm if needed	No
Principal material of construction of the Roof / Tile	Confirm if needed	No
Principal material of construction of the Roof / Asbestos	Confirm if needed	No
Principal material of construction of the Roof / Concrete	Confirm if needed	No
Principal material of construction of the Roof / Zink Aluminium Sheet	Confirm if needed	No
Principal material of construction of the Roof / Metal Sheet	Confirm if needed	No
Principal material of construction of the Roof / Cadjan/ Palmyrah/ Straw	Confirm if needed	No
Principal material of construction of the Roof / Other (specify)	Confirm if needed	No
Principal material of construction of the Roof / Not relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Household Information by Grama Niladhari Division, CPH-2024 · Population & Households

Existing form reference: da744a0cfc8f5c9f

Field	Unit	Required
Province Code	Confirm if needed	No
Province Name	Confirm if needed	No
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DS_Division Code	Confirm if needed	No
DS_Division Name	Confirm if needed	No
GN_Division Code	Confirm if needed	No
GN_Division Name	Confirm if needed	No
GN_Division Number	Confirm if needed	No
Number of Households	Confirm if needed	No
Main Source/way of drinking water / Ground Water / Protected well	Confirm if needed	No
Main Source/way of drinking water / Ground Water / Semi protected well	Confirm if needed	No
Main Source/way of drinking water / Ground Water / Unprotected well	Confirm if needed	No
Main Source/way of drinking water / Ground Water / Tube well	Confirm if needed	No
Main Source/way of drinking water / Ground Water / Spring/ Fountain	Confirm if needed	No
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - National water supply & drainage board	Confirm if needed	No
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Local Authority	Confirm if needed	No
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Community base organiziation	Confirm if needed	No
Main Source/way of drinking water / Pipe Borne water / Pipe borne water - Private water supply project	Confirm if needed	No
Main Source/way of drinking water / Other / Tank/ River/Streams	Confirm if needed	No
Main Source/way of drinking water / Other / Rain water	Confirm if needed	No
Main Source/way of drinking water / Other / Bottled water	Confirm if needed	No
Main Source/way of drinking water / Other / Filter water (R.O. Plant)	Confirm if needed	No
Main Source/way of drinking water / Other / Bowser	Confirm if needed	No
Main Source/way of drinking water / Other / Other (specify)	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Fire wood	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Kerosene	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Electricity	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy husk	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Bio gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Other (Specify bellow )	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Not relavent	Confirm if needed	No
Main source of Lighting / Electricity - from National grid/rural hydro power project	Confirm if needed	No
Main source of Lighting / Kerosene lamp	Confirm if needed	No
Main source of Lighting / Solar power (grid connected)	Confirm if needed	No
Main source of Lighting / Solar power (stand alone)	Confirm if needed	No
Main source of Lighting / Bio gas	Confirm if needed	No
Main source of Lighting / Generator	Confirm if needed	No
Main source of Lighting / Other (Specify bellow )	Confirm if needed	No
Toilet facilities / Within the unit / Within the housing unit - Exclusively for the household	Confirm if needed	No
Toilet facilities / Within the unit / Within the housing unit - Sharing with another household	Confirm if needed	No
Toilet facilities / Outside the unit / Within Premises - Exclusively for the household	Confirm if needed	No
Toilet facilities / Outside the unit / Within Premises - Sharing with another household	Confirm if needed	No
Toilet facilities / Other / No toilet but sharing with another housing unit/units	Confirm if needed	No
Toilet facilities / Other / Common/ Public toilet	Confirm if needed	No
Toilet facilities / Other / Not using a toilet (use jungle, beach and open ground)	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

GN Level Population by Ethnic Group, CPH 2024 · Population & Households

Existing form reference: e5112accd6912288

Field	Unit	Required
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DSD Code	Confirm if needed	No
DSD Name	persons	No
GND Code	Confirm if needed	No
GND Name	persons	No
Ethnic Group / Total	persons	No
Ethnic Group / Sinhalese	persons	No
Ethnic Group / Sri Lanka Tamil	persons	No
Ethnic Group / Indian Tamil/ Malaiyaga Thamilar	persons	No
Ethnic Group / Sri Lanka Moor/Muslim	persons	No
Ethnic Group / Burgher	persons	No
Ethnic Group / Malay	persons	No
Ethnic Group / Sri Lanka Chetty	persons	No
Ethnic Group / Bharatha	persons	No
Ethnic Group / Veddahs	persons	No
Ethnic Group / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

GN Level Population by Five Year Age Group, CPH 2024 · Population & Households

Existing form reference: bb924a4e93f0a33d

Field	Unit	Required
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DSD Code	Confirm if needed	No
DSD Name	persons	No
GND Code	Confirm if needed	No
GND Name	persons	No
Age Group / Total	persons	No
Age Group / 0 - 4	persons	No
Age Group / 5 - 9	persons	No
Age Group / 10-14	persons	No
Age Group / 15-19	persons	No
Age Group / 20-24	persons	No
Age Group / 25-29	persons	No
Age Group / 30-34	persons	No
Age Group / 35-39	persons	No
Age Group / 40-44	persons	No
Age Group / 45-49	persons	No
Age Group / 50-54	persons	No
Age Group / 55-59	persons	No
Age Group / 60-64	persons	No
Age Group / 65-69	persons	No
Age Group / 70-74	persons	No
Age Group / 75-79	persons	No
Age Group / 80-84	persons	No
Age Group / 85-89	persons	No
Age Group / 90-94	persons	No
Age Group / 95 and above	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

GN Level Population by Local Government Area, CPH 2024 · Population & Households

Existing form reference: 05d85f4e809f399c

Field	Unit	Required
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DSD Code	Confirm if needed	No
DSD Name	persons	No
GND Code	Confirm if needed	No
GND Name	persons	No
Sector / Total	persons	No
Sector / Municiple Council	persons	No
Sector / Urban Council	persons	No
Sector / Pradeshiya Sabha	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

GN Level Population by Religion, CPH 2024 · Population & Households

Existing form reference: 9fe44f410d52a912

Field	Unit	Required
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DSD Code	Confirm if needed	No
DSD Name	persons	No
GND Code	Confirm if needed	No
GND Name	persons	No
Religion / Total	persons	No
Religion / Buddhist	persons	No
Religion / Hindu	persons	No
Religion / Islam	persons	No
Religion / Roman Catholic	persons	No
Religion / Other Christian	persons	No
Religion / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

GN Level Population by Sector, CPH 2024 · Population & Households

Existing form reference: a96d28bdb2a7a507

Field	Unit	Required
District Code	Confirm if needed	No
District Name	Confirm if needed	No
DSD Code	Confirm if needed	No
DSD Name	persons	No
GND Code	Confirm if needed	No
GND Name	persons	No
Sector / Total	persons	No
Sector / Urban*	persons	No
Sector / Rural	persons	No
Sector / Estate Rural**	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by sex and age according to districts, 2024 · Population & Households

Existing form reference: e937770c5212a493

Field	Unit	Required
District	Confirm if needed	No
Total number of persons	persons	No
Sex / Male	persons	No
Sex / Female	persons	No
Age / Less than 15 years	persons	No
Age / 15 ‐ 59 Years	persons	No
Age / 60-64 Years	persons	No
Age / 65 years and over	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by ethnic group according to districts, 2024 · Population & Households

Existing form reference: 5830f8c01719d23d

Field	Unit	Required
District	Confirm if needed	No
Total number of persons	persons	No
Ethnic Group / Sinhalees	persons	No
Ethnic Group / Sri lanka Tamil	persons	No
Ethnic Group / Indian Tamil/ Malaiyaga Thamilar	persons	No
Ethnic Group / Sri Lanka Moor/Muslim	persons	No
Ethnic Group / Burgher	persons	No
Ethnic Group / Malay	persons	No
Ethnic Group / Sri Lanka Chetty	persons	No
Ethnic Group / Bharatha	persons	No
Ethnic Group / Veddhas	persons	No
Ethnic Group / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by religion according to districts, 2024 · Population & Households

Existing form reference: 596bd468dd17458f

Field	Unit	Required
District	Confirm if needed	No
Total number of persons	persons	No
Religion / Buddhist	persons	No
Religion / Hindu	persons	No
Religion / Islam	persons	No
Religion / Roman Catholic	persons	No
Religion / Other Christian	persons	No
Religion / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Migrant population by reason for migrating according to districts, 2024 · Population & Households

Existing form reference: 322c7e6af73ccfe3

Field	Unit	Required
District	Confirm if needed	No
Total migrant population	Confirm if needed	No
Main reason for migration / Marriage	Confirm if needed	No
Main reason for migration / Employment / Searching for a job	Confirm if needed	No
Main reason for migration / Education	Confirm if needed	No
Main reason for migration / Accompanied a family member	Confirm if needed	No
Main reason for migration / Returning for permanent	Confirm if needed	No
Main reason for migration / Development project	Confirm if needed	No
Main reason for migration / Resettled after displacement	Confirm if needed	No
Main reason for migration / A disaster / a displaced happened in the prior place	Confirm if needed	No
Main reason for migration / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by sex, age according to Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 010da3c91df400eb

Field	Unit	Required
District and Divisional Secretary's Division	Confirm if needed	No
Total number of persons	persons	No
Sex / Male	persons	No
Sex / Female	persons	No
Age / Less than 15 years	persons	No
Age / 15 ‐ 59 Years	persons	No
Age / 60-64 Years	persons	No
Age / 65 years and over	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by ethnicity according to Divisional SSecretariat Divisions, 2024 · Population & Households

Existing form reference: 7053ac00629aeff8

Field	Unit	Required
District and Divisional Secretary's Division	Confirm if needed	No
Total number of persons	persons	No
Ethnic Group / Sinhalees	persons	No
Ethnic Group / Sri lanka Tamil	persons	No
Ethnic Group / Indian Tamil/ Malaiyaga Thamilar	persons	No
Ethnic Group / Sri Lanka Moor/Muslim	persons	No
Ethnic Group / Burgher	persons	No
Ethnic Group / Malay	persons	No
Ethnic Group / Sri Lanka Chetty	persons	No
Ethnic Group / Bharatha	persons	No
Ethnic Group / Veddhas	persons	No
Ethnic Group / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Population by religion according to Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 36222798f483fabe

Field	Unit	Required
District and Divisional Secretary's Division	Confirm if needed	No
Total number of persons	persons	No
Religion / Buddhist	persons	No
Religion / Hindu	persons	No
Religion / Islam	persons	No
Religion / Roman Catholic	persons	No
Religion / Other Christian	persons	No
Religion / Other	persons	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by housing unit structure at district level 2024 · Population & Households

Existing form reference: a2103035c8ce0bac

Field	Unit	Required
District	Confirm if needed	No
Number of housing units	Confirm if needed	No
Structure of housing unit / Single house - Single storeyed	Confirm if needed	No
Structure of housing unit / Single house - Two storeyed	Confirm if needed	No
Structure of housing unit / Single house - more than two storeyed	Confirm if needed	No
Structure of housing unit / Attached House - 1st Floor	Confirm if needed	No
Structure of housing unit / Attached House - 2nd Floor	Confirm if needed	No
Structure of housing unit / Attached House - 3rd or 4th Floors	Confirm if needed	No
Structure of housing unit / Attached House - 5th to 10th Floors	Confirm if needed	No
Structure of housing unit / Attached House - 11th to 19th Floors	Confirm if needed	No
Structure of housing unit / Attached House - From 20th Floors or more	Confirm if needed	No
Structure of housing unit / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for walls construction at district level, 2024 · Population & Households

Existing form reference: 41eb1069e9c9c17d

Field	Unit	Required
District	Confirm if needed	No
Number of housing units	Confirm if needed	No
Main material of construction of the roof / Brick	Confirm if needed	No
Main material of construction of the roof / Cement block	Confirm if needed	No
Main material of construction of the roof / Granite/Cube stones	Confirm if needed	No
Main material of construction of the roof / Cabook	Confirm if needed	No
Main material of construction of the roof / Pressed soil bricks	Confirm if needed	No
Main material of construction of the roof / Mud/Warichchi	Confirm if needed	No
Main material of construction of the roof / Kadjan/ Palmyrah	Confirm if needed	No
Main material of construction of the roof / Plank/ Metal Sheet/Asbestos	Confirm if needed	No
Main material of construction of the roof / Zink Aluminium Sheets	Confirm if needed	No
Main material of construction of the roof / Other	Confirm if needed	No
Main material of construction of the roof / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for roof construction at district level, 2024 · Population & Households

Existing form reference: 74f863b697ebe277

Field	Unit	Required
District	Confirm if needed	No
Number of housing units	Confirm if needed	No
Main material of construction of the roof / Tile	Confirm if needed	No
Main material of construction of the roof / Asbestos	Confirm if needed	No
Main material of construction of the roof / Concrete	Confirm if needed	No
Main material of construction of the roof / Zink Aluminium Sheet	Confirm if needed	No
Main material of construction of the roof / Metal Sheet	Confirm if needed	No
Main material of construction of the roof / cadjan/ Palmyrah/Straw	Confirm if needed	No
Main material of construction of the roof / Other	Confirm if needed	No
Main material of construction of the roof / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for floor construction at district level, 2024 · Population & Households

Existing form reference: 78b642444e82761a

Field	Unit	Required
District	Confirm if needed	No
Number of housing units	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Cement	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Terrazzo/Tile/Granite/Wood(finished)/Titanium	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Concrete	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Mud	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Wood	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Sand	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Other	Confirm if needed	No
நிலம் அமைப்பதற்குப் பயன்படுத்தப்பட்டுள்ள பிரதான பொருட்கள் Main material of construction of the floor / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by main source of drinking water at district level, 2024 · Population & Households

Existing form reference: ef0674489fe2bdc3

Field	Unit	Required
District	Confirm if needed	No
Number of households	Confirm if needed	No
Main source of drinking water / Ground Water / Protected well	Confirm if needed	No
Main source of drinking water / Ground Water / Semi Protected well	Confirm if needed	No
Main source of drinking water / Ground Water / Unprotected well	Confirm if needed	No
Main source of drinking water / Ground Water / Tube Well	Confirm if needed	No
Main source of drinking water / Ground Water / Spring/Fountain	Confirm if needed	No
Main source of drinking water / Pipe Borne water / National Water Supply &drainage board	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Local Authority	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Community base Organiziation	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Private Water Supply Project	Confirm if needed	No
Main source of drinking water / Other / Tank/River/Streams	Confirm if needed	No
Main source of drinking water / Other / Rain Water	Confirm if needed	No
Main source of drinking water / Other / Bottled water	Confirm if needed	No
Main source of drinking water / Other / மீள் வடிகட்டல் ஆலை (R.O. Plant) Filter water(R.O.plant)	Confirm if needed	No
Main source of drinking water / Other / Bowser	Confirm if needed	No
Main source of drinking water / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by Main Source of EnergyFuel Used for Cooking at District, 2024 · Population & Households

Existing form reference: 018e27b1cfd72a36

Field	Unit	Required
District	Confirm if needed	No
Number of households	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Fire wood	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Kerosene	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Electricity	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy husk	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Bio gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Other	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Not relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by source of lighting at district level 2024 · Population & Households

Existing form reference: d3aec442e748e54b

Field	Unit	Required
District	Confirm if needed	No
Number of households	Confirm if needed	No
Main type of lighting / Electricity - from National Grid / from rural electrification project	Confirm if needed	No
Main type of lighting / Kerosene lamp	Confirm if needed	No
Main type of lighting / Solar power (grid connected)	Confirm if needed	No
Main type of lighting / Solar power (stand alone)	Confirm if needed	No
Main type of lighting / Bio gas	Confirm if needed	No
Main type of lighting / Generator	Confirm if needed	No
Main type of lighting / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households using toilet facilities at district level 2024 · Population & Households

Existing form reference: 1776b9ac25ff6b34

Field	Unit	Required
District	Confirm if needed	No
Number of households	Confirm if needed	No
Toilet facilities / Within the unit / Exclusively for the household	Confirm if needed	No
Toilet facilities / Within the unit / Sharing with another household	Confirm if needed	No
Toilet facilities / Outside the unit / Exclusively for the household	Confirm if needed	No
Toilet facilities / Outside the unit / Sharing with another household	Confirm if needed	No
Toilet facilities / Other / No toilet but sharing with another housing unit/ units	Confirm if needed	No
Toilet facilities / Other / Common/ public toilet	Confirm if needed	No
Toilet facilities / Other / Not using a toilet	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by housing unit structure at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: 512d4139dfc4438e

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of housing units	Confirm if needed	No
Type of housing unit / Single house - Single storeyed	Confirm if needed	No
Type of housing unit / Single house - two storeyed	Confirm if needed	No
Type of housing unit / Single house - more than two storeyed	Confirm if needed	No
Type of housing unit / Attached House - 1st Floor	Confirm if needed	No
Type of housing unit / Attached House - 2nd Floor	Confirm if needed	No
Type of housing unit / Attached House - 3rd or 4th Floors	Confirm if needed	No
Type of housing unit / Attached House - 5th to 10th Floors	Confirm if needed	No
Type of housing unit / Attached House - 11th to 19th Floors	Confirm if needed	No
Type of housing unit / Attached House - From 20th Floors or more	Confirm if needed	No
Type of housing unit / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for walls construction at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: 083d1e12fbf4e056

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of housing units	Confirm if needed	No
Main material of construction of the wall / Brick	Confirm if needed	No
Main material of construction of the wall / Cement block	Confirm if needed	No
Main material of construction of the wall / Granite/Cube stones	Confirm if needed	No
Main material of construction of the wall / Cabook	Confirm if needed	No
Main material of construction of the wall / Pressed soil bricks	Confirm if needed	No
Main material of construction of the wall / Mud/Warichchi	Confirm if needed	No
Main material of construction of the wall / Kadjan/ Palmyrah	Confirm if needed	No
Main material of construction of the wall / Plank/ Metal Sheet/Asbestos	Confirm if needed	No
Main material of construction of the wall / Zink Aluminium Sheets	Confirm if needed	No
Main material of construction of the wall / Other	Confirm if needed	No
Main material of construction of the wall / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for roof construction at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: e1b26edc2e6a0e5e

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of housing units	Confirm if needed	No
Main material of construction of the roof / Tile	Confirm if needed	No
Main material of construction of the roof / Asbestos	Confirm if needed	No
Main material of construction of the roof / Concrete	Confirm if needed	No
Main material of construction of the roof / Zink Aluminium Sheet	Confirm if needed	No
Main material of construction of the roof / Metal Sheet	Confirm if needed	No
Main material of construction of the roof / cadjan/ Palmyrah/Straw	Confirm if needed	No
Main material of construction of the roof / Other	Confirm if needed	No
Main material of construction of the roof / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Housing units by main material used for floor construction at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 9a5782101a90d9fe

Field	Unit	Required
District	Confirm if needed	No
Number of housing units	Confirm if needed	No
Main material of construction of the floor / Cement	Confirm if needed	No
Main material of construction of the floor / Terrazzo/Tile/Granite/Wood(finished)/Titanium	Confirm if needed	No
Main material of construction of the floor / Concrete	Confirm if needed	No
Main material of construction of the floor / Mud	Confirm if needed	No
Main material of construction of the floor / Wood	Confirm if needed	No
Main material of construction of the floor / Sand	Confirm if needed	No
Main material of construction of the floor / Other	Confirm if needed	No
Main material of construction of the floor / Not Relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by Main Source of EnergyFuel Used for Cooking at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: dafbcc0869c20819

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of households	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Fire wood	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Kerosene	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Electricity	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Saw dust/Paddy husk	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Bio gas	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Other	Confirm if needed	No
Main Source of Energy/Fuel Used for Cooking / Not relavent	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by main source of drinking water at district level and Divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: ce89abd871f197b0

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of households	Confirm if needed	No
Main source of drinking water / Ground Water / Protected well	Confirm if needed	No
Main source of drinking water / Ground Water / Semi Protected well	Confirm if needed	No
Main source of drinking water / Ground Water / Unprotected well	Confirm if needed	No
Main source of drinking water / Ground Water / Tube Well	Confirm if needed	No
Main source of drinking water / Ground Water / Spring/Fountain	Confirm if needed	No
Main source of drinking water / Pipe Borne water / National Water Supply &drainage board	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Local Authority	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Community base Organiziation	Confirm if needed	No
Main source of drinking water / Pipe Borne water / Private Water Supply Project	Confirm if needed	No
Main source of drinking water / Other / Tank/River/Streams	Confirm if needed	No
Main source of drinking water / Other / Rain Water	Confirm if needed	No
Main source of drinking water / Other / Bottled water	Confirm if needed	No
Main source of drinking water / Other / மீள் வடிகட்டல் ஆலை (R.O. Plant) Filter water(R.O.plant)	Confirm if needed	No
Main source of drinking water / Other / Bowser	Confirm if needed	No
Main source of drinking water / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households by source of lighting at district level and Divisional Secretariat Divisions , 2024 · Population & Households

Existing form reference: bc8a342569a5c0ac

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of households	Confirm if needed	No
Main type of lighting / Electricity - from National Grid / from rural electrification project	Confirm if needed	No
Main type of lighting / Kerosene lamp	Confirm if needed	No
Main type of lighting / Solar power (grid connected)	Confirm if needed	No
Main type of lighting / Solar power (stand alone)	Confirm if needed	No
Main type of lighting / Bio gas	Confirm if needed	No
Main type of lighting / Rural water supply project	Confirm if needed	No
Main type of lighting / Other	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

Households using toilet facilities at district level and divisional Secretariat Divisions, 2024 · Population & Households

Existing form reference: 2dbde244619e1052

Field	Unit	Required
District and Divisional Secretary Division	Confirm if needed	No
Number of households	Confirm if needed	No
Toilet facilities / Within the unit / Exclusively for the household	Confirm if needed	No
Toilet facilities / Within the unit / Sharing with another household	Confirm if needed	No
Toilet facilities / Outside the unit / Exclusively for the household	Confirm if needed	No
Toilet facilities / Outside the unit / Sharing with another household	Confirm if needed	No
Toilet facilities / Other / No toilet but sharing with another housing unit/ units	Confirm if needed	No
Toilet facilities / Other / Common/ public toilet	Confirm if needed	No
Toilet facilities / Other / Not using a toilet	Confirm if needed	No
Geography level	Confirm if needed	No
Measure basis	Confirm if needed	No
Area label	Confirm if needed	No
Source row	Confirm if needed	No

5. Documents and images

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

Open this screen for District Secretariats See the presentation example

District Secretariats Documents and images prototype screen — District Secretariats. Prototype screen. Select the image to enlarge it.

What you can try

Open Documents and images. Check the institution name.
Use All files, Documents or Images to find a file. Open its preview or download the original.
Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
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

Does a separate library for your institution meet your needs?Should new files start as Private for the permitted institution team?Should Public access require a review of the file and sharing permission?What documents and images will you store? Give the file types, usual sizes and need for earlier versions.Which job roles may add files, read Private files and approve Public files?Which files must stay Private? What permission, licence or expiry rule is needed for Public files?What else should change in this library?

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.

Open this screen for District Secretariats See the presentation example

District Secretariats Data structure management prototype screen — District Secretariats. Prototype screen. Select the image to enlarge it.

What you can try

Open Data structure and choose Manage structure.
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.
Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
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

Do the existing main topics and subject areas match your institution’s work?Should definition changes stay Draft until the responsible reviewer checks them?Is it right to reuse the same entity type or field when its meaning is the same?Which main topics, subject areas, entity types or fields should we add or change?Which units, choices, limits, decimal places and missing-value rules must each new field use?Which job roles may edit definitions and review them? Who owns each main information area?When a meaning, unit or calculation changes, what review and version history does your institution need?

7. Users and access

User management shows example profiles for each institution. People and Roles and access let you review the proposed account screens.

Open this screen for District Secretariats See the presentation example

District Secretariats Users and access prototype screen — District Secretariats. Prototype screen. Select the image to enlarge it.

What you can try

Open User management and choose the institution. The rows are examples, not a list of your staff.
Use View access to check a role. An administrator title alone does not give access to Private files.
Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
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

Do the proposed role names and responsibilities match your institution?Should access be limited to the assigned institution and the agreed dates?Should reading Private files need a separate permission, even for an administrator?Which job roles should view data, add files, review Public requests, edit definitions and manage users?Who should approve new access, set an end date or remove access when someone changes duties?Which user fields, roles or access checks are missing? Give role names rather than passwords or private account details.

9. Anything else we should change?

Which decisions or services are missing?Which forms or fields should change? Give the existing form reference where possible.What should change in the entry, checking, expert, map or report steps?Are the English, Sinhala and Tamil words clear? Give the screen name, current word and your suggested wording.Who should join the next review and what should happen next?

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.

District Secretariats

1. Check a decision

2. Try the inputs

3. Check each decision

4. Existing data forms for your institution

5. Documents and images

What you can try

What your institution needs to confirm

6. Data structure management

What you can try

What your institution needs to confirm

7. Users and access

What you can try

What your institution needs to confirm

8. Can you share data regularly?

9. Anything else we should change?