# Make the school launch decision

Category: Setup and support

Before you start: confirm the correct school and role. Use approved source records; perform live changes only within your assigned authority.

Record each gate separately:

- [ ] Data starting point selected and saved for the named school
- [ ] Import package accepted and imported data validated, or clean-start state explicitly confirmed
- [ ] Latest school-data review is confirmed and has not become stale
- [ ] Every staff member expected to sign in has a reconciled application user, usable password-login Auth account, approved application role, and exact school grant; every active Prisma user with potential school access and any outstanding application/device session has been checked against the approved roster regardless of Auth login state; older untracked cookies have been invalidated or their expiry proved; intentionally uninvited staff and access exceptions are named, owned, and held off
- [ ] Director access tested
- [ ] Teacher access and rosters tested
- [ ] Every expected parent/guardian and authorized-pickup account has usable password/MFA sign-in; every existing application account, role, family link, and outstanding session with potential school-family access is reconciled against the approved guardian/pickup roster; removed or unexpected access is denied before parent/pickup-access GO
- [ ] Parent invitations approved or intentionally held off
- [ ] Parent family-only visibility tested
- [ ] Kiosk approved or intentionally held off
- [ ] Tuition, balances, credits, and first-cycle preview approved
- [ ] School payout status shows charges and payouts ready, or live payments are intentionally held off
- [ ] Live payments approved or intentionally held off
- [ ] Previous-system/BEE Suite billing boundary recorded with no overlap, or clean start recorded
- [ ] First-week support and reconciliation owners assigned
- [ ] Previous-system retirement approved or intentionally held off, or not applicable for a clean start

Final decision: **GO / NO-GO**

Record:

- School / decision date and time:
- Modules approved for GO / modules held off:
- Bidirectional staff/account and application-session reconciliation evidence, intentionally uninvited staff, unexpected access, and blockers/owners:
- Bidirectional guardian/authorized-pickup account, role, family-link, and session reconciliation evidence, unexpected access, and blockers/owners:
- Last previous-system tuition cycle / first BEE Suite tuition cycle, or clean-start note:
- Owner / director / billing / implementation approvers:
- Open exceptions, owner, due date, and exact retest:

`HELD OFF` is not `PASS`. Technical readiness is not approval to send invitations, activate the kiosk, bill families, process payments, or retire a previous system.

## Verify the result

Each required gate has a dated owner decision.

## If something goes wrong

HELD OFF is not PASS; technical readiness does not authorize business activation. Wait for pending actions; reopen the record before retrying an uncertain save or send.

Source: sources/SCHOOL_TRANSITION_SETUP_AND_CUTOVER_SOP.md — 10. School-Specific GO Or NO-GO Record. Prepared October 8, 2026. SOP snapshot e06ad8d5; current source corrections are identified above. Written procedure; not a recording of a completed live action.