National Enterprise Development Authority

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. Improve uptake of appropriate enterprise-support offersDEC-DP27-001 · Support uptake
Try this decision

Check progression from enterprise-support offers to documented uptake.

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 — support uptake / 202553.333844836Check the original cases that have not reached a verified outcome
Rattota — support uptake / 202553.333844836Check the original cases that have not reached a verified outcome
Panvila — support uptake / 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.

Completion shares do not establish whether the support was appropriate or effective.

Inputs, method and sources
Supplied inputValueUnit
Distinct original enterprise support case 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: Eligible enterprises; offers; accepted offers; participation; reasons for non-uptake.

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. Follow trainees needing subsequent business assistanceDEC-DP27-002 · Training progression
Try this decision

Check trainee follow-up through the stated business-assistance stages.

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 — training progression / 202553.333844836Check the original cases that have not reached a verified outcome
Rattota — training progression / 202553.333844836Check the original cases that have not reached a verified outcome
Panvila — training progression / 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.

Attendance or a completed follow-up does not establish business improvement.

Inputs, method and sources
Supplied inputValueUnit
Distinct original enterprise support case 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: Training cohort; completion; business plans; support referral; business establishment.

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. Prioritize enterprise assistance cases waiting longestDEC-DP27-003 · Service delays
Try this decision

Identify enterprise-assistance cases past their recorded response date.

Validation required

Fictional default example · 2025.

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

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

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

Information still needed
  • Documented critical unresolved condition: Unknown

Age alone does not establish need, eligibility or a support priority.

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

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

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

Other required records: Case ID; support type; receipt; due date; pauses; assigned adviser.

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. Redirect outreach toward underserved target districtsDEC-DP27-004 · Geographic reach
Try this decision

Find target enterprises without confirmed outreach coverage.

Validation required

Fictional default example · 2025.

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

What the selected record shows. 30 enterprises 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.

Outreach does not establish uptake or enterprise benefit.

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

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: Enterprise frame; eligible need; support received; district; programme period.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
5. Refer enterprise plans for financial and market appraisalDEC-DP27-005 · Business viability
Try this decision

Review enterprise cash-flow scenarios before financial and market appraisal.

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.

Net present value alone does not establish viability or approve finance.

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: Sales assumptions; variable costs; fixed costs; cash flows; markets; risks.

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
6. Match enterprises to suitable finance-support pathwaysDEC-DP27-006 · Finance referral
Try this decision

Find missing evidence for a finance-support pathway referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — finance referral / Laggala PallegamaEnterprise needs: MissingObtain the missing evidence listed below
Rattota — finance referral / Rattotafinance product terms: MissingObtain the missing evidence listed below
Panvila — finance referral / Panvilaeligibility evidence: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this finance referral 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
  • Enterprise needs: Missing

The example does not approve a loan, grant or programme entitlement.

Inputs, method and sources
Supplied inputValueUnit
Enterprise needsMissing
Enterprise needs evidence referenceNot provided
finance product termsDocumented
finance product terms evidence referenceSample Laggala Pallegama field register / 2025
eligibility evidenceDocumented
eligibility evidence evidence referenceSample Laggala Pallegama field register / 2025
repayment capacityDocumented
repayment capacity evidence referenceSample Laggala Pallegama field register / 2025
consentDocumented
consent 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: Enterprise needs; finance product terms; eligibility evidence; repayment capacity; consent.

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. Allocate mentors to documented enterprise needsDEC-DP27-007 · Mentoring
Try this decision

Compare proposed mentor time with documented enterprise needs and availability.

Validation required

Fictional default example · 2025.

Fictional case / areaAvailable minus required hours [hours]Next check
Laggala Pallegama — mentoring / 20258Obtain the missing evidence listed below
Rattota — mentoring / 20258Obtain the missing evidence listed below
Panvila — mentoring / 20258Obtain the missing evidence listed below

