Land Commissioner General's Department

Tell us what to change or add.

1. Check a decision

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

2. Try the inputs

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

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

3. Check each decision

1. Choose what to handle first: unresolved state-land applicationsDEC-DP24-001 · Land applications · Suggested priority: High
Try this decision

Prioritize unresolved state-land applications.

Validation required

Open days past due — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Application ID; receipt date; case stage; due date; missing evidence; officer.

Fictional worked example · 2025

Laggala Pallegama — land applications · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
2. Schedule lease and permit reviews before due datesDEC-DP24-002 · Lease reviews · Suggested priority: High
Try this decision

Schedule lease and permit reviews before due dates.

Validation required

Planned duration — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Lease ID; expiry; conditions; review date; arrears; responsible office.

Fictional worked example · 2025

Laggala Pallegama — lease reviews · Laggala Pallegama

Input or resultValueUnit
Required resourceWatershed field team
Task start2025-06-01
Task end2025-06-04
Earliest permitted start2025-05-28
Latest permitted finish2025-06-08
Required resource effort16hours
Available resource effort24hours
Predecessor task referenceNone
Mandatory permits and prerequisitesMet
Planned duration3days
Resource hours remaining8hours

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
3. Target gaps in state-land record digitizationDEC-DP24-003 · Digitization · Suggested priority: Medium
Try this decision

Target gaps in state-land record digitization.

Validation required

Verified coverage — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Land-record frame; digitized records; verification status; geography; document type.

Fictional worked example · 2025

Laggala Pallegama — digitization · Laggala Pallegama

Input or resultValueUnit
Required eligible frame100records
Distinct members of that frame covered65records
Frame members with unknown coverage5records
Verified coverage65%
Known uncovered30records
Unknown coverage5records

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
4. Address delays in administrative land requestsDEC-DP24-004 · Processing performance · Suggested priority: Medium
Try this decision

Address delays in administrative land requests.

Validation required

Verified completion share — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Case timestamps; stage; pauses; approved targets; office; final outcome.

Fictional worked example · 2025

Laggala Pallegama — processing performance · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
5. Refer allocation cases with complete eligibility evidenceDEC-DP24-005 · Land allocation · Suggested priority: High
Try this decision

Refer allocation cases with complete eligibility evidence.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Applicant; Applicant evidence reference; parcel; parcel evidence reference; purpose; purpose evidence reference; current rules; current rules evidence reference; prior allocations; prior allocations evidence reference; documentary evidence; documentary evidence evidence reference

Other required evidence. Applicant; parcel; purpose; current rules; prior allocations; documentary evidence.

Fictional worked example · 2025

Laggala Pallegama — land allocation · Laggala Pallegama

Input or resultValueUnit
ApplicantMissing
Applicant evidence reference
parcelDocumented
parcel evidence referenceSample Laggala Pallegama field register / 2025
purposeDocumented
purpose evidence referenceSample Laggala Pallegama field register / 2025
current rulesDocumented
current rules evidence referenceSample Laggala Pallegama field register / 2025
prior allocationsDocumented
prior allocations evidence referenceSample Laggala Pallegama field register / 2025
documentary evidenceDocumented
documentary evidence evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
6. Resolve conflicting state-land parcel recordsDEC-DP24-006 · Boundary reconciliation · Suggested priority: High
Try this decision

Resolve conflicting state-land parcel records.

Validation required

Difference — fictional 2025 examples

Method. Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive.

Next step. Review evidence. Assign discrepancies to the custodian, accept documented corrections, or retain unresolved versions.

Inputs, example and sources

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

