Divisional 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. Clear applications awaiting divisional administrative action 2. Address divisional services exceeding approved response targets 3. Prepare complete land cases for the competent authority 4. Compare village-development proposals 5. Schedule required inspections efficiently 6. Assign unresolved local complaints to accountable offices 7. Verify local works against approved scope 8. Prioritize maintenance referrals for local public assets 9. Allocate staff to service desks with capacity shortages 10. Track cases through responsible institutions to documented outcomes 11. Route an Aswesuma case to the correct appeal or objection process

1. Clear applications awaiting divisional administrative actionDEC-DP30-001 · Administrative applications

Try this decision

Identify divisional applications 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 — administrative applications / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — administrative applications / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — administrative applications / 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 does not establish eligibility or authorise a determination.

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: Application; current stage; received date; due date; missing documents; officer.

Calculation appendix

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

Your checks for this 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. Address divisional services exceeding approved response targetsDEC-DP30-002 · Service standards

Try this decision

Compare divisional case dates with the stated response target.

Validation required

Fictional default example · 2025.

Fictional case / area	Open days past due [days]	Calendar age [days]	Next check
Laggala Pallegama — service standards / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — service standards / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — service standards / 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

The supplied target must be confirmed; a delay does not establish its cause.

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: Service; receipt; completion; pauses; target; backlog; 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. Target reported local programme-support gapsDEC-DP30-003 · Programme gaps

Try this decision

Find target households without confirmed local programme support.

Validation required

Fictional default example · 2025.

Fictional case / area	Verified coverage [%]	Known uncovered [households]	Unknown coverage [households]	Next check
Laggala Pallegama — programme gaps / 2025	65	30	5	Check the records behind the uncovered and unknown groups
Rattota — programme gaps / 2025	85	15	0	Check the records behind the uncovered and unknown groups
Panvila — programme gaps / 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 entitlement, suitability or benefit.

Example chart

Verified coverage — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Required eligible frame	100	households
Distinct members of that frame covered	65	households
Frame members with unknown coverage	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 local units; needs; services received; programme; period.

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 incomplete village-level reportsDEC-DP30-004 · Grama Niladhari returns

Try this decision

Find missing or overdue village-level returns.

Validation required

Fictional default example · 2025.

Fictional case / area	Completeness [%]	Age of latest observation [days]	Missing observations [observations]	Next check
Laggala Pallegama — grama niladhari returns / 2025	80	2	6	Check overdue observation
Rattota — grama niladhari returns / 2025	80	2	6	Check overdue observation
Panvila — grama niladhari returns / 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.

A recent return does not establish complete or accurate data.

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 report; GN area; reporting period; submitted evidence; approval; 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. Prepare complete land cases for the competent authorityDEC-DP30-005 · State-land referrals

Try this decision

Find missing land-case evidence before referral to the competent authority.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — state-land referrals / Laggala Pallegama	Parcel: Missing	Obtain the missing evidence listed below
Rattota — state-land referrals / Rattota	applicant: Missing	Obtain the missing evidence listed below
Panvila — state-land referrals / Panvila	rights evidence: Missing	Obtain the missing evidence listed below

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

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

Information still needed

Parcel: Missing

The prototype does not determine ownership, rights or allocation.

Inputs, method and sources

Supplied input	Value	Unit
Parcel	Missing
Parcel evidence reference	Not provided
applicant	Documented
applicant evidence reference	Sample Laggala Pallegama field register / 2025
rights evidence	Documented
rights evidence evidence reference	Sample Laggala Pallegama field register / 2025
survey	Documented
survey evidence reference	Sample Laggala Pallegama field register / 2025
current rules	Documented
current rules evidence reference	Sample Laggala Pallegama field register / 2025
objections	Documented
objections 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: Parcel; applicant; rights evidence; survey; current rules; objections.

Calculation appendix

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

Reference map image

Matale District location in Sri Lanka — published static reference map — **Reference map image — not live.** Matale District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks · CC BY-SA 3.0. Detail crop only; no features added. The example areas are supplied records, not measurements from this image.

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. Prioritize verified local relief needs and avoid duplicate claimsDEC-DP30-006 · Disaster relief

Try this decision

Check local relief records for matching recipients, purposes and periods.

Validation required

Fictional default example · 2025.

