Sprout for schools
We are developing class codes, shared focus periods and a teacher overview.
Example class
Planned teacher overview
| Pupil | Status | Location |
|---|---|---|
| Pupil 1 | Working | School area A |
| Pupil 2 | Needs help | School area B |
| Pupil 3 | Task completed | School area A |
Names, statuses and areas are fictional. No pupils are connected.
Available today
The current School web test can save lesson plans and class agreements locally in the browser. Class codes, pupil connections, location and access controls are planned.
Class codes
The plan is for teachers to create a class code that pupils use to join a teaching session. Teachers should be able to see who has joined and follow pupils’ task status.
The web test does not create class codes, pupil accounts or shared sessions.
Focus and contact
We want to support agreed focus periods with access to the apps and websites needed for teaching. The web test does not change Wi-Fi, mobile data or other apps.
The aim is to keep important calls and SMS possible during focus periods. This depends on the platform and the school’s setup. The web test does not handle calls or SMS, and flight mode is not the planned solution.
Status and location
The teacher overview is planned to show both task status and physical location in the agreed school setting. Location must be a separate, visible school opt-in with a defined purpose during teaching.
Pupils should be able to see when sharing is active. The school’s requirements and boundaries must be clarified before the feature is used. The web test shows only fictional areas and collects no position.
School is a separate professional product and is not part of the ten family apps.