Survey Department

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. Select the authoritative survey edition for a case 2. Compare registered and surveyed area records 3. Check terrain evidence before site survey 4. Prioritize features needing ground verification 5. Follow up pending cadastral survey requests 6. Schedule geodetic control inspection and restoration 7. Review supplied coordinate-check residuals 8. Review survey accuracy-test results 9. Schedule aerial imagery for priority mapping gaps 10. Review unresolved boundary-evidence issues 11. Compare reported map-feature changes 12. Check required access and survey approvals 13. Select elevation datasets fit for intended analysis 14. Check boundary re-establishment evidence 15. Balance crew instrument and travel requirements 16. Track survey products through independent checking 17. Check parcel identifiers across sources 18. Compare costs for equivalent survey work types 19. Clear delayed requests for permitted map products 20. Retain superseded survey editions with traceable revisions

1. Select the authoritative survey edition for a caseDEC-DP14-001 · Boundary selection

Try this decision

Check edition, authority, scale and source evidence for a survey record.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — boundary selection / Laggala Pallegama	Boundary ID: Missing	Obtain the missing evidence listed below
Rattota — boundary selection / Rattota	legal source: Missing	Obtain the missing evidence listed below
Panvila — boundary selection / Panvila	survey date: Missing	Obtain the missing evidence listed below

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

Boundary ID: Missing

A catalogue label alone does not establish the legally applicable survey.

Inputs, method and sources

Supplied input	Value	Unit
Boundary ID	Missing
Boundary ID evidence reference	Not provided
legal source	Documented
legal source evidence reference	Sample Laggala Pallegama field register / 2025
survey date	Documented
survey date evidence reference	Sample Laggala Pallegama field register / 2025
scale	Documented
scale evidence reference	Sample Laggala Pallegama field register / 2025
supersession	Documented
supersession evidence reference	Sample Laggala Pallegama field register / 2025
intended use	Documented
intended use 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: Boundary ID; legal source; survey date; scale; supersession; intended use.

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. Compare registered and surveyed area recordsDEC-DP14-002 · Parcel reconciliation

Try this decision

Compare supplied registered and surveyed areas with matching definitions.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [ha]	Relative change [%]	Next check
Laggala Pallegama — parcel reconciliation / 2025	-10	-10	Reconcile the original records using their source references
Rattota — parcel reconciliation / 2025	5	5	Reconcile the original records using their source references
Panvila — parcel reconciliation / 2025	-2	-2	Reconcile the original records using their source references

What the selected record shows. Difference: -10 ha.

Next step. Reconcile the original records using their source references. Prepare source comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A difference does not settle a boundary or identify the correct area.

Inputs, method and sources

Supplied input	Value	Unit
Original source measurement	100	ha
Independent comparison measurement	90	ha
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable ha measure; same input scope

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

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

Other required records: Parcel ID; registered hectares; surveyed geometry; accuracy; edition; 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?

3. Check terrain evidence before site surveyDEC-DP14-003 · Terrain screening

Try this decision

Check reported terrain overlap and source evidence before detailed site survey.

Validation required

Fictional default example · 2025.

Fictional case / area	Overlap share [%]	Overlapping area [ha]	Next check
Laggala Pallegama — terrain screening / 2025	24	18	Check the matching footprint, source boundary and applicable conditions
Rattota — terrain screening / 2025	24	18	Check the matching footprint, source boundary and applicable conditions
Panvila — terrain screening / 2025	24	18	Check the matching footprint, source boundary and applicable conditions

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

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

The prototype does not process terrain or select a safe development site.

Inputs, method and sources

Supplied input	Value	Unit
Assessed footprint or frame	75	ha
Reported common overlap, counted once	18	ha
Boundary edition	Sample boundary1
Constraint definition	Sample constraint class
Matching source frame, boundary and period evidence	Provided
Area/count source and matching definition reference	Fictional matched survey return / edition 1

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

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

Other required records: Elevation model; resolution; slope; proposed footprint; accuracy; constraints.

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?

4. Prioritize features needing ground verificationDEC-DP14-004 · Field verification

Try this decision

