Project Management Unit

Tell us what to change or add.

1. Check a decision

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

2. Try the inputs

Use Change example to try different values. Use Data needed to check the fields and sources. The land-use change decision has its own comparison views.

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

3. Check each decision

1. Follow up project outputs awaiting verificationDEC-DP11-001 · Output verification
Try this decision

Identify project outputs whose checking or verified completion is outstanding.

Validation required

Fictional default example · 2025.

Fictional case / areaVerified completion share [%]Not verified complete [cases]Original cases awaiting review [cases]Reviewed cases not confirmed complete [cases]Next check
Laggala Pallegama — output verification / 202553.333844836Check the original cases that have not reached a verified outcome
Rattota — output verification / 202553.333844836Check the original cases that have not reached a verified outcome
Panvila — output verification / 202553.333844836Check the original cases that have not reached a verified outcome

What the selected record shows. Verified completion share: 53.333 %.

Next step. Check the original cases that have not reached a verified outcome. Prepare progress follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Recorded completion stages do not establish formal acceptance.

Inputs, method and sources
Supplied inputValueUnit
Distinct original programme activity in the stated cohort180cases
Those original cohort members with documented review132cases
Those reviewed members meeting the stated completion definition96cases
Original cohort members whose follow-up is unknown12cases

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

Attendance, receipt, adoption, delivered service and outcomes are distinct stages. Repeated visits must not become new people. The original cohort and nested review/completion stages must match; an uncompleted record is not automatically overdue. Unknown follow-up is a subset, not an extra stage.

Other required records: Output ID; target; submitted quantity; accepted quantity; evidence; reviewer.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
2. Investigate spending ahead of verified physical progress (proposed; scope pending)DEC-DP11-002 · Delivery performance
Try this decision

Review expenditure and verified physical progress against their separate plans.

Validation required

Fictional default example · 2025.

Fictional case / areaSpending against phased budget [%]Verified physical progress [%]Verified minus planned progress [percentage points]Next check
Laggala Pallegama — delivery performance / 202566.66740-20Check the matching records and reasons for the difference
Rattota — delivery performance / 202566.66740-20Check the matching records and reasons for the difference
Panvila — delivery performance / 202566.66740-20Check the matching records and reasons for the difference

What the selected record shows. Spending against phased budget: 66.667 %.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

The percentages have different denominators; their difference is not a measure of misuse.

Inputs, method and sources
Supplied inputValueUnit
Phased budget for the period1,800,000LKR
Actual spending1,200,000LKR
Planned physical progress60%
Independently verified physical progress40%

100 × spending/phased budget, and verified−planned physical progress. Do not subtract LKR from physical progress, infer earned value or equate expenditure with outcomes.

Other required records: Activity; phased budget; actual expenditure; planned progress; verified progress.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
3. Follow up source reviews needed for reportsDEC-DP11-003 · Reporting bottlenecks
Try this decision

Identify overdue source reviews needed for project reporting.

Validation required

Fictional default example · 2025.

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

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

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

Information still needed
  • Documented critical unresolved condition: Unknown

A reporting deadline does not establish data quality or permit release.

Inputs, method and sources
Supplied inputValueUnit
Received or defect observed2025-04-01
Recorded due date2025-06-01
Assessment date2025-06-30
Case/work closedNo
Documented critical unresolved conditionUnknown
Responsible office or maintainerProposed responsible office
Actual closure date when closedNot provided

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

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

Other required records: Report deadline; required dataset; submission status; review age; responsible owner.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
4. Check overlapping interventions at the same sitesDEC-DP11-004 · Intervention overlap
Try this decision

Check interventions whose stated sites, purposes and delivery periods overlap.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlapping days [days]Next check
Laggala Pallegama — intervention overlap / 202561Review possible overlap
Rattota — intervention overlap / 202561Review possible overlap
Panvila — intervention overlap / 202561Review possible overlap

What the selected record shows. Overlapping days: 61 days. Review possible overlap.

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

