National Building Research Organisation

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 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. Refer proposed sites overlapping landslide hazard zonesDEC-DP17-001 · Site clearance
Try this decision

Check reported development overlap with a cited landslide-hazard zone.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlap share [%]Overlapping area [ha]Next check
Laggala Pallegama — site clearance / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — site clearance / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — site clearance / 20252418Check 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.

A reported overlap supports referral; it does not establish site safety or permission.

Inputs, method and sources
Supplied inputValueUnit
Assessed footprint or frame75ha
Reported common overlap, counted once18ha
Boundary editionSample boundary1
Constraint definitionSample constraint class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional 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: Site polygon; hazard map edition; slope; development type; investigation requirement.

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.
Your checks for this decision
2. Prioritize zones with outdated or incomplete hazard evidenceDEC-DP17-002 · Hazard-map updates
Try this decision

Find missing edition, scale and classification details in a hazard layer.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — hazard-map updates / Laggala PallegamaMap coverage: MissingObtain the missing evidence listed below
Rattota — hazard-map updates / Rattotaedition date: MissingObtain the missing evidence listed below
Panvila — hazard-map updates / Panvilanew incidents: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this hazard-map updates 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
  • Map coverage: Missing

Complete metadata do not establish fitness for a particular engineering design.

Inputs, method and sources
Supplied inputValueUnit
Map coverageMissing
Map coverage evidence referenceNot provided
edition dateDocumented
edition date evidence referenceSample Laggala Pallegama field register / 2025
new incidentsDocumented
new incidents evidence referenceSample Laggala Pallegama field register / 2025
terrain changesDocumented
terrain changes evidence referenceSample Laggala Pallegama field register / 2025
survey needDocumented
survey need evidence referenceSample 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: Map coverage; edition date; new incidents; terrain changes; survey 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.
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.
Your checks for this decision
3. Prioritize exposed assets for site-specific investigationDEC-DP17-003 · Asset exposure
Try this decision

Review supplied asset matches to a dated hazard footprint.

Validation required

Fictional default example · 2025.

Fictional case / areaSpatially matched share [%]Distinct matched receptors [assets]Next check
Laggala Pallegama — asset exposure / 20252418Check the matching footprint, source boundary and applicable conditions
Rattota — asset exposure / 20252418Check the matching footprint, source boundary and applicable conditions
Panvila — asset exposure / 20252418Check the matching footprint, source boundary and applicable conditions

What the selected record shows. The supplied overlap is 18 assets within the 75 assets 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.

This example does not run a spatial exposure analysis or predict damage.

Inputs, method and sources
Supplied inputValueUnit
Distinct assets in the matching assessed frame75assets
Those assets reported within the source-defined area; counted once18assets
Boundary edition and spatial predicateSample within/overlap predicate1
Hazard/constraint/source class and observation periodSample dated source class
Matching source frame, boundary and period evidenceProvided
Area/count source and matching definition referenceFictional matched survey return / edition 1

100×distinct spatially matched receptors / receptors in the same frame. Count a receptor once across overlapping areas; do not invent hectare areas from points. 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: Asset geometry; susceptibility class; vulnerability evidence; map accuracy; occupancy.

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.
Your checks for this decision
4. Investigate rainfall patterns associated with landslidesDEC-DP17-004 · Rainfall investigations
Try this decision

Review rainfall observations and their reference periods for specialist interpretation.

Validation required

Fictional default example · 2025.

Fictional case / areaObserved value [mm]Next check
Laggala Pallegama — rainfall investigations / 2025104Check source and period comparability before using the trend
Rattota — rainfall investigations / 2025111Check source and period comparability before using the trend
Panvila — rainfall investigations / 2025118Check source and period comparability before using the trend

What the selected record shows. Observed value: 104 mm.

Next step. Check source and period comparability before using the trend. Prepare trend report in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A rainfall pattern alone does not supply an authorised warning trigger.

Inputs, method and sources
Supplied inputValueUnit
Comparable observation104mm

Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean.

Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend.

Other required records: Dated landslides; rainfall series; antecedent conditions; station coverage; uncertainty.

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 decision
5. Escalate observed cracks movement and drainage defectsDEC-DP17-005 · Slope inspections
Try this decision

