Requirement status

Innorve owners shall be able to manage institutions, subscriptions, entitlements, cohort credits, curriculum access, facilitators, and support status.

Acceptance: Commercial operations are visible in one admin workspace.

Admin workspace lists institutions, provisions a setup tenant, and lets an Innorve admin draft, review, and apply entitlement changes with an audit trail. Facilitator assignment is still not edited here.

The platform shall support institution-level configuration without duplicating curriculum for every CU.

Acceptance: One approved curriculum item can be licensed to many tenants with controlled overrides.

One curriculum item is licensed to many tenants with controlled overrides (enable, feature, sponsor note).

The platform shall support program packages that bundle app access, curriculum, marketing, reporting, and cohort entitlements.

Acceptance: Sales can offer a simple package rather than many separate SKUs.

Standard package bundles app, curriculum, marketing, reporting and Money Lab seats.

Custom curriculum, dedicated cohorts, event kits, and specialized branding may be optional add-ons.

Acceptance: Add-ons do not break the core turnkey experience.

Optional event-kit and dedicated white-label add-ons can be scheduled without removing core package access. Custom curriculum stays unavailable so it cannot bypass rights review.

The platform shall support institution renewal review with usage and outcome summary.

Acceptance: Account owner can generate renewal packet.

An Innorve admin can open an aggregate renewal packet with reach, engagement, cohorts, licensed curriculum, definitions, suppression under 10, and “Efficacy: not evaluated.”

The product shall support household-based rather than child-by-child billing where contractually preferred.

Acceptance: Commercial model does not penalize larger families.

The contract view states one annual subscription billed per household, with no per-child fees. Larger families are not charged more.

The platform shall support free pilot/design-partner programs while clearly distinguishing them from standard contracts.

Acceptance: Pilot entitlements and dates are explicit.

Lakeshore is a labeled design-partner pilot with explicit dates and entitlements.

The product shall provide customer-success tasks and onboarding milestones for each CU.

Acceptance: No institution is “live” without confirmed brand, consent flow, support contacts, and program owner.

Customer success confirms onboarding milestones in admin; going live is refused (and audited) unless brand, consent flow, support contacts and program owner are confirmed and the contacts and owner actually exist. Required items can't be reopened while live. Tested.

The product shall support institution offboarding and data disposition.

Acceptance: CU and Innorve have clear end-of-contract process.

Offboarding is planned and confirmed separately. Confirmation shuts off access. Deletion is a second confirmation and stays held under the recorded retention policy (D-01); it does not claim the data is gone.

The platform shall maintain a release/readiness checklist for new curriculum collections and program capabilities.

Acceptance: Marketing cannot sell a feature still marked draft.

Release/readiness checklist for new collections and capabilities not built (this requirements page is the interim tracker).