CIFOR-ICRAF and Research Partners

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. Compare recorded ecosystem-class changesDEC-DP12-001 · Ecosystem change
Try this decision

Compare dated ecosystem-class areas and the supporting condition evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaNet class-area change [ha]Relative class-area change [%]Gross loss from class [ha]Gross gain to class [ha]Next check
Laggala Pallegama — ecosystem change / 2025-10-10188Check the matching source records before interpreting the change
Rattota — ecosystem change / 202554.16738Check the matching source records before interpreting the change
Panvila — ecosystem change / 2025-2-2.564Check the matching source records before interpreting the change

What the selected record shows. The recorded Sample matching forest/land-use class area changes from 100 to 90 ha. Net change is -10 ha; supplied gross loss is 18 ha and gross gain is 8 ha.

Next step. Check the matching source records before interpreting the change. Prepare change comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Extent change alone does not measure ecosystem condition or identify its cause.

Example chart
Net class-area change — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Earlier mapped class area100ha
Later mapped class area90ha
Matched area leaving the class18ha
Matched area entering the class8ha
Same fixed analysis extent200ha
Native class and mapping versionSample matching forest/land-use class
Earlier observation date2024-06-30
Later observation date2025-06-30

Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion.

Same boundary, definitions, observation basis and adequate map quality are required. Coverage changes and classification error are not proven land-use change. Example boundaries and transitions are fictional.

Other required records: Ecosystem class; mapped extent; condition indicator; dates; method; 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
2. Compare soil-carbon monitoring recordsDEC-DP12-002 · Soil-carbon monitoring
Try this decision

Compare soil-carbon observations with matching sampling conventions.

Verified published formula · Soil-carbon stock with volume correction

Fictional default example · 2025.

Fictional case / areaSoil-carbon stock [t C/ha]Next check
Laggala Pallegama — soil-carbon monitoring / 202559.4Check sampling comparability before using the stock comparison
Rattota — soil-carbon monitoring / 202559.4Check sampling comparability before using the stock comparison
Panvila — soil-carbon monitoring / 202559.4Check sampling comparability before using the stock comparison

What the selected record shows. The supplied 1.8% carbon, 1.25 g/cm³ bulk density, 0.3 m depth and 12% coarse fragments give 59.4 t C/ha under the stated fine-earth convention.

Next step. Check sampling comparability before using the stock comparison. Prepare carbon comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Stock differences do not establish treatment effects without comparable samples.

Inputs, method and sources
Supplied inputValueUnit
Soil organic carbon1.8%
Fine-earth bulk-density basis1.25t/m³
Sample depth0.3m
Coarse-fragment volume fraction12%
Sampling depth, design and density conventionSample matched depth and fine-earth convention

(Organic carbon% /100) × bulk density × depth ×10000 × (1−coarse% /100). Confirm that the density and coarse-fragment conventions are mutually consistent.

A carbon concentration is not a stock. Change comparisons require consistent depth/mass, sampling, density convention and uncertainty review.

Other required records: Carbon fraction; bulk density; depth; coarse fragments; sampling design; date.

Intergovernmental Panel on Climate Change · Good Practice Guidance for LULUCF
Institution publication · Section 4.3.3.5.4, equation 4.3.3, printed page 4.106, PDF page 18

The screen converts carbon percent to a fraction and uses the published coarse-fragment volume convention. Sampling and bulk-density conventions still need confirmation.

Calculation appendix

  • IPCC 2006 Guidelines Volume 4 Chapter 2 — Institution publication. Volume4 chapter2 sections2.2 and2.3.3. Published carbon-stock/change and soil-carbon framework; input conventions and local applicability require review.
  • 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
3. Check biodiversity survey effort and comparabilityDEC-DP12-003 · Biodiversity evidence
Try this decision

Check survey effort, protocol and coverage before comparing biodiversity observations.

Validation required

Fictional default example · 2025.

Fictional case / areaObserved richness [species]Recorded effort [hours]Next check
Laggala Pallegama — biodiversity evidence / 20252818Review survey comparability
Rattota — biodiversity evidence / 20252818Review survey comparability
Panvila — biodiversity evidence / 20252818Review survey comparability