Check feature records requiring ground-verification evidence.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — field verification / Laggala Pallegama	Feature ID: Missing	Obtain the missing evidence listed below
Rattota — field verification / Rattota	source date: Missing	Obtain the missing evidence listed below
Panvila — field verification / Panvila	positional uncertainty: Missing	Obtain the missing evidence listed below

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

Feature ID: Missing

The record does not establish that a mapped feature is wrong.

Inputs, method and sources

Supplied input	Value	Unit
Feature ID	Missing
Feature ID evidence reference	Not provided
source date	Documented
source date evidence reference	Sample Laggala Pallegama field register / 2025
positional uncertainty	Documented
positional uncertainty evidence reference	Sample Laggala Pallegama field register / 2025
reported mismatch	Documented
reported mismatch evidence reference	Sample Laggala Pallegama field register / 2025
survey request	Documented
survey request 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: Feature ID; source date; positional uncertainty; reported mismatch; survey request.

Calculation appendix

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

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

5. Follow up pending cadastral survey requestsDEC-DP14-005 · Cadastral backlog

Try this decision

Identify cadastral survey requests 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 — cadastral backlog / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — cadastral backlog / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — cadastral backlog / 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

Days overdue do not establish a legally adopted survey priority.

Inputs, method and sources

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

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

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

Other required records: Request ID; receipt date; statutory priority; due date; dependencies; survey crew.

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. Schedule geodetic control inspection and restorationDEC-DP14-006 · Control network

Try this decision

Identify geodetic-control inspection or restoration cases needing follow-up.

Validation required

Fictional default example · 2025.

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

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: Control point; stability; last check; observed error; access; maintenance need.

Calculation appendix

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

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

7. Review supplied coordinate-check residualsDEC-DP14-007 · Coordinate transformation

Try this decision

Compare supplied expected and independently reproduced control residuals.

Validation required

Fictional default example · 2025.

Fictional case / area	Difference [m]	Relative change [%]	Next check
Laggala Pallegama — coordinate transformation / 2025	0.01	8.333	Investigate reproduction difference
Rattota — coordinate transformation / 2025	0	0	Difference within supplied tolerance
Panvila — coordinate transformation / 2025	0.03	25	Investigate reproduction difference

What the selected record shows. Difference: 0.01 m. Investigate reproduction difference.

Next step. Investigate reproduction difference. Prepare reproduction-check note in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The page does not execute a coordinate transformation or establish its fitness.

Inputs, method and sources

Supplied input	Value	Unit
Supplied expected control residual	0.12	m
Supplied independently reproduced residual	0.13	m
Original measurement unit	Sample matching unit
Comparison measurement unit	Sample matching unit
Compared measure and definition	Sample comparable m measure; same input scope
Documented absolute comparison tolerance	0.01	m
Expected input/method version	Sample input1 /method1
Reproduced input/method version	Sample input1 /method1
Original result creator	Preparation officer
Independent reproducer	Independent checking officer

Reproduced minus expected result, within an explicitly supplied absolute tolerance, using the same exact input/method versions and a separate checker. Retain originals, code, parameters and environment evidence.

No coordinate transformation is performed. This compares supplied scalar control-check results only.

Other required records: Source datum; target datum; transformation; control points; residual error; tolerance.

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?

8. Review survey accuracy-test resultsDEC-DP14-008 · Survey accuracy

Try this decision

Compare a reported survey residual with the stated specification and test details.

Validation required

Fictional default example · 2025.

Fictional case / area	Observed result	Supplied comparison bounds	Next check
Laggala Pallegama — survey accuracy / Laggala Pallegama	0.12 m	0 to 0.1 m	Obtain the missing evidence listed below
Rattota — survey accuracy / Rattota	0.108 m	0 to 0.1 m	Review the sample, analytical method and comparison basis
Panvila — survey accuracy / Panvila	0.06 m	0 to 0.1 m	Review the sample, analytical method and comparison basis

What the selected record shows. The supplied Reported horizontal position-error magnitude, not a signed coordinate residual result is 0.12 m. Its stated comparison range is 0 to 0.1 m. Outside example comparison bounds.

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

Exact sample and site reference
Sample observation date

An example bound is not an adopted accuracy standard.

Inputs, method and sources