An overlap is a coordination flag, not proof of double counting or wrongdoing.

Inputs, method and sources
Supplied inputValueUnit
Permitted recipient/service referenceLaggala Pallegama — intervention overlap
Support purposeSample seasonal input support
Earlier support period begins2025-01-01
Earlier support period ends2025-06-30
Other support period begins2025-05-01
Other support period ends2025-08-31
Same purpose and qualifying unitYes

Compare the same permitted entity, purpose and qualifying unit. Intersect dated support intervals; overlapping support is a review flag, not proof of duplicate entitlement.

Other required records: Site ID; intervention footprint; component; schedule; beneficiary IDs; purpose.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
5. Compare work-plan alternatives within programme constraintsDEC-DP11-005 · Annual planning
Try this decision

Compare work-plan choices against commitments, resources and programme constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Complete committed activities first / Laggala PallegamaFocus the plan on existing commitments.Needs confirmed obligations, dependencies, capacity and remaining funding.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Stage the remaining work packages / Laggala PallegamaDeliver the remaining packages in defined stages.Needs compatible stage boundaries, resource windows and updated delivery evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Redistribute field-support capacity / Laggala PallegamaMove proposed field-support effort to the stated work gaps.Needs skills, partner agreement, access and a defensible workload comparison.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

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

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

Information still needed
  • Records needed: Activities; costs; dependencies; outcomes; capacity; safeguards; funding ceiling
  • Applicable conditions, what was checked and the supporting reference

A budget surplus does not establish deliverability or programme value.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionFocus the plan on existing commitments.
Resource needs and adverse effectsNeeds confirmed obligations, dependencies, capacity and remaining funding.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

A budget surplus does not establish deliverability or programme value.

Other required records: Activities; costs; dependencies; outcomes; capacity; safeguards; funding ceiling.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
6. Identify unfunded activities and unfulfilled co-financing (proposed; scope pending)DEC-DP11-006 · Funding commitments
Try this decision

Reconcile activity funding needs, commitments, receipts and expenditure.

Validation required

Fictional default example · 2025.

Fictional case / areaUnfunded need [LKR]Committed but not disbursed [LKR]Disbursed but not spent [LKR]Next check
Laggala Pallegama — funding commitments / 2025850,0001,010,000440,000Review unfunded need
Rattota — funding commitments / 2025850,0001,010,000440,000Review unfunded need
Panvila — funding commitments / 2025850,0001,010,000440,000Review unfunded need

What the selected record shows. Unfunded need: 850,000 LKR. Review unfunded need.

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

Unfunded need and undisbursed commitments are separate gaps.

Inputs, method and sources
Supplied inputValueUnit
Approved financing need3,500,000LKR
Confirmed commitments2,650,000LKR
Funds actually disbursed1,640,000LKR
Verified eligible expenditure1,200,000LKR

Unfunded = need − commitments. Undisbursed = commitments − disbursements. Unspent = disbursements − eligible spending.

Keep commitments, cash receipts, expenditure and verified physical outputs separate. Negative balances flag overcommitment or reconciliation; no automatic accounting adjustment.

Other required records: Approved cost; confirmed commitments; disbursements; expenditure; currency; funding terms.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
7. Prioritize procurements on the implementation critical path (proposed; scope pending)DEC-DP11-007 · Procurement scheduling
Try this decision

Check procurement task windows, resources and dependencies.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — procurement scheduling / 202538Resolve overlapping resource bookings
Rattota — procurement scheduling / 202538Resolve overlapping resource bookings
Panvila — procurement scheduling / 202538Resolve overlapping resource bookings

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

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

The example does not establish a complete project critical path or authorise procurement.

Inputs, method and sources
Supplied inputValueUnit
Required resourceWatershed field team
Task start2025-06-01
Task end2025-06-04
Earliest permitted start2025-05-28
Latest permitted finish2025-06-08
Required resource effort16hours
Available resource effort24hours
Predecessor task referenceNone
Mandatory permits and prerequisitesMet

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