What the selected record shows. Observed richness: 28 species. Review survey comparability.

Next step. Review survey comparability. Prepare biodiversity comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Observed richness can differ because effort and detection conditions differ.

Inputs, method and sources
Supplied inputValueUnit
Observed distinct species28species
Survey effort18hours
Survey protocol and versionSample protocol1
Survey season and taxonomic scopeSample matched season / taxon group
All planned survey visits completedYes

Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred.

Observed richness is not population size or occupancy. Comparable effort alone does not remove detection bias or establish a biodiversity trend.

Other required records: Survey event; protocol; effort; taxa; detections; season; sampling frame.

Calculation appendix

  • GBIF biological survey publishing guide — Institution publication. Version1.0.2, sections5.4 to5.7 and7.3. Survey event, effort, protocol, sampling scope and non-detection context; not a population estimator.
  • 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. Review evidence for forest-carbon estimatesDEC-DP12-004 · Forest-carbon estimates
Try this decision

Check the inventories and pool definitions supporting a forest-carbon comparison.

Verified published component · Carbon stock-difference component

Fictional default example · 2025.

Fictional case / areaCarbon stock change [t C]Carbon-density change [t C/ha]Next check
Laggala Pallegama — forest-carbon estimates / 2025-850-10Review the matched pools, area and observation periods
Rattota — forest-carbon estimates / 2025-850-10Review the matched pools, area and observation periods
Panvila — forest-carbon estimates / 2025-850-10Review the matched pools, area and observation periods

What the selected record shows. Carbon stock change: -850 t C.

Next step. Review the matched pools, area and observation periods. Prepare carbon comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A stock estimate does not establish a verified emissions reduction or credit.

Inputs, method and sources
Supplied inputValueUnit
Earlier carbon density100t C/ha
Later carbon density90t C/ha
Same inventory area85ha
Included pools and allometry referencesSample matching biomass pools; source model required

(Later carbon density − earlier carbon density) × same inventory area, with identical pools, method and boundaries.

Inventory plots, allometry and uncertainty remain required evidence. Stock change is not an issued carbon credit, additionality test or payable service.

Other required records: Inventory plots; tree measurements; allometry; pool coverage; carbon fraction; uncertainty.

Intergovernmental Panel on Climate Change · 2006 IPCC Guidelines Volume 4 Chapter 2
Institution publication · Section 2.3.1.1, equation 2.8, stock-difference method

The screen reports the period total. IPCC annualisation requires elapsed years. Pools, inventory inputs and local application still need confirmation.

Calculation appendix

  • IPCC 2006 Guidelines Volume 4 Chapter 2 — Institution publication. Volume4 chapter2 sections2.2 and2.3.3. Published carbon-stock/change and soil-carbon framework; input conventions and local applicability require review.
  • 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. Compare landscape restoration opportunitiesDEC-DP12-005 · Landscape restoration
Try this decision

Compare restoration opportunities using ecological, livelihood and rights evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Natural regeneration in degraded forest / Laggala PallegamaSupport recovery in the specified degraded forest.Needs ecological suitability, regeneration sources, rights and protection.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Agroforestry on eligible holdings / Laggala PallegamaCombine trees and crops on holdings assessed as eligible.Needs crop/tree compatibility, farmer agreement, resources and maintenance.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Riparian habitat restoration / Laggala PallegamaRestore the specified riparian habitat.Needs an applicable boundary, rights, suitable vegetation and outcome monitoring.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: Degradation; tenure; ecological potential; community priorities; costs; connectivity
  • Applicable conditions, what was checked and the supporting reference

Expected benefits remain assumptions until supported for the site.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionSupport recovery in the specified degraded forest.
Resource needs and adverse effectsNeeds ecological suitability, regeneration sources, rights and protection.
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.

Expected benefits remain assumptions until supported for the site.

Other required records: Degradation; tenure; ecological potential; community priorities; costs; connectivity.

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. Compare locally suitable tree-crop combinationsDEC-DP12-006 · Agroforestry design
Try this decision

