Mock — B2 Director setup

Mock of B2 — Director sets up the center

Sources: spec §3.2 B2, prd.md §5 Journey 2, PRD §3.3 design principles (admin-not-technical, forgiving-and-resumable, gentle-over-strict).

Invariants enforced in this screen: go-live threshold = ≥1 classroom only (AC5); forgiving-and-resumable (§5.2) — every step saves on blur/advance; gentle-over-strict — pending items are surfaced, never gating.

Inference flags:

inference: step ordering and navigation UI — spec names 7 steps and says all save automatically and can be skipped/resumed (§3.2 behavior), but does not specify whether they are presented as a linear wizard with a sidebar, tabs, or pickable tiles. Mock uses a linear wizard with a sidebar of step status.
inference: CSV columns and layout — spec says "columns: name, DOB, classroom" (§3.2 step 4). Bulk import screen shows those three.
inference: QR code visual — spec §3.2 step 7 says "optional printable codes per classroom" linking to B7 flow scoped to classroom. Rendered here as a labeled box.
[exact microcopy on consent options "all / solo_only / none"] — spec provides the enum values, not the user-facing labels

B2 — Director sets up the center

Wizard shell

Linear sidebar of steps; each step is resumable and skippable. Any step is reachable out of order after initial completion (AC3).

Step	Status	Required for go-live?
1 — Center info	done	name only
2 — Classrooms	done (≥1)	yes — single required step
3 — Add teachers	skipped	no
4 — Enroll children	skipped	no
5 — Photo consent	n/a (no children yet)	no
6 — Invite parents	skipped	no (post-live-friendly, §3.2 step 6)
7 — QR codes	skipped	no

AC5: a director can go from access-code redemption to Daycare.status = live by entering only center name + one classroom name.

Step 4 — Enroll children (three paths, each first-class)

Spec §3.2 step 4 names three paths. All three are surfaced equally; none is primary.

Path A — One at a time

Child name

Age group

Classroom

Path B — Bulk CSV import

CSV columns: name, DOB, classroom. Preview-with-errors screen surfaces any duplicates/malformed rows before any row is committed (§3.2 error cases).

CSV file

Path C — Teacher-initiated

Director does not enter each child personally; teachers add children from their classroom view. See B2.1.

Duplicate detection: matching (name, DOB, classroom) triples warn before saving and offer merge-or-create. In bulk CSV, duplicates are flagged on the preview screen; no partial import (§3.2 error cases, §4.4 Child invariants).

Step 5 — Photo consent (per child)

Child	Consent level
[child A]	all (default)
[child B]	solo_only
[child C]	none

[user-facing labels for "all" / "solo_only" / "none" — not specified in spec; enum values shown]

Can be updated any time after setup (§3.2 step 5).

Step 6 — Invite parents

Per child: one or more guardians via email or phone. Post-live-friendly — any subset now, rest later, or skip entirely. Photos captured before a parent subscribes are held retroactively up to the 90-day retention window (§3.2 step 6, I-Retention).

Child

Guardian email/phone

Send invite

Setup complete — pending items on dashboard

Once ≥1 classroom exists, the daycare is live. Dashboard shows what's done and what's still pending with gentle prompts (§3.2 postconditions, §5.2 gentle-over-strict).

Pending: no teachers invited
Pending: no children enrolled
Pending: no parents invited
No red badges, no escalating alerts (§5.2).

See B8 — Admin dashboard.