Other required records: Procurement package; lead time; milestones; dependencies; approvals; delivery windows.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
8. Escalate contract milestone delays and unresolved deliverables (proposed; scope pending)DEC-DP11-008 · Contract performance
Try this decision

Compare contract milestone dates and the evidence for outstanding deliverables.

Validation required

Fictional default example · 2025.

Fictional case / areaCalendar date difference [days]Next check
Laggala Pallegama — contract performance / 20258Check the matching records and reasons for the difference
Rattota — contract performance / 20258Check the matching records and reasons for the difference
Panvila — contract performance / 20258Check the matching records and reasons for the difference

What the selected record shows. Calendar date difference: 8 days.

Next step. Check the matching records and reasons for the difference. Prepare difference review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

A date difference does not determine liability, penalties or contractual acceptance.

Inputs, method and sources
Supplied inputValueUnit
Planned milestone/sowing date2025-06-01
Observed completion/sowing date2025-06-09

Observed date minus planned date in calendar days. Missing actual dates are pending, not zero delay. Approved working-day rules require a defined calendar.

Other required records: Contract version; milestone dates; actual delivery; acceptance; conditions; contractor.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
9. Review environmental and social case evidenceDEC-DP11-009 · Safeguards
Try this decision

Check environmental and social case evidence for responsible referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — safeguards / Laggala PallegamaActivity scope: MissingObtain the missing evidence listed below
Rattota — safeguards / Rattotascreening: MissingObtain the missing evidence listed below
Panvila — safeguards / Panvilaaffected people: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Activity scope: Missing

A checklist does not certify safeguards or calculate a risk probability.

Inputs, method and sources
Supplied inputValueUnit
Activity scopeMissing
Activity scope evidence referenceNot provided
screeningDocumented
screening evidence referenceSample Laggala Pallegama field register / 2025
affected peopleDocumented
affected people evidence referenceSample Laggala Pallegama field register / 2025
safeguardsDocumented
safeguards evidence referenceSample Laggala Pallegama field register / 2025
mitigationsDocumented
mitigations evidence referenceSample Laggala Pallegama field register / 2025
reviewerDocumented
reviewer evidence referenceSample Laggala Pallegama field register / 2025
conditionsDocumented
conditions evidence referenceSample Laggala Pallegama field register / 2025
Documented unresolved critical conditionUnknown
Evidence observation date2025-06-30
Existing control and its evidenceSample documented control
Competent recipientResponsible specialist / duty authority

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

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

Other required records: Activity scope; screening; affected people; safeguards; mitigations; reviewer; conditions.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
10. Follow up overdue programme grievancesDEC-DP11-010 · Grievances
Try this decision

Identify programme grievances whose response date has passed.

Validation required

Fictional default example · 2025.

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

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

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

Information still needed
  • Documented critical unresolved condition: Unknown

The prototype does not send an escalation or determine the grievance outcome.

Inputs, method and sources
Supplied inputValueUnit
Received or defect observed2025-04-01
Recorded due date2025-06-01
Assessment date2025-06-30
Case/work closedNo
Documented critical unresolved conditionUnknown
Responsible office or maintainerProposed responsible office
Actual closure date when closedNot provided

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

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

Other required records: Case ID; confidential category; received date; due date; response; escalation owner.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
11. Find gaps in access to project benefitsDEC-DP11-011 · Participation equity
Try this decision

Identify eligible households without confirmed access to project benefits.

Validation required

Fictional default example · 2025.

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

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

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

Coverage does not establish eligibility, vulnerability or informed consent.

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

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

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

Other required records: Eligible population frame; unique recipients; consented group attributes; location; benefit type.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
12. Compare material scope-change alternatives before approvalDEC-DP11-012 · Change control
Try this decision

