Requirement status

Analytics shall distinguish reach, enrollment, participation, learning evidence, cohort engagement, retention, and parent feedback.

Acceptance: Metrics are not collapsed into one vanity score.

Reach, enrollment, participation, evidence, cohorts, retention and parent feedback are reported separately.

The primary family engagement funnel shall include invited/reached → household enrolled → child activated → first mission → repeat mission → 30/90-day return → cohort participation where applicable.

Acceptance: CU dashboard shows denominator at each stage.

Funnel from reached to cohort participation with each stage's denominator.

Learning reporting shall focus on skill practice and transfer evidence, not only quiz scores.

Acceptance: Reports include the evidence class and context.

Learning reporting by evidence class and skill, not quiz scores.

The product shall support baseline/follow-up assessment using approved instruments or clearly labeled internal measures.

Acceptance: Internal measures are not described as validated unless they are.

Baseline/follow-up assessments not implemented; reports state internal measures are not validated.

The platform shall permit experimental/pilot cohorts to be labeled separately from validated programs.

Acceptance: Reports show pilot status.

Pilot tenants, items and labs are labeled; reports don't yet segment pilot cohorts.

The platform shall track curriculum performance by version.

Acceptance: A revised mission can be compared without mixing versions silently.

Evidence records store curriculum version; version comparison views not built.

Curriculum creators shall receive aggregated feedback on drop-off, confusing steps, parent comments, facilitator flags, and transfer performance.

Acceptance: Improvement loop is visible in Creator Studio.

Library shows facilitator flags and field notes per item; drop-off and transfer analytics not built.

The CU shall be able to report community impact without exposing individual child data.

Acceptance: Exports use aggregate counts and suppression where needed.

Aggregate counts with suppression under 10.

Product referrals, if enabled, shall be measured separately and only from adult-initiated actions.

Acceptance: No child mission response counts as a sales lead.

Referrals are counted only from adult requests and reported separately.

The platform shall support annual renewal reporting summarizing reach, engagement, cohorts, curriculum used, and program recommendations.

Acceptance: CU can use report in budget/board review.

The board report summarizes reach, participation, cohorts, curriculum in use and renewal notes. Counts are aggregates with suppression under 10. Efficacy is not evaluated, and the file is not advice.

Analytics shall clearly label demo/synthetic data in demonstrations.

Acceptance: No demo is mistaken for achieved results.

Every synthetic metric is labeled demo data; live demo counts are shown separately.

The platform shall support custom success goals per CU while retaining standard metric definitions.

Acceptance: CU can choose focus without redefining core measures.

Custom success goals per CU not implemented.