Check reported cracks, movement and inspection evidence before engineering referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — slope inspections / Laggala PallegamaSlope ID: MissingObtain the missing evidence listed below
Rattota — slope inspections / Rattotamovement observations: MissingObtain the missing evidence listed below
Panvila — slope inspections / Panvilacracks: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this slope inspections 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
  • Slope ID: Missing

The page does not diagnose slope stability or declare a site safe.

Inputs, method and sources
Supplied inputValueUnit
Slope IDMissing
Slope ID evidence referenceNot provided
movement observationsDocumented
movement observations evidence referenceSample Laggala Pallegama field register / 2025
cracksDocumented
cracks evidence referenceSample Laggala Pallegama field register / 2025
seepageDocumented
seepage evidence referenceSample Laggala Pallegama field register / 2025
dated inspectionDocumented
dated inspection evidence referenceSample Laggala Pallegama field register / 2025
approved limitsDocumented
approved limits evidence referenceSample 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: Slope ID; movement observations; cracks; seepage; dated inspection; approved limits.

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 decision
6. Repair failed landslide-monitoring instrumentsDEC-DP17-006 · Monitoring systems
Try this decision

Identify overdue or missing instrument observations.

Validation required

Fictional default example · 2025.

Fictional case / areaCompleteness [%]Age of latest observation [days]Missing observations [observations]Next check
Laggala Pallegama — monitoring systems / 20258026Check overdue observation
Rattota — monitoring systems / 20258026Check overdue observation
Panvila — monitoring systems / 20258026Check overdue observation

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

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

Observation age alone does not establish movement or immediate danger.

Inputs, method and sources
Supplied inputValueUnit
Expected observations in the window30observations
Distinct valid observations24observations
Latest valid observation2025-06-28
Assessment date2025-06-30
Required observation interval1days

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

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

Other required records: Sensor ID; cadence; last observation; calibration; fault history; criticality.

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 decision
7. Compare engineering mitigation alternativesDEC-DP17-007 · Slope stabilization
Try this decision

Compare stabilisation choices using the investigation evidence and site constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Engineered surface drainage / Laggala PallegamaManage the documented surface runoff.Needs an engineered drainage design, outfall checks and upkeep.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Designed retaining intervention / Laggala PallegamaProvide a designed retaining intervention.Needs geotechnical investigation, design checks and construction resources.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Managed avoidance and land-use controls / Laggala PallegamaAvoid the specified hazardous use.Needs hazard, land-rights, livelihood and planning evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

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

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

Information still needed
  • Records needed: Site investigation; failure mechanism; designs; costs; land access; maintenance
  • Applicable conditions, what was checked and the supporting reference

Budget and descriptive benefits cannot determine a safe engineering design.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionManage the documented surface runoff.
Resource needs and adverse effectsNeeds an engineered drainage design, outfall checks and upkeep.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

Budget and descriptive benefits cannot determine a safe engineering design.

Other required records: Site investigation; failure mechanism; designs; costs; land access; maintenance.

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 decision
8. Refer relocation alternatives for competent determinationDEC-DP17-008 · Relocation assessment
Try this decision

Follow up unresolved relocation issues and participation barriers.

Validation required

Fictional default example · 2025.

Fictional case / areaUnresolved issues [issues]Response share [%]Next check
Laggala Pallegama — relocation assessment / 20251671.579Obtain the missing evidence listed below
Rattota — relocation assessment / 20251671.579Obtain the missing evidence listed below
Panvila — relocation assessment / 20251671.579Obtain 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

Responses or attendance do not establish informed consent or resolve rights.

Inputs, method and sources
Supplied inputValueUnit
Distinct relevant people invited95people
People who responded68people
Unresolved issues16issues
Proposal/version being discussedSample proposal1
Required participation channels accessibleUnknown
Reference for unresolved issues and their progressNot provided
Evidence about participation barriersNot 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: Hazard evidence; household needs; feasible sites; rights; consultations; approvals.

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 decision
9. Verify compliance with site-clearance conditionsDEC-DP17-009 · Construction conditions
Try this decision