Supplied input	Value	Unit
Parameter and applicable use	Reported horizontal position-error magnitude, not a signed coordinate residual
Measured result	0.12	m
Example lower comparison bound	0	m
Example upper comparison bound	0.1	m
Original and limit unit	m
Sampling and analytical method/version	Sample laboratory method
Limit source, version and use	Fictional comparison bounds; not a regulatory limit
Parameter, unit, use and averaging period match	Yes
Result is below a reporting/detection limit	No
Averaging interval, sampling depth or process basis	Sample stated sampling/averaging basis
Sample and site reference	Not provided
Sample observation date	Not provided

Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status.

Example bounds establish no compliance or diagnosis. Ambient, drinking-water, effluent, crop, food, air and noise standards are not interchangeable. A censored result is not an exact zero. Physical concentrations and magnitude measurements are non-negative. Signed raw instrument signals need laboratory interpretation; do not silently replace them with zero.

Other required records: Survey observations; closures; residuals; instrument calibration; approved accuracy class.

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. Schedule aerial imagery for priority mapping gapsDEC-DP14-009 · Aerial acquisition

Try this decision

Check imagery-task windows, resources, access and prerequisites.

Validation required

Fictional default example · 2025.

Fictional case / area	Planned duration [days]	Resource hours remaining [hours]	Next check
Laggala Pallegama — aerial acquisition / 2025	3	8	Resolve overlapping resource bookings
Rattota — aerial acquisition / 2025	3	8	Resolve overlapping resource bookings
Panvila — aerial acquisition / 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 schedule does not arrange a flight or authorise image acquisition.

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: Coverage area; resolution need; cloud season; permissions; platform; budget.

Calculation appendix

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

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

10. Review unresolved boundary-evidence issuesDEC-DP14-010 · Boundary disputes

Try this decision

Identify unresolved issues in conflicting boundary evidence.

Validation required

Fictional default example · 2025.

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

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

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

Information still needed

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

Response counts do not determine a legal boundary.

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: Parcel surveys; monument evidence; legal records; objections; survey editions.

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. Compare reported map-feature changesDEC-DP14-011 · Topographic updates

Try this decision

Compare reported feature-change and unknown-status counts by map sheet.

Validation required

Fictional default example · 2025.

Fictional case / area	Reported changed-feature share [%]	Features without a reported change [features]	Unknown change status [features]	Next check
Laggala Pallegama — topographic updates / 2025	7.5	905	20	Review the reported feature changes and survey evidence
Rattota — topographic updates / 2025	4	950	10	Review the reported feature changes and survey evidence
Panvila — topographic updates / 2025	12	850	30	Review the reported feature changes and survey evidence

What the selected record shows. 75 of 1,000 features have a reported change; 905 have no reported change; 20 have unknown change status.

Next step. Review the reported feature changes and survey evidence. Prepare coverage follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Counts alone do not establish the significance or priority of a change.

Example chart

Reported changed-feature share — fictional 2025 examples

Inputs, method and sources

Supplied input	Value	Unit
Features in the matching map-sheet frame	1,000	features
Features with a documented reported change	75	features
Features whose change status is unknown	20	features

Changed-feature share = 100 × documented changed features / matching feature frame. Unchanged-or-no-reported-change = frame − changed − unknown. No material-change threshold is inferred.

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

Other required records: Map sheets; dated imagery; change evidence; usage demand; survey 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. Check required access and survey approvalsDEC-DP14-012 · Survey permissions

Try this decision

Check access, survey and disclosure conditions before a formal review.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — survey permissions / Laggala Pallegama	Survey purpose: Missing	Obtain the missing evidence listed below
Rattota — survey permissions / Rattota	property access: Missing	Obtain the missing evidence listed below
Panvila — survey permissions / Panvila	permissions: Missing	Obtain the missing evidence listed below

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

Survey purpose: Missing

The prototype does not grant access or issue a survey approval.

Inputs, method and sources

Supplied input	Value	Unit
Survey purpose	Missing
Survey purpose evidence reference	Not provided
property access	Documented
property access evidence reference	Sample Laggala Pallegama field register / 2025
permissions	Documented
permissions evidence reference	Sample Laggala Pallegama field register / 2025
restrictions	Documented
restrictions evidence reference	Sample Laggala Pallegama field register / 2025
expiry	Documented
expiry evidence reference	Sample Laggala Pallegama field register / 2025
authority	Documented
authority evidence reference	Sample Laggala Pallegama field register / 2025

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

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