Check local evidence for proposed tree-crop combinations.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — agroforestry design / Laggala PallegamaSpecies traits: MissingObtain the missing evidence listed below
Rattota — agroforestry design / Rattotacrop needs: MissingObtain the missing evidence listed below
Panvila — agroforestry design / Panvilasoil: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this agroforestry design 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
  • Species traits: Missing

A checklist does not establish crop or ecological compatibility.

Inputs, method and sources
Supplied inputValueUnit
Species traitsMissing
Species traits evidence referenceNot provided
crop needsDocumented
crop needs evidence referenceSample Laggala Pallegama field register / 2025
soilDocumented
soil evidence referenceSample Laggala Pallegama field register / 2025
rainfallDocumented
rainfall evidence referenceSample Laggala Pallegama field register / 2025
shadeDocumented
shade evidence referenceSample Laggala Pallegama field register / 2025
farmer objectivesDocumented
farmer objectives evidence referenceSample Laggala Pallegama field register / 2025
market accessDocumented
market access 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: Species traits; crop needs; soil; rainfall; shade; farmer objectives; market 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
7. Check a proposed study designDEC-DP12-007 · Research design
Try this decision

Check whether a study design can address its stated intervention question.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — research design / Laggala PallegamaHypothesis: MissingObtain the missing evidence listed below
Rattota — research design / Rattotatreatment: MissingObtain the missing evidence listed below
Panvila — research design / Panvilacomparison: MissingObtain the missing evidence listed below

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

A documented design still needs appropriate specialist review.

Inputs, method and sources
Supplied inputValueUnit
HypothesisMissing
Hypothesis evidence referenceNot provided
treatmentDocumented
treatment evidence referenceSample Laggala Pallegama field register / 2025
comparisonDocumented
comparison evidence referenceSample Laggala Pallegama field register / 2025
baselineDocumented
baseline evidence referenceSample Laggala Pallegama field register / 2025
sample sizeDocumented
sample size evidence referenceSample Laggala Pallegama field register / 2025
confoundersDocumented
confounders evidence referenceSample Laggala Pallegama field register / 2025
outcomesDocumented
outcomes evidence referenceSample Laggala Pallegama field register / 2025

Check whether the question has a defined outcome, appropriate study design, comparison, baseline/follow-up, sampling, confounding and attrition evidence. Do not manufacture an effect estimate from missing design information.

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

Other required records: Hypothesis; treatment; comparison; baseline; sample size; confounders; outcomes.

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
8. Allocate field effort across environmental strataDEC-DP12-008 · Sampling allocation
Try this decision

Compare proposed survey effort across environmental strata.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Equal effort across strata / Laggala PallegamaDistribute the proposed effort equally across defined strata.Needs valid stratum definitions, feasible access and evidence about precision.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
More effort in variable strata / Laggala PallegamaDirect more effort to strata with greater measured variability.Needs preliminary variance, stratum sizes, costs and a defensible allocation design.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Staged accessible-site survey / Laggala PallegamaSurvey accessible sites in defined stages.Needs explicit coverage exclusions, selection-bias review and a later-access plan.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: Sampling frame; strata; variance estimates; costs; access; target precision
  • Applicable conditions, what was checked and the supporting reference

Cost alone does not establish precision or a defensible sample allocation.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionDistribute the proposed effort equally across defined strata.
Resource needs and adverse effectsNeeds valid stratum definitions, feasible access and evidence about precision.
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.

Cost alone does not establish precision or a defensible sample allocation.

Other required records: Sampling frame; strata; variance estimates; costs; access; target precision.

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. Resolve incompatible ecological concepts before combining datasetsDEC-DP12-009 · Data harmonization
Try this decision

Check ecological definitions before records from different sources are combined.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — data harmonization / Laggala PallegamaSource variables: MissingObtain the missing evidence listed below
Rattota — data harmonization / Rattotadefinitions: MissingObtain the missing evidence listed below
Panvila — data harmonization / Panvilaunits: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Source variables: Missing