What the selected record shows. Available minus required hours: 8 hours. Resolve specification, window or conditions.

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
  • Conflicts, clearance and mandate: Unresolved

Available hours do not establish expertise, compatibility or an appointment.

Inputs, method and sources
Supplied inputValueUnit
Documented skills/expertiseSample required skill
Task requirementSample required skill
Available qualified effort24hours
Required effort16hours
Conflicts, clearance and mandateUnresolved
Availability begins2025-06-01
Availability ends2025-06-20
Task window begins2025-06-05
Task window ends2025-06-18

Match documented expertise, available effort, date windows and required conflict/clearance evidence. A match suggests a candidate; it appoints nobody.

A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract.

Other required records: Enterprise need; mentor expertise; availability; conflicts; location; due date.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
8. Match enterprise products with verified buyer demandDEC-DP27-008 · Market linkages
Try this decision

Compare enterprise offers with documented buyer specifications and demand.

Validation required

Fictional default example · 2025.

Fictional case / areaSupply minus demand [kg]Next check
Laggala Pallegama — market linkages / 2025-300Review quantity/capacity gap
Rattota — market linkages / 2025-300Review quantity/capacity gap
Panvila — market linkages / 2025-300Review quantity/capacity gap

What the selected record shows. Supply minus demand: -300 kg. Review quantity/capacity gap.

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

A quantity match does not establish quality, an order or buyer commitment.

Inputs, method and sources
Supplied inputValueUnit
Offered product and gradeCleaned dry pepper / whole grain
Required product and gradeCleaned dry pepper / whole grain
Available uncommitted quantity1,200kg
Required quantity1,500kg
Supply available from2025-06-01
Supply available until2025-06-20
Delivery window begins2025-06-05
Delivery window ends2025-06-18
Required quality, rights and conditionsMet

Compare the same specification and unit, uncommitted quantity and overlapping delivery windows. Keep mandatory quality and use conditions explicit.

A candidate match does not reserve stock, appoint a person, authorize waste reuse or form a contract.

Other required records: Product; grade; capacity; delivery window; buyer demand; quality requirements.

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. Target follow-up to supported businesses at risk of closureDEC-DP27-009 · Enterprise survival
Try this decision

Separate confirmed business continuation, closure and unknown follow-up.

Validation required

Fictional default example · 2025.

Fictional case / areaConfirmed continuation lower bound [%]Continuation upper bound [%]Unknown follow-up [enterprises]Next check
Laggala Pallegama — enterprise survival / 20257884.44429Check unknown follow-up separately from confirmed survival and failure
Rattota — enterprise survival / 20257884.44429Check unknown follow-up separately from confirmed survival and failure
Panvila — enterprise survival / 20257884.44429Check unknown follow-up separately from confirmed survival and failure

What the selected record shows. Confirmed continuation lower bound: 78 %.

Next step. Check unknown follow-up separately from confirmed survival and failure. Prepare cohort follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.

Unknown enterprises must not be counted as closed or continuing.

Inputs, method and sources
Supplied inputValueUnit
Original distinct cohort450enterprises
Known operating enterprises351enterprises
Known closed enterprises70enterprises
Unknown follow-up29enterprises
Later entrants outside original cohort18enterprises

Lower =100 × known survivors / original cohort. Upper =100 × (known survivors + unknown) / original cohort. Survivors + known failures + unknown = original cohort; replacements do not enter it.

These bounds account for unknown status; they are not statistical confidence intervals. Use actual follow-up dates and distinguish cohort membership from repeated visits.

Other required records: Enterprise cohort; start date; operating status; follow-up; nonresponse; closure reasons.

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. Review changes in enterprise outcomes after assistanceDEC-DP27-010 · Business performance
Try this decision

Compare enterprise outcomes across the supplied support and comparison records.

Verified published formula · Difference-in-differences arithmetic

Fictional default example · 2025.

Fictional case / areaDifference in changes [LKR]Next check
Laggala Pallegama — business performance / 2025100,000Obtain the missing evidence listed below
Rattota — business performance / 2025100,000Obtain the missing evidence listed below
Panvila — business performance / 2025100,000Obtain the missing evidence listed below

