PUBLIC ALPHA • AGGREGATE-FIRST • EVIDENCE OVER VANITY

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.

1 • PROGRAMME DEFINITION

What are you trying to change?

Do not enter participant names, phone numbers, medical details or other sensitive records here. This public alpha is for programme-level aggregate thinking and reporting practice.
2 • AGGREGATE EVIDENCE

Delivery and outcome counts

3 • TRANSPARENT METRICS

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.

0/100
Reach0%enrolled ÷ target
Completion0%completed ÷ enrolled
Activity delivery0%delivered ÷ planned
Outcome rate0%achieved ÷ measured

Recommended evidence improvements

1Define a participant/reach target before reporting progress against reach.
2Add at least one measurable outcome indicator; activity counts alone do not demonstrate change.

Impact claim discipline

Output: what the programme delivered.
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.

NEXT PLATFORM LAYER

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.