Analysis inputs. Original source measurement [ha]; Independent comparison measurement [ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition

Other required evidence. Parcel ID; survey plan; cadastral geometry; registered extent; edition.

Fictional worked example · 2025

Laggala Pallegama — boundary reconciliation · Laggala Pallegama

Input or resultValueUnit
Original source measurement100ha
Independent comparison measurement90ha
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable ha measure; same input scope
Difference-10ha
Relative change-10%

Keep both originals, units, scope, method, calibration and correction history. A difference does not identify which source is correct; no automatic averaging or overwrite.

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
7. Compare and correct differences in assessed rents collections and outstanding balancesDEC-DP24-007 · Lease revenue · Suggested priority: High
Try this decision

Reconcile assessed rents collections and outstanding balances.

Validation required

Calculated closing balance — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Lease; assessed rent; payments; adjustments; due dates; period; currency.

Fictional worked example · 2025

Laggala Pallegama — lease revenue · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
8. Choose what to handle first: overdue lease revenue casesDEC-DP24-008 · Arrears follow-up · Suggested priority: High
Try this decision

Prioritize overdue lease revenue cases.

Validation required

Open days past due — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Account; due date; outstanding amount; dispute status; approved recovery process.

Fictional worked example · 2025

Laggala Pallegama — arrears follow-up · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
9. Refer non-compliance with recorded land-use conditionsDEC-DP24-009 · Permit conditions · Suggested priority: High
Try this decision

Refer non-compliance with recorded land-use conditions.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Permit version; Permit version evidence reference; required use; required use evidence reference; inspection findings; inspection findings evidence reference; due dates; due dates evidence reference; evidence; evidence evidence reference; authority; authority evidence reference

Other required evidence. Permit version; required use; inspection findings; due dates; evidence; authority.

Fictional worked example · 2025

Laggala Pallegama — permit conditions · Laggala Pallegama

Input or resultValueUnit
Permit versionMissing
Permit version evidence reference
required useDocumented
required use evidence referenceSample Laggala Pallegama field register / 2025
inspection findingsDocumented
inspection findings evidence referenceSample Laggala Pallegama field register / 2025
due datesDocumented
due dates evidence referenceSample Laggala Pallegama field register / 2025
evidenceDocumented
evidence evidence referenceSample Laggala Pallegama field register / 2025
authorityDocumented
authority evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
10. Refer succession and transfer requests for determinationDEC-DP24-010 · Succession cases · Suggested priority: High
Try this decision

Refer succession and transfer requests for determination.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Permit; Permit evidence reference; applicant evidence; applicant evidence evidence reference; legal documents; legal documents evidence reference; claims; claims evidence reference; current rules; current rules evidence reference; objections; objections evidence reference

Other required evidence. Permit; applicant evidence; legal documents; claims; current rules; objections.

Fictional worked example · 2025

Laggala Pallegama — succession cases · Laggala Pallegama

Input or resultValueUnit
PermitMissing
Permit evidence reference
applicant evidenceDocumented
applicant evidence evidence referenceSample Laggala Pallegama field register / 2025
legal documentsDocumented
legal documents evidence referenceSample Laggala Pallegama field register / 2025
claimsDocumented
claims evidence referenceSample Laggala Pallegama field register / 2025
current rulesDocumented
current rules evidence referenceSample Laggala Pallegama field register / 2025
objectionsDocumented
objections evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
11. Compare suitable state parcels for public facilitiesDEC-DP24-011 · Public-purpose land · Suggested priority: High
Try this decision

Compare suitable state parcels for public facilities.

Validation required

Budget remaining after option — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Parcel availability; service need; constraints; access; tenure; costs; alternatives.

Fictional worked example · 2025

Record reconciliation · Laggala Pallegama

Input or resultValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Expected benefit and its evidenceCompare suitable state parcels for public facilities; Parcel availability and service need evidence needed
Resource needs and adverse effectsSample water, labour, access and safeguard trade-offs
Budget remaining after option300,000LKR

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
12. Resolve outstanding claims and objections before determinationDEC-DP24-012 · Land disputes · Suggested priority: High
Try this decision

Resolve outstanding claims and objections before determination.

Validation required

Response share — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Parcel; parties; claim evidence; consultation; hearing record; unresolved issues.

Fictional worked example · 2025

Laggala Pallegama — land disputes · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
13. Review allocation requests overlapping protected reservationsDEC-DP24-013 · Land reservations · Suggested priority: High
Try this decision

Review allocation requests overlapping protected reservations.

Validation required

Overlap share — fictional 2025 examples

Method. 100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once.

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

Inputs, example and sources

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

Analysis inputs. Proposal footprint [ha]; Union of overlapping constraint areas [ha]; Boundary edition; Constraint definition

Other required evidence. Proposed parcel; reservation geometry; legal edition; overlap; custodian evidence.

Fictional worked example · 2025

Laggala Pallegama — land reservations · Laggala Pallegama

Input or resultValueUnit
Proposal footprint75ha
Union of overlapping constraint areas18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Overlap share24%
Overlapping area18ha

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
14. Check documentation for inter-agency land transfersDEC-DP24-014 · Institutional handover · Suggested priority: Medium
Try this decision

Verify documentation for inter-agency land transfers.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Parcel; Parcel evidence reference; receiving agency; receiving agency evidence reference; authorization; authorization evidence reference; survey; survey evidence reference; conditions; conditions evidence reference; handover evidence; handover evidence evidence reference

Other required evidence. Parcel; receiving agency; authorization; survey; conditions; handover evidence.

Fictional worked example · 2025

Laggala Pallegama — institutional handover · Laggala Pallegama

Input or resultValueUnit
ParcelMissing
Parcel evidence reference
receiving agencyDocumented
receiving agency evidence referenceSample Laggala Pallegama field register / 2025
authorizationDocumented
authorization evidence referenceSample Laggala Pallegama field register / 2025
surveyDocumented
survey evidence referenceSample Laggala Pallegama field register / 2025
conditionsDocumented
conditions evidence referenceSample Laggala Pallegama field register / 2025
handover evidenceDocumented
handover evidence evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
15. Refer suspected unauthorized occupation for investigationDEC-DP24-015 · Unauthorized occupation · Suggested priority: High
Try this decision

Refer suspected unauthorized occupation for investigation.

Validation required

Unresolved equivalence items — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Occupation evidence; parcel; permit registry; date; survey uncertainty; authority.

Fictional worked example · 2025

Laggala Pallegama — unauthorized occupation · Laggala Pallegama

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
16. Request valuation updates where lease assessments are outdatedDEC-DP24-016 · Valuation review · Suggested priority: Medium
Try this decision

Request valuation updates where lease assessments are outdated.

Validation required

Open days past due — fictional 2025 examples

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

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

Inputs, example and sources

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

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

Other required evidence. Parcel; valuation date; reviewed rental basis; lease terms; review due date.

Fictional worked example · 2025

Laggala Pallegama — valuation review · Laggala Pallegama

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

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
17. Review whether allocated land serves approved purposesDEC-DP24-017 · Land-use effectiveness · Suggested priority: Medium
Try this decision

Review whether allocated land serves approved purposes.

Validation required

Difference — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Planned value [ha]; Observed value [ha]

Other required evidence. Allocation purpose; actual use; inspection date; outputs; conditions; history.

Fictional worked example · 2025

Laggala Pallegama — land-use effectiveness · Laggala Pallegama

Input or resultValueUnit
Planned value100ha
Observed value90ha
Difference-10ha
Relative change-10%

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
18. Determine permitted release of land and applicant informationDEC-DP24-018 · Record access · Suggested priority: High
Try this decision

Determine permitted release of land and applicant information.

Validation required

Evidence gaps — fictional 2025 examples

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

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

Inputs, example and sources

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

Analysis inputs. Requested fields; Requested fields evidence reference; purpose; purpose evidence reference; rights; rights evidence reference; classification; classification evidence reference; scope; scope evidence reference; approval; approval evidence reference; validity; validity evidence reference

Other required evidence. Requested fields; purpose; rights; classification; scope; approval; validity.

Fictional worked example · 2025

Laggala Pallegama — record access · Laggala Pallegama

Input or resultValueUnit
Requested fieldsMissing
Requested fields evidence reference
purposeDocumented
purpose evidence referenceSample Laggala Pallegama field register / 2025
rightsDocumented
rights evidence referenceSample Laggala Pallegama field register / 2025
classificationDocumented
classification evidence referenceSample Laggala Pallegama field register / 2025
scopeDocumented
scope evidence referenceSample Laggala Pallegama field register / 2025
approvalDocumented
approval evidence referenceSample Laggala Pallegama field register / 2025
validityDocumented
validity evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

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

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

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

Your checks for this decision
19. Correct missing references in electronic land filesDEC-DP24-019 · Document quality · Suggested priority: Lower
Try this decision

Correct missing references in electronic land files.

Validation required

Evidence gaps — fictional 2025 examples

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

Next step. Complete the evidence. Accept a fit source for a defined use, restrict it, or request metadata/schema correction.

Inputs, example and sources

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

Analysis inputs. Case ID; Case ID evidence reference; document type; document type evidence reference; survey reference; survey reference evidence reference; issuer; issuer evidence reference; date; date evidence reference; version; version evidence reference; authenticity; authenticity evidence reference

Other required evidence. Case ID; document type; survey reference; issuer; date; version; authenticity.

Fictional worked example · 2025

Laggala Pallegama — document quality · Laggala Pallegama

Input or resultValueUnit
Case IDMissing
Case ID evidence reference
document typeDocumented
document type evidence referenceSample Laggala Pallegama field register / 2025
survey referenceDocumented
survey reference evidence referenceSample Laggala Pallegama field register / 2025
issuerDocumented
issuer evidence referenceSample Laggala Pallegama field register / 2025
dateDocumented
date evidence referenceSample Laggala Pallegama field register / 2025
versionDocumented
version evidence referenceSample Laggala Pallegama field register / 2025
authenticityDocumented
authenticity evidence referenceSample Laggala Pallegama field register / 2025
Evidence gaps1items

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

After the action. Resolved interoperability issues and current verified metadata.

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

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

Your checks for this decision
20. Allocate case-processing capacity across land officesDEC-DP24-020 · Office capacity · Suggested priority: Medium
Try this decision

Allocate case-processing capacity across land offices.

Validation required

Usable capacity minus demand — fictional 2025 examples

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

Next step. Review capacity shortfall. Redistribute usable resources, propose expansion, or manage demand within authorized limits.

Inputs, example and sources

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

Analysis inputs. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours]

