SHARED
Calculations and Decision Rules
Companion to the Software Requirements Specification
Version 1.6
Published methods and pending decisions through Institution review
This appendix states how the prototype calculates results and how the proposed system should handle the related decisions. Read it with the main SRS. Each method shows its source, required inputs, calculation or steps, example, limits and approval needs. A correct sample calculation is not evidence of local scientific acceptance.
The main SRS, appendix and controlled registers form one Version 1.6 review package. The 57 family IDs, 820 candidate decisions and 139 method IDs are retained. Repeated examples use one family definition. Use the registers for exact inputs, units, source links, scope and pending approval.
1 Using this appendix
2 Shared calculations and business rules
3 Calculation families
4 Retained method references
5 Sources
6 Approval and acceptance
1 Using this appendix
The Word, PDF and web editions describe the same method content. The following registers are controlled parts of Version 1.6 and must travel with the appendix. The main coverage workbook remains the design coverage record.
Decision_Register.csv All 820 decision examples, exact configured inputs and limits, units, source roles, owners and pending approval. Open online
Method_References.csv All 139 existing reference definitions, formulas or procedures, inputs, limits and original source links. These are candidate methods, not a claim of equivalence to an implemented family. Open online
Calculation_Sources.csv The full source register, with title, URL, locator, source role and access status. Open online
Government publication and Institution publication identify direct support for the stated core method. Record the publisher, edition and exact page or section. Validation required identifies project rules, adaptations or incomplete support. A data or background source alone does not support a formula. Published methods need no repeat proof; confirm local settings and intended use. Developers test copying, arithmetic and input handling. Section 6 separates these checks from client and expert decisions.
Source IDs LOCAL SRS in the registers retain their original legacy chapter labels. They refer to the earlier separate chapter set, not to the current 14 chapter numbering. The PROTO source identifies the prototype function and decision ID; SRS identifies this main SRS. No source citation grants legal, financial or scientific authority.
Inputs and limits
Use the same population, entity, boundary, period, definition, unit and source edition for a comparison. Keep the numerator and denominator visible. Preserve original values, missing reasons, uncertainty and access rights. No data is different from a measured zero. Do not infer a complete population from a partial snapshot or sum incompatible quantities.
All family inputs are required unless an approved method explicitly permits absence. The Decision Register records each current numeric input bound and whole number constraint. These are prototype guards, not scientifically recommended ranges. Generic units in a sample must be replaced by the exact approved institutional definition. Keep calculation precision; round only for display under an agreed rule. No default weights, rates, risk categories, warning levels or legal limits become official through this appendix.
Examples use invented values to check arithmetic. They are not institutional observations or recommendations. The wider proposed procedure in each family may need more data and specialist processing than the displayed example. Where the prototype only plots inputs or completeness, that limitation is stated explicitly.
Read a family in this order: question; exact formula; inputs and units; worked example; effect of an input change; wider proposed procedure; limits; source category. The example explains the prototype rule. It does not demonstrate every part of the wider procedure.
2 Shared calculations and business rules
Counts and source coverage
Count records only within the selected source and filters. Distinct count uses the reviewed identity key. Coverage reports supplied observations and requested rows separately. A snapshot total is not the population total.
Example One person with two memberships and three support episodes counts as one person, two memberships and three episodes.
Category Validation required. Prototype checks the report rows, shows data coverage and builds the results. Requirements FR076 FR077 FR097. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Weighted means and pooled rates
Weighted mean = sum of weight × value divided by sum of valid weights. For a pooled rate, sum compatible numerators and denominators, then divide. Missing weights or a zero total denominator withhold the result.
Example Values 10 and 20 with weights 1 and 3 give 17.5. Rates 1/2 and 9/10 pool to 10/12, or 83.3333 percent.
Category Institution publication. Publisher United Nations Statistics Division (Final Draft). Source DecisionSupportModel.project SURVEY; SRS 5.4. Requirements FR099 FR103. Sources PROTO, SRS, S91.
Review Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6.
Basic crop yield
Production in tonnes divided by matching positive harvested hectares gives t/ha. Do not mix cultivated, sown and harvested area. Reject negative production or zero area.
Example 400 t / 100 ha = 4 t/ha.
Category Validation required. Source SrsCalculations.yield; YIELD input contract. Requirements FR082 FR103. Sources PROTO, SRS, S67.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Break even and margin ratios
For the stated variable cost scope, break even price = variable cost / positive saleable output. Margin ratio = 100 × gross margin / positive revenue. A break even yield uses cost per hectare divided by the applicable positive net price. State which fixed costs are excluded.
Example Variable cost LKR 70000 and 1000 kg give LKR 70/kg. LKR 30000 gross margin on LKR 100000 revenue gives 30 percent.
Category Validation required. Source SRS 5.4; MARGIN; NF022; proposed algebra from the stated gross margin identity. Requirements FR082 FR103. Sources SRS, S76. Published components: Institution publication - Food and Agriculture Organization of the United Nations (FAO) (S76).
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Percentage variance and target progress
Percentage variance = 100 × (actual − plan) / plan for a nonzero plan. Progress from a baseline = 100 × (actual − baseline) / (target − baseline) for unequal target and baseline. Target achievement = 100 × actual / target for a nonzero target. These are different measures. Keep underachievement and values over 100 percent visible unless an approved display rule says otherwise.
Example Actual 120 and plan 100 give +20 and +20 percent. Baseline 20, actual 60 and target 100 give 50 percent progress and 60 percent target achievement.
Category Validation required. Source SrsCalculations.variance; SRS 5.4; NF171. Requirements FR103 FR124. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Reviewed weighted criteria
Normalize each criterion as (value − worst) / (best − worst). Score = 100 × sum of weight × normalized value. Weights must be finite, nonnegative and total one within 0.000000001. Anchors must differ; every required input must lie between its anchors. Exclude infeasible options first. The prototype rounds the score to four decimals before ranking. Rank = one plus the number of strictly higher displayed scores; ties have equal rank.
Example A benefit criterion with worst 0, best 100 and value 80 scores 80. A cost criterion with worst 100, best 0 and value 20 also scores 80. Equal options both rank 1.
Category Validation required. Source SrsCalculations.weighted; SrsDemonstration.compareDecision. Requirements FR102 FR105. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Annual cash flows and payback
For years 0 to n, discounted flow = signed cash flow / (1 + rate fraction) raised to the year. NPV is the sum. The prototype accepts 2 to 51 annual flows and rate above −1 through 1. Its paybackYear is the first year greater than zero with nonnegative cumulative undiscounted cash flow. It is not discounted payback or fractional payback. Do not use it for an unusual flow pattern without a reviewed rule.
Example Flows −100, 60, 60 at 10 percent give NPV 4.1322 and undiscounted payback year 2.
Category Validation required. Source SrsCalculations.cashFlow; FINANCE; NF145 NF147 NF157. Requirements FR103 FR105. Sources PROTO, SRS, S81. Published components: Institution publication - Food and Agriculture Organization of the United Nations (FAO) (S81).
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Cost per additional observed outcome
Observed change = actual − baseline. Cost per additional unit = nonnegative comparable cost / observed change only when that change is positive. A decrease, no change or missing value withholds this ratio. This rule alone does not establish causation or handle a lower is better indicator.
Example Cost LKR 10000, baseline 20 and actual 60 give change 40 and LKR 250 per additional observed unit.
Category Validation required. Source SrsCalculations.costOutcome. Requirements FR103 FR125. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Rainfall missing values and comparable pairs
Calculate a supplied value mean using only explicitly supplied readings; retain the supplied count. A required complete period mean stays unavailable if any required period is missing. Paired analysis uses only compatible pairs and reports their count. A real zero is retained.
Example Example rainfall 1200, 1300, missing, 1400, 1500 mm gives supplied mean 1350 mm and coverage 4/5. With the corresponding cultivation series, paired coverage is 3/5.
Category Validation required. Source SrsCalculations.rainfall; SRS rainfall acceptance example. Requirements FR099 FR103. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Statistical summaries in retained method references
For sorted valid observations, median is the middle value or mean of the two middle values. Sample standard deviation uses sum of squared deviations divided by n − 1 before taking the square root. CV percent = 100 × sample standard deviation / positive mean, with n at least 2 and a meaningful zero. Quartiles need a named algorithm. Shannon sample diversity uses −sum of p × natural log(p), omitting zero terms. These definitions are proposed reference methods; the simple decision plots do not perform them all.
Example For 10, 20, 30, median and mean are 20, sample SD is 10 and CV is 50 percent. For two equally common species, Shannon index is ln(2), about 0.6931.
Category Validation required. Source NF077 NF086 NF109 NF114 NF115; DISTRIBUTION and VOLATILITY catalogue. Requirements FR099 FR103. Sources SRS, S84. Published components: Government publication - United States National Institute of Standards and Technology (NIST) (S84).
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Spatial measurements and intersection
The prototype uses its spatial engine on WGS84 coordinates. Area in square metres is divided by 10000 for hectares. Line length and point distance use kilometres. Intersection area is measured from the actual intersected polygons. Point containment uses the library boundary rule. These are spherical exploratory estimates. A projected authoritative analysis needs a separately approved service and CRS.
Example An intersection of 200000 square metres is 20 ha. An empty intersection is zero area. Different geographic roles cannot be substituted.
Category Validation required. Source SpatialModel.vector; GeographicWorkflow.analyse/compareHistory. Requirements SH-GEO-FEAT-008 SH-GEO-FEAT-012 FR066. Sources PROTO, SRS, S85, S86, S87, S89, S90.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Buffers proximity and spatial limits
Buffer and point proximity radius must be above zero and no more than 20 km; the buffer uses 24 steps. Viewport vector analysis requires 1 to 749 loaded features and excludes demonstration geometry. Count nearby valid points within the chosen radius and report excluded or unsupported features. These are prototype workload limits, not environmental buffer rules.
Example A point at distance 1.5 km is included by a 2 km radius; one at 2.5 km is excluded. A 0 km radius is rejected.
Category Validation required. Source SpatialModel.vector. Requirements FR066 FR074. Sources PROTO, SRS, S86, S88.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Raster pairs and change
Both rasters must retain native aligned width, height, bounding box, CRS, unit and kind. Preview supports EPSG:4326 and at most 262144 cells per grid; no resampling is performed. For each valid pair count changed cells. Continuous mean difference = sum of later minus earlier values divided by paired count. Classified grids produce transition counts. Missing pairs are excluded and counted, not set to zero. Cell counts are not automatically hectares.
Example Earlier cells 1, missing, 3 and later cells 2, 4, 3 give 2 pairs, 1 missing pair, 1 changed cell and mean difference 0.5.
Category Validation required. Source SpatialModel.rasterCheck/rasterCompare. Requirements FR067 FR074. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Reservoir ratios and capacity
Storage percentage = 100 × effective storage / positive active capacity. Capacity composition accepts positive gross capacity, nonnegative dead and effective volumes, and dead plus effective no greater than gross. Remaining volume = gross − dead − effective. Labels must match the source definitions.
Example Gross 100, dead 10 and effective 60 leave 30 in the stated source volume unit. Effective 60 / active 90 gives 66.6667 percent.
Category Validation required. Source WaterModel.ratio/capacity. Requirements FR099 FR103. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Source water level thresholds
Use the source station unit and ordered alert, minor and major thresholds. At or above major select the major band, else at or above minor the minor band, else at or above alert the alert band, else below the source alert band. Missing or unordered thresholds withhold the band. This display is not a new warning.
Example For source thresholds 2, 3 and 4 m, a 3 m reading is in the minor threshold band.
Category Validation required. Source WaterModel.status; DisasterModel.delta. Requirements FR103 FR134. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Observation age and endpoint trend
Age in minutes = max(0, as of time − observation time) / 60000. A future timestamp is still a quality issue requiring review. Endpoint trend = (last value − first value) / elapsed hours for the same station and basin with verified, identical units and a positive elapsed time. It is not regression, a forecast or a warning.
Example A 2 m to 3 m change over 2 hours gives +0.5 m/hour.
Category Validation required. Source DisasterModel.age/latest/trend; WaterModel.stationRecords. Requirements FR055 FR099 FR103. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Official warning display
Only a nonsynthetic public actual alert or update, without a superseding record, and with at least one interval containing as of time is active. The valid from boundary is inclusive and valid to is exclusive. Derived values and stale warnings must not become official alerts.
Example A warning valid from 10:00 to 12:00 is active at 10:00 and inactive at 12:00.
Category Validation required. Source DisasterModel.active/publicRows. Requirements FR134 FR135. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Dashboard aggregation and display
Apply source, period and place filters first. Sum only a declared additive measure within compatible category groups. Count rows separately from distinct identities. Melt named compatible measure columns into chart points. A scatter requires both values. Missing numbers stay absent with a missing count; incomplete snapshots stay marked partial. Funding chart separates disbursed grant from grant not yet disbursed and requires grant no less than paid.
Example Grant 100 and disbursed 60 show 60 disbursed and 40 not disbursed. Unknown amounts do not create a zero total.
Category Validation required. Source PublicDashboardModel.project/metric/chartModel; IrrigationModel.chart; ApprovedChartModel.project. Requirements FR099 FR100. Sources PROTO, SRS.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Report joins and reproducibility
Use a reviewed record, geography and period, or identity and period grain. Combine at most four sources with one to twelve chosen measures, at most 500 rows per source and 2000 result rows. Reject duplicate matching keys and unsupported aggregation before joining. Retain unmatched source rows and exact input versions. Changed plans or sources invalidate their review. Limits are prototype input guards.
Example Two source rows with the same join key are rejected before they can multiply a total. An unmatched observation stays missing.
Category Validation required. Sources PROTO, SRS. Requirements FR094 to FR098. See Section 8 for custom queries and charts.
Review Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6.
Numeric and date validation
Keep zero distinct from blank. Reject booleans and nonfinite numbers as measurements. Respect each declared type, minimum, maximum, precision and scale; integer fields require safe whole numbers. Provider decimal inputs default to at most 15 significant digits and 8 fractional digits, and reject exponent notation. Validate real calendar dates. Use the exact field contract, not a displayed rounded number, for acceptance.
Example 0 is accepted as a reading. A blank, false and an impossible calendar date are rejected.
Category Validation required. Source SrsCalculations.number; ProviderWorkflows.validate; SrsDemonstration.validate; DecisionSupportModel.validate. Requirements FR038 FR058 FR103. Sources PROTO, SRS.
Review Developer tests valid, invalid and missing inputs. C04 confirms allowed values; expert review applies only to scientific limits.
Identity and competing source claims
An independent steward reviews both source identities before adding a relationship. Preserve the separate objects, source claims and histories. A preferred claim records a purpose and reason; it does not delete alternatives. Similar names do not prove identity.
Example Two reviewed records can be linked as related source identities while both original claims remain visible.
Category Validation required. Source SrsDemonstration.linkIdentity/preferClaim. Requirements FR029 FR030 FR033. Sources PROTO, SRS.
Review C02/C04 confirm identity keys, source owners and conflict resolution. Developer tests matching and preserved versions.
Document suggestions and source purpose
Match existing field labels or keys after normalizing text. Rank possible destination forms by count of matched fields, then form name. This is a name match aid, not a scientific or confidence score. Conflicting values, ambiguous numbers and incompatible units require a person to resolve them. Guidance text cannot supply a measured observation. Independent field mapping review and value review are separate.
Example A document stating two different values for rainfall creates a conflict requiring a checked choice; it does not average them.
Category Validation required. Source DocumentSlotModel.matches/rank/values; SrsDemonstration.reviewMapping/mappingKey. Requirements FR046 FR047 FR048 FR049 FR050. Sources PROTO, SRS.
Review C04/C05 confirm source rights and permitted purpose. Developer tests evidence links and restricted outputs.
Feed mapping and duplicate events
Freeze the reviewed source, destination dataset and version, field list, event/time/value keys, protocol, schema and device mapping. Preserve original raw keys and values. A changed contract invalidates mapping review. Replay uses the stable event identity to return the original receipt or reject changed content under that identity. A typed or sample payload is not a provider receipt.
Example Replay of the same event returns the same receipt; the same event key with different measured content is rejected.
Category Validation required. Source SrsDemonstration.feedContract/reviewFeedMapping/feedReplay/importAtomic. Requirements FR051 FR052 FR053 FR054 FR055 FR056. Sources PROTO, SRS.
Review C04 confirms field mapping and source contract. Developer tests duplicates, rejected rows and safe retries.
Review independence and stale evidence
Authors cannot perform protected independent reviews of their own work. Actions require the correct role, institution, state and exact record version. Revisions preserve predecessors and clear checks tied to changed evidence. A saved sample or a successful arithmetic check does not approve a scientific method.
Example A revised input version cannot reuse an approval for the earlier values.
Category Validation required. Source SrsDemonstration.role/independent/review/revise; ProviderWorkflows.review; DecisionSupportModel.adviceTransition. Requirements FR050 FR107 FR113 FR121. Sources PROTO, SRS.
Review C02 confirms reviewer roles. Developer tests separation of roles, changed versions and stale evidence.
Dependencies and project authorization
Check required people, prerequisites, finance, conditions and institutional authorization before activating work. Block cyclic dependencies and unavailable prerequisites. Track recommendation, authorized decision, performed work and verified outcome separately.
Example A task with an unfinished required prerequisite remains blocked.
Category Validation required. Source SrsDemonstration.dependency/dependenciesComplete/authorize/activate. Requirements FR105 FR110 FR111 FR112 FR114 FR115. Sources PROTO, SRS.
Review C01/C02 confirm scope, roles and approval steps. Developer tests dependencies and authorization rules.
Actual progress and outcome evidence
Only the assigned person records progress on open work. Require nonnegative quantity, unit, observation date, evidence and actual geographic support. A reviewer checks the submitted observation independently before it becomes verified progress. Outcome learning records observed results and source against the decision version.
Example Repeating identical progress evidence returns the existing entry; changed content under the same evidence identity is rejected.
Category Validation required. Source SrsDemonstration.progress/reviewProgress/outcome. Requirements FR120 FR121 FR123 FR124 FR125. Sources PROTO, SRS.
Review C10 confirms progress and outcome definitions. Developer tests evidence links and calculations.
PES verification and payment evidence
A recorded payment requires reviewed evidence, an authorized or active agreement, matching verified service evidence and a source payment reference. Client authority, rights, rates and funding are separate decisions. The prototype records evidence and transfers no money.
Example A service verification for another agreement cannot support a payment record.
Category Validation required. Source SrsDemonstration.recordPayment; PES. Requirements FR092 FR093. Sources PROTO, SRS, S60, S61.
Review E03/C10 confirm rights, service evidence, rates, funding and payment authority. Developer tests the agreed rules.
Closure handover and reopening
Freeze the closure checklist and source versions. Verify each required item independently, with current receiving evidence where needed. Close only after all checks and authority requirements pass. Changing the checklist or linked evidence invalidates its checks. Reopening or a revision keeps the prior closure and history.
Example A receiving asset changed after its review blocks closure until the new evidence is checked.
Category Validation required. Source PrototypeCompletion.closureSignature; SrsDemonstration.prepareClosure/fulfil/linkHandover/close/reopen. Requirements FR126 FR127 FR128. Sources PROTO, SRS.
Review C02/C11 confirm receiving roles and closure evidence. Developer tests the agreed workflow.
Source rights and publication
Apply scoped permissions for source, recipient, purpose, area, right, field list and validity period. A matching deny overrides an allow. Dataset provider views also require the active policy, role and institution. Public knowledge requires Published state, Public classification, unexpired rights and eligible citations recursively. Cycles, withdrawn sources and missing evidence block publication. No organization membership gives unrestricted access.
Example Expiry of a parent source removes dependent public guidance from the eligible list.
Category Validation required. Source SrsCalculations.permit; ProviderWorkflows.permitted; SrsDemonstration.sourceEligible/publishableSource. Requirements FR095 FR106 FR133 FR134. Sources PROTO, SRS.
Review C04/C05 confirm permitted use and audiences. Developer tests publication and source withdrawal.
Feedback appeal and safeguarding
Use the approved receiving institution and response policy. Retain the original feedback, evidence, response, independent appeal and final disposition. A response or attendance record is not consent. Publication checks remove restricted or sensitive content.
Example An unresolved appeal remains open with its accountable receiver.
Category Validation required. Source SrsDemonstration.submitFeedback/respondFeedback/appealFeedback/resolveAppeal; CONSENT. Requirements FR135 FR136. Sources PROTO, SRS, S47.
Review C05/C09 confirm privacy, receiving roles and appeals. Developer tests the agreed workflow.
Optional offline work background jobs and recovery
If the client selects offline operation, retain the base version and original evidence under approved protection and retention. Send stale or changed content to conflict review. Atomic receipts prevent a committed import being repeated. Queued jobs can be cancelled or retried; recover a lost response using its existing receipt. Additional channels and offline synchronisation remain proposed options under C01/C06/C07. Operational evidence is still required.
Example Retry after a lost response returns the committed receipt and does not import a second copy.
Category Validation required. Source SrsDemonstration.queueOffline/syncOffline/importAtomic/jobAction. IDs FR139 FR140 FR141 FR145 FR148 SH-GEO-FEAT-017. Sources PROTO, SRS.
Review C01/C06/C07/C08 confirm the selected options and targets. Developer tests the agreed implementation.
Acceptance and release decisions
Mock design coverage means the screen behavior is shown. It does not prove production implementation, local scientific validity, consultation, legal permission, service operations or formal acceptance. Client and experts approve this SRS and its appendix as one version through Institution review; no separate TOR review or UI reviewer gate is added.
Example An arithmetically correct erosion example still needs local factor and method approval before an operational decision.
Category Validation required. Source SRS Chapter 12 acceptance and Chapter 13 review decisions; Institution review. Requirements FR150 FR151 FR152 FR153 FR154 FR155 FR156. Sources SRS, PROTO.
Review C11 records final acceptance after the relevant C01 to C12 and E01 to E03 decisions. Developer evidence does not grant approval.
3 Calculation families
Find the family by its existing ID. Inputs below show a representative configured decision. The Decision Register supplies every decision specific input, unit and bound, including the crop water, productivity, trend and cash balance variants. Read the shared rules in Section 2 with each family. All source codes resolve in Calculation Sources and the web source register.
CHANGE Comparable change
Decision example. Prioritize bathymetric surveys and desilting appraisal.
change = current − baseline
Inputs and units. Earlier surveyed capacity on the same datum (m³); Later surveyed capacity on the same datum (m³).
Worked example. DEC-DP05-008 — Laggala Pallegama — reservoir sedimentation, 2025. Earlier surveyed capacity on the same datum = 900,000 m³; Later surveyed capacity on the same datum = 860,000 m³. Difference = -40,000 m³; Relative change = -4.444 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Earlier surveyed capacity on the same datum = 900,001. Difference = -40,001 m³. Without Earlier surveyed capacity on the same datum, the required result is withheld.
Procedure. Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. land change, change, publication revision.
OVERLAY Spatial constraint screening
Decision example. Refer proposed developments overlapping constraints.
overlap share = 100 × overlap area ÷ footprint area
Inputs and units. Assessed footprint or frame (ha); Reported common overlap, counted once (ha); Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference.
Worked example. DEC-DP01-002 — Laggala Pallegama — development screening, 2025. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Overlap share = 24 %; Overlapping area = 18 ha. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Assessed footprint or frame = 75.75. Overlap share = 23.762 %. Without Assessed footprint or frame, the required result is withheld.
Procedure. 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.
Limits. 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.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. overlay, mahaweli plan, mahaweli reservation, point overlay, well proximity.
COVERAGE Coverage and unmet need
Decision example. Commission missing divisional land-use plans.
coverage = 100 × served eligible units ÷ eligible units
Inputs and units. Divisions in this reporting record (divisions); Divisions with a current applicable plan (divisions); Divisions whose plan status is unknown (divisions).
Worked example. DEC-DP01-003 — Laggala Pallegama — planning coverage, 2025. Divisions in this reporting record = 1 divisions; Divisions with a current applicable plan = 0 divisions; Divisions whose plan status is unknown = 0 divisions. Verified coverage = 0 %; Known uncovered = 1 divisions; Unknown coverage = 0 divisions. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Divisions with a current applicable plan = 1. Verified coverage = 100 %. Without Divisions in this reporting record, the required result is withheld.
Procedure. 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown.
Limits. Count each eligible unit once for the selected service and period. Received messages, attendance, adoption and outcomes are separate measures.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. coverage, feature changes.
MISMATCH Independent evidence reconciliation
Decision example. Resolve conflicting parcel and cultivator records.
unresolved comparisons = count(missing or conflicting equivalence)
Inputs and units. Original source value/definition; Comparison source value/definition; Original version; Comparison version; Do the two source records have documented matching meanings?
Worked example. DEC-DP04-005 - Laggala Pallegama — paddy register, 2025. Original source value/definition = Parcel ID: primary register entry; Comparison source value/definition = Parcel ID: conflicting source return; Original version = Sample version1; Comparison version = Sample version2; Do the two source records have documented matching meanings? = Unresolved. Source comparisons needing review = 1 items. The original record says “Parcel ID: primary register entry”; the comparison says “Parcel ID: conflicting source return”. Their matching meaning has not been established. Obtain the source definitions and supporting records before reconciling them. Next check: Resolve source disagreement. Realistic sample data.
Changed example. Do the two source records have documented matching meanings? = Documented. Source comparisons needing review = 0 items. Next check: Refer documented equivalence. Without Original source value/definition, The original record says “Not provided”; the comparison says “Parcel ID: conflicting source return”. The example marks their meanings as matching. Check the supporting definitions and comparison basis before any record correction.
Procedure. 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.
Method sources. Validation required. DD-LOCAL - SHARED domain decision contracts. Domain decision rules and matching fictional examples.
Domain variants. field map case, mismatch, series mismatch, numeric mismatch, lineage, location mismatch, schema mismatch, affected lots.
EROSION Erosion model comparison
Decision example. Target detailed soil-loss assessment in planning units.
soil loss = R × K × LS × C × P
Inputs and units. Rainfall erosivity (MJ mm/(ha h year)); Soil erodibility (t ha h/(ha MJ mm)); Slope-length and steepness factor (ratio); Cover-management factor (fraction); Support-practice factor (fraction).
Worked example. DEC-DP01-016 — Laggala Pallegama — land degradation, 2025. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Estimated annual sheet/rill loss = 15.641 t/ha/year. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Rainfall erosivity = 951. Estimated annual sheet/rill loss = 15.657 t/ha/year. Without Rainfall erosivity, the required result is withheld.
Procedure. R × K × LS × C × P, using a mutually consistent SI factor set.
Limits. This USLE factor product is not a full RUSLE2 run, measured loss, delivered sediment, gully loss or landslide forecast. Local factors and uncertainty need review.
Method sources. Verified published formula. USLE factor product. Government publication — United States Department of Agriculture Forest Service. 1980 technical publication SA-TP 11; Universal Soil Loss Equation, printed page 2; metric conversion appendix, printed page 40. https://www.ars.usda.gov/ARSUserFiles/60600505/RUSLE/A%20guide%20for%20predicting%20sheet%20and%20rill%20erosion%20on%20forest%20land.pdf. The historical source verifies the factor product. Local factor choice and suitability still need confirmation; this is not a full RUSLE2 implementation.
Domain variants. erosion.
OPTIONS Alternative appraisal
Decision example. Compare potential settlement areas.
affordability difference = available budget − estimated option cost
Inputs and units. Option cost (LKR); Available budget (LKR); Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference.
Worked example. DEC-DP01-007 - Infill near existing services, 2025. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Use existing nearby roads and services.; Resource needs and adverse effects = Check vacant-site capacity, tenure and pressure on existing services.; Required records available for this option = Not provided; Reference for the required records = Not provided; Applicable conditions, check result and supporting reference = Not provided. Budget remaining after option = 300,000 LKR. 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 check: Obtain the missing records before choosing. Realistic sample data.
Changed example. Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Budget remaining after option = 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Without Reference for the required records, 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.
Procedure. 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.
Limits. A budget surplus does not establish a suitable settlement location.
Method sources. Validation required. DD-LOCAL - SHARED domain decision contracts. Domain decision rules and matching fictional examples.
Domain variants. options.
COMPOSITION Composition without false aggregation
Decision example. Plan seed support around observed rice-category uptake.
category share = 100 × category count ÷ sum of compatible category counts
Inputs and units. Distinct eligible original plots (plots); Sown area recorded separately (ha).
Worked example. DEC-DP03-001 — Bg 300, 2025. Distinct eligible original plots = 107 plots; Sown area recorded separately = 115 ha. Plot count = 107 plots; Share of eligible plots = 18.259 %; Share of recorded sown area = 14.303 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Distinct eligible original plots = 108. Plot count = 108 plots. Without Distinct eligible original plots, the required result is withheld.
Procedure. Plot share =100 × distinct eligible plots in category / eligible plots in all categories. Sown-area shares use a separate hectare denominator; grouped inputs do not verify plot identity.
Limits. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. fragmentation, erosion area, rice plots, variety area, export composition, feedback.
TREND Trend with uncertainty
Decision example. Review long-term trends in homogeneous station records.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
display the observed value against its recorded observation period
Inputs and units. Comparable observation (°C).
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Comparable observation = 28.381. Observed value = 28.381 °C. Without Comparable observation, the required result is withheld.
Procedure. Display dated air temperatures and their mean/sample standard deviation in °C. Celsius has an arbitrary zero; do not report relative percentage change or a coefficient of variation.
Limits. Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. trend, groundwater trend.
COST Unit cost and cost drivers
Decision example. Compare conservation cost per verified treated hectare.
unit cost = (labour + materials + other costs) ÷ verified output
Inputs and units. Labour cost (LKR); Material/input cost (LKR); Other non-overlapping cost (LKR); Verified matching hectares (ha).
Worked example. DEC-DP02-017 — Laggala Pallegama — conservation economics, 2025. Labour cost = 180,000 LKR; Material/input cost = 255,000 LKR; Other non-overlapping cost = 62,000 LKR; Verified matching hectares = 5.4 ha. Cost per matching unit = 92,037.037 LKR/ha; Total cost = 497,000 LKR. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Labour cost = 180,001. Cost per matching unit = 92,037.222 LKR/ha. Without Labour cost, the required result is withheld.
Procedure. Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period.
Limits. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. cost ha, survey cost, damage loss, food basket, input expenditure, cost output, tonne km, verification cost.
WATER Crop water requirement
Decision example. Prepare crop-stage irrigation recommendations.
ETc = ETo × Kc
net = max(0, ETc + DP + dS − (P − RO) − CR)
gross = net × area × 10 ÷ efficiency
ETo is reference evapotranspiration; Kc is the crop coefficient; DP is deep percolation or the stated paddy allowance; dS is the desired increase in stored water; P minus RO is rainfall after runoff; CR is capillary contribution. Net is in mm/day; area is in ha; efficiency is a fraction. Set inapplicable allowances to zero.
Inputs and units. Irrigated crop area (ha); Reference evapotranspiration (mm/day); Crop coefficient (ratio); Rainfall reaching the field after runoff (mm/day); Deep percolation and paddy allowance (mm/day); Capillary contribution (mm/day); Desired change in stored soil water (mm/day); Field application efficiency (fraction).
Worked example. DEC-DP03-003 — Laggala Pallegama — irrigation advice, 2025. Irrigated crop area = 85 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction. Gross daily irrigation requirement = 6,687.5 m³/day; Net field requirement = 5.35 mm/day. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Irrigated crop area = 85.85. Gross daily irrigation requirement = 6,754.375 m³/day. Without Irrigated crop area, the required result is withheld.
Procedure. ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency.
Limits. The full local balance, rooting depth, stress, crop stage and operating constraints still matter. The paddy allowance is explicit and must be zero where inapplicable. This is not an authorized reservoir release.
Method sources. Verified published component. Crop evapotranspiration ETc component. Institution publication — Food and Agriculture Organization of the United Nations. Chapter 5, Crop coefficient approach, equation 56. https://www.fao.org/4/X0490E/x0490e0a.htm. This verifies the ETc component only. Local water-balance allowances, coefficients and operating decisions still need confirmation.
Domain variants. water.
VARIANCE Plan versus actual
Decision example. Investigate differences between planned and actual use.
variance = actual − plan
Inputs and units. Hectares planned for the selected land-use class (ha); Hectares observed in that same class (ha).
Worked example. DEC-DP01-017 — Laggala Pallegama — plan implementation, 2025. Hectares planned for the selected land-use class = 100 ha; Hectares observed in that same class = 90 ha. Difference = -10 ha; Relative change = -10 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Hectares planned for the selected land-use class = 101. Difference = -11 ha. Without Hectares planned for the selected land-use class, the required result is withheld.
Procedure. Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. variance, dated variance, cost progress.
REPEAT Repeated support or overlapping claims
Decision example. Review repeated farmer assistance before new allocation.
overlap = max(0, min(end1, end2) − max(start1, start2) + 1)
Inputs and units. Permitted recipient/service reference; Support purpose; Earlier support period begins; Earlier support period ends; Other support period begins; Other support period ends; Same purpose and qualifying unit.
Worked example. DEC-DP04-002 — Laggala Pallegama — support overlap, 2025. Permitted recipient/service reference = Laggala Pallegama — support overlap; Support purpose = Sample seasonal input support; Earlier support period begins = 2025-01-01; Earlier support period ends = 2025-06-30; Other support period begins = 2025-05-01; Other support period ends = 2025-08-31; Same purpose and qualifying unit = Yes. Overlapping days = 61 days. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Other support period begins = 2025-01-01; Other support period ends = 2025-06-30. Overlapping days = 181 days. Without Permitted recipient/service reference, the required result is withheld.
Procedure. Compare the same permitted entity, purpose and qualifying unit. Intersect dated support intervals; overlapping support is a review flag, not proof of duplicate entitlement.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. repeat.
QUEUE Age due date and response
Decision example. Clear delayed farmer-service requests.
past due = max(0, assessment date − due date), when open
Inputs and units. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed.
Worked example. DEC-DP04-004 — Laggala Pallegama — agrarian services, 2025. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Open days past due = 29 days; Calendar age = 90 days. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Received or defect observed = 2025-03-31. Calendar age = 91 days. Without Received or defect observed, the required result is withheld.
Procedure. Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.
Limits. Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. queue.
FRESH Observation freshness and completeness
Decision example. Repair incomplete soil and weather observation coverage.
completeness = 100 × valid received observations ÷ scheduled observations
Inputs and units. Expected observations in the window (observations); Distinct valid observations (observations); Latest valid observation; Assessment date; Required observation interval (days).
Worked example. DEC-DP02-014 — Laggala Pallegama — monitoring network, 2025. Expected observations in the window = 30 observations; Distinct valid observations = 24 observations; Latest valid observation = 2025-06-28; Assessment date = 2025-06-30; Required observation interval = 1 days. Completeness = 80 %; Age of latest observation = 2 days; Missing observations = 6 observations. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Expected observations in the window = 31. Completeness = 77.419 %. Without Expected observations in the window, the required result is withheld.
Procedure. Completeness = 100 × valid / expected. Age = assessment date − latest valid observation; compare with the explicitly supplied interval.
Limits. A recent observation does not fill earlier gaps. Unknown schedule or observation time cannot establish freshness.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. fresh.
BALANCE Physical mass or water balance
Decision example. Review storage consequences of proposed releases.
closing storage = opening + inflows − releases/transfers − other outflows
Inputs and units. Opening storage (m³); All measured inflows and transfers in (m³); Releases and transfers out (m³); Evaporation and other outflows (m³); Independently observed closing storage (m³).
Worked example. DEC-DP05-004 — Laggala Pallegama — reservoir operation, 2025. Opening storage = 160,000 m³; All measured inflows and transfers in = 48,000 m³; Releases and transfers out = 35,000 m³; Evaporation and other outflows = 9,000 m³; Independently observed closing storage = 163,500 m³. Calculated closing storage = 164,000 m³; Observed minus calculated closing = -500 m³. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Opening storage = 160,001. Calculated closing storage = 164,001 m³. Without Opening storage, the required result is withheld.
Procedure. Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing.
Limits. Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. cash balance, balance, aquifer balance, cash timing.
SURVIVAL Cohort survival and retention
Decision example. Target maintenance to poorly surviving planting cohorts.
Calculation or steps. lower = 100 × survivors ÷ cohort; upper = 100 × (survivors + unknown) ÷ cohort.
Inputs and units. Original cohort (plants); Known surviving original members (plants); Known failed original members (plants); Original members with unknown follow-up (plants); Replacements in a separate cohort (plants).
Worked example. DEC-DP07-003 — Laggala Pallegama — restoration survival, 2025. Original cohort = 450 plants; Known surviving original members = 351 plants; Known failed original members = 70 plants; Original members with unknown follow-up = 29 plants; Replacements in a separate cohort = 18 plants. Confirmed survival lower bound = 78 %; Survival upper bound = 84.444 %; Unknown follow-up = 29 plants. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Known surviving original members = 352; Known failed original members = 69. Confirmed survival lower bound = 78.222 %. Without Original cohort, the required result is withheld.
Procedure. Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it.
Limits. These bounds account for unknown status; they are not statistical confidence intervals. Use actual follow-up dates and distinguish cohort membership from repeated visits.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. survival, business retention, followup retention.
ANOMALY Departure from a reviewed reference
Decision example. Issue evidence packages for local agricultural advisories.
departure = current observation − comparable baseline
Inputs and units. Comparable seasonal rainfall reference (mm); Observed seasonal rainfall (mm).
Worked example. DEC-DP02-013 — Laggala Pallegama — agroclimate advice, 2025. Comparable seasonal rainfall reference = 120 mm; Observed seasonal rainfall = 84 mm. Difference = -36 mm; Relative change = -30 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Comparable seasonal rainfall reference = 121. Difference = -37 mm. Without Comparable seasonal rainfall reference, the required result is withheld.
Procedure. Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. anomaly.
SPELL Dry or wet spell duration
Decision example. Identify prolonged rainfall spells requiring advisory review.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
dry run continues only across observed consecutive dry days
Inputs and units. Observation day; Daily rainfall (mm); Example dry-day threshold (mm); Day classified as dry when rainfall.
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Daily rainfall = 4.04. Daily rainfall = 4.04 mm. Without Observation day, the required result is withheld.
Procedure. Count consecutive dated observations satisfying the stated rainfall rule. Missing days interrupt a spell; do not count unknown rain as zero.
Limits. The example threshold is configurable and is not an official warning criterion.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. spell.
SPI Standardized precipitation index
Decision example. Determine where historical rainfall supports SPI analysis.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
completeness = 100 × valid monthly observations ÷ expected observations
Inputs and units. Complete comparable baseline years (years); Expected monthly observations (observations); Valid comparable monthly observations (observations); Proposed accumulation period; Station history and series homogeneity checked; Distribution fit and zero-rainfall handling documented.
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Valid comparable monthly observations = 351. Baseline completeness = 97.5 %. Without Complete comparable baseline years, the required result is withheld.
Procedure. Show valid/expected monthly coverage and complete baseline years. Assess distribution fit, zero rainfall, timescale and homogeneity separately; no SPI is invented.
Limits. WMO recommends a long rainfall record, ideally at least30 years. Readiness counts alone do not validate the fitted SPI method.
Method sources. Validation required. S82 — WMO No 1090; SPI calculation and interpretation guidance; DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. spi.
LOSS Loss measurement by supply chain stage
Decision example. Select crop stages needing loss-reduction measures.
Calculation or steps. unaccounted = input − output − by-products − closing stock − transfers out; share = 100 × unaccounted ÷ input.
Inputs and units. Batch input on stated moisture basis (kg); Saleable output (kg); Usable by-product (kg); Closing stock (kg); Documented transfers out (kg).
Worked example. DEC-DP03-014 — Laggala Pallegama — post-harvest loss, 2025. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Batch input on stated moisture basis = 1,201. Unaccounted physical share = 6.744 %. Without Batch input on stated moisture basis, the required result is withheld.
Procedure. Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input.
Limits. Use a consistent moisture basis and process boundary. Unaccounted mass is not automatically avoidable food loss or spoilage.
Method sources. Validation required. S57 — Full method locator not established; DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. loss.
MARGIN Enterprise gross margin and break even
Decision example. Identify crop enterprises with weak gross margins.
gross margin = saleable quantity × realized unit price − variable cost
Inputs and units. Saleable output (kg); Realized price (LKR/kg); Variable costs (LKR); Matching crop area (ha); Crop and saleable-output basis.
Worked example. DEC-DP03-017 — Laggala Pallegama — farm income, 2025. Saleable output = 4,500 kg; Realized price = 110 LKR/kg; Variable costs = 360,000 LKR; Matching crop area = 1 ha; Crop and saleable-output basis = Paddy rough rice / fictional one-hectare crop enterprise / same season. Enterprise gross margin = 135,000 LKR; Gross margin per hectare = 135,000 LKR/ha; Variable-cost break-even price = 80 LKR/kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Saleable output = 4,501. Enterprise gross margin = 135,110 LKR. Without Saleable output, the required result is withheld.
Procedure. Gross margin = saleable output × realized price − variable costs. Divide by matching hectares for margin/ha; variable-cost break-even price = variable costs / output.
Limits. Keep fixed costs, family-labour opportunity cost, taxes and financing identifiable. Gross margin is not net profit. Crop, prices and costs are fictional coherent enterprise assumptions. Gross margin excludes fixed and financing costs; it is not household income or net profit.
Method sources. Verified published formula. Enterprise gross margin. Institution publication — Food and Agriculture Organization of the United Nations. Chapter 4, Gross margin and section 4.7.1. https://www.fao.org/4/W7365E/w7365e07.htm. Per-hectare and variable-cost break-even outputs are algebraic rearrangements. Local costs, prices and interpretation still need confirmation.
Domain variants. margin.
SUITABILITY Expert reviewed suitability
Decision example. Shortlist land uses compatible with local conditions.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Land polygon; Land polygon evidence reference; soil depth; soil depth evidence reference; slope degrees; slope degrees evidence reference; rainfall; rainfall evidence reference; water access; water access evidence reference; crop requirements; crop requirements evidence reference.
Worked example. DEC-DP01-005 — Laggala Pallegama — agricultural suitability, 2025. Land polygon = Missing; Land polygon evidence reference = ; soil depth = Documented; soil depth evidence reference = Sample Laggala Pallegama field register / 2025; slope degrees = Documented; slope degrees evidence reference = Sample Laggala Pallegama field register / 2025; rainfall = Documented; rainfall evidence reference = Sample Laggala Pallegama field register / 2025; water access = Documented; water access evidence reference = Sample Laggala Pallegama field register / 2025; crop requirements = Documented; crop requirements evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Land polygon = Documented; Land polygon evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Land polygon, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. suitability.
QUALITY Applicable quality limit comparison
Decision example. Refer nutrient and acidity limitations for agronomic advice.
Calculation or steps. lower bound ≤ matching measured result ≤ upper bound.
Inputs and units. Parameter and applicable use; Measured result (pH); Example lower comparison bound (pH); Example upper comparison bound (pH); Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date.
Worked example. DEC-DP02-005 - Laggala Pallegama — soil fertility, 2025. Parameter and applicable use = Soil pH; Measured result = 6.2 pH; Example lower comparison bound = 5.5 pH; Example upper comparison bound = 7.5 pH; Original and limit unit = pH; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = Not provided; Sample observation date = Not provided. Measured value = 6.2 pH. The supplied Soil pH result is 6.2 pH. Its stated comparison range is 5.5 to 7.5 pH. Within example comparison bounds. Next check: Obtain the missing evidence listed below. Realistic sample data.
Changed example. Measured result = 6.262; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Measured value = 6.262 pH. Next check: Review the sample, analytical method and comparison basis. Without Parameter and applicable use, No usable result. Parameter and applicable use
Procedure. Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status.
Limits. Example bounds establish no compliance or diagnosis. Ambient, drinking-water, effluent, crop, food, air and noise standards are not interchangeable. A censored result is not an exact zero.
Method sources. Validation required. DD-LOCAL - SHARED domain decision contracts. Domain decision rules and matching fictional examples.
Domain variants. quality.
SCHEDULE Resource constrained scheduling
Decision example. Schedule priority land-use map updates.
duration = end date − start date; check windows and conflicts
Inputs and units. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort (hours); Available resource effort (hours); Predecessor task reference; Mandatory permits and prerequisites.
Worked example. DEC-DP01-020 — Laggala Pallegama — survey scheduling, 2025. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Planned duration = 3 days; Resource hours remaining = 8 hours. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Required resource effort = 16.16. Resource hours remaining = 7.84 hours. Without Required resource, the required result is withheld.
Procedure. 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.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. schedule.
YIELD Productivity and efficiency
Decision example. Select improvements for low water productivity.
Calculation or steps productivity = matching output ÷ resource input; multiply by 100 only for the declared output share variants.
Inputs and units. Saleable crop output (kg); Matching irrigation water input (m³).
Worked example. DEC-DP02-010 — Laggala Pallegama — on-farm irrigation, 2025. Saleable crop output = 19,780 kg; Matching irrigation water input = 7,200 m³. Crop water productivity = 2.747 kg/m³. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Saleable crop output = 19,781. Crop water productivity = 2.747 kg/m³. Without Saleable crop output, the required result is withheld.
Procedure. Saleable crop output / Matching irrigation water input, for the same product, process and period.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. water productivity, crop yield, pump energy, drilling, labour, export unit value, resource efficiency, mass conversion, process energy.
DISTRIBUTION Distribution and outlier review
Decision example. Identify markets requiring closer price-distribution study.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
mean = sum(x) ÷ n; sample SD = sqrt(sum((x − mean)^2) ÷ (n − 1))
Inputs and units. Comparable observation (LKR/kg).
Worked example. DEC-DP25-004 — Laggala Pallegama — market comparisons, 2025. Comparable observation = 104 LKR/kg. Observed value = 104 LKR/kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Comparable observation = 105. Observed value = 105 LKR/kg. Without Comparable observation, the required result is withheld.
Procedure. Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean.
Limits. Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. distribution.
CONCENTRATION Concentration and dependence
Decision example. Identify excessive dependence on few export markets.
Calculation or steps concentration = sum of squared fractional category shares.
Inputs and units. Recorded export value in this distinct destination (LKR).
Worked example. DEC-DP26-002 — India, 2025. Recorded export value in this distinct destination = 90,000,000 LKR. Category amount = 90,000,000 LKR; Share of selected total = 45 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Recorded export value in this distinct destination = 90,000,001. Concentration (0–1) = 0.289. Without Recorded export value in this distinct destination, the required result is withheld.
Procedure. Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale.
Limits. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy. The fictional selected spice-export portfolio is not a national export total. No institutional concentration threshold is supplied.
Method sources. Verified published component. HHI concentration component. Government publication — United States Department of Justice. Definition and four-firm worked example. https://www.justice.gov/atr/herfindahl-hirschman-index. The screen uses fractional shares on a 0–1 scale, equivalent to the published percentage-share score divided by 10000. Local exposure categories and policy thresholds are not verified by this source.
Domain variants. concentration.
MATCH Supply demand compatibility matching
Decision example. Match verified exporter offers with buyer requirements.
supply difference = available uncommitted supply − requested demand
Inputs and units. Offered product and grade; Required product and grade; Available uncommitted quantity (kg); Required quantity (kg); Supply available from; Supply available until; Delivery window begins; Delivery window ends; Required quality, rights and conditions.
Worked example. DEC-DP26-008 — Laggala Pallegama — buyer matching, 2025. Offered product and grade = Cleaned dry pepper / whole grain; Required product and grade = Cleaned dry pepper / whole grain; Available uncommitted quantity = 1,200 kg; Required quantity = 1,500 kg; Supply available from = 2025-06-01; Supply available until = 2025-06-20; Delivery window begins = 2025-06-05; Delivery window ends = 2025-06-18; Required quality, rights and conditions = Met. Supply minus demand = -300 kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Available uncommitted quantity = 1,201. Supply minus demand = -299 kg. Without Offered product and grade, the required result is withheld.
Procedure. Compare the same specification and unit, uncommitted quantity and overlapping delivery windows. Keep mandatory quality and use conditions explicit.
Limits. A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. match, human match, plot match.
CAPACITY Capacity gap assessment
Decision example. Allocate staff to agrarian centres with workload gaps.
capacity balance = usable staffed capacity − required capacity
Inputs and units. Demand in the selected period (staff hours); Rated capacity for that period (staff hours); Unavailable or restricted capacity (staff hours).
Worked example. DEC-DP04-014 — Laggala Pallegama — service centres, 2025. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Demand in the selected period = 151. Usable capacity minus demand = -16 staff hours. Without Demand in the selected period, the required result is withheld.
Procedure. Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand.
Limits. Match peak/average basis, time window, skill, staffing, accessibility and other binding constraints. One aggregate capacity does not override a safety constraint.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. capacity.
RISK Reviewed risk and control assessment
Decision example. Prepare response options from authorized hydrological evidence.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. River levels; River levels evidence reference; official forecast; official forecast evidence reference; flood exposure; flood exposure evidence reference; warning protocol; warning protocol evidence reference; evacuation constraints; evacuation constraints evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient.
Worked example. DEC-DP05-006 — Laggala Pallegama — flood readiness, 2025. River levels = Missing; River levels evidence reference = ; official forecast = Documented; official forecast evidence reference = Sample Laggala Pallegama field register / 2025; flood exposure = Documented; flood exposure evidence reference = Sample Laggala Pallegama field register / 2025; warning protocol = Documented; warning protocol evidence reference = Sample Laggala Pallegama field register / 2025; evacuation constraints = Documented; evacuation constraints evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. River levels = Documented; River levels evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without River levels, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Show the hazard, exposure and verified controls separately. No generic score, probability, diagnosis, site clearance or official warning is derived from a count.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. risk.
INSPECT Inspection and evidence checklist
Decision example. Follow up incomplete conservation works.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Work ID; Work ID evidence reference; approved design; approved design evidence reference; inspection items; inspection items evidence reference; photographs; photographs evidence reference; completion evidence; completion evidence evidence reference.
Worked example. DEC-DP02-012 — Laggala Pallegama — conservation inspection, 2025. Work ID = Missing; Work ID evidence reference = ; approved design = Documented; approved design evidence reference = Sample Laggala Pallegama field register / 2025; inspection items = Documented; inspection items evidence reference = Sample Laggala Pallegama field register / 2025; photographs = Documented; photographs evidence reference = Sample Laggala Pallegama field register / 2025; completion evidence = Documented; completion evidence evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Work ID = Documented; Work ID evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Work ID, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. inspect.
ELIGIBILITY Rules based referral for authorized determination
Decision example. Refer land-conversion applications for determination.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Application ID; Application ID evidence reference; current use; current use evidence reference; proposed use; proposed use evidence reference; ownership evidence; ownership evidence evidence reference; applicable rules; applicable rules evidence reference; objections; objections evidence reference.
Worked example. DEC-DP01-006 — Laggala Pallegama — land conversion, 2025. Application ID = Missing; Application ID evidence reference = ; current use = Documented; current use evidence reference = Sample Laggala Pallegama field register / 2025; proposed use = Documented; proposed use evidence reference = Sample Laggala Pallegama field register / 2025; ownership evidence = Documented; ownership evidence evidence reference = Sample Laggala Pallegama field register / 2025; applicable rules = Documented; applicable rules evidence reference = Sample Laggala Pallegama field register / 2025; objections = Documented; objections evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Application ID = Documented; Application ID evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Application ID, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. eligibility.
FINANCE Discounted cash flow appraisal
Decision example. Appraise reservoir rehabilitation cash-flow alternatives.
Calculation or steps NPV = sum of annual net cash flow ÷ (1 + discount rate fraction) raised to the year, for years 1 to n, less initial investment.
Inputs and units. Initial investment (LKR); Net cash flow year1 (LKR); Net cash flow year2 (LKR); Net cash flow year3 (LKR); Net cash flow year4 (LKR); Net cash flow year5 (LKR); Residual value at end of year5 (LKR); Example discount rate (%).
Worked example. DEC-DP05-017 — Base cash-flow scenario, 2025. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Five-year net present value = 109,847.353 LKR. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Initial investment = 2,400,001. Five-year net present value = 109,846.353 LKR. Without Initial investment, the required result is withheld.
Procedure. NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5.
Limits. Match currency, price year, real/nominal basis and cash-flow timing. The example rate and five-year horizon are assumptions, not institutional financing terms; no credit approval follows.
Method sources. Verified published formula. Discounted cash-flow NPV. Institution publication — Food and Agriculture Organization of the United Nations. Sections 2.2.2 and 2.2.3, discounting and Net Present Value. https://www.fao.org/4/w8212e/w8212e06.htm. The five-year horizon, discount rate and cash assumptions are local settings. Verification does not approve an investment or loan.
Domain variants. finance.
DEBT Debt service assessment
Decision example. Assess debt-service coverage under lender-defined scenarios.
debt service coverage = cash available for debt service ÷ scheduled principal and interest
Inputs and units. Cash available for debt service (LKR); Scheduled principal for same period (LKR); Scheduled interest for same period (LKR); Repayment and cash-flow period.
Worked example. DEC-DP38-002 — Laggala Pallegama — repayment capacity, 2025. Cash available for debt service = 860,000 LKR; Scheduled principal for same period = 500,000 LKR; Scheduled interest for same period = 120,000 LKR; Repayment and cash-flow period = Sample annual period. Debt-service coverage = 1.387 ratio; Cash after scheduled debt service = 240,000 LKR. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Cash available for debt service = 860,001. Debt-service coverage = 1.387 ratio. Without Cash available for debt service, the required result is withheld.
Procedure. Debt-service coverage = cash available / (principal + interest) for the same period. Zero scheduled debt has no coverage ratio.
Limits. No lender covenant, credit decision, borrower eligibility or legal consequence is inferred. Seasonal repayment timing and downside scenarios remain explicit.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. debt.
FUNDING Funding and commitment reconciliation
Decision example. Reconcile provincial agriculture funding and verified activities.
funding gap = financing need − confirmed commitments
Inputs and units. Approved financing need (LKR); Confirmed commitments (LKR); Funds actually disbursed (LKR); Verified eligible expenditure (LKR).
Worked example. DEC-DP10-017 — Laggala Pallegama — budget delivery, 2025. Approved financing need = 3,500,000 LKR; Confirmed commitments = 2,650,000 LKR; Funds actually disbursed = 1,640,000 LKR; Verified eligible expenditure = 1,200,000 LKR. Unfunded need = 850,000 LKR; Committed but not disbursed = 1,010,000 LKR; Disbursed but not spent = 440,000 LKR. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Approved financing need = 3,500,001. Unfunded need = 850,001 LKR. Without Approved financing need, the required result is withheld.
Procedure. Unfunded = need − commitments. Undisbursed = commitments − disbursements. Unspent = disbursements − eligible spending.
Limits. Keep commitments, cash receipts, expenditure and verified physical outputs separate. Negative balances flag overcommitment or reconciliation; no automatic accounting adjustment.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. funding.
CARBON Carbon stock and stock change assessment
Decision example. Review inventory evidence for carbon-stock estimates.
carbon stock change = (current carbon density − baseline carbon density) × inventory area
Inputs and units. Earlier carbon density (t C/ha); Later carbon density (t C/ha); Same inventory area (ha); Included pools and allometry references.
Worked example. DEC-DP07-013 — Laggala Pallegama — forest carbon, 2025. Earlier carbon density = 100 t C/ha; Later carbon density = 90 t C/ha; Same inventory area = 85 ha; Included pools and allometry references = Sample matching biomass pools; source model required. Carbon stock change = -850 t C; Carbon-density change = -10 t C/ha. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Earlier carbon density = 101. Carbon stock change = -935 t C. Without Earlier carbon density, the required result is withheld.
Procedure. (Later carbon density − earlier carbon density) × same inventory area, with identical pools, method and boundaries.
Limits. Inventory plots, allometry and uncertainty remain required evidence. Stock change is not an issued carbon credit, additionality test or payable service.
Method sources. Verified published component. Carbon stock-difference component. Institution publication — Intergovernmental Panel on Climate Change. Section 2.3.1.1, equation 2.8, stock-difference method. https://www.ipcc-nggip.iges.or.jp/public/2006gl/pdf/4_Volume4/V4_02_Ch2_Generic.pdf. The screen reports the period total. IPCC annualisation requires elapsed years. Pools, inventory inputs and local application still need confirmation.
Domain variants. carbon.
SOILCARBON Soil carbon stock comparison
Decision example. Select sites for comparable soil-carbon monitoring.
Calculation or steps soil carbon stock = carbon percent ÷ 100 × bulk density × depth × 10000 × (1 − coarse fragment percent ÷ 100).
Inputs and units. Soil organic carbon (%); Fine-earth bulk-density basis (t/m³); Sample depth (m); Coarse-fragment volume fraction (%); Sampling depth, design and density convention.
Worked example. DEC-DP02-004 — Laggala Pallegama — soil carbon, 2025. Soil organic carbon = 1.8 %; Fine-earth bulk-density basis = 1.25 t/m³; Sample depth = 0.3 m; Coarse-fragment volume fraction = 12 %; Sampling depth, design and density convention = Sample matched depth and fine-earth convention. Soil-carbon stock = 59.4 t C/ha. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Soil organic carbon = 1.818. Soil-carbon stock = 59.994 t C/ha. Without Soil organic carbon, the required result is withheld.
Procedure. (Organic carbon% /100) × bulk density × depth ×10000 × (1−coarse% /100). Confirm that the density and coarse-fragment conventions are mutually consistent.
Limits. A carbon concentration is not a stock. Change comparisons require consistent depth/mass, sampling, density convention and uncertainty review.
Method sources. Verified published formula. Soil-carbon stock with volume correction. Institution publication — Intergovernmental Panel on Climate Change. Section 4.3.3.5.4, equation 4.3.3, printed page 4.106, PDF page 18. https://www.ipcc-nggip.iges.or.jp/public/gpglulucf/gpglulucf_files/Chp4/Chp4_3_Projects.pdf. The screen converts carbon percent to a fraction and uses the published coarse-fragment volume convention. Sampling and bulk-density conventions still need confirmation.
Domain variants. soilcarbon.
BIODIVERSITY Comparable biodiversity assessment
Decision example. Select comparable forest biodiversity surveys.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
display observed species richness alongside survey effort
Inputs and units. Observed distinct species (species); Survey effort (hours); Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed.
Worked example. DEC-DP07-018 — Laggala Pallegama — biodiversity monitoring, 2025. Observed distinct species = 28 species; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes. Observed richness = 28 species; Recorded effort = 18 hours. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Observed distinct species = 29. Observed richness = 29 species. Without Observed distinct species, the required result is withheld.
Procedure. Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred.
Limits. Observed richness is not population size or occupancy. Comparable effort alone does not remove detection bias or establish a biodiversity trend.
Method sources. Validation required. DD-GBIF — Version1.0.2, sections5.4 to5.7 and7.3; DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. biodiversity.
IMPACT Outcome and attribution evaluation
Decision example. Evaluate conservation practice outcomes.
Calculation or steps difference in differences = (treatment after − treatment before) − (comparison after − comparison before).
Inputs and units. Treatment Measured runoff before (mm/season); Treatment Measured runoff after (mm/season); Comparison Measured runoff before (mm/season); Comparison Measured runoff after (mm/season); Study design and comparability evidence; Outcome definition, method and reference basis.
Worked example. DEC-DP02-016 — Laggala Pallegama — demonstration trials, 2025. Treatment Measured runoff before = 42 mm/season; Treatment Measured runoff after = 59 mm/season; Comparison Measured runoff before = 39 mm/season; Comparison Measured runoff after = 46 mm/season; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Measured runoff /example matching definition1. Difference in changes = 10 mm/season. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Treatment Measured runoff before = 42.42. Difference in changes = 9.58 mm/season. Without Treatment Measured runoff before, the required result is withheld.
Procedure. (Treatment after−before) − (comparison after−before), using the same outcome definition and periods.
Limits. The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence.
Method sources. Verified published formula. Difference-in-differences arithmetic. Institution publication — World Bank. Chapter 7, table 7.2, printed page 140, PDF page 170. https://documents1.worldbank.org/curated/en/698441474029568469/pdf/Impact-evaluation-in-practice.pdf. The formula is verified. Causal interpretation still requires a defensible study design, comparison and assumptions.
Domain variants. impact, study design.
PRICE Comparable market price analysis
Decision example. Investigate large comparable farmgate wholesale and retail spreads.
net quote return = sell × (1 − loss fraction) − buy − transfer cost
Inputs and units. Comparable purchase quotation (LKR/kg); Comparable selling quotation (LKR/kg); Non-overlapping transfer costs (LKR/kg); Expected saleable mass loss (%); Product, grade and price basis.
Worked example. DEC-DP25-001 — Laggala Pallegama — price spreads, 2025. Comparable purchase quotation = 180 LKR/kg; Comparable selling quotation = 222 LKR/kg; Non-overlapping transfer costs = 20 LKR/kg; Expected saleable mass loss = 5 %; Product, grade and price basis = Tomato / same stated grade / per purchased kilogram. Quoted net return per purchased kg = 10.9 LKR/kg; Unadjusted quoted spread = 42 LKR/kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Comparable purchase quotation = 181. Quoted net return per purchased kg = 9.9 LKR/kg. Without Comparable purchase quotation, the required result is withheld.
Procedure. Quoted spread = sell−buy. Net scenario return per purchased kg = sell×(1−loss%/100)−buy−matching transfer costs.
Limits. Use matching grade, price date, currency, mass basis and payment terms. This quotation scenario excludes unlisted costs and is not realized profit or a forecast.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. price, buyer offer, procurement offer.
VOLATILITY Price variability and seasonality
Decision example. Prioritize commodities with unusual price variability.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
sample CV = 100 × sample SD ÷ positive mean
Inputs and units. Comparable observation (LKR/kg).
Worked example. DEC-DP25-002 — Laggala Pallegama — price volatility, 2025. Comparable observation = 104 LKR/kg. Observed value = 104 LKR/kg. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Comparable observation = 105. Observed value = 105 LKR/kg. Without Comparable observation, the required result is withheld.
Procedure. Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean.
Limits. Match definitions, methods, grade, location and reference basis. Gaps are not joined. Descriptive variation is not a forecast, causal effect or significant trend.
Method sources. Verified published formula. Sample coefficient of variation. Government publication — National Institute of Standards and Technology United States. Description, sample coefficient of variation and ratio-scale restrictions. https://www.itl.nist.gov/div898/software/dataplot/refman2/auxillar/coefvari.htm. Use a meaningful zero and positive mean. Local series selection and decision limits still need confirmation.
Domain variants. volatility.
INVENTORY Stock expiry and reorder planning
Decision example. Plan seed procurement against seasonal demand.
available stock = usable stock − confirmed commitments
Inputs and units. Physical stock (kg seed); Quarantined stock (kg seed); Expired stock (kg seed); Committed usable stock (kg seed); Additional demand (kg seed); Supplier lead time (days); Remaining shelf life of usable stock (days).
Worked example. DEC-DP03-010 — Laggala Pallegama — seed supply, 2025. Physical stock = 1,200 kg seed; Quarantined stock = 100 kg seed; Expired stock = 50 kg seed; Committed usable stock = 740 kg seed; Additional demand = 500 kg seed; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Uncommitted usable stock = 310 kg seed; Additional demand gap = 190 kg seed. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Physical stock = 1,201. Uncommitted usable stock = 311 kg seed. Without Physical stock, the required result is withheld.
Procedure. Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available).
Limits. Stock must be compatible by item, lot, condition, expiry and delivery window. Do not allocate quarantined/expired stock or silently erase overcommitment.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. inventory.
MAINTENANCE Asset maintenance prioritization
Decision example. Prioritize repair packages within engineering and budget limits.
past due = max(0, assessment date − due date), when open
Inputs and units. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed.
Worked example. DEC-DP05-009 — Laggala Pallegama — canal rehabilitation, 2025. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Open days past due = 29 days; Calendar age = 90 days. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Received or defect observed = 2025-03-31. Calendar age = 91 days. Without Received or defect observed, the required result is withheld.
Procedure. Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately.
Limits. Example due dates are not legal service standards. Do not alter statutory deadlines by silently subtracting pauses, or infer severity from age alone.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. maintenance.
FLOW Process progression and conversion
Decision example. Follow up farmers who received technical guidance.
completion share = 100 × completed cases ÷ entered cases
Inputs and units. Distinct farmers receiving the stated guidance (cases); Those farmers reached at follow-up (cases); Those farmers with the stated verified follow-up outcome (cases); Farmers with unknown follow-up (cases).
Worked example. DEC-DP03-019 — Laggala Pallegama — advisory effectiveness, 2025. Distinct farmers receiving the stated guidance = 180 cases; Those farmers reached at follow-up = 132 cases; Those farmers with the stated verified follow-up outcome = 96 cases; Farmers with unknown follow-up = 12 cases. Verified completion share = 53.333 %; Not verified complete = 84 cases; Original cases awaiting review = 48 cases; Reviewed cases not confirmed complete = 36 cases. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Distinct farmers receiving the stated guidance = 181. Verified completion share = 53.039 %. Without Distinct farmers receiving the stated guidance, the required result is withheld.
Procedure. 100 × verified completed members / original unique cohort. Keep unknown follow-up separate; stages are nested, not independent populations.
Limits. Attendance, receipt, adoption, delivered service and outcomes are distinct stages. Repeated visits must not become new people. The follow-up outcome and observation window must be recorded; receipt of advice is not adoption. The original cohort and nested review/completion stages must match; an uncompleted record is not automatically overdue. Unknown follow-up is a subset, not an extra stage.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. flow.
ROUTE Access and logistics comparison
Decision example. Compare access improvements for isolated planning areas.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
display supplied route distance, travel time and vehicle capacity; no route is calculated here
Inputs and units. Supplied journey distance from a documented route survey (km); Supplied journey duration; not calculated here (minutes); Usable vehicle/team capacity (units); Required capacity (units); Access, closures and operating conditions; Operating and service window.
Worked example. DEC-DP01-014 — Laggala Pallegama — service access, 2025. Supplied journey distance from a documented route survey = 24 km; Supplied journey duration; not calculated here = 65 minutes; Usable vehicle/team capacity = 18 units; Required capacity = 15 units; Access, closures and operating conditions = Unresolved; Operating and service window = Sample operating window. Estimated travel time = 65 minutes; Capacity minus demand = 3 units. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Supplied journey duration; not calculated here = 75. Estimated travel time = 75 minutes. Without Supplied journey distance from a documented route survey, the required result is withheld.
Procedure. Compare supplied route times/distances, usable capacity and documented access/window constraints. Display feasible candidates; no route optimization is implied.
Limits. Straight-line distance is not a road route. Example routes establish no current road status, emergency clearance or safe evacuation instruction. This decision view compares supplied journeys. It does not calculate a route or run a coordinate-based analysis.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. route.
PES Environmental service verification and payment proposal
Decision example. Prepare payment proposals only from approved verified conditions.
annual proposal = min(accepted hectares × annual rate, annual cap)
Inputs and units. Agreement and version; Who carries out the work; Who funds the agreement; Area meeting the annual agreement conditions (ha); Illustrative annual rate per accepted hectare (LKR/ha/year); Annual cap for this agreement (LKR/year); Amount already paid for these same annual conditions (LKR); Independent field-check record documented; Rights and voluntary agreement documented; Funding confirmation documented; Field-check and rate references; Confirmed funds available for this annual proposal (LKR).
Worked example. DEC-DP39-011 — Laggala Pallegama farmer group, 2025. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Area meeting the annual agreement conditions = 20 ha; Illustrative annual rate per accepted hectare = 12,500 LKR/ha/year; Annual cap for this agreement = 300,000 LKR/year; Amount already paid for these same annual conditions = 0 LKR; Independent field-check record documented = Documented; Rights and voluntary agreement documented = Documented; Funding confirmation documented = Missing; Field-check and rate references = Example field record / draft annual rate schedule 1; Confirmed funds available for this annual proposal = 200,000 LKR. Calculated annual proposal before payments = 250,000 LKR; Proposal less amount already paid = 250,000 LKR; Amount ready to refer for authorisation = Unavailable LKR. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Area meeting the annual agreement conditions = 21. Calculated annual proposal before payments = 262,500 LKR. Without Agreement and version, the required result is withheld.
Procedure. Annual proposal = min(accepted hectares × annual rate, annual cap). Subtract payments for the same agreement and year. Refer an amount only when required evidence is documented. This screen makes no payment.
Limits. Illustrative watershed-care agreement. Contract rules, rate, payer, monitoring and safeguards need confirmation in Institution review. Maintained hectares do not establish a measured water-quality improvement.
Method sources. Validation required. S60 — Full method locator not established; S61 — Full method locator not established; DD-LOCAL — Domain decision rules and matching fictional examples; PES-FAO — ESA Working Paper 11-20; section 2 printed pages 3–5; sections 3 and 4 on evidence, costs and equity.
PES decisions. DEC-DP39-002 checks physical work only. DEC-DP39-011 calculates the proposal. The 20 separate questions and required evidence are listed in section 6 4 and the decision register.
ACCOUNT Physical and monetary ecosystem accounting
Decision example. Prepare separate physical service accounts.
closing extent = opening extent + additions − reductions
Inputs and units. Opening ecosystem extent (ha); Extent additions (ha); Extent reductions (ha); Measured service flow in the period (m³/year); Service definition and flow unit; Separate monetary valuation method/price year.
Worked example. DEC-DP12-012 — Laggala Pallegama — ecosystem services, 2025. Opening ecosystem extent = 750 ha; Extent additions = 92 ha; Extent reductions = 48 ha; Measured service flow in the period = 120,000 m³/year; Service definition and flow unit = Fictional annual water-provisioning flow to the stated users / m³/year / same accounting boundary; Separate monetary valuation method/price year = Not provided. Closing ecosystem extent = 794 ha; Physical service flow = 120,000 m³/year. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Opening ecosystem extent = 751. Closing ecosystem extent = 795 ha. Without Opening ecosystem extent, the required result is withheld.
Procedure. 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.
Limits. 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.
Method sources. Validation required. S58 — Full method locator not established; DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. account.
CONSENT Consultation and unresolved condition review
Decision example. Follow up unresolved tenure objections.
response share = 100 × participants responding ÷ invited participants
Inputs and units. Distinct relevant people invited (people); People who responded (people); Unresolved issues (issues); Proposal/version being discussed; Required participation channels accessible; Reference for unresolved issues and their progress; Evidence about participation barriers.
Worked example. DEC-DP01-011 - Laggala Pallegama — tenure conflicts, 2025. Distinct relevant people invited = 95 people; People who responded = 68 people; Unresolved issues = 16 issues; Proposal/version being discussed = Sample proposal1; Required participation channels accessible = Unknown; Reference for unresolved issues and their progress = Not provided; Evidence about participation barriers = Not provided. Unresolved issues = 16 issues; Response share = 71.579 %. 16 unresolved issue(s). 71.579% responded; response is not consent. Review the issue references and participation barriers. Next check: Obtain the missing evidence listed below. Realistic sample data.
Changed example. Distinct relevant people invited = 96; Reference for unresolved issues and their progress = DEMO-ISSUE-REGISTER; Evidence about participation barriers = DEMO-PARTICIPATION-REVIEW. Unresolved issues = 16 issues; Response share = 70.833 %. Next check: Review the unresolved issues and participation barriers. Without Distinct relevant people invited, No usable result. Distinct relevant people invited
Procedure. 100 × distinct respondents / invited people. Record unresolved issues individually; one respondent may raise several issues.
Limits. Response, attendance and silence are not consent. Participation does not transfer decision authority or settle rights.
Method sources. Validation required. DD-LOCAL - SHARED domain decision contracts. Domain decision rules and matching fictional examples.
Domain variants. consent.
ACCESS Permission and publication review
Decision example. Check source rights and approval before publishing products.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Product version; Product version evidence reference; forecast validity; forecast validity evidence reference; review; review evidence reference; publication authority; publication authority evidence reference; license; license evidence reference; audience; audience evidence reference.
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Product version = Documented; Product version evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Product version, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. access.
METADATA Dataset fitness and interoperability
Decision example. Correct incomplete land-use layer metadata.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Layer ID; Layer ID evidence reference; scale; scale evidence reference; coordinate system; coordinate system evidence reference; classification edition; classification edition evidence reference; owner; owner evidence reference; survey date; survey date evidence reference.
Worked example. DEC-DP01-019 — Laggala Pallegama — map documentation, 2025. Layer ID = Missing; Layer ID evidence reference = ; scale = Documented; scale evidence reference = Sample Laggala Pallegama field register / 2025; coordinate system = Documented; coordinate system evidence reference = Sample Laggala Pallegama field register / 2025; classification edition = Documented; classification edition evidence reference = Sample Laggala Pallegama field register / 2025; owner = Documented; owner evidence reference = Sample Laggala Pallegama field register / 2025; survey date = Documented; survey date evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Layer ID = Documented; Layer ID evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Layer ID, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. metadata.
REPRODUCE Reproducibility and result verification
Decision example. Review reproducibility of soil and land assessments.
reproduction difference = reproduced result − expected result
Inputs and units. Earlier/source value (t/ha/year); Independently reproduced value (t/ha/year); Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance (t/ha/year); Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer.
Worked example. DEC-DP02-020 — Laggala Pallegama — model assurance, 2025. Earlier/source value = 100 t/ha/year; Independently reproduced value = 90 t/ha/year; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable t/ha/year measure; same input scope; Documented absolute comparison tolerance = 0.01 t/ha/year; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Difference = -10 t/ha/year; Relative change = -10 %. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Earlier/source value = 101. Difference = -11 t/ha/year. Without Earlier/source value, the required result is withheld.
Procedure. 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.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. reproduce.
CLASSIFY Controlled classification and taxonomy review
Decision example. Reconcile inconsistent land and water system codes.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Source system labels; Source system labels evidence reference; official system registry; official system registry evidence reference; geometry edition; geometry edition evidence reference; steward decisions; steward decisions evidence reference.
Worked example. DEC-DP06-020 — Laggala Pallegama — system reporting, 2025. Source system labels = Missing; Source system labels evidence reference = ; official system registry = Documented; official system registry evidence reference = Sample Laggala Pallegama field register / 2025; geometry edition = Documented; geometry edition evidence reference = Sample Laggala Pallegama field register / 2025; steward decisions = Documented; steward decisions evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Source system labels = Documented; Source system labels evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Source system labels, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. classify.
RELIABILITY Service reliability
Decision example. Prioritize aviation meteorological service interruptions.
availability = 100 × (scheduled service time − verified downtime) ÷ scheduled service time
Inputs and units. Scheduled observation window (hours); Union of qualifying outage intervals (hours); Eligible service requests (requests); Failed eligible requests (requests); Measured data-feed transport response time; separate from observation availability (ms).
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Scheduled observation window = 169. Time availability = 92.308 %. Without Scheduled observation window, the required result is withheld.
Procedure. Time availability =100 ×(scheduled−non-overlapping outage)/scheduled. Request success =100 ×(requests−failed)/requests. Response time is a separate measure.
Limits. State maintenance exclusions, operating window, probe, workload and service objective. Observed response time is not a p95 claim unless the percentile is actually measured. These are fictional service-monitoring returns for named airport contexts. No aviation service, warning feed or endpoint is contacted.
Method sources. Validation required. DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. reliability, supply outages.
NRW Non revenue water diagnosis
Decision example. Prioritize systems with large unexplained water balances.
Calculation or steps non revenue water = system input − billed authorized consumption; estimated real loss = input − billed − unbilled authorized use − apparent losses.
Inputs and units. Corrected system input (m³); Billed authorized consumption (m³); Unbilled authorized consumption (m³); Estimated apparent losses (m³).
Worked example. DEC-DP22-001 — Laggala Pallegama — non-revenue water, 2025. Corrected system input = 80,000 m³; Billed authorized consumption = 57,000 m³; Unbilled authorized consumption = 3,200 m³; Estimated apparent losses = 4,500 m³. Non-revenue water = 23,000 m³; NRW share = 28.75 %; Water losses = 19,800 m³; Residual real-loss estimate = 15,300 m³. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Corrected system input = 80,001. Non-revenue water = 23,001 m³. Without Corrected system input, the required result is withheld.
Procedure. NRW=input−billed authorized use. Water losses=NRW−unbilled authorized use. Residual real loss=water losses−estimated apparent losses, only when all components are available.
Limits. NRW is not all leakage. An unknown apparent-loss estimate keeps residual real loss unavailable. Meter uncertainty and matching time/zone boundaries matter.
Method sources. Verified published component. IWA water-balance components. Institution publication — Asian Development Bank. Figure 4, printed page 15; Annex 1 Water Balance Definitions, printed pages 39–41, PDF pages 47–49. https://www.adb.org/sites/default/files/publication/27473/reducing-nonrevenue-water.pdf. Apparent-loss estimates and the residual real-loss estimate remain local inputs with measurement uncertainty.
Domain variants. billed water, leakage evidence.
STAR Specialist species threat and restoration appraisal
Decision example. Refer candidate conservation actions for specialist threat assessment.
Current rule. Use the exact DOMAIN-1 decision variant; the representative example does not establish all local applications.
evidence gaps = count(missing or conflicting required items)
Inputs and units. Species range; Species range evidence reference; threats; threats evidence reference; action feasibility; action feasibility evidence reference; threat reduction evidence; threat reduction evidence evidence reference; uncertainty; uncertainty evidence reference.
Worked example. DEC-DP19-004 — Laggala Pallegama — threat reduction, 2025. Species range = Missing; Species range evidence reference = ; threats = Documented; threats evidence reference = Sample Laggala Pallegama field register / 2025; action feasibility = Documented; action feasibility evidence reference = Sample Laggala Pallegama field register / 2025; threat reduction evidence = Documented; threat reduction evidence evidence reference = Sample Laggala Pallegama field register / 2025; uncertainty = Documented; uncertainty evidence reference = Sample Laggala Pallegama field register / 2025. Evidence gaps = 1 items. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Species range = Documented; Species range evidence reference = Fictional changed-evidence reference / version 2. Evidence gaps = 0 items. Without Species range, the required result is withheld.
Procedure. Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Limits. Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Method sources. Validation required. S71 — Scientific underpinning and approach; full STAR calculation is not implemented; DD-LOCAL — Domain decision rules and matching fictional examples.
Domain variants. star.
SURVEY Design based statistical estimation
Decision example. Select defensible geographic poverty and income comparisons.
Calculation or steps weighted mean = sum of weight × observation ÷ sum of weights.
Inputs and units. Final design weight (weight); Observed variable (LKR/household); Stratum and primary sampling unit.
Worked example. DEC-DP20-002 — Laggala Pallegama — poverty reporting, 2025. Final design weight = 2 weight; Observed variable = 68,000 LKR/household; Stratum and primary sampling unit = Fictional sampling stratum / Laggala Pallegama cluster. Observed variable = 68,000 LKR/household. Realistic sample data; the exact evidence fields remain in the decision register.
Changed example. Final design weight = 2.02. Weighted mean = 78,678.643. Without Final design weight, the required result is withheld.
Procedure. Weighted mean = sum(weight×observation)/sum(weight). Estimated total = sum(weight×observation), only for weights and population coverage suitable for that estimand.
Limits. Retain sampling frame, strata, clusters, nonresponse and calibration. The prototype does not invent complex-design variance, confidence intervals or small-area precision.
Method sources. Verified published component. Weighted estimation component. Institution publication — United Nations Statistics Division. Chapter 9, paragraphs 38 and 39, printed page 9-9, PDF page 417; Chapter 8 weighting. https://unstats.un.org/UNSDWebsite/statcom/session_57/documents/BG-3k-Handbook_on_Surveys_of_Household_and_Individuals-E.pdf. Local weights, population coverage, design variance and ratio-yield interpretation still need confirmation. Positive illustrative weights do not demonstrate every calibration design.
Domain variants. weighted proportion, survey, survey precision, weighted area production.
FORECAST Forecast verification
Decision example. Review forecast errors before operational changes.
Calculation or steps error = forecast − observed; RMSE = square root of mean squared errors.
Inputs and units. Archived forecast rainfall (mm); Verifying observed rainfall (mm); Forecast lead time (hours); Forecast issue date; Forecast valid date.
Meteorology examples use the revised dated records and task-specific definitions in Weather data and Meteorology decisions below.
Changed example. Archived forecast rainfall = 48.48. Forecast minus observed = 6.72 mm. Without Archived forecast rainfall, the required result is withheld.
Procedure. Error=forecast−observed. Matched-pair RMSE=sqrt(mean(error²)); MAE=mean(abs(error)); bias=mean(error).
Limits. Match lead, valid interval, location, variable, units and observation quality. Do not verify a forecast against data available when it was issued. This date-level example supports whole-day lead times only. Issuance, verification date and lead must agree; sub-day verification needs timestamps.
Method sources. Verified published formula. Matched-pair RMSE. Government publication — Environment and Climate Change Canada. Displayed RMSE equation and definitions of forecast, observation and verification count. https://weather.gc.ca/verification/scores/rmse_e.html. Local verification periods, observation quality and forecast applicability still need confirmation.
Domain variants. forecast, probability forecast.
Weather data and Meteorology decisions
Save source weather data once and reuse matching records across decisions. The Meteorology decision definitions below supersede earlier generic examples for DEC-DP08-001 to DEC-DP08-020. Other decision definitions are unchanged.
Record | Information to retain |
|---|---|
Stations | Official station ID, name, owner, location, elevation and dated station or instrument changes. |
Observations | Station, variable, start and end of the observation period, time zone, raw value, numeric value where supplied, unit, quality flag and source version. |
Climate baselines | Station or area, variable, month or season, reference years, normal value, method and publication version. |
Forecasts | Original issue time, valid period, area, variable, lead time, forecast value or category probability, event definition and product version. |
Original sources | Original file or delivery, publisher, source address, retrieval time, permitted use, version and integrity check. |
Checks and corrections | Quality finding, reason, responsible role and source revision. Retain the original record and every correction. |
Calculated results | Exact input records and versions, selected station or area, period, baseline, formula and published source, units, missing data and limitations. |
The system shall retain original weather deliveries and reusable observations once. Store station and variable identifiers, observation start and end, time zone, raw text, numeric value when supplied, unit, QC state and source version. Separate forecasts, observations and climate normals. Each result shall reference exact source records and formula versions. Reuse a matching saved record across decisions instead of entering another copy.
A source delivery shall retain publisher, original URL or file, retrieval time, integrity check, permitted audience, source version and superseded version. A repeated delivery with the same station, variable, period and source version shall be detected as a duplicate. A correction creates a new revision with its reason and responsible role; the original remains available. Reject incompatible units and intervals before aggregation. Unknown time zones and source QC flags remain unknown.
Zero is an observed number. TRACE is a separate state without an invented amount. NA and missing periods remain missing. Three-hour rain and rainfall accumulated since 08:30 are distinct variables and shall not be added. Preserve each product’s exact climate baseline; 1981–2010 and 1991–2020 are different reference periods. Do not replace a forecast with a later issue when checking its performance.
Saved source coverage
The preserved Department of Meteorology capture contains 24 stations at the published time 10 November 2026 at 17:30, with 240 variable records. The publisher’s time zone and QC flags were not supplied. Table 01 of the bulletin issued 5 November 2026 provides 23 district cumulative rainfall departures for 1 January to 4 November 2026 against 1981–2010; Kegalle is NA. Matale is −0.4% and Kandy is +16.5%. These are district summaries, not measurements of Knuckles plots.
The weekly map and Table 02 marked NOT AVAILABLE are excluded even though hidden text can be extracted. Saved forecast files retain issue date and validity separately. The temperature outlook has conflicting printed period labels and unavailable districts; no period or value is inferred. Historical daily and monthly series, source QC histories, matched forecast archives, instrument logs and data-reuse permissions are still required for the respective analyses.
The prototype source form checks a preview. Permanent multi-user storage and automated data feeds are system requirements, not an implemented archive in the prototype. The saved public source package remains a reference archive. Revised prototype scenarios do not overwrite it. All existing client and expert decisions remain in Institution review.
Meteorology method and source categories
Published official data identifies a value transcribed from the stated government table. Verified published component identifies the cited RMSE or Brier equation only. Project checklists, local thresholds, matching rules, permissions and intended use remain Validation required. Published source context does not establish approval of a local decision.
DEC-DP08-001 Check published rainfall departures
Compare published rainfall departures for the same period and climate baseline.
Record: Record basis; District or fixed analysis area.
Period: Observation period starts; Observation period ends.
Baseline: Baseline first year [year]; Baseline last year [year].
Measurements: Published rainfall departure [%] optional.
Optional rainfall totals: Observed rainfall total [mm] optional; Matching normal rainfall [mm] optional.
Source details: Original publication and table reference; Baseline definition and period reference.
Method: For a directly published departure, retain the published percentage. For matched totals only: departure = 100 × (observed − normal) / normal, where normal > 0. Percent of normal = 100 × observed / normal; it is a different measure.
Published example: Kandy +16.5%, 1 January to 4 November 2026, against 1981–2010. Expert Hub retains the year, source and baseline. Edited values are labelled what-if.
What-if example: Change the published Colombo value from 14.4% to 14.5% for the same dates and baseline.
Missing input check: omit District or fixed analysis area. Obtain the records listed below. Missing data stays explicit.
Limits: District cumulative figures do not measure rainfall at a Knuckles site or establish a drought. The weekly table marked NOT AVAILABLE is excluded. Saved Table 01 has 23 district summaries. Kegalle is NA. Table 02 and its weekly map are marked NOT AVAILABLE.
Source: Department of Meteorology agrometeorological bulletin. Government publication. 5 November 2026, page 4 Table 01. https://meteo.gov.lk/pdfs/agromet_pdf.pdf
DEC-DP08-002 Check consecutive low-rainfall days
Identify the dated low-rainfall runs supported by the supplied daily series.
Record: Station or demonstration gauge ID.
Period: Observation day.
Measurements: Rainfall value state; Daily rainfall [mm] optional; Example dry-day cutoff [mm]; A day is dry when rainfall.
Source details: Daily accumulation and reporting convention; Daily series reference; Quality or missing-day note.
Method: Count a run only across distinct consecutive observed days at one gauge using one daily convention and cutoff. Trace and missing days break the known run unless a documented measurement rule supplies a usable value.
Example: Illustrative data. 2025-06-01 records 4 mm; this does not meet the stated example dry-day rule.
Selected matching sample: longestDrySpell = 3.
Changed example: 2025-06-01 records 4.1 mm; this does not meet the stated example dry-day rule.
Missing input check: omit Station or demonstration gauge ID. Obtain the records listed below. Missing data stays explicit.
Limits: This is a known observed run, not a drought diagnosis or warning threshold. A three-hour snapshot cannot replace a daily history. The saved official table is one three-hour snapshot. A continuous daily rainfall series is still required for a real dry-spell analysis.
DEC-DP08-003 Check missing and late station observations
Check received records against an explicit observation schedule and quality review.
Source details: Official station ID; Station and instrument metadata reference; Observation schedule reference; Validity and duplicate-check reference.
Period: Latest published or valid observation time; Monitoring window starts; Monitoring window ends; Assessment time; Time zone.
Completeness: Expected observations [observations]; Distinct valid observations [observations]; Required observation interval [hours].
Method: Completeness = 100 × distinct valid / scheduled observations in the stated window. Age = assessment time − latest valid time in a confirmed common time zone. Compare age with the supplied reporting interval.
Example: Official observations; comparison records missing. The source reports 43444 at 2026-11-10T17:30. A schedule and QC delivery log are needed to calculate completeness.
Changed example: The source reports DEMO revised evidence reference at 2026-11-10T17:30. A schedule and QC delivery log are needed to calculate completeness.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: One public snapshot does not establish how many readings were scheduled, received or quality-checked. The saved table identifies 24 stations and their published report times. It does not provide a complete delivery log or source QC flags.
DEC-DP08-004 Prepare rainfall records for SPI
Check the monthly rainfall series and method evidence needed before a separate SPI calculation.
Source details: Official station ID; Station and instrument metadata reference; Monthly values and missing-month register; Station history and homogeneity assessment; Distribution fit and zero-rainfall treatment; Treatment of missing months.
Period: Baseline starts; Baseline ends.
Monthly series: Expected monthly observations [months]; Usable monthly observations [months]; Accumulation period [months].
Method: Reported coverage = 100 × usable / expected months. Verify the expected monthly sequence, accumulation period, station changes, missing-month treatment and fitted distribution separately. This screen does not calculate SPI.
Example: Illustrative data. 350 of 360 stated monthly observations are usable (97.222%). No SPI value is calculated.
Changed example: 350 of 360 stated monthly observations are usable (97.222%). No SPI value is calculated.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: WMO No. 1090 describes long monthly records and the effect of missing data. A coverage percentage alone does not validate SPI or establish drought. No long monthly station series is present in the saved capture. The published drought and anomaly products do not supply that missing series.
Source: WMO Standardized Precipitation Index User Guide. Institution publication. WMO No 1090; SPI calculation and interpretation guidance. https://www.droughtmanagement.info/literature/WMO_standardized_precipitation_index_user_guide_en_2012.pdf
DEC-DP08-005 Compare matching temperature observations
Compare the same temperature statistic and observation interval before investigating a difference.
Source details: Official station ID; Station and instrument metadata reference; Observation interval definition; Original file or delivery reference; Quality-control or review reference.
Measurements: Temperature statistic; Reported temperature [°C].
Comparison: Matching reference temperature [°C] optional; Reference statistic; Reference observation or baseline period; Matching reference and method.
Period: Observation time; Time zone.
Method: Temperature difference = observed − matching reference in °C. Match station, statistic, observation interval, units and source definitions. Do not calculate a relative percentage from Celsius values.
Example: Official observations; comparison records missing. Published instantaneous temperature is 24 °C. A matching reference has not been established.
Changed example: Published instantaneous temperature is 24.1 °C. A matching reference has not been established.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: An instantaneous reading is not a daily maximum or minimum. A difference does not identify a sensor fault or establish a climate trend. The saved station table supplies instantaneous air temperature, not a daily maximum/minimum history.
DEC-DP08-006 Prepare a weather-warning review case
Check the original warning product and accepted observations before a duty-officer review.
Record: Official bulletin ID; Hazard and affected area.
Period: Official issue time; Valid from; Valid until; Time zone.
Source details: Original bulletin and revision; Accepted observations and their period; Applicable warning procedure and criteria; Responsible duty role; Earlier bulletin replaced or cancelled optional.
Method: Check bulletin identity, issue and validity, replacement history, accepted observation references, affected area, applicable procedure and duty responsibility. No hazard threshold is inferred.
Example: Illustrative data. This case identifies the bulletin and evidence needed for a duty-officer warning review. It does not issue a warning.
Changed example: This case identifies the bulletin and evidence needed for a duty-officer warning review. It does not issue a warning.
Missing input check: omit Official bulletin ID. Obtain the records listed below. Missing data stays explicit.
Limits: This prepares a review note. It never issues or approves a warning. The official site publishes advisories and states that warning API access is available on request. No API key or operational warning feed is used here.
DEC-DP08-007 Compare archived rainfall forecasts with observations
Measure errors for matching forecasts and observations at one stated lead.
Record: Station ID.
Period: Archived forecast issued; Rainfall interval starts; Rainfall interval ends; Time zone.
Forecast: Lead to interval end [hours]; Forecast rainfall [mm].
Verification: Observed rainfall [mm].
Source details: Rainfall interval and measure; Archived forecast and version; Verifying observation and QC reference.
Method: Error = forecast − observed. For complete matching pairs: RMSE = sqrt(mean(error²)), MAE = mean(abs(error)), bias = mean(error). Match station, variable, accumulation, lead, time zone and observation QC before pooling.
Example: Illustrative data. Forecast 48 mm; matching observation 42 mm. Forecast minus observed is 6 mm.
Selected matching sample: n = 3; rmse = 4.65475; mae = 4.33333; bias = 1.
Changed example: Forecast 48.1 mm; matching observation 42 mm. Forecast minus observed is 6.1 mm.
Missing input check: omit Station ID. Obtain the records listed below. Missing data stays explicit.
Limits: Scores describe the selected sample. They do not establish future forecast reliability or authorise an operational change. The saved observations do not contain matching archived daily point forecasts. Issued seasonal category probabilities cannot be substituted for rainfall amounts.
Verified published component: Matched-pair RMSE. Environment and Climate Change Canada. Displayed RMSE equation and definitions of forecast, observation and verification count. https://weather.gc.ca/verification/scores/rmse_e.html
DEC-DP08-008 Check seasonal probability forecast performance
Compare a defined seasonal event with archived probabilities and verifying rainfall.
Record: Forecast area.
Period: Forecast issue time; Season starts; Season ends; Time zone.
Forecast: Forecast event probability [fraction]; Independent reference probability [fraction].
Verification: Observed season rainfall [mm]; Illustrative event cutoff [mm].
Source details: Event and category edition; Archived probability and version; Seasonal rainfall and QC reference; Independent benchmark and reference period.
Method: For the predefined event, y = 1 when rainfall exceeds the stated cutoff, otherwise 0. Brier score = mean((p − y)²). Brier skill = 1 − score/reference score for matching cases and a positive reference score. Category and benchmark choices are local assumptions.
Example: Illustrative data. The supplied 1,040 mm exceeds the example 900 mm cutoff. The squared probability error is 0.09.
Selected matching sample: n = 3; brier = 0.136667; reference = 0.335567; skill = 0.592729.
Changed example: The supplied 1,040.1 mm exceeds the example 900 mm cutoff. The squared probability error is 0.09.
Missing input check: omit Forecast area. Obtain the records listed below. Missing data stays explicit.
Limits: A published Brier formula does not verify a local category threshold, benchmark or forecast. No complete seasonal calibration assessment is claimed. Saved seasonal outlooks are source products. They do not include an archive of matched hindcasts and seasonal observations.
Source: JMA numerical weather prediction outline. Government publication. AppendixA.3, equationsA.3.1 and A.3.3. https://www.jma.go.jp/jma/jma-eng/jma-center/nwp/outline2022-nwp/pdf/outline2022_all.pdf
Source: Department of Meteorology seasonal rainfall outlook. Government publication. SF-2026-11, issue information and seasonal/monthly outlook. https://meteo.gov.lk/pdfs/rainfall_pdf.pdf
Source: Department of Meteorology consensus seasonal outlook. Government publication. NDJ 2026/27 outlook, issued 30 October 2026. https://meteo.gov.lk/pdfs/consensus_pdf.pdf
Verified published component: Binary Brier score and skill component. Japan Meteorological Agency. Sections A.3.1 and A.3.2, equations A.3.1 and A.3.3, printed page 239, PDF page 7. https://www.jma.go.jp/jma/jma-eng/jma-center/nwp/outline2024-nwp/pdf/outline2024_Appendix_A.pdf
DEC-DP08-009 Check a proposed weather-station site
Prepare a site-survey worklist from coverage, exposure and operating evidence.
Record: Proposed site reference.
Source details: Network coverage gap and intended variable; Surveyed terrain, location and elevation; Instrument exposure and obstacle survey; Siting standard and edition; Access and land-use permission; Power arrangement and reliability; Communications coverage and delivery test; Responsible site-survey role.
Method: Review variable-specific siting and exposure against the cited standard using a surveyed site and operating records. No generic distance score or automatic preferred site is generated.
Example: Illustrative data. The site-survey checklist identifies coverage, exposure, access and operating evidence for Rambukoluwa demonstration candidate. It does not rank or select a site.
Changed example: The site-survey checklist identifies coverage, exposure, access and operating evidence for DEMO revised evidence reference. It does not rank or select a site.
Missing input check: omit Proposed site reference. Obtain the records listed below. Missing data stays explicit.
Limits: Complete records support a site review. They do not select or authorise a station. The public station table supplies station identities. It does not establish a coverage-gap study or candidate-site survey.
Source: WMO Guide to Instruments and Methods of Observation. Institution publication. WMO No. 8; applicable instrument, siting and maintenance chapter and edition to be recorded. https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/instruments-and-methods-of-observation-programme-imop/guide-instruments-and-methods-of-observation-wmo-no-8-0
DEC-DP08-010 Plan instrument calibration and repair work
Review due dates, service impact, spares and technician capacity before proposing work.
Record: Instrument ID; Calibration or repair task; Work completed.
Period: Recorded due date; Assessment date; Proposed work starts; Proposed work ends.
Source details: Latest calibration or defect record; Service impact and temporary cover; Technician team or booking reference; Required spares and availability; Completion evidence optional.
Resources: Required technician effort [hours]; Available effort in this window [hours].
Method: For open work, days overdue = max(0, assessment − due date). Compare required effort with available effort in the stated window and detect overlapping bookings for the same resource. Retain completion evidence for closed work.
Example: Illustrative data. The task is 29 days overdue. Review service impact, spares and technician availability before proposing work.
Changed example: The task is 29 days overdue. Review service impact, spares and technician availability before proposing work.
Missing input check: omit Instrument ID. Obtain the records listed below. Missing data stays explicit.
Limits: Overdue age is not a calibration result or a safety priority. A proposed booking does not assign a technician. Instrument serial numbers, calibration certificates, defects, spares and technician bookings are not in the saved public capture.
Source: WMO Guide to Instruments and Methods of Observation. Institution publication. WMO No. 8; applicable instrument, siting and maintenance chapter and edition to be recorded. https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/instruments-and-methods-of-observation-programme-imop/guide-instruments-and-methods-of-observation-wmo-no-8-0
DEC-DP08-011 Check station changes before comparing climate records
Identify the station-history evidence needed before assessing a series break.
Source details: Official station ID; Station and instrument metadata reference; Original location, instrument and observation definition; Revised metadata and effective date; Parallel or reference-station observations; Original dated climate series; Break-test method, result and uncertainty; Proposed adjustment and retained original version optional.
Period: Station or instrument change date.
Record: Change type.
Method: Use dated station metadata and the original and comparison series to investigate an apparent break. Preserve originals and any documented adjustment separately. This screen does not homogenize observations.
Example: Illustrative data. Retain the dated station change and both metadata versions. A series-break assessment needs the original and comparison observations; no adjustment is calculated here.
Changed example: Retain the dated station change and both metadata versions. A series-break assessment needs the original and comparison observations; no adjustment is calculated here.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: A metadata change is a reason to investigate, not proof of a climatic or non-climatic shift. The saved station snapshot has no relocation history, parallel series or statistical break assessment.
Source: WMO climate-data quality and homogenization guidance. Institution publication. Climate data quality, metadata, homogenization and dataset-management guidance. https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/climate-services/climate-data
DEC-DP08-012 Prepare crop-weather advice for review
Match crop exposure with weather for the same place and crop period.
Record: Farm or crop-area reference; Crop; Crop stage and planting date.
Measurements: Exposed crop area [ha].
Period: Crop period starts; Crop period ends.
Source details: Matching daily weather and forecast records; Why the weather represents this crop area; Crop-stage advice protocol; Responsible agricultural adviser.
Method: Join crop, stage and planted-area records to suitable weather and forecasts for the same place and period. Use the cited crop protocol to prepare a specialist review; no advice is inferred from a cumulative rainfall percentage alone.
Example: Official context with crop records missing. Published cumulative departure 16.5% for Jan–4 Nov 2026. This is background rainfall context. Crop stage, planting area and matching local weather are needed before preparing advice.
Changed example: Published cumulative departure 16.5% for Jan–4 Nov 2026. This is background rainfall context. Crop stage, planting area and matching local weather are needed before preparing advice.
Missing input check: omit Farm or crop-area reference. Obtain the records listed below. Missing data stays explicit.
Limits: District cumulative rainfall is background context, not a measurement of crop stress or a field-specific forecast. Saved district cumulative rainfall and the agromet bulletin can provide context. Crop locations, planting dates, stages and matching local weather are still required.
Source: Department of Meteorology agrometeorological bulletin. Government publication. 5 November 2026, page 4 Table 01. https://meteo.gov.lk/pdfs/agromet_pdf.pdf
DEC-DP08-013 Check weather inputs for a water-needs calculation
Check daily weather variables, units and station conditions before an evapotranspiration calculation.
Source details: Official station ID; Station and instrument metadata reference; Humidity statistic and method; Reference-site location, elevation and surface; Daily dataset and QC reference.
Measurements: Input time basis; Published instantaneous temperature [°C] optional.
Period: Weather observation day.
Daily weather: Daily maximum temperature [°C]; Daily minimum temperature [°C]; Relative humidity [%]; Daily solar radiation [MJ/m²/day]; Wind speed [km/h]; Wind measurement height [m].
Method: Check the daily temperature, humidity, radiation and wind definitions required by the selected reference-evapotranspiration method. Wind unit conversion alone does not provide a 2 m wind observation. This screen checks inputs; it does not calculate ETo.
Example: Official observations; comparison records missing. Published snapshot: 24 °C, humidity 92%, wind 0 km/h. Daily extrema, radiation, humidity convention and reference-site wind metadata remain separate inputs. No ETo is calculated.
Changed example: Published snapshot: 24.1 °C, humidity 92%, wind 0 km/h. Daily extrema, radiation, humidity convention and reference-site wind metadata remain separate inputs. No ETo is calculated.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: A three-hour observation is not a daily weather dataset. Missing radiation, wind height or daily extrema must remain missing. The saved snapshot supplies temperature, humidity and wind. It does not supply daily temperature extrema, solar radiation, wind height or reference-site metadata.
Source: FAO Irrigation and Drainage Paper 56 meteorological data. Institution publication. Chapter 3 meteorological data; wind speed, climatic data acquisition and minimum requirements. https://www.fao.org/4/x0490e/x0490e07.htm
DEC-DP08-014 Review an archived marine forecast
Check the marine area, forecast validity and vessel context before a specialist review.
Record: Marine product identifier; Forecast sea area.
Period: Issue time; Stated forecast duration [hours]; Time zone.
Forecast: Forecast wind lower bound [km/h]; Forecast wind upper bound [km/h]; Sea state as published; Separate gust condition.
Source details: Archived original marine product; Vessel, activity and intended area; Applicable marine review protocol; Responsible marine specialist.
Method: Retain the original marine product, area, issue time and validity. Keep normal wind, temporary thunderstorm gusts and sea-state terms separate. Compare the intended activity against the appropriate marine protocol.
Example: Official archived product with review details missing. The archived product states 20–30 km/h normal wind and slight or moderate seas. 60–70 km/h temporarily during thundershowers. Check issue, validity and vessel context before a marine specialist review.
Changed example: The archived product states 20–30 km/h normal wind and slight or moderate seas. 60–70 km/h temporarily during thundershowers. Check issue, validity and vessel context before a marine specialist review.
Missing input check: omit Marine product identifier. Obtain the records listed below. Missing data stays explicit.
Limits: This is an archived source-review example, not live vessel advice or a new warning. Inland field records do not establish marine conditions. The preserved official Marine-page capture supplies the published wind range, sea-state wording and issue time. It does not supply numerical wave heights or vessel-specific clearance.
Source: Department of Meteorology marine forecast archive. Government publication. Marine sea-weather page captured 10 November 2026; issued 14:00. https://meteo.gov.lk/
DEC-DP08-015 Review aviation weather-service interruptions
Reconcile required report delivery and recorded outage intervals for an aerodrome service.
Record: Aerodrome and service.
Source details: Required reporting schedule and service standard; Report issue, receipt and failure log; Service impact and temporary arrangements.
Period: Service window starts; Service window ends; Time zone.
Outages: Outage intervals as start/end on separate lines.
Delivery: Expected reports [reports]; Distinct reports delivered within the required deadline [reports].
Method: Time availability = 100 × (service-window hours − union of outage hours) / service-window hours. Merge overlapping outage intervals. On-time delivery = 100 × distinct qualifying reports / scheduled reports. Match the agreed report schedule and deadline.
Example: Illustrative data. Recorded outage union is 3 hours; time availability is 98.214%. On-time report delivery is not available. The two measures answer different questions.
Changed example: Recorded outage union is 3 hours; time availability is 98.214%. On-time report delivery is not available. The two measures answer different questions.
Missing input check: omit Aerodrome and service. Obtain the records listed below. Missing data stays explicit.
Limits: Availability and delivery metrics do not establish aviation meteorological compliance or flight safety. The public weather capture is not an aerodrome service log. Report schedules, deadlines, outages and operational impact records must be obtained.
DEC-DP08-016 Prepare a lightning-awareness evidence review
Match an authorised lightning source with the exposure frame used for awareness planning.
Record: Lightning evidence type.
Source details: Original event dataset or advisory; Detection coverage, uncertainty or advisory area; Dated household or facility exposure frame; Boundary edition and matching predicate; Responsible awareness-planning role.
Period: Evidence period starts; Evidence period ends.
Measurements: Distinct receptors in the assessed frame [receptors]; Distinct receptors spatially matched [receptors].
Method: For a documented matching exposure frame, share = 100 × distinct matched receptors / receptors in that same frame. Count each receptor once. An issued advisory and a historical strike dataset are different source types.
Example: Illustrative data. Obtain the dated lightning source and a matching exposure frame before reporting a share.
Changed example: Obtain the dated lightning source and a matching exposure frame before reporting a share.
Missing input check: omit Original event dataset or advisory. Obtain the records listed below. Missing data stays explicit.
Limits: A matched share is not a strike probability or an individual risk rating. This view performs no live spatial intersection. The official site publishes lightning advisories. The saved package has no historical strike dataset or matched household exposure frame.
DEC-DP08-017 Compare annual station observations
Compare the same annual statistic at one station with its quality and station-history evidence.
Source details: Official station ID; Station and instrument metadata reference; Annual aggregation and missing-data method; Annual dataset and quality reference; Station history and comparability assessment.
Period: Observation year [year].
Measurements: Annual temperature statistic; Annual statistic [°C].
Quality: Expected daily observations [days]; Valid daily observations [days].
Method: Display comparable annual statistics for one station and definition. Report their mean and sample standard deviation only for complete compatible selected records. No trend significance or climate attribution is calculated.
Example: Illustrative data. The supplied 2023 mean temperature is 25.6 °C, with 100% reported daily coverage. No trend or attribution is calculated.
Selected matching sample: n = 3; mean = 25.7; sd = 0.1.
Changed example: The supplied 2023 mean temperature is 25.7 °C, with 100% reported daily coverage. No trend or attribution is calculated.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: Three illustrative annual values do not establish a long-term climate trend. The saved three-hour snapshot cannot supply an annual mean. A real annual station series and aggregation/QC history are still required. Annual figures below are labelled demonstration values.
Source: WMO climate-data quality and homogenization guidance. Institution publication. Climate data quality, metadata, homogenization and dataset-management guidance. https://community.wmo.int/site/knowledge-hub/programmes-and-initiatives/climate-services/climate-data
DEC-DP08-018 Compare concurrent sensor observations
Compare the same variable, unit and interval from a sensor and an independent reference.
Record: Official station ID.
Source details: Primary instrument reference; Independent reference instrument; Matching observation interval; Calibration and uncertainty evidence; Both original observation references.
Measurements: Variable; Primary unit; Primary observation [stated unit].
Comparison: Reference unit; Independent observation [stated unit] optional.
Period: Primary observation time; Reference observation time; Time zone.
Method: Difference = primary − independent reference only for a matching variable, unit, interval and time convention with instrument and calibration evidence. Temperature differences in °C have no relative percentage.
Example: Official observations; comparison records missing. Primary reading: 24 °C. The concurrent independent comparison is incomplete.
Changed example: Primary reading: 24.1 °C. The concurrent independent comparison is incomplete.
Missing input check: omit Official station ID. Obtain the records listed below. Missing data stays explicit.
Limits: A difference does not identify a faulty instrument. Preserve both originals and their calibration evidence. Saved station temperatures can populate the primary reading. Independent concurrent readings and instrument/calibration metadata are not in the saved package.
DEC-DP08-019 Review delayed climate-data requests
Separate request delay from the permission to release a dataset.
Record: Request ID; Dataset, station and period requested; Intended use; Request closed; Release permission.
Period: Request received; Recorded response due; Assessment date.
Source details: Data-owner permission and permitted audience; Responsible data custodian; Response or closure evidence optional.
Method: For open requests, days overdue = max(0, assessment − recorded due date). Check permission and scope independently. A late response does not grant release rights.
Example: Illustrative data. The request is 15 days overdue while open. Recorded release permission: Not recorded. Delay does not grant release rights.
Changed example: The request is 15 days overdue while open. Recorded release permission: Not recorded. Delay does not grant release rights.
Missing input check: omit Request ID. Obtain the records listed below. Missing data stays explicit.
Limits: This prepares a follow-up. It does not transmit a dataset or approve reuse. The Department provides a data-contact route. Its internal request, due-date and permission registers are not public source data.
DEC-DP08-020 Check a weather product before SHARED publication
Check source rights, product version, validity and audience before a publication review.
Record: Publisher product ID; Product type.
Period: Original issue date; Valid period exactly as published; Period definition.
Source details: Original product and captured version; Earlier version or replacement reference optional; SHARED reuse and redistribution permission; Proposed SHARED audience; Responsible publication reviewer; Editorial and technical review record.
Method: Retain the original product, issue and validity, source version, replacement history, intended audience, review evidence and permitted SHARED use. Public availability alone is not redistribution permission.
Example: Official product metadata; SHARED review records missing. Original Issued seasonal outlook issued 2026-10-30. Validity as printed: November, December and January (NDJ) 2026/27. SHARED reuse permission, audience and publication review are separate records.
Changed example: Original Issued seasonal outlook issued 2026-10-30. Validity as printed: November, December and January (NDJ) 2026/27. SHARED reuse permission, audience and publication review are separate records.
Missing input check: omit Publisher product ID. Obtain the records listed below. Missing data stays explicit.
Limits: The original Department publication is separate from a SHARED publication decision. No publication is authorised or sent by this screen. Three saved issued outlooks populate the source records. Conflicting temperature-outlook period labels remain flagged for publisher clarification.
Source: Department of Meteorology seasonal rainfall outlook. Government publication. SF-2026-11, issue information and seasonal/monthly outlook. https://meteo.gov.lk/pdfs/rainfall_pdf.pdf
Source: Department of Meteorology consensus seasonal outlook. Government publication. NDJ 2026/27 outlook, issued 30 October 2026. https://meteo.gov.lk/pdfs/consensus_pdf.pdf
Source: Department of Meteorology temperature outlook. Government publication. Issued 4 November 2026; headings, captions and availability note. https://meteo.gov.lk/pdfs/temperature_pdf.pdf
Weather map images
Use the saved Department of Meteorology figures: August 2026 observed rainfall total (mm), percent of normal (%) and anomaly (mm), with the stated 1991–2020 reference; November 2026 and November 2026–January 2027 rainfall outlooks; and the November 2026 maximum/minimum temperature outlook. Retain the original colours, legends, units, source pages and dates. Do not use the unavailable weekly map or the temperature panels with conflicting seasonal labels. Matale temperature data remains unavailable.
No new weather calculation is made from these images. Rendering and cropping preserve the source map and legend. For August, 100% of normal means the monthly normal rainfall; an anomaly in millimetres is a different measure. Forecast colours describe category probabilities, not observed amounts or temperature in degrees. The image period remains independent of the selected decision records.
Government publication sources: https://meteo.gov.lk/pdfs/aug26.pdf page 1, Figure 1 A–C; https://meteo.gov.lk/pdfs/rainfall_pdf.pdf page 1 Figure 1 and page 2 Figure 2 November panel; https://meteo.gov.lk/pdfs/temperature_pdf.pdf page 1 Figures 1–2. Saved original files and Map_sources.json retain source and image integrity checks. Local use and permissions remain in Institution review.
4 Retained method references
Method References is the controlled catalogue of all 139 retained definitions. Each row preserves the original formula or procedure, inputs, units, limits and context link. Its category identifies direct publication support or Validation required, with the publisher and method-source locator where checked. Family mappings are candidates only. A published retained method is not implemented merely because a related prototype screen exists.
The source register separates link access from formula support. Official alternatives are now linked for the three previously unavailable entries, so all 33 follow-up entries have readable preferred references. The LUPPD report and FAO guide support planning context; they are not approved replacements for the local divisional manual. Experts must still confirm each selected method, source edition, units and local suitability.
NF012 is an absolute forecast error; VARIANCE is a signed plan difference. NF147 specifies discounted payback, but its linked appraisal and the current cash flow helper use simple or undiscounted payback. NF049 to NF053 and NF055 to NF058 use a water-stress context link that does not establish their methods. NF107 parameter compliance is not the full SDG 6.3.2 water-body indicator. These methods remain separate review questions.
Open all 139 retained method references
5 Sources
Calculation Sources contains 172 entries, including the official data mappings and draft domain references. It keeps original links, locators and access limits. S01 links the LUPPD report hosted by Parliament; NF-SOURCE-04 links FAO planning guidance; NF-SOURCE-12 links a HARTI price bulletin. The original LUPPD manual was not recovered. Local use and source rights remain in Institution review.
S69 FAO 56: crop evapotranspiration
Published method. FAO 56 Chapter 5 equation 56; ETc = Kc × ETo. Retrieved text for review.
S71 IUCN Species Threat Abatement and Restoration metric
Published specialist method overview. Scientific underpinning and approach; full STAR calculation is not implemented. Retrieved text for review.
S72 IWA non-revenue water management
Published definition. Opening NRW definition; detailed water audit protocol not supplied. Retrieved text for review.
S75 Environment Canada: root mean squared error
Published method. What is Root Mean Square Error; displayed formula. Retrieved text for review.
S76 FAO enterprise and activity budgeting
Published method. Section 4.3.8 Gross margin; section 4.7 Parametric budgeting. Retrieved text for review.
PROTO SHARED prototype calculation and workflow implementation
Project implementation. DecisionSupportModel.spec/project and named model functions in each entry. Read only prototype inspection.
SRS SHARED Software Requirements Specification
Project requirement. Sections 5.4, 10, 12 and named requirement IDs in each rule. Version 1.6.
S78 FAO Irrigation Water Management Training Manual 3
Published method. Chapter 4.4 Irrigation water need of rice; steps 1 to 8. Method text checked.
S79 IPCC 2006 Guidelines Volume 4 Chapter 2
Published method. Sections 2.2.3, 2.3.1 and 2.3.3; soil stock guidance printed page 2.37. Method text checked.
S80 USDA Forest Service A guide for predicting sheet and rill erosion on forest land
Historical published method. Universal Soil Loss Equation and Applying the USLE; printed page 2. Historical method text checked; current local calibration not established.
S81 FAO Guidelines for financial economic environmental and social information
Published method. Net Present Value and Internal Rate of Return subsections. Method text checked.
S82 WMO Standardized Precipitation Index User Guide
Published method. WMO No 1090; SPI calculation and interpretation guidance. Full guide checked; local fit and baseline pending.
S83 US Department of Justice Herfindahl Hirschman Index
Published definition. Definition of the sum of squared market shares. Definition checked; US legal thresholds do not apply to this project.
S84 NIST Coefficient of Variation
Published definition. Description of sample CV and ratio scale restriction. Definition checked.
S85 Turf area API
Software method. Version 7.2.0 area; square metres. Documentation checked.
S86 Turf distance API
Software method. Version 7.2.0 distance; Haversine method. Documentation checked.
S87 Turf length API
Software method. Version 7.2.0 length; selected units. Documentation checked.
S88 Turf buffer API
Software method. Version 7.2.0 buffer; radius and steps. Documentation checked.
S89 Turf intersect API
Software method. Version 7.2.0 intersect; polygon intersection. Documentation checked.
S90 Turf point in polygon API
Software method. Version 7.2.0 booleanPointInPolygon; boundary option. Documentation checked.
S91 UN Handbook of Surveys on Households and Individuals
Published guidance. Chapter 9 section 9.4.2, equation 9-16, printed page 9-19 (PDF page 427); Chapter 8 weighting; Final Draft. Weighting guidance checked; draft status retained.
S92 World Bank Impact Evaluation in Practice Second Edition
Published method. Chapter 7 Difference in Differences. Method text checked.
Specific source limits remain open: S16 needs custodian confirmation of jurisdiction; S51 does not establish the intended budgeting guide; S72 gives the NRW definition but not the full utility audit protocol. S80 is a historical USLE source, not a current local calibration. The WMO SPI guide and IUCN STAR overview do not make those full methods implemented in the prototype.
6 Approval and acceptance
Use published methods as their documented basis. Check the exact source and the copied calculation once. Ask the client or expert to confirm only local use, project choices and new or changed rules. Review each shared method once and list where it is used.
Published methods and sources
The core methods below already have a published basis. They do not need to be proved again for every screen. Their local inputs, settings, suitability and intended use remain subject to the confirmation list below. A published reference does not mean that the prototype implements the full method.
Published method | Publication and locator | Local use |
|---|---|---|
Sheet and rill erosion EROSION, NF023 | S80 USDA Forest Service A guide for predicting sheet and rill erosion on forest land. Universal Soil Loss Equation and Applying the USLE; printed page 2 NF-SOURCE-03 FAO Revised Universal Soil Loss Equation toolbox. FAO RUSLE toolbox: equation A = R K L S C P and factor definitions | The USDA source is historical. Confirm current local factors and suitability. |
Enterprise gross margin MARGIN | S76 FAO enterprise and activity budgeting. Section 4.3.8 Gross margin; section 4.7 Parametric budgeting | Confirm which revenue and variable costs are included. |
Net present value FINANCE | S81 FAO Guidelines for financial economic environmental and social information. Net Present Value and Internal Rate of Return subsections | Confirm cash flows, price basis and discount rate. |
Soil carbon stock SOILCARBON, NF034 | S79 IPCC 2006 Guidelines Volume 4 Chapter 2. Sections 2.2.3, 2.3.1 and 2.3.3; soil stock guidance printed page 2.37 | Confirm sampling, depth, bulk density, units and coarse-fragment basis. |
Impact comparison using difference in differences IMPACT | S92 World Bank Impact Evaluation in Practice Second Edition. Chapter 7 Difference in Differences | Confirm the comparison group and study assumptions. |
Weighted mean SURVEY | S91 UN Handbook of Surveys on Households and Individuals. Chapter 9 section 9.4.2, equation 9-16, printed page 9-19 (PDF page 427); Chapter 8 weighting; Final Draft | The cited UN handbook is a Final Draft. Confirm the survey design and weights. This citation does not cover every pooled-rate rule. |
Forecast error using RMSE FORECAST | S75 Environment Canada: root mean squared error. What is Root Mean Square Error; displayed formula | Confirm matching observations, locations, periods and forecast lead times. |
Paddy irrigation depth requirement NF037 | S78 FAO Irrigation Water Management Training Manual 3. Chapter 4.4 Irrigation water need of rice; steps 1 to 8 | Confirm crop stage, soil, rainfall and water-management inputs. |
Coefficient of variation NF086, NF115 | S84 NIST Coefficient of Variation. Description of sample CV and ratio scale restriction | Confirm compatible observations and a meaningful positive mean. It is not a return-volatility method. |
Standardized Precipitation Index NF095 | S82 WMO Standardized Precipitation Index User Guide. WMO No 1090; SPI calculation and interpretation guidance | Confirm the rainfall record, fitting procedure and local interpretation. The separate SPI demonstration remains Validation required. |
How to check each item
Category | Check needed |
|---|---|
Government publication | Record the government publisher, publication, edition and exact page or section. Confirm local inputs and settings where needed. |
Institution publication | Record the institution, publication, edition and exact page or section. Keep draft and historical status visible. Confirm local inputs and settings where needed. |
Validation required | Review new or changed domain rules, incomplete source matches and local assumptions. A data table or background page alone does not support a formula. |
Software check | The developer tests the copied formula, arithmetic, units and invalid or missing inputs. Ordinary arithmetic does not need separate scientific approval. |
Client and expert decisions
These decisions remain pending in Institution review. Each decision should state what was checked, who checked it, the outcome and any conditions. One review can cover the same method used by several screens.
Topic | What to confirm | Who |
|---|---|---|
Scope and institutions C01, C02, C12 | Confirm the final features, proposed decisions, participating institutions and what stays in existing tools. | Client |
Responsibilities C02 | Name who owns data, submits records, reviews them and approves sharing. | Client and institutions |
Maps and boundaries C03 | Source studies report 1,533 and 1,584 GN divisions. Which dated programme roster, official codes and boundary edition apply? Who maintains them? | Data custodian and GIS expert |
Data sources C04 | Confirm datasets, fields, units, update frequency and access or sharing conditions. | Source institutions |
Privacy C05 | Confirm access to personal records, sensitive locations and retention periods. | Client and privacy specialist |
New or changed calculations E01 | Review proposed scores, weights, thresholds, missing-value rules and method changes. For published methods, confirm local inputs, units, settings and intended use. | Relevant expert or statistician |
Land soil and water methods E02 | Confirm local suitability, sampling, laboratory methods and model factors. | Relevant domain experts |
Ecosystem services and PES E03 | Confirm eligibility, rights, rates, safeguards, verification and payment authority. | Client and relevant experts |
Indicators and payments C10 | Confirm indicator definitions, acceptance measures, milestones and payment weights. | Client and monitoring or finance specialists |
Languages and access needs C06 | Confirm wording, supported devices and accessibility requirements. | Client and representative users |
Technical choices and service targets C07, C08 | Agree architecture, hosting, operator, costs, performance, security and recovery targets. | Client and technical adviser |
Complaints and appeals C09 | Confirm receiving officers, response times and the appeal process. | Client |
Final SRS acceptance C11 | Confirm consultation comments, agreed revisions, validation, final presentation and final acceptance. | Authorized client representative |
Source details to confirm
LUPPD: the alternative publications provide planning context. The applicable local planning procedure still needs confirmation under C04 and E02.
HARTI: the published prices support the quoted observations. They do not automatically support proposed volatility, spread or other analysis; review these under C04 and E01.
Live-system security, load and recovery tests belong to implementation. The SRS needs agreed requirements and a test plan. No separate expert approval is needed for each mock screen or repeated calculation.
Record decisions in Institution review only. Keep the source reference, method and affected uses with the decision. A changed method or changed local settings needs a new review of the change; an unchanged shared method can reuse the recorded decision.
The rice-plot examples NF001 and NF002 use fictional grouped counts; plot identity and local category definitions still need confirmation. The disputed PMU finance and procurement examples remain proposed until the client confirms scope.
6 1 Architecture Rules and Worked Examples
These examples support SRS section 10.9. Published sources support the methods or equipment they describe. Local methods and settings require validation. See How crop and rainfall figures are compared and From a question to a report for the related steps. Decisions remain pending in Institution review.
Packet counts and storage arithmetic
Scalar observations per day = devices × observed properties × samples per day. Packets per day = devices × transmissions per day when one transmission contains all the properties. For 100 stations and one-minute reporting: 100 × 10 × 1,440 = 1,440,000 scalar observations/day, while 100 × 1,440 = 144,000 packets/day. Database rows depend on the chosen packet and observation representation. Bytes/day must use declared measured or assumed bytes per packet and scalar record, plus separate index, projection, file and backup allowances. These are sizing illustrations, not benchmarks or prices.
Cultivation fact grain and annual aggregation
Keep one value per source release, area/boundary version, crop category, season and year. Reject duplicate category-season keys and overlapping definitions before aggregation. Sum compatible seasonal hectares into gross annual cultivated area. Do not call this unique physical land area without plot geometry and an approved union method. Preserve source coverage, missing values and the category definition used in the saved report. A later category crosswalk creates a new projection version; earlier reports retain their original categories.
Weather facts and safe joins
Summarise weather separately from cultivation. Check duplicate intervals, counter resets and corrections before adding rainfall. Use time or approved area weights for temperature. Withhold a complete annual result when required coverage is missing. Join one weather summary to the crop figures for the same area and period. In the diagram example, 100 ha of paddy plus 60 ha of maize gives 160 ha. Show the district’s 1,300 mm rainfall once. District results from stations require a reviewed mapping and weighting method.
Raster example
Keep the provider, product version, grid, coordinate system, resolution, period, unit, quality flags and licence. Align grids with a documented method suited to the variable. Use valid cells inside the chosen boundary. Sum rainfall only over compatible intervals with valid coverage and use area weights for compatible cell averages. If clouds hide 25% of a catchment, show 75% usable coverage and leave the obscured cells missing. Keep source files, boundary and method versions, and processing settings so the result can be rebuilt. See the map example.
Four definition-change examples
Soil electrical conductivity: add a versioned optional attribute with an explicit unit, method, sampling context and effective date. Older records remain not collected rather than zero. Crop reclassification: retain the original category edition and apply a reviewed many-to-many crosswalk only in a new report version. Station relocation: create a new deployment/location interval and link readings to the deployment effective at measurement time. Reservoir capacity: retain separate institution-owned gross and effective capacity claims with units, level/datum context, source editions and periods. Neither a similar label nor a newer receipt silently chooses the authoritative claim.
AI candidate checks
An extraction result must identify the exact source version and evidence spans. An unknown unit, ambiguous place, missing total or unresolved field remains unresolved. Parse and reconcile reliable structured tables deterministically, using AI only where the selected method adds value. Validate candidate types, units, periods, geography and totals, then display the source and editable candidate side by side. Only an explicit authorised review commits the candidate in the simulation. A schema-conforming response or an invented confidence number does not establish factual accuracy.
Source rights and derived outputs
Derived rows, map tiles, aggregates, report artifacts and retrieval chunks retain source-version dependencies. A read or export applies current actor access and current source rights. A withdrawal invalidates affected caches and prevents new public retrieval and exports, even before a full index rebuild. Retain historical material only under an explicit restricted retention policy. A withdrawn source must not remain available through a stale cached report. Copies already downloaded outside the platform cannot be recalled by this demonstration.
Storage options and upgrade decisions
Option A is the starting point: the existing modular application, operational/geospatial capability, protected files and bounded analytical views. Choose Option B when measured cross-domain query cost or repeatable reporting needs justify a governed mart, semantic measures and selected cubes or retrieval indexes. Choose Option C only when measured telemetry throughput, stream latency, raster volume or research queries justify specialist engines. Set and measure the required workload, lag, query and recovery budgets before adoption. Do not install every logical store or assume that a vector index, relational store and OLAP cube are interchangeable.
Provider and evaluation evidence
The research catalogue separates documentation, successful bounded public reads, credential-blocked integration and simulated adapters. It retains official URLs, supporting sections, source dates, measured variables, protocols, access and reuse limits. The local AI evaluation uses a small synthetic set with exact expected fields, missing values, ambiguous units and corrected evidence. It reports field correctness and unresolved review work rather than a successful network response. Representative Sinhala or Tamil evaluation remains dependent on an appropriate reviewed corpus. No private document is transmitted to an AI provider by this prototype.
Synthetic Polonnaruwa calculation results
Reporting years end in August. Maha is attributed to its ending year and Yala to that same year; the weather interval runs from September of the preceding year through August. This is an explicit demonstration policy based on the documented season boundaries, not an approved institutional reporting rule. The synthetic grid weights are 0.25 and 0.75.
Reporting year 2023 (2022-09-01 to 2023-08-31): fictional variety areas Bg 300: 100; Bg 352: 60 ha; gross seasonal cultivated area 160 ha; area-weighted annual rainfall 1300 mm; temperature 28.5 degrees C. Unique physical land area is unavailable without plot/overlap evidence.
Reporting year 2024 (2023-09-01 to 2024-08-31): fictional variety areas Bg 300: 120; Bg 352: 80 ha; gross seasonal cultivated area 200 ha; area-weighted annual rainfall 1500 mm; temperature 29.5 degrees C. Unique physical land area is unavailable without plot/overlap evidence.
The 2023 rainfall calculation is 0.25 × 1,000 + 0.75 × 1,400 = 1,300 mm. Temperature is 0.25 × 27 + 0.75 × 29 = 28.5 degrees C because the two grid summaries cover the same full reporting interval. The 2024 figures use the corresponding complete 366-day interval. These weather values are calculated once before joining the category summaries.
A rerun after correction creates a new source/method snapshot and preserves the original manifest. The ordinary report wizard exposes missing weather coverage, incompatible periods, repeated categories, restricted sources and ambiguous meanings as failures rather than plausible numbers. Exact manifest fields and rows are supplied in the downloadable worked example.
Research and integration catalogue
The following are documented, replaceable examples. Source permissions, regional variants, calibration, siting, local network compatibility and operational acceptance must be confirmed before use. The controlled JSON catalogue supplies the full variable, accuracy, protocol, equipment, access and evidence records.
ClimaVue 50 G2, item 43314
Exact model and configuration: ClimaVue 50 G2, item 43314
Manufacturer: Campbell Scientific
Classification: Compact weather sensor; not a complete Internet station
Measured variables
Air temperature (°C): ±0.6 °C. Published measuring range −50 to +60 °C; siting and radiation correction apply. Sources: ARC-S01; ARC-S43; ARC-S44.
Rain accumulation/rate (mm / mm/h): ±5% of measurement. 0–1, 000 mm/h accuracy band; measurement range to 1, 500 mm/h. Liquid precipitation only. Sources: ARC-S01; ARC-S43; ARC-S44.
Relative humidity (%RH): ±2.5% RH typical on current product page. Temperature/humidity dependent; older indexed manual states ±3% RH typical. Supplier must resolve revision. Sources: ARC-S01; ARC-S43; ARC-S44.
Barometric pressure (hPa): ±0.1 hPa at −10 to +50 °C; ±0.5 hPa at −40 to +60 °C on current page. Older indexed manual states ±5 hPa at 25 °C. Do not combine these as equivalent specifications. Sources: ARC-S01; ARC-S43; ARC-S44.
Wind speed (m/s): 0.3 m/s or 6%, whichever is greater. Published range 0–60 m/s; site exposure applies. Sources: ARC-S01; ARC-S43; ARC-S44.
Wind direction (degrees): ±5°. Published 0–359° range; orientation must be recorded. Sources: ARC-S01; ARC-S43; ARC-S44.
Solar radiation (W/m²): ±5% of measurement, typical. Published 0–1, 750 W/m² range; keep sensor level. Sources: ARC-S01; ARC-S43; ARC-S44.
Vapour pressure (kPa): ±0.2 kPa typical below 40 °C. Calculated from temperature/humidity; accuracy varies with both. Sources: ARC-S01; ARC-S43; ARC-S44.
Tilt (degrees): ±1°. Published 0–180° range; supporting instrument-health variable. Sources: ARC-S01; ARC-S43; ARC-S44.
Lightning strike count (strikes): >25% detection at distances under 10 km, typical. Detection varies with distance; not warning authority. Sources: ARC-S01; ARC-S43; ARC-S44.
Lightning average distance (km): Variable; no fixed accuracy adopted. Published 0–40 km range and 3 km resolution. Sources: ARC-S01; ARC-S43; ARC-S44.
Precipitation electrical conductivity (Not confirmed in reviewed specification extract): Not confirmed. Listed among measurements; obtain exact field/unit/method before enabling mapping. Sources: ARC-S01; ARC-S43; ARC-S44.
Accuracy: Temperature ±0.6 °C; rain ±5% at 0–1, 000 mm/h. Variable-specific conditions and the RH/pressure document discrepancy are listed below. Supplier confirmation is required before procurement or scientific use.
Protocol: SDI-12. Overview identifies an eight-pin M12 connector; the specification also uses AQ terminology. Confirm the delivered cable/connector and compatible logger.
Equipment: Compatible SDI-12 logger. Aspen10 is documented; mounting, power and permitted network are separate components.
Power: 3.6–15 V DC. At 12 V: 1.0 mA average using R7! every 10 s; 0.4 mA every 60 s or slower; peak 33 mA. Size logger, modem and power reserve separately.
Connectivity: Logger/edge uplink. No direct sensor web API established.
Maintenance: Check tilt/level and funnel contamination; retain service/calibration record.
Data access: Authorised logger export/adapter into common intake.
Restrictions: No heated solid-precipitation capability. Product/manual discrepancies need supplier resolution. Lightning detection is not an authorised hazard warning.
Local uncertainties: Local availability, scientific approval, installation design, radio/network suitability and institutional acceptance remain unverified.
Downstream use: Weather observations and coverage-aware Expert Hub comparisons.
Source date: 2026-11-02
Status: Optional extension; researched documentation only
Cost category: Current local quotation and lifetime operating cost not established.
Sources: ARC-S01; ARC-S43; ARC-S44
WXT536 within WXT530 series
Exact model and configuration: WXT536 within WXT530 series
Manufacturer: Vaisala
Classification: Weather transmitter; logger,power and communication unit separate
Measured variables
Temperature (°C): ±0.3 °C at +20 °C for the sensor element. Naturally aspirated shield can affect readings in calm wind. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Relative humidity (%RH): ±3% RH at 0–90% RH; ±5% RH at 90–100% RH. Sensor-element specification; natural aspiration caveat applies. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Pressure (hPa): ±0.5 hPa at 0 to +30 °C; ±1 hPa at −52 to +60 °C. Specified for 600–1, 100 hPa. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Rain accumulation/intensity (mm / mm/h): Better than 5% for daily accumulation, weather dependent. Liquid precipitation; excludes wind-induced error. Totals are cumulative since reset. Intensity range 0–200 mm/h, wider with reduced accuracy. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Wind speed (m/s): ±3% at 10 m/s. Observation range 0–60 m/s. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Wind direction (degrees): ±3° at 10 m/s. Averaging interval and sampling rate are configurable. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Hail detection/intensity (hits/cm² / hits/(cm²·h)): No fixed hail accuracy adopted. Manufacturer reports hail-hit outputs; do not convert these to rainfall volume. Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40.
Accuracy: Element temperature ±0.3°C at20°C; wind±3% at10m/s; daily rain better than5%, weather-dependent, excluding wind-induced error. Calm-weather natural aspiration affects field equivalence.
Protocol: SDI-12, ASCII automatic/polled, NMEA 0183 with query option, or Modbus RTU; configurable RS-232/485/422 or SDI-12 interfaces. Confirm ordered mode and wiring.
Equipment: Compatible logger, mast, power and uplink. AWS810/DMU801 is one documented station context.
Power: 5–32 V DC power-up per M211840EN-G. Current consumption depends on mode, interface and intervals; optional heating requires a separately checked power budget.
Connectivity: Serial/logger boundary is not an Internet API.
Maintenance: Inspect siting, shield and precipitation surface; retain service/calibration.
Data access: Authorised logging adapter; not connected in prototype.
Restrictions: Solar radiation is not included in this standard variable bundle. Rain totals have reset semantics.
Local uncertainties: Local availability, scientific approval, installation design, radio/network suitability and institutional acceptance remain unverified.
Downstream use: Weather datastreams and explicitly weighted area comparisons.
Source date: 2026-11-02
Status: Optional extension; researched documentation only
Cost category: Current local quotation and lifetime operating cost not established.
Sources: ARC-S02; ARC-S03; ARC-S04; ARC-S40
Davis Instruments DEV-03
Exact model and configuration: Wireless Vantage Pro2 6323M metric sensor suite with 24-hour fan-aspirated shield
Manufacturer: Davis Instruments
Classification: Wireless sensor suite plus separate gateway/service
Measured variables
Outside temperature (°C): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S05; ARC-S06; ARC-S07; ARC-S08; ARC-S13; ARC-S15.
Outside humidity (%RH): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S05; ARC-S06; ARC-S07; ARC-S08; ARC-S13; ARC-S15.
Wind speed/direction (m/s / degrees): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S05; ARC-S06; ARC-S07; ARC-S08; ARC-S13; ARC-S15.
Rain accumulation (mm): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S05; ARC-S06; ARC-S07; ARC-S08; ARC-S13; ARC-S15.
Accuracy: Manufacturer-linked family sheet: outside temperature ±0.5 °C typical; rain ±3% or one 0.2 mm tip up to 250 mm/h. Confirm these against the current exact regional SKU. Unlisted per-variable tolerances are not adopted.
Protocol: Compatible Davis wireless receiver, then authorised WeatherLink v2 API.
Equipment: WeatherLink Live 6100 or another compatible receiver, router, separate gateway power and mounting. UV, solar, soil and leaf sensors are optional.
Power: Suite solar/battery; gateway has separate supply; fan backup and servicing add operating requirements.
Connectivity: WeatherLink Live Wi-Fi/Ethernet. Local app cadence differs from cloud/API.
Maintenance: Clean gauge/shield; inspect fan, batteries, alignment using current manual.
Data access: Owned/shared eligible account and protected API key/secret; subscription controls history.
Restrictions: Verify metric/US order, regional radio band and entitlement. Public webpage is not API permission.
Local uncertainties: Local availability, scientific approval, installation design, radio/network suitability and institutional acceptance remain unverified.
Downstream use: Station observations retaining packet, unit, time; not automatic district coverage.
Source date: 2026-11-02
Status: Optional extension; credential-blocked integration
Cost category: Current local quotation and lifetime operating cost not established.
Sources: ARC-S05; ARC-S06; ARC-S07; ARC-S08; ARC-S13; ARC-S15
TEROS 12 with compatible ZL6 logger option
Exact model and configuration: TEROS 12 with compatible ZL6 logger option
Manufacturer: METER Group
Classification: Soil sensor; logger/gateway separate
Measured variables
Volumetric water content (m³/m³): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S09.
Temperature (°C): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S09.
Bulk electrical conductivity (µS/cm): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S09.
Accuracy: VWC ±0.03 m³/m³, typical in mineral soils with solution EC below 8, 000 µS/cm; medium-specific calibration ±0.01–0.02. Temperature ±1 °C from −40 to 0 °C and ±0.5 °C from 0 to +60 °C. Bulk EC ±(5% + 10 µS/cm) from 0–10, 000; ±8% from 10, 000–20, 000 µS/cm.
Protocol: DDI serial or SDI-12
Equipment: ZL6, EM60, Em50 or another compatible 4–15 V DC serial/SDI-12 logger. Retain depth and location metadata.
Power: 4–15VDC sensor; logger/uplink power separate.
Connectivity: Sensor cable to logger; connected logger/cloud entitlement separately verified.
Maintenance: Ensure soil contact, depth and calibration; verification clip or medium-specific calibration as justified.
Data access: Authorised logger file/API after provider contract verification.
Restrictions: BulkEC is not pore-waterEC or laboratory extractEC. Depth/deployment affect meaning.
Local uncertainties: Local availability, scientific approval, installation design, radio/network suitability and institutional acceptance remain unverified.
Downstream use: Soil observations, definition-evolution example and land-management evidence.
Source date: 2026-11-02
Status: Optional extension; researched documentation only
Cost category: Current local quotation and lifetime operating cost not established.
Sources: ARC-S09
OTT HydroMet DEV-05
Exact model and configuration: ecoLog 1000 SKU 5545000190-10UC, 0–10 m, 26 Ah, conductivity-equipped LTE-M example
Manufacturer: OTT HydroMet
Classification: Pressure/temperature/conductivity logger with cellular modem
Measured variables
Pressure-derived water level (m relative to declared datum): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S10; ARC-S11; ARC-S12.
Temperature (°C): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S10; ARC-S11; ARC-S12.
Conductivity (µS/cm or mS/cm): See the device accuracy conditions; any unlisted variable-specific tolerance must be confirmed.. Use the exact manufacturer revision and ordered variant; no local deployment validation has been completed. Sources: ARC-S10; ARC-S11; ARC-S12.
Accuracy: Pressure±0.05%FS; temperature±0.1°C. EC±0.5%(minimum1µS/cm) at5–2000µS/cm; ±1.5%(minimum0.01mS/cm) at0.1–100mS/cm; EC calibration5–45°C.
Protocol: Listed HTTPS/TLS1.2, HTTP, FTP/FTPS, MQTT/MQTTS; BLE service.
Equipment: Correct modem/SIM/antenna, probe/cable, mounting, water-level datum and authorised receiving endpoint.
Power: 3.6 V, 26 Ah lithium battery for the researched option. Life depends on sampling, transmission, temperature and conductivity operation.
Connectivity: The 10UC example uses LTE-M. Family EU 4G/2G variants differ; suitability for a local mobile network is unverified.
Maintenance: Inspect pressure datum/vent, fouling, calibration and battery; current regional manual required.
Data access: Authorised IP/file adapter only; real device not configured.
Restrictions: 10U lacks conductivity; 10UC includes it. Do not generalise across family variants.
Local uncertainties: Local availability, scientific approval, installation design, radio/network suitability and institutional acceptance remain unverified.
Downstream use: Water-level/quality observations. Reservoir volume requires reviewed level-volume relationship.
Source date: 2026-11-02
Status: Optional extension; official documentation partly available, no device test
Cost category: Current local quotation and lifetime operating cost not established.
Sources: ARC-S10; ARC-S11; ARC-S12
WeatherLink v2 authorised station data
Type: Station observations through provider cloud
Variables: Configured sensor-type weather fields
Source date: 2026-11-02
Status: Credential-blocked integration
Endpoint example: GET https://api.weatherlink.com/v2/current/{station-id}?api-key={server-side-key}
Coverage: Entitled owned/shared/qualifying stations only
Time coverage: History depends on entitlement. Unix timestamps mark the archive interval end; the historic API selects (start, end]. Preserve the source interval and timezone.
Latency: Basic 15-minute current, Pro 5-minute, Pro+ most recent for WeatherLink Live
Authentication: api-key query and X-Api-Secret header; protected server-side adapter
Licensing: Station relationship, subscription and redistribution permission required
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: station_id, sensors, sensor_type, data_structure_type, lsid, ts and sensor-specific data
Units: Preserve native units and map from exact sensor catalogue/data structure
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: 1000calls/hour, 10/second; history window≤86400seconds
Sources: ARC-S13; ARC-S14; ARC-S15; ARC-S16; ARC-S17; ARC-S39
Sri Lankan Weather Advisory System JSON
Type: Official issued warnings/advisories
Variables: Level, areas, language, validity, publication
Source date: 2026-11-02
Status: Credential-blocked integration
Endpoint example: GET https://was.meteo.gov.lk/api/warnings/changes?since={server-cursor}&lang=en
Coverage: Sri Lanka issued warning areas; not station coverage
Time coverage: Current and cursor changes; complete archive unverified
Latency: About60s changes polling recommended; no SLA
Authentication: X-API-Key; not obtained or used
Licensing: Read-only warning feed; preserve issuer/terms
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: id, day_key, name, level, valid_from, valid_to, summary_en/si/ta, areas_en, published_at; changes since
Units: Offset timestamps; no measured weather unit implied
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
Error handling: 401invalidkey, 400since/lang, 429ratelimit. Retain returned server cursor; never fabricate a newer cursor.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: 120requests/60s; limit1–200(default50)
Sources: ARC-S18
Sri Lankan Weather Advisory System CAP/RSS
Type: Official warning metadata and CAP1.2 XML
Variables: Alert identity, area, validity, language
Source date: 2026-11-02
Status: Successfully tested public read
Endpoint example: GET https://was.meteo.gov.lk/cap/en/rss.xml
Coverage: Sri Lanka warning areas
Time coverage: Active warnings; full archive not established
Latency: Provider issue/expiry distinct from fetch cadence
Authentication: Documented CAP/RSS requires no key
Licensing: Preserve issuing authority; review terms
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: RSS linking CAP1.2 XML resources
Units: Official event/area/timestamps
Pagination: Follow only authorised CAP links; retain replacements/cancellations.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Rate limited; confirm CAP-specific service policy
Sources: ARC-S18
Open-Meteo forecast
Type: Gridded weather-model forecast
Variables: temperature_2m, precipitation and selected variables
Source date: 2026-11-02
Status: Successfully tested public read
Endpoint example: GET https://api.open-meteo.com/v1/forecast?latitude=52.52&longitude=13.41&hourly=temperature_2m,precipitation&forecast_days=1&timezone=UTC
Coverage: Global model grid; resolution depends on product
Time coverage: Normally7days; up to16days per product
Latency: Model-run dependent; no operational latency commitment
Authentication: Keyless public evaluation; customer endpoint/plan separately authorised
Licensing: Weather data is CC BY 4.0 with attribution and modification notices. The free API service is non-commercial; commercial service use requires a suitable subscription.
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: hourly.time, value arrays, hourly_units, grid coordinates, timezone
Units: Tested temperature_2m°C, precipitationmm
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: Evaluation tier documented; production/commercial plan not selected.
Limits: Free600/min, 5000/hour, 10000/day, 300000/month at check date
Sources: ARC-S19; ARC-S21
Open-Meteo historical weather
Type: Gridded reanalysis/historical model
Variables: temperature_2m, precipitation and selected hourly measures
Source date: 2026-11-02
Status: Researched documentation; adapter simulated
Endpoint example: GET https://archive-api.open-meteo.com/v1/archive?latitude=7.9&longitude=81.0&start_date=2020-01-01&end_date=2020-01-02&hourly=temperature_2m,precipitation&models=era5&timezone=UTC
Coverage: ERA5/ERA5-Land/IFS distinct grids
Time coverage: ERA5from1940; ERA5-Landfrom1950; IFSfrom2017
Latency: Historical release/product-dependent
Authentication: Evaluation or licensed route as applicable
Licensing: Retain CC BY 4.0 attribution and product-specific provenance. Commercial historical API access requires Professional or higher at the checked date; no plan is selected.
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Time/value arrays, units; pin product/model
Units: Use returned units and interval meaning
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Bound ranges/variables and confirm account limits
Sources: ARC-S20; ARC-S21
NASA POWER Hourly
Type: Gridded assimilation/satellite-derived analysis
Variables: T2M and selected solar/meteorology
Source date: 2026-11-02
Status: Successfully tested public read
Endpoint example: GET https://power.larc.nasa.gov/api/temporal/hourly/point?parameters=T2M&community=SB&longitude=0&latitude=0&start=20170101&end=20170102&format=JSON&time-standard=UTC
Coverage: Native source grid point/regional product; not station observations
Time coverage: Hourlyfrom2001-01-01 to near-real-time
Latency: Source/parameter dependent
Authentication: Public unauthenticated read tested
Licensing: Preserve NASA source attribution and exact dataset terms
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: properties.parameter byvariable/hour; header and parameters
Units: Community/parameter-specific; testedT2M C; explicitUTC
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: At most15parameters/request; bounded windows
Sources: ARC-S22; ARC-S23
Irrigation Department authorised exchange
Type: Institutional water records/publications
Variables: Reservoir/rain/river data only after dataset agreement
Source date: 2026-11-02
Status: Researched source catalogue; operational adapter unavailable
Endpoint example: No verified public observation API;catalogue https://www.irrigation.gov.lk/web/index.php?lang=en
Coverage: Named stations/assets/basins; exact roster/version required
Time coverage: Dataset-specific
Latency: Owner update policy unconfirmed
Authentication: Operational feed access unknown; no credentials used
Licensing: Custodian use/redistribution agreement required
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Obtain approved file/API contract; retain asset/table/row/period
Units: Declared water-level datum, m³ or approved capacity unit, rainmm; gross/effective capacity separate
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Observation API/rate/size contract not established
Sources: ARC-S24
NSDI spatial metadata/services
Type: Institution-owned GIS services via catalogue
Variables: Permitted layer descriptions/places/geometries
Source date: 2026-11-02
Status: Researched documentation; endpoint not tested
Endpoint example: GET https://gisapps.nsdi.gov.lk/server/services/SLNSDI/Locations/MapServer/WMSServer?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities
Coverage: Layer extent, CRS, boundary edition, original scale
Time coverage: Layer version/validity
Latency: Owner-defined refresh
Authentication: Per-service access; discovery is not open feature permission
Licensing: Free/commercial datasets; owner approval
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: WMS1.3.0 capabilities documented; feature API only if separately authorised
Units: Layer CRS axes, scale and measurement semantics
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Per-service limits unverified; boundedBBOX/CRS
Sources: ARC-S25; ARC-S26; ARC-S38
DCS Paddy Statistics
Type: Official periodic tables
Variables: Sown/harvested area, yield, production
Source date: 2026-11-02
Status: Researched documentation; table-import adapter simulated
Endpoint example: Catalogue https://www.statistics.gov.lk/Agriculture/%20StaticalInformation/PaddyStatistics
Coverage: Published district/season/irrigation grain; variety breakdown not inferred
Time coverage: Maha cross-year, Yala; exact revised release
Latency: Seasonal publication and revision
Authentication: Public table documents; no API claim
Licensing: Confirm exact release rights
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Season, district, area meaning, unit, extent, yield, production, release
Units: Metric/imperial separate; ha, t/ha, t only when table specifies
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Complete deterministic table parsing
Sources: ARC-S27
DOA SEPC / Agstat
Type: Official agriculture publications
Variables: Agstat, cultivation cost, crop forecasts, budgets
Source date: 2026-11-02
Status: Researched documentation; document-import fallback
Endpoint example: Catalogue https://doa.gov.lk/sepc-downloads_en/
Coverage: Publication-specific geographic grain
Time coverage: Periodic editions
Latency: Publication schedule; not real-time
Authentication: Public catalogue; API discovery unreadable, so no routes inferred
Licensing: Edition/rights need custodian review
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Table/page/schema contract; no undocumented API
Units: Table-specific unit, season, crop meaning
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Parse all rows deterministically
Sources: ARC-S28
DMC official warning documents
Type: Issued bulletins/withdrawals
Variables: Issuer, issue/validity, area, replacement
Source date: 2026-11-02
Status: Researched documentation; manual/reference fallback
Endpoint example: Catalogue https://www.dmc.gov.lk/index.php?Itemid=279&lang=en&option=com_dmcreports&report_type_id=8&view=reports
Coverage: Named basins/areas in bulletin
Time coverage: Dated notices; complete archive not guaranteed
Latency: Issue time; no polling SLA
Authentication: Public document list; no API inferred
Licensing: Preserve issuer; automation/reproduction rights reviewed
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Document with exact page and metadata
Units: Source-issued warning classifications; no sensor-derived authority
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: Bounded catalogue checks
Sources: ARC-S29
LUPPD authorised land-use release
Type: Custodian spatial/statistical release
Variables: Land-use classes, coverage, planning definitions
Source date: 2026-11-02
Status: External institutional dependency; current interface unavailable
Endpoint example: No verified endpoint;retain existing LUPPD source identity and approved file/manual fallback
Coverage: Official coverage/geometry/class release unconfirmed
Time coverage: Release-specific
Latency: Unconfirmed
Authentication: Custodian agreement; no verified public API
Licensing: Rights and exact release unconfirmed
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Reuse authorised GIS/file intake; retain institutional claims
Units: Owner-declaredCRS, area unit, categorical meaning
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: No machine contract verified
Sources: No verified current interface reference; institutional confirmation required.
CEA water-quality institutional source
Type: Official laboratory reports and environmental data catalogue
Variables: Approved sample parameters, laboratory method and results; exact released table required
Source date: 2026-11-02
Status: Researched official source; authorised report/file fallback
Endpoint example: Catalogue https://cea.lk/web/en/2013-05-07-07-51-07/environmental-pollution-contorl-division/water-quality-unit
Coverage: Named water bodies/sites and sample locations; no project-area coverage inferred
Time coverage: Release/sample-specific; complete archive not established
Latency: Owner publication or authorised exchange schedule
Authentication: Public service catalogue; restricted records require custodian agreement
Licensing: Exact dataset and reuse rights unconfirmed; some laboratory/project services commercial
Permissions: Source owner and intended audience must authorise use; no blanket redistribution claim.
Schema: Source report/table, sample identity, location, depth, time, method, result, unit and qualifier
Units: Parameter- and method-specific; retain detection limits and censored values
Pagination: Provider-specific bounded pages/windows; retain cursor, overlap and replay-safe source key.
If a delivery fails, check the response and field definitions. Keep rejected data for review. Retry after a delay, resume from the last processed record and skip duplicates. Record a missing delivery separately from a zero reading.
Freshness: Keep phenomenon period, provider issue time, receipt and last successful fetch separately; show stale coverage.
Cost category: No price adopted; institutional/service cost and procurement remain unconfirmed.
Limits: No public observation API contract established
Sources: ARC-S41; ARC-S42
Complete source locators and provider options
The references below identify the publisher and supporting passage for devices, data services, mapping, reporting and document extraction. See From a rain gauge to a recorded reading and From a document to a checked value for the related workflows.
ARC-S01 Campbell Scientific ClimaVue 50 G2
https://www.campbellsci.com/products/climavue50-g2 Overview and Specifications: supply, Air Temperature, Wind Speed, Precipitation SDI-12; compatible Aspen10/loggers; 3.6–15VDC; temperature±0.6°C; wind max(0.3m/s, 6%); rain±5% at0–1000mm/h. Liquid precipitation and stated siting/operating conditions. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S02 Vaisala WXT536 station context
https://docs.vaisala.com/r/M212902EN-G/en-US/GUID-E6912022-5F36-44DF-90CA-2721236D948C Vaisala Weather Transmitter WXT536 WXT536 is a transmitter within a complete station. Power, logger and communications are separate responsibilities. Version: M212902EN-G. Checked: 2026-11-02. Status: Researched documentation
ARC-S03 Vaisala WXT536 specifications
https://docs.vaisala.com/r/M212902EN-G/en-US/GUID-AD3DAFAA-7537-453B-969B-B3229E311DD7 Measurement tables and footnotes1, 2, 5, 7 Temperature sensor element±0.3°C at20°C; wind±3% at10m/s; daily rain better than5%, weather-dependent, excluding wind-induced error. Natural aspiration affects calm-weather readings. Version: M212902EN-G. Checked: 2026-11-02. Status: Researched documentation
ARC-S04 Vaisala configurable WXT530
https://store.vaisala.com/en/products/WXT530 Digital outputs and WXT536 variant Official indexed catalogue lists SDI-12, RS-232, RS-485, RS-422. Page body unreadable; confirm exact power, heater, protocol and order bundle. Version: Current configurable family. Checked: 2026-11-02. Status: Official source partly readable
ARC-S05 Davis Vantage Pro2 fan-aspirated suite
https://www.davisinstruments.com/products/wireless-vantage-pro2-iss-with-24-hr-fan-aspirated-radiation-shield Product title and Highlights Listed6323/6323M; outside temperature/RH, wind, rain; solar/battery. WeatherLinkLive6100 is optional. UV, solar-radiation and soil/leaf sensors are additional options. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S06 Davis WeatherLink Live
https://www.davisinstruments.com/pages/weatherlink-live Live Data; Wi-Fi and Ethernet; compatible stations Separate compatible wireless gateway with Wi-Fi/Ethernet uplink. Local same-network app cadence differs from cloud API permissions. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S07 Davis wireless family specification
https://cdn.shopify.com/s/files/1/0515/5992/3873/files/6152_6162_6153_6163_Spec_SheetFF__Web.pdf?v=1661460993 Printed pp1, 5, 6, 8: rain tip, rainfall, outside temperature, wind Metric tip0.2mm; rain total±3% or one tip up to250mm/h; outside temperature±0.5°C typical. Family sheet is not proof of unchanged current regional SKU. Version: Manufacturer-linked historical family sheet. Checked: 2026-11-02. Status: Researched documentation
ARC-S08 Davis fan-aspirated ISS addendum
https://cdn.shopify.com/s/files/1/0515/5992/3873/files/VP2_Fan_Aspirated_ISS_Rev_C.pdf Printed p7 Fan-Aspirated Shield Specifications; maintenance Solar-powered fan, backup cells and cleaning/service requirements. Reconcile historical manual with current purchased hardware. Version: RevC22March2006. Checked: 2026-11-02. Status: Researched documentation
ARC-S09 METER TEROS12
https://metergroup.com/products/teros-12/ Measurement, Communication, Electrical Specifications VWC, temperature, bulkEC; DDI/SDI-12; 4–15VDC; compatibleZL6/EM60/Em50. Generic mineral-soilVWC±0.03m³/m³ when solutionEC<8000µS/cm; medium calibration±0.01–0.02. BulkEC is not laboratory/pore-waterEC. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S10 OTT ecoLog1000 conductivity SKU
https://www.ott.com/products/5545000190-10uc Product title and Technical Attributes 5545000190-10UC:0–10m, 26Ah, conductivity, LTE-M. Pressure±0.05%FS; temperature±0.1°C; EC conditions vary. Later full-page reads timed out; official indexed specifications retained. Version: Exact10UC variant. Checked: 2026-11-02. Status: Official documentation partly available; no device test
ARC-S11 OTT ecoLog1000 instructions
https://www.ott.com/download/operating-instructions-groundwater-datalogger-ott-ecolog-1000-5/ Section2.2 USA variant table Indexed manufacturer manual distinguishes10U from conductivity10UC, LTE-M. Current download redirects; obtain current regional manual before purchase. Version: Indexed manual; direct download unresolved. Checked: 2026-11-02. Status: Current direct download unavailable
ARC-S12 OTT ecoLog1000 data sheet
https://www.ott.com/products/download/data-sheet-ott-ecolog-1000-en/ Communications, measured values, power Indexed sheet distinguishes EU4G/2G and globalLTE-M. Conductivity optional at family level. Current link redirects to general resources. Version: Indexed sheet; current link redirects. Checked: 2026-11-02. Status: Current direct download unavailable
ARC-S13 WeatherLinkv2 introduction
https://weatherlink.github.io/v2-api/ Station access criteria Ownership, owner-share or qualifying upgrade determines access. Public visibility does not grant unrestricted observation API access. Version: WeatherLinkv2. Checked: 2026-11-02. Status: Researched documentation
ARC-S14 WeatherLink authentication
https://weatherlink.github.io/v2-api/authentication API Key; API Secret api-key query parameter and X-Api-Secret header. Connector keeps credentials server-side and redacts URL logs. Version: WeatherLinkv2 current authentication. Checked: 2026-11-02. Status: Researched documentation
ARC-S15 WeatherLink data permissions
https://weatherlink.github.io/v2-api/data-permissions WeatherLink Console/Live table Basic 15-minute current records, no history; Pro 5-minute current and history; Pro+latest/history, subject to station relationship. Version: WeatherLinkv2. Checked: 2026-11-02. Status: Researched documentation
ARC-S16 WeatherLink rate limits
https://weatherlink.github.io/v2-api/rate-limits Default rate limits 1000calls/hour and10calls/second per API key. Version: WeatherLinkv2. Checked: 2026-11-02. Status: Researched documentation
ARC-S17 WeatherLink size limits
https://weatherlink.github.io/v2-api/size-limits Historic windows Starting/ending Unix timestamps; historic request window at most86400seconds. Version: WeatherLinkv2. Checked: 2026-11-02. Status: Researched documentation
ARC-S18 Sri Lankan Weather Advisory System
https://was.meteo.gov.lk/api-docs Authentication; Warnings; Changes; Timestamps; CAP/RSS; Errors KeyedJSON warnings vs keylessCAP1.2/RSS; en/si/ta; 120requests/60s; limit1–200(default50); changes uses returned since cursor. This is an issued warning feed, not a station API. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S19 Open-Meteo forecast API
https://open-meteo.com/en/docs Weather Forecast API; hourly variables; response Gridded model forecast arrays with timestamps and units; retain product/run, resolution and interval. Not physical station observations. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S20 Open-Meteo historical weather
https://open-meteo.com/en/docs/historical-weather-api Historical Weather introduction/data sources ERA5from1940 at0.25°, ERA5-Landfrom1950 at0.1°, IFSfrom2017 at9km. Use consistent product for comparisons; coordinate is not district coverage. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S21 Open-Meteo access terms
https://open-meteo.com/en/pricing Free/Open Access table; FAQ Free API is non-commercial: 600/minute, 5,000/hour, 10,000/day, 300,000/month. Paid customer access differs; historical APIs require Professional or higher. Data is CC BY 4.0 with attribution; this differs from API-service terms. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S22 NASA POWER Hourly API
https://power.larc.nasa.gov/docs/services/api/temporal/hourly/ Formats; Time Standards; Limitations; Point examples Hourlyfrom2001; at most15parameters/request; UTC or defaultLocalSolarTime. FormatsJSON/CSV/NetCDF. Nativeparameter/community units. LST is not Sri Lankan civil time. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S23 NASA POWER data sources
https://power.larc.nasa.gov/docs/faqs/data/ Sources; Units; Latency Solar is satellite-informed modeled data; meteorology derives fromMERRA-2/GEOS-ITassimilation. Preserve source grid/resolution. Not station observations. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S24 Sri Lanka Irrigation Department
https://www.irrigation.gov.lk/web/index.php?lang=en Water Management; Hydrology; Publications; Flood Warning Official water/irrigation source discovery. Homepage does not establish public observation API, automated reuse rights or update SLA. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S25 Sri Lanka NSDI Geoportal
https://www.nsdi.gov.lk/geoportal Geoportal description Official spatial metadata/service discovery; per-layer authority, scale, rights and versions remain necessary. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S26 Sri Lanka NSDI FAQ
https://www.nsdi.gov.lk/faq Availability; publishing prerequisites Free and commercial datasets coexist; publishing links requires registration/institutionalMOU. Discovery is not blanket redistribution permission. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S27 DCS Paddy Statistics
https://www.statistics.gov.lk/Agriculture/%20StaticalInformation/PaddyStatistics Paddy Statistics definitions; tables; revision note MahaSep–Marfollowingyear; YalaApr–Aug. Asweddumized, sown, harvested differ. Production uses harvestedarea×crop-cuttingyield. Preserve revised releases; district totals do not imply variety breakdown. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S28 DOA SEPC downloads
https://doa.gov.lk/sepc-downloads_en/ Agstat, cost-of-cultivation, crop-forecast categories Official periodic agriculture/weather/paddy publications. Preserve edition, page/table, units/periods. Public API and redistribution licence not established. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S29 DMC flood warnings
https://www.dmc.gov.lk/index.php?Itemid=279&lang=en&option=com_dmcreports&report_type_id=8&view=reports Flood Warning and withdrawal notices Official bulletins/withdrawals. Preserve issuer, issue/validity, area and replacements; prototype thresholds cannot issue official warnings. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S30 OGC SensorThings Sensing1.1
https://docs.ogc.org/is/18-088/18-088.html Sections8.2.1–8.2.8; conformance Thing, Location/HistoricalLocation, Sensor, ObservedProperty, Datastream, Observation, FeatureOfInterest. A datastream has one sensor/property and units. Conceptual alignment is not certified conformance. Version: OGC18-088Version1.1; published2021-08-04. Checked: 2026-11-02. Status: Researched documentation
ARC-S31 Kimball declared grain
https://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/dimensional-modeling-techniques/grain/ Grain Declare what one fact row represents before choosing dimensions and facts. Grain is a binding design choice. Independent source aggregation before joining is the proposed architecture's application of this principle. Version: Author guidance. Checked: 2026-11-02. Status: Researched documentation
ARC-S32 Kimball stars and OLAP
https://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/dimensional-modeling-techniques/star-schema-olap-cube/ Star schemas and OLAP cubes Dimensional stars and multidimensional OLAP are analytical representations; retain grain and aggregation meaning. Version: Author guidance. Checked: 2026-11-02. Status: Researched documentation
ARC-S33 Open Data Cube
https://opendatacube.readthedocs.io/en/latest/ Overview; metadata; analysis; masking Gridded Earth-observation data/metadata across space, time, variable. CRS, mask, resolution and product definitions matter. Not a business approval ledger. Version: Latestdevelopmentdocsobserved1.9.23.dev65; pin chosen release. Checked: 2026-11-02. Status: Researched documentation
ARC-S34 OpenAI file inputs
https://developers.openai.com/api/docs/guides/file-inputs Input mechanisms; file-specific processing; spreadsheet augmentation; usage FileID, Base64 or URL inputs. PDFs include text/page images. Non-PDF embedded charts/images are not extracted. Spreadsheet processing uses first1000rows/sheet. Each file and combined request under50MB. Parse complete tables deterministically. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S35 OpenAI Structured Outputs
https://developers.openai.com/api/docs/guides/structured-outputs Supported schemas; edge cases; text.format JSON-Schema subset constrains shape. Responses text.format can usejson_schema/strict. Handle incomplete/refusal responses; schema conformity is not factual correctness. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S36 OpenAI File Search
https://developers.openai.com/api/docs/guides/tools-file-search File Search; results inclusion; metadata filtering Hosted vector-store retrieval with metadata filters/citations/results. Re-authorise current rights and versions before model context or result delivery. Search is not numerical authority. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S37 OpenAI data controls
https://developers.openai.com/api/docs/guides/your-data Endpoint retention; Responses; Files; residency Default abuse logs may retain content up to30days with exceptions. Response state, Files/vectorstores have distinct retention/deletion. Special retention/residency needs eligibility/configuration. No automatic zero-retention or Sri Lanka residency. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S38 NSDI Location WMS documentation
https://nsdi.gov.lk/location WMS GetCapabilities link ExactWMS1.3.0capabilityURL documented; no feature licence, completeness or service-availability inference. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S39 WeatherLink current and historic endpoint tutorial
https://weatherlink.github.io/v2-api/tutorial Steps 2–4; archive interval explanation Current endpoint and secret header verified. Historic records timestamp the interval end, with selection (start, end]; midnight can close the preceding day. Version: API v2 live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S40 WXT530 interfaces and option bundles
https://docs.vaisala.com/r/M211840EN-G/en-US/GUID-6B30C4BA-CEF6-40DF-9F60-41935D25AB9D Tables 1–2: features and available options Power-up 5–32 V DC; SDI-12, ASCII, NMEA 0183 and Modbus RTU protocols; RS-232/485/422 and SDI-12 interfaces. Heating and auxiliary inputs are configuration options. Version: M211840EN-G. Checked: 2026-11-02. Status: Researched documentation
ARC-S41 CEA laboratory services and surface-water source discovery
https://cea.lk/web/en/2013-05-07-07-51-07/environmental-pollution-contorl-division/water-quality-unit Water Quality Monitoring Unit; services; downloads Official laboratory services include inland water monitoring, analytical reports and a surface-water data download section. Some sample/project services are commercial. No public observation API is established here. Version: Official live documentation. Checked: 2026-11-02. Status: Researched documentation
ARC-S42 CEA selected inland water bodies
https://www.cea.lk/web/en/component/content/article?id=1801&layout=edit Ambient Water Quality Monitoring of Selected Major Inland Surface Water Bodies Lists Kelani River, Diyawanna Oya, Maha Oya, Bolgoda Lake and Benthara Ganga. This programme list does not establish local project coverage or an automated feed. Version: Page last updated 2025-01-09. Checked: 2026-11-02. Status: Researched documentation
ARC-S43 ClimaVue 50 G2 manual, specification discrepancy
https://s.campbellsci.com/documents/us/manuals/climavue50g2.pdf Section 6, specifications Search-indexed manual reports typical RH ±3% and pressure ±5 hPa at 25°C, differing from current product page/brochure specifications. Resolve hardware/revision-specific specification with supplier. Version: Official manual; indexed copy predates current product-page check. Checked: 2026-11-02. Status: Researched official indexed manual; revision confirmation required
ARC-S44 ClimaVue 50 G2 manufacturer brochure
https://s.campbellsci.com/documents/us/product-brochures/b_climavue50-g2-a4-branded.pdf Specification headings: pressure, wind, solar, precipitation, tilt and lightning Current indexed brochure supports product-page pressure, wind, solar and precipitation values. Reconcile delivered hardware and calibration certificate with the older manual. Version: Official product brochure; revision date unconfirmed. Checked: 2026-11-02. Status: Researched official indexed brochure
6 2 Land Use Change Decision Rules
Published source and local validation
DEC-DP01-001 uses method LAND-CHANGE-1. Help a land-use planner find important changes inside the project area, assess the evidence and choose the next investigation.
Inputs. Use a fixed analysis boundary inside each division. Keep the project portion separate from the full administrative division. The three prototype areas and their shapes are fictional.
Group | Required information |
|---|---|
Source and observation | Publisher, original URL or file, dataset release, observation year and season where relevant. Creation or revision years do not automatically identify the observation period. |
Area and classification | Division code, fixed analysis boundary and area in hectares, boundary version, native class/code, proposed class and mapping version, physical land area versus seasonal crop extent. |
Values and quality | Original area and unit, explicit missing value/reason, unclassified area, coverage, area method, representation, coordinate system, raster resolution and local quality reference. |
Formulas and units
Calculation | Definition | Unit |
|---|---|---|
Net change | Later area minus earlier area | ha |
Percentage change | 100 times net change divided by earlier area; unavailable when earlier area is zero | % |
Annual change | Net change divided by elapsed years; interval average, not a forecast | ha/year |
Gross loss and gain | Loss sums matched areas leaving a class. Gain sums matched areas entering it. Net equals gain minus loss | ha |
Converted extent | Sum matched areas whose from and to classes differ. Count each area once, rather than adding all class gains to losses | ha |
Unit conversion | One hectare is 10000 square metres. Retain the original value and unit alongside the converted value | ha |
Comparison and input rules
1. Compare matching analysis boundaries, class definitions, measure types, methods, seasons and source series. Both endpoints must cover the complete selected area; otherwise withhold whole-area change and transitions.
2. Class totals plus unclassified area must equal the fixed analysis area. A blank stays missing and zero stays a known zero. Do not invent a balancing value or join chart lines across missing points.
3. Keep native source categories and codes. A conflicting proposed category is rejected. An ambiguous native class stays unresolved with a mapping note and is excluded from analysis until its mapping is resolved.
4. Order divisions by the largest absolute net class-area change, or by the largest absolute percentage change. Show both metrics and the class used. Allow any change, decreases or increases. Exclude zero-baseline percentages from percentage sorting. Sorting does not set an action threshold.
5. Real gross losses, gains and conversions require matched spatial observations. Net area totals cannot establish where conversion occurred. The prototype constructs fictional parcel histories to demonstrate the rule; its generator is not a real conversion-estimation method.
6. Example annual inputs update the in-page numerical records only after structural and area-total checks. Charts, transitions and exports use those revised records. Reference images retain their independently stated source, coverage and date. Official-source selections remain previews.
7. A decision example records the selected division, analysis scope, years, class, sorting rule, comparison, coverage, reason, next action, proposed responsible role, follow-up and dataset/boundary/class/method versions. Incompatible evidence forces a source-data check. Nothing is assigned or sent by the prototype.
Worked example using fictional data
Scope and period | Earlier forest ha | Later forest ha | Loss ha | Gain ha | Net ha |
|---|---|---|---|---|---|
Laggala Pallegama 2015 to 2019 | 6800 | 6782 | 26 | 8 | -18 |
All three examples 2015 to 2019 | 14900 | 14868 | 56 | 24 | -32 |
For Laggala Pallegama, net change is 6782 minus 6800 = -18 ha. Percentage change is 100 times -18 / 6800 = -0.2647%. Average annual change is -18 / 4 = -4.5 ha/year. Gross loss of 26 ha and gain of 8 ha reproduce the same -18 ha net change. These values do not establish actual project results.
The numerical transition example uses matched fictional area histories. Its independently sourced historical reference images are not generated from those records. Real transition areas require compatible dated observations, source permissions, definitions and quality evidence.
Sources and method categories
Government publication - Sri Lanka National Spatial Data Infrastructure. Planning Cadastre Landuse and Forest Boundary service metadata. Landuse layer 4 native classifications; Forest Boundary layer 1 forest_type domain and coordinate system. Native labels, codes and spatial metadata. The inspected metadata does not establish a comparable annual project series.
Source: Open reference
Supporting reference: Open reference
Institution publication - Copernicus Global Land Service. CGLS LC100 Collection 3 version 3.0.1. 2015 to 2019 product and discrete classification definitions. Annual broad cover classes at nominal 100 m. Woody crops can enter tree or shrub classes; this source alone cannot split every detailed local land use.
Source: Open reference
Supporting reference: Open reference
Government publication - Department of Census and Statistics Sri Lanka. Paddy Statistics. District and Maha or Yala seasonal extent definitions. Seasonal crop context. Sown, harvested and asweddumized extents are not interchangeable with a physical land-cover map.
Source: Open reference
Institution publication - Intergovernmental Panel on Climate Change. 2006 Guidelines Volume 4 Chapter 3. Sections 3.3 and 3.5 consistent land representation, net versus gross change and uncertainty. Methodological context for matched land representation and transition accounting. This prototype is not a greenhouse-gas inventory.
Source: Open reference
Institution publication - UN Handbook on Remote Sensing for Agricultural Statistics. Chapter 8 Map Validation and Use of Maps for Area Estimation. Sections 8.1, 8.3 and 8.5; Gilberto Camara and Lorenzo De Simone. Reference sampling, accuracy assessment and area uncertainty. A global accuracy figure does not replace local validation.
Source: Open reference
Validation required - SHARED project proposal. LAND-CHANGE-1 local comparison and screening specification. This decision specification and its fictional worked example. Local class grouping, scope, sorting choices and intended use require confirmation in Institution review. Arithmetic, conversion, consistency and input handling are developer checks.
Source: Open reference
Published definitions and methodological guidance retain their publisher and locator. Local grouping, scope, sorting criteria and intended use remain project proposals. Record client and expert confirmation in Institution review only. Developer checks cover arithmetic, units, class conflicts, area closure, missing values and consistent output.
Acceptance. Apply scenarios LU A1 to LU A6 in SRS section 5 6. The 22 retained calculation/input checks and 14 purpose checks are prototype software evidence, not independent scientific or stakeholder acceptance.
6 3 Domain Decision Rules
Current decision catalogue. The prototype shows 507 decisions. It retains 466 published method matches and adds 41 proposed decisions. Confirm local use in Institution review. Download the active source audit. See the 354 archived decisions.
Published method status. Verified published formula means the calculation matches its cited publication. Verified published component covers only the named part. The decision register gives the publisher and exact locator. Confirm local inputs, settings and intended use through Institution review.
Input checks follow the measurement definition. Keep valid signed measurements, reject impossible physical values, and distinguish wet-basis moisture percentages from other moisture bases. Published measurement definitions and source locators are listed in the calculation appendix. Local comparison limits still require confirmation in Institution review.
The current decision contracts retain all 820 IDs and 57 family IDs across 41 institutions. LAND-CHANGE-1 covers DEC-DP01-001; the other 819 decisions use 110 named variants. The 20 Meteorology decisions use their specific METEO-1 definitions in Weather data and Meteorology decisions. Use each decision ID and method version to select the matching rule.
For every decision, Decision_Register.csv and the online appendix record the question, typed fields, units, worked and changed examples, missing-input check, method version, source category and map role. The matching Institution review page contains the same current dashboard views and its review questions. Published observations retain their source, place and period; realistic examples remain labelled. Changes in one open page do not change another page or its saved feedback.
Use a published method only for its supported component and stated input convention. Local source matching, parameters, intended use and authority remain separate. Published methods and items needing confirmation are listed in Institution review.
Common checks
Retain area, period, units, definitions and source version. Copy source sheet and cell references exactly. Check ranges, balances and denominators. If evidence is missing, show the supported example result and state what is needed. Withhold calculations that require missing or invalid inputs.
Reference maps
The corrected decision examples use locally stored authentic reference images where geographic context helps. The Matale and Kandy district locators do not show the fictional proposal, reservation or hazard areas. The first land-use example also links to source-derived 2015 and 2018 forest-class images of a regional window. Image years and sources remain separate from the numerical example years. Existing live maps elsewhere in the prototype are preserved; this correction does not add or verify a live spatial integration. Target spatial requirements retain their existing scope and approval status.
Realistic examples and published observations
Use meaningful labels such as Bg 300, pepper exports, water-service zones and Laggala Pallegama. The rice grouped-count fixture remains 586 plots with a separate 804 ha area denominator. Its counts and variety allocation are illustrative. DCS and DOA publications support the crop and variety context, not those counts or institutional adoption.
DCS publishes paddy yields for whole districts. In the all-schemes kg per net hectare column, Kandy is 2859 in 2024 Yala and 3761 in 2025 Yala; Matale is 4500 and 4302; Nuwara Eliya is 3905 and 3941. Retain the period and net-hectare basis. Seasonal differences do not establish a cause.
Sources: Department of Census and Statistics Sri Lanka, Paddy Statistics metric district tables for 2024 Yala and 2025 Yala, page 1, all-schemes average yield column. Government publication.
Explicit domain variants
Field and map comparison
DEC-DP01-004 checks a place when the map and the field record describe it differently. A map label of Forest and a field description of trees mixed with crops are a reason to check the evidence.
Place and records. Demonstration case reference; Exact site or plot reference; Do both records cover the same place?; Map classification; Field classification; Field description.
Observation dates and definitions. Map observation date; Field observation date; Map classification scheme and version; Field classification scheme and version; Can the classification definitions be compared?; Can the observation periods be compared?; Evidence for matching place, periods and definitions.
Sources and review. Map source and version; Field record and version; Evidence reviewed in this example; What does the reviewed comparison show?; Reviewed document or site-evidence reference; Affected area, if measured (ha).
Method. Check the exact site and extent first; obtain both observation dates, source versions and classification definitions. Compare only documented matching records. Prepare a draft field check when a reviewed difference remains. Reviewed site evidence may support a proposed correction for later review.
Example. DEMO-MAP-01 has no exact site, observation dates or matching classification definitions, so request those records first. DEMO-MAP-03 has matching records and a reviewed difference, so prepare a draft field check. If the records are reconciled, prepare a comparison note. After site evidence is reviewed, a remaining difference supports a proposed correction for the responsible officer to check. Removing the site reference returns the case to an evidence request. These are realistic examples.
Source and limits. Validation required - SHARED project comparison rule. Forest and Agroforestry retain the definitions of their source schemes. Different labels, dates or extents do not establish an error, land-use change or legal status. A division name and reporting year do not identify a plot or date both observations. Demonstration progress grants no approval. Sources: DD-LOCAL. Exact locators are in the source register. A count of cases does not decide which record is correct.
Fragmentation
Total holding area / parcel count, alongside count and documented separation. This is a descriptive summary, not a validated fragmentation index or coordination decision. Result units: ha/parcel, parcels. Small parcels do not establish agreement to consolidate holdings. The holding area, parcel count and documented separation describe different aspects; no validated fragmentation index is produced.
Decision bindings: DEC-DP01-012. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Land change
Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion. Result units: ha, %. 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.
Decision bindings: DEC-DP01-013, DEC-DP07-001, DEC-DP12-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Erosion area
Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Result units: ha, %. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Decision bindings: DEC-DP02-003. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Water productivity
Saleable crop output / Matching irrigation water input, for the same product, process and period. Result units: kg/m³.
Decision bindings: DEC-DP02-010, DEC-DP05-013, DEC-DP06-011, DEC-DP10-014. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Cost ha
Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Result units: LKR/ha, LKR. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.
Decision bindings: DEC-DP02-017, DEC-DP03-002, DEC-DP10-003, DEC-DP33-006. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Rice plots
Plot share =100 × distinct eligible plots in category / eligible plots in all categories. Sown-area shares use a separate hectare denominator; grouped inputs do not verify plot identity. Result units: plots, %. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Decision bindings: DEC-DP03-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Dated variance
Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Result units: days.
Decision bindings: DEC-DP03-004, DEC-DP05-018, DEC-DP06-018, DEC-DP11-008, DEC-DP16-015, DEC-DP29-001, DEC-DP33-004. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Crop yield
Harvested crop output / Matching harvested crop area, for the same product, process and period. Result units: kg/ha.
Decision bindings: DEC-DP03-006, DEC-DP09-004. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Cash balance
Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume. Result units: LKR. Use the same physical boundary, period and units. A residual is a reconciliation issue, not automatically a measured loss.
Decision bindings: DEC-DP04-010, DEC-DP24-007, DEC-DP28-011, DEC-DP32-011, DEC-DP35-018, DEC-DP41-013. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Pump energy
Electric energy consumed / Water pumped, for the same product, process and period. Result units: kWh/m³.
Decision bindings: DEC-DP05-016, DEC-DP22-009. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Mahaweli plan
Compatible + conditional + reported conflict + unresolved area must equal total proposal area. Reported conflict share = 100 × conflict area / total proposal area. These are supplied area records, not a map calculation. Result units: ha, %. A percentage cannot establish plan compatibility or permission. Unresolved plan matches and conditions remain visible. The reference image is geographic context, not the source of these areas.
Decision bindings: DEC-DP06-008. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Mahaweli reservation
Reported overlap share = 100 × reported activity overlap / total observed activity area. Count common overlapping parts once in the supplied survey record. No map intersection is performed. Result units: ha, %. A reported overlap is not a finding of unlawful occupation. Confirm the applicable survey, reservation basis, permissions and inspection evidence. No fixed reservation width, eviction, penalty or safety determination is inferred.
Decision bindings: DEC-DP06-009. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Probability forecast
Use the METEO-1 definition for DEC-DP08-008 in Weather data and Meteorology decisions. It gives the current fields, calculation or review steps, matching records, source and limits.
Decision binding: DEC-DP08-008. Method: METEO-1. Sources: DD-BRIER, DD-LOCAL. The current online appendix entry uses the same decision ID.
Series mismatch
Use the METEO-1 definition for DEC-DP08-011 in Weather data and Meteorology decisions. It gives the current fields, calculation or review steps, matching records, source and limits.
Decision binding: DEC-DP08-011. Method: METEO-1. Sources: DD-LOCAL. The current online appendix entry uses the same decision ID.
Point overlay
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. Result units: %, facilities, assets. 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. Use the exact unit declared by the selected decision; compare matching units only.
Decision bindings: DEC-DP16-012, DEC-DP17-003. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register. DEC-DP08-016 uses the separate METEO-1 definition in Weather data and Meteorology decisions.
Numeric mismatch
Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Result units: kg, %, ha, mm, mg/kg, LKR, LKR/kg, t C/ha. Keep both originals, units, scope, method, calibration and correction history. A difference does not identify which source is correct; no automatic averaging or overwrite. Use the exact unit declared by the selected decision; compare matching units only.
Decision bindings: DEC-DP10-019, DEC-DP14-002, DEC-DP17-010, DEC-DP23-014, DEC-DP23-017, DEC-DP24-006, DEC-DP25-017, DEC-DP40-009. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register. DEC-DP08-018 uses the separate METEO-1 definition in Weather data and Meteorology decisions.
Lineage
Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Result units: items. Recorded lineage is not proof of product identity or recall authority. Preserve multi-source batches, transfers and versions; do not clear unlinked lots as safe.
Decision bindings: DEC-DP09-013, DEC-DP18-012, DEC-DP34-017, DEC-DP36-016. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Variety area
Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Result units: ha, %. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Decision bindings: DEC-DP10-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Cost progress
100 × spending/phased budget, and verified−planned physical progress. Do not subtract LKR from physical progress, infer earned value or equate expenditure with outcomes. Result units: %, percentage points.
Decision bindings: DEC-DP11-002. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Study design
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. Result units: items. The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence.
Decision bindings: DEC-DP12-007, DEC-DP35-004, DEC-DP40-012. Sources: S92, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Location mismatch
Display supplied location separation with the two reported accuracies and coordinate-reference evidence. Do not treat a matched name or boundary overlap as confirmed identity. Result units: m.
Decision bindings: DEC-DP13-004, DEC-DP31-004. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Feature changes
Changed-feature share = 100 × documented changed features / matching feature frame. Unchanged-or-no-reported-change = frame − changed − unknown. No material-change threshold is inferred. Result units: %, features. Count each eligible unit once for the selected service and period. Received messages, attendance, adoption and outcomes are separate measures.
Decision bindings: DEC-DP14-011. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Survey cost
Sum non-overlapping survey costs and divide by verified kilometres of the same survey work/terrain class. This does not compare unlike cadastral cases by an undefined survey count. Result units: LKR/km surveyed, LKR. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.
Decision bindings: DEC-DP14-018. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Schema mismatch
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. Result units: items.
Decision bindings: DEC-DP15-010. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Damage loss
Asset quantity × replacement/repair unit cost. Show interrupted economic flows separately; no automatic damage+flow total or double counting. Result units: LKR, LKR/period. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.
Decision bindings: DEC-DP16-002. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Weighted proportion
Weighted proportion = sum(weight×indicator0/1)/sum(weight). Report the classification and eligible population; use design information for uncertainty. Result units: 0 or1. Retain sampling frame, strata, clusters, nonresponse and calibration. The prototype does not invent complex-design variance, confidence intervals or small-area precision. These fictional binary observations demonstrate design weighting. Do not pool changed definitions, population frames or reference periods; no official rate or design variance is produced.
Decision bindings: DEC-DP20-001, DEC-DP20-015. Sources: S91, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Survey precision
Relative standard error=100×design-based SE/abs(estimate), only for a nonzero estimate and an actually supplied design-based SE. Sample count alone does not determine geographic precision. Result units: %. Retain sampling frame, strata, clusters, nonresponse and calibration. The prototype does not invent complex-design variance, confidence intervals or small-area precision. The estimate and standard error are fictional monthly household-income statistics. The 20% review criterion is illustrative; sample count alone does not supply a design-based standard error.
Decision bindings: DEC-DP20-003. Sources: S91, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Publication revision
Match the exact statistical series and version used by each listed publication against its replacement version. A publication using an older version, or with unknown update evidence, needs revision review. Count each listed publication once. Result units: publications. Only documented dependency records are checked. This does not discover unlisted publications or amend a published statistical estimate.
Decision bindings: DEC-DP20-004. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Weighted area production
Estimated production=sum(weight×production); estimated harvested area=sum(weight×area); aggregate yield=estimated production/estimated area. Do not average individual yields without the matching denominator. Result units: kg/ha. Retain sampling frame, strata, clusters, nonresponse and calibration. The prototype does not invent complex-design variance, confidence intervals or small-area precision.
Decision bindings: DEC-DP20-013. Sources: S91, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Groundwater trend
Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Result units: m. Groundwater head and depth below ground have opposite directional meanings. Match datum, pumping state and seasonal context; observed drawdown is not itself a safe-yield estimate. Heads refer to an arbitrary stated datum. Compare pumping state, season and measurement method; do not calculate relative percentage or infer sustainable abstraction.
Decision bindings: DEC-DP21-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Aquifer balance
Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing. Result units: m³. A storage-change calculation needs a defined aquifer boundary and compatible volume estimates. Groundwater head in metres is not a storage volume; uncertainty and safe-abstraction review remain separate.
Decision bindings: DEC-DP21-007. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Well proximity
Display measured separation with hydrogeological direction, source type and the reviewed protection criterion. Distance alone cannot determine contamination, safety or a statutory protection area. Result units: m. 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.
Decision bindings: DEC-DP21-008. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Drilling
Drilling cost / completed depth. Display tested yield and the stated success definition separately; cost per metre does not determine safe abstraction. Result units: LKR/m, L/s.
Decision bindings: DEC-DP21-016. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Billed water
NRW=input−billed authorized use. Water losses=NRW−unbilled authorized use. Residual real loss=water losses−estimated apparent losses, only when all components are available. Result units: m³, %. NRW is not all leakage. An unknown apparent-loss estimate keeps residual real loss unavailable. Meter uncertainty and matching time/zone boundaries matter.
Decision bindings: DEC-DP22-001. Sources: DD-NRW, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Leakage evidence
NRW=input−billed authorized use. Water losses=NRW−unbilled authorized use. Residual real loss=water losses−estimated apparent losses, only when all components are available. Result units: m³, %. NRW is not all leakage. An unknown apparent-loss estimate keeps residual real loss unavailable. Meter uncertainty and matching time/zone boundaries matter.
Decision bindings: DEC-DP22-002. Sources: DD-NRW, DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Supply outages
Time availability = 100 × (stated window − union of no-supply intervals) / positive stated window. Record interruption count and longest duration separately; count overlapping outage intervals once. Result units: %, events, hours. This is a fictional return for one stated supply zone and window. Time availability does not establish water quality, pressure, equitable household access or operational continuity.
Decision bindings: DEC-DP22-011. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Food basket
Basket cost = rice kg × rice LKR/kg + red-dhal kg × red-dhal LKR/kg + white-sugar kg × white-sugar LKR/kg. Compare locations only for the same quantities, product specifications, currency and price period. Result units: LKR. This is a fictional three-item basket with stated quantities. It is not an official consumer-price index, nutritional basket, current market quotation or household expenditure estimate.
Decision bindings: DEC-DP25-006. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Input expenditure
Specified quantity × comparable unit price. Sum only non-overlapping items from the same basket specification, location and price period. Result units: LKR. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable. Fictional same-grade urea prices are in LKR/kg. Quantity and unit price effects are kept separate; no current market price is implied.
Decision bindings: DEC-DP25-011. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Labour
Cash cost/ha = hired days×cash wage/area. Total effort/ha=(hired+unpaid family days)/area. Do not value unpaid labour as zero opportunity cost. Result units: LKR/ha, person-days/ha.
Decision bindings: DEC-DP25-013. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Export composition
Compute export-value and quantity shares independently within compatible product and reporting frames; never add currency and kilograms. Result units: LKR, %. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Decision bindings: DEC-DP26-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Export unit value
Recorded export value / Export quantity on matching product basis, for the same product, process and period. Result units: LKR/kg. A unit value mixes prices and product composition. It is not automatically a like-for-like market price. Match grade, product code, currency and period.
Decision bindings: DEC-DP26-004, DEC-DP37-004. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Human match
Match documented expertise, available effort, date windows and required conflict/clearance evidence. A match suggests a candidate; it appoints nobody. Result units: hours. A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract.
Decision bindings: DEC-DP27-007, DEC-DP40-011, DEC-DP41-012. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Business retention
Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it. Result units: %, enterprises. These bounds account for unknown status; they are not statistical confidence intervals. Use actual follow-up dates and distinguish cohort membership from repeated visits.
Decision bindings: DEC-DP27-009. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Plot match
Compare the same specification and unit, uncommitted quantity and overlapping delivery windows. Keep mandatory quality and use conditions explicit. Result units: m². A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract. Matching text and area do not establish actual utility capacity, rights, environmental permission or a plot allocation.
Decision bindings: DEC-DP28-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Resource efficiency
Energy/output; water/output; and 100 × output/material input. Separate denominators and units; do not sum these efficiencies. Result units: kWh/kg, m³/kg, %.
Decision bindings: DEC-DP28-006, DEC-DP34-011. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Feedback
Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Result units: cases, %. Categories must be mutually exclusive and cover the stated frame. Do not mix values, quantities, plots or hectares, or treat an HHI competition threshold as an institutional policy.
Decision bindings: DEC-DP31-020. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Cash timing
Order the supplied dated receipts and payments. Start with the stated opening cash; add each receipt and subtract each payment once. Minimum cash is the lowest chronological balance, including opening cash. Shortfall = max(0, −minimum cash). Closing cash is opening + receipts − payments. Result units: LKR. These are dated fictional cash assumptions, not actual bank balances or a credit recommendation. A positive closing balance can conceal an earlier shortage. Same-day receipt/payment ordering needs evidence.
Decision bindings: DEC-DP33-007, DEC-DP36-011, DEC-DP37-016, DEC-DP38-018. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Buyer offer
Net receipt per initial kg = quoted buyer price × (1 − assumed mass loss% / 100) − matching transfer/handling cost per initial kg. Do not subtract a trader purchase price from a farmer’s own produce. Result units: LKR/initial kg. Quotes, loss assumptions and costs are fictional. Compare matching grades, weighing bases, payment timing and terms. The result does not authorize a purchase, sale, financing or supply agreement.
Decision bindings: DEC-DP33-014. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Cost output
Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Result units: LKR/kg green leaf, LKR. An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable. The denominator is green leaf, not made tea. Compare the same moisture, weighing, cost and accounting-period basis.
Decision bindings: DEC-DP34-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Mass conversion
Gross recovery = 100 × made-tea mass / received green-leaf mass, on the explicitly stated incoming and outgoing moisture bases. This is not a dry-matter conversion efficiency. Result units: %. The fictional tea example uses 1,200 kg green leaf and 270 kg made tea. The unrepresented mass includes water removed and cannot all be called waste.
Decision bindings: DEC-DP34-010, DEC-DP37-001. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Procurement offer
Landed cost per retained kg = (purchase price per initial kg + matching transfer/handling cost per initial kg) / (1 − assumed mass loss% / 100), only when some mass is retained. Result units: LKR/retained kg, LKR/initial kg. Quotes, loss assumptions and costs are fictional. Compare matching grades, weighing bases, payment timing and terms. The result does not authorize a purchase, sale, financing or supply agreement.
Decision bindings: DEC-DP36-002. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Tonne km
Shipment cost / (actual load tonnes × verified route kilometres). Match empty-return treatment and cost allocation. Result units: LKR/(t km). An absent or zero denominator has no unit-cost result. Keep fixed, variable and opportunity costs identifiable.
Decision bindings: DEC-DP37-002. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Affected lots
Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Result units: items. Recorded lineage is not proof of product identity or recall authority. Preserve multi-source batches, transfers and versions; do not clear unlinked lots as safe.
Decision bindings: DEC-DP37-009. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Process energy
Energy consumed / Saleable product output, for the same product, process and period. Result units: kWh/kg.
Decision bindings: DEC-DP37-011. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Verification cost
Total checking cost = staff + travel + other non-overlapping costs. Cost per accepted hectare = total / accepted hectares. A zero accepted area has no unit-cost result. Result units: LKR/ha, LKR. Illustrative watershed-care agreement. Contract rules, rate, payer, monitoring and safeguards need confirmation in Institution review. Maintained hectares do not establish a measured water-quality improvement.
Decision bindings: DEC-DP39-004. Sources: DD-LOCAL, PES-FAO. Exact per-decision inputs and evidence remain in the controlled decision register.
Followup retention
Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it. Result units: %, participants. These bounds account for unknown status; they are not statistical confidence intervals. Use actual follow-up dates and distinguish cohort membership from repeated visits.
Decision bindings: DEC-DP40-016, DEC-DP41-017. Sources: DD-LOCAL. Exact per-decision inputs and evidence remain in the controlled decision register.
Mahaweli worked cases
DEC-DP06-008 Does this proposed use fit the system plan?
Fictional 2025 case in the Laggala Pallegama area. The Matale district image linked from this decision is geographic context; it does not establish Mahaweli jurisdiction, an official proposal boundary, a system plan or a reservation line.
Input | Starting value | Unit |
|---|---|---|
Case and version | Proposal 1 / 2025 — fictional | |
Geographic context | Laggala Pallegama geographic context; exact system jurisdiction is separate | |
Exact site or asset reference | Not provided | |
Applicable system jurisdiction established in this example | Missing | |
Source for the applicable system office | Not provided | |
Boundary and source edition | Fictional survey record / edition 1 | |
Matching survey and area definitions available in this example | Provided | |
Proposed land use | Agricultural storage and access — fictional proposal | |
Applicable plan and version | Fictional system plan / edition 1 | |
Applicable plan and rules available in this example | Provided | |
Total proposal area | 10 | ha |
Area matching the stated plan use | 4 | ha |
Area with conditions to review | 3 | ha |
Area with a reported plan conflict | 2 | ha |
Area without a confirmed plan match | 1 | ha |
Conditions and rule reference | Fictional conditions: check access and drainage; no official threshold is supplied | |
Affected tenure and rights evidence | Missing |
Result. 10 ha proposed: 4 ha match the example plan, 3 ha have conditions, 2 ha have a reported conflict (20.0%), and 1 ha remain unmatched. No land-use permission is granted. Still needed: Exact site or asset reference; Applicable system jurisdiction and source for the responsible system office; Plan matches for the unmatched area; Affected tenure and rights evidence. The figures describe the supplied example records; they do not settle these gaps. Next check: Obtain the exact site and applicable system-office evidence.
Changed input. Exact site or asset reference = DEMO-CHECKED-SITE; Applicable system jurisdiction established in this example = Provided; Source for the applicable system office = DEMO-OFFICE-SOURCE; Affected tenure and rights evidence = Provided; Area matching the stated plan use = 5; Area without a confirmed plan match = 0. 10 ha proposed: 5 ha match the example plan, 3 ha have conditions, 2 ha have a reported conflict (20.0%), and 0 ha remain unmatched. No land-use permission is granted. Next check: Refer the reported conflict to the planning officer.
Missing source. No usable result. Matching survey and area definitions. Obtain the matching survey before interpreting the supplied areas. No permission, violation or enforcement action is inferred.
Requirements: FR063, FR095, SH-GEO-FEAT-014, SH-GEO-FEAT-020. Method MAHAWELI-1. The online appendix entry, decision page and Institution review use this same stable decision ID.
DEC-DP06-009 Does this activity overlap a reservoir or canal reservation?
Fictional 2025 case in the Laggala Pallegama area. The Matale district image linked from this decision is geographic context; it does not establish Mahaweli jurisdiction, an official proposal boundary, a system plan or a reservation line.
Input | Starting value | Unit |
|---|---|---|
Case and version | Inspection 1 / 2025 — fictional | |
Geographic context | Laggala Pallegama geographic context; exact system jurisdiction is separate | |
Exact site or asset reference | Not provided | |
Applicable system jurisdiction established in this example | Missing | |
Source for the applicable system office | Not provided | |
Boundary and source edition | Fictional survey record / edition 1 | |
Matching survey and area definitions available in this example | Provided | |
Reservoir or canal and case reference | Reservoir-side activity — exact site not provided | |
Activity observed | Temporary material storage — fictional observation | |
Inspection date | 2025-06-12 | |
Reservation survey and basis available in this example | Provided | |
Total observed activity area | 0.6 | ha |
Reported activity area inside the reservation | 0.15 | ha |
Matching permission record | Missing | |
Permission reference or reason it is unknown | No matching permission has been supplied in this fictional case | |
Maintenance access reported obstructed | Unknown |
Result. 0.15 ha of the 0.6 ha observed activity is reported inside the reservation (25.0%). A matching permission is missing or disputed. This does not establish unlawful occupation. Still needed: Exact site or asset reference; Applicable system jurisdiction and source for the responsible system office; Matching permission record and conditions; Inspection evidence about maintenance access. The figures describe the supplied example records; they do not settle these gaps. Next check: Obtain the exact site and applicable system-office evidence.
Changed input. Exact site or asset reference = DEMO-CHECKED-ASSET; Applicable system jurisdiction established in this example = Provided; Source for the applicable system office = DEMO-OFFICE-SOURCE; Reported activity area inside the reservation = 0.05; Matching permission record = Provided; Permission reference or reason it is unknown = DEMO-PERMISSION; Maintenance access reported obstructed = No. 0.05 ha of the 0.6 ha observed activity is reported inside the reservation (8.3%). A permission reference is supplied for review. This does not establish unlawful occupation. Next check: Review the activity against the documented permission.
Missing source. No usable result. Matching survey and area definitions. Obtain the matching survey before interpreting the supplied areas. No permission, violation or enforcement action is inferred.
Requirements: FR063, FR095, SH-GEO-FEAT-014, SH-GEO-FEAT-020. Method MAHAWELI-1. The online appendix entry, decision page and Institution review use this same stable decision ID.
Reference image sources
Matale District location in Sri Lanka. 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 of the published image only; no geographic features, points, labels or scenario overlays added.
https://commons.wikimedia.org/wiki/File:Sri_Lanka_districts_Matale.svg
https://creativecommons.org/licenses/by-sa/3.0/
Kandy District location in Sri Lanka. Reference map image — not live. Kandy District location in Sri Lanka. Map date: 2012-07-30. Uwe Dedering; uploaded by BishkekRocks. CC BY-SA 3.0. Detail crop of the published image only; no geographic features, points, labels or scenario overlays added.
https://commons.wikimedia.org/wiki/File:Sri_Lanka_districts_Kandy.svg
https://creativecommons.org/licenses/by-sa/3.0/
30 × 30 km historical map window around Knuckles; not a project boundary. Reference map image — not live. Copernicus land cover, 2015, 100 m. Contains modified Copernicus Service information (2020). Copernicus Global Land Service. Copernicus Global Land product licence. Previously prepared local crop and binary forest-class colouring. No new spatial processing in this correction.
https://cds.climate.copernicus.eu/licences/Copernicus-Global-Land-product-licence
30 × 30 km historical map window around Knuckles; not a project boundary. Reference map image — not live. Copernicus land cover, 2018, 100 m. Contains modified Copernicus Service information (2020). Copernicus Global Land Service. Copernicus Global Land product licence. Previously prepared local crop and binary forest-class colouring. No new spatial processing in this correction.
https://cds.climate.copernicus.eu/licences/Copernicus-Global-Land-product-licence
Additional source locators
DD-WATER — FAO56 root-zone water balance — Institution publication
Chapter8 equation85 and ETc = Kc ETo. Daily water balance components; local coefficients and operating assumptions still need review.
https://www.fao.org/4/X0490E/x0490e0e.htm
DD-PESTICIDES — Sri Lanka Registrar of Pesticides — Government publication
Current registration lists, restrictions and label guidance. Registration and label evidence; no treatment recommendation or automatic permission.
https://doa.gov.lk/rop-downloads/
DD-CEA — CEA ambient water regulations — Government publication
Gazette2148/20, Schedule of use-specific categories. Published ambient water categories and limits; do not substitute them for drinking-water, effluent, air or noise rules.
https://www.cea.lk/web/images/pdf/epc/2148-20_E-1.pdf
DD-BRIER — JMA numerical weather prediction outline — Government publication
AppendixA.3, equationsA.3.1 and A.3.3. Brier score and reference skill for binary probability forecasts; the prototype uses one specified event, not an undifferentiated seasonal score.
https://www.jma.go.jp/jma/jma-eng/jma-center/nwp/outline2022-nwp/pdf/outline2022_all.pdf
DD-NRW — JICA non-revenue water training materials — Institution publication
Training materials, section1.1, IWA water-balance table. NRW, unbilled authorized use, apparent and real losses are distinct components.
https://openjicareport.jica.go.jp/pdf/12364485_03.pdf
DD-ILO — ILO controlling occupational risks — Institution publication
Controlling risks; hierarchy of controls. Evidence-led control review; no universal numeric risk score or clearance.
DD-GBIF — 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.
https://docs.gbif.org/guide-publishing-survey-data/en/
DD-LOCAL — 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.
USDA-BULK-DENSITY — USDA NRCS: Soil Quality Indicators — Bulk Density — Government publication
Page 1, definition and Factors Affecting. Defines dry soil mass divided by total core volume, in g/cm³. Supports the measurement definition, not the fictional observations or a local compaction threshold.
https://www.nrcs.usda.gov/sites/default/files/2023-01/Soil%20Quality-Indicators-Bulk%20Density.pdf
FAO-MOISTURE-BASIS — FAO: Prevention of post-harvest food losses — Measurement — Intergovernmental publication
Section 1.1 Definitions, Moisture content, wet basis. Wet-basis moisture is water mass divided by the total mass of water and dry matter. Supports the stated percentage basis, not a commodity acceptance limit or the fictional observations.
https://www.fao.org/4/x0039e/x0039e01.htm
NIST-CELSIUS — NIST: SI Units — Temperature — Government publication
SI Units — Temperature, definition and exact temperature conversion. Zero kelvin is absolute zero and Celsius temperature equals kelvin temperature minus 273.15. Supports the physical lower bound, not shipment specifications or fictional observations.
https://www.nist.gov/pml/owm/si-units-temperature
Published ecosystem accounting context: United Nations DESA, System of Environmental-Economic Accounting Ecosystem Accounting, December 2024, publication entry and SEEA account definitions. Extent, condition, physical service flows and monetary accounts remain separate. The publication entry is available; direct PDF retrieval returned access denied during checking. Obtain the full current method before operational account compilation.
6 4 Payments for Ecosystem Services
PES means payments for ecosystem services. In this fictional example, upstream farmer groups maintain riverbank vegetation and soil cover. An illustrative downstream water-user fund pays under an annual agreement. The intermediary keeps the agreement and evidence together; an independent checker checks the work.
Follow the example: agree the work and conditions; check the field record; calculate a proposal; then record separate authorisation and actual payment evidence.
Annual work record | Example |
|---|---|
Agreed area | 24 ha |
Checked area | 22 ha = 20 ha meeting conditions + 2 ha needing correction |
Area still to visit | 2 ha; checked 22 ha + unvisited 2 ha = agreed 24 ha |
Annual payment proposal | min(20 ha × LKR 12,500 per ha/year, LKR 300,000) = LKR 250,000 |
Funding and payment | LKR 200,000 available; funding confirmation missing. No amount ready for authorisation. Authorised = 0; paid = 0. |
These hectares show work compliance only. They do not prove cleaner water, additional environmental benefits or a monetary value of the ecosystem. Annual rates and caps are fictional agreement settings.
Checking possible displacement of land clearing
DEC-DP39-008 compares two fixed 200 ha observation areas using the same clearing definition, season and observation window. New clearing near the agreement increases from 0.6 ha to 1.4 ha; clearing in a separate comparison area increases from 0.4 ha to 0.5 ha. The two increases are 0.8 ha and 0.1 ha. Their difference is 0.7 ha. Investigate this signal; it does not prove that the agreement caused clearing.
DEC-DP39-007 uses the same published difference-of-changes arithmetic for ground cover: (85 − 60) − (67 − 62) = 20 percentage points. Comparable sites, baseline conditions and a defensible study design must be assessed before making a causal or additionality claim.
The 20 PES questions
Decision | Question |
|---|---|
001 | Which field checks are due? |
002 | How much agreed work passed the check? |
003 | What was checked, proposed and paid? |
004 | How much does a field check cost? |
005 | Is the scheme ready to start? |
006 | Can this group join the scheme? |
007 | Did the scheme add an environmental improvement? |
008 | Did land clearing move outside the agreement area? |
009 | Could the agreed work be lost or damaged? |
010 | Which service agreement is practical? |
011 | What payment can we propose? |
012 | How would the payment be shared? |
013 | Is the same work being claimed twice? |
014 | How should we measure the work and its benefits? |
015 | Is there enough money for the full agreement? |
016 | Could participation harm a household or its rights? |
017 | Which complaints need a response? |
018 | Is the checker independent? |
019 | Should the agreement continue, change or close? |
020 | Do the service name, unit and agreement match? |
Data needed
Obtain the versioned scheme and service agreement from its owner, the mapped area and rights/consent records from authorised custodians, field observations and signed protocol from the checker, and the rate schedule, funding commitment, authorisation and transaction references from the responsible payer. Record the original source, year, units, definitions, quality and permitted use. No approved Knuckles PES agreement or tariff is supplied by these examples.
Source basis
FAO, Payments for environmental services: what role in sustainable agricultural development?, ESA Working Paper 11-20, December 2011, section 2, printed pages 3–6: conditional agreements, additionality, displacement risks, durability and monitoring. Published institutional guidance; not a payment formula or a local rate.
https://www.fao.org/docrep/015/an456e/an456e00.pdf
World Bank, Impact Evaluation in Practice, second edition, chapter 7, Table 7.2, printed page 140: difference in differences = (treated after − before) − (comparison after − before). Verified published formula for the arithmetic used in DEC-DP39-007 and DEC-DP39-008. The publication does not verify these fictional data, the comparison design or a causal conclusion.
https://documents1.worldbank.org/curated/en/698441474029568469/pdf/Impact-evaluation-in-practice.pdf
The other PES rules are project checks or illustrative agreement arithmetic. Their status is Validation required. Use Institution review for local scheme authority, service definition, rights, safeguards, rate, funding, checking design and payment responsibility.
Find a decision
Find the inputs, worked example, calculation and sources for each decision.
Download the decision register · Institution review
820 candidate decisions
| Decision | Question and inputs | Calculation, sources and scope |
|---|---|---|
| DEC-DP01-001DP01 | Land change Prioritize divisions with material land-use change Inputs and exampleRule Net = later - earlier; percentage = 100 x net / earlier (nonzero); annual = net / elapsed years; gross loss and gain from matched transitions; net = gain - loss Division and fixed analysis area; earlier/later years; native category/code and mapping; area and unit; dataset/boundary/class/method versions; missing and unclassified extent; source, coverage and local quality; optional matched from/to parcel evidence Result: Change (ha) Limits Complete compatible endpoints only; missing is not zero; reject conflicting source mappings; unresolved categories remain excluded; no invented balancing area, action threshold, confidence interval or causal conclusion. Sorting is a proposed review aid. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Land-use change matrix and net area Land-use change matrix and net area Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP01-002DP01 | Development screening Check development overlap with mapped constraints Inputs and examplePurpose Check reported development overlap before preparing a planning referral. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — development screening, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — development screening. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Supplied overlap and a matching constraint edition do not grant development permission. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Land-Use Planning Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-005DP01 | Agricultural suitability Check evidence for proposed land uses Inputs and examplePurpose Check the land, soil, slope, rainfall and crop evidence needed to compare proposed uses. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — agricultural suitability, the default output explains Obtain the missing evidence listed below. Changing Land polygon, Land polygon evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Land polygon remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Land polygon; Land polygon evidence reference; soil depth; soil depth evidence reference; slope degrees; slope degrees evidence reference; rainfall; rainfall evidence reference; water access; water access evidence reference; crop requirements; crop requirements evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — agricultural suitability. Land polygon = Missing; Land polygon evidence reference = ; soil depth = Documented; soil depth evidence reference = Sample Laggala Pallegama field register / 2025; slope degrees = Documented; slope degrees evidence reference = Sample Laggala Pallegama field register / 2025; rainfall = Documented; rainfall evidence reference = Sample Laggala Pallegama field register / 2025; water access = Documented; water access evidence reference = Sample Laggala Pallegama field register / 2025; crop requirements = Documented; crop requirements evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this agricultural suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Land polygon = Documented; Land polygon evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle agricultural suitability. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Land polygon. The required evidence is incomplete for this agricultural suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Land polygon: Missing. Map context. No map inserted into this decision example Limits Complete records alone do not establish agricultural suitability. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Use local land characteristics in suitability review Assess the potential of the land and water and the social and economic conditions for the specified use. Sector guidance · Guidelines for Land-Use Planning Confirm the relevant district plan, its vintage, and applicable site constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-006DP01 | Land conversion Check land-conversion applications before referral Inputs and examplePurpose Check the application, existing use, ownership and objections before a conversion referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — land conversion, the default output explains Obtain the missing evidence listed below. Changing Application ID, Application ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Application ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Application ID; Application ID evidence reference; current use; current use evidence reference; proposed use; proposed use evidence reference; ownership evidence; ownership evidence evidence reference; applicable rules; applicable rules evidence reference; objections; objections evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — land conversion. Application ID = Missing; Application ID evidence reference = ; current use = Documented; current use evidence reference = Sample Laggala Pallegama field register / 2025; proposed use = Documented; proposed use evidence reference = Sample Laggala Pallegama field register / 2025; ownership evidence = Documented; ownership evidence evidence reference = Sample Laggala Pallegama field register / 2025; applicable rules = Documented; applicable rules evidence reference = Sample Laggala Pallegama field register / 2025; objections = Documented; objections evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this land conversion case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Application ID = Documented; Application ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle land conversion. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Application ID. The required evidence is incomplete for this land conversion case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Application ID: Missing. Map context. No map inserted into this decision example Limits The responsible authority must determine whether conversion is permitted. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Written permission for non-agricultural paddy use When the applicable rule identifies paddy land and the proposed use is non-agricultural, check the Commissioner-General’s written permission before referral. Sector guidance · Guidelines for Land-Use Planning Confirm the parcel's legal status and current law with Agrarian Development. A document check does not authorize a conversion. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S01, S53, S63 Context alone does not validate the formula. |
| DEC-DP01-007DP01 | Settlement planning Compare potential settlement areas Inputs and examplePurpose Compare settlement options using service access, constraints, costs and stated trade-offs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Infill near existing services, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Infill near existing services. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Use existing nearby roads and services.; Resource needs and adverse effects = Check vacant-site capacity, tenure and pressure on existing services.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Candidate polygon; service capacity; access cost; hazard evidence; environmental constraints. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A budget surplus does not establish a suitable settlement location. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Guidelines for Land-Use Planning Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-009DP01 | Wetland protection Check activities reported over mapped wetlands Inputs and examplePurpose Check reported activity overlap with the cited wetland record. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — wetland protection, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — wetland protection. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits An overlap figure does not establish the wetland boundary or permission conditions. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Land-Use Planning Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-010DP01 | Riparian protection Check activities reported inside river reservations Inputs and examplePurpose Check an activity against the cited river-reservation survey and basis. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — riparian protection, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — riparian protection. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits No universal reservation width or legal breach is inferred. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Land-Use Planning Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-013DP01 | Urban expansion Review changes in agricultural land area Inputs and examplePurpose Compare agricultural class losses and gains within the same mapped extent. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion. Checks For Laggala Pallegama — urban expansion, the default output explains Check the matching source records before interpreting the change. Changing Later mapped class area, Matched area entering the class produces Check the matching source records before interpreting the change. Missing Earlier mapped class area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier mapped class area [ha]; Later mapped class area [ha]; Matched area leaving the class [ha]; Matched area entering the class [ha]; Same fixed analysis extent [ha]; Native class and mapping version; Earlier observation date; Later observation date Result: Net class-area change; Relative class-area change; Gross loss from class; Gross gain to class (ha; %; ha; ha) Worked example. Fictional 2025 example. Laggala Pallegama — urban expansion. Earlier mapped class area = 100 ha; Later mapped class area = 90 ha; Matched area leaving the class = 18 ha; Matched area entering the class = 8 ha; Same fixed analysis extent = 200 ha; Native class and mapping version = Agricultural land — demonstration class definition; Earlier observation date = 2024-06-30; Later observation date = 2025-06-30. Results: Net class-area change = -10 ha; Relative class-area change = -10 %; Gross loss from class = 18 ha; Gross gain to class = 8 ha. Interpretation: The recorded Agricultural land — demonstration class definition 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 check: Check the matching source records before interpreting the change. Changed input. Change Later mapped class area = 91; Matched area entering the class = 9. Result: Net class-area change = -9 ha; Relative class-area change = -9 %; Gross loss from class = 18 ha; Gross gain to class = 9 ha. Interpretation: The recorded Agricultural land — demonstration class definition area changes from 100 to 91 ha. Net change is -9 ha; supplied gross loss is 18 ha and gross gain is 9 ha. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier mapped class area. No usable result. Earlier mapped class area Next check: Correct or obtain the missing input records. Information still needed: Earlier mapped class area. Map context. No map inserted into this decision example Limits Aggregate class changes do not identify individual conversions or their causes. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Land-use change matrix and net area Land-use change matrix and net area Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP01-015DP01 | Restoration planning Compare restoration land-use alternatives Inputs and examplePurpose Compare restoration choices using site constraints, benefits, resources and costs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Assisted natural regeneration, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Assisted natural regeneration. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Allow existing native regeneration to recover.; Resource needs and adverse effects = Needs suitable seed sources, protection and time; recovery is uncertain.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Site condition; restoration options; tenure; costs LKR; benefits; constraints. Map context. No map inserted into this decision example Limits No option is preferred solely because it costs less. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Guidelines for Land-Use Planning Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-016DP01 | Land degradation Prepare a detailed soil-loss assessment Inputs and examplePurpose Use the supplied soil-loss factors to identify where a detailed assessment is needed. Output Comparison table Next step Prepare assessment brief creates an unassigned draft that is visible and downloadable, not sent. Rule R × K × LS × C × P, using a mutually consistent SI factor set. Checks For Laggala Pallegama — land degradation, the default output explains Check local factor and site evidence before selecting a detailed erosion assessment. Changing Rainfall erosivity produces Check local factor and site evidence before selecting a detailed erosion assessment. Missing Rainfall erosivity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall erosivity [MJ mm/(ha h year)]; Soil erodibility [t ha h/(ha MJ mm)]; Slope-length and steepness factor [ratio]; Cover-management factor [fraction]; Support-practice factor [fraction] Result: Estimated annual sheet/rill loss (t/ha/year) Worked example. Fictional 2025 example. Laggala Pallegama — land degradation. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Results: Estimated annual sheet/rill loss = 15.641 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.641 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Changed input. Change Rainfall erosivity = 951. Result: Estimated annual sheet/rill loss = 15.657 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.657 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Missing input. Omit Rainfall erosivity. No usable result. Rainfall erosivity Next check: Correct or obtain the missing input records. Information still needed: Rainfall erosivity. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The estimate covers sheet and rill erosion, not landslides or all sediment delivery. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Soil-loss factor product The Sri Lankan catchment study uses the same erosion-factor product. Estimated soil loss = R × K × LS × C × P. Sector guidance · A Guide for Predicting Sheet and Rill Erosion on Forest Land Use locally reviewed factor definitions, units and data for the actual catchment. The study’s factors and map do not transfer automatically. Implementation: prototype |
| DEC-DP01-017DP01 | Plan implementation Investigate differences between planned and actual use Inputs and examplePurpose Compare planned and observed hectares of the same land-use class. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — plan implementation, the default output explains Check the class, period and implementation evidence. Changing Hectares planned for the selected land-use class produces Check the class, period and implementation evidence. Missing Hectares planned for the selected land-use class remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Hectares planned for the selected land-use class [ha]; Hectares observed in that same class [ha] Result: Difference; Relative change (ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — plan implementation. Hectares planned for the selected land-use class = 100 ha; Hectares observed in that same class = 90 ha. Results: Difference = -10 ha; Relative change = -10 %. Interpretation: Difference: -10 ha. Check the class, period and implementation evidence. Next check: Check the class, period and implementation evidence. Changed input. Change Hectares planned for the selected land-use class = 101. Result: Difference = -11 ha; Relative change = -10.891 %. Interpretation: Difference: -11 ha. Check the class, period and implementation evidence. Next check: Check the class, period and implementation evidence. Missing input. Omit Hectares planned for the selected land-use class. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A difference needs source and implementation checks before assigning a cause. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-019DP01 | Map documentation Find missing land-use map details Inputs and examplePurpose Find missing source, scale, coordinate and classification details in a land-use layer. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — map documentation, the default output explains Obtain the missing evidence listed below. Changing Layer ID, Layer ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Layer ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Layer ID; Layer ID evidence reference; scale; scale evidence reference; coordinate system; coordinate system evidence reference; classification edition; classification edition evidence reference; owner; owner evidence reference; survey date; survey date evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — map documentation. Layer ID = Missing; Layer ID evidence reference = ; scale = Documented; scale evidence reference = Sample Laggala Pallegama field register / 2025; coordinate system = Documented; coordinate system evidence reference = Sample Laggala Pallegama field register / 2025; classification edition = Documented; classification edition evidence reference = Sample Laggala Pallegama field register / 2025; owner = Documented; owner evidence reference = Sample Laggala Pallegama field register / 2025; survey date = Documented; survey date evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this map documentation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Layer ID = Documented; Layer ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle map documentation. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Layer ID. The required evidence is incomplete for this map documentation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Layer ID: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Complete metadata do not certify map accuracy. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Data Catalog Vocabulary Version 3 Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP01-020DP01 | Survey scheduling Check land-use survey schedules Inputs and examplePurpose Check survey tasks against staff windows, effort and predecessors. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — survey scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — survey scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A feasible example schedule does not assign work or authorise a survey. Land-use planner and spatial data custodian | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-001DP02 | Erosion Compare estimated sheet and rill soil loss Inputs and examplePurpose Compare supplied sheet-and-rill loss estimates to plan detailed erosion assessments. Output Comparison table Next step Prepare assessment brief creates an unassigned draft that is visible and downloadable, not sent. Rule R × K × LS × C × P, using a mutually consistent SI factor set. Checks For Laggala Pallegama — erosion, the default output explains Check local factor and site evidence before selecting a detailed erosion assessment. Changing Rainfall erosivity produces Check local factor and site evidence before selecting a detailed erosion assessment. Missing Rainfall erosivity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall erosivity [MJ mm/(ha h year)]; Soil erodibility [t ha h/(ha MJ mm)]; Slope-length and steepness factor [ratio]; Cover-management factor [fraction]; Support-practice factor [fraction] Result: Estimated annual sheet/rill loss (t/ha/year) Worked example. Fictional 2025 example. Laggala Pallegama — erosion. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Results: Estimated annual sheet/rill loss = 15.641 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.641 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Changed input. Change Rainfall erosivity = 951. Result: Estimated annual sheet/rill loss = 15.657 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.657 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Missing input. Omit Rainfall erosivity. No usable result. Rainfall erosivity Next check: Correct or obtain the missing input records. Information still needed: Rainfall erosivity. Map context. No map inserted into this decision example Limits Local factor accuracy and site evidence are needed before choosing works. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Soil-loss factor product The Sri Lankan catchment study uses the same erosion-factor product. Estimated soil loss = R × K × LS × C × P. Sector guidance · A Guide for Predicting Sheet and Rill Erosion on Forest Land Use locally reviewed factor definitions, units and data for the actual catchment. The study’s factors and map do not transfer automatically. Implementation: prototype |
| DEC-DP02-002DP02 | Conservation treatments Compare contouring mulching and cover-crop alternatives Inputs and examplePurpose Compare contour strips, mulching and cover crops using site constraints and trade-offs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Contour grass strips, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Contour grass strips. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Maintain a vegetated strip across the slope.; Resource needs and adverse effects = Uses crop space and needs correct alignment and maintenance.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Treatment options; erosion-model inputs; implementation cost; maintenance; site constraints. Map context. No map inserted into this decision example Limits Cost and descriptive benefits alone do not establish runoff reduction. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Water Erosion RUSLE2 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-004DP02 | Soil carbon Check soil-carbon records before choosing monitoring sites Inputs and examplePurpose Compare soil-carbon records with matching depth, density and sampling conventions. Output Comparison table Next step Prepare carbon comparison creates an unassigned draft that is visible and downloadable, not sent. Rule (Organic carbon% /100) × bulk density × depth ×10000 × (1−coarse% /100). Confirm that the density and coarse-fragment conventions are mutually consistent. Checks For Laggala Pallegama — soil carbon, the default output explains Check sampling comparability before using the stock comparison. Changing Soil organic carbon produces Check sampling comparability before using the stock comparison. Missing Soil organic carbon remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Soil organic carbon [%]; Fine-earth bulk-density basis [t/m³]; Sample depth [m]; Coarse-fragment volume fraction [%]; Sampling depth, design and density convention Result: Soil-carbon stock (t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — soil carbon. Soil organic carbon = 1.8 %; Fine-earth bulk-density basis = 1.25 t/m³; Sample depth = 0.3 m; Coarse-fragment volume fraction = 12 %; Sampling depth, design and density convention = Sample matched depth and fine-earth convention. Results: Soil-carbon stock = 59.4 t C/ha. Interpretation: 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 check: Check sampling comparability before using the stock comparison. Changed input. Change Soil organic carbon = 1.818. Result: Soil-carbon stock = 59.994 t C/ha. Interpretation: The supplied 1.818% carbon, 1.25 g/cm³ bulk density, 0.3 m depth and 12% coarse fragments give 59.994 t C/ha under the stated fine-earth convention. Next check: Check sampling comparability before using the stock comparison. Missing input. Omit Soil organic carbon. No usable result. Soil organic carbon Next check: Correct or obtain the missing input records. Information still needed: Soil organic carbon. Map context. No map inserted into this decision example Limits Stock differences do not establish a management effect without comparable samples. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Soil-carbon stock with volume correction Soil-carbon stock with volume correction Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP02-005DP02 | Soil fertility Refer nutrient and acidity limitations for agronomic advice Inputs and examplePurpose Compare the reported soil test with its stated parameter, method and example bounds. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — soil fertility, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [pH]; Example lower comparison bound [pH]; Example upper comparison bound [pH]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (pH) Worked example. Fictional 2025 example. Laggala Pallegama — soil fertility. Parameter and applicable use = Soil pH; Measured result = 6.2 pH; Example lower comparison bound = 5.5 pH; Example upper comparison bound = 7.5 pH; Original and limit unit = pH; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 6.2 pH. Interpretation: The supplied Soil pH result is 6.2 pH. Its stated comparison range is 5.5 to 7.5 pH. Within example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 6.262; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 6.262 pH. Interpretation: The supplied Soil pH result is 6.262 pH. Its stated comparison range is 5.5 to 7.5 pH. Within example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits The page does not prescribe fertiliser or lime. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Use the applicable soil-test interpretation Use the soil test and the table for the stated parameter to support crop-specific nutrient advice. Confirm sampling, analytical method, crop, units and recommendation basis with an agronomist. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-008DP02 | Infiltration Compare practices to improve infiltration and runoff control Inputs and examplePurpose Compare infiltration and runoff practices using measured outcomes and site constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Mulch with soil-cover management, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Mulch with soil-cover management. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Maintain surface cover between crop rows.; Resource needs and adverse effects = Requires mulch, labour and evidence that water and pest effects are acceptable.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Infiltration tests; rainfall intensity; slope; treatment costs; runoff observations. Map context. No map inserted into this decision example Limits A proposed practice needs local evidence before its benefit is assumed. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Water Erosion RUSLE2 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-010DP02 | On-farm irrigation Compare crop output per unit of water Inputs and examplePurpose Compare crop output per delivered water volume for matching seasons. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Saleable crop output / Matching irrigation water input, for the same product, process and period. Checks For Laggala Pallegama — on-farm irrigation, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable crop output produces Check matching outputs, denominators and operating conditions. Missing Saleable crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable crop output [kg]; Matching irrigation water input [m³] Result: Crop water productivity (kg/m³) Worked example. Fictional 2025 example. Laggala Pallegama — on-farm irrigation. Saleable crop output = 19,780 kg; Matching irrigation water input = 7,200 m³. Results: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable crop output = 19,781. Result: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,781 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable crop output. No usable result. Saleable crop output Next check: Correct or obtain the missing input records. Information still needed: Saleable crop output. Map context. No map inserted into this decision example Limits Low productivity alone does not identify which improvement will work. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Output per irrigation water supplied Water productivity = crop output ÷ volume of irrigation water applied for the matching scope. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-011DP02 | Watershed treatments Prioritize connected watershed conservation interventions Inputs and examplePurpose Compare connected watershed interventions and their resource requirements. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Upper-slope soil cover, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Upper-slope soil cover. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Maintain protective cover on upper slopes.; Resource needs and adverse effects = Needs landholder participation, establishment and maintenance resources.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Catchment units; erosion risk; upstream treatments; downstream assets; costs. Map context. No map inserted into this decision example Limits A descriptive benefit does not establish a downstream causal effect. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Water Erosion RUSLE2 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-013DP02 | Agroclimate advice Prepare rainfall evidence for agricultural advice Inputs and examplePurpose Prepare rainfall observations and departures for an agricultural adviser. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — agroclimate advice, the default output explains Prepare the rainfall evidence for an agronomist; no crop advice is generated. Changing Comparable seasonal rainfall reference produces Prepare the rainfall evidence for an agronomist; no crop advice is generated. Missing Comparable seasonal rainfall reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable seasonal rainfall reference [mm]; Observed seasonal rainfall [mm] Result: Difference; Relative change (mm; %) Worked example. Fictional 2025 example. Laggala Pallegama — agroclimate advice. Comparable seasonal rainfall reference = 120 mm; Observed seasonal rainfall = 84 mm. Results: Difference = -36 mm; Relative change = -30 %. Interpretation: Difference: -36 mm. Prepare the rainfall evidence for an agronomist; no crop advice is generated. Next check: Prepare the rainfall evidence for an agronomist; no crop advice is generated. Changed input. Change Comparable seasonal rainfall reference = 121. Result: Difference = -37 mm; Relative change = -30.579 %. Interpretation: Difference: -37 mm. Prepare the rainfall evidence for an agronomist; no crop advice is generated. Next check: Prepare the rainfall evidence for an agronomist; no crop advice is generated. Missing input. Omit Comparable seasonal rainfall reference. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A rainfall difference alone does not generate crop advice. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending Published Sri Lankan step. Compare monthly rainfall with the published normal for the same station or area and calendar month. 72 mm against a 120 mm normal is 60% of normal, equivalent to a 40% shortfall from normal. Department of Meteorology, Sri Lanka · December 2024 Drought Bulletin. Figure 2, monthly rainfall as a percentage of the matching normal. Confirm the station, month and reference years before using the comparison in agricultural advice. Calculation reference. International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Agrometeorological bulletin, 5 November 2026 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-015DP02 | Crop suitability Review limiting soil and climate factors for proposed crops Inputs and examplePurpose Check soil and climate evidence against a proposed crop's requirements. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — crop suitability, the default output explains Obtain the missing evidence listed below. Changing Soil depth, Soil depth evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Soil depth remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Soil depth; Soil depth evidence reference; texture; texture evidence reference; slope; slope evidence reference; rainfall; rainfall evidence reference; temperature; temperature evidence reference; crop requirements; crop requirements evidence reference; irrigation; irrigation evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — crop suitability. Soil depth = Missing; Soil depth evidence reference = ; texture = Documented; texture evidence reference = Sample Laggala Pallegama field register / 2025; slope = Documented; slope evidence reference = Sample Laggala Pallegama field register / 2025; rainfall = Documented; rainfall evidence reference = Sample Laggala Pallegama field register / 2025; temperature = Documented; temperature evidence reference = Sample Laggala Pallegama field register / 2025; crop requirements = Documented; crop requirements evidence reference = Sample Laggala Pallegama field register / 2025; irrigation = Documented; irrigation evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this crop suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Soil depth = Documented; Soil depth evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle crop suitability. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Soil depth. The required evidence is incomplete for this crop suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Soil depth: Missing. Map context. No map inserted into this decision example Limits No crop-suitability score is invented. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Match crop requirements with site limitations Compare the requirements of the stated crop or land use with relevant land qualities and identify limiting conditions. Confirm local crop requirements, agroecological zone, soil observations and decision thresholds. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP02-016DP02 | Demonstration trials Evaluate conservation practice outcomes Inputs and examplePurpose Compare runoff changes in treated and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — demonstration trials, the default output explains Obtain the missing evidence listed below. Changing Treatment Measured runoff before produces Obtain the missing evidence listed below. Missing Treatment Measured runoff before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Measured runoff before [mm/season]; Treatment Measured runoff after [mm/season]; Comparison Measured runoff before [mm/season]; Comparison Measured runoff after [mm/season]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (mm/season) Worked example. Fictional 2025 example. Laggala Pallegama — demonstration trials. Treatment Measured runoff before = 42 mm/season; Treatment Measured runoff after = 59 mm/season; Comparison Measured runoff before = 39 mm/season; Comparison Measured runoff after = 46 mm/season; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Measured runoff /example matching definition1. Results: Difference in changes = 10 mm/season. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 mm/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Measured runoff before = 42.42. Result: Difference in changes = 9.58 mm/season. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 mm/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Measured runoff before. No usable result. Treatment Measured runoff before Next check: Correct or obtain the missing input records. Information still needed: Treatment Measured runoff before; Study design and evidence that the treatment and comparison records are comparable. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Difference in changes alone does not establish a conservation effect. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP02-020DP02 | Model assurance Check whether a soil or land result can be reproduced Inputs and examplePurpose Check whether the same soil-loss method and inputs reproduce the stated result. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — model assurance, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [t/ha/year]; Independently reproduced value [t/ha/year]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [t/ha/year]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (t/ha/year; %) Worked example. Fictional 2025 example. Laggala Pallegama — model assurance. Earlier/source value = 100 t/ha/year; Independently reproduced value = 90 t/ha/year; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable t/ha/year measure; same input scope; Documented absolute comparison tolerance = 0.01 t/ha/year; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 t/ha/year; Relative change = -10 %. Interpretation: Difference: -10 t/ha/year. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 t/ha/year; Relative change = -10.891 %. Interpretation: Difference: -11 t/ha/year. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits A difference requires investigation; it does not by itself identify the faulty source. Soil scientist and land-resource specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-002DP03 | Production costs Target crop production costs requiring intervention Inputs and examplePurpose Compare matching production costs per hectare and inspect their components. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Checks For Laggala Pallegama — production costs, the default output explains Review cost components and comparable verified outputs. Changing Labour cost produces Review cost components and comparable verified outputs. Missing Labour cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Verified matching hectares [ha] Result: Cost per matching unit; Total cost (LKR/ha; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — production costs. Labour cost = 180,000 LKR; Material/input cost = 255,000 LKR; Other non-overlapping cost = 62,000 LKR; Verified matching hectares = 5.4 ha. Results: Cost per matching unit = 92,037.037 LKR/ha; Total cost = 497,000 LKR. Interpretation: The supplied costs total 497,000 LKR for 5.4 ha. Cost per matching unit is 92,037.037 LKR/ha. Next check: Review cost components and comparable verified outputs. Changed input. Change Labour cost = 180,001. Result: Cost per matching unit = 92,037.222 LKR/ha; Total cost = 497,001 LKR. Interpretation: The supplied costs total 497,001 LKR for 5.4 ha. Cost per matching unit is 92,037.222 LKR/ha. Next check: Review cost components and comparable verified outputs. Missing input. Omit Labour cost. No usable result. Labour cost Next check: Correct or obtain the missing input records. Information still needed: Labour cost. Map context. No map inserted into this decision example Limits High cost alone does not identify an effective intervention. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Paddy cash cost per unit of area The survey reports paddy cash production cost per acre. Normalize included cash production costs by the corresponding paddy area. Sector guidance · Socio Economics and Planning Centre downloads Compare the same crop, season and cost components and convert the area consistently. The cited survey covers cash payments. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-003DP03 | Irrigation advice Prepare a crop-water-needs scenario Inputs and examplePurpose Prepare a crop-stage water-needs scenario from the stated weather and crop factors. Output Comparison table Next step Prepare water-needs scenario creates an unassigned draft that is visible and downloadable, not sent. Rule ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency. Checks For Laggala Pallegama — irrigation advice, the default output explains Review weather, crop, water-availability and operating evidence. Changing Irrigated crop area produces Review weather, crop, water-availability and operating evidence. Missing Irrigated crop area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction] Result: Gross daily irrigation requirement; Net field requirement (m³/day; mm/day) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation advice. Irrigated crop area = 85 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction. Results: Gross daily irrigation requirement = 6,687.5 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,687.5 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Changed input. Change Irrigated crop area = 85.85. Result: Gross daily irrigation requirement = 6,754.375 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,754.375 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Missing input. Omit Irrigated crop area. No usable result. Irrigated crop area Next check: Correct or obtain the missing input records. Information still needed: Irrigated crop area. Map context. No map inserted into this decision example Limits Calculated need is not an authorised irrigation release. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Crop evapotranspiration ETc = crop coefficient Kc × reference evapotranspiration ETo. Use mm/day for both ET values. Sector guidance · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration The match covers the ETc term. Confirm local crop coefficients, rainfall, field losses, efficiency and allocation authority. Implementation: prototype |
| DEC-DP03-004DP03 | Planting guidance Compare planned and observed sowing dates Inputs and examplePurpose Compare planned and observed sowing dates to identify records needing follow-up. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — planting guidance, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — planting guidance. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits Date differences alone do not establish a revised sowing recommendation. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare planting dates with the applicable calendar Use the calendar for the crop, season and locality to check the proposed planting window. Confirm the relevant agroecological area, crop, season and current rainfall or water availability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-006DP03 | Yield gaps Compare crop yield records Inputs and examplePurpose Compare matching harvested output and harvested area across crop records. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Harvested crop output / Matching harvested crop area, for the same product, process and period. Checks For Laggala Pallegama — yield gaps, the default output explains Check matching outputs, denominators and operating conditions. Changing Harvested crop output produces Check matching outputs, denominators and operating conditions. Missing Harvested crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Harvested crop output [kg]; Matching harvested crop area [ha] Result: Crop yield (kg/ha) Worked example. Fictional 2025 example. Laggala Pallegama — yield gaps. Harvested crop output = 19,780 kg; Matching harvested crop area = 5.4 ha. Results: Crop yield = 3,662.963 kg/ha. Interpretation: Harvested crop output: 19,780 kg; Matching harvested crop area: 5.4 ha. This gives 3,662.963 kg/ha. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Harvested crop output = 19,781. Result: Crop yield = 3,663.148 kg/ha. Interpretation: Harvested crop output: 19,781 kg; Matching harvested crop area: 5.4 ha. This gives 3,663.148 kg/ha. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Harvested crop output. No usable result. Harvested crop output Next check: Correct or obtain the missing input records. Information still needed: Harvested crop output. Map context. No map inserted into this decision example Limits Yield differences do not establish their causes or justify a treatment. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Area and yield production identity For paddy, estimated production = net harvested area × average yield. Yield = production ÷ matching net harvested area when derived from compatible totals. Sector guidance · FAO Statistical Yearbook 2014, Asia and the Pacific Use the same season and geography, compatible net area and the published crop-cutting method. This source does not establish the prototype's sample weights or non-paddy coverage. Implementation: prototype |
| DEC-DP03-007DP03 | Pest surveillance Check unusual pest observations Inputs and examplePurpose Identify unusual matched pest counts for a field investigation. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — pest surveillance, the default output explains Refer the matched field counts for pest investigation. Changing Comparable pest count per inspected plant produces Refer the matched field counts for pest investigation. Missing Comparable pest count per inspected plant remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable pest count per inspected plant [pests per inspected plant]; Observed pest count per inspected plant [pests per inspected plant] Result: Difference; Relative change (pests per inspected plant; %) Worked example. Fictional 2025 example. Laggala Pallegama — pest surveillance. Comparable pest count per inspected plant = 2 pests per inspected plant; Observed pest count per inspected plant = 3.2 pests per inspected plant. Results: Difference = 1.2 pests per inspected plant; Relative change = 60 %. Interpretation: Difference: 1.2 pests per inspected plant. Refer the matched field counts for pest investigation. Next check: Refer the matched field counts for pest investigation. Changed input. Change Comparable pest count per inspected plant = 2.02. Result: Difference = 1.18 pests per inspected plant; Relative change = 58.416 %. Interpretation: Difference: 1.18 pests per inspected plant. Refer the matched field counts for pest investigation. Next check: Refer the matched field counts for pest investigation. Missing input. Omit Comparable pest count per inspected plant. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits An increased count is not a pest diagnosis or control instruction. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-009DP03 | Seed certification Prioritize seed lots awaiting required tests Inputs and examplePurpose Identify seed lots whose required testing evidence is missing. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — seed certification, the default output explains Obtain the missing evidence listed below. Changing Lot ID, Lot ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Lot ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Lot ID; Lot ID evidence reference; germination test; germination test evidence reference; purity test; purity test evidence reference; health test; health test evidence reference; current certification criteria; current certification criteria evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — seed certification. Lot ID = Missing; Lot ID evidence reference = ; germination test = Documented; germination test evidence reference = Sample Laggala Pallegama field register / 2025; purity test = Documented; purity test evidence reference = Sample Laggala Pallegama field register / 2025; health test = Documented; health test evidence reference = Sample Laggala Pallegama field register / 2025; current certification criteria = Documented; current certification criteria evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this seed certification case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Lot ID = Documented; Lot ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle seed certification. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Lot ID. The required evidence is incomplete for this seed certification case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Lot ID: Missing. Map context. No map inserted into this decision example Limits A complete record does not grant certification. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Seed-lot laboratory evidence Check the required seed-lot test results against the applicable certification standard. Include germination, viability, purity and moisture as relevant. Sector guidance · Quality Declared Planting Material Confirm crop-specific standards, required tests and lot records with the Seed Certification Service. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-010DP03 | Seed supply Plan seed procurement against seasonal demand Inputs and examplePurpose Compare usable, uncommitted seed stock with seasonal demand. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — seed supply, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg seed]; Quarantined stock [kg seed]; Expired stock [kg seed]; Committed usable stock [kg seed]; Additional demand [kg seed]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg seed; kg seed) Worked example. Fictional 2025 example. Laggala Pallegama — seed supply. Physical stock = 1,200 kg seed; Quarantined stock = 100 kg seed; Expired stock = 50 kg seed; Committed usable stock = 740 kg seed; Additional demand = 500 kg seed; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg seed; Additional demand gap = 190 kg seed. Interpretation: Uncommitted usable stock: 310 kg seed. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg seed; Additional demand gap = 189 kg seed. Interpretation: Uncommitted usable stock: 311 kg seed. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Quarantined, expired and committed stock cannot fill the displayed gap. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-011DP03 | Fertilizer advice Review soil nutrient-test results Inputs and examplePurpose Check nutrient-test results using the matching analytical method and units. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — fertilizer advice, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [mg/kg]; Example lower comparison bound [mg/kg]; Example upper comparison bound [mg/kg]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (mg/kg) Worked example. Fictional 2025 example. Laggala Pallegama — fertilizer advice. Parameter and applicable use = Available phosphorus by stated method; Measured result = 12 mg/kg; Example lower comparison bound = 15 mg/kg; Example upper comparison bound = 30 mg/kg; Original and limit unit = mg/kg; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 12 mg/kg. Interpretation: The supplied Available phosphorus by stated method result is 12 mg/kg. Its stated comparison range is 15 to 30 mg/kg. Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 12.12; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 12.12 mg/kg. Interpretation: The supplied Available phosphorus by stated method result is 12.12 mg/kg. Its stated comparison range is 15 to 30 mg/kg. Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The comparison does not calculate a fertiliser dose. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Use the applicable soil-test interpretation Use the soil test and the table for the stated parameter to support crop-specific nutrient advice. Confirm sampling, analytical method, crop, units and recommendation basis with an agronomist. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-012DP03 | Pesticide stewardship Review proposed pesticide use against current conditions Inputs and examplePurpose Check registration, crop, pest and label evidence for proposed pesticide use. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — pesticide stewardship, the default output explains Obtain the missing evidence listed below. Changing Product registration, Product registration evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Product registration remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Product registration; Product registration evidence reference; crop; crop evidence reference; pest; pest evidence reference; label version; label version evidence reference; application record; application record evidence reference; restrictions; restrictions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — pesticide stewardship. Product registration = Missing; Product registration evidence reference = ; crop = Documented; crop evidence reference = Sample Laggala Pallegama field register / 2025; pest = Documented; pest evidence reference = Sample Laggala Pallegama field register / 2025; label version = Documented; label version evidence reference = Sample Laggala Pallegama field register / 2025; application record = Documented; application record evidence reference = Sample Laggala Pallegama field register / 2025; restrictions = Documented; restrictions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this pesticide stewardship case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Product registration = Documented; Product registration evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle pesticide stewardship. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Product registration. The required evidence is incomplete for this pesticide stewardship case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Product registration: Missing. Map context. No map inserted into this decision example Limits The page does not authorise a product or application. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Registered-use evidence check Check the proposed use against the current registered product and approved label before referral. Sector guidance · Pesticide registration, restrictions and guidance Confirm the crop, intended use, label conditions and current registration with the Registrar. The example gives no treatment instruction. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, DD-PESTICIDES, S03, S11, S50 Context alone does not validate the formula. |
| DEC-DP03-014DP03 | Post-harvest loss Select crop stages needing loss-reduction measures Inputs and examplePurpose Reconcile crop inputs, saleable output, by-products and stock to locate unexplained loss. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — post-harvest loss, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — post-harvest loss. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unexplained balance is not automatically measured physical loss. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-015DP03 | Mechanization Compare machinery service options for crop operations Inputs and examplePurpose Compare machinery hire, shared booking and contractor options. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Hire a local tractor service, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Hire a local tractor service. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Obtain machinery for a defined operation without purchasing it.; Resource needs and adverse effects = Booking, transport, field access and machine availability must match the crop window.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Operation hours; cultivated hectares; hire cost; labour availability; access constraints. Map context. No map inserted into this decision example Limits Affordability does not establish capacity, timing or field suitability. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP03-017DP03 | Farm income Identify crop enterprises with weak gross margins Inputs and examplePurpose Compare revenue and variable costs to examine weak gross margins. Output Comparison table Next step Prepare margin comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Gross margin = saleable output × realized price − variable costs. Divide by matching hectares for margin/ha; variable-cost break-even price = variable costs / output. Checks For Laggala Pallegama — farm income, the default output explains Review the prices, quantities and costs behind the margin. Changing Saleable output produces Review the prices, quantities and costs behind the margin. Missing Saleable output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable output [kg]; Realized price [LKR/kg]; Variable costs [LKR]; Matching crop area [ha]; Crop and saleable-output basis Result: Enterprise gross margin; Gross margin per hectare; Variable-cost break-even price (LKR; LKR/ha; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — farm income. Saleable output = 4,500 kg; Realized price = 110 LKR/kg; Variable costs = 360,000 LKR; Matching crop area = 1 ha; Crop and saleable-output basis = Paddy rough rice / fictional one-hectare crop enterprise / same season. Results: Enterprise gross margin = 135,000 LKR; Gross margin per hectare = 135,000 LKR/ha; Variable-cost break-even price = 80 LKR/kg. Interpretation: The supplied 4,500 kg at 110 LKR/kg gives 495,000 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,000 LKR. Next check: Review the prices, quantities and costs behind the margin. Changed input. Change Saleable output = 4,501. Result: Enterprise gross margin = 135,110 LKR; Gross margin per hectare = 135,110 LKR/ha; Variable-cost break-even price = 79.982 LKR/kg. Interpretation: The supplied 4,501 kg at 110 LKR/kg gives 495,110 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,110 LKR. Next check: Review the prices, quantities and costs behind the margin. Missing input. Omit Saleable output. No usable result. Saleable output Next check: Correct or obtain the missing input records. Information still needed: Saleable output. Map context. No map inserted into this decision example Limits Gross margin excludes fixed costs and is not net profit. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Gross margin per hectare Gross margin per hectare = gross benefit per hectare − variable costs per hectare. Sector guidance · Farm Management for Asia A Systems Approach The report demonstrates the paddy calculation. Confirm crop budgets, price, variable-cost boundaries and any local decision threshold. The report does not establish a break-even threshold. Implementation: prototype |
| DEC-DP03-018DP03 | Weather losses Compare yield changes around a weather event Inputs and examplePurpose Compare yield changes around a documented weather event. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — weather losses, the default output explains Obtain the missing evidence listed below. Changing Treatment Crop productivity before produces Obtain the missing evidence listed below. Missing Treatment Crop productivity before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Crop productivity before [kg/ha]; Treatment Crop productivity after [kg/ha]; Comparison Crop productivity before [kg/ha]; Comparison Crop productivity after [kg/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (kg/ha) Worked example. Fictional 2025 example. Laggala Pallegama — weather losses. Treatment Crop productivity before = 42 kg/ha; Treatment Crop productivity after = 59 kg/ha; Comparison Crop productivity before = 39 kg/ha; Comparison Crop productivity after = 46 kg/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Crop productivity /example matching definition1. Results: Difference in changes = 10 kg/ha. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 kg/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Crop productivity before = 42.42. Result: Difference in changes = 9.58 kg/ha. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 kg/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Crop productivity before. No usable result. Treatment Crop productivity before Next check: Correct or obtain the missing input records. Information still needed: Treatment Crop productivity before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A simple before-and-after comparison does not attribute yield loss to weather. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP03-020DP03 | Research trials Check a crop technology result before further validation Inputs and examplePurpose Check whether a crop technology's reported result can be reproduced. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — research trials, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [kg/ha]; Independently reproduced value [kg/ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [kg/ha]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (kg/ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — research trials. Earlier/source value = 100 kg/ha; Independently reproduced value = 90 kg/ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable kg/ha measure; same input scope; Documented absolute comparison tolerance = 0.01 kg/ha; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 kg/ha; Relative change = -10 %. Interpretation: Difference: -10 kg/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 kg/ha; Relative change = -10.891 %. Interpretation: Difference: -11 kg/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Reproduction alone does not establish local effectiveness or acceptance. Crop specialist, extension officer and agricultural statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-003DP04 | Minor irrigation Prioritize service areas with unmet crop water needs Inputs and examplePurpose Compare matching crop-water requirement and supply records. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — minor irrigation, the default output explains Review the delivery shortfall and allocation constraints. Changing Recorded crop-water requirement for this period produces Review the delivery shortfall and allocation constraints. Missing Recorded crop-water requirement for this period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded crop-water requirement for this period [m³]; Recorded water supplied in the same period [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — minor irrigation. Recorded crop-water requirement for this period = 85,000 m³; Recorded water supplied in the same period = 64,000 m³. Results: Difference = -21,000 m³; Relative change = -24.706 %. Interpretation: Difference: -21,000 m³. Review the delivery shortfall and allocation constraints. Next check: Review the delivery shortfall and allocation constraints. Changed input. Change Recorded crop-water requirement for this period = 85,001. Result: Difference = -21,001 m³; Relative change = -24.707 %. Interpretation: Difference: -21,001 m³. Review the delivery shortfall and allocation constraints. Next check: Review the delivery shortfall and allocation constraints. Missing input. Omit Recorded crop-water requirement for this period. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A shortfall alone does not establish an authorised allocation. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-004DP04 | Agrarian services Follow up delayed farmer-service requests Inputs and examplePurpose Identify open farmer-service cases that have passed their due date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — agrarian services, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — agrarian services. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Days overdue describe delay, not case severity. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-007DP04 | Land conversion Screen paddy conversion requests for formal determination Inputs and examplePurpose Check a paddy-conversion application before referring it for formal determination. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — land conversion, the default output explains Obtain the missing evidence listed below. Changing Parcel status, Parcel status evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Parcel status remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parcel status; Parcel status evidence reference; proposed use; proposed use evidence reference; application evidence; application evidence evidence reference; current rules; current rules evidence reference; inspection findings; inspection findings evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — land conversion. Parcel status = Missing; Parcel status evidence reference = ; proposed use = Documented; proposed use evidence reference = Sample Laggala Pallegama field register / 2025; application evidence = Documented; application evidence evidence reference = Sample Laggala Pallegama field register / 2025; current rules = Documented; current rules evidence reference = Sample Laggala Pallegama field register / 2025; inspection findings = Documented; inspection findings evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this land conversion case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Parcel status = Documented; Parcel status evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle land conversion. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Parcel status. The required evidence is incomplete for this land conversion case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Parcel status: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Application completeness is not conversion permission. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Written permission for non-agricultural paddy use When the applicable rule identifies paddy land and the proposed use is non-agricultural, check the Commissioner-General’s written permission before referral. Sector guidance · Department of Agrarian Development Services Confirm the parcel's legal status and current law with Agrarian Development. A document check does not authorize a conversion. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S04, S55 Context alone does not validate the formula. |
| DEC-DP04-008DP04 | Tank rehabilitation Compare minor-tank rehabilitation alternatives Inputs and examplePurpose Compare minor-tank repair choices using engineering evidence and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Repair the sluice and leaks, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Repair the sluice and leaks. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Address the recorded sluice or leakage problem.; Resource needs and adverse effects = Needs an engineering inspection, operating window and competent construction.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Tank condition; command hectares; sediment survey; repair cost; demand; safeguards. Map context. No map inserted into this decision example Limits Cost alone does not establish the safest or most effective repair. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Irrigation Management Circular 01/2008 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-010DP04 | Organization finance Follow up unreconciled farmer-organization funds Inputs and examplePurpose Reconcile receipts, payments and the recorded closing fund balance. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume. Checks For Laggala Pallegama — organization finance, the default output explains Reconcile closing balance. Changing Opening cash/receivable balance produces Reconcile closing balance. Missing Opening cash/receivable balance remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening cash/receivable balance [LKR]; Receipts and documented additions [LKR]; Payments and documented reductions [LKR]; Other documented non-overlapping adjustments [LKR]; Independently recorded closing balance [LKR] Result: Calculated closing balance; Recorded minus calculated closing (LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — organization finance. Opening cash/receivable balance = 160,000 LKR; Receipts and documented additions = 48,000 LKR; Payments and documented reductions = 35,000 LKR; Other documented non-overlapping adjustments = 9,000 LKR; Independently recorded closing balance = 163,500 LKR. Results: Calculated closing balance = 164,000 LKR; Recorded minus calculated closing = -500 LKR. Interpretation: Calculated closing funds are 164,000 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -500 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening cash/receivable balance = 160,001. Result: Calculated closing balance = 164,001 LKR; Recorded minus calculated closing = -501 LKR. Interpretation: Calculated closing funds are 164,001 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -501 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening cash/receivable balance. No usable result. Opening cash/receivable balance Next check: Correct or obtain the missing input records. Information still needed: Opening cash/receivable balance. Map context. No map inserted into this decision example Limits A residual is not proof of theft or a measured loss. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-013DP04 | Input distribution Plan timely distribution of approved farm inputs Inputs and examplePurpose Compare usable input stock and delivery commitments with the distribution requirement. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — input distribution, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg input]; Quarantined stock [kg input]; Expired stock [kg input]; Committed usable stock [kg input]; Additional demand [kg input]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg input; kg input) Worked example. Fictional 2025 example. Laggala Pallegama — input distribution. Physical stock = 1,200 kg input; Quarantined stock = 100 kg input; Expired stock = 50 kg input; Committed usable stock = 740 kg input; Additional demand = 500 kg input; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg input; Additional demand gap = 190 kg input. Interpretation: Uncommitted usable stock: 310 kg input. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg input; Additional demand gap = 189 kg input. Interpretation: Uncommitted usable stock: 311 kg input. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Availability must match the item, season and delivery window. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-014DP04 | Service centres Allocate staff to agrarian centres with workload gaps Inputs and examplePurpose Compare agrarian-centre workload with usable staff hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — service centres, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — service centres. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits A capacity gap does not appoint staff or demonstrate the required skills. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Measuring the Success of Your Service Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-015DP04 | Canal maintenance Schedule communal minor-irrigation maintenance Inputs and examplePurpose Check maintenance tasks against shared resources and prerequisite windows. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — canal maintenance, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — canal maintenance. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The draft schedule does not book staff or operate irrigation assets. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Irrigation Management Circular 01/2008 Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-017DP04 | Tank reservations Check reported encroachment evidence Inputs and examplePurpose Check reported overlap before referring an encroachment concern. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — tank reservations, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — tank reservations. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A supplied overlap does not determine ownership or unlawful occupation. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Department of Agrarian Development Services Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-018DP04 | Irrigation equity Review head-end and tail-end water-delivery differences Inputs and examplePurpose Compare documented head-end and tail-end delivery in the same period. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — irrigation equity, the default output explains Investigate the comparable head-end and tail-end delivery difference. Changing Head-end delivered volume for a matching eligible area produces Investigate the comparable head-end and tail-end delivery difference. Missing Head-end delivered volume for a matching eligible area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Head-end delivered volume for a matching eligible area [m³]; Tail-end delivered volume on the same area and period basis [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation equity. Head-end delivered volume for a matching eligible area = 24,000 m³; Tail-end delivered volume on the same area and period basis = 18,000 m³. Results: Difference = -6,000 m³; Relative change = -25 %. Interpretation: Difference: -6,000 m³. Investigate the comparable head-end and tail-end delivery difference. Next check: Investigate the comparable head-end and tail-end delivery difference. Changed input. Change Head-end delivered volume for a matching eligible area = 24,001. Result: Difference = -6,001 m³; Relative change = -25.003 %. Interpretation: Difference: -6,001 m³. Investigate the comparable head-end and tail-end delivery difference. Next check: Investigate the comparable head-end and tail-end delivery difference. Missing input. Omit Head-end delivered volume for a matching eligible area. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits Unequal volumes need comparable areas, needs and operating conditions. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-019DP04 | Registry updates Schedule outdated farmer and land record checks Inputs and examplePurpose Plan checks of outdated farmer and land records within available staff windows. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — registry updates, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — registry updates. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not verify the records or send assignments. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Department of Agrarian Development Services Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP04-020DP04 | Service outcomes Evaluate whether agrarian support improved cultivation Inputs and examplePurpose Compare cultivation changes in supported and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — service outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Verified cultivated share before produces Obtain the missing evidence listed below. Missing Treatment Verified cultivated share before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Verified cultivated share before [%]; Treatment Verified cultivated share after [%]; Comparison Verified cultivated share before [%]; Comparison Verified cultivated share after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (%) Worked example. Fictional 2025 example. Laggala Pallegama — service outcomes. Treatment Verified cultivated share before = 42 %; Treatment Verified cultivated share after = 59 %; Comparison Verified cultivated share before = 39 %; Comparison Verified cultivated share after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Verified cultivated share /example matching definition1. Results: Difference in changes = 10 %. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Verified cultivated share before = 42.42. Result: Difference in changes = 9.58 %. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Verified cultivated share before. No usable result. Treatment Verified cultivated share before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified cultivated share before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits The comparison alone does not establish that support caused the change. Agrarian service officer and relevant land/water specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP05-001DP05 | Command water demand Prepare an irrigation allocation proposal Inputs and examplePurpose Prepare irrigation demand figures for an allocation proposal. Output Comparison table Next step Prepare water-needs scenario creates an unassigned draft that is visible and downloadable, not sent. Rule ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency. Checks For Laggala Pallegama — command water demand, the default output explains Review weather, crop, water-availability and operating evidence. Changing Irrigated crop area produces Review weather, crop, water-availability and operating evidence. Missing Irrigated crop area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction] Result: Gross daily irrigation requirement; Net field requirement (m³/day; mm/day) Worked example. Fictional 2025 example. Laggala Pallegama — command water demand. Irrigated crop area = 85 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction. Results: Gross daily irrigation requirement = 6,687.5 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,687.5 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Changed input. Change Irrigated crop area = 85.85. Result: Gross daily irrigation requirement = 6,754.375 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,754.375 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Missing input. Omit Irrigated crop area. No usable result. Irrigated crop area Next check: Correct or obtain the missing input records. Information still needed: Irrigated crop area. Map context. No map inserted into this decision example Limits Available water, operating constraints and authority are needed before a release decision. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Crop evapotranspiration ETc = crop coefficient Kc × reference evapotranspiration ETo. Use mm/day for both ET values. Sector guidance · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration The match covers the ETc term. Confirm local crop coefficients, rainfall, field losses, efficiency and allocation authority. Implementation: prototype |
| DEC-DP05-003DP05 | Canal performance Check canal delivery shortfalls Inputs and examplePurpose Compare planned and measured canal deliveries to identify shortfalls for review. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — canal performance, the default output explains Review the delivery gap with the scheme operator. Changing Planned canal delivery for the period produces Review the delivery gap with the scheme operator. Missing Planned canal delivery for the period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned canal delivery for the period [m³]; Measured canal delivery for the same period [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — canal performance. Planned canal delivery for the period = 85,000 m³; Measured canal delivery for the same period = 68,000 m³. Results: Difference = -17,000 m³; Relative change = -20 %. Interpretation: Difference: -17,000 m³. Review the delivery gap with the scheme operator. Next check: Review the delivery gap with the scheme operator. Changed input. Change Planned canal delivery for the period = 85,001. Result: Difference = -17,001 m³; Relative change = -20.001 %. Interpretation: Difference: -17,001 m³. Review the delivery gap with the scheme operator. Next check: Review the delivery gap with the scheme operator. Missing input. Omit Planned canal delivery for the period. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits Delivery volume alone does not establish urgency or the cause of a shortfall. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-004DP05 | Reservoir operation Review storage consequences of proposed releases Inputs and examplePurpose Reconcile opening storage, flows and closing observations for a release scenario. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing. Checks For Laggala Pallegama — reservoir operation, the default output explains Reconcile closing balance. Changing Opening storage produces Reconcile closing balance. Missing Opening storage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening storage [m³]; All measured inflows and transfers in [m³]; Releases and transfers out [m³]; Evaporation and other outflows [m³]; Independently observed closing storage [m³] Result: Calculated closing storage; Observed minus calculated closing (m³; m³) Worked example. Fictional 2025 example. Laggala Pallegama — reservoir operation. Opening storage = 160,000 m³; All measured inflows and transfers in = 48,000 m³; Releases and transfers out = 35,000 m³; Evaporation and other outflows = 9,000 m³; Independently observed closing storage = 163,500 m³. Results: Calculated closing storage = 164,000 m³; Observed minus calculated closing = -500 m³. Interpretation: Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening storage = 160,001. Result: Calculated closing storage = 164,001 m³; Observed minus calculated closing = -501 m³. Interpretation: Calculated closing storage are 164,001 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -501 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening storage. No usable result. Opening storage Next check: Correct or obtain the missing input records. Information still needed: Opening storage. Map context. No map inserted into this decision example Limits The balance does not authorise a release or certify storage measurements. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Water storage balance Water storage balance Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP05-008DP05 | Reservoir sedimentation Compare reservoir-capacity survey records Inputs and examplePurpose Compare capacity-survey records before planning bathymetry or desilting appraisal. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — reservoir sedimentation, the default output explains Check the surveys before commissioning bathymetry or desilting appraisal. Changing Earlier surveyed capacity on the same datum produces Check the surveys before commissioning bathymetry or desilting appraisal. Missing Earlier surveyed capacity on the same datum remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier surveyed capacity on the same datum [m³]; Later surveyed capacity on the same datum [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — reservoir sedimentation. Earlier surveyed capacity on the same datum = 900,000 m³; Later surveyed capacity on the same datum = 860,000 m³. Results: Difference = -40,000 m³; Relative change = -4.444 %. Interpretation: Difference: -40,000 m³. Check the surveys before commissioning bathymetry or desilting appraisal. Next check: Check the surveys before commissioning bathymetry or desilting appraisal. Changed input. Change Earlier surveyed capacity on the same datum = 900,001. Result: Difference = -40,001 m³; Relative change = -4.445 %. Interpretation: Difference: -40,001 m³. Check the surveys before commissioning bathymetry or desilting appraisal. Next check: Check the surveys before commissioning bathymetry or desilting appraisal. Missing input. Omit Earlier surveyed capacity on the same datum. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Differences require matching datums, dates and uncertainty; they are not all sedimentation. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Dam Safety Circular No. 4 of 2013 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-009DP05 | Canal rehabilitation Review overdue irrigation repairs Inputs and examplePurpose Review overdue repair cases alongside their engineering and budget evidence. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — canal rehabilitation, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — canal rehabilitation. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Maintenance age alone is not engineering severity or repair priority. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Irrigation Management Circular 01/2008 Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-010DP05 | Drainage Select drainage improvements for persistently waterlogged areas Inputs and examplePurpose Compare drainage alternatives using obstruction, outlet, site and resource evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Clear existing drainage obstructions, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Clear existing drainage obstructions. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Restore the capacity obstructed by recorded debris or vegetation.; Resource needs and adverse effects = Needs an inspection, disposal plan, access and recurring maintenance.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Flood duration; drainage network; outlet capacity; affected hectares; engineering options. Map context. No map inserted into this decision example Limits A lower cost does not establish the best drainage solution. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · A Framework for Land Evaluation Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-011DP05 | Salinity exclusion Check conductivity records for saline-intrusion review Inputs and examplePurpose Identify conductivity observations needing saline-intrusion investigation. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — salinity exclusion, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [µS/cm]; Example lower comparison bound [µS/cm]; Example upper comparison bound [µS/cm]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (µS/cm) Worked example. Fictional 2025 example. Laggala Pallegama — salinity exclusion. Parameter and applicable use = Irrigation-water electrical conductivity; Measured result = 2,500 µS/cm; Example lower comparison bound = 0 µS/cm; Example upper comparison bound = 2,000 µS/cm; Original and limit unit = µS/cm; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 2,500 µS/cm. Interpretation: The supplied Irrigation-water electrical conductivity result is 2,500 µS/cm. Its stated comparison range is 0 to 2,000 µS/cm. Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 2,501; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 2,501 µS/cm. Interpretation: The supplied Irrigation-water electrical conductivity result is 2,501 µS/cm. Its stated comparison range is 0 to 2,000 µS/cm. Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits Sampling conditions, units and location must support the interpretation. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Ambient water limit comparison Select the applicable water-use category and compare the measured parameter in the schedule's unit and limit type. Sector guidance · Water Quality for Agriculture, Irrigation and Drainage Paper 29 Rev. 1 Use the schedule only for the applicable inland surface-water use, such as irrigation. Confirm sampling and laboratory quality. Other media require their own limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-012DP05 | Gate scheduling Schedule approved gate operations without conflicts Inputs and examplePurpose Check gate-operation tasks for timing and resource conflicts. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — gate scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — gate scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The schedule does not operate gates or grant operating authority. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Dam Safety Circular No. 4 of 2013 Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-013DP05 | Water productivity Target schemes with low crop output per water delivered Inputs and examplePurpose Compare matching crop output and delivered water by scheme. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Saleable crop output / Matching irrigation water input, for the same product, process and period. Checks For Laggala Pallegama — water productivity, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable crop output produces Check matching outputs, denominators and operating conditions. Missing Saleable crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable crop output [kg]; Matching irrigation water input [m³] Result: Crop water productivity (kg/m³) Worked example. Fictional 2025 example. Laggala Pallegama — water productivity. Saleable crop output = 19,780 kg; Matching irrigation water input = 7,200 m³. Results: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable crop output = 19,781. Result: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,781 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable crop output. No usable result. Saleable crop output Next check: Correct or obtain the missing input records. Information still needed: Saleable crop output. Map context. No map inserted into this decision example Limits A productivity ratio does not establish a cause or choose an intervention. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Seasonal grain output per diverted irrigation volume Water productivity = seasonal paddy output in kg ÷ diverted seasonal irrigation supply in m³. Sector guidance · Unlocking the Water Potential of Agriculture Match the measurement boundary. This is a scheme-diversion indicator. A farm delivery ratio requires farm-gate volumes and a separate comparison frame. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-014DP05 | Environmental flows Check proposed flows against the stated conditions Inputs and examplePurpose Compare a proposed flow with the supplied reviewed flow condition. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — environmental flows, the default output explains Refer the proposed flow and stated condition to the responsible engineer. Changing Supplied reviewed minimum-flow condition produces Refer the proposed flow and stated condition to the responsible engineer. Missing Supplied reviewed minimum-flow condition remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Supplied reviewed minimum-flow condition [m³/s]; Proposed flow on the same time and location basis [m³/s] Result: Difference; Relative change (m³/s; %) Worked example. Fictional 2025 example. Laggala Pallegama — environmental flows. Supplied reviewed minimum-flow condition = 1.2 m³/s; Proposed flow on the same time and location basis = 0.9 m³/s. Results: Difference = -0.3 m³/s; Relative change = -25 %. Interpretation: Difference: -0.3 m³/s. Refer the proposed flow and stated condition to the responsible engineer. Next check: Refer the proposed flow and stated condition to the responsible engineer. Changed input. Change Supplied reviewed minimum-flow condition = 1.212. Result: Difference = -0.312 m³/s; Relative change = -25.743 %. Interpretation: Difference: -0.312 m³/s. Refer the proposed flow and stated condition to the responsible engineer. Next check: Refer the proposed flow and stated condition to the responsible engineer. Missing input. Omit Supplied reviewed minimum-flow condition. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The example reference is not an adopted environmental-flow rule. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-015DP05 | Hydrological models Check whether model calibration can be reproduced Inputs and examplePurpose Check model-calibration reproduction using the same inputs and versions. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — hydrological models, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [m³/s]; Independently reproduced value [m³/s]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m³/s]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (m³/s; %) Worked example. Fictional 2025 example. Laggala Pallegama — hydrological models. Earlier/source value = 100 m³/s; Independently reproduced value = 90 m³/s; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable m³/s measure; same input scope; Documented absolute comparison tolerance = 0.01 m³/s; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 m³/s; Relative change = -10 %. Interpretation: Difference: -10 m³/s. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 m³/s; Relative change = -10.891 %. Interpretation: Difference: -11 m³/s. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Agreement alone does not establish model fitness for operational use. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-016DP05 | Pumping systems Compare pumping electricity per water volume Inputs and examplePurpose Compare electricity consumed per matching pumped water volume. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Electric energy consumed / Water pumped, for the same product, process and period. Checks For Laggala Pallegama — pumping systems, the default output explains Check matching outputs, denominators and operating conditions. Changing Electric energy consumed produces Check matching outputs, denominators and operating conditions. Missing Electric energy consumed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Electric energy consumed [kWh]; Water pumped [m³] Result: Specific energy use (kWh/m³) Worked example. Fictional 2025 example. Laggala Pallegama — pumping systems. Electric energy consumed = 3,128 kWh; Water pumped = 18,000 m³. Results: Specific energy use = 0.174 kWh/m³. Interpretation: Electric energy consumed: 3,128 kWh; Water pumped: 18,000 m³. This gives 0.174 kWh/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Electric energy consumed = 3,129. Result: Specific energy use = 0.174 kWh/m³. Interpretation: Electric energy consumed: 3,129 kWh; Water pumped: 18,000 m³. This gives 0.174 kWh/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Electric energy consumed. No usable result. Electric energy consumed Next check: Correct or obtain the missing input records. Information still needed: Electric energy consumed. Map context. No map inserted into this decision example Limits Specific energy use is not hydraulic efficiency. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare energy use per unit of output Relate energy use to output over the same operating period. State the reciprocal when reporting energy intensity rather than productivity. Sector guidance · Enterprise-Level Indicators for Resource Productivity and Pollution Intensity Confirm matching energy and pumped volume readings, meter boundaries and operating conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-017DP05 | Rehabilitation investment Compare rehabilitation cash-flow scenarios Inputs and examplePurpose Compare rehabilitation cash flows using the stated discount assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits A positive present value alone is not an investment approval. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP05-018DP05 | Construction delivery Investigate delayed irrigation construction milestones Inputs and examplePurpose Identify irrigation milestones whose actual dates differ from plan. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — construction delivery, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — construction delivery. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits A delay does not establish its cause or contractual liability. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare observed progress with the schedule baseline Retain the approved baseline and compare the reported actual milestone dates with the matching planned dates. Sector guidance · Irrigation Management Circular 01/2008 Confirm the baseline edition and date convention. Leave absent actual dates open. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-019DP05 | Spare parts Prevent shortages of critical irrigation equipment spares Inputs and examplePurpose Compare usable spares and commitments with the stated requirement. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — spare parts, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [spares]; Quarantined stock [spares]; Expired stock [spares]; Committed usable stock [spares]; Additional demand [spares]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (spares; spares) Worked example. Fictional 2025 example. Laggala Pallegama — spare parts. Physical stock = 1,200 spares; Quarantined stock = 100 spares; Expired stock = 50 spares; Committed usable stock = 740 spares; Additional demand = 500 spares; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 spares; Additional demand gap = 190 spares. Interpretation: Uncommitted usable stock: 310 spares. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 spares; Additional demand gap = 189 spares. Interpretation: Uncommitted usable stock: 311 spares. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits A shortage calculation does not authorise procurement. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP05-020DP05 | Public information Correct missing metadata in published reservoir information Inputs and examplePurpose Identify missing source and definition details in reservoir information. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — public information, the default output explains Obtain the missing evidence listed below. Changing Reservoir ID, Reservoir ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Reservoir ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Reservoir ID; Reservoir ID evidence reference; reading time; reading time evidence reference; unit; unit evidence reference; datum; datum evidence reference; source; source evidence reference; review state; review state evidence reference; update schedule; update schedule evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — public information. Reservoir ID = Missing; Reservoir ID evidence reference = ; reading time = Documented; reading time evidence reference = Sample Laggala Pallegama field register / 2025; unit = Documented; unit evidence reference = Sample Laggala Pallegama field register / 2025; datum = Documented; datum evidence reference = Sample Laggala Pallegama field register / 2025; source = Documented; source evidence reference = Sample Laggala Pallegama field register / 2025; review state = Documented; review state evidence reference = Sample Laggala Pallegama field register / 2025; update schedule = Documented; update schedule evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this public information case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Reservoir ID = Documented; Reservoir ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle public information. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Reservoir ID. The required evidence is incomplete for this public information case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Reservoir ID: Missing. Map context. No map inserted into this decision example Limits Metadata completeness does not establish reading accuracy. Irrigation operations engineer and hydrologist; dam safety specialist for structural decisions | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Data Catalog Vocabulary Version 3 Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-001DP06 | Seasonal cropping Review cropping plans against calculated water requirements Inputs and examplePurpose Compare crop-water requirements with the records supporting a seasonal system plan. Output Comparison table Next step Prepare water-needs scenario creates an unassigned draft that is visible and downloadable, not sent. Rule ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency. Checks For Laggala Pallegama — seasonal cropping, the default output explains Review weather, crop, water-availability and operating evidence. Changing Irrigated crop area produces Review weather, crop, water-availability and operating evidence. Missing Irrigated crop area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction] Result: Gross daily irrigation requirement; Net field requirement (m³/day; mm/day) Worked example. Fictional 2025 example. Laggala Pallegama — seasonal cropping. Irrigated crop area = 85 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction. Results: Gross daily irrigation requirement = 6,687.5 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,687.5 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Changed input. Change Irrigated crop area = 85.85. Result: Gross daily irrigation requirement = 6,754.375 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,754.375 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Missing input. Omit Irrigated crop area. No usable result. Irrigated crop area Next check: Correct or obtain the missing input records. Information still needed: Irrigated crop area. Map context. No map inserted into this decision example Limits Calculated crop need is not an approved cropping or release plan. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Crop evapotranspiration ETc = crop coefficient Kc × reference evapotranspiration ETo. Use mm/day for both ET values. Sector guidance · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration The match covers the ETc term. Confirm local crop coefficients, rainfall, field losses, efficiency and allocation authority. Implementation: prototype |
| DEC-DP06-002DP06 | Water delivery Correct system-level water-delivery shortfalls Inputs and examplePurpose Compare system delivery targets and measured water supplied in the same period. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — water delivery, the default output explains Check the matching records and reasons for the difference. Changing Planned system delivery in the stated period produces Check the matching records and reasons for the difference. Missing Planned system delivery in the stated period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned system delivery in the stated period [m³]; Measured system delivery in the same period [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — water delivery. Planned system delivery in the stated period = 85,000 m³; Measured system delivery in the same period = 69,000 m³. Results: Difference = -16,000 m³; Relative change = -18.824 %. Interpretation: Difference: -16,000 m³. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned system delivery in the stated period = 85,001. Result: Difference = -16,001 m³; Relative change = -18.824 %. Interpretation: Difference: -16,001 m³. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned system delivery in the stated period. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A volume shortfall does not establish its cause or authorise a new allocation. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Water Management Secretariat Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-003DP06 | Reservoir networks Review linked-reservoir storage and transfer scenarios Inputs and examplePurpose Reconcile storage and transfer records within a defined control volume. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing. Checks For Laggala Pallegama — reservoir networks, the default output explains Reconcile closing balance. Changing Opening storage produces Reconcile closing balance. Missing Opening storage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening storage [m³]; All measured inflows and transfers in [m³]; Releases and transfers out [m³]; Evaporation and other outflows [m³]; Independently observed closing storage [m³] Result: Calculated closing storage; Observed minus calculated closing (m³; m³) Worked example. Fictional 2025 example. Laggala Pallegama — reservoir networks. Opening storage = 160,000 m³; All measured inflows and transfers in = 48,000 m³; Releases and transfers out = 35,000 m³; Evaporation and other outflows = 9,000 m³; Independently observed closing storage = 163,500 m³. Results: Calculated closing storage = 164,000 m³; Observed minus calculated closing = -500 m³. Interpretation: Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening storage = 160,001. Result: Calculated closing storage = 164,001 m³; Observed minus calculated closing = -501 m³. Interpretation: Calculated closing storage are 164,001 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -501 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening storage. No usable result. Opening storage Next check: Correct or obtain the missing input records. Information still needed: Opening storage. Map context. No map inserted into this decision example Limits Internal transfers must not be counted as both new system inflow and outflow. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Water storage balance Water storage balance Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP06-007DP06 | Land allocation Check land requests before Mahaweli review Inputs and examplePurpose Check land-request and rights evidence before a Mahaweli land referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — land allocation, the default output explains Obtain the missing evidence listed below. Changing Parcel ID, Parcel ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Parcel ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parcel ID; Parcel ID evidence reference; applicant evidence; applicant evidence evidence reference; permitted purpose; permitted purpose evidence reference; plan edition; plan edition evidence reference; current rules; current rules evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — land allocation. Parcel ID = Missing; Parcel ID evidence reference = ; applicant evidence = Documented; applicant evidence evidence reference = Sample Laggala Pallegama field register / 2025; permitted purpose = Documented; permitted purpose evidence reference = Sample Laggala Pallegama field register / 2025; plan edition = Documented; plan edition evidence reference = Sample Laggala Pallegama field register / 2025; current rules = Documented; current rules evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this land allocation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Parcel ID = Documented; Parcel ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle land allocation. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Parcel ID. The required evidence is incomplete for this land allocation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Parcel ID: Missing. Map context. No map inserted into this decision example Limits Complete paperwork does not grant agricultural or commercial use permission. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Mahaweli land request routing Use the land purpose and responsible Mahaweli office to identify the applicable land-disposal procedure before referring the application. Confirm the system area, current documentation and referral authority for the case. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S07, S08, S50 Context alone does not validate the formula. |
| DEC-DP06-009DP06 | Reservation protection Check activities reported inside tank or canal reservations Inputs and examplePurpose Review the reported reservation overlap, inspection, permission and maintenance access before preparing a case referral. Output Inspection case worklist Next step Prepare evidence request or case-review note according to the actual gaps. Rule Reported overlap share = 100 × reported activity overlap / total observed activity area. Count common overlapping parts once in the supplied survey record. No map intersection is performed. Checks Area categories close; overlap cannot exceed activity area; missing survey blocks the numeric comparison; missing site or jurisdiction prevents a substantive recommendation; permission and rights gaps remain visible; drafts are unassigned and not sent; no permission, enforcement or approval is inferred. Case and version; Geographic context; Exact site or asset reference; Applicable system jurisdiction established in this example; Source for the applicable system office; Boundary and source edition; Matching survey and area definitions available in this example; Reservoir or canal and case reference; Activity observed; Inspection date; Reservation survey and basis available in this example; Total observed activity area [ha]; Reported activity area inside the reservation [ha]; Matching permission record; Permission reference or reason it is unknown; Maintenance access reported obstructed Result: Reported overlap inside the reservation; Share of observed activity inside the reservation (ha; %) Worked example. Fictional Inspection 1 / 2025 — fictional / Laggala Pallegama / 2025. 0.15 ha of the 0.6 ha observed activity is reported inside the reservation (25.0%). A matching permission is missing or disputed. This does not establish unlawful occupation. Still needed: Exact site or asset reference; Applicable system jurisdiction and source for the responsible system office; Matching permission record and conditions; Inspection evidence about maintenance access. The figures describe the supplied example records; they do not settle these gaps. Changed input. Use the same 0.6 ha inspection case with reported overlap 0.05 ha. Supply fictional site, system-office source, jurisdiction and permission evidence and record no reported access obstruction. Overlap share is 100 × 0.05 / 0.6 = 8.333%. Prepare a review note against the documented permission, not an enforcement finding. Missing input. Remove matching survey and area-definition evidence. Withhold the overlap/plan-match result and request the matching survey before interpreting it. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A reported overlap is not a finding of unlawful occupation. Confirm the applicable survey, reservation basis, permissions and inspection evidence. No fixed reservation width, eviction, penalty or safety determination is inferred. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Reservation boundary source For a major irrigation scheme, obtain the reservation from the Irrigation Department or Mahaweli Authority blocking-out diagram. Sector guidance · Land Use Planning The match covers boundary selection. Confirm the controlling plan version and surveyed overlap. The regulation does not define the screen's overlap percentage. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-011DP06 | System productivity Compare agricultural water productivity Inputs and examplePurpose Compare matching agricultural output and water volume by system. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Saleable crop output / Matching irrigation water input, for the same product, process and period. Checks For Laggala Pallegama — system productivity, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable crop output produces Check matching outputs, denominators and operating conditions. Missing Saleable crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable crop output [kg]; Matching irrigation water input [m³] Result: Crop water productivity (kg/m³) Worked example. Fictional 2025 example. Laggala Pallegama — system productivity. Saleable crop output = 19,780 kg; Matching irrigation water input = 7,200 m³. Results: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable crop output = 19,781. Result: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,781 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable crop output. No usable result. Saleable crop output Next check: Correct or obtain the missing input records. Information still needed: Saleable crop output. Map context. No map inserted into this decision example Limits Productivity ratios do not establish the cause of a difference. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Seasonal grain output per diverted irrigation volume Water productivity = seasonal paddy output in kg ÷ diverted seasonal irrigation supply in m³. Sector guidance · Unlocking the Water Potential of Agriculture Match the measurement boundary. This is a scheme-diversion indicator. A farm delivery ratio requires farm-gate volumes and a separate comparison frame. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-013DP06 | Irrigation assets Review overdue Mahaweli maintenance cases Inputs and examplePurpose Identify overdue maintenance cases and inspect their engineering evidence. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — irrigation assets, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation assets. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Case age alone is not engineering severity or repair priority. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Irrigation Management Circular 01/2008 Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-014DP06 | Settlement services Plan service capacity for settlement growth Inputs and examplePurpose Compare settlement-service demand with usable service capacity. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — settlement services, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [m³/day]; Rated capacity for that period [m³/day]; Unavailable or restricted capacity [m³/day] Result: Usable capacity minus demand; Usable capacity (m³/day; m³/day) Worked example. Fictional 2025 example. Laggala Pallegama — settlement services. Demand in the selected period = 150 m³/day; Rated capacity for that period = 180 m³/day; Unavailable or restricted capacity = 45 m³/day. Results: Usable capacity minus demand = -15 m³/day; Usable capacity = 135 m³/day. Interpretation: Usable capacity minus demand: -15 m³/day. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 m³/day; Usable capacity = 135 m³/day. Interpretation: Usable capacity minus demand: -16 m³/day. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits A capacity gap does not select or authorise an infrastructure expansion. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-015DP06 | Environmental restoration Select riparian and catchment restoration alternatives Inputs and examplePurpose Compare restoration choices using catchment, riparian, rights and resource evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Riparian natural regeneration, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Riparian natural regeneration. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Allow suitable riparian vegetation to recover.; Resource needs and adverse effects = Needs the applicable boundary, seed sources, protection and landholder agreement.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Site condition; land rights; restoration costs; biodiversity; watershed benefit evidence. Map context. No map inserted into this decision example Limits Predicted benefits remain assumptions until supported by local evidence. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · FP124 Funding Proposal and project documentation Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-018DP06 | Investment delivery Check delayed system-development milestones Inputs and examplePurpose Compare planned and recorded system-development milestone dates. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — investment delivery, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — investment delivery. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits Delay alone does not establish cause, liability or an escalation level. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare observed progress with the schedule baseline Retain the approved baseline and compare the reported actual milestone dates with the matching planned dates. Confirm the baseline edition and date convention. Leave absent actual dates open. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP06-020DP06 | System reporting Reconcile inconsistent land and water system codes Inputs and examplePurpose Find land and water-system codes whose definitions or source references need reconciliation. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — system reporting, the default output explains Obtain the missing evidence listed below. Changing Source system labels, Source system labels evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source system labels remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source system labels; Source system labels evidence reference; official system registry; official system registry evidence reference; geometry edition; geometry edition evidence reference; steward decisions; steward decisions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — system reporting. Source system labels = Missing; Source system labels evidence reference = ; official system registry = Documented; official system registry evidence reference = Sample Laggala Pallegama field register / 2025; geometry edition = Documented; geometry edition evidence reference = Sample Laggala Pallegama field register / 2025; steward decisions = Documented; steward decisions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this system reporting case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source system labels = Documented; Source system labels evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle system reporting. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source system labels. The required evidence is incomplete for this system reporting case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source system labels: Missing. Map context. No map inserted into this decision example Limits A completed mapping checklist does not authorise overwriting the source codes. Water-planning engineer and land/settlement specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · Land Use Planning Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-001DP07 | Forest cover Investigate comparable forest-cover changes Inputs and examplePurpose Compare dated forest-class areas within the same mapped extent. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion. Checks For Laggala Pallegama — forest cover, the default output explains Check the matching source records before interpreting the change. Changing Later mapped class area, Matched area entering the class produces Check the matching source records before interpreting the change. Missing Earlier mapped class area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier mapped class area [ha]; Later mapped class area [ha]; Matched area leaving the class [ha]; Matched area entering the class [ha]; Same fixed analysis extent [ha]; Native class and mapping version; Earlier observation date; Later observation date Result: Net class-area change; Relative class-area change; Gross loss from class; Gross gain to class (ha; %; ha; ha) Worked example. Fictional 2025 example. Laggala Pallegama — forest cover. Earlier mapped class area = 100 ha; Later mapped class area = 90 ha; Matched area leaving the class = 18 ha; Matched area entering the class = 8 ha; Same fixed analysis extent = 200 ha; Native class and mapping version = Sample matching forest/land-use class; Earlier observation date = 2024-06-30; Later observation date = 2025-06-30. Results: Net class-area change = -10 ha; Relative class-area change = -10 %; Gross loss from class = 18 ha; Gross gain to class = 8 ha. Interpretation: 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 check: Check the matching source records before interpreting the change. Changed input. Change Later mapped class area = 91; Matched area entering the class = 9. Result: Net class-area change = -9 ha; Relative class-area change = -9 %; Gross loss from class = 18 ha; Gross gain to class = 9 ha. Interpretation: The recorded Sample matching forest/land-use class area changes from 100 to 91 ha. Net change is -9 ha; supplied gross loss is 18 ha and gross gain is 9 ha. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier mapped class area. No usable result. Earlier mapped class area Next check: Correct or obtain the missing input records. Information still needed: Earlier mapped class area. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A mapped class change does not by itself establish clearing or illegal activity. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Forest transition and deforestation activity data Report forest-to-nonforest change and forest gain separately. Use reviewed area estimates and report their uncertainty. Sector guidance · 2006 IPCC Guidelines, Volume 4, Chapter 3 The match covers the separate forest-loss and forest-gain check. Confirm classification compatibility, uncertainty and site-level validity before use. Implementation: prototype |
| DEC-DP07-003DP07 | Restoration survival Check planting-cohort survival and unknown follow-up Inputs and examplePurpose Check surviving, failed and unvisited members of the original planting cohort. Output Comparison table Next step Prepare cohort follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it. Checks For Laggala Pallegama — restoration survival, the default output explains Check unknown follow-up separately from confirmed survival and failure. Changing Known surviving original members, Known failed original members produces Check unknown follow-up separately from confirmed survival and failure. Missing Original cohort remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original cohort [plants]; Known surviving original members [plants]; Known failed original members [plants]; Original members with unknown follow-up [plants]; Replacements in a separate cohort [plants] Result: Confirmed survival lower bound; Survival upper bound; Unknown follow-up (%; %; plants) Worked example. Fictional 2025 example. Laggala Pallegama — restoration survival. Original cohort = 450 plants; Known surviving original members = 351 plants; Known failed original members = 70 plants; Original members with unknown follow-up = 29 plants; Replacements in a separate cohort = 18 plants. Results: Confirmed survival lower bound = 78 %; Survival upper bound = 84.444 %; Unknown follow-up = 29 plants. Interpretation: Confirmed survival lower bound: 78 %. Next check: Check unknown follow-up separately from confirmed survival and failure. Changed input. Change Known surviving original members = 352; Known failed original members = 69. Result: Confirmed survival lower bound = 78.222 %; Survival upper bound = 84.667 %; Unknown follow-up = 29 plants. Interpretation: Confirmed survival lower bound: 78.222 %. Next check: Check unknown follow-up separately from confirmed survival and failure. Missing input. Omit Original cohort. No usable result. Original cohort Next check: Correct or obtain the missing input records. Information still needed: Original cohort. Map context. No map inserted into this decision example Limits Unknown follow-up is not death, and replacement plants are a separate cohort. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Monitor survival after planting Check the survival of planted trees at follow-up and distinguish established trees from failed areas before considering replanting. Confirm the original cohort, replacements, missed observations and the local follow-up protocol. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-004DP07 | Forest alerts Follow up forest-disturbance cases Inputs and examplePurpose Identify open forest-disturbance cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — forest alerts, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — forest alerts. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Days overdue do not determine the disturbance's severity. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-006DP07 | Encroachment Check suspected forest-encroachment records Inputs and examplePurpose Check reported forest overlap before a field and rights investigation. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — encroachment, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — encroachment. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A supplied overlap does not establish ownership or unlawful occupation. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Land-Use Planning Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-007DP07 | Restoration selection Compare assisted regeneration and planting alternatives Inputs and examplePurpose Compare regeneration and planting options using site, species, maintenance and cost evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Assisted natural regeneration, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Assisted natural regeneration. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Support the existing native regeneration at the site.; Resource needs and adverse effects = Needs seed sources, protection, maintenance and an appropriate recovery period.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Site degradation; natural regeneration; tenure; species options; costs; maintenance. Map context. No map inserted into this decision example Limits A cheaper option is not automatically the best restoration method. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match restoration approach to the site Use the baseline and site conditions to choose a restoration approach and monitor its performance after implementation. Sector guidance · Forest Restoration Module Confirm plot boundaries, reference ecosystem, species and measurement protocol. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-008DP07 | Species selection Shortlist restoration species suited to site conditions Inputs and examplePurpose Check species requirements against the restoration site's evidence. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — species selection, the default output explains Obtain the missing evidence listed below. Changing Species traits, Species traits evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Species traits remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Species traits; Species traits evidence reference; soil; soil evidence reference; rainfall; rainfall evidence reference; elevation; elevation evidence reference; native range; native range evidence reference; site objectives; site objectives evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — species selection. Species traits = Missing; Species traits evidence reference = ; soil = Documented; soil evidence reference = Sample Laggala Pallegama field register / 2025; rainfall = Documented; rainfall evidence reference = Sample Laggala Pallegama field register / 2025; elevation = Documented; elevation evidence reference = Sample Laggala Pallegama field register / 2025; native range = Documented; native range evidence reference = Sample Laggala Pallegama field register / 2025; site objectives = Documented; site objectives evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this species selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Species traits = Documented; Species traits evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle species selection. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Species traits. The required evidence is incomplete for this species selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Species traits: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A complete checklist does not establish ecological suitability. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match restoration approach to the site Use the baseline and site conditions to choose a restoration approach and monitor its performance after implementation. Sector guidance · Forest Restoration Module Confirm plot boundaries, reference ecosystem, species and measurement protocol. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-009DP07 | Nursery supply Compare seedling stock with planting demand Inputs and examplePurpose Compare usable seedling stock and commitments with planting demand. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — nursery supply, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [seedlings]; Quarantined stock [seedlings]; Expired stock [seedlings]; Committed usable stock [seedlings]; Additional demand [seedlings]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (seedlings; seedlings) Worked example. Fictional 2025 example. Laggala Pallegama — nursery supply. Physical stock = 1,200 seedlings; Quarantined stock = 100 seedlings; Expired stock = 50 seedlings; Committed usable stock = 740 seedlings; Additional demand = 500 seedlings; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 seedlings; Additional demand gap = 190 seedlings. Interpretation: Uncommitted usable stock: 310 seedlings. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 seedlings; Additional demand gap = 189 seedlings. Interpretation: Uncommitted usable stock: 311 seedlings. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Stock must match species, provenance, condition and planting window. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Sector guidance · Forest Restoration Module Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-012DP07 | Watershed protection Prepare forest-catchment erosion assessments Inputs and examplePurpose Use the supplied soil-loss factors to identify catchments needing detailed assessment. Output Comparison table Next step Prepare assessment brief creates an unassigned draft that is visible and downloadable, not sent. Rule R × K × LS × C × P, using a mutually consistent SI factor set. Checks For Laggala Pallegama — watershed protection, the default output explains Check local factor and site evidence before selecting a detailed erosion assessment. Changing Rainfall erosivity produces Check local factor and site evidence before selecting a detailed erosion assessment. Missing Rainfall erosivity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall erosivity [MJ mm/(ha h year)]; Soil erodibility [t ha h/(ha MJ mm)]; Slope-length and steepness factor [ratio]; Cover-management factor [fraction]; Support-practice factor [fraction] Result: Estimated annual sheet/rill loss (t/ha/year) Worked example. Fictional 2025 example. Laggala Pallegama — watershed protection. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Results: Estimated annual sheet/rill loss = 15.641 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.641 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Changed input. Change Rainfall erosivity = 951. Result: Estimated annual sheet/rill loss = 15.657 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.657 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Missing input. Omit Rainfall erosivity. No usable result. Rainfall erosivity Next check: Correct or obtain the missing input records. Information still needed: Rainfall erosivity. Map context. No map inserted into this decision example Limits Sheet-and-rill estimates do not measure all catchment sediment processes. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Soil-loss factor product The Sri Lankan catchment study uses the same erosion-factor product. Estimated soil loss = R × K × LS × C × P. Sector guidance · A Guide for Predicting Sheet and Rill Erosion on Forest Land Use locally reviewed factor definitions, units and data for the actual catchment. The study’s factors and map do not transfer automatically. Implementation: prototype |
| DEC-DP07-013DP07 | Forest carbon Review inventory evidence for carbon-stock estimates Inputs and examplePurpose Compare carbon-stock records using matching pools, area and inventory conventions. Output Comparison table Next step Prepare carbon comparison creates an unassigned draft that is visible and downloadable, not sent. Rule (Later carbon density − earlier carbon density) × same inventory area, with identical pools, method and boundaries. Checks For Laggala Pallegama — forest carbon, the default output explains Review the matched pools, area and observation periods. Changing Earlier carbon density produces Review the matched pools, area and observation periods. Missing Earlier carbon density remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier carbon density [t C/ha]; Later carbon density [t C/ha]; Same inventory area [ha]; Included pools and allometry references Result: Carbon stock change; Carbon-density change (t C; t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — forest carbon. Earlier carbon density = 100 t C/ha; Later carbon density = 90 t C/ha; Same inventory area = 85 ha; Included pools and allometry references = Sample matching biomass pools; source model required. Results: Carbon stock change = -850 t C; Carbon-density change = -10 t C/ha. Interpretation: Carbon stock change: -850 t C. Next check: Review the matched pools, area and observation periods. Changed input. Change Earlier carbon density = 101. Result: Carbon stock change = -935 t C; Carbon-density change = -11 t C/ha. Interpretation: Carbon stock change: -935 t C. Next check: Review the matched pools, area and observation periods. Missing input. Omit Earlier carbon density. No usable result. Earlier carbon density Next check: Correct or obtain the missing input records. Information still needed: Earlier carbon density. Map context. No map inserted into this decision example Limits Stock change is not automatically a verified emissions reduction or credit. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Carbon stock-difference component Carbon stock-difference component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP07-016DP07 | Plantation management Schedule silvicultural work by stand condition Inputs and examplePurpose Check silvicultural task windows, resources and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — plantation management, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — plantation management. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The example schedule does not authorise operations in a forest stand. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Forest Restoration Module Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-018DP07 | Biodiversity monitoring Check biodiversity survey comparability Inputs and examplePurpose Check biodiversity survey effort, season and protocol before comparing observations. Output Comparison table Next step Prepare biodiversity comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred. Checks For Laggala Pallegama — biodiversity monitoring, the default output explains Review survey comparability. Changing Observed distinct species produces Review survey comparability. Missing Observed distinct species remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Observed distinct species [species]; Survey effort [hours]; Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed Result: Observed richness; Recorded effort (species; hours) Worked example. Fictional 2025 example. Laggala Pallegama — biodiversity monitoring. Observed distinct species = 28 species; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes. Results: Observed richness = 28 species; Recorded effort = 18 hours. Interpretation: Observed richness: 28 species. Review survey comparability. Next check: Review survey comparability. Changed input. Change Observed distinct species = 29. Result: Observed richness = 29 species; Recorded effort = 18 hours. Interpretation: Observed richness: 29 species. Review survey comparability. Next check: Review survey comparability. Missing input. Omit Observed distinct species. No usable result. Observed distinct species Next check: Correct or obtain the missing input records. Information still needed: Observed distinct species. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Different effort or detection conditions can change observed richness. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check whether biological surveys are comparable Retain the survey protocol, effort and event scope when comparing observations. Confirm season, coverage, species identification and any difference in detectability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP07-020DP07 | Forest records Correct inconsistent forest and compartment classifications Inputs and examplePurpose Identify forest or compartment classifications needing source-definition review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — forest records, the default output explains Obtain the missing evidence listed below. Changing Forest ID, Forest ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Forest ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Forest ID; Forest ID evidence reference; compartment label; compartment label evidence reference; source definition; source definition evidence reference; legal edition; legal edition evidence reference; steward mapping; steward mapping evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — forest records. Forest ID = Missing; Forest ID evidence reference = ; compartment label = Documented; compartment label evidence reference = Sample Laggala Pallegama field register / 2025; source definition = Documented; source definition evidence reference = Sample Laggala Pallegama field register / 2025; legal edition = Documented; legal edition evidence reference = Sample Laggala Pallegama field register / 2025; steward mapping = Documented; steward mapping evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this forest records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Forest ID = Documented; Forest ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle forest records. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Forest ID. The required evidence is incomplete for this forest records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Forest ID: Missing. Map context. No map inserted into this decision example Limits Classification matching does not change an authoritative forest record. Forester, inventory specialist and biodiversity specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · National Forest Inventory Field Manual Template Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP08-002DP08 | Dry and wet spells Check consecutive low-rainfall days Inputs and examplePurpose Identify the dated low-rainfall runs supported by the supplied daily series. Output Dated observation table Next step Prepare comparison note creates an unassigned draft that is visible and downloadable, not sent. Rule Count a run only across distinct consecutive observed days at one gauge using one daily convention and cutoff. Trace and missing days break the known run unless a documented measurement rule supplies a usable value. Checks For Rattota demonstration gauge, the default output explains Review the dated daily sequence and any gaps. Changing Daily rainfall produces Review the dated daily sequence and any gaps. Missing Station or demonstration gauge ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Station or demonstration gauge ID; Observation day; Rainfall value state; Daily rainfall [mm]; Example dry-day cutoff [mm]; A day is dry when rainfall; Daily accumulation and reporting convention; Daily series reference; Quality or missing-day note Result: Daily rainfall (mm) Worked example. Illustrative data / 2025. Rattota demonstration gauge. Station or demonstration gauge ID = DEMO-RATTOTA; Observation day = 2025-06-01; Rainfall value state = Measured; Daily rainfall = 4 mm; Example dry-day cutoff = 1 mm; A day is dry when rainfall = < cutoff; Daily accumulation and reporting convention = Illustrative 24-hour observation day; Daily series reference = Illustrative daily rainfall register; Quality or missing-day note = Illustrative unchecked series. Results: Daily rainfall = 4 mm. Interpretation: 2025-06-01 records 4 mm; this does not meet the stated example dry-day rule. Next check: Review the dated daily sequence and any gaps. Changed input. Change Daily rainfall = 4.1. Result: Daily rainfall = 4.1 mm. Interpretation: 2025-06-01 records 4.1 mm; this does not meet the stated example dry-day rule. Next check: Review the dated daily sequence and any gaps. Missing input. Omit Station or demonstration gauge ID. 2025-06-01 records 4.1 mm; this does not meet the stated example dry-day rule. Next check: Obtain the records listed below. Information still needed: Station or demonstration gauge ID; Record: Station or demonstration gauge ID.. Selected-frame statistics. longestDrySpell = 3 Map context. No map inserted into this decision example Limits This is a known observed run, not a drought diagnosis or warning threshold. A three-hour snapshot cannot replace a daily history. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Longest dry-day run at the published cutoff With daily rainfall below 1 mm and a strict cutoff, count the longest consecutive run of measured dry days. Sector guidance · Five Decadal Trends in Averages and Extremes of Rainfall and Temperature in Sri Lanka Confirm the Department of Meteorology day definition, cutoff and missing-value treatment before operational use. The prototype retains the selected example cutoff. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP08-003DP08 | Station completeness Check missing and late station observations Inputs and examplePurpose Check received records against an explicit observation schedule and quality review. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Completeness = 100 × distinct valid / scheduled observations in the stated window. Age = assessment time − latest valid time in a confirmed common time zone. Compare age with the supplied reporting interval. Checks For Jaffna, the default output explains Obtain the records listed below. Changing Official station ID produces Obtain the records listed below. Missing Official station ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official station ID; Station and instrument metadata reference; Latest published or valid observation time; Monitoring window starts; Monitoring window ends; Assessment time; Time zone; Expected observations [observations]; Distinct valid observations [observations]; Required observation interval [hours]; Observation schedule reference; Validity and duplicate-check reference Result: Valid observations; Observation age (%; hours) Worked example. Official observations; comparison records missing / 2026. Jaffna. Official station ID = 43404; Station and instrument metadata reference = ; Latest published or valid observation time = 2026-11-10T17:30; Monitoring window starts = ; Monitoring window ends = ; Assessment time = ; Time zone = Not stated; Expected observations = Unavailable observations; Distinct valid observations = Unavailable observations; Required observation interval = Unavailable hours; Observation schedule reference = ; Validity and duplicate-check reference = . Results: Valid observations = Unavailable %; Observation age = Unavailable hours. Interpretation: The source reports 43404 at 2026-11-10T17:30. A schedule and QC delivery log are needed to calculate completeness. Next check: Obtain the records listed below. Changed input. Change Official station ID = DEMO revised evidence reference. Result: Valid observations = Unavailable %; Observation age = Unavailable hours. Interpretation: The source reports DEMO revised evidence reference at 2026-11-10T17:30. A schedule and QC delivery log are needed to calculate completeness. Next check: Obtain the records listed below. Missing input. Omit Official station ID. The source reports at 2026-11-10T17:30. A schedule and QC delivery log are needed to calculate completeness. Next check: Obtain the records listed below. Information still needed: Official station ID; Station and instrument metadata reference; Monitoring window starts; Monitoring window ends; Assessment time; Expected observations; Distinct valid observations; Required observation interval; Observation schedule reference; Validity and duplicate-check reference; Confirm the observation or product time zone before joining records or measuring elapsed time.; Source details: Official station ID; Station and instrument metadata reference; Observation schedule reference; Validity and duplicate-check reference.; Period: Monitoring window starts; Monitoring window ends; Assessment time.; Completeness: Expected observations; Distinct valid observations; Required observation interval.. Map context. No map inserted into this decision example Limits One public snapshot does not establish how many readings were scheduled, received or quality-checked. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Observation availability share Observation availability compares received observations with the scheduled expected observations. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP08-005DP08 | Temperature extremes Compare matching temperature observations Inputs and examplePurpose Compare the same temperature statistic and observation interval before investigating a difference. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Temperature difference = observed − matching reference in °C. Match station, statistic, observation interval, units and source definitions. Do not calculate a relative percentage from Celsius values. Checks For Katugastota, the default output explains Obtain the records listed below. Changing Reported temperature produces Obtain the records listed below. Missing Official station ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official station ID; Station and instrument metadata reference; Temperature statistic; Reported temperature [°C]; Matching reference temperature [°C]; Reference statistic; Observation time; Observation interval definition; Reference observation or baseline period; Matching reference and method; Time zone; Original file or delivery reference; Quality-control or review reference Result: Observed minus reference (°C) Worked example. Official observations; comparison records missing / 2026. Katugastota. Official station ID = 43444; Station and instrument metadata reference = ; Temperature statistic = Instantaneous; Reported temperature = 24 °C; Matching reference temperature = Unavailable °C; Reference statistic = Not provided; Observation time = 2026-11-10T17:30; Observation interval definition = Instantaneous value in the published three-hour table; Reference observation or baseline period = ; Matching reference and method = ; Time zone = Not stated; Original file or delivery reference = Observation Data → 3 Hourly Data; https://meteo.gov.lk/; captured 2026-11-10T13:31:12.516Z; Quality-control or review reference = . Results: Observed minus reference = Unavailable °C. Interpretation: Published instantaneous temperature is 24 °C. A matching reference has not been established. Next check: Obtain the records listed below. Changed input. Change Reported temperature = 24.1. Result: Observed minus reference = Unavailable °C. Interpretation: Published instantaneous temperature is 24.1 °C. A matching reference has not been established. Next check: Obtain the records listed below. Missing input. Omit Official station ID. Published instantaneous temperature is 24.1 °C. A matching reference has not been established. Next check: Obtain the records listed below. Information still needed: Official station ID; Station and instrument metadata reference; Reference observation or baseline period; Matching reference and method; Quality-control or review reference; Confirm the observation or product time zone before joining records or measuring elapsed time.; Matching reference temperature and its statistic, interval and source.; State the temperature statistic of the reference.; Source details: Official station ID; Station and instrument metadata reference; Quality-control or review reference.; Comparison: Reference observation or baseline period; Matching reference and method.. Map context. No map inserted into this decision example Limits An instantaneous reading is not a daily maximum or minimum. A difference does not identify a sensor fault or establish a climate trend. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Temperature difference from a matching reference Temperature difference from a matching reference Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP08-006DP08 | Severe weather Prepare a weather-warning review case Inputs and examplePurpose Check the original warning product and accepted observations before a duty-officer review. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check bulletin identity, issue and validity, replacement history, accepted observation references, affected area, applicable procedure and duty responsibility. No hazard threshold is inferred. Checks For Laggala Pallegama warning-review example, the default output explains Obtain the records listed below. Changing Official bulletin ID produces Obtain the records listed below. Missing Official bulletin ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official bulletin ID; Hazard and affected area; Official issue time; Valid from; Valid until; Time zone; Original bulletin and revision; Accepted observations and their period; Applicable warning procedure and criteria; Responsible duty role; Earlier bulletin replaced or cancelled Result: Evidence review () Worked example. Illustrative data / 2025. Laggala Pallegama warning-review example. Official bulletin ID = ; Hazard and affected area = Heavy rainfall / proposed Laggala Pallegama review; Official issue time = ; Valid from = ; Valid until = ; Time zone = Not stated; Original bulletin and revision = ; Accepted observations and their period = ; Applicable warning procedure and criteria = ; Responsible duty role = ; Earlier bulletin replaced or cancelled = . Results: Evidence review = Records needed . Interpretation: This case identifies the bulletin and evidence needed for a duty-officer warning review. It does not issue a warning. Next check: Obtain the records listed below. Changed input. Change Official bulletin ID = DEMO revised evidence reference. Result: Evidence review = Records needed . Interpretation: This case identifies the bulletin and evidence needed for a duty-officer warning review. It does not issue a warning. Next check: Obtain the records listed below. Missing input. Omit Official bulletin ID. This case identifies the bulletin and evidence needed for a duty-officer warning review. It does not issue a warning. Next check: Obtain the records listed below. Information still needed: Official bulletin ID; Official issue time; Valid from; Valid until; Original bulletin and revision; Accepted observations and their period; Applicable warning procedure and criteria; Responsible duty role; Confirm the observation or product time zone before joining records or measuring elapsed time.; Record: Official bulletin ID.; Period: Official issue time; Valid from; Valid until.; Source details: Original bulletin and revision; Accepted observations and their period; Applicable warning procedure and criteria; Responsible duty role.. Map context. No map inserted into this decision example Limits This prepares a review note. It never issues or approves a warning. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending Sri Lanka source match. Check the area and time covered by a warning. Match the affected area and selected time to the Department’s warning. Check the warning ID, original level, issue time and validity window. Use Sri Lanka time (UTC+05:30). Department of Meteorology, Sri Lanka · Weather Advisory System. Warnings endpoint, response fields and time format. CAP 1.2 format reference. Confirm the duty officer, observation evidence and escalation procedure in Institution review. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP08-007DP08 | Forecast verification Compare archived rainfall forecasts with observations Inputs and examplePurpose Measure errors for matching forecasts and observations at one stated lead. Output Decision case table Next step Prepare comparison note creates an unassigned draft that is visible and downloadable, not sent. Rule Error = forecast − observed. For complete matching pairs: RMSE = sqrt(mean(error²)), MAE = mean(abs(error)), bias = mean(error). Match station, variable, accumulation, lead, time zone and observation QC before pooling. Checks For Katugastota forecast example, the default output explains Review the matched sample scores and its coverage. Changing Forecast rainfall produces Review the matched sample scores and its coverage. Missing Station ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Station ID; Archived forecast issued; Rainfall interval starts; Rainfall interval ends; Time zone; Lead to interval end [hours]; Forecast rainfall [mm]; Observed rainfall [mm]; Rainfall interval and measure; Archived forecast and version; Verifying observation and QC reference Result: Forecast minus observed (mm) Worked example. Illustrative data / 2025. Katugastota forecast example. Station ID = 43444; Archived forecast issued = 2025-06-01T08:30; Rainfall interval starts = 2025-06-01T08:30; Rainfall interval ends = 2025-06-02T08:30; Time zone = UTC+05:30; Lead to interval end = 24 hours; Forecast rainfall = 48 mm; Observed rainfall = 42 mm; Rainfall interval and measure = 24-hour accumulated rainfall, mm; Archived forecast and version = DEMO forecast release 1; Verifying observation and QC reference = DEMO matching daily observation 1. Results: Forecast minus observed = 6 mm. Interpretation: Forecast 48 mm; matching observation 42 mm. Forecast minus observed is 6 mm. Next check: Review the matched sample scores and its coverage. Changed input. Change Forecast rainfall = 48.1. Result: Forecast minus observed = 6.1 mm. Interpretation: Forecast 48.1 mm; matching observation 42 mm. Forecast minus observed is 6.1 mm. Next check: Review the matched sample scores and its coverage. Missing input. Omit Station ID. Forecast 48.1 mm; matching observation 42 mm. Complete the matching interval, lead and source checks before scoring. Next check: Obtain the records listed below. Information still needed: Station ID; Record: Station ID.. Selected-frame statistics. n = 3; rmse = 4.655; mae = 4.333; bias = 1; excluded = 0 Map context. No map inserted into this decision example Limits Scores describe the selected sample. They do not establish future forecast reliability or authorise an operational change. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Matched-pair RMSE Matched-pair RMSE Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP08-008DP08 | Seasonal forecasts Check seasonal probability forecast performance Inputs and examplePurpose Compare a defined seasonal event with archived probabilities and verifying rainfall. Output Decision case table Next step Prepare comparison note creates an unassigned draft that is visible and downloadable, not sent. Rule For the predefined event, y = 1 when rainfall exceeds the stated cutoff, otherwise 0. Brier score = mean((p − y)²). Brier skill = 1 − score/reference score for matching cases and a positive reference score. Category and benchmark choices are local assumptions. Checks For Kandy seasonal forecast example, the default output explains Review the matched sample scores and its coverage. Changing Observed season rainfall produces Review the matched sample scores and its coverage. Missing Forecast area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Forecast area; Forecast issue time; Season starts; Season ends; Time zone; Forecast event probability [fraction]; Observed season rainfall [mm]; Illustrative event cutoff [mm]; Independent reference probability [fraction]; Event and category edition; Archived probability and version; Seasonal rainfall and QC reference; Independent benchmark and reference period Result: Event occurred; Squared probability error (0 or 1; 0–1) Worked example. Illustrative data / 2023. Kandy seasonal forecast example. Forecast area = Kandy demonstration area; Forecast issue time = 2023-03-15T08:30; Season starts = 2023-04-01; Season ends = 2023-06-30; Time zone = UTC+05:30; Forecast event probability = 0.7 fraction; Observed season rainfall = 1,040 mm; Illustrative event cutoff = 900 mm; Independent reference probability = 0.33 fraction; Event and category edition = Seasonal rainfall above the illustrative 900 mm cutoff; Archived probability and version = DEMO season 2023 forecast; Seasonal rainfall and QC reference = DEMO season 2023 rainfall; Independent benchmark and reference period = DEMO independent 0.33 benchmark. Results: Event occurred = 1 0 or 1; Squared probability error = 0.09 0–1. Interpretation: The supplied 1,040 mm exceeds the example 900 mm cutoff. The squared probability error is 0.09. Next check: Review the matched sample scores and its coverage. Changed input. Change Observed season rainfall = 1,040.1. Result: Event occurred = 1 0 or 1; Squared probability error = 0.09 0–1. Interpretation: The supplied 1,040.1 mm exceeds the example 900 mm cutoff. The squared probability error is 0.09. Next check: Review the matched sample scores and its coverage. Missing input. Omit Forecast area. Define the event, archive, season, observations and independent benchmark before scoring. Next check: Obtain the records listed below. Information still needed: Forecast area; Record: Forecast area.. Selected-frame statistics. n = 3; brier = 0.137; reference = 0.336; skill = 0.593; excluded = 0 Map context. No map inserted into this decision example Limits A published Brier formula does not verify a local category threshold, benchmark or forecast. No complete seasonal calibration assessment is claimed. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Binary Brier score and skill component Binary Brier score and skill component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Retained context sourcesS75, MET-DOM-RAIN, MET-DOM-CONSENSUS, S10 Context alone does not validate the formula. |
| DEC-DP08-009DP08 | Station siting Check a proposed weather-station site Inputs and examplePurpose Prepare a site-survey worklist from coverage, exposure and operating evidence. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Review variable-specific siting and exposure against the cited standard using a surveyed site and operating records. No generic distance score or automatic preferred site is generated. Checks For Rambukoluwa proposed-site example, the default output explains Obtain the records listed below. Changing Proposed site reference produces Obtain the records listed below. Missing Proposed site reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Proposed site reference; Network coverage gap and intended variable; Surveyed terrain, location and elevation; Instrument exposure and obstacle survey; Siting standard and edition; Access and land-use permission; Power arrangement and reliability; Communications coverage and delivery test; Responsible site-survey role Result: Evidence review () Worked example. Illustrative data / 2025. Rambukoluwa proposed-site example. Proposed site reference = Rambukoluwa demonstration candidate; Network coverage gap and intended variable = ; Surveyed terrain, location and elevation = ; Instrument exposure and obstacle survey = ; Siting standard and edition = WMO No. 8; applicable edition to be recorded; Access and land-use permission = ; Power arrangement and reliability = ; Communications coverage and delivery test = ; Responsible site-survey role = . Results: Evidence review = Records needed . Interpretation: The site-survey checklist identifies coverage, exposure, access and operating evidence for Rambukoluwa demonstration candidate. It does not rank or select a site. Next check: Obtain the records listed below. Changed input. Change Proposed site reference = DEMO revised evidence reference. Result: Evidence review = Records needed . Interpretation: The site-survey checklist identifies coverage, exposure, access and operating evidence for DEMO revised evidence reference. It does not rank or select a site. Next check: Obtain the records listed below. Missing input. Omit Proposed site reference. The site-survey checklist identifies coverage, exposure, access and operating evidence for . It does not rank or select a site. Next check: Obtain the records listed below. Information still needed: Proposed site reference; Network coverage gap and intended variable; Surveyed terrain, location and elevation; Instrument exposure and obstacle survey; Access and land-use permission; Power arrangement and reliability; Communications coverage and delivery test; Responsible site-survey role; Record: Proposed site reference.; Source details: Network coverage gap and intended variable; Surveyed terrain, location and elevation; Instrument exposure and obstacle survey; Access and land-use permission; Power arrangement and reliability; Communications coverage and delivery test; Responsible site-survey role.. Map context. No map inserted into this decision example Limits Complete records support a site review. They do not select or authorise a station. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check station exposure and siting Compare the documented surroundings and exposure with the siting requirements for the measurement. Sector guidance · Guide to Instruments and Methods of Observation, WMO-No. 8 Confirm station purpose, site survey and the applicable instrument classification. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesS02, S63, LOCAL-SRS12, MET-WMO-8, S10 Context alone does not validate the formula. |
| DEC-DP08-013DP08 | Evapotranspiration Check weather inputs for a water-needs calculation Inputs and examplePurpose Check daily weather variables, units and station conditions before an evapotranspiration calculation. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check the daily temperature, humidity, radiation and wind definitions required by the selected reference-evapotranspiration method. Wind unit conversion alone does not provide a 2 m wind observation. This screen checks inputs; it does not calculate ETo. Checks For Katugastota, the default output explains Obtain the records listed below. Changing Published instantaneous temperature produces Obtain the records listed below. Missing Official station ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official station ID; Station and instrument metadata reference; Input time basis; Weather observation day; Published instantaneous temperature [°C]; Daily maximum temperature [°C]; Daily minimum temperature [°C]; Relative humidity [%]; Humidity statistic and method; Daily solar radiation [MJ/m²/day]; Wind speed [km/h]; Wind measurement height [m]; Reference-site location, elevation and surface; Daily dataset and QC reference Result: Evidence review () Worked example. Official observations; comparison records missing / 2026. Katugastota. Official station ID = 43444; Station and instrument metadata reference = ; Input time basis = Three-hour snapshot; Weather observation day = 2026-11-10; Published instantaneous temperature = 24 °C; Daily maximum temperature = Unavailable °C; Daily minimum temperature = Unavailable °C; Relative humidity = 92 %; Humidity statistic and method = ; Daily solar radiation = Unavailable MJ/m²/day; Wind speed = 0 km/h; Wind measurement height = Unavailable m; Reference-site location, elevation and surface = ; Daily dataset and QC reference = Observation Data → 3 Hourly Data; https://meteo.gov.lk/; captured 2026-11-10T13:31:12.516Z. Results: Evidence review = Records needed . Interpretation: Published snapshot: 24 °C, humidity 92%, wind 0 km/h. Daily extrema, radiation, humidity convention and reference-site wind metadata remain separate inputs. No ETo is calculated. Next check: Obtain the records listed below. Changed input. Change Published instantaneous temperature = 24.1. Result: Evidence review = Records needed . Interpretation: Published snapshot: 24.1 °C, humidity 92%, wind 0 km/h. Daily extrema, radiation, humidity convention and reference-site wind metadata remain separate inputs. No ETo is calculated. Next check: Obtain the records listed below. Missing input. Omit Official station ID. Published snapshot: 24.1 °C, humidity 92%, wind 0 km/h. Daily extrema, radiation, humidity convention and reference-site wind metadata remain separate inputs. No ETo is calculated. Next check: Obtain the records listed below. Information still needed: Official station ID; Station and instrument metadata reference; Daily maximum temperature; Daily minimum temperature; Humidity statistic and method; Daily solar radiation; Wind measurement height; Reference-site location, elevation and surface; Supply matching daily weather statistics; the source snapshot is not a daily dataset.; Source details: Official station ID; Station and instrument metadata reference; Humidity statistic and method; Reference-site location, elevation and surface.; Daily weather: Daily maximum temperature; Daily minimum temperature; Daily solar radiation; Wind measurement height.. Map context. No map inserted into this decision example Limits A three-hour observation is not a daily weather dataset. Missing radiation, wind height or daily extrema must remain missing. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Daily inputs for reference evapotranspiration Check daily temperature, humidity, radiation and wind. Record wind height for the reference-height adjustment. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesS16, S17, LOCAL-SRS05, MET-FAO-WEATHER, S10 Context alone does not validate the formula. |
| DEC-DP08-017DP08 | Climate trends Compare annual station observations Inputs and examplePurpose Compare the same annual statistic at one station with its quality and station-history evidence. Output Dated observation table Next step Prepare comparison note creates an unassigned draft that is visible and downloadable, not sent. Rule Display comparable annual statistics for one station and definition. Report their mean and sample standard deviation only for complete compatible selected records. No trend significance or climate attribution is calculated. Checks For Katugastota annual demonstration, the default output explains Review the documented case with the responsible role. Changing Annual statistic produces Review the documented case with the responsible role. Missing Official station ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official station ID; Station and instrument metadata reference; Observation year [year]; Annual temperature statistic; Annual statistic [°C]; Expected daily observations [days]; Valid daily observations [days]; Annual aggregation and missing-data method; Annual dataset and quality reference; Station history and comparability assessment Result: Annual temperature statistic; Daily coverage (°C; %) Worked example. Illustrative data / 2023. Katugastota annual demonstration. Official station ID = DEMO-KATUGASTOTA; Station and instrument metadata reference = DEMO stable station-history record; Observation year = 2,023 year; Annual temperature statistic = Mean temperature; Annual statistic = 25.6 °C; Expected daily observations = 365 days; Valid daily observations = 365 days; Annual aggregation and missing-data method = DEMO matching complete-day mean convention; Annual dataset and quality reference = DEMO annual series 2023; Station history and comparability assessment = DEMO comparability assessment. Results: Annual temperature statistic = 25.6 °C; Daily coverage = 100 %. Interpretation: The supplied 2023 mean temperature is 25.6 °C, with 100% reported daily coverage. No trend or attribution is calculated. Next check: Review the documented case with the responsible role. Changed input. Change Annual statistic = 25.7. Result: Annual temperature statistic = 25.7 °C; Daily coverage = 100 %. Interpretation: The supplied 2023 mean temperature is 25.7 °C, with 100% reported daily coverage. No trend or attribution is calculated. Next check: Review the documented case with the responsible role. Missing input. Omit Official station ID. The supplied 2023 mean temperature is 25.7 °C, with 100% reported daily coverage. No trend or attribution is calculated. Next check: Obtain the records listed below. Information still needed: Official station ID; Source details: Official station ID.. Selected-frame statistics. n = 3; mean = 25.7; sd = 0.1; excluded = 0 Map context. No map inserted into this decision example Limits Three illustrative annual values do not establish a long-term climate trend. The saved three-hour snapshot cannot supply an annual mean. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Retained context sourcesLOCAL-SRS12, MET-WMO-CLIMATE, S10 Context alone does not validate the formula. |
| DEC-DP08-020DP08 | Forecast publication Check a weather product before SHARED publication Inputs and examplePurpose Check source rights, product version, validity and audience before a publication review. Output Decision case table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Retain the original product, issue and validity, source version, replacement history, intended audience, review evidence and permitted SHARED use. Public availability alone is not redistribution permission. Checks For consensus_pdf.pdf, the default output explains Obtain the records listed below. Changing Publisher product ID produces Obtain the records listed below. Missing Publisher product ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Publisher product ID; Product type; Original issue date; Valid period exactly as published; Period definition; Original product and captured version; Earlier version or replacement reference; SHARED reuse and redistribution permission; Proposed SHARED audience; Responsible publication reviewer; Editorial and technical review record Result: Evidence review () Worked example. Official product metadata; SHARED review records missing / 2026. consensus_pdf.pdf. Publisher product ID = ; Product type = Issued seasonal outlook; Original issue date = 2026-10-30; Valid period exactly as published = November, December and January (NDJ) 2026/27; Period definition = Clear; Original product and captured version = consensus_pdf.pdf; https://meteo.gov.lk/pdfs/consensus_pdf.pdf; Earlier version or replacement reference = ; SHARED reuse and redistribution permission = ; Proposed SHARED audience = ; Responsible publication reviewer = ; Editorial and technical review record = . Results: Evidence review = Records needed . Interpretation: Original Issued seasonal outlook issued 2026-10-30. Validity as printed: November, December and January (NDJ) 2026/27. SHARED reuse permission, audience and publication review are separate records. Next check: Obtain the records listed below. Changed input. Change Publisher product ID = DEMO revised evidence reference. Result: Evidence review = Records needed . Interpretation: Original Issued seasonal outlook issued 2026-10-30. Validity as printed: November, December and January (NDJ) 2026/27. SHARED reuse permission, audience and publication review are separate records. Next check: Obtain the records listed below. Missing input. Omit Publisher product ID. Original Issued seasonal outlook issued 2026-10-30. Validity as printed: November, December and January (NDJ) 2026/27. SHARED reuse permission, audience and publication review are separate records. Next check: Obtain the records listed below. Information still needed: Publisher product ID; SHARED reuse and redistribution permission; Proposed SHARED audience; Responsible publication reviewer; Editorial and technical review record; Record: Publisher product ID.; Source details: SHARED reuse and redistribution permission; Proposed SHARED audience; Responsible publication reviewer; Editorial and technical review record.. Map context. No map inserted into this decision example Limits The original Department publication is separate from a SHARED publication decision. No publication is authorised or sent by this screen. Duty meteorologist and climate/forecast verification specialist | Candidate; institutional release acceptance pending Sri Lanka source match. Verify the original warning before sharing. For a Department warning, check the warning ID, original level, issue time, validity and affected area against the Department’s current record. Department of Meteorology, Sri Lanka · Weather Advisory System. Warnings endpoint, response fields and time format. CAP 1.2 format reference. Confirm reuse permission and the publication reviewer in Institution review. Public availability does not grant permission. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesS17, LOCAL-SRS03, MET-DOM-RAIN, MET-DOM-CONSENSUS, MET-DOM-TEMP, S10 Context alone does not validate the formula. |
| DEC-DP09-001DP09 | Crop economics Compare export-crop gross margins Inputs and examplePurpose Compare export-crop revenue and variable costs for the stated enterprises. Output Comparison table Next step Prepare margin comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Gross margin = saleable output × realized price − variable costs. Divide by matching hectares for margin/ha; variable-cost break-even price = variable costs / output. Checks For Laggala Pallegama — crop economics, the default output explains Review the prices, quantities and costs behind the margin. Changing Saleable output produces Review the prices, quantities and costs behind the margin. Missing Saleable output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable output [kg]; Realized price [LKR/kg]; Variable costs [LKR]; Matching crop area [ha]; Crop and saleable-output basis Result: Enterprise gross margin; Gross margin per hectare; Variable-cost break-even price (LKR; LKR/ha; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — crop economics. Saleable output = 600 kg; Realized price = 2,000 LKR/kg; Variable costs = 650,000 LKR; Matching crop area = 1 ha; Crop and saleable-output basis = Saleable dry pepper / fictional one-hectare crop enterprise / same season. Results: Enterprise gross margin = 550,000 LKR; Gross margin per hectare = 550,000 LKR/ha; Variable-cost break-even price = 1,083.333 LKR/kg. Interpretation: The supplied 600 kg at 2,000 LKR/kg gives 1,200,000 LKR revenue. After 650,000 LKR variable costs, gross margin is 550,000 LKR. Next check: Review the prices, quantities and costs behind the margin. Changed input. Change Saleable output = 601. Result: Enterprise gross margin = 552,000 LKR; Gross margin per hectare = 552,000 LKR/ha; Variable-cost break-even price = 1,081.531 LKR/kg. Interpretation: The supplied 601 kg at 2,000 LKR/kg gives 1,202,000 LKR revenue. After 650,000 LKR variable costs, gross margin is 552,000 LKR. Next check: Review the prices, quantities and costs behind the margin. Missing input. Omit Saleable output. No usable result. Saleable output Next check: Correct or obtain the missing input records. Information still needed: Saleable output. Map context. No map inserted into this decision example Limits Gross margin excludes fixed costs and does not establish net profit. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Enterprise gross margin Enterprise gross margin Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP09-002DP09 | Market opportunities Prioritize feasible export-crop market development Inputs and examplePurpose Compare market-development options using quality, buyer, capacity and resource evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Pepper quality and buyer linkage, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Pepper quality and buyer linkage. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Develop the proposed pepper-quality and buyer relationship.; Resource needs and adverse effects = Needs grade evidence, buyer demand, volumes and agreement on delivery conditions.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Crop-market options; demand evidence; quality requirements; access costs; risks. Map context. No map inserted into this decision example Limits Budget headroom does not establish market demand or export eligibility. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Export Procedure and Logistics Requirements Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-003DP09 | Post-harvest quality Select processing stages with excessive spice losses Inputs and examplePurpose Reconcile spice-processing input, output, by-products and stock. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — post-harvest quality, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — post-harvest quality. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unexplained mass balance is not automatically a measured processing loss. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Published Sri Lankan step. The guide reports roughly 30–33 kg dried black pepper per 100 kg raw pepper. Track raw and dried weight for the same lot. Keep normal drying weight reduction separate from unexplained losses. Department of Export Agriculture · Pepper cultivation and processing guide. Pepper Products, Black Pepper. Confirm product form, intake moisture and the applicable operating range before interpreting a yield gap. Calculation reference. International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-004DP09 | Crop productivity Compare export-crop yield records Inputs and examplePurpose Compare matching harvested output and harvested area for export crops. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Harvested crop output / Matching harvested crop area, for the same product, process and period. Checks For Laggala Pallegama — crop productivity, the default output explains Check matching outputs, denominators and operating conditions. Changing Harvested crop output produces Check matching outputs, denominators and operating conditions. Missing Harvested crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Harvested crop output [kg]; Matching harvested crop area [ha] Result: Crop yield (kg/ha) Worked example. Fictional 2025 example. Laggala Pallegama — crop productivity. Harvested crop output = 2,800 kg; Matching harvested crop area = 2 ha. Results: Crop yield = 1,400 kg/ha. Interpretation: Harvested crop output: 2,800 kg; Matching harvested crop area: 2 ha. This gives 1,400 kg/ha. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Harvested crop output = 2,801. Result: Crop yield = 1,400.5 kg/ha. Interpretation: Harvested crop output: 2,801 kg; Matching harvested crop area: 2 ha. This gives 1,400.5 kg/ha. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Harvested crop output. No usable result. Harvested crop output Next check: Correct or obtain the missing input records. Information still needed: Harvested crop output. Map context. No map inserted into this decision example Limits Yield differences do not identify their agronomic causes. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Crop yield per harvested area Crop yield per harvested area Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP09-005DP09 | Crop suitability Shortlist export crops suited to local soils and climate Inputs and examplePurpose Check soil, climate and crop-requirement evidence for proposed export crops. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — crop suitability, the default output explains Obtain the missing evidence listed below. Changing Crop requirements, Crop requirements evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Crop requirements remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Crop requirements; Crop requirements evidence reference; soil; soil evidence reference; rainfall; rainfall evidence reference; temperature; temperature evidence reference; slope; slope evidence reference; shade; shade evidence reference; water access; water access evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — crop suitability. Crop requirements = Missing; Crop requirements evidence reference = ; soil = Documented; soil evidence reference = Sample Laggala Pallegama field register / 2025; rainfall = Documented; rainfall evidence reference = Sample Laggala Pallegama field register / 2025; temperature = Documented; temperature evidence reference = Sample Laggala Pallegama field register / 2025; slope = Documented; slope evidence reference = Sample Laggala Pallegama field register / 2025; shade = Documented; shade evidence reference = Sample Laggala Pallegama field register / 2025; water access = Documented; water access evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this crop suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Crop requirements = Documented; Crop requirements evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle crop suitability. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Crop requirements. The required evidence is incomplete for this crop suitability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Crop requirements: Missing. Map context. No map inserted into this decision example Limits A complete evidence record does not establish crop suitability. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Match crop requirements with site limitations Compare the requirements of the stated crop or land use with relevant land qualities and identify limiting conditions. Sector guidance · Pepper cultivation guidance Confirm local crop requirements, agroecological zone, soil observations and decision thresholds. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-006DP09 | Planting materials Plan certified planting-material supply Inputs and examplePurpose Compare valid planting-material stock with matching demand and delivery windows. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — planting materials, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [plants]; Quarantined stock [plants]; Expired stock [plants]; Committed usable stock [plants]; Additional demand [plants]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (plants; plants) Worked example. Fictional 2025 example. Laggala Pallegama — planting materials. Physical stock = 1,200 plants; Quarantined stock = 100 plants; Expired stock = 50 plants; Committed usable stock = 740 plants; Additional demand = 500 plants; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 plants; Additional demand gap = 190 plants. Interpretation: Uncommitted usable stock: 310 plants. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 plants; Additional demand gap = 189 plants. Interpretation: Uncommitted usable stock: 311 plants. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Availability alone does not establish certification or provenance. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Sector guidance · Quality Declared Planting Material Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-007DP09 | Plant health Check unusual export-crop health observations Inputs and examplePurpose Identify unusual crop-health observations for a field or diagnostic review. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — plant health, the default output explains Check the unusual observation and its comparison basis. Changing Reference affected plants per 100 inspected produces Check the unusual observation and its comparison basis. Missing Reference affected plants per 100 inspected remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Reference affected plants per 100 inspected [affected plants per 100 inspected]; Observed affected plants per 100 inspected [affected plants per 100 inspected] Result: Difference; Relative change (affected plants per 100 inspected; %) Worked example. Fictional 2025 example. Laggala Pallegama — plant health. Reference affected plants per 100 inspected = 12 affected plants per 100 inspected; Observed affected plants per 100 inspected = 18 affected plants per 100 inspected. Results: Difference = 6 affected plants per 100 inspected; Relative change = 50 %. Interpretation: Difference: 6 affected plants per 100 inspected. Next check: Check the unusual observation and its comparison basis. Changed input. Change Reference affected plants per 100 inspected = 12.12. Result: Difference = 5.88 affected plants per 100 inspected; Relative change = 48.515 %. Interpretation: Difference: 5.88 affected plants per 100 inspected. Next check: Check the unusual observation and its comparison basis. Missing input. Omit Reference affected plants per 100 inspected. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits Observed changes do not establish a disease diagnosis or control treatment. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-009DP09 | Replanting Compare rehabilitation and replanting of ageing crop stands Inputs and examplePurpose Compare rehabilitation and replanting choices for an ageing stand. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Rehabilitate the existing stand, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Rehabilitate the existing stand. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve the existing crop stand.; Resource needs and adverse effects = Needs stand-health, remaining-life, treatment and yield-response evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Stand age; yield; disease; replant cost; income gap; options. Map context. No map inserted into this decision example Limits Cost alone does not establish future yield or the best replacement strategy. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Pepper cultivation guidance Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-012DP09 | Value addition Appraise investments in grading drying and processing Inputs and examplePurpose Compare grading, drying or processing cash-flow scenarios. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Present value depends on the supplied volumes, prices, costs and discount assumption. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP09-013DP09 | Traceability Check broken lot-to-farm links Inputs and examplePurpose Find lot-to-farm links whose source identity or lineage needs checking. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Checks For Laggala Pallegama — traceability, the default output explains Investigate linked downstream lot. Changing Recorded upstream issue produces Review recorded lineage. Missing Upstream lot/source reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Upstream lot/source reference; Downstream lot/batch reference; Exact upstream source version; Recorded upstream issue Result: Broken or affected lineage (items) Worked example. Fictional 2025 example. Laggala Pallegama — traceability. Upstream lot/source reference = EXAMPLE-ROOT; Downstream lot/batch reference = 2025-BATCH-1; Exact upstream source version = Sample version1; Recorded upstream issue = Confirmed defect. Results: Broken or affected lineage = 1 items. Interpretation: Broken or affected lineage: 1 items. Investigate linked downstream lot. Next check: Investigate linked downstream lot. Changed input. Change Recorded upstream issue = None. Result: Broken or affected lineage = 0 items. Interpretation: Broken or affected lineage: 0 items. Review recorded lineage. Next check: Review recorded lineage. Missing input. Omit Upstream lot/source reference. No usable result. Upstream lot/source reference Next check: Correct or obtain the missing input records. Information still needed: Upstream lot/source reference. Map context. No map inserted into this decision example Limits A missing link must not be replaced with an invented farm origin. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Source and destination links for food lots Trace food back to its recorded source and forward to the next recorded destination. Sector guidance · Food Hygiene Regulations 2011 Confirm the applicable food operation, record period, linkage and recall authority. Obtain the current regulations and records. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-015DP09 | Climate adaptation Compare shade water and soil adaptation practices Inputs and examplePurpose Compare shade, soil-cover and water-adaptation choices using local evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Improve shade management, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Improve shade management. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Change the stated shade-management practice.; Resource needs and adverse effects = Needs crop response, labour, canopy and disease-risk evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Crop exposure; practice costs; water requirement; yield evidence; uncertainty. Map context. No map inserted into this decision example Limits Stated benefits remain assumptions until supported for the crop and site. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Pepper cultivation guidance Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-018DP09 | Soil conservation Prepare erosion-assessment evidence for export-crop land Inputs and examplePurpose Use supplied soil-loss factors to prepare erosion-assessment evidence. Output Comparison table Next step Prepare assessment brief creates an unassigned draft that is visible and downloadable, not sent. Rule R × K × LS × C × P, using a mutually consistent SI factor set. Checks For Laggala Pallegama — soil conservation, the default output explains Check local factor and site evidence before selecting a detailed erosion assessment. Changing Rainfall erosivity produces Check local factor and site evidence before selecting a detailed erosion assessment. Missing Rainfall erosivity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall erosivity [MJ mm/(ha h year)]; Soil erodibility [t ha h/(ha MJ mm)]; Slope-length and steepness factor [ratio]; Cover-management factor [fraction]; Support-practice factor [fraction] Result: Estimated annual sheet/rill loss (t/ha/year) Worked example. Fictional 2025 example. Laggala Pallegama — soil conservation. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Results: Estimated annual sheet/rill loss = 15.641 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.641 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Changed input. Change Rainfall erosivity = 951. Result: Estimated annual sheet/rill loss = 15.657 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.657 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Missing input. Omit Rainfall erosivity. No usable result. Rainfall erosivity Next check: Correct or obtain the missing input records. Information still needed: Rainfall erosivity. Map context. No map inserted into this decision example Limits The estimate does not itself select a conservation treatment. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Soil-loss factor product The Sri Lankan catchment study uses the same erosion-factor product. Estimated soil loss = R × K × LS × C × P. Sector guidance · A Guide for Predicting Sheet and Rill Erosion on Forest Land Use locally reviewed factor definitions, units and data for the actual catchment. The study’s factors and map do not transfer automatically. Implementation: prototype |
| DEC-DP09-019DP09 | Grower records Reconcile inconsistent crop names and varieties Inputs and examplePurpose Find inconsistent crop and variety definitions before reconciling records. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — grower records, the default output explains Obtain the missing evidence listed below. Changing Source crop label, Source crop label evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source crop label remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source crop label; Source crop label evidence reference; scientific name; scientific name evidence reference; variety registry; variety registry evidence reference; definition; definition evidence reference; steward decision; steward decision evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — grower records. Source crop label = Missing; Source crop label evidence reference = ; scientific name = Documented; scientific name evidence reference = Sample Laggala Pallegama field register / 2025; variety registry = Documented; variety registry evidence reference = Sample Laggala Pallegama field register / 2025; definition = Documented; definition evidence reference = Sample Laggala Pallegama field register / 2025; steward decision = Documented; steward decision evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this grower records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source crop label = Documented; Source crop label evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle grower records. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source crop label. The required evidence is incomplete for this grower records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source crop label: Missing. Map context. No map inserted into this decision example Limits Names alone do not establish varietal identity or genetic equivalence. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · Pepper cultivation guidance Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP09-020DP09 | Programme evaluation Evaluate export-crop support outcomes beyond participation Inputs and examplePurpose Compare enterprise outcome changes in supported and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — programme evaluation, the default output explains Obtain the missing evidence listed below. Changing Treatment Enterprise gross margin before produces Obtain the missing evidence listed below. Missing Treatment Enterprise gross margin before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Enterprise gross margin before [LKR/ha]; Treatment Enterprise gross margin after [LKR/ha]; Comparison Enterprise gross margin before [LKR/ha]; Comparison Enterprise gross margin after [LKR/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR/ha) Worked example. Fictional 2025 example. Laggala Pallegama — programme evaluation. Treatment Enterprise gross margin before = 420,000 LKR/ha; Treatment Enterprise gross margin after = 590,000 LKR/ha; Comparison Enterprise gross margin before = 390,000 LKR/ha; Comparison Enterprise gross margin after = 460,000 LKR/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Enterprise gross margin /example matching definition1. Results: Difference in changes = 100,000 LKR/ha. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Enterprise gross margin before = 420,001. Result: Difference in changes = 99,999 LKR/ha. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Enterprise gross margin before. No usable result. Treatment Enterprise gross margin before Next check: Correct or obtain the missing input records. Information still needed: Treatment Enterprise gross margin before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits The difference alone does not establish an effect of the support programme. Export-crop agronomist and market/quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP10-003DP10 | Input costs Investigate high local farm production costs Inputs and examplePurpose Compare matching farm-cost components and cultivated hectares. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Checks For Laggala Pallegama — input costs, the default output explains Review cost components and comparable verified outputs. Changing Labour cost produces Review cost components and comparable verified outputs. Missing Labour cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Verified matching hectares [ha] Result: Cost per matching unit; Total cost (LKR/ha; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — input costs. Labour cost = 180,000 LKR; Material/input cost = 255,000 LKR; Other non-overlapping cost = 62,000 LKR; Verified matching hectares = 5.4 ha. Results: Cost per matching unit = 92,037.037 LKR/ha; Total cost = 497,000 LKR. Interpretation: The supplied costs total 497,000 LKR for 5.4 ha. Cost per matching unit is 92,037.037 LKR/ha. Next check: Review cost components and comparable verified outputs. Changed input. Change Labour cost = 180,001. Result: Cost per matching unit = 92,037.222 LKR/ha; Total cost = 497,001 LKR. Interpretation: The supplied costs total 497,001 LKR for 5.4 ha. Cost per matching unit is 92,037.222 LKR/ha. Next check: Review cost components and comparable verified outputs. Missing input. Omit Labour cost. No usable result. Labour cost Next check: Correct or obtain the missing input records. Information still needed: Labour cost. Map context. No map inserted into this decision example Limits High cost alone does not establish its cause or the best intervention. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Paddy cash cost per unit of area The survey reports paddy cash production cost per acre. Normalize included cash production costs by the corresponding paddy area. Sector guidance · Socio Economics and Planning Centre downloads Compare the same crop, season and cost components and convert the area consistently. The cited survey covers cash payments. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-005DP10 | Provincial production Compare crop output with its target Inputs and examplePurpose Compare accepted crop output with its stated target. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — provincial production, the default output explains Check the matching records and reasons for the difference. Changing Planned value produces Check the matching records and reasons for the difference. Missing Planned value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned value [kg]; Observed value [kg] Result: Difference; Relative change (kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — provincial production. Planned value = 100 kg; Observed value = 90 kg. Results: Difference = -10 kg; Relative change = -10 %. Interpretation: Difference: -10 kg. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned value = 101. Result: Difference = -11 kg; Relative change = -10.891 %. Interpretation: Difference: -11 kg. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned value. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A shortfall does not establish its cause or whether the target was appropriate. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Paddy Statistics Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-007DP10 | Extension staffing Review extension staff capacity gaps Inputs and examplePurpose Compare extension workload with usable staff hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — extension staffing, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — extension staffing. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits A gap does not establish staff skills, deployment authority or travel feasibility. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-008DP10 | Seed distribution Match approved seasonal seed demand to valid stocks Inputs and examplePurpose Compare valid seed stock and commitments with the stated seasonal demand. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — seed distribution, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg seed]; Quarantined stock [kg seed]; Expired stock [kg seed]; Committed usable stock [kg seed]; Additional demand [kg seed]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg seed; kg seed) Worked example. Fictional 2025 example. Laggala Pallegama — seed distribution. Physical stock = 1,200 kg seed; Quarantined stock = 100 kg seed; Expired stock = 50 kg seed; Committed usable stock = 740 kg seed; Additional demand = 500 kg seed; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg seed; Additional demand gap = 190 kg seed. Interpretation: Uncommitted usable stock: 310 kg seed. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg seed; Additional demand gap = 189 kg seed. Interpretation: Uncommitted usable stock: 311 kg seed. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Stock must match the crop, quality and required delivery window. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-013DP10 | Mechanization access Plan shared machinery services for uncovered farming areas Inputs and examplePurpose Compare machinery-service demand with usable machine hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — mechanization access, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [machine hours]; Rated capacity for that period [machine hours]; Unavailable or restricted capacity [machine hours] Result: Usable capacity minus demand; Usable capacity (machine hours; machine hours) Worked example. Fictional 2025 example. Laggala Pallegama — mechanization access. Demand in the selected period = 150 machine hours; Rated capacity for that period = 180 machine hours; Unavailable or restricted capacity = 45 machine hours. Results: Usable capacity minus demand = -15 machine hours; Usable capacity = 135 machine hours. Interpretation: Usable capacity minus demand: -15 machine hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 machine hours; Usable capacity = 135 machine hours. Interpretation: Usable capacity minus demand: -16 machine hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish access, operator competence or booking permission. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-014DP10 | Water-saving practices Compare irrigation-management practices on equivalent farms Inputs and examplePurpose Compare matching crop output and irrigation water on equivalent farms. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Saleable crop output / Matching irrigation water input, for the same product, process and period. Checks For Laggala Pallegama — water-saving practices, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable crop output produces Check matching outputs, denominators and operating conditions. Missing Saleable crop output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable crop output [kg]; Matching irrigation water input [m³] Result: Crop water productivity (kg/m³) Worked example. Fictional 2025 example. Laggala Pallegama — water-saving practices. Saleable crop output = 19,780 kg; Matching irrigation water input = 7,200 m³. Results: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,780 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable crop output = 19,781. Result: Crop water productivity = 2.747 kg/m³. Interpretation: Saleable crop output: 19,781 kg; Matching irrigation water input: 7,200 m³. This gives 2.747 kg/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable crop output. No usable result. Saleable crop output Next check: Correct or obtain the missing input records. Information still needed: Saleable crop output. Map context. No map inserted into this decision example Limits Ratios alone do not identify which management practice caused a difference. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Output per irrigation water supplied Water productivity = crop output ÷ volume of irrigation water applied for the matching scope. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-015DP10 | Diversification Shortlist locally viable alternative crop programmes Inputs and examplePurpose Compare alternative crop programmes using suitability, water, livelihoods and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Drought-tolerant field crops, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Drought-tolerant field crops. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Support the proposed field crops under the stated dry-season scenario.; Resource needs and adverse effects = Needs local suitability, water, seed, labour and market evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Crop suitability; gross margins; demand; water; labour; programme cost. Map context. No map inserted into this decision example Limits A budget comparison does not establish a viable crop programme. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Farm Management for Asia A Systems Approach Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-016DP10 | Horticulture Review post-harvest loss balances Inputs and examplePurpose Reconcile post-harvest input, saleable output, by-products and stock. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — horticulture, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — horticulture. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits Unaccounted quantities need source checks before a loss-reduction intervention. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-019DP10 | Reporting consistency Correct differences between district crop returns Inputs and examplePurpose Compare district crop returns using matching definitions, units and periods. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — reporting consistency, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [kg]; Independent comparison measurement [kg]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — reporting consistency. Original source measurement = 100 kg; Independent comparison measurement = 90 kg; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable kg measure; same input scope. Results: Difference = -10 kg; Relative change = -10 %. Interpretation: Difference: -10 kg. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 kg; Relative change = -10.891 %. Interpretation: Difference: -11 kg. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A numerical difference does not identify which return is correct. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Paddy Statistics Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP10-020DP10 | Provincial outcomes Evaluate provincial agricultural programmes Inputs and examplePurpose Compare agricultural programme outcomes using matching treatment and comparison records. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — provincial outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Crop productivity before produces Obtain the missing evidence listed below. Missing Treatment Crop productivity before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Crop productivity before [kg/ha]; Treatment Crop productivity after [kg/ha]; Comparison Crop productivity before [kg/ha]; Comparison Crop productivity after [kg/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (kg/ha) Worked example. Fictional 2025 example. Laggala Pallegama — provincial outcomes. Treatment Crop productivity before = 42 kg/ha; Treatment Crop productivity after = 59 kg/ha; Comparison Crop productivity before = 39 kg/ha; Comparison Crop productivity after = 46 kg/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Crop productivity /example matching definition1. Results: Difference in changes = 10 kg/ha. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 kg/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Crop productivity before = 42.42. Result: Difference in changes = 9.58 kg/ha. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 kg/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Crop productivity before. No usable result. Treatment Crop productivity before Next check: Correct or obtain the missing input records. Information still needed: Treatment Crop productivity before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A descriptive difference does not establish programme impact. Provincial crop specialist and extension coordinator | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP11-002DP11 | Delivery performance Investigate spending ahead of verified physical progress (proposed; scope pending) Inputs and examplePurpose Review expenditure and verified physical progress against their separate plans. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × spending/phased budget, and verified−planned physical progress. Do not subtract LKR from physical progress, infer earned value or equate expenditure with outcomes. Checks For Laggala Pallegama — delivery performance, the default output explains Check the matching records and reasons for the difference. Changing Phased budget for the period produces Check the matching records and reasons for the difference. Missing Phased budget for the period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Phased budget for the period [LKR]; Actual spending [LKR]; Planned physical progress [%]; Independently verified physical progress [%] Result: Spending against phased budget; Verified physical progress; Verified minus planned progress (%; %; percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — delivery performance. Phased budget for the period = 1,800,000 LKR; Actual spending = 1,200,000 LKR; Planned physical progress = 60 %; Independently verified physical progress = 40 %. Results: Spending against phased budget = 66.667 %; Verified physical progress = 40 %; Verified minus planned progress = -20 percentage points. Interpretation: Spending against phased budget: 66.667 %. Next check: Check the matching records and reasons for the difference. Changed input. Change Phased budget for the period = 1,800,001. Result: Spending against phased budget = 66.667 %; Verified physical progress = 40 %; Verified minus planned progress = -20 percentage points. Interpretation: Spending against phased budget: 66.667 %. Next check: Check the matching records and reasons for the difference. Missing input. Omit Phased budget for the period. No usable result. Phased budget for the period Next check: Correct or obtain the missing input records. Information still needed: Phased budget for the period. Map context. No map inserted into this decision example Limits The percentages have different denominators; their difference is not a measure of misuse. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Proposed; awaiting scope confirmation Sri Lanka source matchLocal use · Validation required Budget utilization Budget utilization (%) = 100 × spending for the period ÷ allocation for that period. Report physical progress separately. Sector guidance · Cost Estimating and Assessment Guide GAO-20-195G Use the approved phased budget and comparable ledger period. Agree any investigation trigger in Institution review. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-003DP11 | Reporting bottlenecks Follow up source reviews needed for reports Inputs and examplePurpose Identify overdue source reviews needed for project reporting. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — reporting bottlenecks, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — reporting bottlenecks. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A reporting deadline does not establish data quality or permit release. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · FP124 Funding Proposal and project documentation Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-005DP11 | Annual planning Compare work-plan alternatives within programme constraints Inputs and examplePurpose Compare work-plan choices against commitments, resources and programme constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Complete committed activities first, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Complete committed activities first. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Focus the plan on existing commitments.; Resource needs and adverse effects = Needs confirmed obligations, dependencies, capacity and remaining funding.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Activities; costs; dependencies; outcomes; capacity; safeguards; funding ceiling. Map context. No map inserted into this decision example Limits A budget surplus does not establish deliverability or programme value. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · FP124 Funding Proposal and project documentation Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-007DP11 | Procurement scheduling Prioritize procurements on the implementation critical path (proposed; scope pending) Inputs and examplePurpose Check procurement task windows, resources and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — procurement scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — procurement scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not establish a complete project critical path or authorise procurement. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Proposed; awaiting scope confirmation Sri Lanka source matchLocal use · Validation required Procurement action schedule Use the approved procurement time schedule to check the dates and sequence of the pre-contract activities. Sector guidance · Project Submission Format Confirm the applicable edition, procurement method and approved milestones. Resource conflicts and critical-path scoring are local rules. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-008DP11 | Contract performance Escalate contract milestone delays and unresolved deliverables (proposed; scope pending) Inputs and examplePurpose Compare contract milestone dates and the evidence for outstanding deliverables. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — contract performance, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — contract performance. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits A date difference does not determine liability, penalties or contractual acceptance. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Proposed; awaiting scope confirmation International method matchSri Lanka · Validation required Compare observed progress with the schedule baseline Retain the approved baseline and compare the reported actual milestone dates with the matching planned dates. Sector guidance · Project Submission Format Confirm the baseline edition and date convention. Leave absent actual dates open. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-009DP11 | Safeguards Review environmental and social case evidence Inputs and examplePurpose Check environmental and social case evidence for responsible referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — safeguards, the default output explains Obtain the missing evidence listed below. Changing Activity scope, Activity scope evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Activity scope remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Activity scope; Activity scope evidence reference; screening; screening evidence reference; affected people; affected people evidence reference; safeguards; safeguards evidence reference; mitigations; mitigations evidence reference; reviewer; reviewer evidence reference; conditions; conditions evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — safeguards. Activity scope = Missing; Activity scope evidence reference = ; screening = Documented; screening evidence reference = Sample Laggala Pallegama field register / 2025; affected people = Documented; affected people evidence reference = Sample Laggala Pallegama field register / 2025; safeguards = Documented; safeguards evidence reference = Sample Laggala Pallegama field register / 2025; mitigations = Documented; mitigations evidence reference = Sample Laggala Pallegama field register / 2025; reviewer = Documented; reviewer evidence reference = Sample Laggala Pallegama field register / 2025; conditions = Documented; conditions evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this safeguards case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Activity scope = Documented; Activity scope evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle safeguards. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Activity scope. The required evidence is incomplete for this safeguards case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Activity scope: Missing. Map context. No map inserted into this decision example Limits A checklist does not certify safeguards or calculate a risk probability. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Review environmental alternatives or mitigation Identify potential impacts, document relevant alternatives and review the measures proposed to reduce significant impacts. Sector guidance · Environmental and Social Framework Confirm whether the EIA process applies and obtain the competent authority’s scope and conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-010DP11 | Grievances Follow up overdue programme grievances Inputs and examplePurpose Identify programme grievances whose response date has passed. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — grievances, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — grievances. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits The prototype does not send an escalation or determine the grievance outcome. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-012DP11 | Change control Compare material scope-change alternatives before approval Inputs and examplePurpose Compare a proposed scope change with the retained baseline and constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Retain the agreed baseline, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Retain the agreed baseline. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Keep the current proposed baseline unchanged.; Resource needs and adverse effects = Needs evidence that the retained plan still addresses the intended requirements.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Baseline scope; proposed change; cost; schedule; benefits; consultations; constraints. Map context. No map inserted into this decision example Limits The example neither accepts a change nor alters the agreed scope. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · FP124 Funding Proposal and project documentation Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-014DP11 | Partner coordination Resolve dependency conflicts between implementing partners Inputs and examplePurpose Check partner tasks for resource clashes and unmet predecessors. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — partner coordination, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — partner coordination. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A draft schedule does not assign work to a partner. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Project Submission Format Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-015DP11 | Outcome evaluation Assess verified programme outcomes and attribution limits Inputs and examplePurpose Compare programme outcome changes and the evidence for attribution. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — outcome evaluation, the default output explains Obtain the missing evidence listed below. Changing Intervention group households receiving the stated programme service within the same observation window before produces Obtain the missing evidence listed below. Missing Intervention group households receiving the stated programme service within the same observation window before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Intervention group households receiving the stated programme service within the same observation window before [%]; Intervention group households receiving the stated programme service within the same observation window after [%]; Comparison group households receiving the stated programme service within the same observation window before [%]; Comparison group households receiving the stated programme service within the same observation window after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — outcome evaluation. Intervention group households receiving the stated programme service within the same observation window before = 42 %; Intervention group households receiving the stated programme service within the same observation window after = 59 %; Comparison group households receiving the stated programme service within the same observation window before = 39 %; Comparison group households receiving the stated programme service within the same observation window after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Fictional measure: Households receiving the stated programme service within the same observation window / matching frame, method and before-after windows. Results: Difference in changes = 10 percentage points. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Intervention group households receiving the stated programme service within the same observation window before = 42.42. Result: Difference in changes = 9.58 percentage points. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Intervention group households receiving the stated programme service within the same observation window before. No usable result. Treatment Verified outcome indicator before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified outcome indicator before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A descriptive difference does not establish a programme effect. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP11-016DP11 | Risk financing Compare financial consequences of implementation scenarios (proposed; scope pending) Inputs and examplePurpose Compare the stated financial scenario cash flows. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Present value alone does not approve an implementation or financing choice. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Proposed; awaiting scope confirmation Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP11-018DP11 | Learning and scaling Compare piloting, expansion and redesign choices Inputs and examplePurpose Compare further piloting, expansion and redesign choices using the available evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Continue a bounded pilot, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Continue a bounded pilot. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Continue a bounded test of the intervention.; Resource needs and adverse effects = Needs a sound design, outcomes, resources and criteria for the next review.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Verified outcomes; costs; context; adverse effects; evidence quality; transferability. Map context. No map inserted into this decision example Limits A cost comparison does not establish readiness to scale. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · FP124 Funding Proposal and project documentation Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP11-019DP11 | Evidence catalogue Correct incomplete references in reporting evidence packages Inputs and examplePurpose Identify missing source references and definitions in a report package. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — evidence catalogue, the default output explains Obtain the missing evidence listed below. Changing Evidence ID, Evidence ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Evidence ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Evidence ID; Evidence ID evidence reference; source version; source version evidence reference; period; period evidence reference; geography; geography evidence reference; license; license evidence reference; reviewer; reviewer evidence reference; lineage; lineage evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — evidence catalogue. Evidence ID = Missing; Evidence ID evidence reference = ; source version = Documented; source version evidence reference = Sample Laggala Pallegama field register / 2025; period = Documented; period evidence reference = Sample Laggala Pallegama field register / 2025; geography = Documented; geography evidence reference = Sample Laggala Pallegama field register / 2025; license = Documented; license evidence reference = Sample Laggala Pallegama field register / 2025; reviewer = Documented; reviewer evidence reference = Sample Laggala Pallegama field register / 2025; lineage = Documented; lineage evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this evidence catalogue case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Evidence ID = Documented; Evidence ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle evidence catalogue. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Evidence ID. The required evidence is incomplete for this evidence catalogue case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Evidence ID: Missing. Map context. No map inserted into this decision example Limits Complete references do not verify the underlying findings. PMU monitoring lead, technical lead and finance/safeguards reviewers as relevant | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-001DP12 | Ecosystem change Compare recorded ecosystem-class changes Inputs and examplePurpose Compare dated ecosystem-class areas and the supporting condition evidence. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Net=later−earlier; percentage=100×net/earlier when earlier>0. Matched transitions must reproduce net=gain−loss. Net totals alone do not establish conversion. Checks For Laggala Pallegama — ecosystem change, the default output explains Check the matching source records before interpreting the change. Changing Later mapped class area, Matched area entering the class produces Check the matching source records before interpreting the change. Missing Earlier mapped class area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier mapped class area [ha]; Later mapped class area [ha]; Matched area leaving the class [ha]; Matched area entering the class [ha]; Same fixed analysis extent [ha]; Native class and mapping version; Earlier observation date; Later observation date Result: Net class-area change; Relative class-area change; Gross loss from class; Gross gain to class (ha; %; ha; ha) Worked example. Fictional 2025 example. Laggala Pallegama — ecosystem change. Earlier mapped class area = 100 ha; Later mapped class area = 90 ha; Matched area leaving the class = 18 ha; Matched area entering the class = 8 ha; Same fixed analysis extent = 200 ha; Native class and mapping version = Sample matching forest/land-use class; Earlier observation date = 2024-06-30; Later observation date = 2025-06-30. Results: Net class-area change = -10 ha; Relative class-area change = -10 %; Gross loss from class = 18 ha; Gross gain to class = 8 ha. Interpretation: 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 check: Check the matching source records before interpreting the change. Changed input. Change Later mapped class area = 91; Matched area entering the class = 9. Result: Net class-area change = -9 ha; Relative class-area change = -9 %; Gross loss from class = 18 ha; Gross gain to class = 9 ha. Interpretation: The recorded Sample matching forest/land-use class area changes from 100 to 91 ha. Net change is -9 ha; supplied gross loss is 18 ha and gross gain is 9 ha. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier mapped class area. No usable result. Earlier mapped class area Next check: Correct or obtain the missing input records. Information still needed: Earlier mapped class area. Map context. No map inserted into this decision example Limits Extent change alone does not measure ecosystem condition or identify its cause. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Forest transition and deforestation activity data Report forest-to-nonforest change and forest gain separately. Use reviewed area estimates and report their uncertainty. Sector guidance · SEEA Ecosystem Accounting The match covers the separate forest-loss and forest-gain check. Confirm classification compatibility, uncertainty and site-level validity before use. Implementation: prototype |
| DEC-DP12-002DP12 | Soil-carbon monitoring Compare soil-carbon monitoring records Inputs and examplePurpose Compare soil-carbon observations with matching sampling conventions. Output Comparison table Next step Prepare carbon comparison creates an unassigned draft that is visible and downloadable, not sent. Rule (Organic carbon% /100) × bulk density × depth ×10000 × (1−coarse% /100). Confirm that the density and coarse-fragment conventions are mutually consistent. Checks For Laggala Pallegama — soil-carbon monitoring, the default output explains Check sampling comparability before using the stock comparison. Changing Soil organic carbon produces Check sampling comparability before using the stock comparison. Missing Soil organic carbon remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Soil organic carbon [%]; Fine-earth bulk-density basis [t/m³]; Sample depth [m]; Coarse-fragment volume fraction [%]; Sampling depth, design and density convention Result: Soil-carbon stock (t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — soil-carbon monitoring. Soil organic carbon = 1.8 %; Fine-earth bulk-density basis = 1.25 t/m³; Sample depth = 0.3 m; Coarse-fragment volume fraction = 12 %; Sampling depth, design and density convention = Sample matched depth and fine-earth convention. Results: Soil-carbon stock = 59.4 t C/ha. Interpretation: 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 check: Check sampling comparability before using the stock comparison. Changed input. Change Soil organic carbon = 1.818. Result: Soil-carbon stock = 59.994 t C/ha. Interpretation: The supplied 1.818% carbon, 1.25 g/cm³ bulk density, 0.3 m depth and 12% coarse fragments give 59.994 t C/ha under the stated fine-earth convention. Next check: Check sampling comparability before using the stock comparison. Missing input. Omit Soil organic carbon. No usable result. Soil organic carbon Next check: Correct or obtain the missing input records. Information still needed: Soil organic carbon. Map context. No map inserted into this decision example Limits Stock differences do not establish treatment effects without comparable samples. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Soil-carbon stock with volume correction Soil-carbon stock with volume correction Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP12-003DP12 | Biodiversity evidence Check biodiversity survey effort and comparability Inputs and examplePurpose Check survey effort, protocol and coverage before comparing biodiversity observations. Output Comparison table Next step Prepare biodiversity comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred. Checks For Laggala Pallegama — biodiversity evidence, the default output explains Review survey comparability. Changing Observed distinct species produces Review survey comparability. Missing Observed distinct species remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Observed distinct species [species]; Survey effort [hours]; Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed Result: Observed richness; Recorded effort (species; hours) Worked example. Fictional 2025 example. Laggala Pallegama — biodiversity evidence. Observed distinct species = 28 species; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes. Results: Observed richness = 28 species; Recorded effort = 18 hours. Interpretation: Observed richness: 28 species. Review survey comparability. Next check: Review survey comparability. Changed input. Change Observed distinct species = 29. Result: Observed richness = 29 species; Recorded effort = 18 hours. Interpretation: Observed richness: 29 species. Review survey comparability. Next check: Review survey comparability. Missing input. Omit Observed distinct species. No usable result. Observed distinct species Next check: Correct or obtain the missing input records. Information still needed: Observed distinct species. Map context. No map inserted into this decision example Limits Observed richness can differ because effort and detection conditions differ. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check whether biological surveys are comparable Retain the survey protocol, effort and event scope when comparing observations. Confirm season, coverage, species identification and any difference in detectability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-004DP12 | Forest-carbon estimates Review evidence for forest-carbon estimates Inputs and examplePurpose Check the inventories and pool definitions supporting a forest-carbon comparison. Output Comparison table Next step Prepare carbon comparison creates an unassigned draft that is visible and downloadable, not sent. Rule (Later carbon density − earlier carbon density) × same inventory area, with identical pools, method and boundaries. Checks For Laggala Pallegama — forest-carbon estimates, the default output explains Review the matched pools, area and observation periods. Changing Earlier carbon density produces Review the matched pools, area and observation periods. Missing Earlier carbon density remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier carbon density [t C/ha]; Later carbon density [t C/ha]; Same inventory area [ha]; Included pools and allometry references Result: Carbon stock change; Carbon-density change (t C; t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — forest-carbon estimates. Earlier carbon density = 100 t C/ha; Later carbon density = 90 t C/ha; Same inventory area = 85 ha; Included pools and allometry references = Sample matching biomass pools; source model required. Results: Carbon stock change = -850 t C; Carbon-density change = -10 t C/ha. Interpretation: Carbon stock change: -850 t C. Next check: Review the matched pools, area and observation periods. Changed input. Change Earlier carbon density = 101. Result: Carbon stock change = -935 t C; Carbon-density change = -11 t C/ha. Interpretation: Carbon stock change: -935 t C. Next check: Review the matched pools, area and observation periods. Missing input. Omit Earlier carbon density. No usable result. Earlier carbon density Next check: Correct or obtain the missing input records. Information still needed: Earlier carbon density. Map context. No map inserted into this decision example Limits A stock estimate does not establish a verified emissions reduction or credit. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Carbon stock-difference component Carbon stock-difference component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP12-005DP12 | Landscape restoration Compare landscape restoration opportunities Inputs and examplePurpose Compare restoration opportunities using ecological, livelihood and rights evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Natural regeneration in degraded forest, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Natural regeneration in degraded forest. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Support recovery in the specified degraded forest.; Resource needs and adverse effects = Needs ecological suitability, regeneration sources, rights and protection.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Degradation; tenure; ecological potential; community priorities; costs; connectivity. Map context. No map inserted into this decision example Limits Expected benefits remain assumptions until supported for the site. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Forest Restoration Module Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-007DP12 | Research design Check a proposed study design Inputs and examplePurpose Check whether a study design can address its stated intervention question. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — research design, the default output explains Obtain the missing evidence listed below. Changing Hypothesis, Hypothesis evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Hypothesis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Hypothesis; Hypothesis evidence reference; treatment; treatment evidence reference; comparison; comparison evidence reference; baseline; baseline evidence reference; sample size; sample size evidence reference; confounders; confounders evidence reference; outcomes; outcomes evidence reference Result: Study evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — research design. Hypothesis = Missing; Hypothesis evidence reference = ; treatment = Documented; treatment evidence reference = Sample Laggala Pallegama field register / 2025; comparison = Documented; comparison evidence reference = Sample Laggala Pallegama field register / 2025; baseline = Documented; baseline evidence reference = Sample Laggala Pallegama field register / 2025; sample size = Documented; sample size evidence reference = Sample Laggala Pallegama field register / 2025; confounders = Documented; confounders evidence reference = Sample Laggala Pallegama field register / 2025; outcomes = Documented; outcomes evidence reference = Sample Laggala Pallegama field register / 2025. Results: Study evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this research design case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Hypothesis = Documented; Hypothesis evidence reference = DEMO-REVIEW-REFERENCE. Result: Study evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle research design. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Hypothesis. The required evidence is incomplete for this research design case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Hypothesis: Missing. Map context. No map inserted into this decision example Limits A documented design still needs appropriate specialist review. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check what a study design can support Check outcomes, comparison, baseline and follow-up evidence against the study design before attributing effects. Sector guidance · Impact Evaluation in Practice, second edition Confirm identification assumptions, population, missing follow-up and analytical limitations. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-009DP12 | Data harmonization Resolve incompatible ecological concepts before combining datasets Inputs and examplePurpose Check ecological definitions before records from different sources are combined. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — data harmonization, the default output explains Obtain the missing evidence listed below. Changing Source variables, Source variables evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source variables remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source variables; Source variables evidence reference; definitions; definitions evidence reference; units; units evidence reference; methods; methods evidence reference; taxonomic references; taxonomic references evidence reference; steward review; steward review evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — data harmonization. Source variables = Missing; Source variables evidence reference = ; definitions = Documented; definitions evidence reference = Sample Laggala Pallegama field register / 2025; units = Documented; units evidence reference = Sample Laggala Pallegama field register / 2025; methods = Documented; methods evidence reference = Sample Laggala Pallegama field register / 2025; taxonomic references = Documented; taxonomic references evidence reference = Sample Laggala Pallegama field register / 2025; steward review = Documented; steward review evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this data harmonization case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source variables = Documented; Source variables evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle data harmonization. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source variables. The required evidence is incomplete for this data harmonization case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source variables: Missing. Map context. No map inserted into this decision example Limits Similar terms do not establish equivalent concepts or compatible measurements. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · Guide for Publishing Biological Survey and Monitoring Data Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-010DP12 | Model validation Check independently reproduced model results Inputs and examplePurpose Compare an independently reproduced model result with its stated expectation. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — model validation, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [m³/season]; Independently reproduced value [m³/season]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m³/season]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (m³/season; %) Worked example. Fictional 2025 example. Laggala Pallegama — model validation. Earlier/source value = 100 m³/season; Independently reproduced value = 90 m³/season; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable m³/season measure; same input scope; Documented absolute comparison tolerance = 0.01 m³/season; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 m³/season; Relative change = -10 %. Interpretation: Difference: -10 m³/season. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 m³/season; Relative change = -10.891 %. Interpretation: Difference: -11 m³/season. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Agreement does not establish model validity or fitness for a new use. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-011DP12 | Hydrological evidence Assess whether land-management changes affect water outcomes Inputs and examplePurpose Compare water-outcome changes in managed and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — hydrological evidence, the default output explains Obtain the missing evidence listed below. Changing Treatment Seasonal streamflow volume before produces Obtain the missing evidence listed below. Missing Treatment Seasonal streamflow volume before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Seasonal streamflow volume before [m³/season]; Treatment Seasonal streamflow volume after [m³/season]; Comparison Seasonal streamflow volume before [m³/season]; Comparison Seasonal streamflow volume after [m³/season]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (m³/season) Worked example. Fictional 2025 example. Laggala Pallegama — hydrological evidence. Treatment Seasonal streamflow volume before = 42 m³/season; Treatment Seasonal streamflow volume after = 59 m³/season; Comparison Seasonal streamflow volume before = 39 m³/season; Comparison Seasonal streamflow volume after = 46 m³/season; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Seasonal streamflow volume /example matching definition1. Results: Difference in changes = 10 m³/season. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 m³/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Seasonal streamflow volume before = 42.42. Result: Difference in changes = 9.58 m³/season. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 m³/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Seasonal streamflow volume before. No usable result. Treatment Seasonal streamflow volume before Next check: Correct or obtain the missing input records. Information still needed: Treatment Seasonal streamflow volume before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits Difference in changes alone does not establish a land-management effect. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP12-012DP12 | Ecosystem services Prepare separate physical service accounts Inputs and examplePurpose Reconcile ecosystem extent separately from recorded physical service flows. Output Comparison table Next step Prepare account comparison creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — ecosystem services, the default output explains Review the extent or flow definitions and matching source records. Changing Opening ecosystem extent produces Review the extent or flow definitions and matching source records. Missing Opening ecosystem extent remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening ecosystem extent [ha]; Extent additions [ha]; Extent reductions [ha]; Measured service flow in the period [m³/year]; Service definition and flow unit; Separate monetary valuation method/price year Result: Closing ecosystem extent; Physical service flow (ha; m³/year) Worked example. Fictional 2025 example. Laggala Pallegama — ecosystem services. Opening ecosystem extent = 750 ha; Extent additions = 92 ha; Extent reductions = 48 ha; Measured service flow in the period = 120,000 m³/year; Service definition and flow unit = Fictional annual water-provisioning flow to the stated users / m³/year / same accounting boundary; Separate monetary valuation method/price year = Not provided. Results: Closing ecosystem extent = 794 ha; Physical service flow = 120,000 m³/year. Interpretation: Closing ecosystem extent: 794 ha. Next check: Review the extent or flow definitions and matching source records. Changed input. Change Opening ecosystem extent = 751. Result: Closing ecosystem extent = 795 ha; Physical service flow = 120,000 m³/year. Interpretation: Closing ecosystem extent: 795 ha. Next check: Review the extent or flow definitions and matching source records. Missing input. Omit Opening ecosystem extent. No usable result. Opening ecosystem extent Next check: Correct or obtain the missing input records. Information still needed: Opening ecosystem extent. Map context. No map inserted into this decision example Limits Extent, annual service flow and monetary value cannot be combined as one quantity. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Physical ecosystem extent account Physical ecosystem extent account Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP12-013DP12 | Trade-offs Compare livelihood conservation and water-management alternatives Inputs and examplePurpose Compare livelihood, conservation and water-management choices using their trade-offs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Agroforestry livelihood support, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Agroforestry livelihood support. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Support the proposed agroforestry livelihood activity.; Resource needs and adverse effects = Needs rights, crop/tree suitability, income evidence and maintenance resources.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Options; ecological outcomes; livelihood effects; water effects; costs; constraints. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A budget comparison does not establish the best landscape outcome. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Forest Restoration Module Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-017DP12 | Long-term monitoring Sustain observation coverage beyond initial field campaigns Inputs and examplePurpose Check repeat-observation tasks against the required windows and resources. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — long-term monitoring, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — long-term monitoring. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not secure long-term funding or guarantee observations. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Guide for Publishing Biological Survey and Monitoring Data Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-019DP12 | Knowledge products Follow up requested evidence products Inputs and examplePurpose Identify evidence-product requests whose response date has passed. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — knowledge products, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — knowledge products. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not determine scientific importance or user priority. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP12-020DP12 | Research translation Evaluate uptake and consequences of research recommendations Inputs and examplePurpose Compare recommendation uptake and outcome records. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — research translation, the default output explains Obtain the missing evidence listed below. Changing Treatment Verified recommendation uptake before produces Obtain the missing evidence listed below. Missing Treatment Verified recommendation uptake before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Verified recommendation uptake before [%]; Treatment Verified recommendation uptake after [%]; Comparison Verified recommendation uptake before [%]; Comparison Verified recommendation uptake after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (%) Worked example. Fictional 2025 example. Laggala Pallegama — research translation. Treatment Verified recommendation uptake before = 42 %; Treatment Verified recommendation uptake after = 59 %; Comparison Verified recommendation uptake before = 39 %; Comparison Verified recommendation uptake after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Verified recommendation uptake /example matching definition1. Results: Difference in changes = 10 %. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Verified recommendation uptake before = 42.42. Result: Difference in changes = 9.58 %. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Verified recommendation uptake before. No usable result. Treatment Verified recommendation uptake before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified recommendation uptake before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits Uptake and a later outcome do not establish a causal research effect. Relevant research lead, statistician and data steward | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP13-001DP13 | Field assignments Follow up assignments lacking accepted field evidence Inputs and examplePurpose Identify field assignments whose evidence or response is overdue. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — field assignments, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — field assignments. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A task record does not establish accepted completion. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · FP124 Funding Proposal and project documentation Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-003DP13 | Community cases Review overdue community cases and urgency evidence Inputs and examplePurpose Review overdue community cases alongside their documented urgency evidence. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — community cases, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — community cases. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Days overdue alone do not establish an urgency ranking. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-005DP13 | Watershed plans Compare community priorities for sub-watershed actions Inputs and examplePurpose Compare sub-watershed actions using community priorities, resources and safeguards. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Protect stream-bank vegetation, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Protect stream-bank vegetation. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Protect the stated stream-bank vegetation.; Resource needs and adverse effects = Needs the applicable boundary, rights, community agreement and maintenance.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Sites; needs; costs; water links; safeguards; community preferences; constraints. Map context. No map inserted into this decision example Limits A cost comparison does not establish community consent or a preferred action. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Community Engagement and Accountability Toolkit Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-006DP13 | Intervention scheduling Coordinate field works around seasonal and resource limits Inputs and examplePurpose Check field-work timing, resource bookings and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — intervention scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — intervention scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example schedule does not send assignments or authorise works. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-007DP13 | Restoration follow-up Target visits to restoration cohorts with uncertain survival Inputs and examplePurpose Identify original restoration cohorts with failed or unknown follow-up. Output Comparison table Next step Prepare cohort follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it. Checks For Laggala Pallegama — restoration follow-up, the default output explains Check unknown follow-up separately from confirmed survival and failure. Changing Known surviving original members, Known failed original members produces Check unknown follow-up separately from confirmed survival and failure. Missing Original cohort remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original cohort [plants]; Known surviving original members [plants]; Known failed original members [plants]; Original members with unknown follow-up [plants]; Replacements in a separate cohort [plants] Result: Confirmed survival lower bound; Survival upper bound; Unknown follow-up (%; %; plants) Worked example. Fictional 2025 example. Laggala Pallegama — restoration follow-up. Original cohort = 450 plants; Known surviving original members = 351 plants; Known failed original members = 70 plants; Original members with unknown follow-up = 29 plants; Replacements in a separate cohort = 18 plants. Results: Confirmed survival lower bound = 78 %; Survival upper bound = 84.444 %; Unknown follow-up = 29 plants. Interpretation: Confirmed survival lower bound: 78 %. Next check: Check unknown follow-up separately from confirmed survival and failure. Changed input. Change Known surviving original members = 352; Known failed original members = 69. Result: Confirmed survival lower bound = 78.222 %; Survival upper bound = 84.667 %; Unknown follow-up = 29 plants. Interpretation: Confirmed survival lower bound: 78.222 %. Next check: Check unknown follow-up separately from confirmed survival and failure. Missing input. Omit Original cohort. No usable result. Original cohort Next check: Correct or obtain the missing input records. Information still needed: Original cohort. Map context. No map inserted into this decision example Limits Unknown follow-up is not mortality; replacements remain separate. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Monitor survival after planting Check the survival of planted trees at follow-up and distinguish established trees from failed areas before considering replanting. Confirm the original cohort, replacements, missed observations and the local follow-up protocol. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-009DP13 | Water problems Review local water-shortage records Inputs and examplePurpose Compare local water requirement and supply records before a referral. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — water problems, the default output explains Check the matching records and reasons for the difference. Changing Planned value produces Check the matching records and reasons for the difference. Missing Planned value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned value [m³/day]; Observed value [m³/day] Result: Difference; Relative change (m³/day; %) Worked example. Fictional 2025 example. Laggala Pallegama — water problems. Planned value = 100 m³/day; Observed value = 90 m³/day. Results: Difference = -10 m³/day; Relative change = -10 %. Interpretation: Difference: -10 m³/day. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned value = 101. Result: Difference = -11 m³/day; Relative change = -10.891 %. Interpretation: Difference: -11 m³/day. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned value. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A shortfall does not identify its cause or establish an authorised response. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-012DP13 | Team workload Redistribute assignments where field workload exceeds capacity Inputs and examplePurpose Compare field demand with usable staff hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — team workload, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — team workload. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits A capacity gap does not appoint staff or establish travel feasibility. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-013DP13 | Safeguard conditions Check safeguards before starting field interventions Inputs and examplePurpose Identify missing safeguard evidence before field-work review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — safeguard conditions, the default output explains Obtain the missing evidence listed below. Changing Site approval, Site approval evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Site approval remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Site approval; Site approval evidence reference; consent; consent evidence reference; safeguards; safeguards evidence reference; unresolved conditions; unresolved conditions evidence reference; evidence; evidence evidence reference; responsible reviewer; responsible reviewer evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — safeguard conditions. Site approval = Missing; Site approval evidence reference = ; consent = Documented; consent evidence reference = Sample Laggala Pallegama field register / 2025; safeguards = Documented; safeguards evidence reference = Sample Laggala Pallegama field register / 2025; unresolved conditions = Documented; unresolved conditions evidence reference = Sample Laggala Pallegama field register / 2025; evidence = Documented; evidence evidence reference = Sample Laggala Pallegama field register / 2025; responsible reviewer = Documented; responsible reviewer evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this safeguard conditions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Site approval = Documented; Site approval evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle safeguard conditions. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Site approval. The required evidence is incomplete for this safeguard conditions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Site approval: Missing. Map context. No map inserted into this decision example Limits A checklist does not grant clearance or authorise starting work. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Review environmental alternatives or mitigation Identify potential impacts, document relevant alternatives and review the measures proposed to reduce significant impacts. Sector guidance · Environmental and Social Framework Confirm whether the EIA process applies and obtain the competent authority’s scope and conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-014DP13 | Equipment logistics Plan shared field equipment and supply availability Inputs and examplePurpose Compare usable field kits and commitments with the stated requirement. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — equipment logistics, the default output explains Review replenishment gap. Changing Field-instrument kits physically held produces Review replenishment gap. Missing Field-instrument kits physically held remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Field-instrument kits physically held [field-instrument kits]; Kits held for examination [field-instrument kits]; Unserviceable or retired kits; separate from held kits [field-instrument kits]; Usable kits already booked [field-instrument kits]; Additional kits required [field-instrument kits]; Supplier lead time [days]; Remaining serviceability window [days] Result: Uncommitted usable stock; Additional demand gap (field-instrument kits; field-instrument kits) Worked example. Fictional 2025 example. Laggala Pallegama — equipment logistics. Field-instrument kits physically held = 12 field-instrument kits; Kits held for examination = 1 field-instrument kits; Unserviceable or retired kits; separate from held kits = 0 field-instrument kits; Usable kits already booked = 8 field-instrument kits; Additional kits required = 5 field-instrument kits; Supplier lead time = 14 days; Remaining serviceability window = 365 days. Results: Uncommitted usable stock = 3 field-instrument kits; Additional demand gap = 2 field-instrument kits. Interpretation: Uncommitted usable stock: 3 field-instrument kits. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Field-instrument kits physically held = 13. Result: Uncommitted usable stock = 4 field-instrument kits; Additional demand gap = 1 field-instrument kits. Interpretation: Uncommitted usable stock: 4 field-instrument kits. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Field-instrument kits physically held. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Availability must match the instrument, condition and visit window. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-016DP13 | Progress exceptions Investigate deviations from agreed field work plans Inputs and examplePurpose Compare planned and recorded work packages within the same scope. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — progress exceptions, the default output explains Check the matching records and reasons for the difference. Changing Agreed conservation work packages produces Check the matching records and reasons for the difference. Missing Agreed conservation work packages remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreed conservation work packages [work packages]; Matching packages with accepted completion evidence [work packages] Result: Difference; Relative change (work packages; %) Worked example. Fictional 2025 example. Laggala Pallegama — progress exceptions. Agreed conservation work packages = 20 work packages; Matching packages with accepted completion evidence = 16 work packages. Results: Difference = -4 work packages; Relative change = -20 %. Interpretation: Difference: -4 work packages. Next check: Check the matching records and reasons for the difference. Changed input. Change Agreed conservation work packages = 21. Result: Difference = -5 work packages; Relative change = -23.81 %. Interpretation: Difference: -5 work packages. Next check: Check the matching records and reasons for the difference. Missing input. Omit Agreed conservation work packages. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A difference does not establish cause or accepted completion. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · FP124 Funding Proposal and project documentation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP13-020DP13 | Local outcomes Assess whether completed interventions improved local outcomes Inputs and examplePurpose Compare outcomes in treated and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — local outcomes, the default output explains Obtain the missing evidence listed below. Changing Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before produces Obtain the missing evidence listed below. Missing Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before [%]; Intervention group households with the stated functioning soil-and-water conservation measure at follow-up after [%]; Comparison group households with the stated functioning soil-and-water conservation measure at follow-up before [%]; Comparison group households with the stated functioning soil-and-water conservation measure at follow-up after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — local outcomes. Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before = 42 %; Intervention group households with the stated functioning soil-and-water conservation measure at follow-up after = 59 %; Comparison group households with the stated functioning soil-and-water conservation measure at follow-up before = 39 %; Comparison group households with the stated functioning soil-and-water conservation measure at follow-up after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Fictional measure: Households with the stated functioning soil-and-water conservation measure at follow-up / matching frame, method and before-after windows. Results: Difference in changes = 10 percentage points. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before = 42.42. Result: Difference in changes = 9.58 percentage points. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Intervention group households with the stated functioning soil-and-water conservation measure at follow-up before. No usable result. Treatment Verified local outcome indicator before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified local outcome indicator before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits The difference alone does not establish that the works caused an improvement. Delivery-team technical lead and community/safeguards reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP14-001DP14 | Boundary selection Select the authoritative survey edition for a case Inputs and examplePurpose Check edition, authority, scale and source evidence for a survey record. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — boundary selection, the default output explains Obtain the missing evidence listed below. Changing Boundary ID, Boundary ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Boundary ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Boundary ID; Boundary ID evidence reference; legal source; legal source evidence reference; survey date; survey date evidence reference; scale; scale evidence reference; supersession; supersession evidence reference; intended use; intended use evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — boundary selection. Boundary ID = Missing; Boundary ID evidence reference = ; legal source = Documented; legal source evidence reference = Sample Laggala Pallegama field register / 2025; survey date = Documented; survey date evidence reference = Sample Laggala Pallegama field register / 2025; scale = Documented; scale evidence reference = Sample Laggala Pallegama field register / 2025; supersession = Documented; supersession evidence reference = Sample Laggala Pallegama field register / 2025; intended use = Documented; intended use evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this boundary selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Boundary ID = Documented; Boundary ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle boundary selection. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Boundary ID. The required evidence is incomplete for this boundary selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Boundary ID: Missing. Map context. No map inserted into this decision example Limits A catalogue label alone does not establish the legally applicable survey. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Survey Act No. 17 of 2002 Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-002DP14 | Parcel reconciliation Compare registered and surveyed area records Inputs and examplePurpose Compare supplied registered and surveyed areas with matching definitions. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — parcel reconciliation, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [ha]; Independent comparison measurement [ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — parcel reconciliation. Original source measurement = 100 ha; Independent comparison measurement = 90 ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable ha measure; same input scope. Results: Difference = -10 ha; Relative change = -10 %. Interpretation: Difference: -10 ha. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 ha; Relative change = -10.891 %. Interpretation: Difference: -11 ha. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A difference does not settle a boundary or identify the correct area. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. Establish that both plans refer to the same parcel. Compare the new and previous computed areas using the Department’s permissible error and area comparison procedure for the applicable survey and boundary class. Survey Department · Departmental Survey Regulations, sixth edition. Chapter XIII, §§13.11 and 13.18–13.19. A percentage difference is a screening result. Have the surveyor confirm the boundary type, survey class and permissible error before correcting the record. Calculation reference. International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Survey Act No. 17 of 2002 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-003DP14 | Terrain screening Check terrain evidence before site survey Inputs and examplePurpose Check reported terrain overlap and source evidence before detailed site survey. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — terrain screening, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — terrain screening. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not process terrain or select a safe development site. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-005DP14 | Cadastral backlog Follow up pending cadastral survey requests Inputs and examplePurpose Identify cadastral survey requests past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — cadastral backlog, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — cadastral backlog. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Days overdue do not establish a legally adopted survey priority. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Departmental Survey Regulations, sixth edition Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-006DP14 | Control network Schedule geodetic control inspection and restoration Inputs and examplePurpose Identify geodetic-control inspection or restoration cases needing follow-up. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — control network, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — control network. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish control-point accuracy or safety. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · National Standard for Spatial Data Accuracy Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-007DP14 | Coordinate transformation Review supplied coordinate-check residuals Inputs and examplePurpose Compare supplied expected and independently reproduced control residuals. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — coordinate transformation, the default output explains Investigate reproduction difference. Changing Supplied expected control residual produces Difference within supplied tolerance. Missing Supplied expected control residual remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Supplied expected control residual [m]; Supplied independently reproduced residual [m]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (m; %) Worked example. Fictional 2025 example. Laggala Pallegama — coordinate transformation. Supplied expected control residual = 0.12 m; Supplied independently reproduced residual = 0.13 m; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable m measure; same input scope; Documented absolute comparison tolerance = 0.01 m; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = 0.01 m; Relative change = 8.333 %. Interpretation: Difference: 0.01 m. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Supplied expected control residual = 0.13. Result: Difference = 0 m; Relative change = 0 %. Interpretation: Difference: 0 m. Difference within supplied tolerance. Next check: Difference within supplied tolerance. Missing input. Omit Supplied expected control residual. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The page does not execute a coordinate transformation or establish its fitness. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare spatial positions against independent control Compare the same locations against independently checked positions of higher accuracy, with consistent coordinate reference information. Confirm the governing Sri Lankan survey tolerance, datum and applicability to the geometry. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-009DP14 | Aerial acquisition Schedule aerial imagery for priority mapping gaps Inputs and examplePurpose Check imagery-task windows, resources, access and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — aerial acquisition, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — aerial acquisition. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The schedule does not arrange a flight or authorise image acquisition. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-013DP14 | Elevation products Select elevation datasets fit for intended analysis Inputs and examplePurpose Check elevation-data resolution, datum, source and quality for the intended use. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — elevation products, the default output explains Obtain the missing evidence listed below. Changing Resolution, Resolution evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Resolution remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Resolution; Resolution evidence reference; vertical datum; vertical datum evidence reference; accuracy; accuracy evidence reference; acquisition date; acquisition date evidence reference; coverage; coverage evidence reference; intended scale; intended scale evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — elevation products. Resolution = Missing; Resolution evidence reference = ; vertical datum = Documented; vertical datum evidence reference = Sample Laggala Pallegama field register / 2025; accuracy = Documented; accuracy evidence reference = Sample Laggala Pallegama field register / 2025; acquisition date = Documented; acquisition date evidence reference = Sample Laggala Pallegama field register / 2025; coverage = Documented; coverage evidence reference = Sample Laggala Pallegama field register / 2025; intended scale = Documented; intended scale evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this elevation products case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Resolution = Documented; Resolution evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle elevation products. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Resolution. The required evidence is incomplete for this elevation products case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Resolution: Missing. Map context. No map inserted into this decision example Limits Complete metadata do not establish fitness for a specific analysis. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-015DP14 | Survey resources Balance crew instrument and travel requirements Inputs and examplePurpose Compare survey workload with usable crew and instrument capacity. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — survey resources, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [crew days]; Rated capacity for that period [crew days]; Unavailable or restricted capacity [crew days] Result: Usable capacity minus demand; Usable capacity (crew days; crew days) Worked example. Fictional 2025 example. Laggala Pallegama — survey resources. Demand in the selected period = 150 crew days; Rated capacity for that period = 180 crew days; Unavailable or restricted capacity = 45 crew days. Results: Usable capacity minus demand = -15 crew days; Usable capacity = 135 crew days. Interpretation: Usable capacity minus demand: -15 crew days. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 crew days; Usable capacity = 135 crew days. Interpretation: Usable capacity minus demand: -16 crew days. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish skills, access or appointment authority. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-018DP14 | Survey cost Compare costs for equivalent survey work types Inputs and examplePurpose Compare costs for a defined equivalent survey work unit. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Sum non-overlapping survey costs and divide by verified kilometres of the same survey work/terrain class. This does not compare unlike cadastral cases by an undefined survey count. Checks For Laggala Pallegama — survey cost, the default output explains Review cost components and comparable verified outputs. Changing Labour cost produces Review cost components and comparable verified outputs. Missing Labour cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Kilometres of the same stated survey work class [km surveyed]; Equivalent survey work/terrain class Result: Cost per matching unit; Total cost (LKR/km surveyed; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — survey cost. Labour cost = 180,000 LKR; Material/input cost = 255,000 LKR; Other non-overlapping cost = 62,000 LKR; Kilometres of the same stated survey work class = 5.4 km surveyed; Equivalent survey work/terrain class = Fictional boundary-line survey / comparable terrain and specification. Results: Cost per matching unit = 92,037.037 LKR/km surveyed; Total cost = 497,000 LKR. Interpretation: The supplied costs total 497,000 LKR for 5.4 km surveyed. Cost per matching unit is 92,037.037 LKR/km surveyed. Next check: Review cost components and comparable verified outputs. Changed input. Change Labour cost = 180,001. Result: Cost per matching unit = 92,037.222 LKR/km surveyed; Total cost = 497,001 LKR. Interpretation: The supplied costs total 497,001 LKR for 5.4 km surveyed. Cost per matching unit is 92,037.222 LKR/km surveyed. Next check: Review cost components and comparable verified outputs. Missing input. Omit Labour cost. No usable result. Labour cost Next check: Correct or obtain the missing input records. Information still needed: Labour cost. Map context. No map inserted into this decision example Limits Lowest unit cost does not establish equivalent accuracy or deliverables. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Identify the official survey estimate basis Use the official chargeable-survey estimate and applicable Surveyor General circular for the work type. Obtain the current circular and compare rates only across equivalent jobs, terrain and quantities. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-019DP14 | Map distribution Clear delayed requests for permitted map products Inputs and examplePurpose Identify permitted map-product requests past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — map distribution, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — map distribution. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A deadline does not override source rights or disclosure restrictions. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP14-020DP14 | Historical integrity Retain superseded survey editions with traceable revisions Inputs and examplePurpose Check edition and revision references when a survey is superseded. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — historical integrity, the default output explains Obtain the missing evidence listed below. Changing Current survey edition, Current survey edition evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Current survey edition remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Current survey edition; Current survey edition evidence reference; Superseded edition references; Superseded edition references evidence reference; Revision reason and effective version; Revision reason and effective version evidence reference; Preserved original location; Preserved original location evidence reference; Change history; Change history evidence reference; Retention and access rules; Retention and access rules evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — historical integrity. Current survey edition = Missing; Current survey edition evidence reference = ; Superseded edition references = Documented; Superseded edition references evidence reference = Sample Laggala Pallegama field register / 2025; Revision reason and effective version = Documented; Revision reason and effective version evidence reference = Sample Laggala Pallegama field register / 2025; Preserved original location = Documented; Preserved original location evidence reference = Sample Laggala Pallegama field register / 2025; Change history = Documented; Change history evidence reference = Sample Laggala Pallegama field register / 2025; Retention and access rules = Documented; Retention and access rules evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this historical integrity case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Current survey edition = Documented; Current survey edition evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle historical integrity. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Current survey edition. The required evidence is incomplete for this historical integrity case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Current survey edition: Missing. Map context. No map inserted into this decision example Limits Old evidence must remain traceable; no authoritative edition is replaced here. Authorized survey professional and geospatial quality reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Data Catalog Vocabulary Version 3 Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-001DP15 | Published services Review reported geospatial-service interruptions Inputs and examplePurpose Review reported geospatial-service outages against user requirements. Output Comparison table Next step Prepare service review creates an unassigned draft that is visible and downloadable, not sent. Rule Time availability =100 ×(scheduled−non-overlapping outage)/scheduled. Request success =100 ×(requests−failed)/requests. Response time is a separate measure. Checks For Laggala Pallegama — published services, the default output explains Check recorded outages, failed requests and the agreed service conditions. Changing Scheduled observation window produces Check recorded outages, failed requests and the agreed service conditions. Missing Scheduled observation window remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Scheduled observation window [hours]; Union of qualifying outage intervals [hours]; Eligible service requests [requests]; Failed eligible requests [requests]; Measured response time [ms] Result: Time availability; Request success; Measured response time (%; %; ms) Worked example. Fictional 2025 example. Laggala Pallegama — published services. Scheduled observation window = 168 hours; Union of qualifying outage intervals = 13 hours; Eligible service requests = 1,000 requests; Failed eligible requests = 40 requests; Measured response time = 800 ms. Results: Time availability = 92.262 %; Request success = 96 %; Measured response time = 800 ms. Interpretation: Time availability: 92.262 %. Next check: Check recorded outages, failed requests and the agreed service conditions. Changed input. Change Scheduled observation window = 169. Result: Time availability = 92.308 %; Request success = 96 %; Measured response time = 800 ms. Interpretation: Time availability: 92.308 %. Next check: Check recorded outages, failed requests and the agreed service conditions. Missing input. Omit Scheduled observation window. No usable result. Scheduled observation window Next check: Correct or obtain the missing input records. Information still needed: Scheduled observation window. Map context. No map inserted into this decision example Limits The page does not call live services or establish overall service fitness. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Time-availability arithmetic 100 × (service-window time − qualifying outage time) ÷ service-window time. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-003DP15 | Semantic conflicts Resolve conflicting classifications between publishers Inputs and examplePurpose Check classification definitions from different publishers. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — semantic conflicts, the default output explains Obtain the missing evidence listed below. Changing Source class, Source class evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source class remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source class; Source class evidence reference; definition; definition evidence reference; units; units evidence reference; reference vocabulary; reference vocabulary evidence reference; mapping evidence; mapping evidence evidence reference; steward; steward evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — semantic conflicts. Source class = Missing; Source class evidence reference = ; definition = Documented; definition evidence reference = Sample Laggala Pallegama field register / 2025; units = Documented; units evidence reference = Sample Laggala Pallegama field register / 2025; reference vocabulary = Documented; reference vocabulary evidence reference = Sample Laggala Pallegama field register / 2025; mapping evidence = Documented; mapping evidence evidence reference = Sample Laggala Pallegama field register / 2025; steward = Documented; steward evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this semantic conflicts case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source class = Documented; Source class evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle semantic conflicts. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source class. The required evidence is incomplete for this semantic conflicts case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source class: Missing. Map context. No map inserted into this decision example Limits Matching labels do not establish compatible source meanings. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-006DP15 | Coordinate standards Review supplied transformation-check results Inputs and examplePurpose Compare supplied transformation-check results and their exact input versions. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — coordinate standards, the default output explains Investigate reproduction difference. Changing Supplied expected transformation residual produces Difference within supplied tolerance. Missing Supplied expected transformation residual remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Supplied expected transformation residual [m]; Supplied independent control residual [m]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [m]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (m; %) Worked example. Fictional 2025 example. Laggala Pallegama — coordinate standards. Supplied expected transformation residual = 0.12 m; Supplied independent control residual = 0.13 m; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable m measure; same input scope; Documented absolute comparison tolerance = 0.01 m; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = 0.01 m; Relative change = 8.333 %. Interpretation: Difference: 0.01 m. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Supplied expected transformation residual = 0.13. Result: Difference = 0 m; Relative change = 0 %. Interpretation: Difference: 0 m. Difference within supplied tolerance. Next check: Difference within supplied tolerance. Missing input. Omit Supplied expected transformation residual. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not execute a transformation or validate a service. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare spatial positions against independent control Compare the same locations against independently checked positions of higher accuracy, with consistent coordinate reference information. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the governing Sri Lankan survey tolerance, datum and applicability to the geometry. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-010DP15 | Schema changes Review source-schema changes Inputs and examplePurpose Compare schema definitions and versions before reviewing downstream effects. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — schema changes, the default output explains Resolve source disagreement. Changing Do the two source records have documented matching meanings? produces Refer documented equivalence. Missing Original source value/definition remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source value/definition; Comparison source value/definition; Original version; Comparison version; Do the two source records have documented matching meanings? Result: Source comparisons needing review (items) Worked example. Fictional 2025 example. Laggala Pallegama — schema changes. Original source value/definition = Schema versions: primary register entry; Comparison source value/definition = Schema versions: conflicting source return; Original version = Sample version1; Comparison version = Sample version2; Do the two source records have documented matching meanings? = Unresolved. Results: Source comparisons needing review = 1 items. Interpretation: The original record says “Schema versions: primary register entry”; the comparison says “Schema versions: conflicting source return”. Their matching meaning has not been established. Obtain the source definitions and supporting records before reconciling them. Next check: Resolve source disagreement. Changed input. Change Do the two source records have documented matching meanings? = Documented. Result: Source comparisons needing review = 0 items. Interpretation: The original record says “Schema versions: primary register entry”; the comparison says “Schema versions: conflicting source return”. The example marks their meanings as matching. Check the supporting definitions and comparison basis before any record correction. Next check: Refer documented equivalence. Missing input. Omit Original source value/definition. The original record says “Not provided”; the comparison says “Schema versions: conflicting source return”. The example marks their meanings as matching. Check the supporting definitions and comparison basis before any record correction. Next check: Correct or obtain the missing input records. Information still needed: Original source value/definition. Map context. No map inserted into this decision example Limits A version difference alone does not identify every affected consumer. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-011DP15 | Data lineage Identify products lacking traceable source versions Inputs and examplePurpose Identify products missing original source and version references. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — data lineage, the default output explains Obtain the missing evidence listed below. Changing Product ID, Product ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Product ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Product ID; Product ID evidence reference; source IDs; source IDs evidence reference; transformations; transformations evidence reference; edition dates; edition dates evidence reference; permissions; permissions evidence reference; hashes; hashes evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — data lineage. Product ID = Missing; Product ID evidence reference = ; source IDs = Documented; source IDs evidence reference = Sample Laggala Pallegama field register / 2025; transformations = Documented; transformations evidence reference = Sample Laggala Pallegama field register / 2025; edition dates = Documented; edition dates evidence reference = Sample Laggala Pallegama field register / 2025; permissions = Documented; permissions evidence reference = Sample Laggala Pallegama field register / 2025; hashes = Documented; hashes evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this data lineage case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Product ID = Documented; Product ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle data lineage. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Product ID. The required evidence is incomplete for this data lineage case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Product ID: Missing. Map context. No map inserted into this decision example Limits A complete lineage record does not verify the original data. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Data Catalog Vocabulary Version 3 Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-015DP15 | Incident response Assign source-feed failures to accountable custodians Inputs and examplePurpose Identify source-feed failure cases whose response is overdue. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — incident response, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — incident response. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A proposed custodian is not an assigned incident owner. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-016DP15 | Update scheduling Coordinate shared-layer refreshes with consumers Inputs and examplePurpose Check source-refresh windows and dependencies with consumers. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — update scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — update scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not refresh a service or notify consumers. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-017DP15 | Catalogue discovery Improve discovery of poorly described geospatial resources Inputs and examplePurpose Find missing descriptions, keywords and ownership references. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — catalogue discovery, the default output explains Obtain the missing evidence listed below. Changing Dataset title, Dataset title evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Dataset title remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Dataset title; Dataset title evidence reference; keywords; keywords evidence reference; geography; geography evidence reference; period; period evidence reference; entity definition; entity definition evidence reference; source owner; source owner evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — catalogue discovery. Dataset title = Missing; Dataset title evidence reference = ; keywords = Documented; keywords evidence reference = Sample Laggala Pallegama field register / 2025; geography = Documented; geography evidence reference = Sample Laggala Pallegama field register / 2025; period = Documented; period evidence reference = Sample Laggala Pallegama field register / 2025; entity definition = Documented; entity definition evidence reference = Sample Laggala Pallegama field register / 2025; source owner = Documented; source owner evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this catalogue discovery case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Dataset title = Documented; Dataset title evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle catalogue discovery. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Dataset title. The required evidence is incomplete for this catalogue discovery case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Dataset title: Missing. Map context. No map inserted into this decision example Limits Better metadata do not establish source quality or sharing rights. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Metadata discovery check Review whether the metadata is enough to discover the data, judge its suitability and find the route to access it. Sector guidance · Data Catalog Vocabulary Version 3 Confirm the current NSDI profile and exact mandatory fields before setting validation rules. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP15-019DP15 | Usage requests Prioritize dataset requests using recorded service demand Inputs and examplePurpose Identify dataset requests past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — usage requests, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — usage requests. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish public importance or a service priority. Geospatial custodian, metadata steward and access/security reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-002DP16 | Damage and loss Direct sector assessments where losses are greatest Inputs and examplePurpose Compare recorded asset damage and interruption losses for the same event. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Asset quantity × replacement/repair unit cost. Show interrupted economic flows separately; no automatic damage+flow total or double counting. Checks For Laggala Pallegama — damage and loss, the default output explains Review cost components and comparable verified outputs. Changing Damaged asset quantity produces Review cost components and comparable verified outputs. Missing Damaged asset quantity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Damaged asset quantity [asset units]; Repair/replacement cost per matching unit [LKR/unit]; Interrupted service/production flow value [LKR/period]; Price year and flow interruption period Result: Estimated asset damage; Interrupted flow value (LKR; LKR/period) Worked example. Fictional 2025 example. Laggala Pallegama — damage and loss. Damaged asset quantity = 12 asset units; Repair/replacement cost per matching unit = 150,000 LKR/unit; Interrupted service/production flow value = 250,000 LKR/period; Price year and flow interruption period = Sample2025 prices / stated interruption period. Results: Estimated asset damage = 1,800,000 LKR; Interrupted flow value = 250,000 LKR/period. Interpretation: Estimated asset damage: 1,800,000 LKR. Next check: Review cost components and comparable verified outputs. Changed input. Change Damaged asset quantity = 13. Result: Estimated asset damage = 1,950,000 LKR; Interrupted flow value = 250,000 LKR/period. Interpretation: Estimated asset damage: 1,950,000 LKR. Next check: Review cost components and comparable verified outputs. Missing input. Omit Damaged asset quantity. No usable result. Damaged asset quantity Next check: Correct or obtain the missing input records. Information still needed: Damaged asset quantity. Map context. No map inserted into this decision example Limits Stocks damaged and flows interrupted must not be added without compatible valuation rules. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Repair and replacement cost basis The Sri Lanka assessment uses pre-disaster repair or replacement costs for affected assets and reports economic losses separately. Multiply affected quantities by the applicable repair or replacement unit cost by damage class. Sector guidance · Conducting Damage and Loss Assessments after Disasters, volume 2 Confirm verified quantities, asset class, damage grade and the applicable Sri Lankan unit costs. Recovery premiums need separate evidence. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-005DP16 | Warning dissemination Identify communities missing authorized warnings Inputs and examplePurpose Identify communities with no confirmed receipt of an authorised warning. Output Comparison table Next step Prepare coverage follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown. Checks For Laggala Pallegama — warning dissemination, the default output explains Check the records behind the uncovered and unknown groups. Changing Required eligible frame produces Check the records behind the uncovered and unknown groups. Missing Required eligible frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required eligible frame [households]; Distinct members of that frame covered [households]; Frame members with unknown coverage [households] Result: Verified coverage; Known uncovered; Unknown coverage (%; households; households) Worked example. Fictional 2025 example. Laggala Pallegama — warning dissemination. Required eligible frame = 100 households; Distinct members of that frame covered = 65 households; Frame members with unknown coverage = 5 households. Results: Verified coverage = 65 %; Known uncovered = 30 households; Unknown coverage = 5 households. Interpretation: 30 households are known to be uncovered; 5 have unknown coverage. 65% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Changed input. Change Required eligible frame = 101. Result: Verified coverage = 64.356 %; Known uncovered = 31 households; Unknown coverage = 5 households. Interpretation: 31 households are known to be uncovered; 5 have unknown coverage. 64.356% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Missing input. Omit Required eligible frame. No usable result. Required eligible frame Next check: Correct or obtain the missing input records. Information still needed: Required eligible frame. Map context. No map inserted into this decision example Limits Recorded dissemination is not proof that people received or understood the warning. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check warning authority and dissemination Use the warning from the responsible technical agency and follow the documented dissemination arrangements. Sector guidance · Sendai Framework Monitor Methodology Confirm event, issue time, target area, receipt evidence and assigned responsibilities. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-007DP16 | Emergency resources Allocate response resources against assessed needs Inputs and examplePurpose Compare usable response resources with the stated event workload. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — emergency resources, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — emergency resources. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Resource counts alone do not establish skills, deployment authority or readiness. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · National Emergency Operational Plan Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-009DP16 | Relief stocks Prevent critical shortages in emergency stores Inputs and examplePurpose Check usable emergency stocks against commitments and expected receipts. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — relief stocks, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [packs]; Quarantined stock [packs]; Expired stock [packs]; Committed usable stock [packs]; Additional demand [packs]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (packs; packs) Worked example. Fictional 2025 example. Laggala Pallegama — relief stocks. Physical stock = 1,200 packs; Quarantined stock = 100 packs; Expired stock = 50 packs; Committed usable stock = 740 packs; Additional demand = 500 packs; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 packs; Additional demand gap = 190 packs. Interpretation: Uncommitted usable stock: 310 packs. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 packs; Additional demand gap = 189 packs. Interpretation: Uncommitted usable stock: 311 packs. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Stock totals do not establish item condition, suitability or a reliable delivery date. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-010DP16 | Preparedness drills Resolve failures identified during preparedness exercises Inputs and examplePurpose Find missing evidence from a response exercise. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — preparedness drills, the default output explains Obtain the missing evidence listed below. Changing Exercise scenario, Exercise scenario evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Exercise scenario remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Exercise scenario; Exercise scenario evidence reference; required actions; required actions evidence reference; response times; response times evidence reference; observed failures; observed failures evidence reference; corrective owner; corrective owner evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — preparedness drills. Exercise scenario = Missing; Exercise scenario evidence reference = ; required actions = Documented; required actions evidence reference = Sample Laggala Pallegama field register / 2025; response times = Documented; response times evidence reference = Sample Laggala Pallegama field register / 2025; observed failures = Documented; observed failures evidence reference = Sample Laggala Pallegama field register / 2025; corrective owner = Documented; corrective owner evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this preparedness drills case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Exercise scenario = Documented; Exercise scenario evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle preparedness drills. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Exercise scenario. The required evidence is incomplete for this preparedness drills case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Exercise scenario: Missing. Map context. No map inserted into this decision example Limits A documented exercise does not establish readiness for every emergency. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check emergency readiness and assigned responsibilities Check the documented preparedness arrangements, responsible organizations and available support for the affected area. Confirm the current plan, resource readiness, access restrictions and the person responsible for follow-up. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-011DP16 | Risk reduction Compare mitigation proposals for exposed communities Inputs and examplePurpose Compare mitigation choices using site evidence, benefits, constraints and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Improve warning dissemination, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Improve warning dissemination. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve receipt of authorised warnings.; Resource needs and adverse effects = Needs audience, channel, accessibility and response evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Hazards; exposure; vulnerability; mitigation options; costs; feasibility; safeguards. Map context. No map inserted into this decision example Limits Cost alone does not select an effective mitigation measure. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-014DP16 | Response coordination Resolve incompatible assignments across response agencies Inputs and examplePurpose Check inter-agency task dates, capacity and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — response coordination, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — response coordination. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A feasible example schedule does not notify or assign responders. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · National Emergency Operational Plan Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-015DP16 | Recovery progress Escalate delayed reconstruction and rehabilitation work Inputs and examplePurpose Identify recovery milestones with missing or late completion evidence. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — recovery progress, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — recovery progress. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits A missed milestone does not establish its cause or justify a funding decision. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare observed progress with the schedule baseline Retain the approved baseline and compare the reported actual milestone dates with the matching planned dates. Confirm the baseline edition and date convention. Leave absent actual dates open. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-016DP16 | Impact trends Review changing disaster impacts across comparable events Inputs and examplePurpose Review recorded disaster impacts over the available comparable years. Output Time-series chart and observation table Next step Prepare trend report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — impact trends, the default output explains Check source and period comparability before using the trend. Changing Comparable observation produces Check source and period comparability before using the trend. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [affected households per 1000 exposed] Result: Observed value (affected households per 1000 exposed) Worked example. Fictional 2025 example. Laggala Pallegama — impact trends. Comparable observation = 104 affected households per 1000 exposed. Results: Observed value = 104 affected households per 1000 exposed. Interpretation: Observed value: 104 affected households per 1000 exposed. Next check: Check source and period comparability before using the trend. Changed input. Change Comparable observation = 105. Result: Observed value = 105 affected households per 1000 exposed. Interpretation: Observed value: 105 affected households per 1000 exposed. Next check: Check source and period comparability before using the trend. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7 Map context. No map inserted into this decision example Limits A short example series does not establish a trend in hazard probability. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP16-017DP16 | Contingency plans Check whether local contingency plans remain usable Inputs and examplePurpose Find missing responsibilities and evidence in a contingency-plan review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — contingency plans, the default output explains Obtain the missing evidence listed below. Changing Plan edition, Plan edition evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Plan edition remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Plan edition; Plan edition evidence reference; hazard scenarios; hazard scenarios evidence reference; contacts; contacts evidence reference; resources; resources evidence reference; drills; drills evidence reference; approval dates; approval dates evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — contingency plans. Plan edition = Missing; Plan edition evidence reference = ; hazard scenarios = Documented; hazard scenarios evidence reference = Sample Laggala Pallegama field register / 2025; contacts = Documented; contacts evidence reference = Sample Laggala Pallegama field register / 2025; resources = Documented; resources evidence reference = Sample Laggala Pallegama field register / 2025; drills = Documented; drills evidence reference = Sample Laggala Pallegama field register / 2025; approval dates = Documented; approval dates evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this contingency plans case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Plan edition = Documented; Plan edition evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle contingency plans. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Plan edition. The required evidence is incomplete for this contingency plans case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Plan edition: Missing. Map context. No map inserted into this decision example Limits Checklist completeness does not establish operational readiness. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check emergency readiness and assigned responsibilities Check the documented preparedness arrangements, responsible organizations and available support for the affected area. Confirm the current plan, resource readiness, access restrictions and the person responsible for follow-up. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-018DP16 | Public information Verify authority and validity before publishing alerts Inputs and examplePurpose Check the source, issuer and audience conditions before a warning-publication referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — public information, the default output explains Obtain the missing evidence listed below. Changing Issuing authority, Issuing authority evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Issuing authority remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Issuing authority; Issuing authority evidence reference; warning version; warning version evidence reference; affected area; affected area evidence reference; expiry; expiry evidence reference; publication approval; publication approval evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — public information. Issuing authority = Missing; Issuing authority evidence reference = ; warning version = Documented; warning version evidence reference = Sample Laggala Pallegama field register / 2025; affected area = Documented; affected area evidence reference = Sample Laggala Pallegama field register / 2025; expiry = Documented; expiry evidence reference = Sample Laggala Pallegama field register / 2025; publication approval = Documented; publication approval evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this public information case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Issuing authority = Documented; Issuing authority evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle public information. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Issuing authority. The required evidence is incomplete for this public information case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Issuing authority: Missing. Map context. No map inserted into this decision example Limits The example does not authorise, publish or send a warning. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check warning authority and dissemination Use the warning from the responsible technical agency and follow the documented dissemination arrangements. Sector guidance · Common Alerting Protocol Confirm event, issue time, target area, receipt evidence and assigned responsibilities. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP16-019DP16 | Response evaluation Assess response effectiveness and unintended consequences Inputs and examplePurpose Compare response outcomes across the supplied treatment and comparison periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — response evaluation, the default output explains Obtain the missing evidence listed below. Changing Treatment Verified response completion before produces Obtain the missing evidence listed below. Missing Treatment Verified response completion before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Verified response completion before [%]; Treatment Verified response completion after [%]; Comparison Verified response completion before [%]; Comparison Verified response completion after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (%) Worked example. Fictional 2025 example. Laggala Pallegama — response evaluation. Treatment Verified response completion before = 42 %; Treatment Verified response completion after = 59 %; Comparison Verified response completion before = 39 %; Comparison Verified response completion after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Verified response completion /example matching definition1. Results: Difference in changes = 10 %. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Verified response completion before = 42.42. Result: Difference in changes = 9.58 %. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Verified response completion before. No usable result. Treatment Verified response completion before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified response completion before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits Differences in changes do not establish a causal response effect. Disaster operations coordinator and relevant hazard/relief specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP17-001DP17 | Site clearance Refer proposed sites overlapping landslide hazard zones Inputs and examplePurpose Check reported development overlap with a cited landslide-hazard zone. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — site clearance, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — site clearance. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A reported overlap supports referral; it does not establish site safety or permission. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Landslide Clearance for Construction in Landslide Prone Areas Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-002DP17 | Hazard-map updates Prioritize zones with outdated or incomplete hazard evidence Inputs and examplePurpose Find missing edition, scale and classification details in a hazard layer. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — hazard-map updates, the default output explains Obtain the missing evidence listed below. Changing Map coverage, Map coverage evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Map coverage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Map coverage; Map coverage evidence reference; edition date; edition date evidence reference; new incidents; new incidents evidence reference; terrain changes; terrain changes evidence reference; survey need; survey need evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — hazard-map updates. Map coverage = Missing; Map coverage evidence reference = ; edition date = Documented; edition date evidence reference = Sample Laggala Pallegama field register / 2025; new incidents = Documented; new incidents evidence reference = Sample Laggala Pallegama field register / 2025; terrain changes = Documented; terrain changes evidence reference = Sample Laggala Pallegama field register / 2025; survey need = Documented; survey need evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this hazard-map updates case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Map coverage = Documented; Map coverage evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle hazard-map updates. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Map coverage. The required evidence is incomplete for this hazard-map updates case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Map coverage: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Complete metadata do not establish fitness for a particular engineering design. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · Landslide Clearance for Construction in Landslide Prone Areas Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-004DP17 | Rainfall investigations Investigate rainfall patterns associated with landslides Inputs and examplePurpose Review rainfall observations and their reference periods for specialist interpretation. Output Time-series chart and observation table Next step Prepare trend report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — rainfall investigations, the default output explains Check source and period comparability before using the trend. Changing Comparable observation produces Check source and period comparability before using the trend. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [mm] Result: Observed value (mm) Worked example. Fictional 2025 example. Laggala Pallegama — rainfall investigations. Comparable observation = 104 mm. Results: Observed value = 104 mm. Interpretation: Observed value: 104 mm. Next check: Check source and period comparability before using the trend. Changed input. Change Comparable observation = 105. Result: Observed value = 105 mm. Interpretation: Observed value: 105 mm. Next check: Check source and period comparability before using the trend. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7 Map context. No map inserted into this decision example Limits A rainfall pattern alone does not supply an authorised warning trigger. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. Match a landslide record to the relevant rain-gauge history and compare accumulated rainfall by event and divisional area. Treat the published Kalutara results as study findings for those areas. National Building Research Organisation · Study of effective rainfall thresholds for landslide initiation in Kalutara. Abstract and study method, rain-gauge and landslide event records. Have NBRO confirm the appropriate observation window and station coverage for the area under review. Calculation reference. International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP17-007DP17 | Slope stabilization Compare engineering mitigation alternatives Inputs and examplePurpose Compare stabilisation choices using the investigation evidence and site constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Engineered surface drainage, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Engineered surface drainage. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Manage the documented surface runoff.; Resource needs and adverse effects = Needs an engineered drainage design, outfall checks and upkeep.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Site investigation; failure mechanism; designs; costs; land access; maintenance. Map context. No map inserted into this decision example Limits Budget and descriptive benefits cannot determine a safe engineering design. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · The Landslide Handbook, Circular 1325 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-010DP17 | Geotechnical evidence Resolve conflicting ground-investigation results Inputs and examplePurpose Compare supplied ground-investigation results and their matching definitions. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — geotechnical evidence, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [mm]; Independent comparison measurement [mm]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (mm; %) Worked example. Fictional 2025 example. Laggala Pallegama — geotechnical evidence. Original source measurement = 100 mm; Independent comparison measurement = 90 mm; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable mm measure; same input scope. Results: Difference = -10 mm; Relative change = -10 %. Interpretation: Difference: -10 mm. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 mm; Relative change = -10.891 %. Interpretation: Difference: -11 mm. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits Differences require source and site checks before an engineering interpretation. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-011DP17 | Early warning evidence Prepare technical review of landslide-warning conditions Inputs and examplePurpose Check rainfall, movement and observation conditions before an authorised warning review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — early warning evidence, the default output explains Obtain the missing evidence listed below. Changing Rainfall, Rainfall evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Rainfall remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall; Rainfall evidence reference; soil moisture; soil moisture evidence reference; movement; movement evidence reference; approved thresholds; approved thresholds evidence reference; forecast; forecast evidence reference; duty authority; duty authority evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — early warning evidence. Rainfall = Missing; Rainfall evidence reference = ; soil moisture = Documented; soil moisture evidence reference = Sample Laggala Pallegama field register / 2025; movement = Documented; movement evidence reference = Sample Laggala Pallegama field register / 2025; approved thresholds = Documented; approved thresholds evidence reference = Sample Laggala Pallegama field register / 2025; forecast = Documented; forecast evidence reference = Sample Laggala Pallegama field register / 2025; duty authority = Documented; duty authority evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this early warning evidence case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Rainfall = Documented; Rainfall evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle early warning evidence. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Rainfall. The required evidence is incomplete for this early warning evidence case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Rainfall: Missing. Map context. No map inserted into this decision example Limits A checklist is not a warning threshold or a publication authority. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Evidence used for landslide warning review Check the relevant 24-hour rainfall evidence and soil-water status against the archived NBRO warning and its stated criteria. Sector guidance · The Landslide Handbook, Circular 1325 The case-study thresholds are historical. Obtain the current NBRO bulletin and applicable area. The prototype may only prepare a review case. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-012DP17 | Laboratory workload Prioritize delayed geotechnical testing requests Inputs and examplePurpose Identify tests and inspections whose recorded response is overdue. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — laboratory workload, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — laboratory workload. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Age alone does not establish engineering urgency or a safe operating condition. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Landslide Clearance for Construction in Landslide Prone Areas Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-014DP17 | Post-event inspection Schedule investigations after reported slope failures Inputs and examplePurpose Check post-failure assessment tasks against resources and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — post-event inspection, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — post-event inspection. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not assign investigators or permit access to a hazardous site. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · The Landslide Handbook, Circular 1325 Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-015DP17 | Drainage remediation Compare options to reduce slope-related drainage problems Inputs and examplePurpose Compare drainage choices using the stated slope investigation and constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Repair surface drains, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Repair surface drains. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Repair the documented surface drains.; Resource needs and adverse effects = Needs inspection, capacity, outfall and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Seepage; runoff; drainage condition; slope mechanism; proposed works; costs. Map context. No map inserted into this decision example Limits Drainage benefits must be supported by site-specific engineering evidence. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · The Landslide Handbook, Circular 1325 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP17-017DP17 | Mitigation outcomes Evaluate stabilization performance after completion Inputs and examplePurpose Compare stabilisation outcomes in the supplied observation groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — mitigation outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Measured slope displacement before produces Obtain the missing evidence listed below. Missing Treatment Measured slope displacement before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Measured slope displacement before [mm]; Treatment Measured slope displacement after [mm]; Comparison Measured slope displacement before [mm]; Comparison Measured slope displacement after [mm]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (mm) Worked example. Fictional 2025 example. Laggala Pallegama — mitigation outcomes. Treatment Measured slope displacement before = 42 mm; Treatment Measured slope displacement after = 59 mm; Comparison Measured slope displacement before = 39 mm; Comparison Measured slope displacement after = 46 mm; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Measured slope displacement /example matching definition1. Results: Difference in changes = 10 mm. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 mm. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Measured slope displacement before = 42.42. Result: Difference in changes = 9.58 mm. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 mm. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Measured slope displacement before. No usable result. Treatment Measured slope displacement before Next check: Correct or obtain the missing input records. Information still needed: Treatment Measured slope displacement before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a causal treatment effect. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP17-020DP17 | Case administration Clear incomplete landslide assessment applications Inputs and examplePurpose Identify investigation applications past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — case administration, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — case administration. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A deadline does not establish the technical risk or grant an application. Geotechnical/landslide specialist and authorized technical reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Landslide Clearance for Construction in Landslide Prone Areas Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-001DP18 | Water pollution Investigate water samples exceeding applicable limits Inputs and examplePurpose Check the reported water sample against its stated parameter and comparison bounds. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — water pollution, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [pH]; Example lower comparison bound [pH]; Example upper comparison bound [pH]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (pH) Worked example. Fictional 2025 example. Laggala Pallegama — water pollution. Parameter and applicable use = Ambient water pH for selected use; Measured result = 7.4 pH; Example lower comparison bound = 6.5 pH; Example upper comparison bound = 8.5 pH; Original and limit unit = pH; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 7.4 pH. Interpretation: The supplied Ambient water pH for selected use result is 7.4 pH. Its stated comparison range is 6.5 to 8.5 pH. Within example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 7.474; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 7.474 pH. Interpretation: The supplied Ambient water pH for selected use result is 7.474 pH. Its stated comparison range is 6.5 to 8.5 pH. Within example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits Method, use and sampling evidence are needed before a legal or health interpretation. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Ambient water limit comparison Select the applicable water-use category and compare the measured parameter in the schedule's unit and limit type. Use the schedule only for the applicable inland surface-water use, such as irrigation. Confirm sampling and laboratory quality. Other media require their own limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-003DP18 | Mitigation compliance Follow up unverified environmental mitigation obligations Inputs and examplePurpose Find missing evidence for recorded mitigation obligations. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — mitigation compliance, the default output explains Obtain the missing evidence listed below. Changing Permit or approval, Permit or approval evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Permit or approval remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Permit or approval; Permit or approval evidence reference; condition; condition evidence reference; due date; due date evidence reference; inspection; inspection evidence reference; compliance evidence; compliance evidence evidence reference; owner; owner evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — mitigation compliance. Permit or approval = Missing; Permit or approval evidence reference = ; condition = Documented; condition evidence reference = Sample Laggala Pallegama field register / 2025; due date = Documented; due date evidence reference = Sample Laggala Pallegama field register / 2025; inspection = Documented; inspection evidence reference = Sample Laggala Pallegama field register / 2025; compliance evidence = Documented; compliance evidence evidence reference = Sample Laggala Pallegama field register / 2025; owner = Documented; owner evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this mitigation compliance case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Permit or approval = Documented; Permit or approval evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle mitigation compliance. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Permit or approval. The required evidence is incomplete for this mitigation compliance case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Permit or approval: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A filled checklist does not establish implementation or permit compliance. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Review environmental alternatives or mitigation Identify potential impacts, document relevant alternatives and review the measures proposed to reduce significant impacts. Confirm whether the EIA process applies and obtain the competent authority’s scope and conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-004DP18 | Water anomalies Investigate unusual changes in water-quality observations Inputs and examplePurpose Identify an unusual water observation for source and sampling checks. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — water anomalies, the default output explains Check the unusual observation and its comparison basis. Changing Comparable reference value produces Check the unusual observation and its comparison basis. Missing Comparable reference value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable reference value [mg/L]; Later/comparison value [mg/L] Result: Difference; Relative change (mg/L; %) Worked example. Fictional 2025 example. Laggala Pallegama — water anomalies. Comparable reference value = 100 mg/L; Later/comparison value = 90 mg/L. Results: Difference = -10 mg/L; Relative change = -10 %. Interpretation: Difference: -10 mg/L. Next check: Check the unusual observation and its comparison basis. Changed input. Change Comparable reference value = 101. Result: Difference = -11 mg/L; Relative change = -10.891 %. Interpretation: Difference: -11 mg/L. Next check: Check the unusual observation and its comparison basis. Missing input. Omit Comparable reference value. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits A deviation alone does not diagnose pollution or identify its source. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · National Environmental Ambient Water Quality Regulations No. 1 of 2019 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-005DP18 | Environmental licensing Refer complete license applications to the competent authority Inputs and examplePurpose Check the records needed for a licence-application review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — environmental licensing, the default output explains Obtain the missing evidence listed below. Changing Activity classification, Activity classification evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Activity classification remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Activity classification; Activity classification evidence reference; application; application evidence reference; inspection; inspection evidence reference; current rules; current rules evidence reference; required documents; required documents evidence reference; conditions; conditions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — environmental licensing. Activity classification = Missing; Activity classification evidence reference = ; application = Documented; application evidence reference = Sample Laggala Pallegama field register / 2025; inspection = Documented; inspection evidence reference = Sample Laggala Pallegama field register / 2025; current rules = Documented; current rules evidence reference = Sample Laggala Pallegama field register / 2025; required documents = Documented; required documents evidence reference = Sample Laggala Pallegama field register / 2025; conditions = Documented; conditions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this environmental licensing case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Activity classification = Documented; Activity classification evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle environmental licensing. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Activity classification. The required evidence is incomplete for this environmental licensing case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Activity classification: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not issue an environmental licence. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Licence application routing Match the prescribed activity category and jurisdiction to the licensing authority before referring the case. Sector guidance · Acts and Regulations Confirm the current gazette, any BOI status and required application evidence. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S20, S21 Context alone does not validate the formula. |
| DEC-DP18-007DP18 | Environmental assessment Screen project proposals for required assessment pathways Inputs and examplePurpose Check the evidence needed to refer a project through the applicable assessment pathway. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — environmental assessment, the default output explains Obtain the missing evidence listed below. Changing Project type, Project type evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Project type remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Project type; Project type evidence reference; location; location evidence reference; scale; scale evidence reference; sensitive areas; sensitive areas evidence reference; current criteria; current criteria evidence reference; authority; authority evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — environmental assessment. Project type = Missing; Project type evidence reference = ; location = Documented; location evidence reference = Sample Laggala Pallegama field register / 2025; scale = Documented; scale evidence reference = Sample Laggala Pallegama field register / 2025; sensitive areas = Documented; sensitive areas evidence reference = Sample Laggala Pallegama field register / 2025; current criteria = Documented; current criteria evidence reference = Sample Laggala Pallegama field register / 2025; authority = Documented; authority evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this environmental assessment case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Project type = Documented; Project type evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle environmental assessment. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Project type. The required evidence is incomplete for this environmental assessment case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Project type: Missing. Map context. No map inserted into this decision example Limits The responsible authority must determine the required assessment and permission. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Environmental assessment screening Check project type, scale and sensitive location against the prescribed-project rules. Refer a matching project for determination of the IEE or EIA route. Verify the current gazette and project footprint. CEA and the assigned Project Approving Agency decide the pathway. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S20, S21 Context alone does not validate the formula. |
| DEC-DP18-008DP18 | Air pollution Investigate measured air-quality departures from applicable limits Inputs and examplePurpose Check the reported air observation against its stated averaging period and bounds. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — air pollution, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [µg/m³]; Example lower comparison bound [µg/m³]; Example upper comparison bound [µg/m³]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (µg/m³) Worked example. Fictional 2025 example. Laggala Pallegama — air pollution. Parameter and applicable use = PM2.5 concentration over stated averaging period; Measured result = 38 µg/m³; Example lower comparison bound = 0 µg/m³; Example upper comparison bound = 35 µg/m³; Original and limit unit = µg/m³; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 38 µg/m³. Interpretation: The supplied PM2.5 concentration over stated averaging period result is 38 µg/m³. Its stated comparison range is 0 to 35 µg/m³. Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 38.38; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 38.38 µg/m³. Interpretation: The supplied PM2.5 concentration over stated averaging period result is 38.38 µg/m³. Its stated comparison range is 0 to 35 µg/m³. Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits A sample comparison does not establish legal air-quality compliance. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Air quality averaging-period comparison Compare the matching pollutant with the limit for its averaging period only when enough valid observations support that average. Sector guidance · Acts and Regulations Confirm the station, units, observation coverage and currently applicable limit. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-009DP18 | Noise complaints Prioritize investigation of evidence-supported noise complaints Inputs and examplePurpose Check the reported noise observation against its stated time and use conditions. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — noise complaints, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [dB(A)]; Example lower comparison bound [dB(A)]; Example upper comparison bound [dB(A)]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (dB(A)) Worked example. Fictional 2025 example. Laggala Pallegama — noise complaints. Parameter and applicable use = LAeq over stated interval and zone; Measured result = 62 dB(A); Example lower comparison bound = 0 dB(A); Example upper comparison bound = 60 dB(A); Original and limit unit = dB(A); Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 62 dB(A). Interpretation: The supplied LAeq over stated interval and zone result is 62 dB(A). Its stated comparison range is 0 to 60 dB(A). Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 62.62; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 62.62 dB(A). Interpretation: The supplied LAeq over stated interval and zone result is 62.62 dB(A). Its stated comparison range is 0 to 60 dB(A). Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits A comparison does not establish a legal breach without the applicable standard and method. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Boundary noise comparison Use the boundary measurement and the applicable zone and time-period limit. Check the background-noise provision when applicable. Sector guidance · Acts and Regulations Confirm the site category, measurement method and applicable provisions before referral. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-011DP18 | Waste management Compare waste collection treatment and disposal options Inputs and examplePurpose Compare waste-management choices using permissions, capacity and adverse effects. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Improve segregated collection, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Improve segregated collection. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve segregation and collection of the stated waste.; Resource needs and adverse effects = Needs waste composition, reliable collection and permitted destinations.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Waste type; quantity; hazards; facilities; costs; environmental constraints. Map context. No map inserted into this decision example Limits Cost does not establish lawful or environmentally suitable disposal. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Acts and Regulations Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-012DP18 | Hazardous waste Review traceability of hazardous-waste transfers Inputs and examplePurpose Trace hazardous-waste records between the stated source and receiving records. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Checks For Laggala Pallegama — hazardous waste, the default output explains Investigate linked downstream lot. Changing Recorded upstream issue produces Review recorded lineage. Missing Upstream lot/source reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Upstream lot/source reference; Downstream lot/batch reference; Exact upstream source version; Recorded upstream issue Result: Broken or affected lineage (items) Worked example. Fictional 2025 example. Laggala Pallegama — hazardous waste. Upstream lot/source reference = EXAMPLE-ROOT; Downstream lot/batch reference = 2025-BATCH-1; Exact upstream source version = Sample version1; Recorded upstream issue = Confirmed defect. Results: Broken or affected lineage = 1 items. Interpretation: Broken or affected lineage: 1 items. Investigate linked downstream lot. Next check: Investigate linked downstream lot. Changed input. Change Recorded upstream issue = None. Result: Broken or affected lineage = 0 items. Interpretation: Broken or affected lineage: 0 items. Review recorded lineage. Next check: Review recorded lineage. Missing input. Omit Upstream lot/source reference. No usable result. Upstream lot/source reference Next check: Correct or obtain the missing input records. Information still needed: Upstream lot/source reference. Map context. No map inserted into this decision example Limits A complete reference chain does not prove physical receipt or lawful handling. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Trace a scheduled waste movement Use consignment and receiving records to trace the waste from the generator through transport to the receiving facility. Sector guidance · Notification and Movement Documents Confirm the applicable waste category, current licence, custody records and exceptions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-013DP18 | Wetland conservation Refer development pressure overlapping protected wetland evidence Inputs and examplePurpose Check reported activity overlap with the cited wetland record. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — wetland conservation, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — wetland conservation. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The figure does not establish an authoritative wetland boundary or permission. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Environmental Impact Assessment Procedure in Sri Lanka Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-014DP18 | Public complaints Escalate unresolved pollution complaints Inputs and examplePurpose Identify pollution complaints past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — public complaints, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — public complaints. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Age alone does not establish severity or justify enforcement. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending Published Sri Lankan step. Screen the complaint for CEA jurisdiction, retain its reference number and route it to the relevant CEA office or another responsible agency. Central Environmental Authority · Compliance Monitoring Unit. How to manage and proceed with a complaint. Confirm the responsible office and any service target separately in Institution review. Calculation reference. International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-015DP18 | Inspection targeting Schedule inspections by approved pollution-risk priorities Inputs and examplePurpose Check inspection dates, resources and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — inspection targeting, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — inspection targeting. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not appoint inspectors or issue access authority. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Acts and Regulations Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP18-018DP18 | Restoration outcomes Assess environmental recovery after remedial works Inputs and examplePurpose Compare environmental observations before and after the stated intervention. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — restoration outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Selected water-quality parameter before produces Obtain the missing evidence listed below. Missing Treatment Selected water-quality parameter before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Selected water-quality parameter before [mg/L]; Treatment Selected water-quality parameter after [mg/L]; Comparison Selected water-quality parameter before [mg/L]; Comparison Selected water-quality parameter after [mg/L]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (mg/L) Worked example. Fictional 2025 example. Laggala Pallegama — restoration outcomes. Treatment Selected water-quality parameter before = 42 mg/L; Treatment Selected water-quality parameter after = 59 mg/L; Comparison Selected water-quality parameter before = 39 mg/L; Comparison Selected water-quality parameter after = 46 mg/L; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Selected water-quality parameter /example matching definition1. Results: Difference in changes = 10 mg/L. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 mg/L. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Selected water-quality parameter before = 42.42. Result: Difference in changes = 9.58 mg/L. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 mg/L. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Selected water-quality parameter before. No usable result. Treatment Selected water-quality parameter before Next check: Correct or obtain the missing input records. Information still needed: Treatment Selected water-quality parameter before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish recovery caused by the intervention. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP18-020DP18 | Environmental records Harmonize classifications without altering source meanings Inputs and examplePurpose Compare environmental classification meanings across sources. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — environmental records, the default output explains Obtain the missing evidence listed below. Changing Source activity labels, Source activity labels evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source activity labels remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source activity labels; Source activity labels evidence reference; current reference list; current reference list evidence reference; definition; definition evidence reference; edition; edition evidence reference; steward review; steward review evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — environmental records. Source activity labels = Missing; Source activity labels evidence reference = ; current reference list = Documented; current reference list evidence reference = Sample Laggala Pallegama field register / 2025; definition = Documented; definition evidence reference = Sample Laggala Pallegama field register / 2025; edition = Documented; edition evidence reference = Sample Laggala Pallegama field register / 2025; steward review = Documented; steward review evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this environmental records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source activity labels = Documented; Source activity labels evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle environmental records. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source activity labels. The required evidence is incomplete for this environmental records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source activity labels: Missing. Map context. No map inserted into this decision example Limits A matching label does not establish equivalent legal or scientific definitions. Environmental specialist, laboratory reviewer and regulatory officer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-001DP19 | Survey coverage Improve comparable biodiversity surveys in protected areas Inputs and examplePurpose Check biodiversity records against survey effort, season and protocol. Output Comparison table Next step Prepare biodiversity comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred. Checks For Laggala Pallegama — survey coverage, the default output explains Review survey comparability. Changing Observed distinct species produces Review survey comparability. Missing Observed distinct species remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Observed distinct species [species]; Survey effort [hours]; Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed Result: Observed richness; Recorded effort (species; hours) Worked example. Fictional 2025 example. Laggala Pallegama — survey coverage. Observed distinct species = 28 species; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes. Results: Observed richness = 28 species; Recorded effort = 18 hours. Interpretation: Observed richness: 28 species. Review survey comparability. Next check: Review survey comparability. Changed input. Change Observed distinct species = 29. Result: Observed richness = 29 species; Recorded effort = 18 hours. Interpretation: Observed richness: 29 species. Review survey comparability. Next check: Review survey comparability. Missing input. Omit Observed distinct species. No usable result. Observed distinct species Next check: Correct or obtain the missing input records. Information still needed: Observed distinct species. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Recorded taxa and effort do not establish complete species presence or absence. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check whether biological surveys are comparable Retain the survey protocol, effort and event scope when comparing observations. Confirm season, coverage, species identification and any difference in detectability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-002DP19 | Wildlife incidents Prioritize unresolved wildlife conflict and rescue cases Inputs and examplePurpose Identify wildlife conflict and rescue cases needing a documented follow-up. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — wildlife incidents, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — wildlife incidents. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Case age alone does not establish biological urgency or authorise a response. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Guidelines on Human-Wildlife Conflict and Coexistence Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-003DP19 | Habitat exposure Identify threatened-species habitats requiring protection review Inputs and examplePurpose Review supplied habitat-footprint overlaps and source editions. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — habitat exposure, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — habitat exposure. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Reported hectares are not a new habitat map or proof of ecological damage. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Conserving Connectivity through Ecological Networks and Corridors Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-004DP19 | Threat reduction Refer candidate conservation actions for specialist threat assessment Inputs and examplePurpose Find missing species, threat and restoration evidence for a STAR assessment. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — threat reduction, the default output explains Obtain the missing evidence listed below. Changing Species range, Species range evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Species range remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Species range; Species range evidence reference; threats; threats evidence reference; action feasibility; action feasibility evidence reference; threat reduction evidence; threat reduction evidence evidence reference; uncertainty; uncertainty evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — threat reduction. Species range = Missing; Species range evidence reference = ; threats = Documented; threats evidence reference = Sample Laggala Pallegama field register / 2025; action feasibility = Documented; action feasibility evidence reference = Sample Laggala Pallegama field register / 2025; threat reduction evidence = Documented; threat reduction evidence evidence reference = Sample Laggala Pallegama field register / 2025; uncertainty = Documented; uncertainty evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this threat reduction case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Species range = Documented; Species range evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle threat reduction. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Species range. The required evidence is incomplete for this threat reduction case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Species range: Missing. Map context. No map inserted into this decision example Limits The checklist does not calculate or validate a STAR score. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Identify the threat and proposed action before STAR assessment Check documented species, threats and sites to decide whether the threat-abatement or restoration component applies. Confirm the species and extent with a specialist. The prototype does not produce a STAR score. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-006DP19 | Fence maintenance Prioritize defects in approved protective fences Inputs and examplePurpose Identify overdue fence inspections and missing maintenance records. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — fence maintenance, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — fence maintenance. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Inspection age does not establish fence effectiveness or immediate conflict risk. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Guidelines on Human-Wildlife Conflict and Coexistence Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-007DP19 | Wildlife corridors Review proposed activities affecting habitat connectivity Inputs and examplePurpose Check reported corridor overlap against dated source evidence. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — wildlife corridors, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — wildlife corridors. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A footprint overlap is not an animal-movement or connectivity analysis. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Conserving Connectivity through Ecological Networks and Corridors Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-008DP19 | Poaching response Assign verified illegal-activity observations for authorized investigation Inputs and examplePurpose Identify investigation cases awaiting documented evidence or response. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — poaching response, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — poaching response. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits The prototype does not determine an offence or enforcement action. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-012DP19 | Research permissions Check research proposals against current permit requirements Inputs and examplePurpose Check the records needed for a wildlife-research permit referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — research permissions, the default output explains Obtain the missing evidence listed below. Changing Research proposal, Research proposal evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Research proposal remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Research proposal; Research proposal evidence reference; species; species evidence reference; methods; methods evidence reference; site; site evidence reference; ethics; ethics evidence reference; requested collections; requested collections evidence reference; conditions; conditions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — research permissions. Research proposal = Missing; Research proposal evidence reference = ; species = Documented; species evidence reference = Sample Laggala Pallegama field register / 2025; methods = Documented; methods evidence reference = Sample Laggala Pallegama field register / 2025; site = Documented; site evidence reference = Sample Laggala Pallegama field register / 2025; ethics = Documented; ethics evidence reference = Sample Laggala Pallegama field register / 2025; requested collections = Documented; requested collections evidence reference = Sample Laggala Pallegama field register / 2025; conditions = Documented; conditions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this research permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Research proposal = Documented; Research proposal evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle research permissions. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Research proposal. The required evidence is incomplete for this research permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Research proposal: Missing. Map context. No map inserted into this decision example Limits The example issues no permit or access authority. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Protected wildlife research permit check Refer regulated research involving protected species or protected areas for DWC permit review. Check the proposal, methods, site and proposed collections. Confirm any additional ethics, collection or site-access requirements with the competent bodies. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S22, S23, S45 Context alone does not validate the formula. |
| DEC-DP19-014DP19 | Habitat restoration Compare restoration actions for degraded wildlife habitats Inputs and examplePurpose Compare habitat-restoration choices using the documented ecological and rights evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Restore native vegetation, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Restore native vegetation. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Restore suitable native vegetation.; Resource needs and adverse effects = Needs reference habitat, site suitability, rights and maintenance.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Habitat condition; native species; hydrology; land rights; costs; threats. Map context. No map inserted into this decision example Limits A budget balance does not establish an appropriate restoration design. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match restoration approach to the site Use the baseline and site conditions to choose a restoration approach and monitor its performance after implementation. Sector guidance · Forest Restoration Module Confirm plot boundaries, reference ecosystem, species and measurement protocol. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-015DP19 | Population monitoring Review population trends using comparable survey effort Inputs and examplePurpose Compare recorded encounters per survey hour under matching protocols. Output Comparison table Next step Prepare biodiversity comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Observed encounter rate = recorded encounters / positive survey hours. Compare only the same species, area, season, protocol and count definition. This is a simple survey index, not a population estimate or detection-corrected trend. Checks For Laggala Pallegama — population monitoring, the default output explains Review effort, detection and count comparability. Changing Recorded encounters of the stated species produces Review effort, detection and count comparability. Missing Recorded encounters of the stated species remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded encounters of the stated species [encounters]; Survey effort [hours]; Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed; Species and count definition Result: Observed encounter rate; Recorded effort; Recorded encounters (encounters/hour; hours; encounters) Worked example. Fictional 2025 example. Laggala Pallegama — population monitoring. Recorded encounters of the stated species = 28 encounters; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes; Species and count definition = Sambar deer — fictional standardized encounter count. Results: Observed encounter rate = 1.556 encounters/hour; Recorded effort = 18 hours; Recorded encounters = 28 encounters. Interpretation: Observed encounter rate: 1.556 encounters/hour. Review effort, detection and count comparability. Next check: Review effort, detection and count comparability. Changed input. Change Recorded encounters of the stated species = 29. Result: Observed encounter rate = 1.611 encounters/hour; Recorded effort = 18 hours; Recorded encounters = 29 encounters. Interpretation: Observed encounter rate: 1.611 encounters/hour. Review effort, detection and count comparability. Next check: Review effort, detection and count comparability. Missing input. Omit Recorded encounters of the stated species. No usable result. Observed distinct species Next check: Correct or obtain the missing input records. Information still needed: Observed distinct species. Map context. No map inserted into this decision example Limits An encounter rate is not a wildlife population estimate. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check whether biological surveys are comparable Retain the survey protocol, effort and event scope when comparing observations. Confirm season, coverage, species identification and any difference in detectability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-016DP19 | Wildlife health Refer unusual mortality or illness clusters to specialists Inputs and examplePurpose Compare recorded wildlife mortality between matching reporting periods. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — wildlife health, the default output explains Refer the increased reports; no outbreak or spatial cluster is established. Changing Comparable reported mortality/illness cases produces Refer the increased reports; no outbreak or spatial cluster is established. Missing Comparable reported mortality/illness cases remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable reported mortality/illness cases [cases]; Reported cases in the selected comparable window [cases] Result: Difference; Relative change (cases; %) Worked example. Fictional 2025 example. Laggala Pallegama — wildlife health. Comparable reported mortality/illness cases = 2 cases; Reported cases in the selected comparable window = 7 cases. Results: Difference = 5 cases; Relative change = 250 %. Interpretation: Difference: 5 cases. Refer the increased reports; no outbreak or spatial cluster is established. Next check: Refer the increased reports; no outbreak or spatial cluster is established. Changed input. Change Comparable reported mortality/illness cases = 3. Result: Difference = 4 cases; Relative change = 133.333 %. Interpretation: Difference: 4 cases. Refer the increased reports; no outbreak or spatial cluster is established. Next check: Refer the increased reports; no outbreak or spatial cluster is established. Missing input. Omit Comparable reported mortality/illness cases. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits A change in counts does not diagnose a cause or establish a spatial cluster. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP19-019DP19 | Conservation effectiveness Evaluate conservation outcomes and adverse effects Inputs and examplePurpose Compare reported outcomes and adverse effects across the supplied periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — conservation effectiveness, the default output explains Obtain the missing evidence listed below. Changing Intervention group native vegetation cover in matched habitat-monitoring plots before produces Obtain the missing evidence listed below. Missing Intervention group native vegetation cover in matched habitat-monitoring plots before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Intervention group native vegetation cover in matched habitat-monitoring plots before [%]; Intervention group native vegetation cover in matched habitat-monitoring plots after [%]; Comparison group native vegetation cover in matched habitat-monitoring plots before [%]; Comparison group native vegetation cover in matched habitat-monitoring plots after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — conservation effectiveness. Intervention group native vegetation cover in matched habitat-monitoring plots before = 42 %; Intervention group native vegetation cover in matched habitat-monitoring plots after = 59 %; Comparison group native vegetation cover in matched habitat-monitoring plots before = 39 %; Comparison group native vegetation cover in matched habitat-monitoring plots after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Fictional measure: Native vegetation cover in matched habitat-monitoring plots / matching frame, method and before-after windows. Results: Difference in changes = 10 percentage points. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Intervention group native vegetation cover in matched habitat-monitoring plots before = 42.42. Result: Difference in changes = 9.58 percentage points. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Intervention group native vegetation cover in matched habitat-monitoring plots before. No usable result. Treatment Comparable habitat-condition indicator before Next check: Correct or obtain the missing input records. Information still needed: Treatment Comparable habitat-condition indicator before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a causal conservation effect. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP19-020DP19 | Protected-area records Resolve conflicting protected-area and habitat labels Inputs and examplePurpose Compare habitat and protected-area classification meanings and source references. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — protected-area records, the default output explains Obtain the missing evidence listed below. Changing Boundary source, Boundary source evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Boundary source remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Boundary source; Boundary source evidence reference; legal edition; legal edition evidence reference; area name; area name evidence reference; habitat classification; habitat classification evidence reference; custodian; custodian evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — protected-area records. Boundary source = Missing; Boundary source evidence reference = ; legal edition = Documented; legal edition evidence reference = Sample Laggala Pallegama field register / 2025; area name = Documented; area name evidence reference = Sample Laggala Pallegama field register / 2025; habitat classification = Documented; habitat classification evidence reference = Sample Laggala Pallegama field register / 2025; custodian = Documented; custodian evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this protected-area records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Boundary source = Documented; Boundary source evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle protected-area records. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Boundary source. The required evidence is incomplete for this protected-area records case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Boundary source: Missing. Map context. No map inserted into this decision example Limits Matching labels do not establish the same boundary or legal protection. Wildlife ecologist, protected-area manager and veterinary specialist where needed | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-001DP20 | Agricultural patterns Identify crop variety and irrigation patterns needing analysis Inputs and examplePurpose Compare design-weighted crop indicators under the same definition and survey frame. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Weighted proportion = sum(weight×indicator0/1)/sum(weight). Report the classification and eligible population; use design information for uncertainty. Checks For Laggala Pallegama — agricultural patterns, the default output explains Refer the recorded evidence and unresolved conditions for the responsible review. Changing Final design weight produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Final design weight remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Final design weight [weight]; Recorded 0/1 indicator under that exact definition [0 or1]; Stratum and primary sampling unit; Exact binary indicator and reference period Result: Observed variable (0 or1) Worked example. Fictional 2025 example. Laggala Pallegama — agricultural patterns. Final design weight = 2 weight; Recorded 0/1 indicator under that exact definition = 1 0 or1; Stratum and primary sampling unit = Fictional sampling stratum / Laggala Pallegama cluster; Exact binary indicator and reference period = Fictional indicator: Bg 300 paddy on an irrigated plot in the stated reference season; 1 = meets definition, 0 = does not. Results: Observed variable = 1 0 or1. Interpretation: Observed variable: 1 0 or1. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Changed input. Change Final design weight = 2.02. Result: Observed variable = 1 0 or1. Interpretation: Observed variable: 1 0 or1. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Final design weight. No usable result. Final design weight Next check: Correct or obtain the missing input records. Information still needed: Final design weight. Selected-frame statistics. n = 3; weightTotal = 10; percent = 70 Map context. No map inserted into this decision example Limits A fictional weighted proportion is not an official rate or a precision estimate. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Weighted estimation component Weighted estimation component Sector guidance · Paddy Statistics Confirm the survey weights, crop-cutting estimation method, irrigation classification and corresponding area. The source gives the reporting basis. Implementation: prototype |
| DEC-DP20-002DP20 | Poverty reporting Select defensible geographic poverty and income comparisons Inputs and examplePurpose Compare design-weighted household-income observations in a matching reference period. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Weighted mean = sum(weight×observation)/sum(weight). Estimated total = sum(weight×observation), only for weights and population coverage suitable for that estimand. Checks For Laggala Pallegama — poverty reporting, the default output explains Refer the recorded evidence and unresolved conditions for the responsible review. Changing Final design weight produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Final design weight remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Final design weight [weight]; Observed variable [LKR/household]; Stratum and primary sampling unit Result: Observed variable (LKR/household) Worked example. Fictional 2025 example. Laggala Pallegama — poverty reporting. Final design weight = 2 weight; Observed variable = 68,000 LKR/household; Stratum and primary sampling unit = Fictional sampling stratum / Laggala Pallegama cluster. Results: Observed variable = 68,000 LKR/household. Interpretation: Observed variable: 68,000 LKR/household. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Changed input. Change Final design weight = 2.02. Result: Observed variable = 68,000 LKR/household. Interpretation: Observed variable: 68,000 LKR/household. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Final design weight. No usable result. Final design weight Next check: Correct or obtain the missing input records. Information still needed: Final design weight. Selected-frame statistics. n = 3; weightTotal = 10; total = 787,000; mean = 78,700 Map context. No map inserted into this decision example Limits A weighted mean alone does not establish poverty or design-based precision. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Weighted estimation component Weighted estimation component Sector guidance · Household Income and Expenditure Survey Confirm the approved weights, poverty line, precision and permitted geography before using a local estimate. Implementation: prototype |
| DEC-DP20-003DP20 | Small-area reporting Determine whether estimates support district or divisional reporting Inputs and examplePurpose Check a supplied estimate and standard error before choosing a reporting level. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Relative standard error=100×design-based SE/abs(estimate), only for a nonzero estimate and an actually supplied design-based SE. Sample count alone does not determine geographic precision. Checks For Laggala Pallegama — small-area reporting, the default output explains Obtain the missing evidence listed below. Changing Design-based standard error produces Obtain the missing evidence listed below. Missing Responding sample units remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Responding sample units [selected units]; Design-weighted estimate [LKR/household/month]; Design-based standard error [LKR/household/month]; Example maximum relative standard error [%]; Variance method, strata and cluster reference Result: Relative standard error (%) Worked example. Fictional 2025 example. Laggala Pallegama — small-area reporting. Responding sample units = 120 selected units; Design-weighted estimate = 78,700 LKR/household/month; Design-based standard error = 12,592 LKR/household/month; Example maximum relative standard error = 20 %; Variance method, strata and cluster reference = Not provided. Results: Relative standard error = 16 %. Interpretation: The supplied estimate 78,700 and standard error 12,592 give a relative standard error of 16%. The supplied 20% review criterion is an example assumption. Confirm the survey design and variance method before choosing a reporting level. Next check: Obtain the missing evidence listed below. Changed input. Change Design-based standard error = 12,593. Result: Relative standard error = 16.001 %. Interpretation: The supplied estimate 78,700 and standard error 12,593 give a relative standard error of 16.001%. The supplied 20% review criterion is an example assumption. Confirm the survey design and variance method before choosing a reporting level. Next check: Obtain the missing evidence listed below. Missing input. Omit Responding sample units. No usable result. Responding sample units Next check: Correct or obtain the missing input records. Information still needed: Responding sample units; Variance method, strata and cluster reference: Not provided. Map context. No map inserted into this decision example Limits The variance method and design evidence are required; the review bound is illustrative. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative standard error percentage Relative standard error percentage Sector guidance · Household Income and Expenditure Survey Confirm the approved weights, poverty line, precision and permitted geography before using a local estimate. Implementation: prototype |
| DEC-DP20-004DP20 | Statistical revisions Identify publications affected by revised statistical series Inputs and examplePurpose Find publications that still use a superseded statistical-series version. Output Case/evidence table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Match the exact statistical series and version used by each listed publication against its replacement version. A publication using an older version, or with unknown update evidence, needs revision review. Count each listed publication once. Checks For District population-profile scenario, the default output explains Check the matching source records before interpreting the change. Changing Series version used in that publication, Publication revision state produces Check the matching source records before interpreting the change. Missing Statistical series and definition remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Statistical series and definition; Superseded series version; Current replacement version; Dependent publication or table reference; Series version used in that publication; Publication revision state; Dependency or revision-check reference Result: Publications needing revision review (publications) Worked example. Fictional 2025 example. District population-profile scenario. Statistical series and definition = Fictional annual population-estimate series; Superseded series version = Population series / version 1; Current replacement version = Population series / version 2; Dependent publication or table reference = District population-profile scenario; Series version used in that publication = Population series / version 1; Publication revision state = Not updated; Dependency or revision-check reference = Fictional source-reference register / entry 1. Results: Publications needing revision review = 1 publications. Interpretation: District population-profile scenario uses Population series / version 1. A revision check is required. Next check: Check the matching source records before interpreting the change. Changed input. Change Series version used in that publication = Population series / version 2; Publication revision state = Updated with evidence. Result: Publications needing revision review = 0 publications. Interpretation: District population-profile scenario uses Population series / version 2. The listed dependency uses the replacement version with recorded update evidence. Next check: Check the matching source records before interpreting the change. Missing input. Omit Statistical series and definition. No usable result. Statistical series and definition Next check: Correct or obtain the missing input records. Information still needed: Statistical series and definition; Statistical series and definition: Not provided. Map context. No map inserted into this decision example Limits A version difference requires a dependency check; no published table is replaced here. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-006DP20 | Nonresponse Target follow-up where survey response is incomplete Inputs and examplePurpose Identify non-response and unknown response status within a matching sample frame. Output Comparison table Next step Prepare coverage follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown. Checks For Laggala Pallegama — nonresponse, the default output explains Check the records behind the uncovered and unknown groups. Changing Required eligible frame produces Check the records behind the uncovered and unknown groups. Missing Required eligible frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required eligible frame [selected units]; Distinct members of that frame covered [selected units]; Frame members with unknown coverage [selected units] Result: Verified coverage; Known uncovered; Unknown coverage (%; selected units; selected units) Worked example. Fictional 2025 example. Laggala Pallegama — nonresponse. Required eligible frame = 100 selected units; Distinct members of that frame covered = 65 selected units; Frame members with unknown coverage = 5 selected units. Results: Verified coverage = 65 %; Known uncovered = 30 selected units; Unknown coverage = 5 selected units. Interpretation: 30 selected units are known to be uncovered; 5 have unknown coverage. 65% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Changed input. Change Required eligible frame = 101. Result: Verified coverage = 64.356 %; Known uncovered = 31 selected units; Unknown coverage = 5 selected units. Interpretation: 31 selected units are known to be uncovered; 5 have unknown coverage. 64.356% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Missing input. Omit Required eligible frame. No usable result. Required eligible frame Next check: Correct or obtain the missing input records. Information still needed: Required eligible frame. Map context. No map inserted into this decision example Limits A response percentage does not establish freedom from non-response bias. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Calculate a survey response rate from eligible units Relate completed interviews to the eligible sample under documented disposition rules. Sector guidance · Handbook of Surveys on Households and Individuals Confirm how partial and unknown-eligibility cases enter the denominator and which survey unit is used. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-009DP20 | Field deployment Allocate enumerators to achieve survey coverage Inputs and examplePurpose Compare enumerator workload with usable time and skills. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — field deployment, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [enumerator days]; Rated capacity for that period [enumerator days]; Unavailable or restricted capacity [enumerator days] Result: Usable capacity minus demand; Usable capacity (enumerator days; enumerator days) Worked example. Fictional 2025 example. Laggala Pallegama — field deployment. Demand in the selected period = 150 enumerator days; Rated capacity for that period = 180 enumerator days; Unavailable or restricted capacity = 45 enumerator days. Results: Usable capacity minus demand = -15 enumerator days; Usable capacity = 135 enumerator days. Interpretation: Usable capacity minus demand: -15 enumerator days. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 enumerator days; Usable capacity = 135 enumerator days. Interpretation: Usable capacity minus demand: -16 enumerator days. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish the sampling design or approve assignments. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Handbook of Surveys on Households and Individuals Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-011DP20 | Method comparability Determine whether series can be compared across revisions Inputs and examplePurpose Find missing definitions and revision history in a statistical series. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — method comparability, the default output explains Obtain the missing evidence listed below. Changing Definitions, Definitions evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Definitions remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Definitions; Definitions evidence reference; questionnaire editions; questionnaire editions evidence reference; sample design; sample design evidence reference; weights; weights evidence reference; units; units evidence reference; reference periods; reference periods evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — method comparability. Definitions = Missing; Definitions evidence reference = ; questionnaire editions = Documented; questionnaire editions evidence reference = Sample Laggala Pallegama field register / 2025; sample design = Documented; sample design evidence reference = Sample Laggala Pallegama field register / 2025; weights = Documented; weights evidence reference = Sample Laggala Pallegama field register / 2025; units = Documented; units evidence reference = Sample Laggala Pallegama field register / 2025; reference periods = Documented; reference periods evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this method comparability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Definitions = Documented; Definitions evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle method comparability. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Definitions. The required evidence is incomplete for this method comparability case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Definitions: Missing. Map context. No map inserted into this decision example Limits Matching years alone do not make revised series comparable. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-013DP20 | Crop estimates Reconcile crop area yield and production estimates Inputs and examplePurpose Compare weighted production and area totals before calculating their ratio yield. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Estimated production=sum(weight×production); estimated harvested area=sum(weight×area); aggregate yield=estimated production/estimated area. Do not average individual yields without the matching denominator. Checks For Laggala Pallegama — crop estimates, the default output explains Refer the recorded evidence and unresolved conditions for the responsible review. Changing Final design weight produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Final design weight remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Final design weight [weight]; Observed harvested area [ha]; Observed harvested production [kg]; Stratum / cluster Result: Observed holding yield (kg/ha) Worked example. Fictional 2025 example. Laggala Pallegama — crop estimates. Final design weight = 2 weight; Observed harvested area = 1 ha; Observed harvested production = 3,000 kg; Stratum / cluster = Fictional sampling stratum / Laggala Pallegama cluster. Results: Observed holding yield = 3,000 kg/ha. Interpretation: Observed holding yield: 3,000 kg/ha. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Changed input. Change Final design weight = 2.02. Result: Observed holding yield = 3,000 kg/ha. Interpretation: Observed holding yield: 3,000 kg/ha. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Final design weight. No usable result. Final design weight Next check: Correct or obtain the missing input records. Information still needed: Final design weight. Selected-frame statistics. n = 3; weightTotal = 10; production = 116,000; area = 28; yield = 4,142.857 Map context. No map inserted into this decision example Limits Do not average holding-level yields or infer design precision from the ratio alone. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Area and yield production identity For paddy, estimated production = net harvested area × average yield. Yield = production ÷ matching net harvested area when derived from compatible totals. Sector guidance · Paddy Statistics Use the same season and geography, compatible net area and the published crop-cutting method. This source does not establish the prototype's sample weights or non-paddy coverage. Implementation: prototype |
| DEC-DP20-014DP20 | Price statistics Investigate unusual observations before index compilation Inputs and examplePurpose Identify a price observation that differs from its supplied comparison series. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — price statistics, the default output explains Check the unusual observation and its comparison basis. Changing Comparable reference value produces Check the unusual observation and its comparison basis. Missing Comparable reference value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable reference value [LKR]; Later/comparison value [LKR] Result: Difference; Relative change (LKR; %) Worked example. Fictional 2025 example. Laggala Pallegama — price statistics. Comparable reference value = 100 LKR; Later/comparison value = 90 LKR. Results: Difference = -10 LKR; Relative change = -10 %. Interpretation: Difference: -10 LKR. Next check: Check the unusual observation and its comparison basis. Changed input. Change Comparable reference value = 101. Result: Difference = -11 LKR; Relative change = -10.891 %. Interpretation: Difference: -11 LKR. Next check: Check the unusual observation and its comparison basis. Missing input. Omit Comparable reference value. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits A deviation needs product, unit, market and collection-period checks. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-015DP20 | Labour statistics Review geographic differences using comparable labour definitions Inputs and examplePurpose Compare weighted labour indicators under matching age, activity and period definitions. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Weighted proportion = sum(weight×indicator0/1)/sum(weight). Report the classification and eligible population; use design information for uncertainty. Checks For Laggala Pallegama — labour statistics, the default output explains Refer the recorded evidence and unresolved conditions for the responsible review. Changing Final design weight produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Final design weight remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Final design weight [weight]; Recorded 0/1 indicator under that exact definition [0 or1]; Stratum and primary sampling unit; Exact binary indicator and reference period Result: Observed variable (0 or1) Worked example. Fictional 2025 example. Laggala Pallegama — labour statistics. Final design weight = 2 weight; Recorded 0/1 indicator under that exact definition = 1 0 or1; Stratum and primary sampling unit = Fictional sampling stratum / Laggala Pallegama cluster; Exact binary indicator and reference period = Fictional indicator: Employed person under the same stated reference-week definition; 1 = meets definition, 0 = does not. Results: Observed variable = 1 0 or1. Interpretation: Observed variable: 1 0 or1. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Changed input. Change Final design weight = 2.02. Result: Observed variable = 1 0 or1. Interpretation: Observed variable: 1 0 or1. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Final design weight. No usable result. Final design weight Next check: Correct or obtain the missing input records. Information still needed: Final design weight. Selected-frame statistics. n = 3; weightTotal = 10; percent = 70 Map context. No map inserted into this decision example Limits An indicator is not comparable when population or labour definitions change. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Labour force proportion and denominator The Sri Lankan survey expresses unemployment as a share of the labour force and participation as a share of the eligible population. Unemployment rate = 100 × unemployed people ÷ labour force. Sector guidance · Handbook of Surveys on Households and Individuals Final Draft Use the approved survey weights and corresponding numerator and eligible frame. Confirm geography, period and design variance. Implementation: prototype |
| DEC-DP20-016DP20 | Demographic change Identify population changes requiring denominator updates Inputs and examplePurpose Compare population figures with matching boundaries and reference dates. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — demographic change, the default output explains Check the matching source records before interpreting the change. Changing Earlier/source value produces Check the matching source records before interpreting the change. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [people]; Later/comparison value [people] Result: Difference; Relative change (people; %) Worked example. Fictional 2025 example. Laggala Pallegama — demographic change. Earlier/source value = 100 people; Later/comparison value = 90 people. Results: Difference = -10 people; Relative change = -10 %. Interpretation: Difference: -10 people. Next check: Check the matching source records before interpreting the change. Changed input. Change Earlier/source value = 101. Result: Difference = -11 people; Relative change = -10.891 %. Interpretation: Difference: -11 people. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits An aggregate change does not establish migration, births or deaths separately. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Intercensal population change Change = later census count − earlier count. Intercensal increase (%) = 100 × change ÷ earlier count. Sector guidance · Calculating Percent Changes Confirm comparable boundaries, dates and coverage. Keep the cumulative change separate from average annual growth. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-017DP20 | Administrative sources Assess administrative datasets before statistical reuse Inputs and examplePurpose Find missing fitness, definition and permission evidence for an administrative source. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — administrative sources, the default output explains Obtain the missing evidence listed below. Changing Coverage, Coverage evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Coverage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Coverage; Coverage evidence reference; definitions; definitions evidence reference; identifiers; identifiers evidence reference; update schedule; update schedule evidence reference; quality; quality evidence reference; permitted purpose; permitted purpose evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — administrative sources. Coverage = Missing; Coverage evidence reference = ; definitions = Documented; definitions evidence reference = Sample Laggala Pallegama field register / 2025; identifiers = Documented; identifiers evidence reference = Sample Laggala Pallegama field register / 2025; update schedule = Documented; update schedule evidence reference = Sample Laggala Pallegama field register / 2025; quality = Documented; quality evidence reference = Sample Laggala Pallegama field register / 2025; permitted purpose = Documented; permitted purpose evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this administrative sources case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Coverage = Documented; Coverage evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle administrative sources. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Coverage. The required evidence is incomplete for this administrative sources case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Coverage: Missing. Map context. No map inserted into this decision example Limits A complete description does not establish statistical suitability. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-018DP20 | Data access services Prioritize permitted requests for statistical extracts Inputs and examplePurpose Identify statistical-extract requests past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — data access services, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — data access services. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age does not override disclosure restrictions or source rights. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-019DP20 | Reproducible estimates Independently reproduce published estimates and revisions Inputs and examplePurpose Check whether the stated inputs reproduce a published estimate. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — reproducible estimates, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [people]; Independently reproduced value [people]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [people]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (people; %) Worked example. Fictional 2025 example. Laggala Pallegama — reproducible estimates. Earlier/source value = 100 people; Independently reproduced value = 90 people; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable people measure; same input scope; Documented absolute comparison tolerance = 0 people; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 people; Relative change = -10 %. Interpretation: Difference: -10 people. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 people; Relative change = -10.891 %. Interpretation: Difference: -11 people. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Reproduction verifies arithmetic consistency, not the survey design or official acceptance. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP20-020DP20 | Classification maintenance Resolve unmapped economic agricultural and geographic codes Inputs and examplePurpose Compare statistical codes, definitions and editions before joining sources. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — classification maintenance, the default output explains Obtain the missing evidence listed below. Changing Source code, Source code evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source code remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source code; Source code evidence reference; reference classification; reference classification evidence reference; validity dates; validity dates evidence reference; definitions; definitions evidence reference; crosswalk review; crosswalk review evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — classification maintenance. Source code = Missing; Source code evidence reference = ; reference classification = Documented; reference classification evidence reference = Sample Laggala Pallegama field register / 2025; validity dates = Documented; validity dates evidence reference = Sample Laggala Pallegama field register / 2025; definitions = Documented; definitions evidence reference = Sample Laggala Pallegama field register / 2025; crosswalk review = Documented; crosswalk review evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this classification maintenance case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source code = Documented; Source code evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle classification maintenance. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source code. The required evidence is incomplete for this classification maintenance case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source code: Missing. Map context. No map inserted into this decision example Limits Matching codes do not establish equivalent categories or geographic boundaries. Survey statistician, subject-matter statistician and disclosure reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match administrative areas to official codes Use the published code for the corresponding division level and edition. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the code vintage, boundary correspondence and any records that cannot be matched. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP21-001DP21 | Groundwater depletion Investigate wells showing sustained drawdown Inputs and examplePurpose Review comparable groundwater-head observations before planning a well investigation. Output Time-series chart and observation table Next step Prepare trend report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — groundwater depletion, the default output explains Check source and period comparability before using the trend. Changing Groundwater head relative to the stated datum produces Check source and period comparability before using the trend. Missing Groundwater head relative to the stated datum remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Groundwater head relative to the stated datum [m]; Datum, pumping state and measurement convention Result: Observed value (m) Worked example. Fictional 2025 example. Laggala Pallegama — groundwater depletion. Groundwater head relative to the stated datum = 100.9 m; Datum, pumping state and measurement convention = Sample common head datum; static measurement. Results: Observed value = 100.9 m. Interpretation: Observed value: 100.9 m. Next check: Check source and period comparability before using the trend. Changed input. Change Groundwater head relative to the stated datum = 101.9. Result: Observed value = 101.9 m. Interpretation: Observed value: 101.9 m. Next check: Check source and period comparability before using the trend. Missing input. Omit Groundwater head relative to the stated datum. No usable result. Groundwater head relative to the stated datum Next check: Correct or obtain the missing input records. Information still needed: Groundwater head relative to the stated datum. Selected-frame statistics. n = 3; mean = 112.8; sd = 31.673 Map context. No map inserted into this decision example Limits Head, datum and pumping state must match; a short series does not establish sustainable abstraction. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP21-007DP21 | Abstraction balance Compare recorded abstraction with reviewed aquifer budgets Inputs and examplePurpose Reconcile the supplied aquifer inflows, outflows and closing-storage observation. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Calculated closing = opening + inflows − releases/transfers − other outflows. Residual = independently observed closing − calculated closing. Checks For Laggala Pallegama — abstraction balance, the default output explains Reconcile closing balance. Changing Opening storage produces Reconcile closing balance. Missing Opening storage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening storage [m³]; Recharge and external groundwater inflow [m³]; Abstraction and groundwater outflow [m³]; Other identified non-overlapping water outflow [m³]; Independently observed closing storage [m³] Result: Calculated closing storage; Observed minus calculated closing (m³; m³) Worked example. Fictional 2025 example. Laggala Pallegama — abstraction balance. Opening storage = 160,000 m³; Recharge and external groundwater inflow = 48,000 m³; Abstraction and groundwater outflow = 35,000 m³; Other identified non-overlapping water outflow = 9,000 m³; Independently observed closing storage = 163,500 m³. Results: Calculated closing storage = 164,000 m³; Observed minus calculated closing = -500 m³. Interpretation: Calculated closing storage are 164,000 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -500 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening storage = 160,001. Result: Calculated closing storage = 164,001 m³; Observed minus calculated closing = -501 m³. Interpretation: Calculated closing storage are 164,001 m³. The recorded closing observation is 163,500 m³; recorded minus calculated is -501 m³. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening storage. No usable result. Opening storage Next check: Correct or obtain the missing input records. Information still needed: Opening storage. Map context. No map inserted into this decision example Limits A balance does not establish sustainable yield without a reviewed aquifer model. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Water storage balance Water storage balance Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP21-009DP21 | Saline intrusion Prioritize coastal groundwater salinity investigations Inputs and examplePurpose Review comparable conductivity observations for a salinity investigation. Output Time-series chart and observation table Next step Prepare trend report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Kalpitiya — saline intrusion scenario, the default output explains Check source and period comparability before using the trend. Changing Comparable observation produces Check source and period comparability before using the trend. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [µS/cm] Result: Observed value (µS/cm) Worked example. Fictional 2025 example. Kalpitiya — saline intrusion scenario. Comparable observation = 1,800 µS/cm. Results: Observed value = 1,800 µS/cm. Interpretation: Observed value: 1,800 µS/cm. Next check: Check source and period comparability before using the trend. Changed input. Change Comparable observation = 1,801. Result: Observed value = 1,801 µS/cm. Interpretation: Observed value: 1,801 µS/cm. Next check: Check source and period comparability before using the trend. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 1,900; sd = 360.555 Map context. No map inserted into this decision example Limits Conductivity alone does not identify seawater intrusion or its cause. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP21-010DP21 | Industrial abstraction Refer industrial groundwater requests for determination Inputs and examplePurpose Find missing demand, hydrogeological and permit evidence for an industrial request. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — industrial abstraction, the default output explains Obtain the missing evidence listed below. Changing Demand, Demand evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Demand remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand; Demand evidence reference; hydrogeological report; hydrogeological report evidence reference; abstraction proposal; abstraction proposal evidence reference; permits; permits evidence reference; monitoring conditions; monitoring conditions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — industrial abstraction. Demand = Missing; Demand evidence reference = ; hydrogeological report = Documented; hydrogeological report evidence reference = Sample Laggala Pallegama field register / 2025; abstraction proposal = Documented; abstraction proposal evidence reference = Sample Laggala Pallegama field register / 2025; permits = Documented; permits evidence reference = Sample Laggala Pallegama field register / 2025; monitoring conditions = Documented; monitoring conditions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this industrial abstraction case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Demand = Documented; Demand evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle industrial abstraction. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Demand. The required evidence is incomplete for this industrial abstraction case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Demand: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not authorise groundwater abstraction. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Industrial well approval and metering Check for a WRB-supervised safe-yield assessment and relevant approval. The directive also requires daily metering records for covered industry wells. Sector guidance · Water Resources Board Annual Report 2022 Confirm the applicable industry, permission and current monitoring conditions with the Water Resources Board. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S25, S26, S56 Context alone does not validate the formula. |
| DEC-DP21-011DP21 | Recharge options Compare managed-recharge alternatives Inputs and examplePurpose Compare managed-recharge choices using geology, water quality and site constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Infiltration basin under investigation, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Infiltration basin under investigation. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate an infiltration basin.; Resource needs and adverse effects = Needs geology, source-water quality, rights, clogging and groundwater-response evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Site geology; source-water quality; recharge volume; costs; controls; feasibility. Map context. No map inserted into this decision example Limits Budget and descriptive benefits do not establish recharge feasibility or safety. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Guidelines for Evaluating Ground-Water Flow Models Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP21-012DP21 | Mining impacts Investigate groundwater changes around extraction sites Inputs and examplePurpose Compare groundwater-head changes around extraction and comparison observations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — mining impacts, the default output explains Obtain the missing evidence listed below. Changing Treatment Groundwater head at common datum before produces Obtain the missing evidence listed below. Missing Treatment Groundwater head at common datum before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Groundwater head at common datum before [m]; Treatment Groundwater head at common datum after [m]; Comparison Groundwater head at common datum before [m]; Comparison Groundwater head at common datum after [m]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (m) Worked example. Fictional 2025 example. Laggala Pallegama — mining impacts. Treatment Groundwater head at common datum before = 42 m; Treatment Groundwater head at common datum after = 59 m; Comparison Groundwater head at common datum before = 39 m; Comparison Groundwater head at common datum after = 46 m; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Groundwater head at common datum /example matching definition1. Results: Difference in changes = 10 m. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 m. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Groundwater head at common datum before = 42.42. Result: Difference in changes = 9.58 m. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 m. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Groundwater head at common datum before. No usable result. Treatment Groundwater head at common datum before Next check: Correct or obtain the missing input records. Information still needed: Treatment Groundwater head at common datum before; Study design and evidence that the treatment and comparison records are comparable. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A difference in changes does not establish an extraction effect. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP21-013DP21 | Well rehabilitation Prioritize rehabilitation of poorly performing wells Inputs and examplePurpose Identify well-rehabilitation cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — well rehabilitation, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — well rehabilitation. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish the best repair or its urgency. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Report 2022 Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP21-014DP21 | Laboratory turnaround Clear delayed groundwater laboratory analyses Inputs and examplePurpose Identify groundwater laboratory cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — laboratory turnaround, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — laboratory turnaround. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A deadline does not establish sample validity or the cause of delay. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · National Field Manual for the Collection of Water-Quality Data Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP21-015DP21 | Drought supply Compare feasible groundwater contingency supplies Inputs and examplePurpose Compare tested contingency supplies using yield, quality, rights and delivery constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Rehabilitate a tested supply well, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Rehabilitate a tested supply well. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Rehabilitate the tested supply well.; Resource needs and adverse effects = Needs yield, quality, engineering, rights and operating-cost evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Demand; verified yields; water quality; transport; costs; authorized abstraction. Map context. No map inserted into this decision example Limits Cost alone does not establish a dependable or safe supply. Hydrogeologist and water-quality specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Water Safety Plan Manual, second edition Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-001DP22 | Non-revenue water Prioritize systems with large unexplained water balances Inputs and examplePurpose Reconcile non-revenue water and its stated consumption and loss components. Output Comparison table Next step Prepare water-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule NRW=input−billed authorized use. Water losses=NRW−unbilled authorized use. Residual real loss=water losses−estimated apparent losses, only when all components are available. Checks For Laggala Pallegama — non-revenue water, the default output explains Check matching meter, billing and loss-estimation records. Changing Corrected system input produces Check matching meter, billing and loss-estimation records. Missing Corrected system input remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Corrected system input [m³]; Billed authorized consumption [m³]; Unbilled authorized consumption [m³]; Estimated apparent losses [m³] Result: Non-revenue water; NRW share; Water losses; Residual real-loss estimate (m³; %; m³; m³) Worked example. Fictional 2025 example. Laggala Pallegama — non-revenue water. Corrected system input = 80,000 m³; Billed authorized consumption = 57,000 m³; Unbilled authorized consumption = 3,200 m³; Estimated apparent losses = 4,500 m³. Results: Non-revenue water = 23,000 m³; NRW share = 28.75 %; Water losses = 19,800 m³; Residual real-loss estimate = 15,300 m³. Interpretation: Non-revenue water: 23,000 m³. Next check: Check matching meter, billing and loss-estimation records. Changed input. Change Corrected system input = 80,001. Result: Non-revenue water = 23,001 m³; NRW share = 28.751 %; Water losses = 19,801 m³; Residual real-loss estimate = 15,301 m³. Interpretation: Non-revenue water: 23,001 m³. Next check: Check matching meter, billing and loss-estimation records. Missing input. Omit Corrected system input. No usable result. Corrected system input Next check: Correct or obtain the missing input records. Information still needed: Corrected system input. Map context. No map inserted into this decision example Limits Non-revenue water includes authorised unbilled use and is not all physical leakage. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Non-revenue water volume Non-revenue water = produced water entering the stated supply system − water billed as authorized use. Sector guidance · Annual Report 2019 Use one system, volume unit and period. Confirm imports, exports, unbilled use and apparent loss before estimating real leakage. Implementation: prototype |
| DEC-DP22-002DP22 | Leakage management Target leakage investigations by service area Inputs and examplePurpose Review estimated real losses before planning a leakage investigation. Output Comparison table Next step Prepare water-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule NRW=input−billed authorized use. Water losses=NRW−unbilled authorized use. Residual real loss=water losses−estimated apparent losses, only when all components are available. Checks For Laggala Pallegama — leakage management, the default output explains Check matching meter, billing and loss-estimation records. Changing Corrected system input produces Check matching meter, billing and loss-estimation records. Missing Corrected system input remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Corrected system input [m³]; Billed authorized consumption [m³]; Unbilled authorized consumption [m³]; Estimated apparent losses [m³] Result: Non-revenue water; NRW share; Water losses; Residual real-loss estimate (m³; %; m³; m³) Worked example. Fictional 2025 example. Laggala Pallegama — leakage management. Corrected system input = 80,000 m³; Billed authorized consumption = 57,000 m³; Unbilled authorized consumption = 3,200 m³; Estimated apparent losses = 4,500 m³. Results: Non-revenue water = 23,000 m³; NRW share = 28.75 %; Water losses = 19,800 m³; Residual real-loss estimate = 15,300 m³. Interpretation: Non-revenue water: 23,000 m³. Next check: Check matching meter, billing and loss-estimation records. Changed input. Change Corrected system input = 80,001. Result: Non-revenue water = 23,001 m³; NRW share = 28.751 %; Water losses = 19,801 m³; Residual real-loss estimate = 15,301 m³. Interpretation: Non-revenue water: 23,001 m³. Next check: Check matching meter, billing and loss-estimation records. Missing input. Omit Corrected system input. No usable result. Corrected system input Next check: Correct or obtain the missing input records. Information still needed: Corrected system input. Map context. No map inserted into this decision example Limits A system balance does not locate a leak or verify the apparent-loss estimate. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. Distinguish leakage, free supply and unauthorized consumption when investigating non-revenue water. Use matched service areas and periods before comparing quantities. National Water Supply and Drainage Board · Annual Report 2015. Non-Revenue Water Reduction and Auditor General report, Non-revenue Water. Confirm the current meter coverage and water-balance procedure. Use the cited IWA method for the full calculation. Calculation reference. International method matchSri Lanka · Validation required IWA water-balance components IWA water-balance components Sector guidance · Annual Report 2019 Obtain the current NWSDB water-balance method and approved components for this system. Confirm the reported input and billed water on the same period and boundary. Implementation: prototype |
| DEC-DP22-005DP22 | Water safety planning Prioritize source-to-consumer hazards and controls Inputs and examplePurpose Find missing hazard, exposure and control evidence in a water-safety review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — water safety planning, the default output explains Obtain the missing evidence listed below. Changing Supply system, Supply system evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Supply system remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Supply system; Supply system evidence reference; hazards; hazards evidence reference; exposure; exposure evidence reference; control measures; control measures evidence reference; evidence; evidence evidence reference; approved risk method; approved risk method evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — water safety planning. Supply system = Missing; Supply system evidence reference = ; hazards = Documented; hazards evidence reference = Sample Laggala Pallegama field register / 2025; exposure = Documented; exposure evidence reference = Sample Laggala Pallegama field register / 2025; control measures = Documented; control measures evidence reference = Sample Laggala Pallegama field register / 2025; evidence = Documented; evidence evidence reference = Sample Laggala Pallegama field register / 2025; approved risk method = Documented; approved risk method evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this water safety planning case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Supply system = Documented; Supply system evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle water safety planning. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Supply system. The required evidence is incomplete for this water safety planning case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Supply system: Missing. Map context. No map inserted into this decision example Limits The checklist does not assign a validated risk score or certify a safe supply. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Review hazards across the water supply system Review hazards and controls at each step from catchment to consumer before prioritizing the risks. Confirm system boundaries, applicable limits, existing controls and who can approve action. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-006DP22 | Treatment capacity Compare peak demand with usable treatment capacity Inputs and examplePurpose Compare peak demand with treatment capacity available in the same period. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — treatment capacity, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [m³/day]; Rated capacity for that period [m³/day]; Unavailable or restricted capacity [m³/day] Result: Usable capacity minus demand; Usable capacity (m³/day; m³/day) Worked example. Fictional 2025 example. Laggala Pallegama — treatment capacity. Demand in the selected period = 150 m³/day; Rated capacity for that period = 180 m³/day; Unavailable or restricted capacity = 45 m³/day. Results: Usable capacity minus demand = -15 m³/day; Usable capacity = 135 m³/day. Interpretation: Usable capacity minus demand: -15 m³/day. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 m³/day; Usable capacity = 135 m³/day. Interpretation: Usable capacity minus demand: -16 m³/day. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish treatment performance or a safe operating plan. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Water Safety Plan Manual, second edition Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-008DP22 | Pipe replacement Prioritize pipe rehabilitation using verified asset condition Inputs and examplePurpose Identify overdue pipe-condition and rehabilitation follow-ups. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — pipe replacement, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — pipe replacement. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Case age alone does not establish asset failure probability or repair priority. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Water Safety Plan Manual, second edition Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-009DP22 | Pump efficiency Select pumping systems for energy-efficiency appraisal Inputs and examplePurpose Compare pumping electricity per delivered water volume. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Electric energy consumed / Water pumped, for the same product, process and period. Checks For Laggala Pallegama — pump efficiency, the default output explains Check matching outputs, denominators and operating conditions. Changing Electric energy consumed produces Check matching outputs, denominators and operating conditions. Missing Electric energy consumed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Electric energy consumed [kWh]; Water pumped [m³] Result: Specific energy use (kWh/m³) Worked example. Fictional 2025 example. Laggala Pallegama — pump efficiency. Electric energy consumed = 3,128 kWh; Water pumped = 18,000 m³. Results: Specific energy use = 0.174 kWh/m³. Interpretation: Electric energy consumed: 3,128 kWh; Water pumped: 18,000 m³. This gives 0.174 kWh/m³. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Electric energy consumed = 3,129. Result: Specific energy use = 0.174 kWh/m³. Interpretation: Electric energy consumed: 3,129 kWh; Water pumped: 18,000 m³. This gives 0.174 kWh/m³. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Electric energy consumed. No usable result. Electric energy consumed Next check: Correct or obtain the missing input records. Information still needed: Electric energy consumed. Map context. No map inserted into this decision example Limits A high ratio needs equipment and operating checks before choosing a replacement. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare energy use per unit of output Relate energy use to output over the same operating period. State the reciprocal when reporting energy intensity rather than productivity. Sector guidance · Enterprise-Level Indicators for Resource Productivity and Pollution Intensity Confirm matching energy and pumped volume readings, meter boundaries and operating conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-010DP22 | Meter replacement Schedule verification of suspect customer and bulk meters Inputs and examplePurpose Identify overdue meter-verification cases. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — meter replacement, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — meter replacement. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A late verification does not prove meter error or justify changing a bill. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Water Safety Plan Manual, second edition Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-012DP22 | Source security Compare alternative sources under seasonal stress Inputs and examplePurpose Compare seasonal supply choices using tested yield, quality, rights and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Improve existing-source management, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Improve existing-source management. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve management of the existing source.; Resource needs and adverse effects = Needs dependable yield, water quality, demand and operating evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Source yield; demand; quality; drought exposure; treatment costs; permissions. Map context. No map inserted into this decision example Limits A budget balance does not establish a safe or dependable source. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Water Safety Plan Manual, second edition Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-013DP22 | Connection requests Prioritize delayed service-connection applications Inputs and examplePurpose Identify service-connection applications past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — connection requests, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — connection requests. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A deadline does not establish eligibility or approve a connection. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-014DP22 | Customer complaints Escalate unresolved water and sanitation complaints Inputs and examplePurpose Identify unresolved water and sanitation complaints past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — customer complaints, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — customer complaints. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish severity or a safe resolution. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-015DP22 | Chemical supply Prevent treatment interruptions from chemical shortages Inputs and examplePurpose Check usable treatment chemicals against commitments and matching deliveries. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — chemical supply, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg chemical]; Quarantined stock [kg chemical]; Expired stock [kg chemical]; Committed usable stock [kg chemical]; Additional demand [kg chemical]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg chemical; kg chemical) Worked example. Fictional 2025 example. Laggala Pallegama — chemical supply. Physical stock = 1,200 kg chemical; Quarantined stock = 100 kg chemical; Expired stock = 50 kg chemical; Committed usable stock = 740 kg chemical; Additional demand = 500 kg chemical; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg chemical; Additional demand gap = 190 kg chemical. Interpretation: Uncommitted usable stock: 310 kg chemical. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg chemical; Additional demand gap = 189 kg chemical. Interpretation: Uncommitted usable stock: 311 kg chemical. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Quantity alone does not establish product condition, suitability or delivery certainty. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-016DP22 | Wastewater treatment Investigate effluent performance against permit conditions Inputs and examplePurpose Check supplied effluent results against their cited method and permit basis. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — wastewater treatment, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [mg/L]; Example lower comparison bound [mg/L]; Example upper comparison bound [mg/L]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (mg/L) Worked example. Fictional 2025 example. Laggala Pallegama — wastewater treatment. Parameter and applicable use = Effluent BOD5; Measured result = 38 mg/L; Example lower comparison bound = 0 mg/L; Example upper comparison bound = 30 mg/L; Original and limit unit = mg/L; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 38 mg/L. Interpretation: The supplied Effluent BOD5 result is 38 mg/L. Its stated comparison range is 0 to 30 mg/L. Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 38.38; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 38.38 mg/L. Interpretation: The supplied Effluent BOD5 result is 38.38 mg/L. Its stated comparison range is 0 to 30 mg/L. Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits An example comparison does not establish legal compliance or a pollution cause. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Effluent limit selection by receiving environment Select the applicable effluent schedule and limit using the discharge destination, parameter and unit. Sector guidance · Gazette No. 2264/17, amended effluent standards Confirm the permit's actual conditions and the current schedule. Do not apply an ambient-water threshold to a discharge. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP22-018DP22 | Capital investments Compare water-service investment alternatives Inputs and examplePurpose Compare water-service cash-flow scenarios under the stated discount assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value alone does not establish service benefit or investment authority. Water utility engineer, quality specialist and service/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP23-001DP23 | Geological constraints Refer proposed sites overlapping geological constraints Inputs and examplePurpose Check reported proposal overlap with the cited geological constraint. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — geological constraints, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — geological constraints. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Reported hectares do not establish a site's engineering suitability or permission. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Landslide Clearance for Construction in Landslide Prone Areas Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-004DP23 | Map revisions Reassess site screening after geological-map changes Inputs and examplePurpose Compare reported geological-map class areas between source editions. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — map revisions, the default output explains Check the matching source records before interpreting the change. Changing Earlier/source value produces Check the matching source records before interpreting the change. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [affected sites]; Later/comparison value [affected sites] Result: Difference; Relative change (affected sites; %) Worked example. Fictional 2025 example. Laggala Pallegama — map revisions. Earlier/source value = 100 affected sites; Later/comparison value = 90 affected sites. Results: Difference = -10 affected sites; Relative change = -10 %. Interpretation: Difference: -10 affected sites. Next check: Check the matching source records before interpreting the change. Changed input. Change Earlier/source value = 101. Result: Difference = -11 affected sites; Relative change = -10.891 %. Interpretation: Difference: -11 affected sites. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits An area change does not identify every parcel needing a new site appraisal. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-005DP23 | Mining licenses Refer complete mining applications for authorized determination Inputs and examplePurpose Check the documents needed for an authorised mining-application review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — mining licenses, the default output explains Obtain the missing evidence listed below. Changing Application, Application evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Application remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Application; Application evidence reference; mineral; mineral evidence reference; location; location evidence reference; land rights; land rights evidence reference; current conditions; current conditions evidence reference; environmental approval; environmental approval evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — mining licenses. Application = Missing; Application evidence reference = ; mineral = Documented; mineral evidence reference = Sample Laggala Pallegama field register / 2025; location = Documented; location evidence reference = Sample Laggala Pallegama field register / 2025; land rights = Documented; land rights evidence reference = Sample Laggala Pallegama field register / 2025; current conditions = Documented; current conditions evidence reference = Sample Laggala Pallegama field register / 2025; environmental approval = Documented; environmental approval evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this mining licenses case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Application = Documented; Application evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle mining licenses. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Application. The required evidence is incomplete for this mining licenses case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Application: Missing. Map context. No map inserted into this decision example Limits The example does not grant a mineral licence or extraction right. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Industrial-mineral application evidence For industrial mineral mining, check the detailed exploration report and relevant documents before referral. Confirm the licence type, current submission list, environmental evidence and legal determination. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-006DP23 | Extraction monitoring Investigate extraction differing from authorized quantities Inputs and examplePurpose Compare reported extraction with matching authorised quantities and periods. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — extraction monitoring, the default output explains Check the matching records and reasons for the difference. Changing Planned value produces Check the matching records and reasons for the difference. Missing Planned value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned value [m³]; Observed value [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — extraction monitoring. Planned value = 100 m³; Observed value = 90 m³. Results: Difference = -10 m³; Relative change = -10 %. Interpretation: Difference: -10 m³. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned value = 101. Result: Difference = -11 m³; Relative change = -10.891 %. Interpretation: Difference: -11 m³. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned value. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A numerical difference is not a final determination of unauthorised extraction. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. Capture the mineral and quantity extracted against the renewal period and unit in Form 11. Compare those quantities with the applicable licence and period before escalating a variance. Geological Survey and Mines Bureau · Artisanal Mining Licence Renewal, Form 11. Section on minerals mined or removed from the mine or quarry. Confirm licence type, the authorized amount and any approved changes before interpreting the difference. Calculation reference. International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Licensing Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-008DP23 | River sand Identify extraction proposals needing hydrological and ecological review Inputs and examplePurpose Check reported extraction overlap with cited hydrological and ecological constraints. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — river sand, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — river sand. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Overlap is a referral input, not proof of impact or permission status. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Environmental Impact Assessment Procedure in Sri Lanka Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-011DP23 | Mineral resources Prioritize exploration using evidence and feasibility constraints Inputs and examplePurpose Compare exploration approaches using geological evidence, access and feasibility constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Detailed surface investigation, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Detailed surface investigation. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate the surface geology in detail.; Resource needs and adverse effects = Needs a defined question, access, mapping scale and sampling strategy.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Geological evidence; sample results; access; infrastructure; costs; restrictions. Map context. No map inserted into this decision example Limits Cost and stated benefits do not establish a mineral resource. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-012DP23 | Groundwater interactions Review mining proposals affecting groundwater systems Inputs and examplePurpose Find missing groundwater and control evidence for a mining-proposal referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — groundwater interactions, the default output explains Obtain the missing evidence listed below. Changing Mine depth, Mine depth evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Mine depth remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Mine depth; Mine depth evidence reference; aquifer; aquifer evidence reference; pumping; pumping evidence reference; well network; well network evidence reference; baseline quality; baseline quality evidence reference; hydrogeological assessment; hydrogeological assessment evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — groundwater interactions. Mine depth = Missing; Mine depth evidence reference = ; aquifer = Documented; aquifer evidence reference = Sample Laggala Pallegama field register / 2025; pumping = Documented; pumping evidence reference = Sample Laggala Pallegama field register / 2025; well network = Documented; well network evidence reference = Sample Laggala Pallegama field register / 2025; baseline quality = Documented; baseline quality evidence reference = Sample Laggala Pallegama field register / 2025; hydrogeological assessment = Documented; hydrogeological assessment evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this groundwater interactions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Mine depth = Documented; Mine depth evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle groundwater interactions. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Mine depth. The required evidence is incomplete for this groundwater interactions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Mine depth: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A checklist does not establish groundwater safety or allowable extraction. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Review environmental alternatives or mitigation Identify potential impacts, document relevant alternatives and review the measures proposed to reduce significant impacts. Confirm whether the EIA process applies and obtain the competent authority’s scope and conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-013DP23 | Laboratory services Prioritize pending mineral and material analyses Inputs and examplePurpose Identify mineral-analysis cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — laboratory services, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — laboratory services. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish analytical priority or result validity. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Laboratory Services Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-014DP23 | Sample integrity Resolve analytical discrepancies before resource assessment Inputs and examplePurpose Compare mineral-analysis measurements under matching units and definitions. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — sample integrity, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [mg/kg]; Independent comparison measurement [mg/kg]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (mg/kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — sample integrity. Original source measurement = 100 mg/kg; Independent comparison measurement = 90 mg/kg; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable mg/kg measure; same input scope. Results: Difference = -10 mg/kg; Relative change = -10 %. Interpretation: Difference: -10 mg/kg. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 mg/kg; Relative change = -10.891 %. Interpretation: Difference: -11 mg/kg. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A discrepancy needs laboratory and source checks before resource interpretation. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Laboratory Services Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-015DP23 | Transport permissions Check mineral transport documents against authorized sources Inputs and examplePurpose Check transport records against their stated source and authority references. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — transport permissions, the default output explains Obtain the missing evidence listed below. Changing Shipment, Shipment evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Shipment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Shipment; Shipment evidence reference; source license; source license evidence reference; mineral; mineral evidence reference; quantity; quantity evidence reference; route; route evidence reference; validity; validity evidence reference; required documents; required documents evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — transport permissions. Shipment = Missing; Shipment evidence reference = ; source license = Documented; source license evidence reference = Sample Laggala Pallegama field register / 2025; mineral = Documented; mineral evidence reference = Sample Laggala Pallegama field register / 2025; quantity = Documented; quantity evidence reference = Sample Laggala Pallegama field register / 2025; route = Documented; route evidence reference = Sample Laggala Pallegama field register / 2025; validity = Documented; validity evidence reference = Sample Laggala Pallegama field register / 2025; required documents = Documented; required documents evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this transport permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Shipment = Documented; Shipment evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle transport permissions. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Shipment. The required evidence is incomplete for this transport permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Shipment: Missing. Map context. No map inserted into this decision example Limits The example does not authenticate a permit or authorise transport. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Mineral transport source check Check the applicable source licence, mine, mineral, quantity and destination against the transport application. Sector guidance · Licensing Confirm the current form, any trading licence, transport conditions and authorization with GSMB. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-016DP23 | Mine inspections Schedule inspections according to approved risk priorities Inputs and examplePurpose Check inspection dates and resources against the documented priorities and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — mine inspections, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — mine inspections. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The prototype does not invent a risk ranking or assign inspectors. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Licensing Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-017DP23 | Revenue reconciliation Investigate differences in extraction-related payable and recorded receipts Inputs and examplePurpose Compare reported extraction-related amounts payable with matching recorded receipts. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — revenue reconciliation, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [LKR]; Independent comparison measurement [LKR]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (LKR; %) Worked example. Fictional 2025 example. Laggala Pallegama — revenue reconciliation. Original source measurement = 100 LKR; Independent comparison measurement = 90 LKR; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable LKR measure; same input scope. Results: Difference = -10 LKR; Relative change = -10 %. Interpretation: Difference: -10 LKR. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 LKR; Relative change = -10.891 %. Interpretation: Difference: -11 LKR. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A difference requires reconciliation before determining a debt or irregularity. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. Match the licence and quarter in Form 14 to the supporting royalty and payment records before comparing amounts. Geological Survey and Mines Bureau · Mining Royalty Return, Form 14. Regulation 33, licence, quarter and royalty return fields. Verify the applicable royalty basis and the payment evidence with GSMB before treating a variance as payable. Calculation reference. International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Licensing Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-019DP23 | Resource estimates Require reproducible mineral-resource estimation evidence Inputs and examplePurpose Check whether supplied resource-estimation inputs reproduce the stated result. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — resource estimates, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [tonnes]; Independently reproduced value [tonnes]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [tonnes]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (tonnes; %) Worked example. Fictional 2025 example. Laggala Pallegama — resource estimates. Earlier/source value = 100 tonnes; Independently reproduced value = 90 tonnes; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable tonnes measure; same input scope; Documented absolute comparison tolerance = 0.01 tonnes; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 tonnes; Relative change = -10 %. Interpretation: Difference: -10 tonnes. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 tonnes; Relative change = -10.891 %. Interpretation: Difference: -11 tonnes. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Reproduction is not a resource certification or a validation of geological assumptions. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP23-020DP23 | Geological catalogue Improve discoverability and provenance of geological records Inputs and examplePurpose Find missing source and edition details in geological records. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — geological catalogue, the default output explains Obtain the missing evidence listed below. Changing Map ID, Map ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Map ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Map ID; Map ID evidence reference; scale; scale evidence reference; survey date; survey date evidence reference; lithology definitions; lithology definitions evidence reference; owner; owner evidence reference; access rights; access rights evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — geological catalogue. Map ID = Missing; Map ID evidence reference = ; scale = Documented; scale evidence reference = Sample Laggala Pallegama field register / 2025; survey date = Documented; survey date evidence reference = Sample Laggala Pallegama field register / 2025; lithology definitions = Documented; lithology definitions evidence reference = Sample Laggala Pallegama field register / 2025; owner = Documented; owner evidence reference = Sample Laggala Pallegama field register / 2025; access rights = Documented; access rights evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this geological catalogue case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Map ID = Documented; Map ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle geological catalogue. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Map ID. The required evidence is incomplete for this geological catalogue case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Map ID: Missing. Map context. No map inserted into this decision example Limits Better metadata do not establish analytical quality or publication rights. Geologist, mining/environmental specialist and licensing reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · ISO 19157-1:2023 Geographic information Data quality Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-001DP24 | Land applications Prioritize unresolved state-land applications Inputs and examplePurpose Identify state-land applications past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — land applications, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — land applications. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits Age does not establish eligibility, legal rights or an allocation priority. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Department services and land administration Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-002DP24 | Lease reviews Schedule lease and permit reviews before due dates Inputs and examplePurpose Check lease-review tasks against due dates, resources and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — lease reviews, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — lease reviews. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not renew a lease or assign an officer. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Department services and land administration Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-004DP24 | Processing performance Address delays in administrative land requests Inputs and examplePurpose Identify administrative land requests past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — processing performance, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — processing performance. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A deadline does not authorise a determination. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Department services and land administration Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-006DP24 | Boundary reconciliation Resolve conflicting state-land parcel records Inputs and examplePurpose Compare conflicting parcel-area measurements and source definitions. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — boundary reconciliation, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [ha]; Independent comparison measurement [ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — boundary reconciliation. Original source measurement = 100 ha; Independent comparison measurement = 90 ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable ha measure; same input scope. Results: Difference = -10 ha; Relative change = -10 %. Interpretation: Difference: -10 ha. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 ha; Relative change = -10.891 %. Interpretation: Difference: -11 ha. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits An area discrepancy does not establish the authoritative legal boundary. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Electronic State Land Information Management System Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-010DP24 | Succession cases Refer succession and transfer requests for determination Inputs and examplePurpose Check the source documents for a succession or transfer referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — succession cases, the default output explains Obtain the missing evidence listed below. Changing Permit, Permit evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Permit remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Permit; Permit evidence reference; applicant evidence; applicant evidence evidence reference; legal documents; legal documents evidence reference; claims; claims evidence reference; current rules; current rules evidence reference; objections; objections evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — succession cases. Permit = Missing; Permit evidence reference = ; applicant evidence = Documented; applicant evidence evidence reference = Sample Laggala Pallegama field register / 2025; legal documents = Documented; legal documents evidence reference = Sample Laggala Pallegama field register / 2025; claims = Documented; claims evidence reference = Sample Laggala Pallegama field register / 2025; current rules = Documented; current rules evidence reference = Sample Laggala Pallegama field register / 2025; objections = Documented; objections evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this succession cases case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Permit = Documented; Permit evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle succession cases. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Permit. The required evidence is incomplete for this succession cases case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Permit: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not determine succession or transfer ownership. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Successor nomination form check For the stated deed or grant route, check the required nomination form and supporting title record before referral. Sector guidance · Department services and land administration Confirm the applicable instrument and current succession rules. A form check does not settle competing claims. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S29, S30 Context alone does not validate the formula. |
| DEC-DP24-011DP24 | Public-purpose land Compare suitable state parcels for public facilities Inputs and examplePurpose Compare proposed public-facility parcels using rights, services and site constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Reuse a serviced state parcel, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Reuse a serviced state parcel. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Reuse the serviced state parcel.; Resource needs and adverse effects = Needs confirmed rights, availability, service capacity and site suitability.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Parcel availability; service need; constraints; access; tenure; costs; alternatives. Map context. No map inserted into this decision example Limits Budget and stated benefits do not establish land availability or permission. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Guidelines for Land-Use Planning Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-013DP24 | Land reservations Review allocation requests overlapping protected reservations Inputs and examplePurpose Check reported allocation overlap with the cited reservation boundary. Output Comparison table Next step Prepare overlap review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — land reservations, the default output explains Check the matching footprint, source boundary and applicable conditions. Changing Assessed footprint or frame produces Check the matching footprint, source boundary and applicable conditions. Missing Assessed footprint or frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Assessed footprint or frame [ha]; Reported common overlap, counted once [ha]; Boundary edition; Constraint definition; Matching source frame, boundary and period evidence; Area/count source and matching definition reference Result: Overlap share; Overlapping area (%; ha) Worked example. Fictional 2025 example. Laggala Pallegama — land reservations. Assessed footprint or frame = 75 ha; Reported common overlap, counted once = 18 ha; Boundary edition = Sample boundary1; Constraint definition = Sample constraint class; Matching source frame, boundary and period evidence = Provided; Area/count source and matching definition reference = Fictional matched survey return / edition 1. Results: Overlap share = 24 %; Overlapping area = 18 ha. Interpretation: 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 check: Check the matching footprint, source boundary and applicable conditions. Changed input. Change Assessed footprint or frame = 75.75. Result: Overlap share = 23.762 %; Overlapping area = 18 ha. Interpretation: The supplied overlap is 18 ha within the 75.75 ha assessed footprint, or 23.762%. Check the cited boundary and source records before interpreting the overlap. Next check: Check the matching footprint, source boundary and applicable conditions. Missing input. Omit Assessed footprint or frame. No usable result. Proposal footprint Next check: Correct or obtain the missing input records. Information still needed: Proposal footprint. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A supplied overlap does not establish the legal boundary or permission. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Calculate the share of a footprint intersecting constraints Intersect the comparable geometries and divide the overlap area by the footprint area. Merge overlapping constraint areas before totaling the combined footprint share. Sector guidance · Guidelines for Land-Use Planning Confirm the coordinate system, official boundaries, permissions, accuracy and qualifying constraints. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-017DP24 | Land-use effectiveness Review whether allocated land serves approved purposes Inputs and examplePurpose Compare allocated hectares with documented hectares serving the same stated purpose. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — land-use effectiveness, the default output explains Check the matching records and reasons for the difference. Changing Allocated hectares for the stated approved purpose produces Check the matching records and reasons for the difference. Missing Allocated hectares for the stated approved purpose remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Allocated hectares for the stated approved purpose [ha]; Matching hectares with evidence of that same use [ha] Result: Difference; Relative change (ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — land-use effectiveness. Allocated hectares for the stated approved purpose = 100 ha; Matching hectares with evidence of that same use = 90 ha. Results: Difference = -10 ha; Relative change = -10 %. Interpretation: Difference: -10 ha. Next check: Check the matching records and reasons for the difference. Changed input. Change Allocated hectares for the stated approved purpose = 101. Result: Difference = -11 ha; Relative change = -10.891 %. Interpretation: Difference: -11 ha. Next check: Check the matching records and reasons for the difference. Missing input. Omit Allocated hectares for the stated approved purpose. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A difference requires source checks before determining non-compliance. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Department services and land administration Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP24-020DP24 | Office capacity Allocate case-processing capacity across land offices Inputs and examplePurpose Compare case-processing workload with usable staff time. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — office capacity, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — office capacity. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity does not establish competence, appointment authority or case priority. State-land officer, legal/document reviewer and survey professional | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-001DP25 | Price spreads Investigate large comparable farmgate wholesale and retail spreads Inputs and examplePurpose Compare matching purchase and sale quotations after stated costs and mass loss. Output Comparison table Next step Prepare quote comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Quoted spread = sell−buy. Net scenario return per purchased kg = sell×(1−loss%/100)−buy−matching transfer costs. Checks For Laggala Pallegama — price spreads, the default output explains Check matching product grades, quantities, losses and quote periods. Changing Comparable purchase quotation produces Check matching product grades, quantities, losses and quote periods. Missing Comparable purchase quotation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable purchase quotation [LKR/kg]; Comparable selling quotation [LKR/kg]; Non-overlapping transfer costs [LKR/kg]; Expected saleable mass loss [%]; Product, grade and price basis Result: Quoted net return per purchased kg; Unadjusted quoted spread (LKR/kg; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — price spreads. Comparable purchase quotation = 180 LKR/kg; Comparable selling quotation = 222 LKR/kg; Non-overlapping transfer costs = 20 LKR/kg; Expected saleable mass loss = 5 %; Product, grade and price basis = Tomato / same stated grade / per purchased kilogram. Results: Quoted net return per purchased kg = 10.9 LKR/kg; Unadjusted quoted spread = 42 LKR/kg. Interpretation: Quoted net return per purchased kg: 10.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Changed input. Change Comparable purchase quotation = 181. Result: Quoted net return per purchased kg = 9.9 LKR/kg; Unadjusted quoted spread = 41 LKR/kg. Interpretation: Quoted net return per purchased kg: 9.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Missing input. Omit Comparable purchase quotation. No usable result. Comparable purchase quotation Next check: Correct or obtain the missing input records. Information still needed: Comparable purchase quotation. Map context. No map inserted into this decision example Limits A spread does not establish excess profit, market power or an actual realised return. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Same-period market price spread Subtract the preceding market-stage price from the next-stage price using observations at the same point in time. Sector guidance · Daily Food Commodities Bulletin, 30 October 2026 Match crop, grade, unit, time and supply chain. Confirm loss, transfer costs and threshold separately. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-002DP25 | Price volatility Prioritize commodities with unusual price variability Inputs and examplePurpose Review variation in comparable commodity-price observations. Output Time-series chart and observation table Next step Prepare variation report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — price volatility, the default output explains Check the comparable series and the reason for its variation. Changing Comparable observation produces Check the comparable series and the reason for its variation. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [LKR/kg] Result: Observed value (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — price volatility. Comparable observation = 104 LKR/kg. Results: Observed value = 104 LKR/kg. Interpretation: Observed value: 104 LKR/kg. Next check: Check the comparable series and the reason for its variation. Changed input. Change Comparable observation = 105. Result: Observed value = 105 LKR/kg. Interpretation: Observed value: 105 LKR/kg. Next check: Check the comparable series and the reason for its variation. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7; cv = 6.306 Map context. No map inserted into this decision example Limits A short series does not forecast prices or establish market instability. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample coefficient of variation Sample coefficient of variation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP25-003DP25 | Seasonal markets Inform seasonal marketing using comparable historical patterns Inputs and examplePurpose Review historical prices for the same commodity, grade and period basis. Output Time-series chart and observation table Next step Prepare trend report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — seasonal markets, the default output explains Check source and period comparability before using the trend. Changing Comparable observation produces Check source and period comparability before using the trend. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [LKR/kg] Result: Observed value (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — seasonal markets. Comparable observation = 104 LKR/kg. Results: Observed value = 104 LKR/kg. Interpretation: Observed value: 104 LKR/kg. Next check: Check source and period comparability before using the trend. Changed input. Change Comparable observation = 105. Result: Observed value = 105 LKR/kg. Interpretation: Observed value: 105 LKR/kg. Next check: Check source and period comparability before using the trend. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7 Map context. No map inserted into this decision example Limits A few annual observations do not establish within-year seasonality or a forecast. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP25-004DP25 | Market comparisons Identify markets requiring closer price-distribution study Inputs and examplePurpose Compare the spread of supplied matching price observations. Output Time-series chart and observation table Next step Prepare distribution report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — market comparisons, the default output explains Check the observations, spread and coverage of the selected series. Changing Comparable observation produces Check the observations, spread and coverage of the selected series. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [LKR/kg] Result: Observed value (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — market comparisons. Comparable observation = 104 LKR/kg. Results: Observed value = 104 LKR/kg. Interpretation: Observed value: 104 LKR/kg. Next check: Check the observations, spread and coverage of the selected series. Changed input. Change Comparable observation = 105. Result: Observed value = 105 LKR/kg. Interpretation: Observed value: 105 LKR/kg. Next check: Check the observations, spread and coverage of the selected series. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7; cv = 6.306 Map context. No map inserted into this decision example Limits A small example distribution does not establish a representative market distribution. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample standard deviation Sample standard deviation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP25-006DP25 | Food affordability Compare documented food-basket costs across locations Inputs and examplePurpose Compare costs of the same specified rice, dhal and sugar basket. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Basket cost = rice kg × rice LKR/kg + red-dhal kg × red-dhal LKR/kg + white-sugar kg × white-sugar LKR/kg. Compare locations only for the same quantities, product specifications, currency and price period. Checks For Laggala Pallegama price-basket scenario, the default output explains Check matching product grades and price sources. Changing Comparable raw-rice price produces Check matching product grades and price sources. Missing Raw rice in the stated basket remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Raw rice in the stated basket [kg]; Comparable raw-rice price [LKR/kg]; Red dhal in the stated basket [kg]; Comparable red-dhal price [LKR/kg]; White sugar in the stated basket [kg]; Comparable white-sugar price [LKR/kg] Result: Stated three-item basket cost (LKR) Worked example. Fictional 2025 example. Laggala Pallegama price-basket scenario. Raw rice in the stated basket = 5 kg; Comparable raw-rice price = 220 LKR/kg; Red dhal in the stated basket = 1 kg; Comparable red-dhal price = 350 LKR/kg; White sugar in the stated basket = 1 kg; Comparable white-sugar price = 290 LKR/kg. Results: Stated three-item basket cost = 1,740 LKR. Interpretation: 5 kg rice × 220 + 1 kg red dhal × 350 + 1 kg white sugar × 290 = 1740.00 LKR. The quantities and prices are labelled scenario assumptions. Next check: Check matching product grades and price sources. Changed input. Change Comparable raw-rice price = 240. Result: Stated three-item basket cost = 1,840 LKR. Interpretation: 5 kg rice × 240 + 1 kg red dhal × 350 + 1 kg white sugar × 290 = 1840.00 LKR. The quantities and prices are labelled scenario assumptions. Next check: Check matching product grades and price sources. Missing input. Omit Raw rice in the stated basket. No usable result. Raw rice in the stated basket Next check: Correct or obtain the missing input records. Information still needed: Raw rice in the stated basket. Map context. No map inserted into this decision example Limits The fictional three-item basket is not an official cost-of-living measure. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Price a common basket or set of quantities Multiply comparable quantities by their matching prices and sum the component costs. Sector guidance · Consumer Price Index Manual Concepts and Methods 2020 Confirm item, quantity, price unit, market and period. Keep the basket fixed for comparisons. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-007DP25 | Farmer returns Assess enterprise margins for policy research Inputs and examplePurpose Compare farm-enterprise gross margins under matching output and cost conventions. Output Comparison table Next step Prepare margin comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Gross margin = saleable output × realized price − variable costs. Divide by matching hectares for margin/ha; variable-cost break-even price = variable costs / output. Checks For Laggala Pallegama — farmer returns, the default output explains Review the prices, quantities and costs behind the margin. Changing Saleable output produces Review the prices, quantities and costs behind the margin. Missing Saleable output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable output [kg]; Realized price [LKR/kg]; Variable costs [LKR]; Matching crop area [ha]; Crop and saleable-output basis Result: Enterprise gross margin; Gross margin per hectare; Variable-cost break-even price (LKR; LKR/ha; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — farmer returns. Saleable output = 4,500 kg; Realized price = 110 LKR/kg; Variable costs = 360,000 LKR; Matching crop area = 1 ha; Crop and saleable-output basis = Paddy rough rice / fictional one-hectare crop enterprise / same season. Results: Enterprise gross margin = 135,000 LKR; Gross margin per hectare = 135,000 LKR/ha; Variable-cost break-even price = 80 LKR/kg. Interpretation: The supplied 4,500 kg at 110 LKR/kg gives 495,000 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,000 LKR. Next check: Review the prices, quantities and costs behind the margin. Changed input. Change Saleable output = 4,501. Result: Enterprise gross margin = 135,110 LKR; Gross margin per hectare = 135,110 LKR/ha; Variable-cost break-even price = 79.982 LKR/kg. Interpretation: The supplied 4,501 kg at 110 LKR/kg gives 495,110 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,110 LKR. Next check: Review the prices, quantities and costs behind the margin. Missing input. Omit Saleable output. No usable result. Saleable output Next check: Correct or obtain the missing input records. Information still needed: Saleable output. Map context. No map inserted into this decision example Limits Gross margin excludes some fixed and opportunity costs and does not establish profit. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Gross margin per hectare Gross margin per hectare = gross benefit per hectare − variable costs per hectare. Sector guidance · Farm Management for Asia A Systems Approach The report demonstrates the paddy calculation. Confirm crop budgets, price, variable-cost boundaries and any local decision threshold. The report does not establish a break-even threshold. Implementation: prototype |
| DEC-DP25-008DP25 | Marketing losses Identify value-chain stages requiring loss studies Inputs and examplePurpose Reconcile input mass with saleable output, by-products, transfers and stock. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — marketing losses, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — marketing losses. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unaccounted balance does not establish where or why physical loss occurred. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-009DP25 | Market integration Investigate persistent differences between connected markets Inputs and examplePurpose Compare connected-market quotations after stated transport costs and losses. Output Comparison table Next step Prepare quote comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Quoted spread = sell−buy. Net scenario return per purchased kg = sell×(1−loss%/100)−buy−matching transfer costs. Checks For Laggala Pallegama — market integration, the default output explains Check matching product grades, quantities, losses and quote periods. Changing Comparable purchase quotation produces Check matching product grades, quantities, losses and quote periods. Missing Comparable purchase quotation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable purchase quotation [LKR/kg]; Comparable selling quotation [LKR/kg]; Non-overlapping transfer costs [LKR/kg]; Expected saleable mass loss [%]; Product, grade and price basis Result: Quoted net return per purchased kg; Unadjusted quoted spread (LKR/kg; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — market integration. Comparable purchase quotation = 180 LKR/kg; Comparable selling quotation = 222 LKR/kg; Non-overlapping transfer costs = 20 LKR/kg; Expected saleable mass loss = 5 %; Product, grade and price basis = Tomato / same stated grade / per purchased kilogram. Results: Quoted net return per purchased kg = 10.9 LKR/kg; Unadjusted quoted spread = 42 LKR/kg. Interpretation: Quoted net return per purchased kg: 10.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Changed input. Change Comparable purchase quotation = 181. Result: Quoted net return per purchased kg = 9.9 LKR/kg; Unadjusted quoted spread = 41 LKR/kg. Interpretation: Quoted net return per purchased kg: 9.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Missing input. Omit Comparable purchase quotation. No usable result. Comparable purchase quotation Next check: Correct or obtain the missing input records. Information still needed: Comparable purchase quotation. Map context. No map inserted into this decision example Limits A price difference does not prove arbitrage feasibility or market inefficiency. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Same-period market price spread Subtract the preceding market-stage price from the next-stage price using observations at the same point in time. Sector guidance · Daily Food Commodities Bulletin, 30 October 2026 Match crop, grade, unit, time and supply chain. Confirm loss, transfer costs and threshold separately. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-010DP25 | Policy evaluation Evaluate agricultural policy outcomes with credible comparisons Inputs and examplePurpose Compare enterprise-income changes in the supplied treatment and comparison records. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — policy evaluation, the default output explains Obtain the missing evidence listed below. Changing Treatment Real enterprise income on stated price basis before produces Obtain the missing evidence listed below. Missing Treatment Real enterprise income on stated price basis before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Real enterprise income on stated price basis before [LKR/ha]; Treatment Real enterprise income on stated price basis after [LKR/ha]; Comparison Real enterprise income on stated price basis before [LKR/ha]; Comparison Real enterprise income on stated price basis after [LKR/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR/ha) Worked example. Fictional 2025 example. Laggala Pallegama — policy evaluation. Treatment Real enterprise income on stated price basis before = 420,000 LKR/ha; Treatment Real enterprise income on stated price basis after = 590,000 LKR/ha; Comparison Real enterprise income on stated price basis before = 390,000 LKR/ha; Comparison Real enterprise income on stated price basis after = 460,000 LKR/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Real enterprise income on stated price basis /example matching definition1. Results: Difference in changes = 100,000 LKR/ha. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Real enterprise income on stated price basis before = 420,001. Result: Difference in changes = 99,999 LKR/ha. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Real enterprise income on stated price basis before. No usable result. Treatment Real enterprise income on stated price basis before Next check: Correct or obtain the missing input records. Information still needed: Treatment Real enterprise income on stated price basis before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a causal policy effect. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP25-011DP25 | Input markets Investigate shifts in agricultural input expenditure Inputs and examplePurpose Compare expenditure for the same specified input quantity and price basis. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Specified quantity × comparable unit price. Sum only non-overlapping items from the same basket specification, location and price period. Checks For Laggala Pallegama — input markets, the default output explains Review cost components and comparable verified outputs. Changing Specified basket/input quantity produces Review cost components and comparable verified outputs. Missing Specified basket/input quantity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Specified basket/input quantity [kg]; Comparable unit price [LKR/kg]; Item, grade and basket specification Result: Item expenditure (LKR) Worked example. Fictional 2025 example. Laggala Pallegama — input markets. Specified basket/input quantity = 50 kg; Comparable unit price = 210 LKR/kg; Item, grade and basket specification = Urea / stated same grade and bag basis. Results: Item expenditure = 10,500 LKR. Interpretation: Item expenditure: 10,500 LKR. Next check: Review cost components and comparable verified outputs. Changed input. Change Specified basket/input quantity = 50.5. Result: Item expenditure = 10,605 LKR. Interpretation: Item expenditure: 10,605 LKR. Next check: Review cost components and comparable verified outputs. Missing input. Omit Specified basket/input quantity. No usable result. Specified basket/input quantity Next check: Correct or obtain the missing input records. Information still needed: Specified basket/input quantity. Map context. No map inserted into this decision example Limits An expenditure change does not separate price, quantity and product-quality effects automatically. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Price a common basket or set of quantities Multiply comparable quantities by their matching prices and sum the component costs. Sector guidance · Consumer Price Index Manual Concepts and Methods 2020 Confirm item, quantity, price unit, market and period. Keep the basket fixed for comparisons. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-013DP25 | Land and labour Review farm labour costs and labour-use differences Inputs and examplePurpose Compare cash labour cost and total recorded effort per matching hectare. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Cash cost/ha = hired days×cash wage/area. Total effort/ha=(hired+unpaid family days)/area. Do not value unpaid labour as zero opportunity cost. Checks For Laggala Pallegama — land and labour, the default output explains Check matching outputs, denominators and operating conditions. Changing Person-days worked produces Check matching outputs, denominators and operating conditions. Missing Person-days worked remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Person-days worked [person-days]; Cash wage per hired person-day [LKR/person-day]; Matching cultivated area [ha]; Unpaid family labour [person-days] Result: Cash labour cost per hectare; Total labour per hectare (LKR/ha; person-days/ha) Worked example. Fictional 2025 example. Laggala Pallegama — land and labour. Person-days worked = 45 person-days; Cash wage per hired person-day = 3,200 LKR/person-day; Matching cultivated area = 2 ha; Unpaid family labour = 12 person-days. Results: Cash labour cost per hectare = 72,000 LKR/ha; Total labour per hectare = 28.5 person-days/ha. Interpretation: Cash labour cost per hectare: 72,000 LKR/ha. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Person-days worked = 45.45. Result: Cash labour cost per hectare = 72,720 LKR/ha; Total labour per hectare = 28.725 person-days/ha. Interpretation: Cash labour cost per hectare: 72,720 LKR/ha. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Person-days worked. No usable result. Person-days worked Next check: Correct or obtain the missing input records. Information still needed: Person-days worked. Map context. No map inserted into this decision example Limits Unpaid family labour is effort and is not included as a cash wage payment. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Record farm labour by type and unit Keep family and hired labour separate and compare labour use and cost on a common area basis. Sector guidance · Cost of Production for Agricultural Products, basic concepts Confirm operation, area, person-day definition, wage rates and season. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-014DP25 | Food supply disruptions Prioritize research on documented market supply shocks Inputs and examplePurpose Compare reported supply observations with their matching reference values. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — food supply disruptions, the default output explains Check the unusual observation and its comparison basis. Changing Comparable reference value produces Check the unusual observation and its comparison basis. Missing Comparable reference value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable reference value [kg]; Later/comparison value [kg] Result: Difference; Relative change (kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — food supply disruptions. Comparable reference value = 100 kg; Later/comparison value = 90 kg. Results: Difference = -10 kg; Relative change = -10 %. Interpretation: Difference: -10 kg. Next check: Check the unusual observation and its comparison basis. Changed input. Change Comparable reference value = 101. Result: Difference = -11 kg; Relative change = -10.891 %. Interpretation: Difference: -11 kg. Next check: Check the unusual observation and its comparison basis. Missing input. Omit Comparable reference value. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits A difference needs source checks before identifying a shock or its cause. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Daily Food Commodities Bulletin, 30 October 2026 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-015DP25 | Storage investments Compare storage and handling options for perishables Inputs and examplePurpose Compare storage cash-flow scenarios under the stated investment and discount assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish avoided spoilage or investment suitability. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP25-017DP25 | Publication quality Resolve contradictory market observations before release Inputs and examplePurpose Compare conflicting market measurements with matching units, grades and periods. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — publication quality, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [LKR/kg]; Independent comparison measurement [LKR/kg]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (LKR/kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — publication quality. Original source measurement = 100 LKR/kg; Independent comparison measurement = 90 LKR/kg; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable LKR/kg measure; same input scope. Results: Difference = -10 LKR/kg; Relative change = -10 %. Interpretation: Difference: -10 LKR/kg. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 LKR/kg; Relative change = -10.891 %. Interpretation: Difference: -11 LKR/kg. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A difference does not identify which source should be corrected. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · Daily Food Commodities Bulletin, 30 October 2026 Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP25-020DP25 | Evidence reproducibility Independently reproduce agrarian research findings Inputs and examplePurpose Check whether supplied inputs reproduce a stated agrarian-research result. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — evidence reproducibility, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [LKR/ha]; Independently reproduced value [LKR/ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [LKR/ha]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (LKR/ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — evidence reproducibility. Earlier/source value = 100 LKR/ha; Independently reproduced value = 90 LKR/ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable LKR/ha measure; same input scope; Documented absolute comparison tolerance = 0.01 LKR/ha; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 LKR/ha; Relative change = -10 %. Interpretation: Difference: -10 LKR/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 LKR/ha; Relative change = -10.891 %. Interpretation: Difference: -11 LKR/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Arithmetic reproduction does not validate the research design or policy inference. Agricultural economist, market analyst and survey statistician | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-001DP26 | Export destinations Prioritize products and destination markets for support Inputs and examplePurpose Compare recorded export values by product and destination. Output Comparison table Next step Prepare composition report creates an unassigned draft that is visible and downloadable, not sent. Rule Compute export-value and quantity shares independently within compatible product and reporting frames; never add currency and kilograms. Checks For Pepper — India, the default output explains Check category definitions, coverage and the stated denominator. Changing Recorded export value produces Check category definitions, coverage and the stated denominator. Missing Recorded export value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded export value [LKR]; Matching export quantity [kg]; Product code, destination and grade Result: Export value; Value share; Quantity share (LKR; %; %) Worked example. Fictional 2025 example. Pepper — India. Recorded export value = 900,000 LKR; Matching export quantity = 500 kg; Product code, destination and grade = Pepper — India. Results: Export value = 900,000 LKR; Value share = 10.749 %; Quantity share = 17.986 %. Interpretation: Export value: 900,000 LKR. Next check: Check category definitions, coverage and the stated denominator. Changed input. Change Recorded export value = 900,001. Result: Export value = 900,001 LKR; Value share = 10.749 %; Quantity share = 17.986 %. Interpretation: Export value: 900,001 LKR. Next check: Check category definitions, coverage and the stated denominator. Missing input. Omit Recorded export value. No usable result. Recorded export value Next check: Correct or obtain the missing input records. Information still needed: Recorded export value. Selected-frame statistics. total = 8,372,500; hhi = 0.179 Map context. No map inserted into this decision example Limits Value shares do not establish market potential or the best support investment. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare export composition by value Report each product or destination’s value against the matching total and retain volume separately. Sector guidance · International Merchandise Trade Statistics 2010 Compilers Manual Confirm commodity codes, market, time period, currency and denominator before ranking support. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-002DP26 | Market dependence Identify excessive dependence on few export markets Inputs and examplePurpose Review concentration in the stated destination-market portfolio. Output Comparison table Next step Prepare concentration review creates an unassigned draft that is visible and downloadable, not sent. Rule Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Checks For India, the default output explains Review the complete portfolio, category definitions and exposure constraints. Changing Recorded export value in this distinct destination produces Review the complete portfolio, category definitions and exposure constraints. Missing Recorded export value in this distinct destination remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded export value in this distinct destination [LKR] Result: Category amount; Share of selected total (LKR; %) Worked example. Fictional 2025 example. India. Recorded export value in this distinct destination = 90,000,000 LKR. Results: Category amount = 90,000,000 LKR; Share of selected total = 45 %. Interpretation: Category amount: 90,000,000 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Changed input. Change Recorded export value in this distinct destination = 90,000,001. Result: Category amount = 90,000,001 LKR; Share of selected total = 45 %. Interpretation: Category amount: 90,000,001 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Missing input. Omit Recorded export value in this distinct destination. No usable result. Compatible category amount Next check: Correct or obtain the missing input records. Information still needed: Compatible category amount. Selected-frame statistics. total = 200,000,000; hhi = 0.289 Map context. No map inserted into this decision example Limits A concentration index does not establish buyer risk without a complete comparable portfolio. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required HHI concentration component HHI concentration component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP26-003DP26 | Growth opportunities Target product groups contributing to export growth Inputs and examplePurpose Compare matching export values between the stated periods. Output Comparison table Next step Prepare change comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Pepper export-value scenario, the default output explains Check the matching source records before interpreting the change. Changing Earlier/source value produces Check the matching source records before interpreting the change. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [LKR]; Later/comparison value [LKR] Result: Difference; Relative change (LKR; %) Worked example. Fictional 2025 example. Pepper export-value scenario. Earlier/source value = 8,500,000 LKR; Later/comparison value = 9,400,000 LKR. Results: Difference = 900,000 LKR; Relative change = 10.588 %. Interpretation: Difference: 900,000 LKR. Next check: Check the matching source records before interpreting the change. Changed input. Change Earlier/source value = 8,500,001. Result: Difference = 899,999 LKR; Relative change = 10.588 %. Interpretation: Difference: 899,999 LKR. Next check: Check the matching source records before interpreting the change. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Nominal growth does not separate price, volume, exchange-rate or composition effects. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Export earnings year-on-year change Growth (%) = 100 × (current export earnings − corresponding prior-year earnings) ÷ prior-year earnings. Sector guidance · Calculating Percent Changes Match product classification, currency and reporting period. Keep product growth separate from contribution to aggregate growth. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-004DP26 | Unit values Investigate changing export unit values Inputs and examplePurpose Compare export value per matching shipped kilogram. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Recorded export value / Export quantity on matching product basis, for the same product, process and period. Checks For Laggala Pallegama — unit values, the default output explains Check matching outputs, denominators and operating conditions. Changing Recorded export value produces Check matching outputs, denominators and operating conditions. Missing Recorded export value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded export value [LKR]; Export quantity on matching product basis [kg] Result: Output per resource (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — unit values. Recorded export value = 8,832,000 LKR; Export quantity on matching product basis = 4,500 kg. Results: Output per resource = 1,962.667 LKR/kg. Interpretation: Recorded export value: 8,832,000 LKR; Export quantity on matching product basis: 4,500 kg. This gives 1,962.667 LKR/kg. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Recorded export value = 8,832,001. Result: Output per resource = 1,962.667 LKR/kg. Interpretation: Recorded export value: 8,832,001 LKR; Export quantity on matching product basis: 4,500 kg. This gives 1,962.667 LKR/kg. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Recorded export value. No usable result. Recorded export value Next check: Correct or obtain the missing input records. Information still needed: Recorded export value. Map context. No map inserted into this decision example Limits A unit value is not a price index and may reflect changes in product mix. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Export unit value Export unit value Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP26-007DP26 | Trade promotion Compare proposed trade-promotion activities Inputs and examplePurpose Compare trade-promotion choices using product, buyer and resource evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Targeted buyer meetings, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Targeted buyer meetings. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Arrange targeted buyer meetings.; Resource needs and adverse effects = Needs matching products, verified buyers, access and follow-up capacity.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Target buyers; market demand; event costs; exporter readiness; expected outcomes. Map context. No map inserted into this decision example Limits Cost alone does not establish sales or additional export earnings. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-009DP26 | Export diversification Compare alternative products and markets under constraints Inputs and examplePurpose Compare product-market alternatives using their particular requirements and trade-offs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Pepper sales to India, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Pepper sales to India. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate pepper sales to India.; Resource needs and adverse effects = Needs product/grade demand, market-entry rules, landed costs and buyer evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Product-market options; demand; costs; readiness; risks; concentration. Map context. No map inserted into this decision example Limits A budget balance does not establish demand, competitiveness or access. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-012DP26 | Brand development Compare product branding and certification investments Inputs and examplePurpose Compare branding or certification cash-flow scenarios. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish the validity of a certification or a market benefit. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP26-014DP26 | Trade barriers Escalate unresolved exporter market-access cases Inputs and examplePurpose Identify exporter market-access cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — trade barriers, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — trade barriers. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age does not establish a market entitlement or a justified intervention. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Export Procedure and Logistics Requirements Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP26-020DP26 | Export policy impact Assess outcomes of export-development interventions Inputs and examplePurpose Compare enterprise outcomes in the supplied treatment and comparison periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — export policy impact, the default output explains Obtain the missing evidence listed below. Changing Treatment Comparable export value before produces Obtain the missing evidence listed below. Missing Treatment Comparable export value before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Comparable export value before [LKR]; Treatment Comparable export value after [LKR]; Comparison Comparable export value before [LKR]; Comparison Comparable export value after [LKR]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR) Worked example. Fictional 2025 example. Laggala Pallegama — export policy impact. Treatment Comparable export value before = 420,000 LKR; Treatment Comparable export value after = 590,000 LKR; Comparison Comparable export value before = 390,000 LKR; Comparison Comparable export value after = 460,000 LKR; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Comparable export value /example matching definition1. Results: Difference in changes = 100,000 LKR. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Comparable export value before = 420,001. Result: Difference in changes = 99,999 LKR. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Comparable export value before. No usable result. Treatment Comparable export value before Next check: Correct or obtain the missing input records. Information still needed: Treatment Comparable export value before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish an export-support effect. Export development adviser and market/compliance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP27-003DP27 | Service delays Prioritize enterprise assistance cases waiting longest Inputs and examplePurpose Identify enterprise-assistance cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — service delays, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — service delays. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish need, eligibility or a support priority. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP27-005DP27 | Business viability Refer enterprise plans for financial and market appraisal Inputs and examplePurpose Review enterprise cash-flow scenarios before financial and market appraisal. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value alone does not establish viability or approve finance. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP27-010DP27 | Business performance Review changes in enterprise outcomes after assistance Inputs and examplePurpose Compare enterprise outcomes across the supplied support and comparison records. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — business performance, the default output explains Obtain the missing evidence listed below. Changing Treatment Real enterprise sales on stated price basis before produces Obtain the missing evidence listed below. Missing Treatment Real enterprise sales on stated price basis before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Real enterprise sales on stated price basis before [LKR]; Treatment Real enterprise sales on stated price basis after [LKR]; Comparison Real enterprise sales on stated price basis before [LKR]; Comparison Real enterprise sales on stated price basis after [LKR]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR) Worked example. Fictional 2025 example. Laggala Pallegama — business performance. Treatment Real enterprise sales on stated price basis before = 420,000 LKR; Treatment Real enterprise sales on stated price basis after = 590,000 LKR; Comparison Real enterprise sales on stated price basis before = 390,000 LKR; Comparison Real enterprise sales on stated price basis after = 460,000 LKR; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Real enterprise sales on stated price basis /example matching definition1. Results: Difference in changes = 100,000 LKR. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Real enterprise sales on stated price basis before = 420,001. Result: Difference in changes = 99,999 LKR. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Real enterprise sales on stated price basis before. No usable result. Treatment Real enterprise sales on stated price basis before Next check: Correct or obtain the missing input records. Information still needed: Treatment Real enterprise sales on stated price basis before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits Differences do not establish that assistance caused the outcome. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP27-014DP27 | Business skills Prioritize training topics using verified capability gaps Inputs and examplePurpose Compare training approaches against the stated capability gaps. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Basic business records, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Basic business records. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve basic enterprise records.; Resource needs and adverse effects = Needs capability evidence, accessible delivery and practical follow-up.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Needs assessments; skills; course availability; prior training; adoption evidence. Map context. No map inserted into this decision example Limits Cost and attendance do not establish competence or the best training topic. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP27-016DP27 | Climate resilience Compare enterprise adaptation options Inputs and examplePurpose Compare enterprise-continuity choices using exposure and operating constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Protect critical equipment, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Protect critical equipment. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Protect the documented critical equipment.; Resource needs and adverse effects = Needs exposure, engineering, continuity and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Hazard exposure; business dependencies; adaptation costs; continuity benefits; constraints. Map context. No map inserted into this decision example Limits A stated benefit does not establish avoided losses or business resilience. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP27-017DP27 | Incubation capacity Allocate incubation services within facility and adviser limits Inputs and examplePurpose Compare incubation demand with usable facility and adviser capacity. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — incubation capacity, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [adviser hours]; Rated capacity for that period [adviser hours]; Unavailable or restricted capacity [adviser hours] Result: Usable capacity minus demand; Usable capacity (adviser hours; adviser hours) Worked example. Fictional 2025 example. Laggala Pallegama — incubation capacity. Demand in the selected period = 150 adviser hours; Rated capacity for that period = 180 adviser hours; Unavailable or restricted capacity = 45 adviser hours. Results: Usable capacity minus demand = -15 adviser hours; Usable capacity = 135 adviser hours. Interpretation: Usable capacity minus demand: -15 adviser hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 adviser hours; Usable capacity = 135 adviser hours. Interpretation: Usable capacity minus demand: -16 adviser hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish suitability or allocate a place. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP27-020DP27 | Programme effectiveness Select enterprise-support approaches for continuation or redesign Inputs and examplePurpose Compare continuation and redesign choices using outcome and exclusion evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Continue targeted mentoring, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Continue targeted mentoring. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Continue targeted mentoring.; Resource needs and adverse effects = Needs documented needs, mentor competence and follow-up outcomes.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Verified outcomes; costs; inclusion; unintended effects; context; evaluation evidence. Map context. No map inserted into this decision example Limits Budget alone does not establish which support approach should continue. Enterprise development adviser and finance/monitoring reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-004DP28 | Estate requests Resolve outstanding tenant-support requests Inputs and examplePurpose Identify tenant-support requests past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — estate requests, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — estate requests. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish operational urgency or a support entitlement. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · International Guidelines for Industrial Parks Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-005DP28 | Technology upgrades Compare industrial modernization alternatives Inputs and examplePurpose Compare modernisation cash flows under stated investment assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish technical feasibility or environmental suitability. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP28-006DP28 | Resource productivity Identify facilities with inefficient material and energy use Inputs and examplePurpose Compare energy use per matching product quantity. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Energy/output; water/output; and 100 × output/material input. Separate denominators and units; do not sum these efficiencies. Checks For Laggala Pallegama — resource productivity, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable product produces Check matching outputs, denominators and operating conditions. Missing Saleable product remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable product [kg]; Electric energy [kWh]; Process water [m³]; Raw material input [kg] Result: Energy per product; Water per product; Saleable mass conversion (kWh/kg; m³/kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — resource productivity. Saleable product = 4,500 kg; Electric energy = 3,400 kWh; Process water = 80 m³; Raw material input = 5,300 kg. Results: Energy per product = 0.756 kWh/kg; Water per product = 0.018 m³/kg; Saleable mass conversion = 84.906 %. Interpretation: Energy per product: 0.756 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable product = 4,501. Result: Energy per product = 0.755 kWh/kg; Water per product = 0.018 m³/kg; Saleable mass conversion = 84.925 %. Interpretation: Energy per product: 0.755 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable product. No usable result. Saleable product Next check: Correct or obtain the missing input records. Information still needed: Saleable product. Map context. No map inserted into this decision example Limits A high ratio needs process, product and operating checks before choosing an improvement. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Output per material input Materials productivity = product output ÷ materials used. The prototype multiplies the mass-to-mass ratio by 100 for percent. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-008DP28 | Industrial training Schedule technical training around verified skill needs Inputs and examplePurpose Check training dates, capacity and prerequisites against documented skills needs. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — industrial training, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — industrial training. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not assign trainees or establish acquired competence. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · International Guidelines for Industrial Parks Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-010DP28 | Estate maintenance Prioritize shared infrastructure maintenance Inputs and examplePurpose Identify shared-infrastructure maintenance cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — estate maintenance, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — estate maintenance. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish asset risk or engineering priority. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · International Guidelines for Industrial Parks Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-012DP28 | Pollution referrals Refer industrial environmental concerns to competent agencies Inputs and examplePurpose Find missing evidence for an industrial environmental referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — pollution referrals, the default output explains Obtain the missing evidence listed below. Changing Facility, Facility evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Facility remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Facility; Facility evidence reference; observed discharge; observed discharge evidence reference; permits; permits evidence reference; inspection; inspection evidence reference; exposed receptors; exposed receptors evidence reference; authority; authority evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — pollution referrals. Facility = Missing; Facility evidence reference = ; observed discharge = Documented; observed discharge evidence reference = Sample Laggala Pallegama field register / 2025; permits = Documented; permits evidence reference = Sample Laggala Pallegama field register / 2025; inspection = Documented; inspection evidence reference = Sample Laggala Pallegama field register / 2025; exposed receptors = Documented; exposed receptors evidence reference = Sample Laggala Pallegama field register / 2025; authority = Documented; authority evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this pollution referrals case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Facility = Documented; Facility evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle pollution referrals. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Facility. The required evidence is incomplete for this pollution referrals case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Facility: Missing. Map context. No map inserted into this decision example Limits The prototype does not determine pollution, liability or compliance. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Review environmental alternatives or mitigation Identify potential impacts, document relevant alternatives and review the measures proposed to reduce significant impacts. Sector guidance · International Guidelines for Industrial Parks Confirm whether the EIA process applies and obtain the competent authority’s scope and conditions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-013DP28 | Common facilities Compare demand for shared industrial processing facilities Inputs and examplePurpose Compare shared-processing demand with usable facility hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — common facilities, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [facility hours]; Rated capacity for that period [facility hours]; Unavailable or restricted capacity [facility hours] Result: Usable capacity minus demand; Usable capacity (facility hours; facility hours) Worked example. Fictional 2025 example. Laggala Pallegama — common facilities. Demand in the selected period = 150 facility hours; Rated capacity for that period = 180 facility hours; Unavailable or restricted capacity = 45 facility hours. Results: Usable capacity minus demand = -15 facility hours; Usable capacity = 135 facility hours. Interpretation: Usable capacity minus demand: -15 facility hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 facility hours; Usable capacity = 135 facility hours. Interpretation: Usable capacity minus demand: -16 facility hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity does not establish product compatibility, quality or a booking. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · International Guidelines for Industrial Parks Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-014DP28 | Product development Select feasible product-development support projects Inputs and examplePurpose Compare product-development approaches using testing and market evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Improve an existing product prototype, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Improve an existing product prototype. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve the existing product prototype.; Resource needs and adverse effects = Needs user requirements, test results, resources and design evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Prototype evidence; market demand; technical readiness; testing costs; risks. Map context. No map inserted into this decision example Limits Cost alone does not establish product fitness or commercial demand. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · International Guidelines for Industrial Parks Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-015DP28 | Testing services Reduce delays in technical testing and consultancy Inputs and examplePurpose Identify technical-testing and consultancy cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — testing services, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — testing services. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age does not establish the validity or urgency of a technical result. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP28-020DP28 | Industrial outcomes Evaluate whether technical support improved enterprise performance Inputs and examplePurpose Compare supplied energy-productivity changes in supported and comparison enterprises. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — industrial outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Saleable production per resource before produces Obtain the missing evidence listed below. Missing Treatment Saleable production per resource before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Saleable production per resource before [kg/kWh]; Treatment Saleable production per resource after [kg/kWh]; Comparison Saleable production per resource before [kg/kWh]; Comparison Saleable production per resource after [kg/kWh]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (kg/kWh) Worked example. Fictional 2025 example. Laggala Pallegama — industrial outcomes. Treatment Saleable production per resource before = 1.25 kg/kWh; Treatment Saleable production per resource after = 1.5 kg/kWh; Comparison Saleable production per resource before = 1.3 kg/kWh; Comparison Saleable production per resource after = 1.35 kg/kWh; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Saleable production per resource /example matching definition1. Results: Difference in changes = 0.2 kg/kWh. Interpretation: Treatment change: 0.25; comparison change: 0.05; difference in changes: 0.2 kg/kWh. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Saleable production per resource before = 1.262. Result: Difference in changes = 0.188 kg/kWh. Interpretation: Treatment change: 0.238; comparison change: 0.05; difference in changes: 0.188 kg/kWh. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Saleable production per resource before. No usable result. Treatment Saleable production per resource before Next check: Correct or obtain the missing input records. Information still needed: Treatment Saleable production per resource before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a technical-assistance effect. Industrial engineer and enterprise/estate service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP29-001DP29 | District projects Escalate overdue district project milestones Inputs and examplePurpose Compare district milestone completion dates with the stated plan. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — district projects, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — district projects. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits A delay needs dependency and source checks before assigning a cause. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare observed progress with the schedule baseline Retain the approved baseline and compare the reported actual milestone dates with the matching planned dates. Sector guidance · Project Submission Format Confirm the baseline edition and date convention. Leave absent actual dates open. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-002DP29 | Citizen services Prioritize aging district service requests Inputs and examplePurpose Identify district service requests past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — citizen services, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — citizen services. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish need or priority. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Published Sri Lankan step. Use the service duration and responsible officer in the institution’s published Citizen Charter to review delayed district requests. Ministry of Public Administration · Public Administration Circular 05/2008(II). Annex 01, Citizen Charter service time and responsible officer. Confirm the relevant charter version and how incomplete submissions affect timing. Calculation reference. International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-005DP29 | District planning Compare district development priorities within resource limits Inputs and examplePurpose Compare district proposals using service needs, resources and constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Repair an essential local service, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Repair an essential local service. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Repair the stated essential service.; Resource needs and adverse effects = Needs condition, user need, rights, engineering and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Needs; project options; costs; benefits; safeguards; dependencies; budget. Map context. No map inserted into this decision example Limits Budget and descriptive benefits do not establish an approved development priority. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Project Submission Format Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-006DP29 | Disaster coordination Allocate district response resources against verified needs Inputs and examplePurpose Compare usable district response resources with documented workload. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — disaster coordination, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [team hours]; Rated capacity for that period [team hours]; Unavailable or restricted capacity [team hours] Result: Usable capacity minus demand; Usable capacity (team hours; team hours) Worked example. Fictional 2025 example. Laggala Pallegama — disaster coordination. Demand in the selected period = 150 team hours; Rated capacity for that period = 180 team hours; Unavailable or restricted capacity = 45 team hours. Results: Usable capacity minus demand = -15 team hours; Usable capacity = 135 team hours. Interpretation: Usable capacity minus demand: -15 team hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 team hours; Usable capacity = 135 team hours. Interpretation: Usable capacity minus demand: -16 team hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity does not establish skills, readiness or deployment authority. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · National Emergency Operational Plan Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-012DP29 | Divisional capacity Target administrative support to overloaded divisions Inputs and examplePurpose Compare divisional workload with usable administrative staff time. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — divisional capacity, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — divisional capacity. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish staff competence or a defensible transfer priority. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Schedule Assessment Guide GAO-16-89G Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-013DP29 | District grievances Resolve inter-agency grievances with clear ownership Inputs and examplePurpose Identify inter-agency grievance cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — district grievances, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — district grievances. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A proposed office is not an assigned owner or a resolved grievance. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-016DP29 | Procurement dependencies Schedule district procurements affecting critical works Inputs and examplePurpose Check procurement task dates against dependencies and resource windows. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — procurement dependencies, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — procurement dependencies. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not approve procurement, select a supplier or commit funds. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Procurement action schedule Use the approved procurement time schedule to check the dates and sequence of the pre-contract activities. Sector guidance · Project Submission Format Confirm the applicable edition, procurement method and approved milestones. Resource conflicts and critical-path scoring are local rules. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP29-018DP29 | Outcome reporting Assess district programme outcomes with stated limitations Inputs and examplePurpose Compare district programme outcomes across the supplied groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — outcome reporting, the default output explains Obtain the missing evidence listed below. Changing Intervention group households receiving the stated district programme service within the same window before produces Obtain the missing evidence listed below. Missing Intervention group households receiving the stated district programme service within the same window before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Intervention group households receiving the stated district programme service within the same window before [%]; Intervention group households receiving the stated district programme service within the same window after [%]; Comparison group households receiving the stated district programme service within the same window before [%]; Comparison group households receiving the stated district programme service within the same window after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — outcome reporting. Intervention group households receiving the stated district programme service within the same window before = 42 %; Intervention group households receiving the stated district programme service within the same window after = 59 %; Comparison group households receiving the stated district programme service within the same window before = 39 %; Comparison group households receiving the stated district programme service within the same window after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Fictional measure: Households receiving the stated district programme service within the same window / matching frame, method and before-after windows. Results: Difference in changes = 10 percentage points. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Intervention group households receiving the stated district programme service within the same window before = 42.42. Result: Difference in changes = 9.58 percentage points. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Intervention group households receiving the stated district programme service within the same window before. No usable result. Treatment Verified programme outcome before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified programme outcome before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish programme impact. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP29-019DP29 | Geographic consistency Resolve district reporting boundary and code mismatches Inputs and examplePurpose Compare reporting boundary and code definitions before joining returns. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — geographic consistency, the default output explains Obtain the missing evidence listed below. Changing Source geography, Source geography evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Source geography remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Source geography; Source geography evidence reference; official code; official code evidence reference; boundary edition; boundary edition evidence reference; period; period evidence reference; crosswalk evidence; crosswalk evidence evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — geographic consistency. Source geography = Missing; Source geography evidence reference = ; official code = Documented; official code evidence reference = Sample Laggala Pallegama field register / 2025; boundary edition = Documented; boundary edition evidence reference = Sample Laggala Pallegama field register / 2025; period = Documented; period evidence reference = Sample Laggala Pallegama field register / 2025; crosswalk evidence = Documented; crosswalk evidence evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this geographic consistency case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Source geography = Documented; Source geography evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle geographic consistency. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Source geography. The required evidence is incomplete for this geographic consistency case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Source geography: Missing. Map context. No map inserted into this decision example Limits Matching codes do not establish the same geographic extent. District planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match administrative areas to official codes Use the published code for the corresponding division level and edition. Confirm the code vintage, boundary correspondence and any records that cannot be matched. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-001DP30 | Administrative applications Clear applications awaiting divisional administrative action Inputs and examplePurpose Identify divisional applications past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — administrative applications, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — administrative applications. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age does not establish eligibility or authorise a determination. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-002DP30 | Service standards Address divisional services exceeding approved response targets Inputs and examplePurpose Compare divisional case dates with the stated response target. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — service standards, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — service standards. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits The supplied target must be confirmed; a delay does not establish its cause. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Published Sri Lankan step. Match the request to the Divisional Secretariat’s published service duration and complaint officer before escalating a delay. Ministry of Public Administration · Public Administration Circular 05/2008(II). Annex 01, Citizen Charter service time and complaint officer. Confirm the correct service category, charter version and timing for complete applications. Calculation reference. International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-005DP30 | State-land referrals Prepare complete land cases for the competent authority Inputs and examplePurpose Find missing land-case evidence before referral to the competent authority. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — state-land referrals, the default output explains Obtain the missing evidence listed below. Changing Parcel, Parcel evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Parcel remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parcel; Parcel evidence reference; applicant; applicant evidence reference; rights evidence; rights evidence evidence reference; survey; survey evidence reference; current rules; current rules evidence reference; objections; objections evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — state-land referrals. Parcel = Missing; Parcel evidence reference = ; applicant = Documented; applicant evidence reference = Sample Laggala Pallegama field register / 2025; rights evidence = Documented; rights evidence evidence reference = Sample Laggala Pallegama field register / 2025; survey = Documented; survey evidence reference = Sample Laggala Pallegama field register / 2025; current rules = Documented; current rules evidence reference = Sample Laggala Pallegama field register / 2025; objections = Documented; objections evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this state-land referrals case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Parcel = Documented; Parcel evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle state-land referrals. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Parcel. The required evidence is incomplete for this state-land referrals case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Parcel: Missing. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The prototype does not determine ownership, rights or allocation. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Written permission for non-agricultural paddy use When the applicable rule identifies paddy land and the proposed use is non-agricultural, check the Commissioner-General’s written permission before referral. Sector guidance · Department services and land administration Confirm the parcel's legal status and current law with Agrarian Development. A document check does not authorize a conversion. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S29, S30, S38 Context alone does not validate the formula. |
| DEC-DP30-009DP30 | Local development Compare village-development proposals Inputs and examplePurpose Compare village-development proposals using needs, constraints and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Community water-service repair, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Community water-service repair. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Repair the community water service.; Resource needs and adverse effects = Needs source, quality, condition, demand, rights and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Needs; beneficiaries; location; cost; safeguards; capacity; alternatives. Map context. No map inserted into this decision example Limits A budget balance does not establish an agreed or suitable village priority. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-011DP30 | Field inspections Schedule required inspections efficiently Inputs and examplePurpose Check inspection dates against staff windows, prerequisites and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — field inspections, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — field inspections. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not assign an inspector or authorise access. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Annual Performance Report Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-014DP30 | Citizen complaints Assign unresolved local complaints to accountable offices Inputs and examplePurpose Identify unresolved local complaint cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — citizen complaints, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — citizen complaints. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A proposed office is not an assigned recipient or a completed response. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-015DP30 | Project monitoring Verify local works against approved scope Inputs and examplePurpose Compare observed work quantities with the same approved scope and unit. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — project monitoring, the default output explains Check the matching records and reasons for the difference. Changing Approved drain-repair length in this sample scope produces Check the matching records and reasons for the difference. Missing Approved drain-repair length in this sample scope remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Approved drain-repair length in this sample scope [m of the stated drain repair]; Matching drain length with accepted inspection evidence [m of the stated drain repair] Result: Difference; Relative change (m of the stated drain repair; %) Worked example. Fictional 2025 example. Laggala Pallegama — project monitoring. Approved drain-repair length in this sample scope = 450 m of the stated drain repair; Matching drain length with accepted inspection evidence = 420 m of the stated drain repair. Results: Difference = -30 m of the stated drain repair; Relative change = -6.667 %. Interpretation: Difference: -30 m of the stated drain repair. Next check: Check the matching records and reasons for the difference. Changed input. Change Approved drain-repair length in this sample scope = 451. Result: Difference = -31 m of the stated drain repair; Relative change = -6.874 %. Interpretation: Difference: -31 m of the stated drain repair. Next check: Check the matching records and reasons for the difference. Missing input. Omit Approved drain-repair length in this sample scope. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A quantity difference does not establish quality, payment entitlement or acceptance. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Sector guidance · FP124 Funding Proposal and project documentation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-016DP30 | Public assets Prioritize maintenance referrals for local public assets Inputs and examplePurpose Identify local-asset maintenance referrals past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — public assets, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — public assets. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish engineering urgency or repair priority. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-018DP30 | Office workload Allocate staff to service desks with capacity shortages Inputs and examplePurpose Compare service-desk workload with usable staff time. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — office workload, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [staff hours]; Rated capacity for that period [staff hours]; Unavailable or restricted capacity [staff hours] Result: Usable capacity minus demand; Usable capacity (staff hours; staff hours) Worked example. Fictional 2025 example. Laggala Pallegama — office workload. Demand in the selected period = 150 staff hours; Rated capacity for that period = 180 staff hours; Unavailable or restricted capacity = 45 staff hours. Results: Usable capacity minus demand = -15 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -15 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 staff hours; Usable capacity = 135 staff hours. Interpretation: Usable capacity minus demand: -16 staff hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity does not establish competence or authorise a staff assignment. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · Annual Performance Report Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP30-020DP30 | Referral completion Track cases through responsible institutions to documented outcomes Inputs and examplePurpose Track referrals through documented institutional response and outcome stages. Output Comparison table Next step Prepare progress follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × verified completed members / original unique cohort. Keep unknown follow-up separate; stages are nested, not independent populations. Checks For Laggala Pallegama — referral completion, the default output explains Check the original cases that have not reached a verified outcome. Changing Distinct original divisional service area in the stated cohort produces Check the original cases that have not reached a verified outcome. Missing Distinct original divisional service area in the stated cohort remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Distinct original divisional service area in the stated cohort [cases]; Those original cohort members with documented review [cases]; Those reviewed members meeting the stated completion definition [cases]; Original cohort members whose follow-up is unknown [cases] Result: Verified completion share; Not verified complete; Original cases awaiting review; Reviewed cases not confirmed complete (%; cases; cases; cases) Worked example. Fictional 2025 example. Laggala Pallegama — referral completion. Distinct original divisional service area in the stated cohort = 180 cases; Those original cohort members with documented review = 132 cases; Those reviewed members meeting the stated completion definition = 96 cases; Original cohort members whose follow-up is unknown = 12 cases. Results: Verified completion share = 53.333 %; Not verified complete = 84 cases; Original cases awaiting review = 48 cases; Reviewed cases not confirmed complete = 36 cases. Interpretation: Verified completion share: 53.333 %. Next check: Check the original cases that have not reached a verified outcome. Changed input. Change Distinct original divisional service area in the stated cohort = 181. Result: Verified completion share = 53.039 %; Not verified complete = 85 cases; Original cases awaiting review = 49 cases; Reviewed cases not confirmed complete = 36 cases. Interpretation: Verified completion share: 53.039 %. Next check: Check the original cases that have not reached a verified outcome. Missing input. Omit Distinct original divisional service area in the stated cohort. No usable result. Unique original cohort entrants Next check: Correct or obtain the missing input records. Information still needed: Unique original cohort entrants. Map context. No map inserted into this decision example Limits A completed stage does not establish formal acceptance or a beneficial outcome. Divisional planning/service officer and relevant sector specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Completion share Completion share Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-001DP31 | Field reporting Submit overdue required village reports Inputs and examplePurpose Identify required village reports past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — field reporting, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — field reporting. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A late report is not proof of inaccurate reporting or a cause of delay. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-008DP31 | Household updates Schedule verification of reported household changes Inputs and examplePurpose Check household-verification tasks against dates, staff windows and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — household updates, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — household updates. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not assign visits or disclose private household locations. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Annual Performance Report Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-011DP31 | Community complaints Escalate unresolved local complaints within jurisdiction Inputs and examplePurpose Identify local complaints past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — community complaints, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — community complaints. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits A proposed responsible office is not an assigned recipient or resolved complaint. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-012DP31 | Public warnings Identify residents missing authorized emergency messages Inputs and examplePurpose Find households without confirmed receipt of an authorised emergency message. Output Comparison table Next step Prepare coverage follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × distinct covered eligible units / eligible frame. Known uncovered = frame − covered − unknown. Checks For Laggala Pallegama — public warnings, the default output explains Check the records behind the uncovered and unknown groups. Changing Required eligible frame produces Check the records behind the uncovered and unknown groups. Missing Required eligible frame remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required eligible frame [households]; Distinct members of that frame covered [households]; Frame members with unknown coverage [households] Result: Verified coverage; Known uncovered; Unknown coverage (%; households; households) Worked example. Fictional 2025 example. Laggala Pallegama — public warnings. Required eligible frame = 100 households; Distinct members of that frame covered = 65 households; Frame members with unknown coverage = 5 households. Results: Verified coverage = 65 %; Known uncovered = 30 households; Unknown coverage = 5 households. Interpretation: 30 households are known to be uncovered; 5 have unknown coverage. 65% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Changed input. Change Required eligible frame = 101. Result: Verified coverage = 64.356 %; Known uncovered = 31 households; Unknown coverage = 5 households. Interpretation: 31 households are known to be uncovered; 5 have unknown coverage. 64.356% are confirmed covered. Next check: Check the records behind the uncovered and unknown groups. Missing input. Omit Required eligible frame. No usable result. Required eligible frame Next check: Correct or obtain the missing input records. Information still needed: Required eligible frame. Map context. No map inserted into this decision example Limits Dissemination does not establish understanding or an appropriate response. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check warning authority and dissemination Use the warning from the responsible technical agency and follow the documented dissemination arrangements. Confirm event, issue time, target area, receipt evidence and assigned responsibilities. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-014DP31 | Local infrastructure Refer damaged public assets to responsible maintainers Inputs and examplePurpose Identify public-asset repair referrals past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — local infrastructure, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — local infrastructure. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish engineering urgency. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Annual Performance Report Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-017DP31 | Programme follow-up Track referrals to verified service outcomes Inputs and examplePurpose Track referrals through documented service and outcome stages. Output Comparison table Next step Prepare progress follow-up creates an unassigned draft that is visible and downloadable, not sent. Rule 100 × verified completed members / original unique cohort. Keep unknown follow-up separate; stages are nested, not independent populations. Checks For Laggala Pallegama — programme follow-up, the default output explains Check the original cases that have not reached a verified outcome. Changing Distinct original village service case in the stated cohort produces Check the original cases that have not reached a verified outcome. Missing Distinct original village service case in the stated cohort remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Distinct original village service case in the stated cohort [cases]; Those original cohort members with documented review [cases]; Those reviewed members meeting the stated completion definition [cases]; Original cohort members whose follow-up is unknown [cases] Result: Verified completion share; Not verified complete; Original cases awaiting review; Reviewed cases not confirmed complete (%; cases; cases; cases) Worked example. Fictional 2025 example. Laggala Pallegama — programme follow-up. Distinct original village service case in the stated cohort = 180 cases; Those original cohort members with documented review = 132 cases; Those reviewed members meeting the stated completion definition = 96 cases; Original cohort members whose follow-up is unknown = 12 cases. Results: Verified completion share = 53.333 %; Not verified complete = 84 cases; Original cases awaiting review = 48 cases; Reviewed cases not confirmed complete = 36 cases. Interpretation: Verified completion share: 53.333 %. Next check: Check the original cases that have not reached a verified outcome. Changed input. Change Distinct original village service case in the stated cohort = 181. Result: Verified completion share = 53.039 %; Not verified complete = 85 cases; Original cases awaiting review = 49 cases; Reviewed cases not confirmed complete = 36 cases. Interpretation: Verified completion share: 53.039 %. Next check: Check the original cases that have not reached a verified outcome. Missing input. Omit Distinct original village service case in the stated cohort. No usable result. Unique original cohort entrants Next check: Correct or obtain the missing input records. Information still needed: Unique original cohort entrants. Map context. No map inserted into this decision example Limits A recorded stage does not establish quality or formal acceptance. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Completion share Completion share Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-019DP31 | Boundary codes Correct local records assigned to inconsistent geographic codes Inputs and examplePurpose Find missing evidence for geographic code definitions and source editions. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — boundary codes, the default output explains Obtain the missing evidence listed below. Changing Record location, Record location evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Record location remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Record location; Record location evidence reference; official GN code; official GN code evidence reference; boundary edition; boundary edition evidence reference; source date; source date evidence reference; crosswalk; crosswalk evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — boundary codes. Record location = Missing; Record location evidence reference = ; official GN code = Documented; official GN code evidence reference = Sample Laggala Pallegama field register / 2025; boundary edition = Documented; boundary edition evidence reference = Sample Laggala Pallegama field register / 2025; source date = Documented; source date evidence reference = Sample Laggala Pallegama field register / 2025; crosswalk = Documented; crosswalk evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this boundary codes case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Record location = Documented; Record location evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle boundary codes. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Record location. The required evidence is incomplete for this boundary codes case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Record location: Missing. Map context. No map inserted into this decision example Limits Matching codes do not establish the same village boundary. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Match administrative areas to official codes Use the published code for the corresponding division level and edition. Confirm the code vintage, boundary correspondence and any records that cannot be matched. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP31-020DP31 | Service feedback Identify recurring local service problems from feedback Inputs and examplePurpose Compare counts of the stated feedback categories. Output Comparison table Next step Prepare composition report creates an unassigned draft that is visible and downloadable, not sent. Rule Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Checks For Water supply, the default output explains Check category definitions, coverage and the stated denominator. Changing Distinct feedback cases in category produces Check category definitions, coverage and the stated denominator. Missing Distinct feedback cases in category remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Distinct feedback cases in category [cases]; Cases still unresolved [cases]; Feedback service/category Result: Feedback case count; Share of recorded feedback (cases; %) Worked example. Fictional 2025 example. Water supply. Distinct feedback cases in category = 18 cases; Cases still unresolved = 5 cases; Feedback service/category = Water supply. Results: Feedback case count = 18 cases; Share of recorded feedback = 32.727 %. Interpretation: Feedback case count: 18 cases. Next check: Check category definitions, coverage and the stated denominator. Changed input. Change Distinct feedback cases in category = 19. Result: Feedback case count = 19 cases; Share of recorded feedback = 33.929 %. Interpretation: Feedback case count: 19 cases. Next check: Check category definitions, coverage and the stated denominator. Missing input. Omit Distinct feedback cases in category. No usable result. Distinct feedback cases in category Next check: Correct or obtain the missing input records. Information still needed: Distinct feedback cases in category. Selected-frame statistics. total = 55; hhi = 0.207 Map context. No map inserted into this decision example Limits Feedback counts do not establish population prevalence, severity or urgency. Grama Niladhari officer with divisional supervisor and relevant service reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Code recurring feedback and route it for follow-up Log feedback, group it by topic and use the agreed response and referral process. Confirm the categories and permitted details. Keep urgent and sensitive cases in their proper channels. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-003DP32 | Irrigation requests Prepare evidence-based seasonal water requests Inputs and examplePurpose Prepare a crop-stage water-needs scenario for the stated member area. Output Comparison table Next step Prepare water-needs scenario creates an unassigned draft that is visible and downloadable, not sent. Rule ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency. Checks For Laggala Pallegama — irrigation requests, the default output explains Review weather, crop, water-availability and operating evidence. Changing Irrigated crop area produces Review weather, crop, water-availability and operating evidence. Missing Irrigated crop area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction] Result: Gross daily irrigation requirement; Net field requirement (m³/day; mm/day) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation requests. Irrigated crop area = 85 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction. Results: Gross daily irrigation requirement = 6,687.5 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,687.5 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Changed input. Change Irrigated crop area = 85.85. Result: Gross daily irrigation requirement = 6,754.375 m³/day; Net field requirement = 5.35 mm/day. Interpretation: Gross daily irrigation requirement: 6,754.375 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Missing input. Omit Irrigated crop area. No usable result. Irrigated crop area Next check: Correct or obtain the missing input records. Information still needed: Irrigated crop area. Map context. No map inserted into this decision example Limits Calculated demand does not establish water availability or authorise a release. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Crop evapotranspiration ETc = crop coefficient Kc × reference evapotranspiration ETo. Use mm/day for both ET values. Sector guidance · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration The match covers the ETc term. Confirm local crop coefficients, rainfall, field losses, efficiency and allocation authority. Implementation: prototype |
| DEC-DP32-004DP32 | Service coordination Escalate overdue collective farming requests Inputs and examplePurpose Identify collective farming requests past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — service coordination, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — service coordination. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish eligibility or need. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Department of Agrarian Development Services Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-005DP32 | Water rotations Propose workable water rotations for member areas Inputs and examplePurpose Check proposed water-rotation dates, effort and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — water rotations, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — water rotations. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not establish hydraulic feasibility, agreement or release authority. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Modernizing irrigation operations — spatially differentiated resource allocations Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-006DP32 | Tail-end equity Investigate unequal delivery against agreed allocations Inputs and examplePurpose Compare documented water delivery with the same agreed allocation and period. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — tail-end equity, the default output explains Check the matching records and reasons for the difference. Changing Planned value produces Check the matching records and reasons for the difference. Missing Planned value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned value [m³]; Observed value [m³] Result: Difference; Relative change (m³; %) Worked example. Fictional 2025 example. Laggala Pallegama — tail-end equity. Planned value = 100 m³; Observed value = 90 m³. Results: Difference = -10 m³; Relative change = -10 %. Interpretation: Difference: -10 m³. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned value = 101. Result: Difference = -11 m³; Relative change = -10.891 %. Interpretation: Difference: -11 m³. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned value. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A difference does not establish unfairness or its cause. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-007DP32 | Collective inputs Plan joint input purchases against verified member demand Inputs and examplePurpose Check usable input stocks, commitments and matching expected receipts. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — collective inputs, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg input]; Quarantined stock [kg input]; Expired stock [kg input]; Committed usable stock [kg input]; Additional demand [kg input]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg input; kg input) Worked example. Fictional 2025 example. Laggala Pallegama — collective inputs. Physical stock = 1,200 kg input; Quarantined stock = 100 kg input; Expired stock = 50 kg input; Committed usable stock = 740 kg input; Additional demand = 500 kg input; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg input; Additional demand gap = 190 kg input. Interpretation: Uncommitted usable stock: 310 kg input. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg input; Additional demand gap = 189 kg input. Interpretation: Uncommitted usable stock: 311 kg input. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Quantity alone does not establish quality, delivery certainty or a purchase authority. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-009DP32 | Machinery sharing Allocate shared machinery without conflicting reservations Inputs and examplePurpose Check machinery bookings against resources, effort and predecessor tasks. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — machinery sharing, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — machinery sharing. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not reserve a machine or appoint an operator. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-010DP32 | Irrigation upkeep Prioritize common tank and canal maintenance requests Inputs and examplePurpose Identify common tank and canal repair cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — irrigation upkeep, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation upkeep. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish engineering urgency or the best repair. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Department of Agrarian Development Services Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-011DP32 | Group finance Reconcile organization receipts expenses and balances Inputs and examplePurpose Reconcile organisation receipts, expenditure and the matching closing balance. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume. Checks For Laggala Pallegama — group finance, the default output explains Reconcile closing balance. Changing Opening cash/receivable balance produces Reconcile closing balance. Missing Opening cash/receivable balance remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening cash/receivable balance [LKR]; Receipts and documented additions [LKR]; Payments and documented reductions [LKR]; Other documented non-overlapping adjustments [LKR]; Independently recorded closing balance [LKR] Result: Calculated closing balance; Recorded minus calculated closing (LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — group finance. Opening cash/receivable balance = 160,000 LKR; Receipts and documented additions = 48,000 LKR; Payments and documented reductions = 35,000 LKR; Other documented non-overlapping adjustments = 9,000 LKR; Independently recorded closing balance = 163,500 LKR. Results: Calculated closing balance = 164,000 LKR; Recorded minus calculated closing = -500 LKR. Interpretation: Calculated closing funds are 164,000 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -500 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening cash/receivable balance = 160,001. Result: Calculated closing balance = 164,001 LKR; Recorded minus calculated closing = -501 LKR. Interpretation: Calculated closing funds are 164,001 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -501 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening cash/receivable balance. No usable result. Opening cash/receivable balance Next check: Correct or obtain the missing input records. Information still needed: Opening cash/receivable balance. Map context. No map inserted into this decision example Limits A difference does not establish fraud, a legal debt or final accounts acceptance. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-015DP32 | Drought plans Compare collective responses to forecast water shortages Inputs and examplePurpose Compare collective crop-calendar and rotation choices under a water shortage. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Revise the agreed crop calendar, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Revise the agreed crop calendar. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Revise the agreed crop calendar.; Resource needs and adverse effects = Needs crop-stage, forecast uncertainty, water availability and member agreement.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Approved forecasts; available water; crop choices; loss estimates; member consultation. Map context. No map inserted into this decision example Limits Cost alone does not establish crop suitability, water availability or agreement. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Modernizing irrigation operations — spatially differentiated resource allocations Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP32-017DP32 | Storage Compare collective storage and handling investments Inputs and examplePurpose Compare collective storage and handling cash flows. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish reduced losses, quality or investment authority. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP32-020DP32 | Collective outcomes Evaluate benefits and costs of group farming services Inputs and examplePurpose Compare recorded outcomes of group services across the supplied periods and groups. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — collective outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Member enterprise gross margin before produces Obtain the missing evidence listed below. Missing Treatment Member enterprise gross margin before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Member enterprise gross margin before [LKR/ha]; Treatment Member enterprise gross margin after [LKR/ha]; Comparison Member enterprise gross margin before [LKR/ha]; Comparison Member enterprise gross margin after [LKR/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR/ha) Worked example. Fictional 2025 example. Laggala Pallegama — collective outcomes. Treatment Member enterprise gross margin before = 420,000 LKR/ha; Treatment Member enterprise gross margin after = 590,000 LKR/ha; Comparison Member enterprise gross margin before = 390,000 LKR/ha; Comparison Member enterprise gross margin after = 460,000 LKR/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Member enterprise gross margin /example matching definition1. Results: Difference in changes = 100,000 LKR/ha. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Member enterprise gross margin before = 420,001. Result: Difference in changes = 99,999 LKR/ha. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Member enterprise gross margin before. No usable result. Treatment Member enterprise gross margin before Next check: Correct or obtain the missing input records. Information still needed: Treatment Member enterprise gross margin before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a causal group-service effect. Farmer-organization committee and relevant agriculture/water adviser | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP33-001DP33 | Farm profitability Choose crops using transparent enterprise gross margins Inputs and examplePurpose Compare crop-enterprise gross margins under stated output, price and cost assumptions. Output Comparison table Next step Prepare margin comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Gross margin = saleable output × realized price − variable costs. Divide by matching hectares for margin/ha; variable-cost break-even price = variable costs / output. Checks For Laggala Pallegama — farm profitability, the default output explains Review the prices, quantities and costs behind the margin. Changing Saleable output produces Review the prices, quantities and costs behind the margin. Missing Saleable output remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable output [kg]; Realized price [LKR/kg]; Variable costs [LKR]; Matching crop area [ha]; Crop and saleable-output basis Result: Enterprise gross margin; Gross margin per hectare; Variable-cost break-even price (LKR; LKR/ha; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — farm profitability. Saleable output = 4,500 kg; Realized price = 110 LKR/kg; Variable costs = 360,000 LKR; Matching crop area = 1 ha; Crop and saleable-output basis = Paddy rough rice / fictional one-hectare crop enterprise / same season. Results: Enterprise gross margin = 135,000 LKR; Gross margin per hectare = 135,000 LKR/ha; Variable-cost break-even price = 80 LKR/kg. Interpretation: The supplied 4,500 kg at 110 LKR/kg gives 495,000 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,000 LKR. Next check: Review the prices, quantities and costs behind the margin. Changed input. Change Saleable output = 4,501. Result: Enterprise gross margin = 135,110 LKR; Gross margin per hectare = 135,110 LKR/ha; Variable-cost break-even price = 79.982 LKR/kg. Interpretation: The supplied 4,501 kg at 110 LKR/kg gives 495,110 LKR revenue. After 360,000 LKR variable costs, gross margin is 135,110 LKR. Next check: Review the prices, quantities and costs behind the margin. Missing input. Omit Saleable output. No usable result. Saleable output Next check: Correct or obtain the missing input records. Information still needed: Saleable output. Map context. No map inserted into this decision example Limits Gross margin excludes some fixed and opportunity costs and does not select a suitable crop. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Gross margin per hectare Gross margin per hectare = gross benefit per hectare − variable costs per hectare. Sector guidance · Farm Management for Asia A Systems Approach The report demonstrates the paddy calculation. Confirm crop budgets, price, variable-cost boundaries and any local decision threshold. The report does not establish a break-even threshold. Implementation: prototype |
| DEC-DP33-002DP33 | Irrigation planning Plan irrigation needs for the proposed crop season Inputs and examplePurpose Prepare a crop-water-needs scenario from stated weather, crop and efficiency inputs. Output Comparison table Next step Prepare water-needs scenario creates an unassigned draft that is visible and downloadable, not sent. Rule ETc = ETo × Kc. Net = max(0, ETc + percolation + desired storage increase − rainfall after runoff − capillary contribution). Gross = net × hectares ×10 / application efficiency. Stage volume = gross daily requirement × stated stage days, only under the declared constant daily assumptions. A complete season requires all stages and dated conditions. Checks For Laggala Pallegama — irrigation planning, the default output explains Review weather, crop, water-availability and operating evidence. Changing Irrigated crop area produces Review weather, crop, water-availability and operating evidence. Missing Irrigated crop area remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Irrigated crop area [ha]; Reference evapotranspiration [mm/day]; Crop coefficient [ratio]; Rainfall reaching the field after runoff [mm/day]; Deep percolation and paddy allowance [mm/day]; Capillary contribution [mm/day]; Desired change in stored soil water [mm/day]; Field application efficiency [fraction]; Crop, stage and balance assumptions; Number of days at this stated constant balance [days] Result: Gross daily irrigation requirement; Net field requirement; Volume for this constant-balance stage (m³/day; mm/day; m³) Worked example. Fictional 2025 example. Laggala Pallegama — irrigation planning. Irrigated crop area = 1.2 ha; Reference evapotranspiration = 4.5 mm/day; Crop coefficient = 1.1 ratio; Rainfall reaching the field after runoff = 1.6 mm/day; Deep percolation and paddy allowance = 2 mm/day; Capillary contribution = 0 mm/day; Desired change in stored soil water = 0 mm/day; Field application efficiency = 0.68 fraction; Crop, stage and balance assumptions = Fictional paddy mid-season stage / constant daily balance for seven days; Number of days at this stated constant balance = 7 days. Results: Gross daily irrigation requirement = 94.412 m³/day; Net field requirement = 5.35 mm/day; Volume for this constant-balance stage = 660.882 m³. Interpretation: Gross daily irrigation requirement: 94.412 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Changed input. Change Irrigated crop area = 1.212. Result: Gross daily irrigation requirement = 95.356 m³/day; Net field requirement = 5.35 mm/day; Volume for this constant-balance stage = 667.491 m³. Interpretation: Gross daily irrigation requirement: 95.356 m³/day. Next check: Review weather, crop, water-availability and operating evidence. Missing input. Omit Irrigated crop area. No usable result. Irrigated crop area Next check: Correct or obtain the missing input records. Information still needed: Irrigated crop area. Map context. No map inserted into this decision example Limits Calculated need does not establish available water or authorise irrigation. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Crop evapotranspiration ETc = crop coefficient Kc × reference evapotranspiration ETo. Use mm/day for both ET values. Sector guidance · FAO Irrigation and Drainage Paper 56 Crop Evapotranspiration The match covers the ETc term. Confirm local crop coefficients, rainfall, field losses, efficiency and allocation authority. Implementation: prototype |
| DEC-DP33-003DP33 | Harvest losses Identify handling stages causing verified crop losses Inputs and examplePurpose Reconcile crop input mass with output, by-products, transfers and stock. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — harvest losses, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — harvest losses. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unaccounted balance does not identify a loss stage or cause. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-004DP33 | Planting dates Adjust planned planting against crop calendar and advice Inputs and examplePurpose Compare the proposed planting date with the stated crop-calendar date. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar. Checks For Laggala Pallegama — planting dates, the default output explains Check the matching records and reasons for the difference. Changing Planned milestone/sowing date produces Check the matching records and reasons for the difference. Missing Planned milestone/sowing date remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned milestone/sowing date; Observed completion/sowing date Result: Calendar date difference (days) Worked example. Fictional 2025 example. Laggala Pallegama — planting dates. Planned milestone/sowing date = 2025-06-01; Observed completion/sowing date = 2025-06-09. Results: Calendar date difference = 8 days. Interpretation: Calendar date difference: 8 days. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned milestone/sowing date = 2025-05-31. Result: Calendar date difference = 9 days. Interpretation: Calendar date difference: 9 days. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned milestone/sowing date. No usable result. Planned milestone/sowing date Next check: Correct or obtain the missing input records. Information still needed: Planned milestone/sowing date. Map context. No map inserted into this decision example Limits A date difference does not supply site-specific agronomic advice. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare planting dates with the applicable calendar Use the calendar for the crop, season and locality to check the proposed planting window. Confirm the relevant agroecological area, crop, season and current rainfall or water availability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-006DP33 | Input budgeting Plan affordable crop inputs with actual cost assumptions Inputs and examplePurpose Compare the input-cost scenario with the supplied affordable funds. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Budget gap = max(0, total matching cost − funds available). This is separate from cost per hectare. Checks For Laggala Pallegama — input budgeting, the default output explains Review the funding shortfall before buying inputs. Changing Labour cost produces Review the funding shortfall before buying inputs. Missing Labour cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Verified matching hectares [ha]; Funds available for these same crop-input costs [LKR] Result: Cost per matching unit; Total cost; Cost beyond the stated funds (LKR/ha; LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — input budgeting. Labour cost = 110,000 LKR; Material/input cost = 190,000 LKR; Other non-overlapping cost = 25,000 LKR; Verified matching hectares = 1.2 ha; Funds available for these same crop-input costs = 300,000 LKR. Results: Cost per matching unit = 270,833.333 LKR/ha; Total cost = 325,000 LKR; Cost beyond the stated funds = 25,000 LKR. Interpretation: The supplied costs total 325,000 LKR for 1.2 ha. Cost per matching unit is 270,833.333 LKR/ha. Next check: Review the funding shortfall before buying inputs. Changed input. Change Labour cost = 110,001. Result: Cost per matching unit = 270,834.167 LKR/ha; Total cost = 325,001 LKR; Cost beyond the stated funds = 25,001 LKR. Interpretation: The supplied costs total 325,001 LKR for 1.2 ha. Cost per matching unit is 270,834.167 LKR/ha. Next check: Review the funding shortfall before buying inputs. Missing input. Omit Labour cost. No usable result. Labour cost Next check: Correct or obtain the missing input records. Information still needed: Labour cost. Map context. No map inserted into this decision example Limits Affordability does not establish appropriate input rates or a safe treatment. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Paddy cash cost per unit of area The survey reports paddy cash production cost per acre. Normalize included cash production costs by the corresponding paddy area. Sector guidance · Socio Economics and Planning Centre downloads Compare the same crop, season and cost components and convert the area consistently. The cited survey covers cash payments. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-007DP33 | Cash needs Identify seasonal cash shortages before commitments Inputs and examplePurpose Review chronological farm cash events for temporary shortfalls. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Order the supplied dated receipts and payments. Start with the stated opening cash; add each receipt and subtract each payment once. Minimum cash is the lowest chronological balance, including opening cash. Shortfall = max(0, −minimum cash). Closing cash is opening + receipts − payments. Checks For Crop-input payment cash-plan scenario, the default output explains Review funding and payment timing before committing. Changing Cash available before the first dated event produces Review funding and payment timing before committing. Missing Cash available before the first dated event remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available before the first dated event [LKR]; Crop-input payment date; Crop-input payment [LKR]; Other crop-operation payment date; Other crop-operation payment [LKR]; Harvest-sale receipt date; Harvest-sale receipt [LKR] Result: Minimum projected cash; Maximum projected cash shortfall; Projected closing cash (LKR; LKR; LKR) Worked example. Fictional 2025 example. Crop-input payment cash-plan scenario. Cash available before the first dated event = 100,000 LKR; Crop-input payment date = 2025-06-01; Crop-input payment = 250,000 LKR; Other crop-operation payment date = 2025-06-08; Other crop-operation payment = 50,000 LKR; Harvest-sale receipt date = 2025-06-25; Harvest-sale receipt = 380,000 LKR. Results: Minimum projected cash = -200,000 LKR; Maximum projected cash shortfall = 200,000 LKR; Projected closing cash = 180,000 LKR. Interpretation: Lowest projected cash: -200000.00 LKR; shortfall: 200000.00 LKR; closing cash: 180000.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Changed input. Change Cash available before the first dated event = 100,001. Result: Minimum projected cash = -199,999 LKR; Maximum projected cash shortfall = 199,999 LKR; Projected closing cash = 180,001 LKR. Interpretation: Lowest projected cash: -199999.00 LKR; shortfall: 199999.00 LKR; closing cash: 180001.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Missing input. Omit Cash available before the first dated event. No usable result. Cash available before the first dated event Next check: Correct or obtain the missing input records. Information still needed: Cash available before the first dated event. Map context. No map inserted into this decision example Limits Positive closing cash does not rule out an earlier financing gap. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing, Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-008DP33 | Soil advice Seek reviewed nutrient advice using valid soil tests Inputs and examplePurpose Check the soil sample against its stated analytical method and comparison bounds. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare the measured value only with matching parameter, unit, use and averaging period. Retain limit source/version and censored-result status. Checks For Laggala Pallegama — soil advice, the default output explains Obtain the missing evidence listed below. Changing Measured result, Sample and site reference, Sample observation date produces Review the sample, analytical method and comparison basis. Missing Parameter and applicable use remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Parameter and applicable use; Measured result [mg/kg]; Example lower comparison bound [mg/kg]; Example upper comparison bound [mg/kg]; Original and limit unit; Sampling and analytical method/version; Limit source, version and use; Parameter, unit, use and averaging period match; Result is below a reporting/detection limit; Averaging interval, sampling depth or process basis; Sample and site reference; Sample observation date Result: Measured value (mg/kg) Worked example. Fictional 2025 example. Laggala Pallegama — soil advice. Parameter and applicable use = Available phosphorus by stated method; Measured result = 12 mg/kg; Example lower comparison bound = 15 mg/kg; Example upper comparison bound = 30 mg/kg; Original and limit unit = mg/kg; Sampling and analytical method/version = Sample laboratory method; Limit source, version and use = Fictional comparison bounds; not a regulatory limit; Parameter, unit, use and averaging period match = Yes; Result is below a reporting/detection limit = No; Averaging interval, sampling depth or process basis = Sample stated sampling/averaging basis; Sample and site reference = ; Sample observation date = . Results: Measured value = 12 mg/kg. Interpretation: The supplied Available phosphorus by stated method result is 12 mg/kg. Its stated comparison range is 15 to 30 mg/kg. Outside example comparison bounds. Next check: Obtain the missing evidence listed below. Changed input. Change Measured result = 12.12; Sample and site reference = DEMO-SAMPLE-REFERENCE; Sample observation date = 2025-06-12. Result: Measured value = 12.12 mg/kg. Interpretation: The supplied Available phosphorus by stated method result is 12.12 mg/kg. Its stated comparison range is 15 to 30 mg/kg. Outside example comparison bounds. Next check: Review the sample, analytical method and comparison basis. Missing input. Omit Parameter and applicable use. No usable result. Parameter and applicable use Next check: Correct or obtain the missing input records. Information still needed: Parameter and applicable use. Map context. No map inserted into this decision example Limits The example does not prescribe nutrient rates or treatment. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Use the applicable soil-test interpretation Use the soil test and the table for the stated parameter to support crop-specific nutrient advice. Confirm sampling, analytical method, crop, units and recommendation basis with an agronomist. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-010DP33 | Safe crop protection Check proposed treatments against current authorized guidance Inputs and examplePurpose Find missing product, crop, label and authority evidence for a treatment referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — safe crop protection, the default output explains Obtain the missing evidence listed below. Changing Product, Product evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Product remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Product; Product evidence reference; crop; crop evidence reference; pest; pest evidence reference; registration; registration evidence reference; label version; label version evidence reference; restrictions; restrictions evidence reference; adviser recommendation; adviser recommendation evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — safe crop protection. Product = Missing; Product evidence reference = ; crop = Documented; crop evidence reference = Sample Laggala Pallegama field register / 2025; pest = Documented; pest evidence reference = Sample Laggala Pallegama field register / 2025; registration = Documented; registration evidence reference = Sample Laggala Pallegama field register / 2025; label version = Documented; label version evidence reference = Sample Laggala Pallegama field register / 2025; restrictions = Documented; restrictions evidence reference = Sample Laggala Pallegama field register / 2025; adviser recommendation = Documented; adviser recommendation evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this safe crop protection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Product = Documented; Product evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle safe crop protection. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Product. The required evidence is incomplete for this safe crop protection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Product: Missing. Map context. No map inserted into this decision example Limits The example does not authorise pesticide use or provide a treatment dose. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Registered-use evidence check Check the proposed use against the current registered product and approved label before referral. Sector guidance · Pesticide registration, restrictions and guidance Confirm the crop, intended use, label conditions and current registration with the Registrar. The example gives no treatment instruction. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, DD-PESTICIDES, S03, S04, S31 Context alone does not validate the formula. |
| DEC-DP33-011DP33 | Seed purchase Select seed lots with verified suitability and quality evidence Inputs and examplePurpose Find missing seed-lot identity, suitability and test evidence. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — seed purchase, the default output explains Obtain the missing evidence listed below. Changing Variety, Variety evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Variety remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Variety; Variety evidence reference; lot ID; lot ID evidence reference; certification; certification evidence reference; germination; germination evidence reference; expiry; expiry evidence reference; required quantity; required quantity evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — seed purchase. Variety = Missing; Variety evidence reference = ; lot ID = Documented; lot ID evidence reference = Sample Laggala Pallegama field register / 2025; certification = Documented; certification evidence reference = Sample Laggala Pallegama field register / 2025; germination = Documented; germination evidence reference = Sample Laggala Pallegama field register / 2025; expiry = Documented; expiry evidence reference = Sample Laggala Pallegama field register / 2025; required quantity = Documented; required quantity evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this seed purchase case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Variety = Documented; Variety evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle seed purchase. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Variety. The required evidence is incomplete for this seed purchase case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Variety: Missing. Map context. No map inserted into this decision example Limits The prototype does not certify a lot or guarantee crop performance. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Seed-lot laboratory evidence Check the required seed-lot test results against the applicable certification standard. Include germination, viability, purity and moisture as relevant. Sector guidance · Quality Declared Planting Material Confirm crop-specific standards, required tests and lot records with the Seed Certification Service. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-012DP33 | Labour planning Schedule available labour around critical crop operations Inputs and examplePurpose Check labour dates, usable time and task dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — labour planning, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — labour planning. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not employ workers or guarantee a suitable crop window. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · Crop Calendar Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-013DP33 | Machinery choice Compare hiring and ownership of farm machinery Inputs and examplePurpose Compare machinery cash flows under the stated hiring or ownership assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Own the stated machinery, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%]; Common machinery-service basis for all three choices Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Own the stated machinery. Initial investment = 2,400,000 LKR; Net cash flow year1 = -240,000 LKR; Net cash flow year2 = -240,000 LKR; Net cash flow year3 = -240,000 LKR; Net cash flow year4 = -240,000 LKR; Net cash flow year5 = -240,000 LKR; Residual value at end of year5 = 800,000 LKR; Example discount rate = 8 %; Common machinery-service basis for all three choices = Fictional 40 matching service-hours each year / same task, timing and capacity. Results: Five-year net present value = -2,813,783.851 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give -2,813,783.851 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = -2,813,784.851 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give -2,813,784.851 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish operational suitability or financing approval. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP33-016DP33 | Drought adaptation Compare feasible water-saving and crop-adaptation options Inputs and examplePurpose Compare water-saving choices using crop, water, cost and site constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Drip irrigation scenario, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Drip irrigation scenario. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate drip irrigation.; Resource needs and adverse effects = Needs crop/site suitability, water quality, pressure, cost and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Farm exposure; water supply; crop alternatives; costs; technical advice; risks. Map context. No map inserted into this decision example Limits A stated benefit does not establish measured water savings or suitability. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Farm Management for Asia A Systems Approach Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP33-018DP33 | Farm investment Appraise proposed farm improvements under realistic scenarios Inputs and examplePurpose Compare farm-improvement cash flows under explicit investment assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits A positive net present value does not establish technical suitability or manageable risk. Farmer with qualified agriculture/water/finance adviser for the decision | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP34-001DP34 | Production economics Target estate crop and seasonal cost drivers Inputs and examplePurpose Compare estate production costs per matching crop-output unit. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Sum non-overlapping costs, then divide by the matching verified quantity for the same currency and accounting period. Checks For Laggala Pallegama — production economics, the default output explains Review cost components and comparable verified outputs. Changing Labour cost produces Review cost components and comparable verified outputs. Missing Labour cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Labour cost [LKR]; Material/input cost [LKR]; Other non-overlapping cost [LKR]; Green-leaf output on the stated weighing basis [kg green leaf] Result: Cost per matching unit; Total cost (LKR/kg green leaf; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — production economics. Labour cost = 180,000 LKR; Material/input cost = 255,000 LKR; Other non-overlapping cost = 62,000 LKR; Green-leaf output on the stated weighing basis = 4,500 kg green leaf. Results: Cost per matching unit = 110.444 LKR/kg green leaf; Total cost = 497,000 LKR. Interpretation: The supplied costs total 497,000 LKR for 4,500 kg green leaf. Cost per matching unit is 110.444 LKR/kg green leaf. Next check: Review cost components and comparable verified outputs. Changed input. Change Labour cost = 180,001. Result: Cost per matching unit = 110.445 LKR/kg green leaf; Total cost = 497,001 LKR. Interpretation: The supplied costs total 497,001 LKR for 4,500 kg green leaf. Cost per matching unit is 110.445 LKR/kg green leaf. Next check: Review cost components and comparable verified outputs. Missing input. Omit Labour cost. No usable result. Labour cost Next check: Correct or obtain the missing input records. Information still needed: Labour cost. Map context. No map inserted into this decision example Limits Unit cost does not establish quality, efficiency causes or an appropriate cost reduction. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Manufactured tea cost per kilogram For made tea, normalize matching production cost by kilograms of manufactured tea. Sector guidance · Cost of Production for Agricultural Products, basic concepts Confirm included estate costs and processing scope. Use one output and cost period. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-002DP34 | Soil and water Evaluate soil and water-management practice outcomes Inputs and examplePurpose Compare soil and water outcomes in the supplied observation groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — soil and water, the default output explains Obtain the missing evidence listed below. Changing Treatment Measured runoff before produces Obtain the missing evidence listed below. Missing Treatment Measured runoff before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Measured runoff before [mm/season]; Treatment Measured runoff after [mm/season]; Comparison Measured runoff before [mm/season]; Comparison Measured runoff after [mm/season]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (mm/season) Worked example. Fictional 2025 example. Laggala Pallegama — soil and water. Treatment Measured runoff before = 42 mm/season; Treatment Measured runoff after = 59 mm/season; Comparison Measured runoff before = 39 mm/season; Comparison Measured runoff after = 46 mm/season; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Measured runoff /example matching definition1. Results: Difference in changes = 10 mm/season. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 mm/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Measured runoff before = 42.42. Result: Difference in changes = 9.58 mm/season. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 mm/season. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Measured runoff before. No usable result. Treatment Measured runoff before Next check: Correct or obtain the missing input records. Information still needed: Treatment Measured runoff before; Study design and evidence that the treatment and comparison records are comparable. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A difference in changes does not establish a management-practice effect. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP34-003DP34 | Replanting areas Prioritize blocks for replanting or rehabilitation Inputs and examplePurpose Compare rehabilitation and replanting choices using block and resource evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Rehabilitate productive retained plants, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Rehabilitate productive retained plants. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Rehabilitate the retained productive plants.; Resource needs and adverse effects = Needs block health, age, yield, suitability and cost evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Block age; yield; plant condition; area; replant cost; income gap. Map context. No map inserted into this decision example Limits Cost alone does not establish plant health, productivity or the best intervention. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · TRI Guideline 01/2019 Climate Change Impacts and Adaptation Strategies for Tea Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-007DP34 | Erosion control Prioritize conservation treatment in vulnerable estate blocks Inputs and examplePurpose Compare supplied sheet-and-rill erosion estimates for detailed field assessment. Output Comparison table Next step Prepare assessment brief creates an unassigned draft that is visible and downloadable, not sent. Rule R × K × LS × C × P, using a mutually consistent SI factor set. Checks For Laggala Pallegama — erosion control, the default output explains Check local factor and site evidence before selecting a detailed erosion assessment. Changing Rainfall erosivity produces Check local factor and site evidence before selecting a detailed erosion assessment. Missing Rainfall erosivity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Rainfall erosivity [MJ mm/(ha h year)]; Soil erodibility [t ha h/(ha MJ mm)]; Slope-length and steepness factor [ratio]; Cover-management factor [fraction]; Support-practice factor [fraction] Result: Estimated annual sheet/rill loss (t/ha/year) Worked example. Fictional 2025 example. Laggala Pallegama — erosion control. Rainfall erosivity = 950 MJ mm/(ha h year); Soil erodibility = 0.035 t ha h/(ha MJ mm); Slope-length and steepness factor = 2.8 ratio; Cover-management factor = 0.24 fraction; Support-practice factor = 0.7 fraction. Results: Estimated annual sheet/rill loss = 15.641 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.641 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Changed input. Change Rainfall erosivity = 951. Result: Estimated annual sheet/rill loss = 15.657 t/ha/year. Interpretation: Estimated annual sheet/rill loss: 15.657 t/ha/year. Next check: Check local factor and site evidence before selecting a detailed erosion assessment. Missing input. Omit Rainfall erosivity. No usable result. Rainfall erosivity Next check: Correct or obtain the missing input records. Information still needed: Rainfall erosivity. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits The estimate does not establish landslide risk, all sediment loss or a treatment design. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Soil-loss factor product The Sri Lankan catchment study uses the same erosion-factor product. Estimated soil loss = R × K × LS × C × P. Sector guidance · A Guide for Predicting Sheet and Rill Erosion on Forest Land Use locally reviewed factor definitions, units and data for the actual catchment. The study’s factors and map do not transfer automatically. Implementation: prototype |
| DEC-DP34-008DP34 | Harvest scheduling Plan harvesting around maturity weather and capacity Inputs and examplePurpose Check harvesting dates against usable resources and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — harvest scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — harvest scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not establish maturity, safe weather or crop quality. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · TRI Guideline 01/2019 Climate Change Impacts and Adaptation Strategies for Tea Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-009DP34 | Pest management Refer unusual plantation pest and disease patterns Inputs and examplePurpose Identify an unusual pest observation against the supplied comparison basis. Output Comparison table Next step Prepare investigation brief creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive. Checks For Laggala Pallegama — pest management, the default output explains Check the unusual observation and its comparison basis. Changing Reference affected plants per 100 inspected produces Check the unusual observation and its comparison basis. Missing Reference affected plants per 100 inspected remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Reference affected plants per 100 inspected [affected plants per 100 inspected]; Observed affected plants per 100 inspected [affected plants per 100 inspected] Result: Difference; Relative change (affected plants per 100 inspected; %) Worked example. Fictional 2025 example. Laggala Pallegama — pest management. Reference affected plants per 100 inspected = 12 affected plants per 100 inspected; Observed affected plants per 100 inspected = 18 affected plants per 100 inspected. Results: Difference = 6 affected plants per 100 inspected; Relative change = 50 %. Interpretation: Difference: 6 affected plants per 100 inspected. Next check: Check the unusual observation and its comparison basis. Changed input. Change Reference affected plants per 100 inspected = 12.12. Result: Difference = 5.88 affected plants per 100 inspected; Relative change = 48.515 %. Interpretation: Difference: 5.88 affected plants per 100 inspected. Next check: Check the unusual observation and its comparison basis. Missing input. Omit Reference affected plants per 100 inspected. No usable result. Comparable reference value Next check: Correct or obtain the missing input records. Information still needed: Comparable reference value. Map context. No map inserted into this decision example Limits A deviation alone does not diagnose a pest outbreak or justify treatment. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-010DP34 | Processing efficiency Investigate poor conversion of harvest to saleable product Inputs and examplePurpose Compare gross made-tea output with matching received green leaf. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Gross recovery = 100 × made-tea mass / received green-leaf mass, on the explicitly stated incoming and outgoing moisture bases. This is not a dry-matter conversion efficiency. Checks For Laggala Pallegama — processing efficiency, the default output explains Check matching outputs, denominators and operating conditions. Changing Green-leaf mass received; declared incoming moisture basis produces Check matching outputs, denominators and operating conditions. Missing Green-leaf mass received; declared incoming moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Green-leaf mass received; declared incoming moisture basis [kg]; Made-tea mass; declared outgoing moisture basis [kg]; Separately recorded processing by-product mass [kg] Result: Gross made-tea recovery from received leaf (%) Worked example. Fictional 2025 example. Laggala Pallegama — processing efficiency. Green-leaf mass received; declared incoming moisture basis = 1,200 kg; Made-tea mass; declared outgoing moisture basis = 270 kg; Separately recorded processing by-product mass = 15 kg. Results: Gross made-tea recovery from received leaf = 22.5 %. Interpretation: Made-tea mass; declared outgoing moisture basis: 270 kg; Green-leaf mass received; declared incoming moisture basis: 1,200 kg. This gives 22.5 %. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Green-leaf mass received; declared incoming moisture basis = 1,201. Result: Gross made-tea recovery from received leaf = 22.481 %. Interpretation: Made-tea mass; declared outgoing moisture basis: 270 kg; Green-leaf mass received; declared incoming moisture basis: 1,201 kg. This gives 22.481 %. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Green-leaf mass received; declared incoming moisture basis. No usable result. Input mass on matching moisture basis Next check: Correct or obtain the missing input records. Information still needed: Input mass on matching moisture basis. Map context. No map inserted into this decision example Limits The ratio does not establish moisture-adjusted process efficiency or a loss cause. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Made-tea out-turn Out-turn (%) = 100 × made-tea mass ÷ green-leaf mass. Sector guidance · Food Loss Assessments in Small-Scale Agriculture and Fisheries Use the same production batch and stated moisture and weighing basis. Historical pricing factors in the article are outside this match. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-011DP34 | Energy and water Target resource-efficiency improvements in estate operations Inputs and examplePurpose Compare energy use per matching product quantity. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Energy/output; water/output; and 100 × output/material input. Separate denominators and units; do not sum these efficiencies. Checks For Laggala Pallegama — energy and water, the default output explains Check matching outputs, denominators and operating conditions. Changing Saleable product produces Check matching outputs, denominators and operating conditions. Missing Saleable product remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Saleable product [kg]; Electric energy [kWh]; Process water [m³]; Raw material input [kg] Result: Energy per product; Water per product; Saleable mass conversion (kWh/kg; m³/kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — energy and water. Saleable product = 4,500 kg; Electric energy = 3,400 kWh; Process water = 80 m³; Raw material input = 5,300 kg. Results: Energy per product = 0.756 kWh/kg; Water per product = 0.018 m³/kg; Saleable mass conversion = 84.906 %. Interpretation: Energy per product: 0.756 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Saleable product = 4,501. Result: Energy per product = 0.755 kWh/kg; Water per product = 0.018 m³/kg; Saleable mass conversion = 84.925 %. Interpretation: Energy per product: 0.755 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Saleable product. No usable result. Saleable product Next check: Correct or obtain the missing input records. Information still needed: Saleable product. Map context. No map inserted into this decision example Limits Product mix, quality and operating conditions must match before inferring efficiency. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Energy per kilogram of made tea The Sri Lankan benchmark reports energy used per kilogram of made tea. Specific electricity consumption = electricity used in kWh ÷ kilograms of made tea. Sector guidance · Enterprise-Level Indicators for Resource Productivity and Pollution Intensity For tea processing, match made-tea output, meter boundary and energy source. Confirm a sector-specific denominator before applying it to other products. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-013DP34 | Climate resilience Compare estate adaptation investments Inputs and examplePurpose Compare estate-adaptation cash flows under explicit assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish avoided climate damage or technical suitability. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP34-016DP34 | Maintenance Schedule critical estate and factory equipment maintenance Inputs and examplePurpose Identify equipment-maintenance cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — maintenance, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — maintenance. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish failure risk or a safe operating condition. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Irrigation Management Circular 01/2008 Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-017DP34 | Traceability Resolve breaks in estate product provenance Inputs and examplePurpose Trace broken source links between the stated estate lots. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Checks For Laggala Pallegama — traceability, the default output explains Investigate linked downstream lot. Changing Recorded upstream issue produces Review recorded lineage. Missing Upstream lot/source reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Upstream lot/source reference; Downstream lot/batch reference; Exact upstream source version; Recorded upstream issue Result: Broken or affected lineage (items) Worked example. Fictional 2025 example. Laggala Pallegama — traceability. Upstream lot/source reference = EXAMPLE-ROOT; Downstream lot/batch reference = 2025-BATCH-1; Exact upstream source version = Sample version1; Recorded upstream issue = Confirmed defect. Results: Broken or affected lineage = 1 items. Interpretation: Broken or affected lineage: 1 items. Investigate linked downstream lot. Next check: Investigate linked downstream lot. Changed input. Change Recorded upstream issue = None. Result: Broken or affected lineage = 0 items. Interpretation: Broken or affected lineage: 0 items. Review recorded lineage. Next check: Review recorded lineage. Missing input. Omit Upstream lot/source reference. No usable result. Upstream lot/source reference Next check: Correct or obtain the missing input records. Information still needed: Upstream lot/source reference. Map context. No map inserted into this decision example Limits A reference chain does not prove physical identity, conformity or actual recall scope. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Source and destination links for food lots Trace food back to its recorded source and forward to the next recorded destination. Sector guidance · Food Hygiene Regulations 2011 Confirm the applicable food operation, record period, linkage and recall authority. Obtain the current regulations and records. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP34-018DP34 | Carbon evidence Review estate carbon-stock estimates and pool coverage Inputs and examplePurpose Review carbon-stock changes with the stated area and pool coverage. Output Comparison table Next step Prepare carbon comparison creates an unassigned draft that is visible and downloadable, not sent. Rule (Later carbon density − earlier carbon density) × same inventory area, with identical pools, method and boundaries. Checks For Laggala Pallegama — carbon evidence, the default output explains Review the matched pools, area and observation periods. Changing Earlier carbon density produces Review the matched pools, area and observation periods. Missing Earlier carbon density remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier carbon density [t C/ha]; Later carbon density [t C/ha]; Same inventory area [ha]; Included pools and allometry references Result: Carbon stock change; Carbon-density change (t C; t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — carbon evidence. Earlier carbon density = 100 t C/ha; Later carbon density = 90 t C/ha; Same inventory area = 85 ha; Included pools and allometry references = Sample matching biomass pools; source model required. Results: Carbon stock change = -850 t C; Carbon-density change = -10 t C/ha. Interpretation: Carbon stock change: -850 t C. Next check: Review the matched pools, area and observation periods. Changed input. Change Earlier carbon density = 101. Result: Carbon stock change = -935 t C; Carbon-density change = -11 t C/ha. Interpretation: Carbon stock change: -935 t C. Next check: Review the matched pools, area and observation periods. Missing input. Omit Earlier carbon density. No usable result. Earlier carbon density Next check: Correct or obtain the missing input records. Information still needed: Earlier carbon density. Map context. District locator only; no asset, constraint, reservation or scenario overlay Limits A stock change does not establish a verified emission reduction or carbon credit. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Carbon stock-difference component Carbon stock-difference component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP34-020DP34 | Estate classifications Reconcile inconsistent block crop and land-use records Inputs and examplePurpose Find missing classification meanings and source versions for estate blocks. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — estate classifications, the default output explains Obtain the missing evidence listed below. Changing Block ID, Block ID evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Block ID remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Block ID; Block ID evidence reference; crop labels; crop labels evidence reference; planted area; planted area evidence reference; source edition; source edition evidence reference; definitions; definitions evidence reference; steward; steward evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — estate classifications. Block ID = Missing; Block ID evidence reference = ; crop labels = Documented; crop labels evidence reference = Sample Laggala Pallegama field register / 2025; planted area = Documented; planted area evidence reference = Sample Laggala Pallegama field register / 2025; source edition = Documented; source edition evidence reference = Sample Laggala Pallegama field register / 2025; definitions = Documented; definitions evidence reference = Sample Laggala Pallegama field register / 2025; steward = Documented; steward evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this estate classifications case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Block ID = Documented; Block ID evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle estate classifications. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Block ID. The required evidence is incomplete for this estate classifications case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Block ID: Missing. Map context. No map inserted into this decision example Limits Matching class labels do not establish the same land use or boundary. Estate agronomist, operations lead and environmental/social reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · Guidelines for Land-Use Planning Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-002DP35 | Issue follow-up Escalate unresolved worker and community issues Inputs and examplePurpose Identify unresolved worker and community cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — issue follow-up, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — issue follow-up. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish urgency or a resolution. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending Published Sri Lankan step. For a labour issue, record the complaint type, district of the final workplace and any earlier complaint before referral. Department of Labour · Complaint Management System, worker complaint registration. Complaint type, district of final workplace and earlier complaint fields. Confirm the responsible Labour office. Route other community concerns through their applicable service. Calculation reference. International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-004DP35 | Verified outcomes Identify programmes lacking baseline and follow-up evidence Inputs and examplePurpose Find missing baseline, follow-up and comparison-design evidence. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — verified outcomes, the default output explains Obtain the missing evidence listed below. Changing Programme cohort, Programme cohort evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Programme cohort remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Programme cohort; Programme cohort evidence reference; baseline outcome; baseline outcome evidence reference; follow-up; follow-up evidence reference; verification; verification evidence reference; attrition; attrition evidence reference; context; context evidence reference Result: Study evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — verified outcomes. Programme cohort = Missing; Programme cohort evidence reference = ; baseline outcome = Documented; baseline outcome evidence reference = Sample Laggala Pallegama field register / 2025; follow-up = Documented; follow-up evidence reference = Sample Laggala Pallegama field register / 2025; verification = Documented; verification evidence reference = Sample Laggala Pallegama field register / 2025; attrition = Documented; attrition evidence reference = Sample Laggala Pallegama field register / 2025; context = Documented; context evidence reference = Sample Laggala Pallegama field register / 2025. Results: Study evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this verified outcomes case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Programme cohort = Documented; Programme cohort evidence reference = DEMO-REVIEW-REFERENCE. Result: Study evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle verified outcomes. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Programme cohort. The required evidence is incomplete for this verified outcomes case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Programme cohort: Missing. Map context. No map inserted into this decision example Limits A complete checklist does not establish a causal programme effect. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check what a study design can support Check outcomes, comparison, baseline and follow-up evidence against the study design before attributing effects. Sector guidance · Impact Evaluation in Practice, second edition Confirm identification assumptions, population, missing follow-up and analytical limitations. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-010DP35 | Skills development Select training topics aligned with livelihood needs Inputs and examplePurpose Compare livelihood-training approaches against documented skills needs. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Livelihood business skills, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Livelihood business skills. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve livelihood business skills.; Resource needs and adverse effects = Needs documented needs, accessible training and practical follow-up.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Needs assessment; course options; costs; access; participant preferences; outcomes. Map context. No map inserted into this decision example Limits Cost and attendance do not establish competence or an income benefit. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-011DP35 | Livelihood alternatives Compare feasible supplementary livelihood options Inputs and examplePurpose Compare supplementary livelihood choices using skills, rights and market evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Home-based food processing, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Home-based food processing. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate home-based food processing.; Resource needs and adverse effects = Needs skills, food-safety conditions, premises, inputs and market evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Skills; resources; market demand; costs; care responsibilities; risks. Map context. No map inserted into this decision example Limits A budget balance does not establish enterprise viability or household suitability. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · National Policy Framework for Small and Medium Enterprise Development Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-016DP35 | Community facilities Prioritize repair referrals for shared facilities Inputs and examplePurpose Identify shared-facility repair cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — community facilities, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — community facilities. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish engineering urgency or service safety. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Water Safety Plan Manual, second edition Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP35-018DP35 | Community funds Reconcile approved group contributions and expenditure Inputs and examplePurpose Reconcile group contributions, expenditure and the matching closing balance. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume. Checks For Laggala Pallegama — community funds, the default output explains Reconcile closing balance. Changing Opening cash/receivable balance produces Reconcile closing balance. Missing Opening cash/receivable balance remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening cash/receivable balance [LKR]; Receipts and documented additions [LKR]; Payments and documented reductions [LKR]; Other documented non-overlapping adjustments [LKR]; Independently recorded closing balance [LKR] Result: Calculated closing balance; Recorded minus calculated closing (LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — community funds. Opening cash/receivable balance = 160,000 LKR; Receipts and documented additions = 48,000 LKR; Payments and documented reductions = 35,000 LKR; Other documented non-overlapping adjustments = 9,000 LKR; Independently recorded closing balance = 163,500 LKR. Results: Calculated closing balance = 164,000 LKR; Recorded minus calculated closing = -500 LKR. Interpretation: Calculated closing funds are 164,000 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -500 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening cash/receivable balance = 160,001. Result: Calculated closing balance = 164,001 LKR; Recorded minus calculated closing = -501 LKR. Interpretation: Calculated closing funds are 164,001 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -501 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening cash/receivable balance. No usable result. Opening cash/receivable balance Next check: Correct or obtain the missing input records. Information still needed: Opening cash/receivable balance. Map context. No map inserted into this decision example Limits A difference does not establish misuse or final accounts acceptance. Community representative, service specialist and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-002DP36 | Procurement prices Compare procurement offers for equivalent product grades Inputs and examplePurpose Compare procurement cost per retained kilogram for equivalent grades. Output Comparison table Next step Prepare quote comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Landed cost per retained kg = (purchase price per initial kg + matching transfer/handling cost per initial kg) / (1 − assumed mass loss% / 100), only when some mass is retained. Checks For Matale supplier-quotation scenario, the default output explains Compare the stated price result and payment terms. Changing Quoted purchase price produces Compare the stated price result and payment terms. Missing Supplier or offer reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Supplier or offer reference; Product, grade and weighing basis; Quoted purchase price [LKR/initial kg]; Non-overlapping transfer and handling cost [LKR/initial kg]; Assumed mass not retained for sale [%]; Stated delivery date; Stated payment date; Matching grade, weighing basis and terms evidenced in this example; Quotation, grade and terms reference Result: Landed cost per retained kilogram; Quoted headline price (LKR/retained kg; LKR/initial kg) Worked example. Fictional 2025 example. Matale supplier-quotation scenario. Supplier or offer reference = Matale supplier-quotation scenario; Product, grade and weighing basis = Tomato / same stated grade / per initial kilogram; Quoted purchase price = 180 LKR/initial kg; Non-overlapping transfer and handling cost = 20 LKR/initial kg; Assumed mass not retained for sale = 5 %; Stated delivery date = 2025-06-25; Stated payment date = 2025-06-30; Matching grade, weighing basis and terms evidenced in this example = Recorded; Quotation, grade and terms reference = Fictional quotation and specification / version 1. Results: Landed cost per retained kilogram = 210.526 LKR/retained kg; Quoted headline price = 180 LKR/initial kg. Interpretation: (180 + 20) / 0.950 = 210.53 LKR per retained kg. Next check: Compare the stated price result and payment terms. Changed input. Change Quoted purchase price = 181. Result: Landed cost per retained kilogram = 211.579 LKR/retained kg; Quoted headline price = 181 LKR/initial kg. Interpretation: (181 + 20) / 0.950 = 211.58 LKR per retained kg. Next check: Compare the stated price result and payment terms. Missing input. Omit Supplier or offer reference. No usable result. Supplier or offer reference Next check: Correct or obtain the missing input records. Information still needed: Supplier or offer reference. Map context. No map inserted into this decision example Limits Loss and transfer-cost assumptions must match; this is not a confirmed purchase price. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check comparable offers against stated requirements Compare offers with the stated specifications, material requirements, delivery terms and applicable price adjustments. Sector guidance · Exporter Standards Confirm the applicable procurement rules, quality grades, units, evaluation basis and approval authority. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-003DP36 | Trading spreads Investigate wholesale and retail spreads after costs Inputs and examplePurpose Compare purchase and sale quotations after stated costs and mass loss. Output Comparison table Next step Prepare quote comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Quoted spread = sell−buy. Net scenario return per purchased kg = sell×(1−loss%/100)−buy−matching transfer costs. Checks For Laggala Pallegama — trading spreads, the default output explains Check matching product grades, quantities, losses and quote periods. Changing Comparable purchase quotation produces Check matching product grades, quantities, losses and quote periods. Missing Comparable purchase quotation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable purchase quotation [LKR/kg]; Comparable selling quotation [LKR/kg]; Non-overlapping transfer costs [LKR/kg]; Expected saleable mass loss [%]; Product, grade and price basis Result: Quoted net return per purchased kg; Unadjusted quoted spread (LKR/kg; LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — trading spreads. Comparable purchase quotation = 180 LKR/kg; Comparable selling quotation = 222 LKR/kg; Non-overlapping transfer costs = 20 LKR/kg; Expected saleable mass loss = 5 %; Product, grade and price basis = Tomato / same stated grade / per purchased kilogram. Results: Quoted net return per purchased kg = 10.9 LKR/kg; Unadjusted quoted spread = 42 LKR/kg. Interpretation: Quoted net return per purchased kg: 10.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Changed input. Change Comparable purchase quotation = 181. Result: Quoted net return per purchased kg = 9.9 LKR/kg; Unadjusted quoted spread = 41 LKR/kg. Interpretation: Quoted net return per purchased kg: 9.9 LKR/kg. Next check: Check matching product grades, quantities, losses and quote periods. Missing input. Omit Comparable purchase quotation. No usable result. Comparable purchase quotation Next check: Correct or obtain the missing input records. Information still needed: Comparable purchase quotation. Map context. No map inserted into this decision example Limits A spread does not establish actual profit or excess market power. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Same-period market price spread Subtract the preceding market-stage price from the next-stage price using observations at the same point in time. Sector guidance · Daily Food Commodities Bulletin, 30 October 2026 Match crop, grade, unit, time and supply chain. Confirm loss, transfer costs and threshold separately. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-004DP36 | Delivery commitments Prioritize time-sensitive buyer orders Inputs and examplePurpose Check buyer-order tasks against deadlines, resources and dependencies. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — delivery commitments, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — delivery commitments. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits The example does not accept an order or guarantee delivery. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-005DP36 | Supplier reliability Review supplier delivery performance using accepted records Inputs and examplePurpose Compare delivered and agreed quantities for the same accepted order. Output Comparison table Next step Prepare difference review creates an unassigned draft that is visible and downloadable, not sent. Rule Observed value minus Planned value. Relative change = 100 × difference / Planned value when the earlier value is positive. Checks For Laggala Pallegama — supplier reliability, the default output explains Check the matching records and reasons for the difference. Changing Planned value produces Check the matching records and reasons for the difference. Missing Planned value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Planned value [kg]; Observed value [kg] Result: Difference; Relative change (kg; %) Worked example. Fictional 2025 example. Laggala Pallegama — supplier reliability. Planned value = 100 kg; Observed value = 90 kg. Results: Difference = -10 kg; Relative change = -10 %. Interpretation: Difference: -10 kg. Next check: Check the matching records and reasons for the difference. Changed input. Change Planned value = 101. Result: Difference = -11 kg; Relative change = -10.891 %. Interpretation: Difference: -11 kg. Next check: Check the matching records and reasons for the difference. Missing input. Omit Planned value. No usable result. Planned value Next check: Correct or obtain the missing input records. Information still needed: Planned value. Map context. No map inserted into this decision example Limits A shortfall needs acceptance and source checks before determining liability. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-007DP36 | Stock management Plan replenishment without overcommitting perishable stock Inputs and examplePurpose Check usable perishable stock against commitments and expected receipts. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — stock management, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg]; Quarantined stock [kg]; Expired stock [kg]; Committed usable stock [kg]; Additional demand [kg]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg; kg) Worked example. Fictional 2025 example. Laggala Pallegama — stock management. Physical stock = 1,200 kg; Quarantined stock = 100 kg; Expired stock = 50 kg; Committed usable stock = 740 kg; Additional demand = 500 kg; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg; Additional demand gap = 190 kg. Interpretation: Uncommitted usable stock: 310 kg. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg; Additional demand gap = 189 kg. Interpretation: Uncommitted usable stock: 311 kg. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits Quantity does not establish freshness, saleability or certain replenishment. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-008DP36 | Spoilage reduction Identify handling and storage stages with verified losses Inputs and examplePurpose Reconcile input mass with saleable output, stock, transfers and by-products. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — spoilage reduction, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — spoilage reduction. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unaccounted balance does not identify the stage or cause of loss. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-011DP36 | Trading cash flow Identify cash gaps from buying and selling schedules Inputs and examplePurpose Review chronological purchase and sale cash events for temporary shortfalls. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Order the supplied dated receipts and payments. Start with the stated opening cash; add each receipt and subtract each payment once. Minimum cash is the lowest chronological balance, including opening cash. Shortfall = max(0, −minimum cash). Closing cash is opening + receipts − payments. Checks For Produce purchase payment cash-plan scenario, the default output explains Review funding and payment timing before committing. Changing Cash available before the first dated event produces Review funding and payment timing before committing. Missing Cash available before the first dated event remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available before the first dated event [LKR]; Produce purchase payment date; Produce purchase payment [LKR]; Handling and storage payment date; Handling and storage payment [LKR]; Buyer receipt date; Buyer receipt [LKR] Result: Minimum projected cash; Maximum projected cash shortfall; Projected closing cash (LKR; LKR; LKR) Worked example. Fictional 2025 example. Produce purchase payment cash-plan scenario. Cash available before the first dated event = 100,000 LKR; Produce purchase payment date = 2025-06-01; Produce purchase payment = 250,000 LKR; Handling and storage payment date = 2025-06-08; Handling and storage payment = 50,000 LKR; Buyer receipt date = 2025-06-25; Buyer receipt = 380,000 LKR. Results: Minimum projected cash = -200,000 LKR; Maximum projected cash shortfall = 200,000 LKR; Projected closing cash = 180,000 LKR. Interpretation: Lowest projected cash: -200000.00 LKR; shortfall: 200000.00 LKR; closing cash: 180000.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Changed input. Change Cash available before the first dated event = 100,001. Result: Minimum projected cash = -199,999 LKR; Maximum projected cash shortfall = 199,999 LKR; Projected closing cash = 180,001 LKR. Interpretation: Lowest projected cash: -199999.00 LKR; shortfall: 199999.00 LKR; closing cash: 180001.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Missing input. Omit Cash available before the first dated event. No usable result. Cash available before the first dated event Next check: Correct or obtain the missing input records. Information still needed: Cash available before the first dated event. Map context. No map inserted into this decision example Limits Positive closing cash does not rule out an earlier financing gap. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing, Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-013DP36 | Customer dependence Review exposure to a small number of buyers Inputs and examplePurpose Review the stated sales exposure across buyers. Output Comparison table Next step Prepare concentration review creates an unassigned draft that is visible and downloadable, not sent. Rule Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Checks For Kandy wholesale channel, the default output explains Review the complete portfolio, category definitions and exposure constraints. Changing Compatible category amount produces Review the complete portfolio, category definitions and exposure constraints. Missing Compatible category amount remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Compatible category amount [LKR] Result: Category amount; Share of selected total (LKR; %) Worked example. Fictional 2025 example. Kandy wholesale channel. Compatible category amount = 900,000 LKR. Results: Category amount = 900,000 LKR; Share of selected total = 45 %. Interpretation: Category amount: 900,000 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Changed input. Change Compatible category amount = 900,001. Result: Category amount = 900,001 LKR; Share of selected total = 45 %. Interpretation: Category amount: 900,001 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Missing input. Omit Compatible category amount. No usable result. Compatible category amount Next check: Correct or obtain the missing input records. Information still needed: Compatible category amount. Selected-frame statistics. total = 2,000,000; hhi = 0.289 Map context. No map inserted into this decision example Limits Concentration does not establish buyer default probability or a complete portfolio. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required HHI concentration component HHI concentration component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP36-014DP36 | Supplier dependence Compare sourcing alternatives where supply is concentrated Inputs and examplePurpose Review the stated procurement quantities across suppliers. Output Comparison table Next step Prepare concentration review creates an unassigned draft that is visible and downloadable, not sent. Rule Category share = 100 × category amount / total compatible category amounts. HHI = sum of squared fractional shares, displayed on a 0–1 scale. Checks For Laggala farmer group, the default output explains Review the complete portfolio, category definitions and exposure constraints. Changing Compatible category amount produces Review the complete portfolio, category definitions and exposure constraints. Missing Compatible category amount remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Compatible category amount [kg] Result: Category amount; Share of selected total (kg; %) Worked example. Fictional 2025 example. Laggala farmer group. Compatible category amount = 95 kg. Results: Category amount = 95 kg; Share of selected total = 4.762 %. Interpretation: Category amount: 95 kg. Next check: Review the complete portfolio, category definitions and exposure constraints. Changed input. Change Compatible category amount = 95.95. Result: Category amount = 95.95 kg; Share of selected total = 4.807 %. Interpretation: Category amount: 95.95 kg. Next check: Review the complete portfolio, category definitions and exposure constraints. Missing input. Omit Compatible category amount. No usable result. Compatible category amount Next check: Correct or obtain the missing input records. Information still needed: Compatible category amount. Selected-frame statistics. total = 1,995; hhi = 0.206 Map context. No map inserted into this decision example Limits Concentration does not establish supplier reliability or an available substitute. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required HHI concentration component HHI concentration component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP36-015DP36 | Price variability Adjust procurement exposure after reviewing price volatility Inputs and examplePurpose Review variation in comparable procurement-price observations. Output Time-series chart and observation table Next step Prepare variation report creates an unassigned draft that is visible and downloadable, not sent. Rule Display observations in dated order. Sample SD uses n−1; coefficient of variation = 100 × SD / positive mean. Checks For Laggala Pallegama — price variability, the default output explains Check the comparable series and the reason for its variation. Changing Comparable observation produces Check the comparable series and the reason for its variation. Missing Comparable observation remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Comparable observation [LKR/kg] Result: Observed value (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — price variability. Comparable observation = 104 LKR/kg. Results: Observed value = 104 LKR/kg. Interpretation: Observed value: 104 LKR/kg. Next check: Check the comparable series and the reason for its variation. Changed input. Change Comparable observation = 105. Result: Observed value = 105 LKR/kg. Interpretation: Observed value: 105 LKR/kg. Next check: Check the comparable series and the reason for its variation. Missing input. Omit Comparable observation. No usable result. Comparable observation Next check: Correct or obtain the missing input records. Information still needed: Comparable observation. Selected-frame statistics. n = 3; mean = 111; sd = 7; cv = 6.306 Map context. No map inserted into this decision example Limits A short series does not forecast prices or establish a safe procurement position. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Sample coefficient of variation Sample coefficient of variation Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP36-016DP36 | Traceability Resolve missing provenance for traded lots Inputs and examplePurpose Trace missing source links for the stated traded lots. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Checks For Laggala Pallegama — traceability, the default output explains Investigate linked downstream lot. Changing Recorded upstream issue produces Review recorded lineage. Missing Upstream lot/source reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Upstream lot/source reference; Downstream lot/batch reference; Exact upstream source version; Recorded upstream issue Result: Broken or affected lineage (items) Worked example. Fictional 2025 example. Laggala Pallegama — traceability. Upstream lot/source reference = EXAMPLE-ROOT; Downstream lot/batch reference = 2025-BATCH-1; Exact upstream source version = Sample version1; Recorded upstream issue = Confirmed defect. Results: Broken or affected lineage = 1 items. Interpretation: Broken or affected lineage: 1 items. Investigate linked downstream lot. Next check: Investigate linked downstream lot. Changed input. Change Recorded upstream issue = None. Result: Broken or affected lineage = 0 items. Interpretation: Broken or affected lineage: 0 items. Review recorded lineage. Next check: Review recorded lineage. Missing input. Omit Upstream lot/source reference. No usable result. Upstream lot/source reference Next check: Correct or obtain the missing input records. Information still needed: Upstream lot/source reference. Map context. No map inserted into this decision example Limits A reference chain does not prove physical identity or product conformity. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Source and destination links for food lots Trace food back to its recorded source and forward to the next recorded destination. Sector guidance · Food Hygiene Regulations 2011 Confirm the applicable food operation, record period, linkage and recall authority. Obtain the current regulations and records. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-017DP36 | Market expansion Compare candidate markets against logistics and demand Inputs and examplePurpose Compare candidate markets using buyer, product and logistics evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Local cooperative market, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Local cooperative market. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate the local cooperative market.; Resource needs and adverse effects = Needs actual demand, grades, costs, terms and delivery access.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Market demand; access; competition evidence; transport; margins; regulatory needs. Map context. No map inserted into this decision example Limits Cost alone does not establish demand or a feasible sale. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP36-019DP36 | Packaging choices Compare packaging options for losses cost and buyer needs Inputs and examplePurpose Compare packaging choices using loss evidence, costs and buyer requirements. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Reusable crates, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Reusable crates. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Use reusable crates.; Resource needs and adverse effects = Needs product compatibility, cleaning, return logistics and measured loss evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Packaging costs; damage rates; capacity; buyer specification; handling conditions. Map context. No map inserted into this decision example Limits Descriptive benefits do not establish measured loss reduction or packaging conformity. Procurement/sales manager and quality/logistics reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · General Principles of Food Hygiene CXC 1-1969 Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-002DP37 | Logistics costs Investigate high shipment cost per tonne-kilometre Inputs and examplePurpose Compare shipment cost per matching tonne-kilometre. Output Comparison table Next step Prepare cost comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Shipment cost / (actual load tonnes × verified route kilometres). Match empty-return treatment and cost allocation. Checks For Laggala Pallegama — logistics costs, the default output explains Review cost components and comparable verified outputs. Changing Shipment cost produces Review cost components and comparable verified outputs. Missing Shipment cost remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Shipment cost [LKR]; Actual carried load [t]; Verified travelled route distance [km] Result: Shipment cost per tonne-kilometre (LKR/(t km)) Worked example. Fictional 2025 example. Laggala Pallegama — logistics costs. Shipment cost = 180,000 LKR; Actual carried load = 12 t; Verified travelled route distance = 80 km. Results: Shipment cost per tonne-kilometre = 187.5 LKR/(t km). Interpretation: Shipment cost per tonne-kilometre: 187.5 LKR/(t km). Next check: Review cost components and comparable verified outputs. Changed input. Change Shipment cost = 180,001. Result: Shipment cost per tonne-kilometre = 187.501 LKR/(t km). Interpretation: Shipment cost per tonne-kilometre: 187.501 LKR/(t km). Next check: Review cost components and comparable verified outputs. Missing input. Omit Shipment cost. No usable result. Shipment cost Next check: Correct or obtain the missing input records. Information still needed: Shipment cost. Map context. No map inserted into this decision example Limits A low ratio does not establish equivalent service quality, handling or delivery conditions. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Tonne-kilometres denominator Tonne-kilometres denominator Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP37-004DP37 | Export performance Review export unit values and destination performance Inputs and examplePurpose Compare export value per matching shipped kilogram. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Recorded export value / Export quantity on matching product basis, for the same product, process and period. Checks For Laggala Pallegama — export performance, the default output explains Check matching outputs, denominators and operating conditions. Changing Recorded export value produces Check matching outputs, denominators and operating conditions. Missing Recorded export value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Recorded export value [LKR]; Export quantity on matching product basis [kg] Result: Output per resource (LKR/kg) Worked example. Fictional 2025 example. Laggala Pallegama — export performance. Recorded export value = 8,832,000 LKR; Export quantity on matching product basis = 4,500 kg. Results: Output per resource = 1,962.667 LKR/kg. Interpretation: Recorded export value: 8,832,000 LKR; Export quantity on matching product basis: 4,500 kg. This gives 1,962.667 LKR/kg. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Recorded export value = 8,832,001. Result: Output per resource = 1,962.667 LKR/kg. Interpretation: Recorded export value: 8,832,001 LKR; Export quantity on matching product basis: 4,500 kg. This gives 1,962.667 LKR/kg. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Recorded export value. No usable result. Recorded export value Next check: Correct or obtain the missing input records. Information still needed: Recorded export value. Map context. No map inserted into this decision example Limits Unit value may reflect product mix and is not a price or profitability index. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Export unit value Export unit value Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP37-006DP37 | Capacity planning Compare orders with usable processing capacity Inputs and examplePurpose Compare processing demand with usable machine hours. Output Comparison table Next step Prepare capacity review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand. Checks For Laggala Pallegama — capacity planning, the default output explains Review capacity shortfall. Changing Demand in the selected period produces Review capacity shortfall. Missing Demand in the selected period remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Demand in the selected period [machine hours]; Rated capacity for that period [machine hours]; Unavailable or restricted capacity [machine hours] Result: Usable capacity minus demand; Usable capacity (machine hours; machine hours) Worked example. Fictional 2025 example. Laggala Pallegama — capacity planning. Demand in the selected period = 150 machine hours; Rated capacity for that period = 180 machine hours; Unavailable or restricted capacity = 45 machine hours. Results: Usable capacity minus demand = -15 machine hours; Usable capacity = 135 machine hours. Interpretation: Usable capacity minus demand: -15 machine hours. Review capacity shortfall. Next check: Review capacity shortfall. Changed input. Change Demand in the selected period = 151. Result: Usable capacity minus demand = -16 machine hours; Usable capacity = 135 machine hours. Interpretation: Usable capacity minus demand: -16 machine hours. Review capacity shortfall. Next check: Review capacity shortfall. Missing input. Omit Demand in the selected period. No usable result. Demand in the selected period Next check: Correct or obtain the missing input records. Information still needed: Demand in the selected period. Map context. No map inserted into this decision example Limits Capacity alone does not establish product compatibility or a production booking. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare usable capacity with demand Allow for known capacity constraints and compare the remaining capacity with demand in matching units and periods. Sector guidance · International Guidelines for Industrial Parks Confirm the basis of rated and unavailable capacity, relevant operating limits and demand estimate. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-007DP37 | Production scheduling Schedule batches around quality and delivery constraints Inputs and examplePurpose Check batch dates against resources, delivery windows and prerequisites. Output Task schedule table Next step Prepare schedule review creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — production scheduling, the default output explains Resolve overlapping resource bookings. Changing Required resource effort produces Resolve overlapping resource bookings. Missing Required resource remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Required resource; Task start; Task end; Earliest permitted start; Latest permitted finish; Required resource effort [hours]; Available resource effort [hours]; Predecessor task reference; Mandatory permits and prerequisites Result: Planned duration; Resource hours remaining (days; hours) Worked example. Fictional 2025 example. Laggala Pallegama — production scheduling. Required resource = Watershed field team; Task start = 2025-06-01; Task end = 2025-06-04; Earliest permitted start = 2025-05-28; Latest permitted finish = 2025-06-08; Required resource effort = 16 hours; Available resource effort = 24 hours; Predecessor task reference = None; Mandatory permits and prerequisites = Met. Results: Planned duration = 3 days; Resource hours remaining = 8 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Changed input. Change Required resource effort = 16.16. Result: Planned duration = 3 days; Resource hours remaining = 7.84 hours. Interpretation: Planned duration: 3 days. Resolve overlapping resource bookings. Next check: Resolve overlapping resource bookings. Missing input. Omit Required resource. No usable result. Required resource Next check: Correct or obtain the missing input records. Information still needed: Required resource. Map context. No map inserted into this decision example Limits A schedule does not establish conformity or guarantee delivery. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check schedule dependencies and resource conflicts Sequence dependent tasks, assign resources and check whether simultaneous work exceeds available resources. Sector guidance · General Principles of Food Hygiene CXC 1-1969 Confirm the actual dates, available resources, operating windows and constraints before acting. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-009DP37 | Traceability and recall Identify affected lots when a source defect is confirmed Inputs and examplePurpose Trace the supplied source defect through recorded downstream lot links. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Follow recorded upstream→downstream links within the same scope and period. Flag missing links; a confirmed defect identifies downstream linked candidates for authorized investigation. Checks For Laggala Pallegama — traceability and recall, the default output explains Investigate linked downstream lot. Changing Recorded upstream issue produces Review recorded lineage. Missing Upstream lot/source reference remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Upstream lot/source reference; Downstream lot/batch reference; Exact upstream source version; Recorded upstream issue Result: Broken or affected lineage (items) Worked example. Fictional 2025 example. Laggala Pallegama — traceability and recall. Upstream lot/source reference = EXAMPLE-ROOT; Downstream lot/batch reference = 2025-BATCH-1; Exact upstream source version = Sample version1; Recorded upstream issue = Confirmed defect. Results: Broken or affected lineage = 1 items. Interpretation: Broken or affected lineage: 1 items. Investigate linked downstream lot. Next check: Investigate linked downstream lot. Changed input. Change Recorded upstream issue = None. Result: Broken or affected lineage = 0 items. Interpretation: Broken or affected lineage: 0 items. Review recorded lineage. Next check: Review recorded lineage. Missing input. Omit Upstream lot/source reference. No usable result. Upstream lot/source reference Next check: Correct or obtain the missing input records. Information still needed: Upstream lot/source reference. Map context. No map inserted into this decision example Limits Candidate links do not establish physical recall scope or authorise a recall. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Source and destination links for food lots Trace food back to its recorded source and forward to the next recorded destination. Sector guidance · Food Hygiene Regulations 2011 Confirm the applicable food operation, record period, linkage and recall authority. Obtain the current regulations and records. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-010DP37 | Food loss Select loss-reduction actions at processing bottlenecks Inputs and examplePurpose Reconcile processing input mass with output, transfers and stock. Output Comparison table Next step Prepare loss-balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Unaccounted = input − saleable output − usable by-products − closing stock − transfers out. Share =100 × unaccounted / input. Checks For Laggala Pallegama — food loss, the default output explains Reconcile the input, output, stock and transfer records. Changing Batch input on stated moisture basis produces Reconcile the input, output, stock and transfer records. Missing Batch input on stated moisture basis remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Batch input on stated moisture basis [kg]; Saleable output [kg]; Usable by-product [kg]; Closing stock [kg]; Documented transfers out [kg] Result: Unaccounted physical share; Unaccounted mass (%; kg) Worked example. Fictional 2025 example. Laggala Pallegama — food loss. Batch input on stated moisture basis = 1,200 kg; Saleable output = 970 kg; Usable by-product = 85 kg; Closing stock = 45 kg; Documented transfers out = 20 kg. Results: Unaccounted physical share = 6.667 %; Unaccounted mass = 80 kg. Interpretation: Unaccounted physical share: 6.667 %. Next check: Reconcile the input, output, stock and transfer records. Changed input. Change Batch input on stated moisture basis = 1,201. Result: Unaccounted physical share = 6.744 %; Unaccounted mass = 81 kg. Interpretation: Unaccounted physical share: 6.744 %. Next check: Reconcile the input, output, stock and transfer records. Missing input. Omit Batch input on stated moisture basis. No usable result. Batch input on stated moisture basis Next check: Correct or obtain the missing input records. Information still needed: Batch input on stated moisture basis. Map context. No map inserted into this decision example Limits An unaccounted balance does not identify the bottleneck or the best intervention. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare matched quantities at a process stage Measure comparable amounts before and after a stage and account separately for intended weight changes such as drying. Confirm product, moisture basis, transfers, by-products, inventory changes and evidence of actual loss. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-011DP37 | Energy efficiency Target processes with high energy per saleable unit Inputs and examplePurpose Compare process energy per matching saleable output. Output Comparison table Next step Prepare performance comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Energy consumed / Saleable product output, for the same product, process and period. Checks For Laggala Pallegama — energy efficiency, the default output explains Check matching outputs, denominators and operating conditions. Changing Energy consumed produces Check matching outputs, denominators and operating conditions. Missing Energy consumed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Energy consumed [kWh]; Saleable product output [kg] Result: Specific energy use (kWh/kg) Worked example. Fictional 2025 example. Laggala Pallegama — energy efficiency. Energy consumed = 3,128 kWh; Saleable product output = 4,500 kg. Results: Specific energy use = 0.695 kWh/kg. Interpretation: Energy consumed: 3,128 kWh; Saleable product output: 4,500 kg. This gives 0.695 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Changed input. Change Energy consumed = 3,129. Result: Specific energy use = 0.695 kWh/kg. Interpretation: Energy consumed: 3,129 kWh; Saleable product output: 4,500 kg. This gives 0.695 kWh/kg. Next check: Check matching outputs, denominators and operating conditions. Missing input. Omit Energy consumed. No usable result. Energy consumed Next check: Correct or obtain the missing input records. Information still needed: Energy consumed. Map context. No map inserted into this decision example Limits A high ratio requires process and operating checks before selecting an improvement. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Energy per kilogram of made tea The Sri Lankan benchmark reports energy used per kilogram of made tea. Specific electricity consumption = electricity used in kWh ÷ kilograms of made tea. Sector guidance · Energy Intensity Indicators Terminology and Definitions For tea processing, match made-tea output, meter boundary and energy source. Confirm a sector-specific denominator before applying it to other products. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-012DP37 | Water efficiency Compare process water use and reuse alternatives Inputs and examplePurpose Compare water-saving and reuse choices using quality, treatment and process evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Reduce process-water losses, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Reduce process-water losses. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Reduce process-water losses.; Resource needs and adverse effects = Needs a matching water balance, process controls and measured effects.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Water input; usable recycled water; output; water quality; costs; controls. Map context. No map inserted into this decision example Limits Cost alone does not establish safe reuse or measured water savings. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Enterprise-Level Indicators for Resource Productivity and Pollution Intensity Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-013DP37 | Equipment reliability Prioritize critical equipment repairs and preventive work Inputs and examplePurpose Identify equipment-repair cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — equipment reliability, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — equipment reliability. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish criticality or a safe operating condition. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · International Guidelines for Industrial Parks Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-014DP37 | Inventory expiry Avoid using expired or quarantined materials Inputs and examplePurpose Check usable stock after the stated unavailable and committed quantities. Output Comparison table Next step Prepare stock review creates an unassigned draft that is visible and downloadable, not sent. Rule Usable = physical−quarantined−expired (non-overlapping groups). Available = usable−commitments. Additional gap = max(0, new demand−available). Checks For Laggala Pallegama — inventory expiry, the default output explains Review replenishment gap. Changing Physical stock produces Review replenishment gap. Missing Physical stock remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Physical stock [kg]; Quarantined stock [kg]; Expired stock [kg]; Committed usable stock [kg]; Additional demand [kg]; Supplier lead time [days]; Remaining shelf life of usable stock [days] Result: Uncommitted usable stock; Additional demand gap (kg; kg) Worked example. Fictional 2025 example. Laggala Pallegama — inventory expiry. Physical stock = 1,200 kg; Quarantined stock = 100 kg; Expired stock = 50 kg; Committed usable stock = 740 kg; Additional demand = 500 kg; Supplier lead time = 14 days; Remaining shelf life of usable stock = 30 days. Results: Uncommitted usable stock = 310 kg; Additional demand gap = 190 kg. Interpretation: Uncommitted usable stock: 310 kg. Review replenishment gap. Next check: Review replenishment gap. Changed input. Change Physical stock = 1,201. Result: Uncommitted usable stock = 311 kg; Additional demand gap = 189 kg. Interpretation: Uncommitted usable stock: 311 kg. Review replenishment gap. Next check: Review replenishment gap. Missing input. Omit Physical stock. No usable result. Physical stock Next check: Correct or obtain the missing input records. Information still needed: Physical stock. Map context. No map inserted into this decision example Limits The underlying expiry and quarantine records must be checked before use. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Compare available stock with new demand Distinguish physical stock from stock already committed. Use the available balance for planning. Sector guidance · Logistics Operational Guide, Monitoring and Counting Confirm expiry and quarantine separately, reconcile the same unit and date, and confirm safety stock. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-016DP37 | Working capital Identify cash shortfalls across purchase production and payment cycles Inputs and examplePurpose Review chronological buying, production and receipt cash events. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Order the supplied dated receipts and payments. Start with the stated opening cash; add each receipt and subtract each payment once. Minimum cash is the lowest chronological balance, including opening cash. Shortfall = max(0, −minimum cash). Closing cash is opening + receipts − payments. Checks For Raw-material payment cash-plan scenario, the default output explains Review funding and payment timing before committing. Changing Cash available before the first dated event produces Review funding and payment timing before committing. Missing Cash available before the first dated event remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available before the first dated event [LKR]; Raw-material payment date; Raw-material payment [LKR]; Production payment date; Production payment [LKR]; Customer receipt date; Customer receipt [LKR] Result: Minimum projected cash; Maximum projected cash shortfall; Projected closing cash (LKR; LKR; LKR) Worked example. Fictional 2025 example. Raw-material payment cash-plan scenario. Cash available before the first dated event = 100,000 LKR; Raw-material payment date = 2025-06-01; Raw-material payment = 250,000 LKR; Production payment date = 2025-06-08; Production payment = 50,000 LKR; Customer receipt date = 2025-06-25; Customer receipt = 380,000 LKR. Results: Minimum projected cash = -200,000 LKR; Maximum projected cash shortfall = 200,000 LKR; Projected closing cash = 180,000 LKR. Interpretation: Lowest projected cash: -200000.00 LKR; shortfall: 200000.00 LKR; closing cash: 180000.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Changed input. Change Cash available before the first dated event = 100,001. Result: Minimum projected cash = -199,999 LKR; Maximum projected cash shortfall = 199,999 LKR; Projected closing cash = 180,001 LKR. Interpretation: Lowest projected cash: -199999.00 LKR; shortfall: 199999.00 LKR; closing cash: 180001.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Missing input. Omit Cash available before the first dated event. No usable result. Cash available before the first dated event Next check: Correct or obtain the missing input records. Information still needed: Cash available before the first dated event. Map context. No map inserted into this decision example Limits Positive closing cash does not rule out an earlier financing gap. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing, Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP37-017DP37 | Expansion appraisal Compare equipment and facility expansion investments Inputs and examplePurpose Compare equipment or expansion cash flows under explicit assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value does not establish technical suitability or investment authority. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP37-018DP37 | Export documentation Refer complete shipment documentation for required clearance Inputs and examplePurpose Find missing shipment documents before an authorised clearance referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — export documentation, the default output explains Obtain the missing evidence listed below. Changing Shipment, Shipment evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Shipment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Shipment; Shipment evidence reference; certificates; certificates evidence reference; origin; origin evidence reference; permits; permits evidence reference; specification; specification evidence reference; current requirements; current requirements evidence reference; authority; authority evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — export documentation. Shipment = Missing; Shipment evidence reference = ; certificates = Documented; certificates evidence reference = Sample Laggala Pallegama field register / 2025; origin = Documented; origin evidence reference = Sample Laggala Pallegama field register / 2025; permits = Documented; permits evidence reference = Sample Laggala Pallegama field register / 2025; specification = Documented; specification evidence reference = Sample Laggala Pallegama field register / 2025; current requirements = Documented; current requirements evidence reference = Sample Laggala Pallegama field register / 2025; authority = Documented; authority evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this export documentation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Shipment = Documented; Shipment evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle export documentation. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Shipment. The required evidence is incomplete for this export documentation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Shipment: Missing. Map context. No map inserted into this decision example Limits The prototype does not grant customs, health or export clearance. Production/quality manager and trade/logistics/finance specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Food export certificate referral Check the establishment registration evidence and factory inspection status before referring an application for the applicable export certificate. Sector guidance · Export Procedure and Logistics Requirements Confirm current rules, the destination and any commodity-specific certificate with the issuing authority. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S31, S33, S34 Context alone does not validate the formula. |
| DEC-DP38-001DP38 | Investment appraisal Select investments for detailed cash-flow appraisal Inputs and examplePurpose Review investment cash flows before detailed financial appraisal. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits Net present value alone does not establish creditworthiness or investment approval. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP38-002DP38 | Repayment capacity Assess debt-service coverage under lender-defined scenarios Inputs and examplePurpose Compare available debt-service cash with matching scheduled principal and interest. Output Comparison table Next step Prepare repayment review creates an unassigned draft that is visible and downloadable, not sent. Rule Debt-service coverage = cash available / (principal + interest) for the same period. Zero scheduled debt has no coverage ratio. Checks For Laggala Pallegama — repayment capacity, the default output explains Review the cash-flow evidence and repayment conditions. Changing Cash available for debt service produces Review the cash-flow evidence and repayment conditions. Missing Cash available for debt service remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available for debt service [LKR]; Scheduled principal for same period [LKR]; Scheduled interest for same period [LKR]; Repayment and cash-flow period Result: Debt-service coverage; Cash after scheduled debt service (ratio; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — repayment capacity. Cash available for debt service = 860,000 LKR; Scheduled principal for same period = 500,000 LKR; Scheduled interest for same period = 120,000 LKR; Repayment and cash-flow period = Sample annual period. Results: Debt-service coverage = 1.387 ratio; Cash after scheduled debt service = 240,000 LKR. Interpretation: Debt-service coverage: 1.387 ratio. Next check: Review the cash-flow evidence and repayment conditions. Changed input. Change Cash available for debt service = 860,001. Result: Debt-service coverage = 1.387 ratio; Cash after scheduled debt service = 240,001 LKR. Interpretation: Debt-service coverage: 1.387 ratio. Next check: Review the cash-flow evidence and repayment conditions. Missing input. Omit Cash available for debt service. No usable result. Cash available for debt service Next check: Correct or obtain the missing input records. Information still needed: Cash available for debt service. Map context. No map inserted into this decision example Limits A coverage ratio is not a credit decision or a universal lending threshold. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Debt-service coverage Debt-service coverage Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP38-004DP38 | Sensitivity Compare investment viability under reviewed stress assumptions Inputs and examplePurpose Compare investment cash flows under explicit stress assumptions. Output Comparison table Next step Prepare cash-flow comparison creates an unassigned draft that is visible and downloadable, not sent. Rule NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5. Checks For Base cash-flow scenario, the default output explains Review the cash flows, discount assumptions and constraints. Changing Initial investment produces Review the cash flows, discount assumptions and constraints. Missing Initial investment remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Initial investment [LKR]; Net cash flow year1 [LKR]; Net cash flow year2 [LKR]; Net cash flow year3 [LKR]; Net cash flow year4 [LKR]; Net cash flow year5 [LKR]; Residual value at end of year5 [LKR]; Example discount rate [%] Result: Five-year net present value (LKR) Worked example. Fictional 2025 example. Base cash-flow scenario. Initial investment = 2,400,000 LKR; Net cash flow year1 = 400,000 LKR; Net cash flow year2 = 550,000 LKR; Net cash flow year3 = 680,000 LKR; Net cash flow year4 = 720,000 LKR; Net cash flow year5 = 760,000 LKR; Residual value at end of year5 = 120,000 LKR; Example discount rate = 8 %. Results: Five-year net present value = 109,847.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,847.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Changed input. Change Initial investment = 2,400,001. Result: Five-year net present value = 109,846.353 LKR. Interpretation: At the supplied 8% annual discount assumption, the five-year cash flows and residual value give 109,846.353 LKR net present value after the initial investment. The figure compares cash flows under these assumptions. Next check: Review the cash flows, discount assumptions and constraints. Missing input. Omit Initial investment. No usable result. Initial investment Next check: Correct or obtain the missing input records. Information still needed: Initial investment. Map context. No map inserted into this decision example Limits The example is not a probabilistic risk model or a credit approval. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Discounted net cash flows Financial net present value is the sum of discounted net benefits. Include the initial outlay at time zero. Sector guidance · Guidelines for defining financial economic environmental and social information The formula is supported. The five-year example, discount rate, cash flows and residual value need case review. Verify the current appraisal instructions for public investment. Implementation: prototype |
| DEC-DP38-006DP38 | Environmental and social risk Evaluate documented environmental and social controls Inputs and examplePurpose Find missing environmental and social control evidence. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — environmental and social risk, the default output explains Obtain the missing evidence listed below. Changing Project screening, Project screening evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Project screening remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Project screening; Project screening evidence reference; permits; permits evidence reference; affected people; affected people evidence reference; safeguards; safeguards evidence reference; controls; controls evidence reference; lender policy; lender policy evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — environmental and social risk. Project screening = Missing; Project screening evidence reference = ; permits = Documented; permits evidence reference = Sample Laggala Pallegama field register / 2025; affected people = Documented; affected people evidence reference = Sample Laggala Pallegama field register / 2025; safeguards = Documented; safeguards evidence reference = Sample Laggala Pallegama field register / 2025; controls = Documented; controls evidence reference = Sample Laggala Pallegama field register / 2025; lender policy = Documented; lender policy evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this environmental and social risk case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Project screening = Documented; Project screening evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle environmental and social risk. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Project screening. The required evidence is incomplete for this environmental and social risk case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Project screening: Missing. Map context. No map inserted into this decision example Limits Checklist completeness does not establish compliance or acceptable residual risk. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Review environmental and social risks and controls Identify project impacts and check that the management program sets out measures to avoid or mitigate them. Sector guidance · Sustainable Finance Confirm the financing policy, scope, evidence, legal duties and review authority. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP38-007DP38 | Green taxonomy Refer proposed green-finance classifications for verification Inputs and examplePurpose Find missing source and scheme evidence for a green-finance classification referral. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — green taxonomy, the default output explains Obtain the missing evidence listed below. Changing Activity, Activity evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Activity remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Activity; Activity evidence reference; taxonomy edition; taxonomy edition evidence reference; technical criteria; technical criteria evidence reference; safeguards; safeguards evidence reference; evidence; evidence evidence reference; reviewer; reviewer evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — green taxonomy. Activity = Missing; Activity evidence reference = ; taxonomy edition = Documented; taxonomy edition evidence reference = Sample Laggala Pallegama field register / 2025; technical criteria = Documented; technical criteria evidence reference = Sample Laggala Pallegama field register / 2025; safeguards = Documented; safeguards evidence reference = Sample Laggala Pallegama field register / 2025; evidence = Documented; evidence evidence reference = Sample Laggala Pallegama field register / 2025; reviewer = Documented; reviewer evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this green taxonomy case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Activity = Documented; Activity evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle green taxonomy. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Activity. The required evidence is incomplete for this green taxonomy case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Activity: Missing. Map context. No map inserted into this decision example Limits The prototype does not certify a green label or grant preferential finance. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Green-finance activity screening Match the economic activity to its taxonomy row and check the activity-specific metric, threshold and do-no-significant-harm evidence. Confirm the current taxonomy and evidence with the responsible institution. This is a review step for the activity, not a lending decision. Implementation: prototype Method source: proposed SHARED rule. Retained context sourcesLOCAL-SRS12, LOCAL-SRS21, S73, S43, S44 Context alone does not validate the formula. |
| DEC-DP38-009DP38 | Seasonal lending Compare repayment schedules with agricultural cash generation Inputs and examplePurpose Compare seasonal cash available for debt service with the stated repayment obligations. Output Comparison table Next step Prepare repayment review creates an unassigned draft that is visible and downloadable, not sent. Rule Debt-service coverage = cash available / (principal + interest) for the same period. Zero scheduled debt has no coverage ratio. Checks For June pre-harvest repayment window, the default output explains Review the cash-flow evidence and repayment conditions. Changing Cash available for debt service produces Review the cash-flow evidence and repayment conditions. Missing Cash available for debt service remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available for debt service [LKR]; Scheduled principal for same period [LKR]; Scheduled interest for same period [LKR]; Repayment and cash-flow period Result: Debt-service coverage; Cash after scheduled debt service (ratio; LKR) Worked example. Fictional 2025 example. June pre-harvest repayment window. Cash available for debt service = 80,000 LKR; Scheduled principal for same period = 100,000 LKR; Scheduled interest for same period = 20,000 LKR; Repayment and cash-flow period = June payment window / same cash and debt basis. Results: Debt-service coverage = 0.667 ratio; Cash after scheduled debt service = -40,000 LKR. Interpretation: Debt-service coverage: 0.667 ratio. Next check: Review the cash-flow evidence and repayment conditions. Changed input. Change Cash available for debt service = 80,001. Result: Debt-service coverage = 0.667 ratio; Cash after scheduled debt service = -39,999 LKR. Interpretation: Debt-service coverage: 0.667 ratio. Next check: Review the cash-flow evidence and repayment conditions. Missing input. Omit Cash available for debt service. No usable result. Cash available for debt service Next check: Correct or obtain the missing input records. Information still needed: Cash available for debt service. Map context. No map inserted into this decision example Limits An aggregate ratio does not establish that every instalment can be paid on time. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Debt-service coverage Debt-service coverage Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP38-010DP38 | Portfolio concentration Review sector geography and counterparty exposure concentration Inputs and examplePurpose Review lending exposure by the stated sectors, districts and counterparties. Output Comparison table Next step Prepare concentration review creates an unassigned draft that is visible and downloadable, not sent. Rule Start from distinct loan exposures counted once. For each dimension separately, sum exposure by sector, district or counterparty; divide each group amount by the same complete portfolio total, then sum its squared fractional shares. Report three separate 0–1 HHIs, not one index across mixed dimensions. Checks For Laggala seasonal-paddy loan scenario, the default output explains Review the complete portfolio, category definitions and exposure constraints. Changing Outstanding exposure of this distinct loan produces Review the complete portfolio, category definitions and exposure constraints. Missing Outstanding exposure of this distinct loan remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Outstanding exposure of this distinct loan [LKR]; Sector classification; District classification; Distinct counterparty reference Result: Outstanding loan exposure; This loan’s share of the selected portfolio (LKR; %) Worked example. Fictional 2025 example. Laggala seasonal-paddy loan scenario. Outstanding exposure of this distinct loan = 7,500,000 LKR; Sector classification = Agriculture; District classification = Matale; Distinct counterparty reference = Laggala cooperative scenario. Results: Outstanding loan exposure = 7,500,000 LKR; This loan’s share of the selected portfolio = 42.857 %. Interpretation: Outstanding loan exposure: 7,500,000 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Changed input. Change Outstanding exposure of this distinct loan = 7,500,001. Result: Outstanding loan exposure = 7,500,001 LKR; This loan’s share of the selected portfolio = 42.857 %. Interpretation: Outstanding loan exposure: 7,500,001 LKR. Next check: Review the complete portfolio, category definitions and exposure constraints. Missing input. Omit Outstanding exposure of this distinct loan. No usable result. Compatible category amount Next check: Correct or obtain the missing input records. Information still needed: Compatible category amount. Selected-frame statistics. total = 17,500,000; hhiSector = 0.496; hhiDistrict = 0.463; hhiCounterparty = 0.352 Map context. No map inserted into this decision example Limits Concentration alone does not establish probability of loss or a prudential limit. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required HHI concentration component HHI concentration component Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP38-014DP38 | Impact claims Review evidence supporting financed environmental and social outcomes Inputs and examplePurpose Compare financed outcome observations across the supplied groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — impact claims, the default output explains Obtain the missing evidence listed below. Changing Intervention group households with the stated functioning water service in the financed-project frame before produces Obtain the missing evidence listed below. Missing Intervention group households with the stated functioning water service in the financed-project frame before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Intervention group households with the stated functioning water service in the financed-project frame before [%]; Intervention group households with the stated functioning water service in the financed-project frame after [%]; Comparison group households with the stated functioning water service in the financed-project frame before [%]; Comparison group households with the stated functioning water service in the financed-project frame after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (percentage points) Worked example. Fictional 2025 example. Laggala Pallegama — impact claims. Intervention group households with the stated functioning water service in the financed-project frame before = 42 %; Intervention group households with the stated functioning water service in the financed-project frame after = 59 %; Comparison group households with the stated functioning water service in the financed-project frame before = 39 %; Comparison group households with the stated functioning water service in the financed-project frame after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Fictional measure: Households with the stated functioning water service in the financed-project frame / matching frame, method and before-after windows. Results: Difference in changes = 10 percentage points. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Intervention group households with the stated functioning water service in the financed-project frame before = 42.42. Result: Difference in changes = 9.58 percentage points. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 percentage points. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Intervention group households with the stated functioning water service in the financed-project frame before. No usable result. Treatment Verified environmental/social indicator before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified environmental/social indicator before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish an attributable financed impact. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP38-018DP38 | Liquidity planning Compare expected funding inflows with committed disbursements Inputs and examplePurpose Review chronological funding and disbursement cash events for temporary gaps. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Order the supplied dated receipts and payments. Start with the stated opening cash; add each receipt and subtract each payment once. Minimum cash is the lowest chronological balance, including opening cash. Shortfall = max(0, −minimum cash). Closing cash is opening + receipts − payments. Checks For Committed disbursement cash-plan scenario, the default output explains Review funding and payment timing before committing. Changing Cash available before the first dated event produces Review funding and payment timing before committing. Missing Cash available before the first dated event remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Cash available before the first dated event [LKR]; Committed disbursement date; Committed disbursement [LKR]; Other committed disbursement date; Other committed disbursement [LKR]; Expected funding receipt date; Expected funding receipt [LKR] Result: Minimum projected cash; Maximum projected cash shortfall; Projected closing cash (LKR; LKR; LKR) Worked example. Fictional 2025 example. Committed disbursement cash-plan scenario. Cash available before the first dated event = 5,000,000 LKR; Committed disbursement date = 2025-06-01; Committed disbursement = 12,500,000 LKR; Other committed disbursement date = 2025-06-08; Other committed disbursement = 2,500,000 LKR; Expected funding receipt date = 2025-06-25; Expected funding receipt = 19,000,000 LKR. Results: Minimum projected cash = -10,000,000 LKR; Maximum projected cash shortfall = 10,000,000 LKR; Projected closing cash = 9,000,000 LKR. Interpretation: Lowest projected cash: -10000000.00 LKR; shortfall: 10000000.00 LKR; closing cash: 9000000.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Changed input. Change Cash available before the first dated event = 5,000,001. Result: Minimum projected cash = -9,999,999 LKR; Maximum projected cash shortfall = 9,999,999 LKR; Projected closing cash = 9,000,001 LKR. Interpretation: Lowest projected cash: -9999999.00 LKR; shortfall: 9999999.00 LKR; closing cash: 9000001.00 LKR. The chronological events explain the difference. Next check: Review funding and payment timing before committing. Missing input. Omit Cash available before the first dated event. No usable result. Cash available before the first dated event Next check: Correct or obtain the missing input records. Information still needed: Cash available before the first dated event. Map context. No map inserted into this decision example Limits A closing surplus does not establish that every commitment can be met when due. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing, Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP38-019DP38 | Adaptation finance Compare financing alternatives for resilient farm and enterprise investments Inputs and examplePurpose Compare financing alternatives using terms, cash timing and investment constraints. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Term-loan financing, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Term-loan financing. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Investigate a term loan.; Resource needs and adverse effects = Needs lender terms, cash timing, collateral conditions and repayment capacity.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Adaptation options; costs; cash benefits; risk changes; terms; evidence. Map context. No map inserted into this decision example Limits A budget balance does not establish affordable or suitable finance. Authorized credit/risk analyst and environmental/social specialist | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Green Book Supplementary Guidance on Multi-Criteria Decision Analysis Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP39-002DP39 | Service delivery Review claims for physically verified environmental services Inputs and examplePurpose Separate agreed, checked, accepted, failed and pending hectares in the annual agreement. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Checked area = area meeting conditions + area needing correction. Agreed area = checked area + area not checked. Do not pay for unvisited or failed area. Checks For Laggala Pallegama farmer group, the default output explains Check the remaining area and correct failed work. Changing Area meeting the agreed conditions, Checked area needing correction produces Check the remaining area and correct failed work. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Area in the annual agreement [ha]; Area visited and checked [ha]; Area meeting the agreed conditions [ha]; Checked area needing correction [ha]; Area not checked yet [ha]; Signed field-check record; Field record and protocol Result: Area meeting the conditions; Area still to check; Area needing correction (ha; ha; ha) Worked example. Fictional 2025 example. Laggala Pallegama farmer group. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Area in the annual agreement = 24 ha; Area visited and checked = 22 ha; Area meeting the agreed conditions = 20 ha; Checked area needing correction = 2 ha; Area not checked yet = 2 ha; Signed field-check record = Documented; Field record and protocol = Example field record / riverbank care checklist 1. Results: Area meeting the conditions = 20 ha; Area still to check = 2 ha; Area needing correction = 2 ha. Interpretation: 20 ha meet the example conditions; 2 ha need correction and 2 ha still need a visit. Next check: Check the remaining area and correct failed work. Changed input. Change Area meeting the agreed conditions = 21; Checked area needing correction = 1. Result: Area meeting the conditions = 21 ha; Area still to check = 2 ha; Area needing correction = 1 ha. Interpretation: 21 ha meet the example conditions; 1 ha need correction and 2 ha still need a visit. Next check: Check the remaining area and correct failed work. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version. Map context. No map inserted into this decision example Limits Accepted hectares do not establish measured downstream water-quality improvement. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Link proposed payment to verified service delivery Use monitoring evidence to check that the contracted activity or service was delivered before recommending payment. Sector guidance · Designing Effective Payments for Environmental Services Confirm eligible services, proof, payment terms, caps and the authorized approval process. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP39-003DP39 | Service accounting Reconcile physical ecosystem services with separate monetary accounts Inputs and examplePurpose Keep the physical service log separate from proposed, authorised and recorded payments. Output Comparison table Next step Prepare account comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Keep hectares separate from rupees. Unpaid authorised amount = authorised amount − paid amount. A contract payment is not a monetary value of the ecosystem. Checks For Laggala Pallegama farmer group, the default output explains Keep this as a proposal until separately authorised. Changing Area meeting annual conditions produces Keep this as a proposal until separately authorised. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Area meeting annual conditions [ha]; Payment proposed for this agreement and year [LKR]; Payment authorised in a separate decision [LKR]; Payment actually recorded [LKR]; Payment record or pending reference Result: Area meeting the conditions; Proposed payment; Recorded payment; Authorised amount not yet paid (ha; LKR; LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama farmer group. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Area meeting annual conditions = 20 ha; Payment proposed for this agreement and year = 250,000 LKR; Payment authorised in a separate decision = 0 LKR; Payment actually recorded = 0 LKR; Payment record or pending reference = No payment authorised or paid in this example. Results: Area meeting the conditions = 20 ha; Proposed payment = 250,000 LKR; Recorded payment = 0 LKR; Authorised amount not yet paid = 0 LKR. Interpretation: 20 ha in the physical log; LKR 250,000 proposed and LKR 0 recorded as paid. These are different records. Next check: Keep this as a proposal until separately authorised. Changed input. Change Area meeting annual conditions = 21. Result: Area meeting the conditions = 21 ha; Proposed payment = 250,000 LKR; Recorded payment = 0 LKR; Authorised amount not yet paid = 0 LKR. Interpretation: 21 ha in the physical log; LKR 250,000 proposed and LKR 0 recorded as paid. These are different records. Next check: Keep this as a proposal until separately authorised. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version. Map context. No map inserted into this decision example Limits Hectares and currency are separate accounts and must not be added together. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Keep physical and monetary service accounts distinct Record physical ecosystem service quantities and monetary service flows in their respective accounts using consistent scope. Sector guidance · SEEA Ecosystem Accounting Confirm service definitions, aggregation, valuation basis and agreement boundaries. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP39-007DP39 | Additionality Assess whether proposed services exceed a credible baseline Inputs and examplePurpose Compare ground-cover changes with the stated baseline and comparison observations. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Difference in differences = (scheme after − before) − (comparison after − before). The arithmetic alone does not prove that the payment caused an improvement. Checks For Laggala Pallegama farmer group, the default output explains Ask a specialist to assess additionality and the study assumptions. Changing Scheme ground cover after produces Ask a specialist to assess additionality and the study assumptions. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Scheme ground cover before [%]; Scheme ground cover after [%]; Comparison ground cover before [%]; Comparison ground cover after [%]; Earlier observation; Later observation; Comparable sites, season and method documented; Baseline and existing obligations Result: Difference between the two changes; Change inside the scheme; Change at the comparison site (percentage points; percentage points; percentage points) Worked example. Fictional 2025 example. Laggala Pallegama farmer group. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Scheme ground cover before = 60 %; Scheme ground cover after = 85 %; Comparison ground cover before = 62 %; Comparison ground cover after = 67 %; Earlier observation = 2024-06-30; Later observation = 2025-06-30; Comparable sites, season and method documented = Documented; Baseline and existing obligations = Fixed-point ground-cover survey; existing duties checked separately — example. Results: Difference between the two changes = 20 percentage points; Change inside the scheme = 25 percentage points; Change at the comparison site = 5 percentage points. Interpretation: Ground cover improved 20 percentage points more than at the comparison site. This does not alone establish a causal effect or an extra payable service. Next check: Ask a specialist to assess additionality and the study assumptions. Changed input. Change Scheme ground cover after = 86. Result: Difference between the two changes = 21 percentage points; Change inside the scheme = 26 percentage points; Change at the comparison site = 5 percentage points. Interpretation: Ground cover improved 21 percentage points more than at the comparison site. This does not alone establish a causal effect or an extra payable service. Next check: Ask a specialist to assess additionality and the study assumptions. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version. Map context. No map inserted into this decision example Limits A difference in changes does not establish causation or an additional payable service. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP39-008DP39 | Leakage Investigate displaced environmental impacts outside agreement areas Inputs and examplePurpose Compare neighbouring clearing with a separate fixed comparison area and period. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Compare changes over the same observation window: (neighbour after − before) − (comparison after − before). A positive difference is a reason to investigate, not proof that the scheme caused clearing. Checks For Laggala Pallegama farmer group, the default output explains Investigate neighbouring clearing and possible causes. Changing New clearing in the neighbouring area after produces Investigate neighbouring clearing and possible causes. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; New clearing in the neighbouring area before [ha]; New clearing in the neighbouring area after [ha]; New clearing in a separate comparison area before [ha]; New clearing in the comparison area after [ha]; Earlier observation; Later observation; Equal observation windows and fixed comparable areas documented; Map and field-check reference Result: Difference between the two increases; Increase in neighbouring clearing; Increase in comparison-area clearing (ha; ha; ha) Worked example. Fictional 2025 example. Laggala Pallegama farmer group. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; New clearing in the neighbouring area before = 0.6 ha; New clearing in the neighbouring area after = 1.4 ha; New clearing in a separate comparison area before = 0.4 ha; New clearing in the comparison area after = 0.5 ha; Earlier observation = 2024-06-30; Later observation = 2025-06-30; Equal observation windows and fixed comparable areas documented = Documented; Map and field-check reference = Two fixed 200 ha observation areas; same clearing definition and season — example. Results: Difference between the two increases = 0.7 ha; Increase in neighbouring clearing = 0.8 ha; Increase in comparison-area clearing = 0.1 ha. Interpretation: Neighbouring clearing increased by 0.8 ha; comparison-area clearing increased by 0.1 ha. The extra 0.7 ha is a signal to investigate, not proof of displacement caused by the agreement. Next check: Investigate neighbouring clearing and possible causes. Changed input. Change New clearing in the neighbouring area after = 1.5. Result: Difference between the two increases = 0.8 ha; Increase in neighbouring clearing = 0.9 ha; Increase in comparison-area clearing = 0.1 ha. Interpretation: Neighbouring clearing increased by 0.9 ha; comparison-area clearing increased by 0.1 ha. The extra 0.8 ha is a signal to investigate, not proof of displacement caused by the agreement. Next check: Investigate neighbouring clearing and possible causes. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version. Map context. No map inserted into this decision example Limits The difference is a reason to investigate, not proof of displacement caused by the agreement. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP39-010DP39 | Contract design Compare feasible service agreements and provider obligations Inputs and examplePurpose Compare agreement payments, checking costs and mandatory service conditions. Output Comparison table Next step Prepare case-review note creates an unassigned draft that is visible and downloadable, not sent. Rule Total cost = provider payment + checking cost. Compare with the matching annual budget and review every safeguard. Lower cost alone does not select the best agreement. Checks For Riverbank vegetation care, the default output explains Compare the benefits and obligations with the parties. Changing Proposed provider payment produces Compare the benefits and obligations with the parties. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Proposed provider payment [LKR/year]; Monitoring and checking cost [LKR/year]; Available annual scheme budget [LKR/year]; Work can be checked with a defined protocol; Rights and voluntary participation documented; Livelihood and environmental safeguards documented; Intended benefit and evidence needed Result: Annual budget left after the proposal; Total annual scheme cost (LKR/year; LKR/year) Worked example. Fictional 2025 example. Riverbank vegetation care. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Proposed provider payment = 300,000 LKR/year; Monitoring and checking cost = 100,000 LKR/year; Available annual scheme budget = 450,000 LKR/year; Work can be checked with a defined protocol = Documented; Rights and voluntary participation documented = Documented; Livelihood and environmental safeguards documented = Documented; Intended benefit and evidence needed = Riverbank vegetation and soil cover; monitor stream conditions separately. Results: Annual budget left after the proposal = 50,000 LKR/year; Total annual scheme cost = 400,000 LKR/year. Interpretation: Provider payment plus checking costs LKR 400,000 per year. Budget balance: LKR 50,000. Next check: Compare the benefits and obligations with the parties. Changed input. Change Proposed provider payment = 301,000. Result: Annual budget left after the proposal = 49,000 LKR/year; Total annual scheme cost = 401,000 LKR/year. Interpretation: Provider payment plus checking costs LKR 401,000 per year. Budget balance: LKR 49,000. Next check: Compare the benefits and obligations with the parties. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version. Map context. No map inserted into this decision example Limits A budget balance does not establish a measurable, lawful or suitable agreement. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Designing Effective Payments for Environmental Services Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP39-011DP39 | Payment proposals Prepare payment proposals only from approved verified conditions Inputs and examplePurpose Calculate a capped annual payment proposal from accepted hectares and the stated rate. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Annual proposal = min(accepted hectares × annual rate, annual cap). Subtract payments for the same agreement and year. Refer an amount only when required evidence is documented. This screen makes no payment. Checks For Laggala Pallegama farmer group, the default output explains Obtain the missing evidence listed below. Changing Area meeting the annual agreement conditions produces Obtain the missing evidence listed below. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Area meeting the annual agreement conditions [ha]; Illustrative annual rate per accepted hectare [LKR/ha/year]; Annual cap for this agreement [LKR/year]; Amount already paid for these same annual conditions [LKR]; Independent field-check record documented; Rights and voluntary agreement documented; Funding confirmation documented; Field-check and rate references; Confirmed funds available for this annual proposal [LKR] Result: Calculated annual proposal before payments; Proposal less amount already paid; Amount ready to refer for authorisation (LKR; LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama farmer group. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Area meeting the annual agreement conditions = 20 ha; Illustrative annual rate per accepted hectare = 12,500 LKR/ha/year; Annual cap for this agreement = 300,000 LKR/year; Amount already paid for these same annual conditions = 0 LKR; Independent field-check record documented = Documented; Rights and voluntary agreement documented = Documented; Funding confirmation documented = Missing; Field-check and rate references = Example field record / draft annual rate schedule 1; Confirmed funds available for this annual proposal = 200,000 LKR. Results: Calculated annual proposal before payments = 250,000 LKR; Proposal less amount already paid = 250,000 LKR; Amount ready to refer for authorisation = Unavailable LKR. Interpretation: 20 ha × LKR 12,500 per ha/year = LKR 250,000, capped at LKR 300,000. Annual proposal: LKR 250,000. Confirm the evidence and matching funds; no amount is ready for authorisation. Next check: Obtain the missing evidence listed below. Changed input. Change Area meeting the annual agreement conditions = 21. Result: Calculated annual proposal before payments = 262,500 LKR; Proposal less amount already paid = 262,500 LKR; Amount ready to refer for authorisation = Unavailable LKR. Interpretation: 21 ha × LKR 12,500 per ha/year = LKR 262,500, capped at LKR 300,000. Annual proposal: LKR 262,500. Confirm the evidence and matching funds; no amount is ready for authorisation. Next check: Obtain the missing evidence listed below. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version; Funding confirmation documented: Missing. Map context. No map inserted into this decision example Limits The illustrative rate is not an official entitlement; no payment is authorised here. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Link proposed payment to verified service delivery Use monitoring evidence to check that the contracted activity or service was delivered before recommending payment. Sector guidance · Designing Effective Payments for Environmental Services Confirm eligible services, proof, payment terms, caps and the authorized approval process. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP39-019DP39 | Renewal decisions Compare renewal redesign and closure of PES agreements Inputs and examplePurpose Compare renewal, redesign and closure with outcomes, feedback and remaining obligations. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Compare renewal, redesign and closure separately. Record the obligations and effects of each; no automatic renewal or closure follows from the cheapest cost. Checks For Renew the agreement, the default output explains Obtain the missing evidence listed below. Changing Estimated next-period cost or closure cost produces Obtain the missing evidence listed below. Missing Agreement and version remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Agreement and version; Who carries out the work; Who funds the agreement; Choice to review; Estimated next-period cost or closure cost [LKR]; Results and outstanding obligations reviewed; Provider feedback reviewed; Funding or closure resources confirmed; Work or commitments that still need attention Result: Cost of this choice to compare (LKR) Worked example. Fictional 2025 example. Renew the agreement. Agreement and version = Laggala Pallegama riverbank care / draft 1; Who carries out the work = Laggala Pallegama farmer group — example; Who funds the agreement = Downstream water-user fund — example; Choice to review = Renew the agreement; Estimated next-period cost or closure cost = 400,000 LKR; Results and outstanding obligations reviewed = Documented; Provider feedback reviewed = Documented; Funding or closure resources confirmed = Missing; Work or commitments that still need attention = Complete outstanding field checks before any renewal. Results: Cost of this choice to compare = 400,000 LKR. Interpretation: Renew the agreement. Estimated cost: LKR 400,000. Remaining obligation: Complete outstanding field checks before any renewal. Next check: Obtain the missing evidence listed below. Changed input. Change Estimated next-period cost or closure cost = 401,000. Result: Cost of this choice to compare = 401,000 LKR. Interpretation: Renew the agreement. Estimated cost: LKR 401,000. Remaining obligation: Complete outstanding field checks before any renewal. Next check: Obtain the missing evidence listed below. Missing input. Omit Agreement and version. No usable result. Agreement and version Next check: Correct or obtain the missing input records. Information still needed: Agreement and version; Funding or closure resources confirmed: Missing. Map context. No map inserted into this decision example Limits Lowest cost alone does not select a responsible agreement outcome. Scheme technical lead, independent verifier and rights/finance reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Payments for Ecosystem Services in Sri Lanka Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-001DP40 | Dataset selection Select datasets suitable for spatial and temporal comparison Inputs and examplePurpose Find missing spatial, temporal and definition evidence before comparing datasets. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — dataset selection, the default output explains Obtain the missing evidence listed below. Changing Coverage, Coverage evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Coverage remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Coverage; Coverage evidence reference; dates; dates evidence reference; methods; methods evidence reference; units; units evidence reference; sampling; sampling evidence reference; rights; rights evidence reference; source versions; source versions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — dataset selection. Coverage = Missing; Coverage evidence reference = ; dates = Documented; dates evidence reference = Sample Laggala Pallegama field register / 2025; methods = Documented; methods evidence reference = Sample Laggala Pallegama field register / 2025; units = Documented; units evidence reference = Sample Laggala Pallegama field register / 2025; sampling = Documented; sampling evidence reference = Sample Laggala Pallegama field register / 2025; rights = Documented; rights evidence reference = Sample Laggala Pallegama field register / 2025; source versions = Documented; source versions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this dataset selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Coverage = Documented; Coverage evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle dataset selection. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Coverage. The required evidence is incomplete for this dataset selection case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Coverage: Missing. Map context. No map inserted into this decision example Limits Matching labels or years do not establish compatible measures or boundaries. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check essential geographic metadata Check dataset identity, date, spatial coverage and lineage where applicable. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the authoritative edition and the source-specific spatial, temporal and use limits. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-002DP40 | Intervention research Compare validated soil and forest outcomes across interventions Inputs and examplePurpose Compare soil or forest outcomes in the supplied groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — intervention research, the default output explains Obtain the missing evidence listed below. Changing Treatment Comparable soil-carbon stock before produces Obtain the missing evidence listed below. Missing Treatment Comparable soil-carbon stock before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Comparable soil-carbon stock before [t C/ha]; Treatment Comparable soil-carbon stock after [t C/ha]; Comparison Comparable soil-carbon stock before [t C/ha]; Comparison Comparable soil-carbon stock after [t C/ha]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (t C/ha) Worked example. Fictional 2025 example. Laggala Pallegama — intervention research. Treatment Comparable soil-carbon stock before = 42 t C/ha; Treatment Comparable soil-carbon stock after = 59 t C/ha; Comparison Comparable soil-carbon stock before = 39 t C/ha; Comparison Comparable soil-carbon stock after = 46 t C/ha; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Comparable soil-carbon stock /example matching definition1. Results: Difference in changes = 10 t C/ha. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 t C/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Comparable soil-carbon stock before = 42.42. Result: Difference in changes = 9.58 t C/ha. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 t C/ha. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Comparable soil-carbon stock before. No usable result. Treatment Comparable soil-carbon stock before Next check: Correct or obtain the missing input records. Information still needed: Treatment Comparable soil-carbon stock before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish an intervention effect. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP40-003DP40 | Sampling limitations Identify biodiversity comparisons limited by survey design Inputs and examplePurpose Check biodiversity counts against survey effort, season and protocol. Output Comparison table Next step Prepare biodiversity comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred. Checks For Laggala Pallegama — sampling limitations, the default output explains Review survey comparability. Changing Observed distinct species produces Review survey comparability. Missing Observed distinct species remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Observed distinct species [species]; Survey effort [hours]; Survey protocol and version; Survey season and taxonomic scope; All planned survey visits completed Result: Observed richness; Recorded effort (species; hours) Worked example. Fictional 2025 example. Laggala Pallegama — sampling limitations. Observed distinct species = 28 species; Survey effort = 18 hours; Survey protocol and version = Sample protocol1; Survey season and taxonomic scope = Sample matched season / taxon group; All planned survey visits completed = Yes. Results: Observed richness = 28 species; Recorded effort = 18 hours. Interpretation: Observed richness: 28 species. Review survey comparability. Next check: Review survey comparability. Changed input. Change Observed distinct species = 29. Result: Observed richness = 29 species; Recorded effort = 18 hours. Interpretation: Observed richness: 29 species. Review survey comparability. Next check: Review survey comparability. Missing input. Omit Observed distinct species. No usable result. Observed distinct species Next check: Correct or obtain the missing input records. Information still needed: Observed distinct species. Map context. No map inserted into this decision example Limits Observed richness does not establish complete species presence or absence. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check whether biological surveys are comparable Retain the survey protocol, effort and event scope when comparing observations. Confirm season, coverage, species identification and any difference in detectability. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-004DP40 | Expert review Prioritize scientific estimates awaiting independent assessment Inputs and examplePurpose Identify scientific-assessment cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — expert review, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — expert review. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish scientific importance or acceptance. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Measuring the Success of Your Service Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-006DP40 | Ethics and permissions Check research approvals before collecting restricted evidence Inputs and examplePurpose Find missing research authority, access and ethical records before collection. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — ethics and permissions, the default output explains Obtain the missing evidence listed below. Changing Protocol, Protocol evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Protocol remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Protocol; Protocol evidence reference; participants; participants evidence reference; consent; consent evidence reference; permits; permits evidence reference; ethics review; ethics review evidence reference; location; location evidence reference; conditions; conditions evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — ethics and permissions. Protocol = Missing; Protocol evidence reference = ; participants = Documented; participants evidence reference = Sample Laggala Pallegama field register / 2025; consent = Documented; consent evidence reference = Sample Laggala Pallegama field register / 2025; permits = Documented; permits evidence reference = Sample Laggala Pallegama field register / 2025; ethics review = Documented; ethics review evidence reference = Sample Laggala Pallegama field register / 2025; location = Documented; location evidence reference = Sample Laggala Pallegama field register / 2025; conditions = Documented; conditions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this ethics and permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Protocol = Documented; Protocol evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle ethics and permissions. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Protocol. The required evidence is incomplete for this ethics and permissions case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Protocol: Missing. Map context. No map inserted into this decision example Limits The prototype does not grant a permit or authorise restricted data collection. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Protected wildlife research permit check Refer regulated research involving protected species or protected areas for DWC permit review. Check the proposal, methods, site and proposed collections. Sector guidance · Environmental and Social Framework Confirm any additional ethics, collection or site-access requirements with the competent bodies. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-009DP40 | Data cleaning Resolve contradictory measurements without altering originals Inputs and examplePurpose Compare conflicting measurements under matching units and definitions. Output Case/evidence table Next step Prepare source comparison creates an unassigned draft that is visible and downloadable, not sent. Rule Later/comparison value minus Earlier/source value. Relative change = 100 × difference / Earlier/source value when the earlier value is positive. Checks For Laggala Pallegama — data cleaning, the default output explains Reconcile the original records using their source references. Changing Original source measurement produces Reconcile the original records using their source references. Missing Original source measurement remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original source measurement [t C/ha]; Independent comparison measurement [t C/ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition Result: Difference; Relative change (t C/ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — data cleaning. Original source measurement = 100 t C/ha; Independent comparison measurement = 90 t C/ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable t C/ha measure; same input scope. Results: Difference = -10 t C/ha; Relative change = -10 %. Interpretation: Difference: -10 t C/ha. Next check: Reconcile the original records using their source references. Changed input. Change Original source measurement = 101. Result: Difference = -11 t C/ha; Relative change = -10.891 %. Interpretation: Difference: -11 t C/ha. Next check: Reconcile the original records using their source references. Missing input. Omit Original source measurement. No usable result. Original source measurement Next check: Correct or obtain the missing input records. Information still needed: Original source measurement. Map context. No map inserted into this decision example Limits A difference does not identify which original should change. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Relative difference against a positive reference 100 × (comparison value − reference value) ÷ reference value. Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-010DP40 | Reproducibility Reproduce reported results from exact evidence versions Inputs and examplePurpose Check reproducibility using the exact evidence and method versions. Output Comparison table Next step Prepare reproduction-check note creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — reproducibility, the default output explains Investigate reproduction difference. Changing Earlier/source value produces Investigate reproduction difference. Missing Earlier/source value remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Earlier/source value [t C/ha]; Independently reproduced value [t C/ha]; Original measurement unit; Comparison measurement unit; Compared measure and definition; Documented absolute comparison tolerance [t C/ha]; Expected input/method version; Reproduced input/method version; Original result creator; Independent reproducer Result: Difference; Relative change (t C/ha; %) Worked example. Fictional 2025 example. Laggala Pallegama — reproducibility. Earlier/source value = 100 t C/ha; Independently reproduced value = 90 t C/ha; Original measurement unit = Sample matching unit; Comparison measurement unit = Sample matching unit; Compared measure and definition = Sample comparable t C/ha measure; same input scope; Documented absolute comparison tolerance = 0.01 t C/ha; Expected input/method version = Sample input1 /method1; Reproduced input/method version = Sample input1 /method1; Original result creator = Preparation officer; Independent reproducer = Independent checking officer. Results: Difference = -10 t C/ha; Relative change = -10 %. Interpretation: Difference: -10 t C/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Changed input. Change Earlier/source value = 101. Result: Difference = -11 t C/ha; Relative change = -10.891 %. Interpretation: Difference: -11 t C/ha. Investigate reproduction difference. Next check: Investigate reproduction difference. Missing input. Omit Earlier/source value. No usable result. Earlier/source value Next check: Correct or obtain the missing input records. Information still needed: Earlier/source value. Map context. No map inserted into this decision example Limits Arithmetic consistency does not establish the scientific validity of the original finding. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Reproduce a result from its original evidence Repeat the analysis with the same data, methods and computational conditions and compare the outputs. Confirm the versions, independent checker and material tolerance for the result. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-012DP40 | Causal interpretation Determine whether evidence supports causal claims Inputs and examplePurpose Find missing design evidence before a causal-claim review. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Laggala Pallegama — causal interpretation, the default output explains Obtain the missing evidence listed below. Changing Study design, Study design evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Study design remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Study design; Study design evidence reference; comparison; comparison evidence reference; baseline; baseline evidence reference; confounders; confounders evidence reference; attrition; attrition evidence reference; sensitivity; sensitivity evidence reference; assumptions; assumptions evidence reference Result: Study evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — causal interpretation. Study design = Missing; Study design evidence reference = ; comparison = Documented; comparison evidence reference = Sample Laggala Pallegama field register / 2025; baseline = Documented; baseline evidence reference = Sample Laggala Pallegama field register / 2025; confounders = Documented; confounders evidence reference = Sample Laggala Pallegama field register / 2025; attrition = Documented; attrition evidence reference = Sample Laggala Pallegama field register / 2025; sensitivity = Documented; sensitivity evidence reference = Sample Laggala Pallegama field register / 2025; assumptions = Documented; assumptions evidence reference = Sample Laggala Pallegama field register / 2025. Results: Study evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this causal interpretation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Study design = Documented; Study design evidence reference = DEMO-REVIEW-REFERENCE. Result: Study evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle causal interpretation. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Study design. The required evidence is incomplete for this causal interpretation case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Study design: Missing. Map context. No map inserted into this decision example Limits A checklist does not establish causal identification. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Check what a study design can support Check outcomes, comparison, baseline and follow-up evidence against the study design before attributing effects. Sector guidance · Impact Evaluation in Practice, second edition Confirm identification assumptions, population, missing follow-up and analytical limitations. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-014DP40 | Research funding Compare study proposals under budget and evidence constraints Inputs and examplePurpose Compare study proposals using the question, design, safeguards and budget. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Small controlled pilot, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Small controlled pilot. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Run a small controlled pilot.; Resource needs and adverse effects = Needs valid allocation, outcomes, safeguards and a testable decision rule.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Proposal; scientific value; feasibility; costs; ethics; dependencies; alternatives. Map context. No map inserted into this decision example Limits A budget balance does not establish scientific validity or permission to proceed. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Impact Evaluation in Practice, second edition Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-018DP40 | Knowledge transfer Prepare evidence packages for specific institutional decisions Inputs and examplePurpose Find missing source, version and decision-context references in an evidence package. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — knowledge transfer, the default output explains Obtain the missing evidence listed below. Changing Target institutional decision, Target institutional decision evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Target institutional decision remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Target institutional decision; Target institutional decision evidence reference; Exact dataset, method and parameter versions; Exact dataset, method and parameter versions evidence reference; Findings and units; Findings and units evidence reference; Observation period and geographic coverage; Observation period and geographic coverage evidence reference; Limitations and uncertainty; Limitations and uncertainty evidence reference; Source rights and permitted sharing; Source rights and permitted sharing evidence reference; Named institutional recipient and review purpose; Named institutional recipient and review purpose evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — knowledge transfer. Target institutional decision = Missing; Target institutional decision evidence reference = ; Exact dataset, method and parameter versions = Documented; Exact dataset, method and parameter versions evidence reference = Sample Laggala Pallegama field register / 2025; Findings and units = Documented; Findings and units evidence reference = Sample Laggala Pallegama field register / 2025; Observation period and geographic coverage = Documented; Observation period and geographic coverage evidence reference = Sample Laggala Pallegama field register / 2025; Limitations and uncertainty = Documented; Limitations and uncertainty evidence reference = Sample Laggala Pallegama field register / 2025; Source rights and permitted sharing = Documented; Source rights and permitted sharing evidence reference = Sample Laggala Pallegama field register / 2025; Named institutional recipient and review purpose = Documented; Named institutional recipient and review purpose evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this knowledge transfer case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Target institutional decision = Documented; Target institutional decision evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle knowledge transfer. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Target institutional decision. The required evidence is incomplete for this knowledge transfer case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Target institutional decision: Missing. Map context. No map inserted into this decision example Limits A complete package does not establish a scientifically accepted conclusion. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Document dataset scope and revisions Retain dataset identity, coverage and version relationships when checking whether sources can be compared. Sector guidance · United Nations National Quality Assurance Frameworks Manual for Official Statistics Confirm the dataset-specific context and acceptable use, and record unresolved revisions. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP40-019DP40 | Research outcomes Evaluate use and effects of research outputs Inputs and examplePurpose Compare reported research-use outcomes across the supplied groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — research outcomes, the default output explains Obtain the missing evidence listed below. Changing Treatment Verified research recommendation uptake before produces Obtain the missing evidence listed below. Missing Treatment Verified research recommendation uptake before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Verified research recommendation uptake before [%]; Treatment Verified research recommendation uptake after [%]; Comparison Verified research recommendation uptake before [%]; Comparison Verified research recommendation uptake after [%]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (%) Worked example. Fictional 2025 example. Laggala Pallegama — research outcomes. Treatment Verified research recommendation uptake before = 42 %; Treatment Verified research recommendation uptake after = 59 %; Comparison Verified research recommendation uptake before = 39 %; Comparison Verified research recommendation uptake after = 46 %; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Verified research recommendation uptake /example matching definition1. Results: Difference in changes = 10 %. Interpretation: Treatment change: 17; comparison change: 7; difference in changes: 10 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Verified research recommendation uptake before = 42.42. Result: Difference in changes = 9.58 %. Interpretation: Treatment change: 16.58; comparison change: 7; difference in changes: 9.58 %. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Verified research recommendation uptake before. No usable result. Treatment Verified research recommendation uptake before Next check: Correct or obtain the missing input records. Information still needed: Treatment Verified research recommendation uptake before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish an effect caused by research use. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
| DEC-DP40-020DP40 | Scientific vocabulary Resolve inconsistent scientific variables and taxonomic labels Inputs and examplePurpose Find missing variable, taxonomic and edition definitions before joining records. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — scientific vocabulary, the default output explains Obtain the missing evidence listed below. Changing Original variable, Original variable evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Original variable remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Original variable; Original variable evidence reference; definition; definition evidence reference; unit; unit evidence reference; taxon reference; taxon reference evidence reference; edition; edition evidence reference; reviewed mapping; reviewed mapping evidence reference Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — scientific vocabulary. Original variable = Missing; Original variable evidence reference = ; definition = Documented; definition evidence reference = Sample Laggala Pallegama field register / 2025; unit = Documented; unit evidence reference = Sample Laggala Pallegama field register / 2025; taxon reference = Documented; taxon reference evidence reference = Sample Laggala Pallegama field register / 2025; edition = Documented; edition evidence reference = Sample Laggala Pallegama field register / 2025; reviewed mapping = Documented; reviewed mapping evidence reference = Sample Laggala Pallegama field register / 2025. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this scientific vocabulary case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Original variable = Documented; Original variable evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle scientific vocabulary. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Original variable. The required evidence is incomplete for this scientific vocabulary case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Original variable: Missing. Map context. No map inserted into this decision example Limits Matching names do not establish equivalent scientific concepts. Principal investigator, statistician and ethics/data-access reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Record documented mappings between source classifications Keep source concepts and use an explicit mapping to distinguish equivalence from approximate correspondence. Sector guidance · Guide for Publishing Biological Survey and Monitoring Data Confirm the authority and versions of both vocabularies. Leave unproven mappings unresolved. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-002DP41 | Community feedback Prioritize unresolved feedback and complaints Inputs and examplePurpose Identify unresolved community feedback cases past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — community feedback, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — community feedback. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish severity or a completed response. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-004DP41 | Service delays Escalate locations with prolonged community-service delays Inputs and examplePurpose Identify community-service cases past their recorded response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — service delays, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — service delays. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Delay does not establish its cause or service severity. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Community Engagement and Accountability Toolkit Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-005DP41 | Needs assessment Compare community priorities using inclusive evidence Inputs and examplePurpose Compare community proposals using inclusive needs, constraints and resources. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Essential water-service improvement, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Essential water-service improvement. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Improve the essential water service.; Resource needs and adverse effects = Needs quality, source, access, rights, engineering and maintenance evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Needs; affected groups; options; costs; feasibility; consultations; constraints. Map context. No map inserted into this decision example Limits Budget and stated benefits do not establish an agreed community priority. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Community Engagement and Accountability Toolkit Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-010DP41 | Climate adaptation Compare community-led adaptation alternatives Inputs and examplePurpose Compare adaptation choices using rights, exposure and livelihood evidence. Output Option comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule 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. Checks For Protect a community water source, the default output explains Obtain the missing records before choosing. Changing Required records available for this option, Reference for the required records, Applicable conditions, check result and supporting reference, Mandatory constraints produces Compare the documented trade-offs with the responsible reviewer. Missing Reference for the required records remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Option cost [LKR]; Available budget [LKR]; Mandatory constraints; Potential benefit and its evidence or assumption; Resource needs and adverse effects; Required records available for this option; Reference for the required records; Applicable conditions, check result and supporting reference Result: Budget remaining after option (LKR) Worked example. Fictional 2025 example. Protect a community water source. Option cost = 1,500,000 LKR; Available budget = 1,800,000 LKR; Mandatory constraints = Met; Potential benefit and its evidence or assumption = Protect the community water source.; Resource needs and adverse effects = Needs hydrology, quality, rights, community agreement and upkeep evidence.; Required records available for this option = Not provided; Reference for the required records = ; Applicable conditions, check result and supporting reference = . Results: Budget remaining after option = 300,000 LKR. Interpretation: 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 check: Obtain the missing records before choosing. Changed input. Change Required records available for this option = Documented for comparison; Reference for the required records = DEMO-DOMAIN-RECORDS; Applicable conditions, check result and supporting reference = DEMO-CONSTRAINT-REVIEW; Mandatory constraints = Met. Result: Budget remaining after option = 300,000 LKR. Interpretation: This option has stated benefits and trade-offs for review. No preferred option is selected. The supplied budget less cost is 300,000 LKR. Next check: Compare the documented trade-offs with the responsible reviewer. Missing input. Omit Reference for the required records. 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 check: Obtain the missing records before choosing. Information still needed: Records needed: Climate exposure; local knowledge; options; costs; livelihoods; safeguards. Map context. No map inserted into this decision example Limits A budget balance does not establish ecological suitability or community agreement. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Compare feasible project alternatives Compare the documented costs, benefits, feasibility and social and environmental effects of each option. Sector guidance · Monitoring and Evaluation of Adaptation at the National and Subnational Levels Confirm the case criteria and budget. Obtain the evidence needed to compare trade-offs. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-011DP41 | Community assets Prioritize repairs to shared livelihood and water assets Inputs and examplePurpose Identify shared livelihood or water-asset repairs past their response date. Output Exception worklist Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Open age = assessment date − received date. Days past due = max(0, assessment date − recorded due date) for open cases. Show documented critical conditions separately. Checks For Laggala Pallegama — community assets, the default output explains Follow up overdue case; confirm the missing condition evidence. Changing Received or defect observed produces Follow up overdue case; confirm the missing condition evidence. Missing Received or defect observed remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Received or defect observed; Recorded due date; Assessment date; Case/work closed; Documented critical unresolved condition; Responsible office or maintainer; Actual closure date when closed Result: Open days past due; Calendar age (days; days) Worked example. Fictional 2025 example. Laggala Pallegama — community assets. Received or defect observed = 2025-04-01; Recorded due date = 2025-06-01; Assessment date = 2025-06-30; Case/work closed = No; Documented critical unresolved condition = Unknown; Responsible office or maintainer = Proposed responsible office; Actual closure date when closed = . Results: Open days past due = 29 days; Calendar age = 90 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Changed input. Change Received or defect observed = 2025-03-31. Result: Open days past due = 29 days; Calendar age = 91 days. Interpretation: Open days past due: 29 days. Follow up overdue case. Next check: Follow up overdue case; confirm the missing condition evidence. Missing input. Omit Received or defect observed. No usable result. Received or defect observed Next check: Correct or obtain the missing input records. Information still needed: Received or defect observed; Documented critical unresolved condition: Unknown. Map context. No map inserted into this decision example Limits Age alone does not establish engineering urgency or a safe repair. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Measure how long an open case has been waiting Measure elapsed time from receipt of an open case to the assessment date. Sector guidance · Water Safety Plan Manual, second edition Use the institution’s own due dates, escalation rules and calendar. The publication supplies the elapsed-time method. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-013DP41 | Programme finance Reconcile community grants and verified expenditure Inputs and examplePurpose Reconcile community grants, receipts, expenditure and the matching closing balance. Output Comparison table Next step Prepare balance review creates an unassigned draft that is visible and downloadable, not sent. Rule Opening + receipts/additions − payments/reductions − other documented adjustments. Compare with independently recorded closing. A negative cash scenario is a shortfall, not an invalid water volume. Checks For Laggala Pallegama — programme finance, the default output explains Reconcile closing balance. Changing Opening cash/receivable balance produces Reconcile closing balance. Missing Opening cash/receivable balance remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Opening cash/receivable balance [LKR]; Receipts and documented additions [LKR]; Payments and documented reductions [LKR]; Other documented non-overlapping adjustments [LKR]; Independently recorded closing balance [LKR] Result: Calculated closing balance; Recorded minus calculated closing (LKR; LKR) Worked example. Fictional 2025 example. Laggala Pallegama — programme finance. Opening cash/receivable balance = 160,000 LKR; Receipts and documented additions = 48,000 LKR; Payments and documented reductions = 35,000 LKR; Other documented non-overlapping adjustments = 9,000 LKR; Independently recorded closing balance = 163,500 LKR. Results: Calculated closing balance = 164,000 LKR; Recorded minus calculated closing = -500 LKR. Interpretation: Calculated closing funds are 164,000 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -500 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Changed input. Change Opening cash/receivable balance = 160,001. Result: Calculated closing balance = 164,001 LKR; Recorded minus calculated closing = -501 LKR. Interpretation: Calculated closing funds are 164,001 LKR. The recorded closing observation is 163,500 LKR; recorded minus calculated is -501 LKR. Check the component records before explaining that difference. Next check: Reconcile closing balance. Missing input. Omit Opening cash/receivable balance. No usable result. Opening cash/receivable balance Next check: Correct or obtain the missing input records. Information still needed: Opening cash/receivable balance. Map context. No map inserted into this decision example Limits A difference does not establish misuse or an accepted financial account. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Cash receipts, payments and balance The statement calculates receipts less payments and reconciles net movement with opening and closing cash. Net cash movement is receipts less payments. Add net movement to opening cash to derive closing cash. Sector guidance · Farm Management and Marketing Farm Financial Management Confirm the accounting rules, dates, adjustments and records for the organisation. The cited form illustrates the local cash calculation. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-016DP41 | Disaster preparedness Address gaps in local warning and evacuation arrangements Inputs and examplePurpose Find missing warning, access and response-arrangement evidence. Output Case/evidence table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval. Checks For Laggala Pallegama — disaster preparedness, the default output explains Obtain the missing evidence listed below. Changing Official hazard information, Official hazard information evidence reference produces Refer the recorded evidence and unresolved conditions for the responsible review. Missing Official hazard information remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Official hazard information; Official hazard information evidence reference; warning access; warning access evidence reference; safe routes; safe routes evidence reference; vulnerable needs; vulnerable needs evidence reference; capacity; capacity evidence reference; Documented unresolved critical condition; Evidence observation date; Existing control and its evidence; Competent recipient Result: Evidence gaps (items) Worked example. Fictional 2025 example. Laggala Pallegama — disaster preparedness. Official hazard information = Missing; Official hazard information evidence reference = ; warning access = Documented; warning access evidence reference = Sample Laggala Pallegama field register / 2025; safe routes = Documented; safe routes evidence reference = Sample Laggala Pallegama field register / 2025; vulnerable needs = Documented; vulnerable needs evidence reference = Sample Laggala Pallegama field register / 2025; capacity = Documented; capacity evidence reference = Sample Laggala Pallegama field register / 2025; Documented unresolved critical condition = Unknown; Evidence observation date = 2025-06-30; Existing control and its evidence = Sample documented control; Competent recipient = Responsible specialist / duty authority. Results: Evidence gaps = 1 items. Interpretation: The required evidence is incomplete for this disaster preparedness case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Changed input. Change Official hazard information = Documented; Official hazard information evidence reference = DEMO-REVIEW-REFERENCE. Result: Evidence gaps = 0 items. Interpretation: The listed items have supporting references in this fictional record. They can be referred for the responsible review; completeness alone does not settle disaster preparedness. Next check: Refer the recorded evidence and unresolved conditions for the responsible review. Missing input. Omit Official hazard information. The required evidence is incomplete for this disaster preparedness case. The items below identify what must be obtained or reconciled. Next check: Obtain the missing evidence listed below. Information still needed: Official hazard information: Missing. Map context. No map inserted into this decision example Limits The checklist does not authorise a warning or establish a safe evacuation plan. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending Sri Lanka source matchLocal use · Validation required Check emergency readiness and assigned responsibilities Check the documented preparedness arrangements, responsible organizations and available support for the affected area. Confirm the current plan, resource readiness, access restrictions and the person responsible for follow-up. Implementation: prototype Method source: proposed SHARED rule. |
| DEC-DP41-018DP41 | Outcome evaluation Evaluate whether programmes produced sustained community benefits Inputs and examplePurpose Compare sustained livelihood observations across supplied groups and periods. Output Comparison table Next step Prepare evidence request creates an unassigned draft that is visible and downloadable, not sent. Rule (Treatment after−before) − (comparison after−before), using the same outcome definition and periods. Checks For Laggala Pallegama — outcome evaluation, the default output explains Obtain the missing evidence listed below. Changing Treatment Consistently measured livelihood outcome before produces Obtain the missing evidence listed below. Missing Treatment Consistently measured livelihood outcome before remains explicit. Retain the same inputs, result and scope in the draft and export; no authoritative record or approval changes. Treatment Consistently measured livelihood outcome before [LKR/household]; Treatment Consistently measured livelihood outcome after [LKR/household]; Comparison Consistently measured livelihood outcome before [LKR/household]; Comparison Consistently measured livelihood outcome after [LKR/household]; Study design and comparability evidence; Outcome definition, method and reference basis Result: Difference in changes (LKR/household) Worked example. Fictional 2025 example. Laggala Pallegama — outcome evaluation. Treatment Consistently measured livelihood outcome before = 420,000 LKR/household; Treatment Consistently measured livelihood outcome after = 590,000 LKR/household; Comparison Consistently measured livelihood outcome before = 390,000 LKR/household; Comparison Consistently measured livelihood outcome after = 460,000 LKR/household; Study design and comparability evidence = Missing; Outcome definition, method and reference basis = Consistently measured livelihood outcome /example matching definition1. Results: Difference in changes = 100,000 LKR/household. Interpretation: Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR/household. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Changed input. Change Treatment Consistently measured livelihood outcome before = 420,001. Result: Difference in changes = 99,999 LKR/household. Interpretation: Treatment change: 169,999; comparison change: 70,000; difference in changes: 99,999 LKR/household. This comparison alone does not establish causation or benefit. Next check: Obtain the missing evidence listed below. Missing input. Omit Treatment Consistently measured livelihood outcome before. No usable result. Treatment Consistently measured livelihood outcome before Next check: Correct or obtain the missing input records. Information still needed: Treatment Consistently measured livelihood outcome before; Study design and evidence that the treatment and comparison records are comparable. Map context. No map inserted into this decision example Limits A difference in changes does not establish a causal programme benefit. Community programme lead, participant representatives and safeguarding reviewer | Candidate; institutional release acceptance pending International method matchSri Lanka · Validation required Difference-in-differences arithmetic Difference-in-differences arithmetic Confirm the current Sri Lankan method, inputs and thresholds with the responsible institution. Implementation: prototype |
Retained method references
All 139 method IDs are retained. Version 1.6 aligns NF001 and NF002 with the fictional rice-plot example and distinguishes grouped mock inputs from future plot-identity validation. Published core methods need no repeat proof. Confirm local settings and intended use; a reference does not prove implementation.
139 method references
| Method | Formula or procedure | Sources and pending review |
|---|---|---|
| NF001 Rice plots by seed category | COUNT(DISTINCT eligible_plot_id) GROUP BY primary_rice_seed_category, period, area Inputs Operational procedure: eligible rice plot identity, one primary rice seed category, period, area and exclusion status. Mock: supplied fictional grouped plot counts. Unit plots Limits The operational procedure counts each eligible plot once. The mock uses fictional grouped counts for named rice varieties such as Bg 300, Bw 361 and At 362; it does not demonstrate underlying plot-identity deduplication. Unknown, missing or multiple categories are excluded with a declared exclusion status. Do not infer hectare coverage or population adoption from plot counts. | Validation required Project-proposed operational count and supplied grouped-count demonstration. The cited agriculture tables provide context, not direct validation of this plot-count example. Local category definitions, coverage and scientific use remain pending E01 and source custodian review. Project definition: retained catalogue NF001 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF002 Rice seed category share | 100 × eligible_plots_in_category / total_eligible_classified_plots Inputs Compatible eligible plot counts by one primary rice seed category; same period and area; explicit exclusions Unit % Limits Denominator is the sum of eligible mutually exclusive category counts. Missing, unknown or multiple-category observations are excluded and reported, never treated as zero. Zero eligible total has no defined share; show unavailable and no composition chart. | Validation required Project demonstration share. The cited agriculture tables provide context, not direct validation of this plot-count denominator. Local fitness and source rights remain pending E01 and source custodian review. Project definition: retained catalogue NF002 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF003 Paddy area under major irrigation | SUM(sown_area where irrigation_type=major) / SUM(sown_area) × 100 Inputs Sown area; irrigation type; season Unit % Limits Do not confuse major irrigation with agrarian minor tanks | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF003 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF004 Paddy area under minor irrigation | SUM(sown_area where irrigation_type=minor) / SUM(sown_area) × 100 Inputs Sown area; irrigation type; season Unit % Limits Source category definitions and incomplete records matter | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF004 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF005 Rainfed paddy cultivation share | 100 × rainfed_sown_area / all_classified_sown_area Inputs Paddy sown area; irrigation class Unit % Limits Classification must separate rainfed/major/minor as documented | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF005 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF006 Sowing-method adoption share | 100 × sown_area_using_method / eligible_sown_area Inputs Sown area by sowing method; season Unit % Limits Not equivalent to demonstrated yields or farmer adoption identities | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF006 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF009 Paddy cultivation intensity | Total seasonal planted/cultivated area across reference year / physical suitable cultivated land area Inputs Annual multiple-season cultivation areas; physical area Unit times/year Limits Denominator must be a nonduplicated physical area; double-cropping is intentional in numerator | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF009 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: YIELD |
| NF012 Crop forecast error, absolute | ABS(predicted_production - later_estimated_production) Inputs Dated forecast; matched later reference estimate Unit tonnes Limits Do not compare with another vintage/revision or different crop | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF012 Recorded context sourceRead the source note for NF-SOURCE-01. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. |
| NF014 Cultivation variable cost per hectare | SUM(variable_cost_lkr) / cultivated_area_ha Inputs Enterprise/season input costs; relevant area Unit LKR/ha Limits Cost definition and source period explicit | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF014 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COST |
| NF015 Total production cost per kilogram | SUM(eligible_production_cost) / saleable_output_kg Inputs Labour, machinery, input and other defined costs; output Unit LKR/kg Limits Total vs variable cost must be distinguished; nonzero output | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF015 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COST |
| NF016 Input cost contribution by category | 100 × cost_category / SUM(all_recorded_cost_categories) Inputs Cost records by type Unit % Limits Avoid double counting nested categories | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF016 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF020 Cultivation delay relative to calendar | Actual sowing date - published intended sowing date Inputs Crop calendar; field sow date Unit days Limits A published calendar is guidance not a mandatory deadline | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF020 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF021 Post-harvest loss percentage | 100 × recorded_lost_quantity / (saleable_quantity + lost_quantity) Inputs Harvest-batch weights; losses; disposition Unit % Limits Denominator represents same batch and measurement method | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF021 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: LOSS |
| NF022 Gross margin ratio | 100 × gross_margin / calculated_revenue Inputs Gross margin and revenue from compatible enterprise/season Unit % Limits Revenue must be positive, distinguish gross from net | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF022 Recorded context sourceRead the source note for NF-SOURCE-02. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: MARGIN |
| NF023 RUSLE annual sheet/rill soil loss | A = R × K × LS × C × P Inputs Rainfall erosivity; soil erodibility; slope length/steepness; cover; practices Unit t/ha/year Limits Empirical factors must be calibrated; does not quantify gullies or sediment delivered to a river | Institution publication - Food and Agriculture Organization of the United Nations (FAO) The FAO toolbox publishes the RUSLE factor equation and credits USDA. This is not proof of local factor calibration or a complete RUSLE2 implementation. Published method: NF-SOURCE-03 Project definition: retained catalogue NF023 Recorded context sourceFAO equation checked; units, local factors and calibration remain pending E01/E02. Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: EROSION |
| NF024 Conservation-practice soil-loss comparison | A_baseline - A_intervention; use documented RUSLE scenarios Inputs Baseline & scenario factor sets R,K,LS,C,P Unit t/ha/year difference Limits Predicted reduction only, not observed actual benefit | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF024 Recorded context sourceRead the source note for NF-SOURCE-03. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: EROSION |
| NF025 Area affected by modeled erosion class | SUM(valid_cell_area classified into reviewed erosion class) Inputs RUSLE output grid; approved class breaks Unit ha Limits Do not invent risk classes or mix grid sizes | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF025 Recorded context sourceRead the source note for NF-SOURCE-03. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: EROSION |
| NF026 Land-use class area share | 100 × area_of_class / total_valid_classified_area Inputs Land-use geometry, category, selected extent Unit % Limits Avoid overlap double count; classification scheme versions matter | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF026 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF027 Land-use conversion rate | (class_area_end - class_area_start) / years Inputs Aligned thematic layers, study interval Unit ha/year Limits End-start net is not gross conversion; keep transition matrix | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF027 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CHANGE |
| NF028 Area of prohibited/conditional overlapping use | Area(land_use_geometry ∩ valid_constraint_geometry) Inputs Permitted land-use and constraints layers Unit ha Limits Overlap supports screening, not a legal determination | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF028 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: OVERLAY |
| NF029 Available assessed site area | Total candidate area - spatially unioned excluded area Inputs Candidate polygon; approved exclusions Unit ha Limits Spatial union avoids counting overlapping exclusions twice | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF029 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF030 Existing land-use-plan geographic coverage | 100 × area_with_valid_plan / eligible_planning_area Inputs Plan geometry/version; planning boundary Unit % Limits Plan existence does not mean accepted intervention | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF030 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF031 Land-parcel slope group share | 100 × parcel_area_in_slope_class / total_valid_parcel_area Inputs Slope raster; parcel; class definition Unit % Limits DEM accuracy and slope class thresholds must be disclosed | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF031 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF032 Geographic source classification disagreement | 100 × area where two classified maps disagree / comparable valid area Inputs Aligned land cover / land use rasters Unit % Limits Difference includes classification method; not necessarily actual change | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF032 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-04 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: MISMATCH |
| NF034 SOC stock in soil layer | SOC concentration × soil bulk density × soil depth × (1 - coarse_fragment_fraction) × unit conversion Inputs Lab SOC; bulk density; sample depth; coarse fragment fraction Unit t C/ha Limits Same depth and compatible lab method; not derived from soil colour | Institution publication - Intergovernmental Panel on Climate Change (IPCC) IPCC describes this soil-stock product on printed page 2.37. Confirm units and the mass basis of coarse fragments. Published method: S79 Project definition: retained catalogue NF034 Recorded context sourceUNCCD context checked; IPCC source S79 supplies soil-stock method detail. E01/E02 approval pending. Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: SOILCARBON |
| NF035 Soil organic carbon stock change | SOC_stock_end - SOC_stock_start Inputs Comparable stock profiles with aligned depths Unit t C/ha Limits Sampling uncertainties and depth basis preserved | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF035 Recorded context sourceUNCCD context checked; IPCC source S79 supplies soil-stock method detail. E01/E02 approval pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CHANGE, SOILCARBON |
| NF037 Paddy irrigation depth requirement | IN = ETcrop + SAT + PERC + WL - Pe Inputs ETo,Kc,pre-saturation,percolation/seepage,water-layer,effective rainfall Unit mm/season Limits Estimate with crop-stage, soil and management data; do not clamp negative without review | Institution publication - Food and Agriculture Organization of the United Nations (FAO) FAO section 4.4 publishes the paddy irrigation-depth equation. All terms must refer to the same period. Published method: S78 Project definition: retained catalogue NF037 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: WATER |
| NF038 Paddy irrigation volume demand | IN_mm / 1000 × irrigated_area_m2 Inputs Reviewed net irrigation depth; actual area Unit m³ Limits Gross canal demand also needs conveyance/application losses | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF038 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: WATER |
| NF040 Reported canal delivery efficiency | 100 × delivered_volume / released_volume Inputs Measured compatible released and delivered volumes Unit % Limits Meter accuracy, storages and return flows; not national efficiency automatically | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF040 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: YIELD |
| NF041 Water delivery service completeness | 100 × successful scheduled deliveries / applicable scheduled deliveries Inputs Water allocation schedule and execution records Unit % Limits Missed schedule is not proof of illegal allocation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF041 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF043 Days since last telemetry receipt | Current time - latest received timestamp Inputs Gauge incoming messages; expected interval Unit hours Limits Freshness rule depends on source interval | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF043 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FRESH |
| NF044 Reservoir storage change per period | Stored_volume_end - stored_volume_start with matched capacity curve Inputs Reservoir dated storage estimates Unit m³ Limits Source revisions and spill context matter | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF044 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. |
| NF045 Reservoir operation discharge balance | Observed inflow - recorded outflow (same period) Inputs Inflow, releases, spills, diversions Unit m³/period Limits Not full water balance unless evaporation and all losses included | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF045 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: BALANCE |
| NF046 Recorded demand coverage share | 100 × demand with valid crop/area/period inputs / submitted total demand Inputs Demand source rows and validation states Unit % Limits Measures data readiness, not adequate water supply | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF046 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF049 Water service connection coverage | 100 × active_service_connections / eligible_connections_or_households Inputs Registered connections, denominator source Unit % Limits Connections are not people or households unless one-to-one justified | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF049 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF050 Unbilled authorized consumption share | 100 × unbilled_authorized_volume / system_input_volume Inputs System input, unbilled authorized recorded volumes Unit % Limits Separate from real/apparent loss under IWA audit | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF050 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: NRW |
| NF051 Apparent loss share | 100 × estimated_apparent_loss / system_input_volume Inputs Meter inaccuracies, unauthorized consumption, data errors Unit % Limits Needs audited water balance, not assumed residual | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF051 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: NRW |
| NF052 Real leakage loss per connection day | Current annual real loss / (number of active connections × days) Inputs Audited real loss, connections, days Unit L/connection/day Limits Unit convert m³ to L; requires validated leakage loss | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF052 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: NRW |
| NF053 Infrastructure leakage index | Current annual real losses / unavoidable annual real losses Inputs Audited leakage loss; approved unavoidable loss model Unit ratio Limits Only if pressure, connection length and approved method support denominator | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF053 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: NRW |
| NF055 Groundwater-level drawdown | Reference groundwater head - later groundwater head Inputs Same well measured depth/head tied to datum Unit m Limits Depth to water versus groundwater elevation sign convention required | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF055 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF056 Groundwater seasonal fluctuation | MAX(groundwater elevation) - MIN(groundwater elevation) Inputs Well observations within matched seasonal window Unit m Limits Need comparable sensor datum and minimum valid observations | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF056 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: TREND |
| NF057 Regulatory water-quality compliant samples | 100 × valid samples meeting applicable rules / assessed valid samples Inputs Lab results, chemical property, legal target and sample conditions Unit % Limits Not universal water quality index; parameters and intended use matter | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF057 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUALITY |
| NF058 Water-quality monitoring coverage | 100 × locations with required valid testing / designated monitored locations Inputs Monitoring plan and valid laboratory samples Unit % Limits Availability is not water quality | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF058 Recorded context sourceRead the source note for NF-SOURCE-06. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF059 Forest proportion of assessed land | 100 × forest_area_ha / compatible_land_area_ha Inputs Forest-cover class, land area, boundary edition Unit % Limits Forest and tree-cover definitions must not be mixed | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF059 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF060 Mean forest tree density | Count of sampled live trees / plot_sampled_area_ha Inputs Forest inventory plots, tree counts, sampled plot area Unit trees/ha Limits Declared diameter inclusion limits and survey design | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF060 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CARBON |
| NF061 Forest basal area per hectare | SUM(π × DBH_m² / 4) / sampled_area_ha Inputs Tree DBH for included inventory trees Unit m²/ha Limits DBH units and species inclusion rules; plot expansion | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF061 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CARBON |
| NF063 Forest biomass density | SUM(model-estimated biomass) / relevant forest area Inputs Accepted allometric biomass, species, tree size Unit t dry matter/ha Limits Mandatory approved species-specific model and uncertainty | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF063 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CARBON |
| NF065 Carbon dioxide equivalent of changed carbon stock | CO2 equivalent = carbon-stock change × 44/12 Inputs Measured/modelled carbon change, defined pools Unit t CO2e Limits Pool accounting, uncertainty, emissions/removals separated | Validation required The linked forest context does not establish this complete conversion rule. IPCC section 2.2.3 distinguishes the 44/12 molecular ratio from the negative sign used for emissions; the sign and reporting purpose require validation. Project definition: retained catalogue NF065 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CARBON |
| NF066 Forest edge length per area | Length of forest/nonforest boundaries / forest area Inputs Classified forest polygons and shared edge rule Unit m/ha Limits Sensitive to map resolution and classification noise | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF066 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF068 Forest cover gross losses by transition | Area of forest-to-nonforest pixels over comparable classification period Inputs Aligned forest classes at start/end Unit ha Limits Not every loss is irreversible deforestation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF068 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CHANGE |
| NF069 Restoration planting density | Number planted / mapped eligible planting area Inputs Planted tree records, planting site area Unit trees/ha Limits Planting density is not survival or verified restoration | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF069 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF070 Restoration observed survival by cohort | 100 × surviving verified trees / planting cohort count Inputs Seedling cohort, revisit observations Unit % Limits Survival must match cohort and period, not unrelated trees | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF070 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: SURVIVAL |
| NF071 Forest change alert review completion | 100 × reviewed detection alerts / eligible received alerts Inputs Remote-sensing alerts and review records Unit % Limits Alert is not a confirmed incident | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF071 Recorded context sourceRead the source note for NF-SOURCE-07. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: INSPECT |
| NF072 Observed species richness | COUNT(DISTINCT taxon_id) within comparable verified survey samples Inputs Survey-event species identifications and protocols Unit species Limits Observed richness, not total species richness or population | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF072 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: BIODIVERSITY |
| NF076 Survey protocol coverage | 100 × surveyed target cells / eligible planned survey cells Inputs Survey sampling grid and completed events Unit % Limits Sampling frame and valid effort required | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF076 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF077 Shannon diversity index (survey-based) | H = -SUM(p_i × LN(p_i)) across recorded species sample proportions Inputs Comparable abundance observations by taxon Unit dimensionless Limits Requires abundance sampling, not presence-only opportunistic sightings | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF077 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: BIODIVERSITY |
| NF079 Threatened taxon observation summary | COUNT(DISTINCT verified_taxa with source-category CR/EN/VU) Inputs Species observations linked to current licensed IUCN categories Unit taxa observed Limits Not a formal threat index and coverage may be incomplete | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF079 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: BIODIVERSITY |
| NF080 Conservation habitat survey response time | Observed incident report time to documented first follow-up Inputs Human-wildlife incident and response cases Unit hours/days Limits Requires accurate timestamps; does not measure mitigation success | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF080 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF081 Protected habitat intersection share | Area(habitat ∩ protected_boundary) / area(habitat) × 100 Inputs Habitat spatial polygons, protected-area boundary editions Unit % Limits Geometries, data rights, sensitive locations | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF081 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: OVERLAY |
| NF082 Biodiversity threat exposure STAR | Apply licensed IUCN STAR tool methodology to input threatened taxon habitat and threat data Inputs IUCN distribution, species risk/threat layers, land use Unit STAR units per IUCN method Limits Not generic Shannon index; official model and expert approval required | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF082 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: STAR |
| NF083 Habitat condition change | End validated condition indicator - baseline condition indicator Inputs Comparable indicator values, scale and surveys Unit indicator units Limits Method approved, condition not a one-size-fits-all score | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF083 Recorded context sourceRead the source note for NF-SOURCE-08. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CHANGE |
| NF085 Rainfall anomaly difference | Observed_period_rainfall - matching_climate_normal Inputs Observed accumulated rain, baseline normal Unit mm Limits Baseline normals and missing data completeness stated | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF085 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: ANOMALY |
| NF086 Rainfall coefficient of variation | 100 × sample_sd(annual_total_rainfall) / mean(annual_total_rainfall) Inputs Complete annual rainfall totals over stated years Unit % Limits Mean positive; sufficiently many complete years | Government publication - United States National Institute of Standards and Technology (NIST) NIST defines sample CV. This reference expresses the ratio as a percentage; rainfall data and aggregation require approval. Published method: S84 Project definition: retained catalogue NF086 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: ANOMALY |
| NF088 Maximum consecutive dry days | MAX(run length of daily precipitation below approved dry-day cutoff) Inputs Complete daily precipitation series Unit days Limits Gap breaks run unless imputed under reviewed method | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF088 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: SPELL |
| NF089 Maximum consecutive wet days | MAX(run length of days meeting approved rain cutoff) Inputs Daily station rainfall and wet-day definition Unit days Limits Document threshold and observation completeness | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF089 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: SPELL |
| NF093 Meteorological observation timeliness | 100 × valid observations received by expected deadline / expected observations Inputs Station schedule and received timestamps Unit % Limits Does not prove measurement accuracy | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF093 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FRESH |
| NF094 Station/source period coverage | 100 × periods with quality-accepted data / expected periods Inputs Expected schedule and valid observation inventory Unit % Limits Coverage should accompany plotted anomalies | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF094 Recorded context sourceRead the source note for NF-SOURCE-09. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FRESH |
| NF095 SPI using fitted probability distribution | Follow WMO recommended precipitation aggregation, fitted distribution and standard normal transform Inputs Long rainfall time series, selected SPI timescale Unit SPI z-score Limits Not simple anomaly / SD; minimum time-series and QA requirements | Institution publication - World Meteorological Organization (WMO) WMO section 6 describes fitting and normal transformation. This retained method is not implemented by the SPI input-only screen. Published method: S82 Project definition: retained catalogue NF095 Recorded context sourceNormals page checked; use WMO SPI guide S82 for the specialist method. E01 approval pending. Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: SPI |
| NF097 Disaster affected family share | 100 × affected_households / total_households_at_same_area Inputs Official affected families; relevant household denominator Unit % Limits Count families only once within incident; not total people | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF097 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF099 Disaster direct loss to GDP | 100 × verified_direct_economic_loss / relevant_GDP Inputs PDNA damages and matched GDP Unit % Limits Separate damage vs output loss, price year and coverage | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF099 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF100 Sectoral damage composition | 100 × approved_sector_damage / all_included_sector_damage Inputs PDNA amounts by category/currency Unit % Limits Avoid overlap between public/private and sectors | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF100 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF101 Disaster recovery funding gap | Estimated approved recovery need - committed eligible financing Inputs PDNA recovery plan needs, confirmed commitments Unit LKR Limits Needs not identical to monetary damage; avoid double counting | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF101 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FUNDING |
| NF102 Safe-center occupancy | Present displaced persons / documented safe-center capacity × 100 Inputs Shelter occupants, certified facility capacity Unit % Limits Capacity requires approved site records; exceeding 100 possible as overload | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF102 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CAPACITY |
| NF104 Hazard overlap of candidate sites | Area(candidate_site ∩ valid_hazard_class) by class Inputs Published NBRO/DMC zonation; project polygons Unit ha Limits Spatial intersection not an operational permit/recommendation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF104 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: OVERLAY |
| NF105 Disaster observation update lag | Latest verified situation time - actual field observation time Inputs Field report source time and publication timestamp Unit hours Limits Lag can be source reporting not current incident | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF105 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FRESH |
| NF106 Landslide model suitability/readiness | Documented zonation geometry and edition; no replacement formula Inputs NBRO hazard layer, scale, valid plan use Unit category/coverage Limits NBRO hazard model cannot be approximated by invented slope score | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF106 Recorded context sourceRead the source note for NF-SOURCE-10. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: RISK |
| NF107 Ambient parameter compliance share | 100 × accepted test observations meeting applicable target / all accepted tests assessed Inputs Sample value, unit, purpose-specific target and period Unit % Limits National threshold and test methods must be verified | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF107 Recorded context sourceParameter compliance is not the full water-body indicator SDG 6.3.2. Confirm the intended measure under E01. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUALITY |
| NF108 Monitoring sites with complete parameter groups | 100 × sites with all required current parameters / required monitored sites Inputs Network sites; valid oxygen/salinity/nutrients/acidity groups Unit % Limits Completion does not imply meeting quality criteria | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF108 Recorded context sourceRead the source note for NF-SOURCE-11. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF109 Median pollutant concentration | MEDIAN(valid lab results at compatible points/periods) Inputs Quality-tested environmental concentrations Unit mg/L Limits Lab detection limits/censored values need method | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF109 Recorded context sourceRead the source note for NF-SOURCE-11. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUALITY |
| NF110 Environment mitigation completion | 100 × independently closed mitigation actions / actions due Inputs Assessment conditions, actions, review records Unit % Limits Action closure not equal pollutant reduction | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF110 Recorded context sourceRead the source note for NF-SOURCE-11. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: INSPECT |
| NF111 Environmental monitoring spatial coverage | 100 × designated zones with sampled sites / planned zones Inputs Sites and monitoring plan polygons Unit % Limits Sparse points do not establish whole-zone water quality | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF111 Recorded context sourceRead the source note for NF-SOURCE-11. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF112 Environmental exceedance duration | SUM(duration of verified exceedance episodes under approved threshold rule) Inputs Time-series, quality control, threshold + hysteresis Unit hours Limits Sampling frequency and gaps require supported interpolation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF112 Recorded context sourceRead the source note for NF-SOURCE-11. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUALITY |
| NF113 Price range width | Market quoted maximum - market quoted minimum Inputs Same date/place/grade min/max price Unit LKR/kg Limits Quotation range not mean/actual sale | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF113 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: DISTRIBUTION |
| NF114 Commodity price median by market | MEDIAN(quality-valid matching price quotations) Inputs Dated comparable unit/grade price quotes Unit LKR/kg Limits Quotations not independently recorded transactions | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF114 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: DISTRIBUTION, PRICE |
| NF115 Commodity weekly price volatility | 100 × sample_std(weekly_price_series) / mean(weekly_price_series) Inputs Matched weekly quoted prices across defined window Unit % Limits Needs >=2 valid periods and positive mean; not return volatility | Government publication - United States National Institute of Standards and Technology (NIST) NIST defines sample CV. This reference expresses the ratio as a percentage; the selected weekly price series requires validation. HARTI is a price-data source, not the source of this statistic. Published method: S84 Project definition: retained catalogue NF115 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Published core needs no repeat proof. Confirm local inputs, units and settings under E01; E02/E03 where relevant. See Section 6. Candidate family: VOLATILITY |
| NF116 Farm-gate to retail spread | Retail_quoted_price - farmgate_quoted_price at compatible grades/periods Inputs Farmgate and retail prices with matching product/grade Unit LKR/kg Limits Transport, margins and losses not implied by spread alone | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF116 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: PRICE |
| NF117 Postharvest batch retention | 100 × usable_output_kg / raw_input_kg Inputs Input mass, usable output, documented process Unit % Limits Moisture/processing losses may be intended; define basis | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF117 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: LOSS |
| NF118 Processor capacity utilization | 100 × actual_processed_quantity / theoretical_available_capacity Inputs Equipment capacity, operating period, output records Unit % Limits Theoretical capacity conditioned on uptime and shifts | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF118 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CAPACITY |
| NF119 Transport cost per tonne-kilometre | Transport_total_cost / (shipment_tonnes × route_km) Inputs Shipment quantity, verified route and cost Unit LKR/t-km Limits Need valid route distance and mode; no straight line substitution | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF119 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COST |
| NF120 Cold-chain temperature excursions | COUNT(valid interval episodes exceeding product-approved range) Inputs Logger temperature, goods specification, logger quality Unit events Limits Sampling interval, trigger hysteresis and allowed limit | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF120 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUALITY |
| NF121 Verified sell-through rate | 100 × actual_sold_quantity / available_marketable_quantity Inputs Confirmed sales and inventory/production availability Unit % Limits Buyer interest, enquiries not sales | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF121 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF122 Export unit value | Customs-reported export value / matched export quantity Inputs Customs value, volume, currency, product, country Unit USD/tonne Limits Changes in quality/product mix distort interpretation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF122 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: YIELD |
| NF123 Export market concentration HHI | SUM((market_export_share)^2) for complete destination breakdown Inputs Product export value by destination, same year Unit HHI share squared Limits Subscription source coverage and missing markets matter | Validation required The HARTI price bulletin does not establish an export-concentration method. Government HHI guidance uses a different market and scale; this application requires validation. Project definition: retained catalogue NF123 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CONCENTRATION |
| NF124 Export destination share | 100 × value_to_destination / total_product_exports Inputs Export data with same product code and year Unit % Limits Official trade data may require subscription | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF124 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COMPOSITION |
| NF125 Export growth contribution | (current_value - prior_value) / (current_total_export_value - prior_total) × 100 Inputs Product-group export values in consistent currency Unit % Limits When total delta zero, no contribution percentage; can be negative | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF125 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF126 Price seasonality index | 100 × mean(price for calendar month over complete years) / grand_mean_price Inputs Consistent historic commodity monthly quotes Unit index, base 100 Limits Missing periods/market mix and inflation context | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF126 Recorded context sourceOfficial alternative checked. Read NF-SOURCE-12 for its scope; method and local application approval remain pending. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: VOLATILITY |
| NF127 Registered state-land permit backlog | COUNT(valid permit applications with open state beyond agreed review date) Inputs Application reference, submitted date, workflow state Unit applications Limits Overdue definition depends on official workflow, not invented SLA | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF127 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUEUE |
| NF128 Permit expiry exposure | COUNT(active recorded permits with end date within selected horizon) Inputs Permit register, documented expiry date Unit permits Limits A warning is not a legal determination of permit validity | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF128 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF129 State land record coverage | 100 × indexed parcels with valid reference / eligible source parcel list Inputs State land parcel records, digitization inventory Unit % Limits Not legal ownership completeness | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF129 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF130 Enterprise programme uptake | 100 × verified participating enterprises / invited eligible enterprises Inputs Programme participant and eligibility records Unit % Limits Enrollment alone does not prove success | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF130 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FLOW |
| NF131 Training to support transition | 100 × trainees completing defined follow-up / enrolled trainees Inputs Training and follow-up support records Unit % Limits Participant identity and training session distinction | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF131 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FLOW |
| NF132 Industrial estate occupied plot share | 100 × leased/occupied developed plots / plots available at start Inputs Industrial estate inventory, dated lease and status Unit % Limits Allocation/lease not proof of operational industry | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF132 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: CAPACITY |
| NF133 Enterprise support response time | Mean(closure_date - request_date) for valid completed service records Inputs Service requests and completion dates Unit days Limits Cases still open are separately reported, not discarded | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF133 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUEUE |
| NF134 Industrial facility infrastructure readiness | Count compliant required infrastructure elements / total required elements (approved checklist) Inputs Site infrastructure assessments and checklist Unit % Limits Locally approved readiness checklist; not automatic investment approval | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF134 Recorded context sourceOriginal linked source retained as context; exact formula and local suitability not certified Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: INSPECT |
| NF135 Population poverty headcount share | 100 × weighted_persons_below_official_poverty_line / valid_survey_population Inputs HIES consumption/income, line, sample weights Unit % Limits Official sample design; avoid GN-level inference from district estimate | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF135 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: DISTRIBUTION |
| NF136 Mean household expenditure per person | Survey-weighted household expenditure per capita Inputs HIES household expenditure, size and sample weights Unit LKR/person/month Limits Use official deflation/reference prices for comparisons | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF136 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: DISTRIBUTION |
| NF138 Community outreach coverage | 100 × distinct verified reached target persons / eligible target population Inputs Outreach event attendance and authorized frame Unit % Limits Cannot use census persons as count of project beneficiaries | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF138 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF139 Service request first response time | Time of first actual official response - submission received time Inputs Case records and timestamps Unit hours/days Limits Acknowledgement may be different from substantive response | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF139 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUEUE |
| NF140 Resolved feedback ratio | 100 × independently closed feedback cases / valid cases received in same cohort Inputs Feedback case registers, dispositions, cohorts Unit % Limits Public anonymous intake requires approved policy | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF140 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF141 Training completion share | 100 × unique completers / unique eligible enrolled participants Inputs Training session and participant records Unit % Limits Completion definition and duplicate IDs reviewed | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF141 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FLOW |
| NF142 Programme support intensity | Total verified delivered support quantity / distinct verified recipients Inputs Support episodes, quantities and participant IDs Unit unit/person Limits Do not merge heterogeneous support units | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF142 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: No equivalence asserted |
| NF143 Repeated-support overlap share | 100 × distinct recipients in >1 support programme / distinct recipients across programmes Inputs Reviewed privacy-permitted beneficiary cross-programme links Unit % Limits Restricted identifiers; overlap is not ineligible or fraud | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF143 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: REPEAT |
| NF144 Community grievance ageing | Age as-of date of unresolved complaint or case Inputs Protected grievance/feedback case and status Unit days Limits Only activate formal grievance workflow if approved | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF144 Recorded context sourceRead the source note for NF-SOURCE-13. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUEUE |
| NF145 Project internal rate of return | Solve NPV(r) = 0 for well-defined dated net cashflow sequence Inputs Initial investment, annual costs/benefits, residual value Unit %/period Limits Multiple/no roots possible, monetary vs economic basis separate | Validation required The linked appraisal illustrates periodic IRR. The reference specifies dated cash flows; timing conventions and the applicable solver require validation. Project definition: retained catalogue NF145 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FINANCE |
| NF147 Discounted payback year | First period where cumulative discounted net cash flow becomes non-negative Inputs Approved cashflow schedule, discount rate Unit years Limits No payback if never recovers; fractional interpolation declared | Validation required The reference requires discounted payback. The linked appraisal and prototype helper use simple or undiscounted payback; they do not validate this method. Project definition: retained catalogue NF147 Recorded context sourceOriginal source describes simple payback, not discounted payback. Select and approve a separate discounted method under E01. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FINANCE |
| NF148 Debt service coverage ratio | Cash available for debt service / scheduled principal+interest due Inputs Cashflows, debt repayment schedule Unit ratio Limits Requires finance-institution definition; not automatic loan approval | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF148 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: DEBT |
| NF149 Co-financing commitment ratio | 100 × documented eligible co-finance commitments / approved co-finance target Inputs Signed funding commitments and target Unit % Limits Commitment is not disbursement | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF149 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FUNDING |
| NF151 Unfunded intervention amount | Approved planned intervention amount - confirmed eligible committed finance Inputs Reviewed intervention budget, grant commitments Unit LKR Limits Do not count planned or interested finance as commitment | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF151 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FUNDING |
| NF152 PES verification completion | 100 × agreements with verified required services / agreements due for verification Inputs PES agreements, evidence and verifier records Unit % Limits Compliance depends on scheme rules and independence | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF152 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: PES |
| NF153 PES quantified physical service flow | SUM(accepted service_units) for comparable service/method and period Inputs Approved ecosystem service physical flow observations Unit service-specific units Limits Different service types cannot be summed in one total | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF153 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: PES |
| NF154 Ecosystem service monetary flow | SUM(verified quantities × reviewed service-unit valuation) with permitted approach Inputs Service flows, approved accounting/valuation model Unit LKR/year Limits Monetary account is not a cash payment or PES entitlement | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF154 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: ACCOUNT |
| NF155 Outcome verification cost per unit | Total project monitoring/verification cost / accepted verified service units Inputs Eligible monitoring expenditure and verified service flow Unit LKR/service unit Limits Service category and period must agree | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF155 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. |
| NF156 PES agreement renewal exposure | COUNT(effective agreements ending during selected horizon) Inputs PES agreement valid-to date and status Unit agreements Limits Status may require official legal source confirmation | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF156 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: PES |
| NF157 Benefit-cost sensitivity range | Recompute BCR/NPV on separate documented discount/cost/benefit assumptions Inputs Approved appraisal, alternative parameter sets Unit LKR; ratio Limits Not an automatic preference ranking; retain scenario lineage | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF157 Recorded context sourceRead the source note for NF-SOURCE-14. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FINANCE |
| NF158 Milestone evidence acceptance share | 100 × verified-complete milestones / due milestones Inputs Milestone due dates, reviewed evidence and states Unit % Limits Submitted evidence is not completion | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF158 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FLOW |
| NF159 Intervention implementation rate | 100 × interventions reaching accepted implementation stage / approved planned interventions Inputs Portfolio intervention states and planned cohort Unit % Limits Stages reflect plan, field work, review separately | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF159 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: VARIANCE |
| NF160 Financial utilization against approved budget | 100 × posted eligible actual expenditure / latest approved budget Inputs Budget editions, eligible posted expenses Unit % Limits Commitments and disbursements distinguished | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF160 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. |
| NF164 Review backlog aged beyond target | COUNT(open review cases exceeding their assigned due date) Inputs Review queue, due dates and current statuses Unit cases Limits No universal SLA unless approved | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF164 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: QUEUE |
| NF165 Outcome indicator data coverage | 100 × required reporting units with valid observed results / applicable reporting units Inputs Indicator plan, report periods, valid observations Unit % Limits Targets do not count as observations | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF165 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF166 Source evidence acceptance ratio | 100 × accepted submissions / received submissions of cohort Inputs Submission versions and review states Unit % Limits Returned duplicates version counted by submitted unit | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF166 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FLOW |
| NF169 Portfolio intervention area coverage | Unique unioned mapped intervention hectares / defined eligible project landscape hectares × 100 Inputs Geometries linked to approved interventions, landscape Unit % Limits Spatial union avoids overlap double counting; area is not beneficiary count | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF169 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: COVERAGE |
| NF170 Review independence compliance | 100 × protected decisions with distinct authorized reviewer / protected decisions requiring independence Inputs Decision/audit actors and review policy Unit % Limits Privacy and role-scope rules; not a substitute for approvals | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF170 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: INSPECT |
| NF171 Target achievement ratio | 100 × compatible observed_result / applicable target Inputs Approved indicator target and verified actuals Unit % Limits If target zero or direction inverted, specify alternate method | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF171 Recorded context sourceRead the source note for NF-SOURCE-15. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: VARIANCE |
| NF173 Schema validation pass rate | 100 × records passing all required schema checks / received records Inputs Submission validation receipts, schema versions Unit % Limits Technical validity not scientific accuracy | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF173 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: METADATA |
| NF174 Data timeliness share | 100 × expected reporting periods received within source-specific deadline / due periods Inputs Source update agreement and timestamps Unit % Limits No universal freshness target; out-of-order intake allowed | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF174 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: FRESH |
| NF176 Record provenance completeness | 100 × observations with mandatory source/version/field/location-time support / eligible observations Inputs Lineage audit contract, record metadata Unit % Limits Location may be explicitly unknown per contract | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF176 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: METADATA |
| NF177 Geospatial object matching review rate | 100 × reviewed candidate identity matches / generated eligible candidates Inputs Match suggestions and reviewer decisions Unit % Limits Similarity does not establish canonical identity | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF177 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: MISMATCH |
| NF178 GIS layer actual data availability | 100 × published catalogue entries with valid retrievable layers / eligible required layers Inputs Catalogue service status, layer count Unit % Limits WMS service available does not guarantee bulk features | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF178 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: METADATA |
| NF179 Expired data source access share | 100 × active saved analytic products with invalid source rights / products due for recheck Inputs Source grants, saved reports, current permissions Unit % Limits A private report should remain inaccessible, not leak metadata | Validation required The linked publication supplies context, observations or related guidance; direct support for this exact formula or procedure is not established. Project definition: retained catalogue NF179 Recorded context sourceRead the source note for NF-SOURCE-16. This link check does not approve the method. Local definitions and method changes: E01; E02/E03 where relevant. Developer checks arithmetic and input handling. See Section 6. Candidate family: ACCESS |
All sources
Official data mapping and draft domain references
The source register contains 172 entries, including the official data mappings and draft domain references. Each keeps its citation and access limits. Government publication and Institution publication identify support for a stated core method. Project adaptations and incomplete support remain Validation required. Availability is not permission, scientific endorsement or acceptance.
The preferred LUPPD planning report and HARTI publication alternatives remain linked with their limits. The original local planning manual was not recovered. Access-unverified sources need an official copy or approved retry under the existing C04/E01 decisions.
Download the complete source register
S01 LUPPD Performance Report 2022: official planning context
Official departmental report hosted by Parliament; planning context
Section 1.3, PDF page 4: divisional, village and micro-watershed planning; stakeholder coordination
Official alternative checked
This official LUPPD report is a readable alternative for institutional planning context. It is not the missing divisional planning manual. The original manual was not recovered; confirm the applicable local procedure and source edition with LUPPD under C04/E02.
Open sourceS02 NRMC functions
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS03 Department of Agriculture publications and regulations
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS04 Agrarian Development services
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS05 Irrigation Department public information
Context or data source; not automatic formula support
Public homepage navigation: reservoir status, hydrology, geo-informatics and branch information
Content checked
The official page is available. It identifies public information routes; it does not establish a data licence, live API or calculation method.
Open sourceS06 Irrigation Department overview and functions
Context or data source; not automatic formula support
Overview: Objectives and Functions
Replacement checked
The old ministry URL has a certificate hostname problem. The department's own overview confirms water-resource planning, operation, maintenance and flood-protection functions. This replacement is institutional context.
Open sourceS07 Mahaweli Water Management Secretariat
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS08 Mahaweli land-use planning
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS09 Forest Conservation functions
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS10 Department of Meteorology products
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS11 Agro-climatology and climate change division
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS12 Export Agriculture research division
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS13 GCF FP124 project and documents
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS14 CIFOR-ICRAF dashboards
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS15 Survey Department responsibilities
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS16 Sri Lanka NSDI reference standards
Context requiring custodian confirmation
Reference standards page contains text about another jurisdiction; no local mandate inferred
Retrieved text for review
Open sourceS17 Sri Lanka NSDI publication and access FAQ
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS18 Disaster Management Centre profile
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS19 Landslide clearance assessment
Context or data source; not automatic formula support
Issuing Landslide Clearance for Building Constructions / Land Developments / Projects: objectives and site assessment
Content checked
The official text describes geological, geotechnical and hydrological site assessment. It is clearance context, not a numerical hazard score. Current applicability and authority remain for the competent institution to confirm.
Open sourceS20 Environmental Protection License scheme
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS21 Natural resources management and monitoring
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS22 Wildlife research permissions
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS23 Wilpattu management plan 2019–2024
Context or data source; not automatic formula support
Wilpattu National Park Management Plan 2019-2024: approval page and executive summary
Replacement checked
The DWC URL returns 404. The same titled plan is available from the collaborating GIZ SNRD archive. It is historical Wilpattu context, not a current Knuckles management plan.
Open sourceS24 Census and Statistics survey catalogue
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS25 Water Resources Board hydrogeology
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS26 Water Resources Board services
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS27 Water supply and sanitation project completion report
Context or data source; not automatic formula support
World Bank ICR00005929: contents, results framework and efficiency analysis
Content checked
The Water Supply and Sanitation Improvement Project report is available. It supports project and service-performance context. Its project-specific values are not SHARED parameters.
Open sourceS28 Geological Survey and Mines Bureau licensing information
Context or data source; not automatic formula support
Licensing: licence categories and application information
Replacement checked
The old /services path returns 404. The official licensing page is available. It supplies regulatory context; permit decisions and current conditions require the Bureau's confirmation.
Open sourceS29 State land administration services
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS30 State Land Information Management System
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS31 HARTI weekly commodity bulletins
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS32 HARTI annual report 2024
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS33 EDB export marketing services
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS34 EDB trade information
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS35 National Enterprise Development Authority
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS36 IDB technical services
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS37 IDB industrial estates
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS38 Home Affairs historical performance report: administration context
Context or data source; not automatic formula support
Historical report: PDF pages 5-6; district, divisional and Grama Niladhari administration sections listed in contents
Content checked
The report is available through verified HTTPS. It concerns historical administration and progress. Do not use its counts or arrangements as the current programme geography or current mandate.
Open sourceS39 Public Administration Circular 23/2021
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS40 Tea Research Institute agronomy
Context or data source; not automatic formula support
Agronomy division: research and development activities and key research areas
Content checked
The official page supports tea agronomy, productivity, labour and soil and water context. It does not prescribe the prototype's numerical rules.
Open sourceS41 TRI climate adaptation guideline 2019
Context or data source; not automatic formula support
TRI Guideline 01/2019, pages 1-2: impacts and adaptation strategies
Content checked
The two-page guideline is available. It gives tea climate-adaptation practices. Local option selection, effectiveness and measurement protocols still need expert approval.
Open sourceS42 Plantation Human Development Trust
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS43 CBSL sustainable finance
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS44 Sri Lanka Green Finance Taxonomy
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS45 GBIF guide for publishing biological survey and monitoring data
Context or data source; not automatic formula support
Guide v1.0.2: sections 5.4, 5.5 and 5.7 on time, protocol and sampling effort
Replacement checked
The original introduction was access-blocked. The official guide is readable and provides stronger sampling-event documentation. It does not establish a Shannon or STAR calculation.
Open sourceS46 GBIF biological survey publishing guide
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS47 IFRC community engagement and accountability
Context or data source; not automatic formula support
Community Engagement and Accountability: participation and trusted feedback mechanisms
Content checked
The official page supports participation and feedback principles. SHARED response deadlines, escalation and safeguarding rules remain client decisions.
Open sourceS48 USDA RUSLE2 overview
Context or data source; not automatic formula support
Water Erosion RUSLE2: overview and official program and database
Content checked
The page describes a rainfall and runoff erosion model. A simple product of factors is not the full RUSLE2 program. Local factors and valid uses need expert approval.
Open sourceS49 IPCC 2019 Refinement
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS50 FAO crop evapotranspiration 56
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS51 Cost of production budgeting
Context requiring follow up
Generic landing page; the intended budgeting guide is not established
Retrieved text for review
Open sourceS52 WMO SPI user guide record
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS53 UDA published zoning map
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS54 Seed Certification Service
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS55 Sri Lanka Agriculture Enterprise Architecture 1.3
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS56 WHO water safety planning
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS57 FAO food loss measurement
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS58 UN SEEA Ecosystem Accounting
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS59 OECD evaluation criteria
Context or data source; not automatic formula support
Understanding the six criteria: definitions and elements for analysis
Content checked
The OECD chapter is available and supplies evaluation criteria. It does not prescribe one SHARED score, weighting scheme or causal estimator.
Open sourceS60 FAO PES and food security
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS61 FAO designing PES
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS62 NRMC Soil Conservation Division
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS63 NRMC Land Use Planning and Geo-Informatics
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS64 Irrigation Department Dam Safety Branch
Context or data source; not automatic formula support
Dam Safety: Main Functions and Services
Content checked
The branch page confirms inspection, monitoring and coordination responsibilities. It does not supply a universal dam-safety risk score or operating threshold.
Open sourceS65 Irrigation Department Water Management Branch
Context or data source; not automatic formula support
Water Management: Objectives and Functions
Content checked
The branch page confirms coordination and irrigation water-management functions. Crop-water calculations use the separate FAO method sources and approved local inputs.
Open sourceS66 NSDI profile of Land Use Policy Planning Department
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS67 DCS Statistical Abstract 2024: agriculture methodology
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS68 FAO 56: Penman-Monteith reference evapotranspiration
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS69 FAO 56: crop evapotranspiration
Published method
FAO 56 Chapter 5 equation 56; ETc = Kc × ETo
Retrieved text for review
Open sourceS70 IPCC 2019 Refinement: AFOLU volume
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS71 IUCN Species Threat Abatement and Restoration metric
Published specialist method overview
Scientific underpinning and approach; full STAR calculation is not implemented
Retrieved text for review
Open sourceS72 IWA non-revenue water management
Published definition
Opening NRW definition; detailed water audit protocol not supplied
Retrieved text for review
Open sourceS73 CBSL Sri Lanka Green Finance Taxonomy 2022
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceS74 World Bank Impact Evaluation in Practice: difference-in-differences
Context or data source; not automatic formula support
Impact Evaluation in Practice, second edition, Chapter 7; printed pages 129-141, especially 132-135
Content checked
The chapter describes difference-in-differences and its comparison-trend assumptions. It does not validate a local causal claim from a simple before-and-after change.
Open sourceS75 Environment Canada: root mean squared error
Published method
What is Root Mean Square Error; displayed formula
Retrieved text for review
Open sourceS76 FAO enterprise and activity budgeting
Published method
Section 4.3.8 Gross margin; section 4.7 Parametric budgeting
Retrieved text for review
Open sourceS77 DCS paddy statistics and revision notice
Context or data source; not automatic formula support
Full method locator not established
Retrieved text for review
Open sourceLOCAL-SRS01 SRS Chapter 01: Introduction
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS02 SRS Chapter 02: Understanding SHARED and How It Works
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS03 SRS Chapter 03: Stakeholders and Responsibilities
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS04 SRS Chapter 04: Overall System Architecture
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS05 SRS Chapter 05: How SHARED Organizes Information
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS06 SRS Chapter 06: Collecting and Importing Data
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS07 SRS Chapter 07: Checking and Approving Data
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS08 SRS Chapter 08: Data Storage and Record History
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS09 SRS Chapter 09: Finding Information and Preparing Reports
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS10 SRS Chapter 10: Maps and Geographic Analysis
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS11 SRS Chapter 11: Dashboards and Information Visualization
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS12 SRS Chapter 12: Decision Support
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS13 SRS Chapter 13: Project Implementation and PMU Monitoring
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS14 SRS Chapter 14: Beneficiary and Community Services
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS15 SRS Chapter 15: Markets Value Chains and Ecosystem Services
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS16 SRS Chapter 16: User Interfaces and Mobile Applications
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS17 SRS Chapter 17: APIs and External System Connections
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS18 SRS Chapter 18: Non Functional Requirements
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS19 SRS Chapter 19: System Testing and Acceptance
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS20 SRS Chapter 20: Development Deployment and Handover
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-SRS21 SRS Chapter 21: Pending Requirements and Institutional Decisions
Project proposal and context
Original project chapter or catalogue named in the title
Existing local SRS extract
Local project context record; no public URL is expected.
LOCAL-CATALOGUE Existing 41-profile, 164-question catalogue
Project proposal and context
Original project chapter or catalogue named in the title
Local catalogue inspected
Local project context record; no public URL is expected.
LOCAL-INTAKE Existing prototype data-entry and upload schemas
Project proposal and context
Original project chapter or catalogue named in the title
Local catalogue inspected
Local project context record; no public URL is expected.
PROTO SHARED prototype calculation and workflow implementation
Project implementation
DecisionSupportModel.spec/project and named model functions in each entry
Read only prototype inspection
Open sourceSRS SHARED Software Requirements Specification
Project requirement
Sections 5.4, 10, 12 and named requirement IDs in each rule
Version 1.6 author revision; institutional acceptance pending
Open sourceS78 FAO Irrigation Water Management Training Manual 3
Published method
Chapter 4.4 Irrigation water need of rice; steps 1 to 8
Method text checked
Open sourceS79 IPCC 2006 Guidelines Volume 4 Chapter 2
Published method
Sections 2.2.3, 2.3.1 and 2.3.3; soil stock guidance printed page 2.37
Method text checked
Open sourceS80 USDA Forest Service A guide for predicting sheet and rill erosion on forest land
Historical published method
Universal Soil Loss Equation and Applying the USLE; printed page 2
Historical method text checked; current local calibration not established
Open sourceS81 FAO Guidelines for financial economic environmental and social information
Published method
Net Present Value and Internal Rate of Return subsections
Method text checked
Open sourceS82 WMO Standardized Precipitation Index User Guide
Published method
WMO No 1090; SPI calculation and interpretation guidance
Full guide checked; local fit and baseline pending
Open sourceS83 US Department of Justice Herfindahl Hirschman Index
Published definition
Definition of the sum of squared market shares
Definition checked; US legal thresholds do not apply to this project
Open sourceS84 NIST Coefficient of Variation
Published definition
Description of sample CV and ratio scale restriction
Definition checked
Open sourceS86 Turf distance API
Software method
Version 7.2.0 distance; Haversine method
Documentation checked
Open sourceS87 Turf length API
Software method
Version 7.2.0 length; selected units
Documentation checked
Open sourceS88 Turf buffer API
Software method
Version 7.2.0 buffer; radius and steps
Documentation checked
Open sourceS89 Turf intersect API
Software method
Version 7.2.0 intersect; polygon intersection
Documentation checked
Open sourceS90 Turf point in polygon API
Software method
Version 7.2.0 booleanPointInPolygon; boundary option
Documentation checked
Open sourceS91 UN Handbook of Surveys on Households and Individuals
Published guidance
Chapter 9 section 9.4.2, equation 9-16, printed page 9-19 (PDF page 427); Chapter 8 weighting; Final Draft
Weighting guidance checked; draft status retained
Open sourceS92 World Bank Impact Evaluation in Practice Second Edition
Published method
Chapter 7 Difference in Differences
Method text checked
Open sourceNF-SOURCE-01 Original context source linked by NF001
Source content checked; linked methods need separate review
Statistical Abstract 2025, Chapter 5: agriculture tables and methodology links
Content checked
This is a source catalogue for agricultural observations and definitions. The linked shares, intensity and forecast-error rules remain project method definitions until their exact input and estimator choices are approved.
Open sourceNF-SOURCE-02 Original context source linked by NF014
Source content checked; linked methods need separate review
SEPC Downloads: Cost of Cultivation and Crop Enterprise Budget
Content checked
The page supplies relevant budget and cultivation publications. It does not by itself verify every linked cost, delay or post-harvest-loss formula. The selected publication and cost scope still require confirmation.
Open sourceNF-SOURCE-03 Original context source linked by NF023
Source content checked; linked methods need separate review
FAO RUSLE toolbox: equation A = R K L S C P and factor definitions
Content checked
The page explicitly supports the RUSLE factor equation for sheet and rill erosion. Scenario subtraction and class-area summaries are separate project operations. Units, factors and local calibration remain pending E01/E02.
Open sourceNF-SOURCE-04 FAO Guidelines for land-use planning: official general guidance
Official FAO planning guidance; proposed alternative for expert review
FAO Development Series 1, 1993; Chapter 3, planning steps, especially Steps 1, 5 and 6; Chapter 4, methods and sources
Official alternative checked
The FAO guide supplies general planning guidance. It is not a confirmed replacement for the Sri Lankan divisional manual. Local limits, source maps, planning rules and the linked area/change calculations remain subject to C04/E01/E02 approval. The LUPPD report provides separate institutional context.
Open sourceNF-SOURCE-05 Original context source linked by NF034
Source content checked; linked methods need separate review
UNCCD Good Practice Guidance Version 2 landing page: land cover, productivity and soil organic carbon
Content checked
The guidance landing page is available. Use the already cited IPCC source S79 for the soil-stock equation; sampling, units and local application remain expert decisions.
Open sourceNF-SOURCE-06 Original context source linked by NF049
Source content checked; linked methods need separate review
FAO indicator 6.4.2: freshwater withdrawal relative to renewable resources after environmental water requirements
Content checked
This source is about water stress. It does not support the linked connection-coverage, utility-loss, leakage-index, groundwater or regulatory-compliance formulas. Those remain separate project proposals needing method-specific evidence.
Open sourceNF-SOURCE-07 Original context source linked by NF059
Source content checked; linked methods need separate review
FAO Forest Resources Assessment document: Land Classifications, Forest Parameters and Changes
Content checked
This is historical terminology and assessment context. It does not verify every linked basal-area, biomass, carbon, survival or alert-review procedure. Current definitions and the appropriate method sources remain required.
Open sourceNF-SOURCE-08 Original context source linked by NF072
Source content checked; linked methods need separate review
GBIF Data quality recommendations: occurrence and sampling-event requirements; sensitive-species handling
Content checked
This source supports record quality and publication requirements. It is not the calculation source for Shannon diversity, STAR, habitat change or response-time metrics.
Open sourceNF-SOURCE-09 Original context source linked by NF085
Source content checked; linked methods need separate review
WMO Climatological Normals: definitions of averages, normals and standard normals
Replacement checked
The original link redirects to this official page. It defines reference periods. SPI uses the separate guide S82; dry-spell thresholds, missing-data policy and local baseline approval remain separate.
Open sourceNF-SOURCE-10 Original context source linked by NF097
Source content checked; linked methods need separate review
Sendai Framework Monitor methodology: Targets and Indicators, including target C direct economic loss relative to GDP
Content checked
The page supports official disaster-indicator definitions. SHARED family coverage, funding gaps, occupancy, response lags and site-overlay rules are separate project measures with their own scope and denominators.
Open sourceNF-SOURCE-11 UNEP SDG 6.3.2 ambient water-quality metadata
Source content checked; linked methods need separate review
UNSD metadata PDF, sections 2.a and 4.c; classification and indicator computation
Replacement checked
The original UN-Water page is access-limited. The custodian metadata is readable. It aggregates assessed water bodies after classification. A parameter-test compliance percentage such as NF107 is not the complete SDG 6.3.2 indicator.
Open sourceNF-SOURCE-12 HARTI Daily Food Commodities Bulletin: checked price publication
Official HARTI price observations; not a universal calculation-method source
Selected bulletin 2026.10.30, PDF page 1: wholesale ranges, published averages and changes by market; explicit Rs/kg and Rs/egg groups
Official alternative checked
The official PDF contains price tables. Read each column date, market and unit; a dash means missing, not zero. This is a selected publication, not a live feed or proof of reuse permission. Medians, volatility, farm-gate spreads and logistics/export measures need additional accepted data and methods under C04/E01.
Open sourceNF-SOURCE-13 Original context source linked by NF135
Source content checked; linked methods need separate review
DCS Household Income and Expenditure Survey publication and report links
Content checked
The page identifies household-survey sources. Use the selected report's poverty line, survey weights and population definition. Outreach, grievance and training measures are project rules, not HIES estimators.
Open sourceNF-SOURCE-14 World Bank Burkina Faso rural development project appraisal, Report 73486-BF
Source content checked; linked methods need separate review
PDF page 107, printed page 97: Formulas for computing economic and financial ratios
Content checked
The historical appraisal gives periodic IRR, NPV, simple payback and sensitivity examples. Its payback formula is not discounted payback. It does not establish SHARED debt-service rules, PES valuations or local financing assumptions.
Open sourceNF-SOURCE-15 Original context source linked by NF158
Source content checked; linked methods need separate review
FP124 Annual Performance Report 2025, Version 1.0: landing page and linked main PDF
Content checked
The report and its PDF are readable. The publisher says the report is under review and may change. It supplies project reporting context, not an approved definition for every linked SHARED workflow ratio.
Open sourceNF-SOURCE-16 Original context source linked by NF173
Source content checked; linked methods need separate review
UNSD SDG metadata repository: introduction and indicator-specific metadata
Content checked
The repository is available and explains metadata governance. It does not prescribe the linked SHARED schema-pass, timeliness, provenance, matching or expired-rights ratios. Those are project control measures requiring client acceptance.
Open sourceDomain method sources
The complete source CSV includes the 133 retained entries and these additional domain source notes.
DD-WATER FAO56 root-zone water balance
Institution publication. Chapter8 equation85 and ETc = Kc ETo. Daily water balance components; local coefficients and operating assumptions still need review.
Open sourceDD-PESTICIDES Sri Lanka Registrar of Pesticides
Government publication. Current registration lists, restrictions and label guidance. Registration and label evidence; no treatment recommendation or automatic permission.
Open sourceDD-CEA CEA ambient water regulations
Government publication. Gazette2148/20, Schedule of use-specific categories. Published ambient water categories and limits; do not substitute them for drinking-water, effluent, air or noise rules.
Open sourceDD-BRIER JMA numerical weather prediction outline
Government publication. AppendixA.3, equationsA.3.1 and A.3.3. Brier score and reference skill for binary probability forecasts; the prototype uses one specified event, not an undifferentiated seasonal score.
Open sourceDD-NRW JICA non-revenue water training materials
Institution publication. Training materials, section1.1, IWA water-balance table. NRW, unbilled authorized use, apparent and real losses are distinct components.
Open sourceDD-ILO ILO controlling occupational risks
Institution publication. Controlling risks; hierarchy of controls. Evidence-led control review; no universal numeric risk score or clearance.
Open sourceDD-GBIF 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.
Open sourceDD-LOCAL 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.
Open sourcePES-FAO FAO Payments for environmental services what role in sustainable agricultural development
Institution publication. ESA Working Paper 11-20; section 2 printed pages 3–5; sections 3 and 4 on evidence, costs and equity. Conditional agreements, baseline/additionality, monitoring, funding and fairness. Does not set a Sri Lankan scheme, rate, tariff or automatic payment rule.
Open sourceUSDA-BULK-DENSITY USDA NRCS: Soil Quality Indicators — Bulk Density
Government publication. Page 1, definition and Factors Affecting. Defines dry soil mass divided by total core volume, in g/cm³. Supports the measurement definition, not the fictional observations or a local compaction threshold.
Open sourceFAO-MOISTURE-BASIS FAO: Prevention of post-harvest food losses — Measurement
Intergovernmental publication. Section 1.1 Definitions, Moisture content, wet basis. Wet-basis moisture is water mass divided by the total mass of water and dry matter. Supports the stated percentage basis, not a commodity acceptance limit or the fictional observations.
Open sourceNIST-CELSIUS NIST: SI Units — Temperature
Government publication. SI Units — Temperature, definition and exact temperature conversion. Zero kelvin is absolute zero and Celsius temperature equals kelvin temperature minus 273.15. Supports the physical lower bound, not shipment specifications or fictional observations.
Open sourceMET-DOM-AGRO Department of Meteorology agrometeorological bulletin
Government publication. 5 November 2026, page 4 Table 01. Directly published district cumulative departures; 1981–2010 baseline. The masked weekly map and Table 02 are excluded.
Open sourceMET-DOM-RAIN Department of Meteorology seasonal rainfall outlook
Government publication. SF-2026-11, issue information and seasonal/monthly outlook. Issued forecast product metadata and category-probability context; not a matched hindcast archive.
Open sourceMET-DOM-CONSENSUS Department of Meteorology consensus seasonal outlook
Government publication. NDJ 2026/27 outlook, issued 30 October 2026. Published outlook and issue/validity context; no future-performance guarantee.
Open sourceMET-DOM-TEMP Department of Meteorology temperature outlook
Government publication. Issued 4 November 2026; headings, captions and availability note. Original product with conflicting printed period labels retained; unavailable districts are not filled.
Open sourceMET-DOM-MARINE Department of Meteorology marine forecast archive
Government publication. Marine sea-weather page captured 10 November 2026; issued 14:00. Archived sea-area wording, wind range and duration. Not current vessel clearance.
Open sourceMET-FAO-WEATHER FAO Irrigation and Drainage Paper 56 meteorological data
Institution publication. Chapter 3 meteorological data; wind speed, climatic data acquisition and minimum requirements. Weather-variable definitions and reference-site requirements. The input checklist is a project implementation, not a published ETo result.
Open sourceMET-WMO-8 WMO Guide to Instruments and Methods of Observation
Institution publication. WMO No. 8; applicable instrument, siting and maintenance chapter and edition to be recorded. Instrument observation, siting, calibration and maintenance context. No universal site score or calibration acceptance is inferred.
Open sourceMET-WMO-CLIMATE WMO climate-data quality and homogenization guidance
Institution publication. Climate data quality, metadata, homogenization and dataset-management guidance. Need for original data, metadata and climate-series quality assessment. The prototype performs no homogenization or trend attribution.
Open sourceUSLE factor product
Verified published formula · Government publication
1980 technical publication SA-TP 11; Universal Soil Loss Equation, printed page 2; metric conversion appendix, printed page 40
The historical source verifies the factor product. Local factor choice and suitability still need confirmation; this is not a full RUSLE2 implementation.
Enterprise gross margin
Verified published formula · Institution publication
Chapter 4, Gross margin and section 4.7.1
Per-hectare and variable-cost break-even outputs are algebraic rearrangements. Local costs, prices and interpretation still need confirmation.
Discounted cash-flow NPV
Verified published formula · Institution publication
Sections 2.2.2 and 2.2.3, discounting and Net Present Value
The five-year horizon, discount rate and cash assumptions are local settings. Verification does not approve an investment or loan.
Carbon stock-difference component
Verified published component · Institution publication
Intergovernmental Panel on Climate Change · 2006 IPCC Guidelines Volume 4 Chapter 2
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.
Soil-carbon stock with volume correction
Verified published formula · Institution publication
Intergovernmental Panel on Climate Change · Good Practice Guidance for LULUCF
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.
Difference-in-differences arithmetic
Verified published formula · Institution publication
World Bank · Impact Evaluation in Practice Second Edition
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.
Sample coefficient of variation
Verified published formula · Government publication
National Institute of Standards and Technology United States · Dataplot Coefficient of Variation
Description, sample coefficient of variation and ratio-scale restrictions
Use a meaningful zero and positive mean. Local series selection and decision limits still need confirmation.
HHI concentration component
Verified published component · Government publication
United States Department of Justice · Herfindahl Hirschman Index
Definition and four-firm worked example
The screen uses fractional shares on a 0–1 scale, equivalent to the published percentage-share score divided by 10000. Local exposure categories and policy thresholds are not verified by this source.
Matched-pair RMSE
Verified published formula · Government publication
Environment and Climate Change Canada · What is Root Mean Square Error
Displayed RMSE equation and definitions of forecast, observation and verification count
Local verification periods, observation quality and forecast applicability still need confirmation.
Binary Brier score and skill component
Verified published component · Government publication
Sections A.3.1 and A.3.2, equations A.3.1 and A.3.3, printed page 239, PDF page 7
The Brier score is checked for binary events. The prototype permits a supplied reference forecast; confirm its independent baseline and comparability before interpreting skill.
Crop evapotranspiration ETc component
Verified published component · Institution publication
Chapter 5, Crop coefficient approach, equation 56
This verifies the ETc component only. Local water-balance allowances, coefficients and operating decisions still need confirmation.
Weighted estimation component
Verified published component · Institution publication
United Nations Statistics Division · Handbook of Surveys on Households and Individuals Final Draft
Chapter 9, paragraphs 38 and 39, printed page 9-9, PDF page 417; Chapter 8 weighting
Local weights, population coverage, design variance and ratio-yield interpretation still need confirmation. Positive illustrative weights do not demonstrate every calibration design.
IWA water-balance components
Verified published component · Institution publication
Asian Development Bank · The Issues and Challenges of Reducing Non-Revenue Water
Figure 4, printed page 15; Annex 1 Water Balance Definitions, printed pages 39–41, PDF pages 47–49
Apparent-loss estimates and the residual real-loss estimate remain local inputs with measurement uncertainty.