[ SEATS, PROVIDERS, AND SCHOOL CONTROLS ]
Plan a school pilot
Talk through a bounded rollout before expanding school access.
Email the Nexus team
Tell us about your school, planned student count, and the task you want to support.
Need help using Nexus?
Find what to include when reporting a sign-in, model, or file problem.
Bring the school context
Share the expected active-student count, classes, provider preferences, and the learning routines the school wants to support.
Review the operating model
Discuss platform seats, separate provider spend, teacher review scope, privacy, identity, and support ownership.
Define the pilot
Choose the group, dates, spending limit, success questions, and stop condition. A planning conversation does not create a purchase.
Plan the first class before the whole school
Describe the learning task, the number of participating students, and the teachers responsible for the pilot. Choose a task with an observable result, such as explaining a mathematical step or revising an argument using evidence.
Questions we will work through
A rollout conversation should cover sign-in, class membership, allowed models, teacher review, source permissions, and provider billing. Decide who can change each setting and how the school will respond to a reported problem.
- Which students and teachers will participate?
- What help is allowed for the first assignment?
- Who owns the provider account and budget?
- What independent work will show whether the pilot helped?
What to bring to the walkthrough
Bring a representative assignment and an approved example document. Use synthetic or redacted student examples. We can use the walkthrough to agree on the school workflow and the remaining setup steps before a paid rollout.