Fictional case / area	Overlapping days [days]	Next check
Laggala Pallegama — disaster relief / 2025	61	Review possible overlap
Rattota — disaster relief / 2025	61	Review possible overlap
Panvila — disaster relief / 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.

An overlapping period does not prove a duplicate claim or establish relief priority.

Inputs, method and sources

Supplied input	Value	Unit
Permitted recipient/service reference	Laggala Pallegama — disaster relief
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: Household ID; assessed loss; relief entitlement; previous support; period.

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. Route complete welfare cases to the responsible programmeDEC-DP30-007 · Social-service referrals

Try this decision

Find missing eligibility records before a welfare-programme referral.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — social-service referrals / Laggala Pallegama	Applicant evidence: Missing	Obtain the missing evidence listed below
Rattota — social-service referrals / Rattota	programme rules: Missing	Obtain the missing evidence listed below
Panvila — social-service referrals / Panvila	consent: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this social-service referrals 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

Applicant evidence: Missing

The example does not approve welfare or establish final entitlement.

Inputs, method and sources

Supplied input	Value	Unit
Applicant evidence	Missing
Applicant evidence evidence reference	Not provided
programme rules	Documented
programme rules evidence reference	Sample Laggala Pallegama field register / 2025
consent	Documented
consent evidence reference	Sample Laggala Pallegama field register / 2025
current support	Documented
current support evidence reference	Sample Laggala Pallegama field register / 2025
referral status	Documented
referral status 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: Applicant evidence; programme rules; consent; current support; referral status.

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. Identify document-verification gaps delaying certificatesDEC-DP30-008 · Certificate services

Try this decision

Find missing verification records that prevent a certificate referral.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — certificate services / Laggala Pallegama	Request: Missing	Obtain the missing evidence listed below
Rattota — certificate services / Rattota	required evidence: Missing	Obtain the missing evidence listed below
Panvila — certificate services / Panvila	verification: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this certificate services 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

Request: Missing

The prototype does not authenticate documents or issue a certificate.

Inputs, method and sources

Supplied input	Value	Unit
Request	Missing
Request evidence reference	Not provided
required evidence	Documented
required evidence evidence reference	Sample Laggala Pallegama field register / 2025
verification	Documented
verification evidence reference	Sample Laggala Pallegama field register / 2025
authorized issuer	Documented
authorized issuer evidence reference	Sample Laggala Pallegama field register / 2025
receipt	Documented
receipt evidence reference	Sample Laggala Pallegama field register / 2025
due date	Documented
due date 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: Request; required evidence; verification; authorized issuer; receipt; due date.

Calculation appendix

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

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. Compare village-development proposalsDEC-DP30-009 · Local development

Try this decision

Compare village-development proposals using needs, constraints and resources.

Validation required

Fictional default example · 2025.

Fictional case / area	Potential benefit · assumption	Resources and adverse effects	Supporting records / conditions	Next check
Community water-service repair / Laggala Pallegama	Repair the community water service.	Needs source, quality, condition, demand, rights and maintenance evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Village access improvement / Laggala Pallegama	Improve the stated village access.	Needs accessibility, land rights, engineering and upkeep evidence.	Records: Not provided; condition evidence: Not provided	Obtain the missing records before choosing
Local livelihood-support proposal / Laggala Pallegama	Support the proposed local livelihood activity.	Needs participant agreement, eligibility, skills, market and resource 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; beneficiaries; location; cost; safeguards; capacity; alternatives
Applicable conditions, what was checked and the supporting reference

A budget balance does not establish an agreed or suitable village 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 community water service.
Resource needs and adverse effects	Needs source, quality, condition, demand, rights 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.

A budget balance does not establish an agreed or suitable village priority.

Other required records: Needs; beneficiaries; location; cost; safeguards; capacity; alternatives.

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. Resolve local objections before administrative determinationDEC-DP30-010 · Community consultation

Try this decision

Follow up unresolved local objections and participation barriers.

Validation required

Fictional default example · 2025.

Fictional case / area	Unresolved issues [issues]	Response share [%]	Next check
Laggala Pallegama — community consultation / 2025	16	71.579	Obtain the missing evidence listed below
Rattota — community consultation / 2025	16	71.579	Obtain the missing evidence listed below
Panvila — community 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

A response percentage does not settle rights or establish consent.

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: Proposal; affected parties; consultation records; objections; conditions; 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.

Reference map image

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. Schedule required inspections efficientlyDEC-DP30-011 · Field inspections

Try this decision