Compare a proposed scope change with the retained baseline and constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Retain the agreed baseline / Laggala PallegamaKeep the current proposed baseline unchanged.Needs evidence that the retained plan still addresses the intended requirements.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Stage the proposed scope change / Laggala PallegamaIntroduce the proposed change in stages.Needs a reviewed change case, dependencies, costs and client authority.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Use a limited pilot change / Laggala PallegamaTest the proposed change in a bounded pilot.Needs clear scope, safeguards, measures and an agreed decision after the pilot.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

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

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

Information still needed
  • Records needed: Baseline scope; proposed change; cost; schedule; benefits; consultations; constraints
  • Applicable conditions, what was checked and the supporting reference

The example neither accepts a change nor alters the agreed scope.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionKeep the current proposed baseline unchanged.
Resource needs and adverse effectsNeeds evidence that the retained plan still addresses the intended requirements.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

The example neither accepts a change nor alters the agreed scope.

Other required records: Baseline scope; proposed change; cost; schedule; benefits; consultations; constraints.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
13. Check mandatory conditions before work startsDEC-DP11-013 · Decision conditions
Try this decision

Identify missing evidence for mandatory pre-work conditions.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — decision conditions / Laggala PallegamaDecision version: MissingObtain the missing evidence listed below
Rattota — decision conditions / Rattotarequired approvals: MissingObtain the missing evidence listed below
Panvila — decision conditions / Panvilaconditions: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Decision version: Missing

A complete record does not grant an approval or operate a real work stoppage.

Inputs, method and sources
Supplied inputValueUnit
Decision versionMissing
Decision version evidence referenceNot provided
required approvalsDocumented
required approvals evidence referenceSample Laggala Pallegama field register / 2025
conditionsDocumented
conditions evidence referenceSample Laggala Pallegama field register / 2025
completion evidenceDocumented
completion evidence evidence referenceSample Laggala Pallegama field register / 2025
appointed authorityDocumented
appointed authority evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Decision version; required approvals; conditions; completion evidence; appointed authority.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
14. Resolve dependency conflicts between implementing partnersDEC-DP11-014 · Partner coordination
Try this decision

Check partner tasks for resource clashes and unmet predecessors.

Validation required

Fictional default example · 2025.

Fictional case / areaPlanned duration [days]Resource hours remaining [hours]Next check
Laggala Pallegama — partner coordination / 202538Resolve overlapping resource bookings
Rattota — partner coordination / 202538Resolve overlapping resource bookings
Panvila — partner coordination / 202538Resolve overlapping resource bookings

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

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

A draft schedule does not assign work to a partner.

Inputs, method and sources
Supplied inputValueUnit
Required resourceWatershed field team
Task start2025-06-01
Task end2025-06-04
Earliest permitted start2025-05-28
Latest permitted finish2025-06-08
Required resource effort16hours
Available resource effort24hours
Predecessor task referenceNone
Mandatory permits and prerequisitesMet

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

Other required records: Partner tasks; deliverables; due dates; dependencies; capacity; consultation responses.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
15. Assess verified programme outcomes and attribution limitsDEC-DP11-015 · Outcome evaluation
Try this decision

Compare programme outcome changes and the evidence for attribution.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [percentage points]Next check
Laggala Pallegama — outcome evaluation / 202510Obtain the missing evidence listed below
Rattota — outcome evaluation / 202510Obtain the missing evidence listed below
Panvila — outcome evaluation / 202510Obtain the missing evidence listed below

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

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

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

A descriptive difference does not establish a programme effect.

Inputs, method and sources
Supplied inputValueUnit
Intervention group households receiving the stated programme service within the same observation window before42%
Intervention group households receiving the stated programme service within the same observation window after59%
Comparison group households receiving the stated programme service within the same observation window before39%
Comparison group households receiving the stated programme service within the same observation window after46%
Study design and comparability evidenceMissing
Outcome definition, method and reference basisFictional measure: Households receiving the stated programme service within the same observation window / matching frame, method and before-after windows

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