Other required evidence. Case backlog; complexity; handling time; staff availability; service deadlines.

Fictional worked example · 2025

Laggala Pallegama — office capacity · Laggala Pallegama

Input or resultValueUnit
Demand in the selected period150staff hours
Rated capacity for that period180staff hours
Unavailable or restricted capacity45staff hours
Usable capacity minus demand-15staff hours
Usable capacity135staff hours

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

Proposed checking role. State-land officer, legal/document reviewer and survey professional.

After the action. Actual usable capacity, unmet demand and service quality.

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

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

Your checks for this decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

District Boundary · Administrative & Planning Areas

Existing form reference: 3e275a626091b924

FieldUnitRequired
District NameConfirm if neededNo
District CodeConfirm if neededNo
Province NameConfirm if neededNo
Province CodeConfirm if neededNo
Adjusted AreaConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Landuse LUPPD 10K · Land Cover

Existing form reference: 30c67d24f5323223

FieldUnitRequired
Luse_CodeConfirm if neededNo
Main_CategoryConfirm if neededNo
Sub_CategoryConfirm if neededNo
Tank_NameConfirm if neededNo
Method_of_UpdationConfirm if neededNo
Year_of_UpdationConfirm if neededNo
Sheet_NoConfirm if neededNo
Road Right of ways · Geospatial Evidence