Check inspection dates against staff windows, prerequisites and dependencies.

Validation required

Fictional default example · 2025.

Fictional case / area	Planned duration [days]	Resource hours remaining [hours]	Next check
Laggala Pallegama — field inspections / 2025	3	8	Resolve overlapping resource bookings
Rattota — field inspections / 2025	3	8	Resolve overlapping resource bookings
Panvila — field inspections / 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 assign an inspector or authorise access.

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: Case locations; due dates; travel routes; inspector skills; capacity.

Calculation appendix

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

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?

12. Reconcile approved assistance with disbursement evidenceDEC-DP30-012 · Financial assistance

Try this decision

Reconcile assistance needs, commitments, receipts and expenditure.

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 — financial assistance / 2025	850,000	1,010,000	440,000	Review unfunded need
Rattota — financial assistance / 2025	850,000	1,010,000	440,000	Review unfunded need
Panvila — financial assistance / 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.

An amount recorded as spent does not by itself establish beneficiary receipt.

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: Scheme; approved amount; commitments; paid amount; eligible costs; recipient.

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?

13. Identify underserved villages and eligible groupsDEC-DP30-013 · Service inclusion

Try this decision

Find target villages or households without confirmed service coverage.

Validation required

Fictional default example · 2025.

Fictional case / area	Verified coverage [%]	Known uncovered [households]	Unknown coverage [households]	Next check
Laggala Pallegama — service inclusion / 2025	65	30	5	Check the records behind the uncovered and unknown groups
Rattota — service inclusion / 2025	85	15	0	Check the records behind the uncovered and unknown groups
Panvila — service 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.

The supplied eligibility frame must be checked before inferring exclusion.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Required eligible frame	100	households
Distinct members of that frame covered	65	households
Frame members with unknown coverage	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: Eligibility frame; service use; geography; consented attributes; 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?

6. Assign unresolved local complaints to accountable officesDEC-DP30-014 · Citizen complaints

Try this decision

Identify unresolved local complaint cases past their response date.

Validation required

Fictional default example · 2025.

Fictional case / area	Open days past due [days]	Calendar age [days]	Next check
Laggala Pallegama — citizen complaints / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — citizen complaints / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — citizen complaints / 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 recipient or a completed response.

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: Complaint; jurisdiction; received date; response; due date; 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?

7. Verify local works against approved scopeDEC-DP30-015 · Project monitoring

Try this decision

Compare observed work quantities with the same approved scope and unit.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m of the stated drain repair]	Relative change [%]	Next check
Laggala Pallegama — project monitoring / 2025	-30	-6.667	Check the matching records and reasons for the difference
Rattota — project monitoring / 2025	0	0	Check the matching records and reasons for the difference
Panvila — project monitoring / 2025	-60	-13.333	Check the matching records and reasons for the difference

What the selected record shows. Difference: -30 m of the stated drain repair.

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 quantity difference does not establish quality, payment entitlement or acceptance.

Example chart

Inputs, method and sources

Supplied input	Value	Unit
Approved drain-repair length in this sample scope	450	m of the stated drain repair
Matching drain length with accepted inspection evidence	420	m of the stated drain repair

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

This fictional work example uses metres of a single stated drain-repair specification. It does not combine unequal work packages or grant acceptance.

Other required records: Work; target quantity; measured quantity; unit; date; acceptance.

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. Prioritize maintenance referrals for local public assetsDEC-DP30-016 · Public assets

Try this decision

Identify local-asset maintenance referrals 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 — public assets / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — public assets / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — public assets / 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 engineering urgency or repair 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: Asset ID; condition; users; risk; maintenance responsibility; repair estimate.

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. Resolve contradictory household and land recordsDEC-DP30-017 · Data reconciliation

Try this decision

Compare conflicting household or land descriptions and source meanings.

Validation required

Fictional default example · 2025.

Fictional case / area	Original record	Comparison record	Next check
Laggala Pallegama — data reconciliation / Laggala Pallegama	Permitted identifiers: primary register entry	Permitted identifiers: conflicting source return	Resolve source disagreement
Rattota — data reconciliation / Rattota	Permitted identifiers: primary register entry	Permitted identifiers: conflicting source return	Resolve source disagreement
Panvila — data reconciliation / Panvila	Permitted identifiers: primary register entry	Permitted identifiers: conflicting source return	Resolve source disagreement