Find missing source records in a site-clearance request.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — construction conditions / Laggala PallegamaClearance version: MissingObtain the missing evidence listed below
Rattota — construction conditions / Rattotacondition checklist: MissingObtain the missing evidence listed below
Panvila — construction conditions / Panvilaconstruction evidence: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this construction conditions 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
  • Clearance version: Missing

The prototype issues no clearance or construction permission.

Inputs, method and sources
Supplied inputValueUnit
Clearance versionMissing
Clearance version evidence referenceNot provided
condition checklistDocumented
condition checklist evidence referenceSample Laggala Pallegama field register / 2025
construction evidenceDocumented
construction evidence evidence referenceSample Laggala Pallegama field register / 2025
inspection datesDocumented
inspection dates evidence referenceSample Laggala Pallegama field register / 2025
engineerDocumented
engineer evidence referenceSample 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: Clearance version; condition checklist; construction evidence; inspection dates; engineer.

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 decision
10. Resolve conflicting ground-investigation resultsDEC-DP17-010 · Geotechnical evidence
Try this decision

Compare supplied ground-investigation results and their matching definitions.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [mm]Relative change [%]Next check
Laggala Pallegama — geotechnical evidence / 2025-10-10Reconcile the original records using their source references
Rattota — geotechnical evidence / 202555Reconcile the original records using their source references
Panvila — geotechnical evidence / 2025-2-2Reconcile the original records using their source references

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

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.

Differences require source and site checks before an engineering interpretation.

Inputs, method and sources
Supplied inputValueUnit
Original source measurement100mm
Independent comparison measurement90mm
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable mm 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: Boreholes; laboratory results; stratigraphy; locations; methods; uncertainty.

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 decision
11. Prepare technical review of landslide-warning conditionsDEC-DP17-011 · Early warning evidence
Try this decision

Check rainfall, movement and observation conditions before an authorised warning review.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — early warning evidence / Laggala PallegamaRainfall: MissingObtain the missing evidence listed below
Rattota — early warning evidence / Rattotasoil moisture: MissingObtain the missing evidence listed below
Panvila — early warning evidence / Panvilamovement: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this early warning evidence 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
  • Rainfall: Missing

A checklist is not a warning threshold or a publication authority.

Inputs, method and sources
Supplied inputValueUnit
RainfallMissing
Rainfall evidence referenceNot provided
soil moistureDocumented
soil moisture evidence referenceSample Laggala Pallegama field register / 2025
movementDocumented
movement evidence referenceSample Laggala Pallegama field register / 2025
approved thresholdsDocumented
approved thresholds evidence referenceSample Laggala Pallegama field register / 2025
forecastDocumented
forecast evidence referenceSample Laggala Pallegama field register / 2025
duty authorityDocumented
duty authority evidence referenceSample Laggala Pallegama field register / 2025
Documented unresolved critical conditionUnknown
Evidence observation date2025-06-30
Existing control and its evidenceSample documented control
Competent recipientResponsible specialist / duty authority

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

Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.

Other required records: Rainfall; soil moisture; movement; approved thresholds; forecast; duty 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.
Your checks for this decision
12. Prioritize delayed geotechnical testing requestsDEC-DP17-012 · Laboratory workload
Try this decision

Identify tests and inspections whose recorded response is overdue.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — laboratory workload / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — laboratory workload / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — laboratory workload / 20252990Follow up overdue case; confirm the missing condition evidence

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

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

Information still needed
  • Documented critical unresolved condition: Unknown

Age alone does not establish engineering urgency or a safe operating condition.

Inputs, method and sources
Supplied inputValueUnit
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 closedNot 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: Sample ID; required test; receipt date; urgency; due date; laboratory 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.
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.
Your checks for this decision
13. Prioritize assessment of unstable road cutsDEC-DP17-013 · Road slopes
Try this decision

Check the evidence behind a reported road-cut stability concern.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — road slopes / Laggala PallegamaRoad segment: MissingObtain the missing evidence listed below
Rattota — road slopes / Rattotaslope condition: MissingObtain the missing evidence listed below
Panvila — road slopes / Panvilatraffic exposure: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this road slopes 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
  • Road segment: Missing