Existing form reference: b65e4609a48e9e05

FieldUnitRequired
Type_ROWConfirm if neededNo
Road_WidthConfirm if neededNo
Road WidthConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
GFCODEConfirm if neededNo
Transport_point_IDConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Parcel Fabrics · Geospatial Evidence

Existing form reference: 91738cf582575742

FieldUnitRequired
Parcel IDConfirm if neededNo
Parcel erConfirm if neededNo
Parcel stConfirm if neededNo
Parcel DateConfirm if neededNo
Parcel tpConfirm if neededNo
Parcel orConfirm if neededNo
Sheet IDConfirm if neededNo
Creation MethodConfirm if neededNo
Year of CreationConfirm if neededNo
Revision MethodConfirm if neededNo
Year of RevisionConfirm if neededNo
St AreaConfirm if neededNo
St LengthConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
typeConfirm if neededNo
pcl_id_covConfirm if neededNo
lot_noConfirm if neededNo
sht_id_conConfirm if neededNo
plan_noConfirm if neededNo
inset_noConfirm if neededNo
sup_noConfirm if neededNo
sheet_noConfirm if neededNo
di_nameConfirm if neededNo
ds_nameConfirm if neededNo
nameConfirm if neededNo
spcific_puConfirm if neededNo
tenure_actConfirm if neededNo
esri_oidConfirm if neededNo
SLTDA Parcels · Geospatial Evidence