The arithmetic alone does not establish causation. Design, parallel trends, confounding, attrition, uncertainty and adverse effects need appropriate evidence. This named fictional indicator illustrates the calculation. Design evidence, adverse effects and attribution remain separate; a difference in changes does not establish causation.

Other required records: Baseline indicators; follow-up; comparison; sampling; external factors; evaluation design.

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

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

Calculation appendix

  • World Bank Impact Evaluation in Practice Second Edition — Institution publication. Chapter7 difference-in-differences. Published difference-in-differences estimator and study assumptions; aggregate examples do not establish causation.
  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
16. Compare financial consequences of implementation scenarios (proposed; scope pending)DEC-DP11-016 · Risk financing
Try this decision

Compare the stated financial scenario cash flows.

Verified published formula · Discounted cash-flow NPV

Fictional default example · 2025.

Fictional case / areaFive-year net present value [LKR]Next check
Base cash-flow scenario / 2025109,847.353Review the cash flows, discount assumptions and constraints
Lower net-receipts scenario / 2025-497,196.989Review the cash flows, discount assumptions and constraints
Higher initial-cost scenario / 2025-370,152.647Review the cash flows, discount assumptions and constraints

What the selected record shows. 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 step. Review the cash flows, discount assumptions and constraints. Prepare cash-flow comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Present value alone does not approve an implementation or financing choice.

Example chart
Five-year net present value — fictional 2025 examples
Inputs, method and sources
Supplied inputValueUnit
Initial investment2,400,000LKR
Net cash flow year1400,000LKR
Net cash flow year2550,000LKR
Net cash flow year3680,000LKR
Net cash flow year4720,000LKR
Net cash flow year5760,000LKR
Residual value at end of year5120,000LKR
Example discount rate8%

NPV = −initial investment + sum of year1…5 net cash flows discounted at the stated annual rate, including residual value once in year5.

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.

Other required records: Scenario costs; delays; benefits; residual risks; cash-flow dates; discount rate.

Food and Agriculture Organization of the United Nations · Guidelines for defining financial economic environmental and social information
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.

Calculation appendix

Your checks for this decision
17. Check asset ownership and maintenance evidenceDEC-DP11-017 · Asset handover
Try this decision

Identify handover assets missing maintenance, ownership or responsibility evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — asset handover / Laggala PallegamaAsset ID: MissingObtain the missing evidence listed below
Rattota — asset handover / Rattotaacceptance: MissingObtain the missing evidence listed below
Panvila — asset handover / Panvilaowner: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Asset ID: Missing

A complete checklist does not transfer ownership or establish operational acceptance.

Inputs, method and sources
Supplied inputValueUnit
Asset IDMissing
Asset ID evidence referenceNot provided
acceptanceDocumented
acceptance evidence referenceSample Laggala Pallegama field register / 2025
ownerDocumented
owner evidence referenceSample Laggala Pallegama field register / 2025
maintenance planDocumented
maintenance plan evidence referenceSample Laggala Pallegama field register / 2025
budgetDocumented
budget evidence referenceSample Laggala Pallegama field register / 2025
trainingDocumented
training evidence referenceSample Laggala Pallegama field register / 2025
handover conditionsDocumented
handover conditions evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Asset ID; acceptance; owner; maintenance plan; budget; training; handover conditions.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
18. Compare piloting, expansion and redesign choicesDEC-DP11-018 · Learning and scaling
Try this decision

Compare further piloting, expansion and redesign choices using the available evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Continue a bounded pilot / Laggala PallegamaContinue a bounded test of the intervention.Needs a sound design, outcomes, resources and criteria for the next review.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Expand to comparable locations / Laggala PallegamaExpand the intervention to stated comparable locations.Needs transferability, site comparability, delivery capacity and safeguard evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Redesign before further testing / Laggala PallegamaRedesign the intervention before testing again.Needs evidence of the current limitations and a testable revised approach.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing

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

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

