Tell us what to change or add.
Open a decision below. Check the area, period, inputs, result and proposed next step.
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.
Check biodiversity records against survey effort, season and protocol.
Validation required
Fictional default example · 2025.
What the selected record shows. Observed richness: 28 species. Review survey comparability.
Next step. Review survey comparability. Prepare biodiversity comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.
Recorded taxa and effort do not establish complete species presence or absence.
Show distinct observed species with survey effort, protocol, season and completed visits. No correction for detection is silently inferred.
Observed richness is not population size or occupancy. Comparable effort alone does not remove detection bias or establish a biodiversity trend.
Other required records: Protected-area frame; survey events; species; effort; protocol; season.
Calculation appendix
Identify wildlife conflict and rescue cases needing a documented follow-up.
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.
Case age alone does not establish biological urgency or authorise a response.
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: Incident; species; location; severity evidence; date; response; responsible team.
Review supplied habitat-footprint overlaps and source editions.
What the selected record shows. The supplied overlap is 18 ha within the 75 ha assessed footprint, or 24%. Check the cited boundary and source records before interpreting the overlap.
Next step. Check the matching footprint, source boundary and applicable conditions. Prepare overlap review in the prototype creates a visible, downloadable draft. It is unassigned and not sent.
Reported hectares are not a new habitat map or proof of ecological damage.
100 × union of constraint overlap / proposal footprint. Count intersecting constraint areas once. The areas/counts are supplied records; this decision view does not calculate intersections, distances or locations.
Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries.
Other required records: Species habitat; threat status edition; development footprint; survey uncertainty.
Find missing species, threat and restoration evidence for a STAR assessment.
What the selected record shows. The required evidence is incomplete for this threat reduction 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.
The checklist does not calculate or validate a STAR score.
Check each required item and retain its reference. A documented item is not a scientific, legal or institutional approval.
Evidence completeness alone cannot establish suitability, eligibility, safety, permission or method validity.
Other required records: Species range; threats; action feasibility; threat reduction evidence; uncertainty.
Compare coexistence choices using conflict evidence, rights and local constraints.
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.
Cost alone does not establish a suitable wildlife intervention.
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.
Other required records: Incident history; elephant movement; settlement use; fence options; costs; consultations.
Identify overdue fence inspections and missing maintenance records.
Inspection age does not establish fence effectiveness or immediate conflict risk.
Other required records: Fence segment; condition; failures; exposed communities; maintenance resources.
Check reported corridor overlap against dated source evidence.
A footprint overlap is not an animal-movement or connectivity analysis.
Geometry preparation must use matching coordinate systems, dated boundary editions and valid spatial predicates. Overlap supports referral; it does not determine ownership, permission or site safety. A static reference image does not verify these supplied measurements or boundaries. Reported overlap is a referral screen. It does not measure functional connectivity or species movement.
Other required records: Habitat patches; movement evidence; corridor alternatives; roads; land rights.
Identify investigation cases awaiting documented evidence or response.
The prototype does not determine an offence or enforcement action.
Other required records: Incident evidence; location; date; species; patrol capacity; responsible authority.
Compare supplied patrol journeys and access conditions.
What the selected record shows. The supplied journey is 24 km and 65 minutes. Usable capacity is 18 against 15 required in the stated service units. Access and operating conditions: Unresolved.
The example calculates no route and does not disclose sensitive operational locations.
Compare supplied route times/distances, usable capacity and documented access/window constraints. Display feasible candidates; no route optimization is implied.
Straight-line distance is not a road route. Example routes establish no current road status, emergency clearance or safe evacuation instruction. This decision view compares supplied journeys. It does not calculate a route or run a coordinate-based analysis.
Other required records: Risk locations; patrol staff; routes; travel time; terrain; access restrictions.
Check the evidence behind an invasive-species control proposal.
What the selected record shows. The required evidence is incomplete for this invasive species case. The items below identify what must be obtained or reconciled.
The page does not select a safe control treatment or establish ecological effects.
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: Species; occupied area; spread; ecological impact; treatment options; uncertainty.
Compare stated visitor demand with the supplied capacity assumption.
What the selected record shows. Usable capacity minus demand: -15 visitors/day. 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.
An example capacity is not an approved ecological carrying capacity.
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: Visitor counts; facilities; sensitive sites; approved limits; seasonal conditions.
Check the records needed for a wildlife-research permit referral.
What the selected record shows. The required evidence is incomplete for this research permissions case. The items below identify what must be obtained or reconciled.
The example issues no permit or access authority.
Other required records: Research proposal; species; methods; site; ethics; requested collections; conditions.
Check audience, sensitivity and source permissions before a wildlife-data referral.
What the selected record shows. The required evidence is incomplete for this sensitive information case. The items below identify what must be obtained or reconciled.
A complete checklist does not authorise disclosure of sensitive locations.
Other required records: Species sensitivity; coordinates; purpose; rights; aggregation policy; approval.
Compare habitat-restoration choices using the documented ecological and rights evidence.
A budget balance does not establish an appropriate restoration design.
Other required records: Habitat condition; native species; hydrology; land rights; costs; threats.
Compare recorded encounters per survey hour under matching protocols.
What the selected record shows. Observed encounter rate: 1.556 encounters/hour. Review effort, detection and count comparability.
Next step. Review effort, detection and count comparability. Prepare biodiversity comparison in the prototype creates a visible, downloadable draft. It is unassigned and not sent.
An encounter rate is not a wildlife population estimate.
Observed encounter rate = recorded encounters / positive survey hours. Compare only the same species, area, season, protocol and count definition. This is a simple survey index, not a population estimate or detection-corrected trend.
Observed richness is not population size or occupancy. Comparable effort alone does not remove detection bias or establish a biodiversity trend. Repeated sightings may include the same individual. Detection, effort and protocol changes can alter this index without a population change.
Other required records: Species; repeat surveys; detection; effort; season; estimation method.
Compare recorded wildlife mortality between matching reporting periods.
What the selected record shows. Difference: 5 cases. Refer the increased reports; no outbreak or spatial cluster is established.
Next step. Refer the increased reports; no outbreak or spatial cluster is established. Prepare investigation brief in the prototype creates a visible, downloadable draft. It is unassigned and not sent.
A change in counts does not diagnose a cause or establish a spatial cluster.
Later/comparison value minus Comparable reference value. Relative change = 100 × difference / Comparable reference value when the earlier value is positive.
Other required records: Species; mortality count; location; dates; sample evidence; veterinary referral.
Compare usable rescue resources with the stated workload and service window.
What the selected record shows. Usable capacity minus demand: -15 team hours. Review capacity shortfall.
Capacity does not establish competence, deployment authority or animal safety.
Other required records: Rescue cases; required skills; vehicles; facilities; travel; available capacity.
Find groups without confirmed community-support coverage.
What the selected record shows. 30 households are known to be uncovered; 5 have unknown coverage. 65% are confirmed covered.
Next step. Check the records behind the uncovered and unknown groups. Prepare coverage follow-up in the prototype creates a visible, downloadable draft. It is unassigned and not sent.
Recorded support is not evidence of conflict reduction or agreement.
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: Affected community frame; outreach; verified uptake; conflict incidents; period.
Compare reported outcomes and adverse effects across the supplied periods.
Verified published formula · Difference-in-differences arithmetic
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.
A difference in changes does not establish a causal conservation effect.
(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: Intervention; baseline condition; follow-up; comparison sites; pressures; uncertainty.
World Bank · Impact Evaluation in Practice Second EditionInstitution 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.
Compare habitat and protected-area classification meanings and source references.
What the selected record shows. The required evidence is incomplete for this protected-area records case. The items below identify what must be obtained or reconciled.
Matching labels do not establish the same boundary or legal protection.
Other required records: Boundary source; legal edition; area name; habitat classification; custodian.
Check which existing source fields can supply the decision inputs.
Existing form reference: d5264d82f6a69e87
Existing form reference: 820f4db29f0a3679
Existing form reference: 5d4e57af1e6712f1
Existing form reference: 388c3f6a1fffaa83
Your institution has its own document and image library. Use the same library for reports, photos and other evidence.
Open this screen for Department of Wildlife ConservationSee the presentation example
Files added in the prototype stay in this browser. Public sharing is an access preview. Existing public reference links already work online.
Data structure keeps the existing source tree, records, charts and map. Manage structure adds a place to propose changes to definitions.
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.
User management shows example profiles for each institution. People and Roles and access let you review the proposed account screens.
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.
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.
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.