Other required records: Survey purpose; property access; permissions; restrictions; expiry; authority.

Calculation appendix

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

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

13. Select elevation datasets fit for intended analysisDEC-DP14-013 · Elevation products

Try this decision

Check elevation-data resolution, datum, source and quality for the intended use.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — elevation products / Laggala Pallegama	Resolution: Missing	Obtain the missing evidence listed below
Rattota — elevation products / Rattota	vertical datum: Missing	Obtain the missing evidence listed below
Panvila — elevation products / Panvila	accuracy: Missing	Obtain the missing evidence listed below

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

Resolution: Missing

Complete metadata do not establish fitness for a specific analysis.

Inputs, method and sources

Supplied input	Value	Unit
Resolution	Missing
Resolution evidence reference	Not provided
vertical datum	Documented
vertical datum evidence reference	Sample Laggala Pallegama field register / 2025
accuracy	Documented
accuracy evidence reference	Sample Laggala Pallegama field register / 2025
acquisition date	Documented
acquisition date evidence reference	Sample Laggala Pallegama field register / 2025
coverage	Documented
coverage evidence reference	Sample Laggala Pallegama field register / 2025
intended scale	Documented
intended scale 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: Resolution; vertical datum; accuracy; acquisition date; coverage; intended scale.

Calculation appendix

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

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

14. Check boundary re-establishment evidenceDEC-DP14-014 · Encroachment surveys

Try this decision

Check evidence for a boundary re-establishment request.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — encroachment surveys / Laggala Pallegama	Boundary identity and edition: Missing	Obtain the missing evidence listed below
Rattota — encroachment surveys / Rattota	Survey and legal source: Missing	Obtain the missing evidence listed below
Panvila — encroachment surveys / Panvila	Reason boundary confidence is inadequate: Missing	Obtain the missing evidence listed below

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

Boundary identity and edition: Missing

The prototype does not re-establish a boundary or change a parcel record.

Inputs, method and sources

Supplied input	Value	Unit
Boundary identity and edition	Missing
Boundary identity and edition evidence reference	Not provided
Survey and legal source	Documented
Survey and legal source evidence reference	Sample Laggala Pallegama field register / 2025
Reason boundary confidence is inadequate	Documented
Reason boundary confidence is inadequate evidence reference	Sample Laggala Pallegama field register / 2025
Control/mark condition	Documented
Control/mark condition evidence reference	Sample Laggala Pallegama field register / 2025
Conflicting source references	Documented
Conflicting source references evidence reference	Sample Laggala Pallegama field register / 2025
Required survey determination	Documented
Required survey determination evidence reference	Sample Laggala Pallegama field register / 2025
Matching source frame, boundary and period evidence	Provided
Area/count source and matching definition reference	Fictional matched survey return / edition 1

Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.

Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity. A static reference image does not verify these supplied measurements or boundaries.

Other required records: Boundary identity and edition; Survey and legal source; Reason boundary confidence is inadequate; Control/mark condition; Conflicting source references; Required survey determination.

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?

15. Balance crew instrument and travel requirementsDEC-DP14-015 · Survey resources

Try this decision

Compare survey workload with usable crew and instrument capacity.

Validation required

Fictional default example · 2025.

Fictional case / area	Usable capacity minus demand [crew days]	Usable capacity [crew days]	Next check
Laggala Pallegama — survey resources / 2025	-15	135	Review capacity shortfall
Rattota — survey resources / 2025	-15	135	Review capacity shortfall
Panvila — survey resources / 2025	-15	135	Review capacity shortfall

What the selected record shows. Usable capacity minus demand: -15 crew days. Review capacity shortfall.

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

Capacity alone does not establish skills, access or appointment authority.

Inputs, method and sources

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

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: Survey workload; skills; equipment; travel hours; available crew days.

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?

16. Track survey products through independent checkingDEC-DP14-016 · Map delivery

Try this decision

Check stages from survey preparation to independently checked output.

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 — map delivery / 2025	53.333	84	48	36	Check the original cases that have not reached a verified outcome
Rattota — map delivery / 2025	53.333	84	48	36	Check the original cases that have not reached a verified outcome
Panvila — map delivery / 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 product acceptance.