What the selected record shows. Treatment change: 170,000; comparison change: 70,000; difference in changes: 100,000 LKR. 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

Differences do not establish that assistance caused the outcome.

Inputs, method and sources
Supplied inputValueUnit
Treatment Real enterprise sales on stated price basis before420,000LKR
Treatment Real enterprise sales on stated price basis after590,000LKR
Comparison Real enterprise sales on stated price basis before390,000LKR
Comparison Real enterprise sales on stated price basis after460,000LKR
Study design and comparability evidenceMissing
Outcome definition, method and reference basisReal enterprise sales on stated price basis /example matching definition1

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

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

Other required records: Baseline sales; follow-up sales; employment; costs; comparison firms; external factors.

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
11. Address gaps in access to enterprise opportunitiesDEC-DP27-011 · Women and youth support
Try this decision

Find target enterprises without confirmed access to an opportunity.

Validation required

Fictional default example · 2025.

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

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

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

Recorded access does not establish fair participation or benefit.

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

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 enterprise frame; consented group attributes; offers; participation; outcomes.

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. Refer complete enterprise-grant applications for determinationDEC-DP27-012 · Grant administration
Try this decision

Find missing source records before an enterprise-grant referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — grant administration / Laggala PallegamaScheme version: MissingObtain the missing evidence listed below
Rattota — grant administration / Rattotaapplicant evidence: MissingObtain the missing evidence listed below
Panvila — grant administration / Panvilabudget: MissingObtain the missing evidence listed below

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

The example does not award a grant or establish final eligibility.

Inputs, method and sources
Supplied inputValueUnit
Scheme versionMissing
Scheme version evidence referenceNot provided
applicant evidenceDocumented
applicant evidence evidence referenceSample Laggala Pallegama field register / 2025
budgetDocumented
budget evidence referenceSample Laggala Pallegama field register / 2025
eligibilityDocumented
eligibility evidence referenceSample Laggala Pallegama field register / 2025
prior supportDocumented
prior support evidence referenceSample Laggala Pallegama field register / 2025
approvalsDocumented
approvals 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: Scheme version; applicant evidence; budget; eligibility; prior support; approvals.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
13. Review potentially overlapping enterprise subsidiesDEC-DP27-013 · Duplicate assistance
Try this decision

Check whether assistance records overlap for the same purpose, recipient and period.

Validation required

Fictional default example · 2025.

Fictional case / areaOverlapping days [days]Next check
Laggala Pallegama — duplicate assistance / 202561Review possible overlap
Rattota — duplicate assistance / 202561Review possible overlap
Panvila — duplicate assistance / 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.

Overlapping dates do not prove duplicate or improper support.

Inputs, method and sources
Supplied inputValueUnit
Permitted recipient/service referenceLaggala Pallegama — duplicate assistance
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: Enterprise ID; programme; support purpose; amount; period; entitlement 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
14. Prioritize training topics using verified capability gapsDEC-DP27-014 · Business skills
Try this decision

Compare training approaches against the stated capability gaps.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Basic business records / Laggala PallegamaImprove basic enterprise records.Needs capability evidence, accessible delivery and practical follow-up.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Product costing and pricing / Laggala PallegamaImprove product costing and pricing skills.Needs relevant enterprise data, numeracy and application evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Quality and market-readiness training / Laggala PallegamaImprove quality and market readiness.Needs product standards, testing, buyer requirements and delivery capacity.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: Needs assessments; skills; course availability; prior training; adoption evidence
  • Applicable conditions, what was checked and the supporting reference

Cost and attendance do not establish competence or the best training topic.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionImprove basic enterprise records.
Resource needs and adverse effectsNeeds capability evidence, accessible delivery and practical follow-up.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

Cost and attendance do not establish competence or the best training topic.

