Scope
Select grades, subjects, participating teachers, approximate student count, duration, and the learning questions the pilot should answer.
Start controlled. Define success. Expand only when the evidence supports it.
Splash pilots should be implemented as instructional programs with a clear scope, not as a district-wide switch that simply turns on more AI access.
A practical path from interest to pilot review.
Review
Review privacy, safety, security, accessibility, data-handling expectations, and any school procurement requirements before student access.
Prepare teachers
Introduce the AI literacy framework, Glass Box, assignment model, verification workflow, and classroom expectations.
Design assignments
Choose a small number of curriculum-aligned Story Studio activities with explicit learning objectives and approved information sources.
Run the pilot
Use the platform in real classes while tracking completion, verification behavior, teacher workload, safety interventions, and student reflection.
Review evidence
Decide whether to expand, revise, or stop based on learning value, teacher usability, safety, privacy, and implementation results.
RECOMMENDED FIRST PILOT
Small enough to learn. Large enough to reveal real classroom problems.
- 5–10 participating teachers
- Approximately 100–250 students
- Grades 6–8 as the initial validation band
- 4–6 weeks
- Approximately three learning projects per student
- Story Studio as the first creation environment
- Glass Box inspection, claim verification, and reflection required
PILOT READINESS
Before students enter
Learning objectivesDefined
Teacher orientationComplete
Approved assignmentsReady
Privacy / safety reviewComplete
Support pathKnown
Success measuresDefined
Clear ownership prevents implementation gaps.
Splash
Product onboarding, implementation guidance, support, safety/technical documentation appropriate to pilot stage, and pilot reporting.
School leadership
Approve scope, assign participating staff, complete institutional review, establish local policies, and define escalation contacts.
Teachers
Set learning objectives, choose assignments and sources, guide student use, review learning evidence, and provide classroom feedback.
TECHNICAL IMPLEMENTATION ROADMAP
Institutional integrations come after the core learning loop works.
For early pilots, keep setup deliberately narrow. Broader deployment can later add enterprise identity, rostering, administrative policy, retention, and reporting capabilities.
Teacher accounts
Classroom roster
Assignments
Approved sources
Student projects
Learning evidence
Future SSO
Future Clever/ClassLink
Future institution policy
Future district reporting
The final deliverable should make the next decision easier.
Participation summaryProject completionVerification behaviorTeacher feedbackAggregate safety resultsUsage economicsObserved implementation issuesRecommendation: expand / revise / stop