What the selected record shows. The original record says “Permitted identifiers: primary register entry”; the comparison says “Permitted identifiers: conflicting source return”. Their matching meaning has not been established. Obtain the source definitions and supporting records before reconciling them.

Next step. Resolve source disagreement. Prepare source comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Matching labels do not establish the same person, household or parcel.

Inputs, method and sources

Supplied input	Value	Unit
Original source value/definition	Permitted identifiers: primary register entry
Comparison source value/definition	Permitted identifiers: conflicting source return
Original version	Sample version1
Comparison version	Sample version2
Do the two source records have documented matching meanings?	Unresolved

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

Other required records: Permitted identifiers; source records; dates; evidence; verification owner.

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. Allocate staff to service desks with capacity shortagesDEC-DP30-018 · Office workload

Try this decision

Compare service-desk workload with usable 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 — office workload / 2025	-15	135	Review capacity shortfall
Rattota — office workload / 2025	-15	135	Review capacity shortfall
Panvila — office workload / 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 does not establish competence or authorise a staff assignment.

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: Service demand; handling times; staff hours; skills; approved targets.

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?

19. Correct missing context in divisional statistical returnsDEC-DP30-019 · Local reporting

Try this decision

Find missing definitions, periods and source context in divisional returns.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — local reporting / Laggala Pallegama	Indicator: Missing	Obtain the missing evidence listed below
Rattota — local reporting / Rattota	source: Missing	Obtain the missing evidence listed below
Panvila — local reporting / Panvila	unit: Missing	Obtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this local reporting 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

Indicator: Missing

Metadata completeness does not establish statistical accuracy.

Inputs, method and sources

Supplied input	Value	Unit
Indicator	Missing
Indicator evidence reference	Not provided
source	Documented
source evidence reference	Sample Laggala Pallegama field register / 2025
unit	Documented
unit evidence reference	Sample Laggala Pallegama field register / 2025
geography	Documented
geography evidence reference	Sample Laggala Pallegama field register / 2025
period	Documented
period evidence reference	Sample Laggala Pallegama field register / 2025
reviewer	Documented
reviewer evidence reference	Sample Laggala Pallegama field register / 2025
revision	Documented
revision 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: Indicator; source; unit; geography; period; reviewer; revision.

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. Track cases through responsible institutions to documented outcomesDEC-DP30-020 · Referral completion

Try this decision

Track referrals through documented institutional response and outcome stages.

Validation required

Fictional default example · 2025.

Fictional case / area	Verified completion share [%]	Not verified complete [cases]	Original cases awaiting review [cases]	Reviewed cases not confirmed complete [cases]	Next check
Laggala Pallegama — referral completion / 2025	53.333	84	48	36	Check the original cases that have not reached a verified outcome
Rattota — referral completion / 2025	53.333	84	48	36	Check the original cases that have not reached a verified outcome
Panvila — referral completion / 2025	53.333	84	48	36	Check the original cases that have not reached a verified outcome

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

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

A completed stage does not establish formal acceptance or a beneficial outcome.

Inputs, method and sources

Supplied input	Value	Unit
Distinct original divisional service area in the stated cohort	180	cases
Those original cohort members with documented review	132	cases
Those reviewed members meeting the stated completion definition	96	cases
Original cohort members whose follow-up is unknown	12	cases

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

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

Other required records: Referral ID; receiving agency; acceptance; response; action; closure 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?

11. Route an Aswesuma case to the correct appeal or objection processDEC-DP30-021 · Published method

Try this decision

Source. Sri Lanka publication.

Data needed. Existing Aswesuma application reference, issue type, submission date and supporting information.

Method. Distinguish an applicant’s appeal from an objection using the current Welfare Benefits Board forms and instructions.

Worked example. An applicant disputes the decision on their own Aswesuma application. Check the current instructions and route the case to the appeal form.

Next step. Send the case through the published route or ask for the missing information needed to submit it.

Welfare Benefits Board, Forms. Aswesuma appeal and objection forms and supporting instructions.

Confirm the active filing period, applicable forms, identity verification and authorized access.

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 Divisional Secretariats See the presentation example

Divisional Secretariats Documents and images prototype screen — Divisional 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 Divisional Secretariats See the presentation example

Divisional Secretariats Data structure management prototype screen — Divisional 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 Divisional Secretariats See the presentation example

Divisional Secretariats Users and access prototype screen — Divisional 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.

Divisional 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?