Other required records: Needs assessments; skills; course availability; prior training; adoption 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
15. Identify enterprises needing registration or compliance referralsDEC-DP27-015 · Formalization support
Try this decision

Find missing registration and compliance records before a responsible referral.

Validation required

Fictional default example · 2025.

Fictional case / areaInformation still neededNext check
Laggala Pallegama — formalization support / Laggala PallegamaEnterprise stage: MissingObtain the missing evidence listed below
Rattota — formalization support / Rattotarequired registrations: MissingObtain the missing evidence listed below
Panvila — formalization support / Panvilaexisting documents: MissingObtain the missing evidence listed below

What the selected record shows. The required evidence is incomplete for this formalization support 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
  • Enterprise stage: Missing

The prototype does not register a business or determine compliance.

Inputs, method and sources
Supplied inputValueUnit
Enterprise stageMissing
Enterprise stage evidence referenceNot provided
required registrationsDocumented
required registrations evidence referenceSample Laggala Pallegama field register / 2025
existing documentsDocumented
existing documents evidence referenceSample Laggala Pallegama field register / 2025
gapsDocumented
gaps evidence referenceSample Laggala Pallegama field register / 2025
responsible agencyDocumented
responsible agency 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: Enterprise stage; required registrations; existing documents; gaps; responsible agency.

Calculation appendix

  • SHARED domain decision contracts — Validation required. Domain decision rules and matching fictional examples. Local comparisons, constraints, source matching, sorting and follow-up proposals; developer checks do not establish scientific or client approval.
Your checks for this decision
16. Compare enterprise adaptation optionsDEC-DP27-016 · Climate resilience
Try this decision

Compare enterprise-continuity choices using exposure and operating constraints.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Protect critical equipment / Laggala PallegamaProtect the documented critical equipment.Needs exposure, engineering, continuity and maintenance evidence.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Diversify suppliers and markets / Laggala PallegamaDiversify suppliers and markets.Needs feasible alternatives, quality, contracts and working capital.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Prepare a staged continuity plan / Laggala PallegamaPrepare a staged continuity plan.Needs critical-process dependencies, triggers, roles and tested arrangements.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: Hazard exposure; business dependencies; adaptation costs; continuity benefits; constraints
  • Applicable conditions, what was checked and the supporting reference

A stated benefit does not establish avoided losses or business resilience.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionProtect the documented critical equipment.
Resource needs and adverse effectsNeeds exposure, engineering, continuity and maintenance evidence.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

A stated benefit does not establish avoided losses or business resilience.

Other required records: Hazard exposure; business dependencies; adaptation costs; continuity benefits; 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
17. Allocate incubation services within facility and adviser limitsDEC-DP27-017 · Incubation capacity
Try this decision

Compare incubation demand with usable facility and adviser capacity.

Validation required

Fictional default example · 2025.

Fictional case / areaUsable capacity minus demand [adviser hours]Usable capacity [adviser hours]Next check
Laggala Pallegama — incubation capacity / 2025-15135Review capacity shortfall
Rattota — incubation capacity / 2025-15135Review capacity shortfall
Panvila — incubation capacity / 2025-15135Review capacity shortfall

What the selected record shows. Usable capacity minus demand: -15 adviser hours. Review capacity shortfall.

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

Capacity alone does not establish suitability or allocate a place.

Inputs, method and sources
Supplied inputValueUnit
Demand in the selected period150adviser hours
Rated capacity for that period180adviser hours
Unavailable or restricted capacity45adviser hours

Usable capacity = rated capacity − documented unavailable capacity. Surplus/shortfall = usable − matching demand.

Match peak/average basis, time window, skill, staffing, accessibility and other binding constraints. One aggregate capacity does not override a safety constraint.

Other required records: Applications; needs; workspace capacity; advisers; time requirements; approved criteria.

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. Identify unfunded enterprise-support commitmentsDEC-DP27-018 · Programme finance
Try this decision