Similar terms do not establish equivalent concepts or compatible measurements.

Inputs, method and sources
Supplied inputValueUnit
Source variablesMissing
Source variables evidence referenceNot provided
definitionsDocumented
definitions evidence referenceSample Laggala Pallegama field register / 2025
unitsDocumented
units evidence referenceSample Laggala Pallegama field register / 2025
methodsDocumented
methods evidence referenceSample Laggala Pallegama field register / 2025
taxonomic referencesDocumented
taxonomic references evidence referenceSample Laggala Pallegama field register / 2025
steward reviewDocumented
steward review 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: Source variables; definitions; units; methods; taxonomic references; steward review.

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. Check independently reproduced model resultsDEC-DP12-010 · Model validation
Try this decision

Compare an independently reproduced model result with its stated expectation.

Validation required

Fictional default example · 2025.

Fictional case / areaDifference [m³/season]Relative change [%]Next check
Laggala Pallegama — model validation / 2025-10-10Investigate reproduction difference
Rattota — model validation / 202555Investigate reproduction difference
Panvila — model validation / 2025-2-2Investigate reproduction difference

What the selected record shows. Difference: -10 m³/season. 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.

Agreement does not establish model validity or fitness for a new use.

Inputs, method and sources
Supplied inputValueUnit
Earlier/source value100m³/season
Independently reproduced value90m³/season
Original measurement unitSample matching unit
Comparison measurement unitSample matching unit
Compared measure and definitionSample comparable m³/season measure; same input scope
Documented absolute comparison tolerance0.01m³/season
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.

Other required records: Model version; training data; held-out validation; parameters; performance; 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. Assess whether land-management changes affect water outcomesDEC-DP12-011 · Hydrological evidence
Try this decision

Compare water-outcome changes in managed and comparison observations.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [m³/season]Next check
Laggala Pallegama — hydrological evidence / 202510Obtain the missing evidence listed below
Rattota — hydrological evidence / 202510Obtain the missing evidence listed below
Panvila — hydrological evidence / 202510Obtain the missing evidence listed below

What the selected record shows. Treatment change: 17; comparison change: 7; difference in changes: 10 m³/season. 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

Difference in changes alone does not establish a land-management effect.

Inputs, method and sources
Supplied inputValueUnit
Treatment Seasonal streamflow volume before42m³/season
Treatment Seasonal streamflow volume after59m³/season
Comparison Seasonal streamflow volume before39m³/season
Comparison Seasonal streamflow volume after46m³/season
Study design and comparability evidenceMissing
Outcome definition, method and reference basisSeasonal streamflow volume /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: Treatment sites; control catchments; rainfall; streamflow; baseline; follow-up.

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
12. Prepare separate physical service accountsDEC-DP12-012 · Ecosystem services
Try this decision

Reconcile ecosystem extent separately from recorded physical service flows.

Validation required

Fictional default example · 2025.

Fictional case / areaClosing ecosystem extent [ha]Physical service flow [m³/year]Next check
Laggala Pallegama — ecosystem services / 2025794120,000Review the extent or flow definitions and matching source records
Rattota — ecosystem services / 2025794120,000Review the extent or flow definitions and matching source records
Panvila — ecosystem services / 2025794120,000Review the extent or flow definitions and matching source records

What the selected record shows. Closing ecosystem extent: 794 ha.

Next step. Review the extent or flow definitions and matching source records. Prepare account comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Extent, annual service flow and monetary value cannot be combined as one quantity.

Inputs, method and sources
Supplied inputValueUnit
Opening ecosystem extent750ha
Extent additions92ha
Extent reductions48ha
Measured service flow in the period120,000m³/year
Service definition and flow unitFictional annual water-provisioning flow to the stated users / m³/year / same accounting boundary
Separate monetary valuation method/price yearNot provided

Closing extent = opening + additions − reductions. Record the period service flow separately; do not add a flow to an asset stock or multiply by an arbitrary PES rate.