No failure probability or construction design is inferred.

Inputs, method and sources
Supplied inputValueUnit
Road segmentMissing
Road segment evidence referenceNot provided
slope conditionDocumented
slope condition evidence referenceSample Laggala Pallegama field register / 2025
traffic exposureDocumented
traffic exposure evidence referenceSample Laggala Pallegama field register / 2025
drainageDocumented
drainage evidence referenceSample Laggala Pallegama field register / 2025
failure historyDocumented
failure history evidence referenceSample Laggala Pallegama field register / 2025
accessDocumented
access evidence referenceSample Laggala Pallegama field register / 2025
Documented unresolved critical conditionUnknown
Evidence observation date2025-06-30
Existing control and its evidenceSample documented control
Competent recipientResponsible specialist / duty authority

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

Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.

Other required records: Road segment; slope condition; traffic exposure; drainage; failure history; access.

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 decision
14. Schedule investigations after reported slope failuresDEC-DP17-014 · Post-event inspection
Try this decision

Check post-failure assessment tasks against resources and dependencies.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — post-event inspection / 202538Resolve overlapping resource bookings
Rattota — post-event inspection / 202538Resolve overlapping resource bookings
Panvila — post-event inspection / 202538Resolve overlapping resource bookings

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

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

The example does not assign investigators or permit access to a hazardous site.

Inputs, method and sources
Supplied inputValueUnit
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

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: Incident ID; access restrictions; exposed assets; investigators; priority; weather.

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 decision
15. Compare options to reduce slope-related drainage problemsDEC-DP17-015 · Drainage remediation
Try this decision

Compare drainage choices using the stated slope investigation and constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Repair surface drains / Laggala PallegamaRepair the documented surface drains.Needs inspection, capacity, outfall and maintenance evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Install designed subsurface drainage / Laggala PallegamaInstall designed subsurface drainage.Needs ground investigation, design, monitoring and upkeep.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Stage drainage and slope investigation / Laggala PallegamaStage drainage work after further investigation.Needs an investigation plan, interim controls and review criteria.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

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

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

Information still needed
  • Records needed: Seepage; runoff; drainage condition; slope mechanism; proposed works; costs
  • Applicable conditions, what was checked and the supporting reference

Drainage benefits must be supported by site-specific engineering evidence.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionRepair the documented surface drains.
Resource needs and adverse effectsNeeds inspection, capacity, outfall and maintenance evidence.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

Drainage benefits must be supported by site-specific engineering evidence.

Other required records: Seepage; runoff; drainage condition; slope mechanism; proposed works; costs.

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 decision
16. Require validation of landslide susceptibility modelsDEC-DP17-016 · Model validation
Try this decision

Check whether supplied model inputs reproduce the reported probability.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [probability]Relative change [%]Next check
Laggala Pallegama — model validation / 2025-0.03-4.615Investigate reproduction difference
Rattota — model validation / 202500Difference within supplied tolerance
Panvila — model validation / 20250.023.077Investigate reproduction difference

What the selected record shows. Difference: -0.03 probability. 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.

Reproduction does not validate the model or establish a new site probability.

Inputs, method and sources
Supplied inputValueUnit
Supplied expected model probability0.65probability
Supplied independently reproduced probability0.62probability
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable probability measure; same input scope
Documented absolute comparison tolerance0.01probability
Expected input/method versionSample input1 /method1
Reproduced input/method versionSample input1 /method1
Original result creatorPreparation officer
Independent reproducerIndependent 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.

Scalar reproduction does not demonstrate model discrimination, calibration, transferability or site safety.

Other required records: Training incidents; independent validation; predictors; resolution; model version; uncertainty.

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 decision
17. Evaluate stabilization performance after completionDEC-DP17-017 · Mitigation outcomes
Try this decision

Compare stabilisation outcomes in the supplied observation groups and periods.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [mm]Next check
Laggala Pallegama — mitigation outcomes / 202510Obtain the missing evidence listed below
Rattota — mitigation outcomes / 202510Obtain the missing evidence listed below
Panvila — mitigation outcomes / 202510Obtain the missing evidence listed below

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

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

Information still needed
  • Study design and evidence that the treatment and comparison records are comparable