Reconcile enterprise-support needs with confirmed financing.

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 — programme finance / 2025850,0001,010,000440,000Review unfunded need
Rattota — programme finance / 2025850,0001,010,000440,000Review unfunded need
Panvila — programme finance / 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.

A funding gap does not establish entitlement or authority to commit funds.

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: Budget; approved assistance; commitments; disbursements; eligible expenditure; currency.

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. Resolve inconsistent enterprise identities before reportingDEC-DP27-019 · Enterprise registry
Try this decision

Compare enterprise identity definitions and original source references.

Validation required

Fictional default example · 2025.

Fictional case / areaOriginal recordComparison recordNext check
Laggala Pallegama — enterprise registry / Laggala PallegamaRegistration ID: primary register entryRegistration ID: conflicting source returnResolve source disagreement
Rattota — enterprise registry / RattotaRegistration ID: primary register entryRegistration ID: conflicting source returnResolve source disagreement
Panvila — enterprise registry / PanvilaRegistration ID: primary register entryRegistration ID: conflicting source returnResolve source disagreement

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

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

A matching name does not establish the same legal enterprise.

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

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

Other required records: Registration ID; source names; location; owner consent; duplicates; verification.

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. Select enterprise-support approaches for continuation or redesignDEC-DP27-020 · Programme effectiveness
Try this decision

Compare continuation and redesign choices using outcome and exclusion evidence.

Validation required

Fictional default example · 2025.

Fictional case / areaPotential benefit · assumptionResources and adverse effectsSupporting records / conditionsNext check
Continue targeted mentoring / Laggala PallegamaContinue targeted mentoring.Needs documented needs, mentor competence and follow-up outcomes.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Combine finance and capability support / Laggala PallegamaCombine finance with capability support.Needs eligibility, finance conditions, market evidence and delivery capacity.Records: Not provided; condition evidence: Not providedObtain the missing records before choosing
Redesign support for excluded enterprises / Laggala PallegamaRedesign support for excluded enterprises.Needs evidence about barriers, accessibility, eligibility and participation.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; inclusion; unintended effects; context; evaluation evidence
  • Applicable conditions, what was checked and the supporting reference

Budget alone does not establish which support approach should continue.

Inputs, method and sources
Supplied inputValueUnit
Option cost1,500,000LKR
Available budget1,800,000LKR
Mandatory constraintsMet
Potential benefit and its evidence or assumptionContinue targeted mentoring.
Resource needs and adverse effectsNeeds documented needs, mentor competence and follow-up outcomes.
Required records available for this optionNot provided
Reference for the required recordsNot provided
Applicable conditions, check result and supporting referenceNot provided

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

Budget alone does not establish which support approach should continue.

Other required records: Verified outcomes; costs; inclusion; unintended effects; context; evaluation 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.

Export earnings by sector, 2015–2026 · Markets & Value Chains

Existing form reference: b3d77003d1866be4

FieldUnitRequired
SectorConfirm if neededNo
YearConfirm if neededNo
Export earningsUSD millionNo
Reporting basisConfirm if neededNo
Major export markets, 2025 · Markets & Value Chains

Existing form reference: d897e621e1f5fb87

FieldUnitRequired
SectorConfirm if neededNo
MarketConfirm if neededNo
YearConfirm if neededNo
Export earningsUSD millionNo
Made in Sri Lanka industry categories · Markets & Value Chains

Existing form reference: 3f2a54c6faac12f2

FieldUnitRequired
Industry categoryConfirm if neededNo

5. Documents and images

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

National Enterprise Development Authority Documents and images prototype screen
National Enterprise Development Authority. Prototype screen. Select the image to enlarge it.

What you can try

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

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

What your institution needs to confirm

6. Data structure management

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

National Enterprise Development Authority Data structure management prototype screen
National Enterprise Development Authority. Prototype screen. Select the image to enlarge it.

What you can try

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

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

What your institution needs to confirm

7. Users and access

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

National Enterprise Development Authority Users and access prototype screen
National Enterprise Development Authority. 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.