Keep extent, condition, physical service flows and monetary accounts distinct. A defensible valuation method, price year and accounting boundary are needed for monetary results. Ecosystem extent in hectares and annual water-provisioning flow in cubic metres are separate accounts. A measured flow does not identify its ecosystem contribution or assign a monetary value.

Other required records: Ecosystem extent; condition; service flow; beneficiaries; accounting area; period.

Calculation appendix

  • UN SEEA Ecosystem Accounting — Institution publication. Full method locator not established. Institutional context; does not establish the calculation or local approval.
  • 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
13. Compare livelihood conservation and water-management alternativesDEC-DP12-013 · Trade-offs
Try this decision

Compare livelihood, conservation and water-management choices using their trade-offs.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Agroforestry livelihood support / Laggala PallegamaSupport the proposed agroforestry livelihood activity.Needs rights, crop/tree suitability, income evidence and maintenance resources.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Riparian conservation support / Laggala PallegamaSupport the proposed riparian conservation activity.Needs ecological, boundary, rights and livelihood trade-off evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Community water-management support / Laggala PallegamaSupport the proposed community water-management activity.Needs hydrological, governance, access and operating-resource 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: Options; ecological outcomes; livelihood effects; water effects; costs; constraints
  • Applicable conditions, what was checked and the supporting reference

A budget comparison does not establish the best landscape outcome.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionSupport the proposed agroforestry livelihood activity.
Resource needs and adverse effectsNeeds rights, crop/tree suitability, income evidence and maintenance resources.
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.

A budget comparison does not establish the best landscape outcome.

Other required records: Options; ecological outcomes; livelihood effects; water effects; costs; 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.
Your checks for this decision
14. Compare measurements proposed to reduce uncertaintyDEC-DP12-014 · Carbon uncertainty
Try this decision

Compare proposed measurement improvements and their uncertainty evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Additional soil-density measurements / Laggala PallegamaImprove the sampled bulk-density input.Needs sensitivity evidence, an appropriate sampling design and matched soil depths.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Additional carbon-concentration samples / Laggala PallegamaImprove the sampled carbon-concentration input.Needs laboratory quality, sample comparability and evidence about its uncertainty contribution.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Repeat depth and coarse-fragment checks / Laggala PallegamaRecheck depth and coarse-fragment inputs.Needs consistent conventions, field methods and evidence of their effect on the estimate.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: Pool estimates; parameter uncertainty; measurement error; sensitivity; sampling costs
  • Applicable conditions, what was checked and the supporting reference

Cost does not identify which input drives uncertainty without sensitivity evidence.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionImprove the sampled bulk-density input.
Resource needs and adverse effectsNeeds sensitivity evidence, an appropriate sampling design and matched soil depths.
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.

Cost does not identify which input drives uncertainty without sensitivity evidence.

Other required records: Pool estimates; parameter uncertainty; measurement error; sensitivity; sampling 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
15. Review conflicting scientific and community recordsDEC-DP12-015 · Community knowledge
Try this decision

Retain conflicting scientific and community observations for a source review.

Validation required

Fictional default example · 2025.

Fictional case / areaOriginal recordComparison recordNext check
Laggala Pallegama — community knowledge / Laggala PallegamaStudy question: primary register entryStudy question: conflicting source returnResolve source disagreement
Rattota — community knowledge / RattotaStudy question: primary register entryStudy question: conflicting source returnResolve source disagreement
Panvila — community knowledge / PanvilaStudy question: primary register entryStudy question: conflicting source returnResolve source disagreement

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

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

Different descriptions do not establish that either knowledge source is wrong.

Inputs, method and sources
Supplied inputValueUnit
Original source value/definitionStudy question: primary register entry
Comparison source value/definitionStudy question: conflicting source return
Original versionSample version1
Comparison versionSample version2
Do the two source records have documented matching meanings?Unresolved

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

Other required records: Study question; community evidence; scientific evidence; consultations; consent; limitations.

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. Review whose knowledge and outcomes research representsDEC-DP12-016 · Gender and inclusion
Try this decision

Identify groups with no confirmed representation in research records.

Validation required

Fictional default example · 2025.

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

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

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