A difference in changes does not establish a causal treatment effect.

Inputs, method and sources
Supplied inputValueUnit
Treatment Measured slope displacement before42mm
Treatment Measured slope displacement after59mm
Comparison Measured slope displacement before39mm
Comparison Measured slope displacement after46mm
Study design and comparability evidenceMissing
Outcome definition, method and reference basisMeasured slope displacement /example matching definition1

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

The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence.

Other required records: Baseline movement; post-work movement; rainfall; controls; maintenance; observation dates.

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

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

Calculation appendix

  • World Bank Impact Evaluation in Practice Second Edition — Institution publication. Chapter7 difference-in-differences. Published difference-in-differences estimator and study assumptions; aggregate examples do not establish causation.
  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
18. Identify developments needing additional terrain investigationDEC-DP17-018 · Land-use advice
Try this decision

Find missing terrain, material and source details for an investigation.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — land-use advice / Laggala PallegamaDevelopment footprint: MissingObtain the missing evidence listed below
Rattota — land-use advice / Rattotageology: MissingObtain the missing evidence listed below
Panvila — land-use advice / Panvilaslope: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this land-use advice 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
  • Development footprint: Missing

A complete evidence list is not a stability assessment.

Inputs, method and sources
Supplied inputValueUnit
Development footprintMissing
Development footprint evidence referenceNot provided
geologyDocumented
geology evidence referenceSample Laggala Pallegama field register / 2025
slopeDocumented
slope evidence referenceSample Laggala Pallegama field register / 2025
hydrologyDocumented
hydrology evidence referenceSample Laggala Pallegama field register / 2025
hazard editionDocumented
hazard edition evidence referenceSample Laggala Pallegama field register / 2025
uncertaintyDocumented
uncertainty evidence referenceSample 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: Development footprint; geology; slope; hydrology; hazard edition; uncertainty.

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.
Your checks for this decision
19. Target exposed communities missing preparedness guidanceDEC-DP17-019 · Community awareness
Try this decision

Find locations with no confirmed access to the relevant building guidance.

Validation required

Fictional default example · 2025.

Fictional case / areaVerified coverage [%]Known uncovered [households]Unknown coverage [households]Next check
Laggala Pallegama — community awareness / 202565305Check the records behind the uncovered and unknown groups
Rattota — community awareness / 202585150Check the records behind the uncovered and unknown groups
Panvila — community awareness / 2025454015Check the records behind the uncovered and unknown groups

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

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

Recorded distribution does not establish compliance or safer construction.

Example chart
Verified coverage — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Required eligible frame100households
Distinct members of that frame covered65households
Frame members with unknown coverage5households

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

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

Other required records: Exposure frame; outreach attendance; verified understanding; location; warning access.

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 decision
20. Clear incomplete landslide assessment applicationsDEC-DP17-020 · Case administration
Try this decision

Identify investigation applications past their recorded response date.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — case administration / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — case administration / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — case administration / 20252990Follow 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 establish the technical risk or grant an application.

Inputs, method and sources
Supplied inputValueUnit
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 closedNot provided

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

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

Other required records: Application ID; missing evidence; received date; due date; assigned reviewer.

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 decision

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Disaster Exposure · Soil & Land Management

Existing form reference: 3c6e0cfb0e978318

FieldUnitRequired
Layer Name RiskInfoConfirm if neededNo
CategoryConfirm if neededNo
MaxConfirm if neededNo
Class NameConfirm if neededNo
max11Confirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Landslide · Soil & Land Management

Existing form reference: ea62ecace985e67d

FieldUnitRequired
idConfirm if neededNo
rangeConfirm if neededNo
levelConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
LHazard10K_U1 · Hazards

Existing form reference: 5b9dbec4b87332bc

FieldUnitRequired
rangeConfirm if neededNo
categoryConfirm if neededNo
manualConfirm if neededNo
areaConfirm 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.

National Building Research Organisation Documents and images prototype screen
National Building Research Organisation. 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.

National Building Research Organisation Data structure management prototype screen
National Building Research Organisation. 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.

National Building Research Organisation Users and access prototype screen
National Building Research Organisation. 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.