Inputs, method and sources

Supplied input	Value	Unit
Distinct original survey case 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: Request cohort; field completion; computation; checking; approval; delivery dates.

Calculation appendix

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

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

17. Check parcel identifiers across sourcesDEC-DP14-017 · Land information

Try this decision

Check parcel identifier definitions and source references before reconciliation.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — land information / Laggala Pallegama	Cadastral ID: Missing	Obtain the missing evidence listed below
Rattota — land information / Rattota	land-register ID: Missing	Obtain the missing evidence listed below
Panvila — land information / Panvila	geometry: Missing	Obtain the missing evidence listed below

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

Cadastral ID: Missing

A matching label does not establish the same legal parcel.

Inputs, method and sources

Supplied input	Value	Unit
Cadastral ID	Missing
Cadastral ID evidence reference	Not provided
land-register ID	Documented
land-register ID evidence reference	Sample Laggala Pallegama field register / 2025
geometry	Documented
geometry evidence reference	Sample Laggala Pallegama field register / 2025
legal evidence	Documented
legal evidence evidence reference	Sample Laggala Pallegama field register / 2025
source owner	Documented
source owner 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: Cadastral ID; land-register ID; geometry; legal evidence; source 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?

18. Compare costs for equivalent survey work typesDEC-DP14-018 · Survey cost

Try this decision

Compare costs for a defined equivalent survey work unit.

Validation required

Fictional default example · 2025.

Fictional case / area	Cost per matching unit [LKR/km surveyed]	Total cost [LKR]	Next check
Laggala Pallegama — survey cost / 2025	92,037.037	497,000	Review cost components and comparable verified outputs
Rattota — survey cost / 2025	92,037.037	497,000	Review cost components and comparable verified outputs
Panvila — survey cost / 2025	92,037.037	497,000	Review cost components and comparable verified outputs

What the selected record shows. The supplied costs total 497,000 LKR for 5.4 km surveyed. Cost per matching unit is 92,037.037 LKR/km surveyed.

Next step. Review cost components and comparable verified outputs. Prepare cost comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Lowest unit cost does not establish equivalent accuracy or deliverables.

Inputs, method and sources

Supplied input	Value	Unit
Labour cost	180,000	LKR
Material/input cost	255,000	LKR
Other non-overlapping cost	62,000	LKR
Kilometres of the same stated survey work class	5.4	km surveyed
Equivalent survey work/terrain class	Fictional boundary-line survey / comparable terrain and specification

Sum non-overlapping survey costs and divide by verified kilometres of the same survey work/terrain class. This does not compare unlike cadastral cases by an undefined survey count.

An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.

Other required records: Crew cost; travel; instrument cost; surveyed units; terrain class; 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?

19. Clear delayed requests for permitted map productsDEC-DP14-019 · Map distribution

Try this decision

Identify permitted map-product requests 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 — map distribution / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Rattota — map distribution / 2025	29	90	Follow up overdue case; confirm the missing condition evidence
Panvila — map distribution / 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 deadline does not override source rights or disclosure restrictions.

Inputs, method and sources

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

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

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

Other required records: Request; product edition; payment or exemption evidence; rights; 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?

20. Retain superseded survey editions with traceable revisionsDEC-DP14-020 · Historical integrity

Try this decision

Check edition and revision references when a survey is superseded.

Validation required

Fictional default example · 2025.

Fictional case / area	Information still needed	Next check
Laggala Pallegama — historical integrity / Laggala Pallegama	Current survey edition: Missing	Obtain the missing evidence listed below
Rattota — historical integrity / Rattota	Superseded edition references: Missing	Obtain the missing evidence listed below
Panvila — historical integrity / Panvila	Revision reason and effective version: Missing	Obtain the missing evidence listed below

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

Current survey edition: Missing

Old evidence must remain traceable; no authoritative edition is replaced here.

Inputs, method and sources

