The right questions before a school pilot.

Using the public preview

The example library and workload planner do not require student information or a school account. Question edits and planner inputs remain in your browser page. The contact tool prepares an email that you review and send yourself.

Do not enter student names, live assessment responses or confidential school material into an enquiry. See website privacy information and optional analytics choices.

What to establish for a pilot

1. Data handling: what information is required, where it is processed, who receives it, and how it is retained, exported and deleted.
2. Access: how accounts are created, how school roles are separated, and which authentication controls are actually enabled.
3. AI use: which tasks use AI, which providers are involved, and how teachers review the outputs.
4. Accessibility: whether the required tasks work with the devices and assistive technology your students use.
5. Integrations: the exact system, version, data direction and permissions required.
6. Support: who responds to problems, how incidents are communicated, and what is agreed at the end of the pilot.

Ask for the actual arrangements

The wider school application is in development. This page is a discussion checklist; it is not a statement that production hosting, security certification, school integrations or support service levels have been established.

Start with the school integration checklist or contact the team about your requirements.