Track what a programme delivered—and what actually changed.
Define a programme objective, enter aggregate delivery and outcome counts, then generate transparent rates and an evidence-readiness summary. The public alpha intentionally avoids participant names and sensitive personal records.
Delivery and outcome counts
Starting • evidence readiness 0/100
The score checks whether basic denominators, delivery counts and outcome measurement are present. It does not validate whether the programme caused the outcome.
Recommended evidence improvements
Impact claim discipline
Outcome: what changed for participants or the target system.
Impact: a stronger claim that usually requires evidence about causality, contribution and alternative explanations.
This alpha deliberately avoids turning activity counts into an automatic “impact” claim.
From reporting burden to learning loop.
A production Community Impact OS can add organization workspaces, surveys, consent-aware participant records, programme cohorts, outcome dashboards and funder reports. Those features should inherit tenant isolation, role-based access, retention rules and audit controls from the same shared platform foundation.