# MetaPet Schools Pilot Runbook

Use this as the operating sheet for the first constrained school pilot. Recommended default: start with `1 school`, `1 class`, and `1 teacher` before any broader expansion conversation.

## Roles

| Role | Main responsibility |
| --- | --- |
| Pilot lead | Owns timeline, signoff, and final recommendation |
| Classroom teacher | Delivers sessions, keeps fidelity notes, logs incidents |
| ICT/privacy reviewer | Confirms privacy, route boundary, and deletion posture |
| Family contact | Manages parent/carer communication and participation questions |
| Evidence owner | Collects feedback, interview notes, and end-of-pilot summary |

## Timeline

### Week 0: Acceptance gate

- Complete browser/network inspection
- Run the teacher dry run
- Complete ICT/privacy review
- Complete parent readability review
- Confirm the family participation process

### Week 1: Launch prep

- Confirm the class, timetable slot, and device setup
- Send family communication
- Confirm aliases and teacher roles
- Capture the `before` side of the pre/post measure

### Fortnight 1: Controlled classroom delivery

- Run the agreed lesson sequence
- Record any deviations in implementation fidelity notes
- Log any incident on the same day
- Keep evidence light and adult-controlled

### End of fortnight 1: Stop/go review

- Review setup burden, route boundary, family clarity, and any incident or workload issue
- Decide whether to continue the same single-class pilot, continue with revisions, or stop
- Do not expand to another class or school at this point

### Remaining pilot window: Continue only if approved

- Finish the agreed lesson sequence with the same class and teacher
- Keep evidence light, adult-controlled, and consistent with the governance pack

### Final week: Close and review

- Capture the `after` side of the pre/post measure
- Collect student, teacher, and parent/carer feedback
- Review incident log and fidelity notes
- Complete the end-of-pilot summary
- Delete local classroom data on pilot close unless the school has a documented reason to retain approved exported evidence separately

## Weekly Rhythm

- `Before first lesson:` check participation list, device, and lesson queue
- `After each lesson:` note fidelity issues and any incident
- `Weekly:` review workload, clarity, and any school-facing confusion
- `End of fortnight 1:` make a stop/go recommendation for continued single-class use
- `End of pilot:` make a go/no-go recommendation for a wider rollout

## Stop Conditions

Pause or stop the pilot if any of the following occurs:

- The school profile exposes non-school product surfaces
- Teachers report unacceptable workload or setup burden
- Families or staff cannot distinguish the school deployment from the broader product
- A privacy, safeguarding, or participation issue remains unresolved