Coverage does not establish consent, representativeness or equitable outcomes.

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

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: Sampling frame; participation; consented group attributes; missing groups; research scope.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
17. Sustain observation coverage beyond initial field campaignsDEC-DP12-017 · Long-term monitoring
Try this decision

Check repeat-observation tasks against the required windows and resources.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — long-term monitoring / 202538Resolve overlapping resource bookings
Rattota — long-term monitoring / 202538Resolve overlapping resource bookings
Panvila — long-term monitoring / 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.

A schedule does not secure long-term funding or guarantee observations.

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: Monitoring sites; required visits; funding; staff; access; equipment lifespan.

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
18. Check research-output sharing conditionsDEC-DP12-018 · Open science
Try this decision

Check research-output rights, audience and disclosure conditions.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — open science / Laggala PallegamaDataset rights: MissingObtain the missing evidence listed below
Rattota — open science / Rattotaparticipant consent: MissingObtain the missing evidence listed below
Panvila — open science / Panvilasensitive species: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this open science 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
  • Dataset rights: Missing

The example does not authorise sharing or publish a research product.

Inputs, method and sources
Supplied inputValueUnit
Dataset rightsMissing
Dataset rights evidence referenceNot provided
participant consentDocumented
participant consent evidence referenceSample Laggala Pallegama field register / 2025
sensitive speciesDocumented
sensitive species evidence referenceSample Laggala Pallegama field register / 2025
licenseDocumented
license evidence referenceSample Laggala Pallegama field register / 2025
publication approvalDocumented
publication approval 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: Dataset rights; participant consent; sensitive species; license; publication approval.

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
19. Follow up requested evidence productsDEC-DP12-019 · Knowledge products
Try this decision

Identify evidence-product requests whose response date has passed.

Validation required

Fictional default example · 2025.

Fictional case / areaOpen days past due [days]Calendar age [days]Next check
Laggala Pallegama — knowledge products / 20252990Follow up overdue case; confirm the missing condition evidence
Rattota — knowledge products / 20252990Follow up overdue case; confirm the missing condition evidence
Panvila — knowledge products / 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 determine scientific importance or user priority.

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: Decision requests; evidence maturity; product deadlines; analyst capacity; audience.

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. Evaluate uptake and consequences of research recommendationsDEC-DP12-020 · Research translation
Try this decision

Compare recommendation uptake and outcome records.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [%]Next check
Laggala Pallegama — research translation / 202510Obtain the missing evidence listed below
Rattota — research translation / 202510Obtain the missing evidence listed below
Panvila — research translation / 202510Obtain the missing evidence listed below

What the selected record shows. Treatment change: 17; comparison change: 7; difference in changes: 10 %. 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

Uptake and a later outcome do not establish a causal research effect.

Inputs, method and sources
Supplied inputValueUnit
Treatment Verified recommendation uptake before42%
Treatment Verified recommendation uptake after59%
Comparison Verified recommendation uptake before39%
Comparison Verified recommendation uptake after46%
Study design and comparability evidenceMissing
Outcome definition, method and reference basisVerified recommendation uptake /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: Recommendation cohort; institutional decisions; implementation; outcomes; alternative explanations.

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

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

Forest Boundary · Administrative & Planning Areas

Existing form reference: 4e74cc389edc2305

FieldUnitRequired
Forest TypeConfirm if neededNo
Forest NameConfirm if neededNo
RangeConfirm if neededNo
BeatConfirm if neededNo
DivisionConfirm if neededNo
FA DivisionConfirm if neededNo
GFCODEConfirm if neededNo
DescriptionConfirm if neededNo
Area FinalConfirm if neededNo
DistrictConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Hydro Meteorological Stations · Rainfall & Weather

Existing form reference: 678a3e2dcda3b2df

FieldUnitRequired
Station NameConfirm if neededNo
River BasinConfirm if neededNo
QuadrantConfirm if neededNo
X_MeterConfirm if neededNo
Y_MeterConfirm if neededNo
DescriptionConfirm if neededNo
Agro Meteorological Stations · Rainfall & Weather

