For schools and institutions

The institution console is not built yet. Capabilities on this page are planned; no trial environment is available yet.

Institution data is strongly isolated so a teacher cannot see students from another school.

Institutions read only limited projections (roster, attendance, learning aggregates, safety events) and do not hold identifying child detail.

School and bus route status is planned to flow through guardian-consented projections.

The path from enquiry to pilot is shown from the buyer, staff and guardian points of view. No free trial is promised.

1. 1
   Buyer: send an enquiry

   Why: to check fit and requirements. How: send scale and goals through the form. You get: an intake record and a follow-up. We cannot: contract instantly, fix a price, or claim certifications.

2. 2
   Staff: agree the pilot scope

   Why: to keep it workable in a classroom. How: agree on classes, period and evaluation. You get: a pilot plan. We cannot: guarantee production rollout or hand over data externally.

3. 3
   Guardian: confirm participation and consent

   Why: so children take part safely. How: review purpose, scope and how to withdraw, then consent. You get: the choice to take part or not. We do not: enrol without consent or use data for other purposes.

All institution capabilities are planned. Nothing here claims a compliance certification.

• Institution console (web)Planned
• Roster and classesPlanned
• AttendancePlanned
• Aggregate reportsPlanned
• Single sign-onPlanned
• Institution enquiry intakeAvailable