Supplied input	Value	Unit
Current survey edition	Missing
Current survey edition evidence reference	Not provided
Superseded edition references	Documented
Superseded edition references evidence reference	Sample Laggala Pallegama field register / 2025
Revision reason and effective version	Documented
Revision reason and effective version evidence reference	Sample Laggala Pallegama field register / 2025
Preserved original location	Documented
Preserved original location evidence reference	Sample Laggala Pallegama field register / 2025
Change history	Documented
Change history evidence reference	Sample Laggala Pallegama field register / 2025
Retention and access rules	Documented
Retention and access rules 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: Current survey edition; Superseded edition references; Revision reason and effective version; Preserved original location; Change history; Retention and access rules.

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. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Country Boundary · Geospatial Evidence

Existing form reference: 8731a23fc188dcb7

Field	Unit	Required
Country_Name	Confirm if needed	No
ISO Alpha 2 Code	Confirm if needed	No
ISO Alpha 3 Code	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Forest Boundary · Administrative & Planning Areas

Existing form reference: 4e74cc389edc2305

Field	Unit	Required
Forest Type	Confirm if needed	No
Forest Name	Confirm if needed	No
Range	Confirm if needed	No
Beat	Confirm if needed	No
Division	Confirm if needed	No
FA Division	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Area Final	Confirm if needed	No
District	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

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

Political · Administrative & Planning Areas

Existing form reference: b4321ffd8103c957

Field	Unit	Required

Planning Areas · Administrative & Planning Areas

Existing form reference: a216ede898036945

Field	Unit	Required

Statistical Areas · Administrative & Planning Areas

Existing form reference: b9addcdb23f83f55

Field	Unit	Required

Sensitive Areas · Administrative & Planning Areas

Existing form reference: 10fbe912859cef22

Field	Unit	Required
Area_Sq_KM	Confirm if needed	No
Area_New	Confirm if needed	No
DSD_Name	Confirm if needed	No
District_Name	Confirm if needed	No
Province_Name	Confirm if needed	No
ID	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Contours · Geospatial Evidence

Existing form reference: 93cc638735e23c72

Field	Unit	Required
Contour Type	Confirm if needed	No
Elevation	Confirm if needed	No
Creation Method	Confirm if needed	No
Year of Creation	Confirm if needed	No
Revision Method	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
st_length(shape)	Confirm if needed	No

SpotHeights · Geospatial Evidence

Existing form reference: 568cf4c5db707e09

Field	Unit	Required
Elevation_Meters	Confirm if needed	No
Creation_Method	Confirm if needed	No
Year_of_Creation	Confirm if needed	No
Description	Confirm if needed	No

Elevation Regime · Geospatial Evidence

Existing form reference: 5a55e896f86c8187

Field	Unit	Required
Contour	Confirm if needed	No
Elevation_Zone	Confirm if needed	No
Zone	Confirm if needed	No
Description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Place Name · Geospatial Evidence

Existing form reference: 66e6c6001ba803cc

Field	Unit	Required
Toponym Type	Confirm if needed	No
Toponym_Name	Confirm if needed	No
Creation_Method	Confirm if needed	No
Year_of_Creation	Confirm if needed	No
Revision_Method	Confirm if needed	No
Year_of_Revision	Confirm if needed	No
GFCODE	Confirm if needed	No

Post Office · Geospatial Evidence

Existing form reference: eb28b45421d1d6fd

Field	Unit	Required
Post Office Type	Confirm if needed	No
Name	Confirm if needed	No
Creation Method	Confirm if needed	No
Year of Creation	Confirm if needed	No
Revision Method	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Description	Confirm if needed	No
Building_ID	Confirm if needed	No

DEM_1m_Point_Cloud · Geospatial Evidence

Existing form reference: 0270f612b0cbab4a

Field	Unit	Required
point_x	Confirm if needed	No
point_y	Confirm if needed	No
point_z	Confirm if needed	No

Building_polygon_10k · Geospatial Evidence

Existing form reference: 806833baabf4f714

Field	Unit	Required
building_type	Confirm if needed	No
name	Confirm if needed	No
height	Confirm if needed	No
cid	Confirm if needed	No
frequency	Confirm if needed	No
mean_z	Confirm if needed	No
creation_method	Confirm if needed	No
year_of_creation	Confirm if needed	No
gfcode	Confirm if needed	No
building_id	Confirm if needed	No
revision_method	Confirm if needed	No
year_of_revision	Confirm if needed	No
description	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

Grama_Niladhari_Division_10K · Geospatial Evidence