Existing form reference: 4404e8d7fb7938f5

FieldUnitRequired
Station IDConfirm if neededNo
Station NameConfirm if neededNo
Station CodeConfirm if neededNo
LatitudeConfirm if neededNo
LongitudeConfirm if neededNo
YearConfirm if neededNo
DescriptionConfirm if neededNo
qualifierConfirm if neededNo
elevationConfirm if neededNo
Rainguage Stations · Rainfall & Weather

Existing form reference: 34f3d59c2619b006

FieldUnitRequired
Serial NumberConfirm if neededNo
Station NameConfirm if neededNo
DistrictConfirm if neededNo
LatitudeConfirm if neededNo
LongitudeConfirm if neededNo
Begin DateConfirm if neededNo
End DateConfirm if neededNo
DescriptionConfirm if neededNo
qualifierConfirm if neededNo
elevationConfirm if neededNo
Rainfall · Rainfall & Weather

Existing form reference: 1d5963784380e5d7

FieldUnitRequired
stationidConfirm if neededNo
dateConfirm if neededNo
rainfall_mmConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Synoptic Stations · Rainfall & Weather

Existing form reference: c7953153a5200702

FieldUnitRequired
Serial NumberConfirm if neededNo
Station NameConfirm if neededNo
DistrictConfirm if neededNo
LatitudeConfirm if neededNo
LongitudeConfirm if neededNo
Begin DateConfirm if neededNo
End DateConfirm if neededNo
DescriptionConfirm if neededNo
qualifierConfirm if neededNo
elevationConfirm if neededNo
Climate Zones · Rainfall & Weather

Existing form reference: 2fd8102b7732d899

FieldUnitRequired
Zone_NameConfirm if neededNo
Climate_ClassificationConfirm if neededNo
IDConfirm if neededNo
AGCODEConfirm if neededNo
AGNAMEConfirm if neededNo
areaConfirm if neededNo
PerimeterConfirm if neededNo
TerrainConfirm if neededNo
AGRO_ZoneConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Hydro Zones · Rainfall & Weather

Existing form reference: 8645ce85db37fa03

FieldUnitRequired
Zone IDConfirm if neededNo
Zone AreaConfirm if neededNo
PerimeterConfirm if neededNo
Hydro_TypeConfirm if neededNo
DescriptionConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Soil Groups · Soil & Land Management

Existing form reference: ce03929a51b9da64

FieldUnitRequired
nameConfirm if neededNo
st_area(shape)Confirm if neededNo
st_length(shape)Confirm if neededNo
Forest area by type, 2018–2023 · Forest Resources

Existing form reference: 5d4e57af1e6712f1

FieldUnitRequired
ClassificationConfirm if neededNo
Forest typeConfirm if neededNo
YearConfirm if neededNo
AreaConfirm if neededNo
FP124 financing · Programme Delivery

Existing form reference: e6af681e07c8efdc

FieldUnitRequired
Funding itemConfirm if neededNo
InstrumentConfirm if neededNo
AmountUSDNo
CurrencyConfirm if neededNo
DateConfirm if neededNo
BasisConfirm if neededNo
Public source inventory, October 2026 · Source Coverage · Calculated

Existing form reference: a9b8c8efe788ee9a

FieldUnitRequired
Source identityConfirm if neededNo
Source nameConfirm if neededNo
PublisherConfirm if neededNo
SubjectConfirm if neededNo
Acquisition statusConfirm if neededNo
Captured rowsrowsNo
Published rowsrowsNo
Captured UTCConfirm if neededNo
CoverageConfirm if neededNo
Time fieldConfirm if neededNo
Source URLConfirm 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.

CIFOR-ICRAF and Research Partners Documents and images prototype screen
CIFOR-ICRAF and Research Partners. 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.

CIFOR-ICRAF and Research Partners Data structure management prototype screen
CIFOR-ICRAF and Research Partners. 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.

CIFOR-ICRAF and Research Partners Users and access prototype screen
CIFOR-ICRAF and Research Partners. 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.