Information still needed
  • Records needed: Verified outcomes; costs; context; adverse effects; evidence quality; transferability
  • Applicable conditions, what was checked and the supporting reference

A cost comparison does not establish readiness to scale.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionContinue a bounded test of the intervention.
Resource needs and adverse effectsNeeds a sound design, outcomes, resources and criteria for the next review.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

A cost comparison does not establish readiness to scale.

Other required records: Verified outcomes; costs; context; adverse effects; evidence quality; transferability.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
19. Correct incomplete references in reporting evidence packagesDEC-DP11-019 · Evidence catalogue
Try this decision

Identify missing source references and definitions in a report package.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — evidence catalogue / Laggala PallegamaEvidence ID: MissingObtain the missing evidence listed below
Rattota — evidence catalogue / Rattotasource version: MissingObtain the missing evidence listed below
Panvila — evidence catalogue / Panvilaperiod: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Evidence ID: Missing

Complete references do not verify the underlying findings.

Inputs, method and sources
Supplied inputValueUnit
Evidence IDMissing
Evidence ID evidence referenceNot provided
source versionDocumented
source version evidence referenceSample Laggala Pallegama field register / 2025
periodDocumented
period evidence referenceSample Laggala Pallegama field register / 2025
geographyDocumented
geography evidence referenceSample Laggala Pallegama field register / 2025
licenseDocumented
license evidence referenceSample Laggala Pallegama field register / 2025
reviewerDocumented
reviewer evidence referenceSample Laggala Pallegama field register / 2025
lineageDocumented
lineage evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Evidence ID; source version; period; geography; license; reviewer; lineage.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
20. Resolve outstanding financial technical and safeguard obligationsDEC-DP11-020 · Project closure
Try this decision

Check outstanding financial, technical and safeguard obligations.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — project closure / Laggala PallegamaClosure checklist: MissingObtain the missing evidence listed below
Rattota — project closure / Rattotacontracts: MissingObtain the missing evidence listed below
Panvila — project closure / Panvilafinances: MissingObtain the missing evidence listed below

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

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

Information still needed
  • Closure checklist: Missing

Document completeness does not establish final programme acceptance.

Inputs, method and sources
Supplied inputValueUnit
Closure checklistMissing
Closure checklist evidence referenceNot provided
contractsDocumented
contracts evidence referenceSample Laggala Pallegama field register / 2025
financesDocumented
finances evidence referenceSample Laggala Pallegama field register / 2025
assetsDocumented
assets evidence referenceSample Laggala Pallegama field register / 2025
unresolved casesDocumented
unresolved cases evidence referenceSample Laggala Pallegama field register / 2025
outcome evidenceDocumented
outcome evidence evidence referenceSample Laggala Pallegama field register / 2025

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

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

Other required records: Closure checklist; contracts; finances; assets; unresolved cases; outcome evidence.

Calculation appendix

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

4. Existing data forms for your institution

Check which existing source fields can supply the decision inputs.

FP124 financing · Programme Delivery

Existing form reference: e6af681e07c8efdc

FieldUnitRequired
Funding itemConfirm if neededNo
InstrumentConfirm if neededNo
AmountUSDNo
CurrencyConfirm if neededNo
DateConfirm if neededNo
BasisConfirm if neededNo

5. Documents and images

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

Project Management Unit Documents and images prototype screen
Project Management Unit. Prototype screen. Select the image to enlarge it.

What you can try

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

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

What your institution needs to confirm

6. Data structure management

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

Project Management Unit Data structure management prototype screen
Project Management Unit. Prototype screen. Select the image to enlarge it.

What you can try

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

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

What your institution needs to confirm

7. Users and access

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

Project Management Unit Users and access prototype screen
Project Management Unit. Prototype screen. Select the image to enlarge it.

What you can try

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

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

What your institution needs to confirm

8. Can you share data regularly?

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

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

9. Anything else we should change?

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