Existing form reference: ca9e78effa85e080

FieldUnitRequired
Plot NumberConfirm if neededNo
DescriptionConfirm if neededNo
Area_Sq_MetersConfirm if neededNo
Present StatusConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Landuse · Geospatial Evidence

Existing form reference: c4b2b042a758c3f0

FieldUnitRequired
Landuse_Classification_1Confirm if neededNo
Landuse_Classification_2Confirm if neededNo
Classification2_CodeConfirm if neededNo
Creation_MethodConfirm if neededNo
Year_of_CreationConfirm if neededNo
Revision_MethodConfirm if neededNo
Year_of_RevisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo

5. Documents and images

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

Land Commissioner General's Department Documents and images prototype screen
Land Commissioner General's Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Documents and images. Check the institution name.
  2. Use All files, Documents or Images to find a file. Open its preview or download the original.
  3. Use a sample file to try Add file. Private is the starting choice. Public needs a source, permission to share and review.
  4. Use Access preview to try the institution reviewer and Public visitor views.

Files added in the prototype stay in this browser. Public sharing is an access preview. Existing public reference links already work online.

What your institution needs to confirm

6. Data structure management

Data structure keeps the existing source tree, records, charts and map. Manage structure adds a place to propose changes to definitions.

Land Commissioner General's Department Data structure management prototype screen
Land Commissioner General's Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open Data structure and choose Manage structure.
  2. Use Add base domain for a main information area. Add inside creates a subject area, a nested subject, an entity type or a field under the right parent.
  3. Give the definition a clear name, code and meaning. Reuse an existing definition when the meaning is the same.
  4. For a field, check the data type, unit, required value, limits and missing-value rule. Save a Draft, then try the separate reviewer view.

An entity type means a kind of thing or event, such as a reservoir or an inspection. Drafts stay in this browser. A demo approval does not change real definitions, data, chart links or sharing rights.

What your institution needs to confirm

7. Users and access

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

Land Commissioner General's Department Users and access prototype screen
Land Commissioner General's Department. Prototype screen. Select the image to enlarge it.

What you can try

  1. Open User management and choose the institution. The rows are examples, not a list of your staff.
  2. Use View access to check a role. An administrator title alone does not give access to Private files.
  3. Try Preview invitation or Preview access change. Check the role, start date, optional end date and reason.
  4. Review the example permissions and tell us which job roles should receive each one.

These are interface previews only. They create no account, send no email and change no access. Use example details in the preview. Institution verification does not grant a real permission.

What your institution needs to confirm

8. Can you share data regularly?

We currently use public data and published reports where available. Please confirm whether your institution can provide data directly, so we can avoid retyping or reading figures from PDFs.

Do not enter passwords, access keys or private account details.

9. Anything else we should change?

Use the Download answers button at the top of this page. Share the downloaded file or printed copy through your agreed review channel. Nothing is sent automatically.