Existing form reference: 426e426930d92ec8

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_10K · Geospatial Evidence

Existing form reference: 6571f8cc88a68adb

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_10K · Geospatial Evidence

Existing form reference: 3ce83bfecf52a582

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_10K · Geospatial Evidence

Existing form reference: 720aef694503f77e

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

TR_Transport_Pt · Geospatial Evidence

Existing form reference: 2dc5dd54789f82bb

Field	Unit	Required
Type of Transport point	Confirm if needed	No
Subtype of Transport pit	Confirm if needed	No
Name	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Transport point ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

TE_Terrain_Pt · Geospatial Evidence

Existing form reference: 689f43051866dc70

Field	Unit	Required
Elevation	Confirm if needed	No
Year of creation	Confirm if needed	No
Type of Terrain Point	Confirm if needed	No
GFCODE	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Year of Creation Source	Confirm if needed	No

HY_Hydro_Pt · Geospatial Evidence

Existing form reference: 13f33e0f07b724b6

Field	Unit	Required
Type of Hydro point	Confirm if needed	No
Subtype of Hydro point	Confirm if needed	No
Name	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro point ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

CO_Building_Pt · Geospatial Evidence

Existing form reference: def7cb4f5387db97

Field	Unit	Required
GFCODE	Confirm if needed	No
Building Category	Confirm if needed	No
Building Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Building ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

CA_Toponym_Pt · Geospatial Evidence

Existing form reference: 08f6677965be7c42

Field	Unit	Required
Type of Toponym	Confirm if needed	No
Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No

TE_Terrain_Li · Geospatial Evidence

Existing form reference: 64ee7dfa3baa634e

Field	Unit	Required
Type of Terrain line	Confirm if needed	No
Elevation	Confirm if needed	No
Year of Creation	Confirm if needed	No
TL_Cd_GFCODE	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
st_length(shape)	Confirm if needed	No

TR_Transport_Li · Geospatial Evidence

Existing form reference: 2c67d1c1e47ead9e

Field	Unit	Required
Type of Transport line	Confirm if needed	No
Name	Confirm if needed	No
Additional info	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Transport line ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Nmae	Confirm if needed	No
st_length(shape)	Confirm if needed	No

HY_Hydro_Li · Geospatial Evidence

Existing form reference: 46186cf703c41f7f

Field	Unit	Required
Type of Hydro line	Confirm if needed	No
Subtype of Hydro line	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro line ID	Confirm if needed	No
Name of Hydro Line	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CA_Grid_Li · Geospatial Evidence

Existing form reference: be817df34fd152ae

Field	Unit	Required
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
st_length(shape)	Confirm if needed	No

LU_Landuse_Pg · Geospatial Evidence

Existing form reference: e119f4245d3aec14

Field	Unit	Required
Landuse Classif 1	Confirm if needed	No
Landuse Classif 2	Confirm if needed	No
Method of creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
LU_Cd_GFCODE	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
Name	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

HY_Hydro_Pg · Geospatial Evidence

Existing form reference: a51bbdb82cc71cfa

Field	Unit	Required
Type of Hydro area	Confirm if needed	No
Name	Confirm if needed	No
Method of Creation	Confirm if needed	No
Year of Creation	Confirm if needed	No
Method of Revision	Confirm if needed	No
Year of Revision	Confirm if needed	No
GFCODE	Confirm if needed	No
Hydro area ID	Confirm if needed	No
Year of Revision Source	Confirm if needed	No
Year of Creation Source	Confirm if needed	No
GeoN_ID	Confirm if needed	No
GeoN_Code	Confirm if needed	No
Sinhala Name	Confirm if needed	No
Tamil Name	Confirm if needed	No
st_area(shape)	Confirm if needed	No
st_length(shape)	Confirm if needed	No

CA_Tile_Pg · Geospatial Evidence

Existing form reference: ce9ea4c4673574d0

Field	Unit	Required
Tile code	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

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 Survey Department See the presentation example

Survey Department Documents and images prototype screen — Survey Department. 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 Survey Department See the presentation example

Survey Department Data structure management prototype screen — Survey Department. 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 Survey Department See the presentation example

Survey Department Users and access prototype screen — Survey Department. 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.

Survey Department

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?