Requirement status

A credit union shall be able to launch a co-branded program without a core-banking integration.

Acceptance: Hosted branded landing page, QR code, and member invitation mechanism are sufficient for launch.

Hosted landing page, QR code and access-code enrollment are sufficient to launch.

The CU shall have a self-service brand setup for logo, colors, program name, welcome message, local resources, and approved campaign imagery.

Acceptance: Preview shows member, parent, and cohort surfaces before publishing.

Self-service program name, colors and welcome message with a live member/parent/kid preview. Logo upload, local resources editing and campaign imagery not yet.

The CU shall be able to choose which age bands and curriculum collections are offered.

Acceptance: Admin can enable/disable collections without editing lesson content.

Toggle age bands and collections without editing lesson content.

The CU shall have a pre-approved starter program configuration that can launch with minimal decisions.

Acceptance: Default setup includes missions, parent hub, marketing kit, and at least one cohort offering.

An Innorve admin provisions a setup tenant from the approved standard package: family app, parent hub, licensed mission collections, campaign kit, aggregate reporting, and a cohort seat offering. Curriculum rows are referenced, not copied. The tenant is not live.

The CU shall be able to invite families using QR codes, public member links, access codes, or optional member-directed invitations.

Acceptance: No member list upload is required for standard launch.

QR codes, public link and access code (member-directed invitations reuse the link); no member list upload.

The CU shall be able to sponsor cohort seats and set eligibility windows and seat limits.

Acceptance: Parent booking reflects sponsor availability and waitlist status.

The program owner sets the eligibility window and seats per household on Sponsored seats. Who qualifies is enrolment only. A parent can't book a sponsored seat outside the window, or more children than the household limit on that session.

The CU shall be able to request custom curriculum in natural language without directly publishing unreviewed child content.

Acceptance: Custom request enters Innorve review workflow.

Natural-language custom requests land in the Studio inbox and go through Innorve review; the CU cannot publish.

The CU shall have a dashboard for activation, enrollment, mission starts, repeat participation, cohort bookings/attendance, age-band mix, and skill-practice aggregates.

Acceptance: Dashboard contains definitions and denominators.

Dashboard with activation funnel, denominators, definitions, age-band mix, skill aggregates and cohorts (synthetic baseline + live demo counts).

The CU shall not receive private child reflections, raw family financial details, or unapproved child-level behavioral profiles.

Acceptance: Institution analytics are aggregate or operationally necessary and policy-approved.

CU surfaces read aggregates only; no reflections, answers or child profiles.

The CU shall be able to download a board/community-impact report with branding and methodology notes.

Acceptance: Report differentiates reach, participation, learning evidence, and optional referrals.

Branded board report with a page-1 preview and a downloadable PDF. Methodology notes separate reach, participation, learning evidence and adult-initiated referrals.

The CU shall receive ready-to-use email, SMS, social, branch, Youth Month, school/community, and event campaign templates.

Acceptance: Campaign kit can be exported or copied without a designer.

Email, SMS, social, branch flyer, poster, school/community flyer, Youth Month and event templates; copy or download the kit.

The CU shall have staff talking points explaining the product in under 60 seconds.

Acceptance: A branch/community employee can explain member value without financial-advice claims.

Staff talking points at /cu/talking-points: four lines under a minute, play money labelled, no child account, parents don't share finances, and the credit union sees totals only. Four don't-say lines block an outcome claim, an NCUA claim, opening an account first, and seeing how a child spends. Owner and marketing can read the page; other roles are refused.

The CU shall be able to promote parent-facing products/resources only through clearly separated, adult-directed resource cards.

Acceptance: Educational mission content remains neutral and does not change based on product conversion goals.

Resource cards are adult-directed and visually separated; mission content never changes with product goals.

The CU shall have a standard vendor due-diligence package available before contracting.

Acceptance: Package includes data-flow overview, privacy practices, security controls, subprocessors, incident process, accessibility statement, insurance/certifications if applicable, and product boundaries.

Vendor due-diligence pack at /cu/due-diligence lists the nine standard items. Drafts are marked DRAFT and need legal and security sign-off. Certifications and insurance are listed only when held (none are). Download all reports that no approved document source exists and does not invent a ZIP. Owner and compliance can read it; other roles are refused.

The product shall never imply that it is NCUA-approved or NCUA-certified.

Acceptance: Marketing/legal review blocks such language.

NCUA disclaimers on every surface; brand editor rejects “NCUA approved/certified” copy.

The CU shall have a designated program owner and optional marketing, analyst, compliance/reviewer, and read-only executive roles.

Acceptance: Permissions match assigned responsibilities.

Program owner invites staff at /cu/team, assigns marketing, analyst, compliance or read-only executive, and can change, resend or revoke. The Brand / Campaigns / Reports / Seats / Review matrix is enforced on every CU route. Owner assignment is refused. No child data.

The CU shall be able to configure local events, branch workshops, and community partnerships in the family calendar.

Acceptance: Events can be offered alongside Innorve cohorts.

Program owner configures local events at /cu/events (5p). A published event is a lab session, so it appears beside Innorve Money Labs in the family calendar. No child records.

The CU shall have one annual contract/subscription with transparent entitlements rather than unpredictable child-level surprise fees.

Acceptance: Admin can see current entitlements and sponsored cohort balance.

The program owner sees the annual contract at /cu/contract: households enrolled of the included cap, sponsored seats used, custom requests used of the yearly allowance, contract dates, the package checklist and the renewal note. Other roles are refused. The page does not edit the contract.

The standard commercial package shall not require the CU to procure separate content, facilitators, or marketing materials to become usable.

Acceptance: Program is turnkey from day one.

Content, facilitators, Money Labs and marketing materials are included in the standard package.

The program shall support an optional dedicated white-label presentation for large institutions without making it the default implementation requirement.

Acceptance: Standard co-branded launch remains available.

Co-branded launch works; a dedicated white-label presentation (custom domain, no Innorve chrome) is not built.