Roosevelt pilot plan

Oakland USD · SEIS companion · one caseload first · demo sandbox today, MOU + FERPA before production

Demo walkthrough Meeting script Dev Hub IEP PDF import Student login Monitor Hub Funding

Vision

Turn what is in the IEP into what the student sees every day — goals, accommodations, assignments, and behavior supports in one dashboard. Staff set it up once; the student gets a clear “what do I do now?” view.

Demo flow: empty roster → live IEP PDF import in the meeting → teacher applies assignment/supports → student opens dashboard and starts work.

Four phases

1 · Discovery — District demo on sandbox (:13002). No live SEIS data. Preview vs Apply on AI. Leadership sees funding + ops story.

2 · Pilot setup — Signed MOU, FERPA one-pager, one case manager caseload (Roosevelt SEIS). Import or sync roster scope. Train co-teachers on Monitor Hub + quick-log.

3 · Classroom use — Students on enhanced dashboard daily; baselines + worksheets; behavior zones + incidents; staff growth-note approve flow.

4 · Scale & measure — Grafana uptime/adoption slide; caseload expansion only after metrics + IT sign-off. Production host separate from demo Mongo.

Timeline (~10 weeks)

Week	Focus
1	District demo + pilot plan review; IT sandbox vs production diagram
2	MOU draft; caseload list; FERPA / data handling one-pager
3–4	IEP import for pilot students; Dev Hub training; student login rollout
5–7	Daily use: assignments, baselines, behavior logging, Monitor Hub
8–9	Mid-pilot check: engagement, staff time saved, incident workflow
10	Report: adopt / expand / pause; production Phase 1 if approved

Success metrics

Adoption — % of pilot students logging in weekly; assignments started vs assigned
IEP workflow — time from PDF/import to live dashboard; accommodations visible on student card
Engagement — worksheet completion, baseline completion, student zone check-ins
Behavior — incidents logged in-app; staff response time on high-severity alerts
Ops — demo/school stack uptime; no cross-contamination of demo vs production DB

Roles

Role	Responsibility
Case manager (SPED)	Roster, IEP import, supports, Monitor Hub, growth-note approve
Gen-ed co-teachers	Quick-log behavior, view student card, assign featured work
Students	Login, dashboard, zones, assignments, optional peer chat (demo)
District IT	Sandbox isolation, SSO path (later), backup/MOU compliance
Leadership	Scope, funding narrative, pilot decision at week 10

2-minute demo script (student + teacher)

Open Dev Hub — point at Demo · sandbox badge
Show IEP import or existing demo student (e.g. Anelise Castro)
Open Monitor Hub — live roster, quick-log, Send High-Five
Student tab: enhanced dashboard — stealth strip, zone, progress ring
Optional: full meeting script for leadership close

How OUSD adopts new tools

There is no district “pitch night.” Public examples (Derivita, TeachFX on OUSD Legistar) follow: department sponsor → sandbox or no-cost pilot → board-ratified services agreement. PulsePoint Phase 1 matches that — one caseload, MOU, isolated data.

Step	PulsePoint
1 · Champion	SPED leadership review (Cary) — demo + written answers
2 · Sandbox	District demo on `:13002` — empty roster, no SEIS leak
3 · Pilot MOU	FERPA one-pager + scoped caseload · ousd-mou.html
4 · Board path	Department sponsors agreement after pilot metrics (week 10 decision)

Parallel long-game: OUSD Community Partner Inquiry. Details: docs/OUSD-DISTRICT-PROCESS.md

FERPA & scope

Demo stack (:13002) uses isolated pulsepoint_dev_db — start empty; no bulk Roosevelt seed in demo
School stack (:8889) uses local production DB for Roosevelt classroom use
SEIS remains system of record; PulsePoint is a daily companion, not a replacement
Production pilot requires MOU, parent notice as directed by district counsel, and scoped caseload

Print this page for leadership leave-behind · Related: demo instructions · enhancement map (repo docs)