Schools and Trusts Onboarding

Bringing a new school or trust on board.

What it does

This guide explains the public onboarding and deployment-readiness route for schools, MATs, and trusts considering a senco pilot. It is designed for stakeholders who need rollout guidance before signing in and before committing to a wider deployment.

Where to find it

  • Schools and trusts page: /schools-and-trusts
  • Printable pilot checklist: /schools-and-trusts/checklist
  • Trust and auditability page: /trust
  • Comparison page: /compare

Step by step

  1. Open /schools-and-trusts to review the phased rollout guidance.
  2. Read the three readiness stages:
  • workflow fit
  • operational readiness
  • pilot rollout
  1. Check the readiness lists for schools and trusts.
  2. Open /schools-and-trusts/checklist if you need a printable readiness worksheet for a pilot meeting.
  3. On the checklist page, use Print checklist to print or save a copy.
  4. Review the onboarding artefacts:
  • before the pilot starts
  • during the first review cycle
  • before expanding rollout
  1. Review operational proof and publishing boundaries so stakeholders know which claims are implemented now and which should wait for formal evidence.
  2. Use the linked public routes if you need supporting proof:
  • /trust for governance posture
  • /compare for alternatives comparison
  • /for-sencos for the SENCO workflow view
  1. Use Start pilot workspace if the team is ready to begin a controlled pilot.

What each screen shows

/schools-and-trusts

  • A public overview of what should be agreed before a senco pilot begins.
  • A phased rollout section covering discovery, operational readiness, and controlled pilot launch.
  • Readiness checklists split between school-level and trust-level concerns.
  • Onboarding artefacts to prepare before pilot launch, during the first review cycle, and before rollout expansion.
  • Operational proof cards covering access and roles, governed evidence trails, retention/operations, and reasoning governance.
  • Publishing-boundary cards clarifying what senco can safely claim now and what should not be claimed yet.
  • FAQ content and links to related public proof pages.
  • Links to the printable pilot checklist for readiness meetings.

/schools-and-trusts/checklist

  • A printable school/trust readiness worksheet.
  • Checklist sections for pilot ownership, workflow scope, governance checks, and readiness evidence.
  • A suggested readiness meeting agenda.
  • Operational proof and public-claim boundaries carried through from the wider rollout page.

/trust

  • The governance and auditability posture that supports the rollout conversation.
  • Public assurances tied to audit trails, retention controls, and non-diagnostic use.

/compare

  • A side-by-side explanation of why senco differs from spreadsheets, generic chatbots, and diagnosis-style classifiers.

Tips

  • Use /schools-and-trusts for rollout planning discussions rather than product feature demos.
  • Use /trust when safeguarding, governance, or procurement stakeholders need public assurance.
  • Use /compare when stakeholders want to understand why a governed workflow is different from a generic AI or spreadsheet approach.
  • Avoid promising a fixed onboarding timeline until the school or trust has confirmed pilot scope, roles, retention expectations, and governance review needs.
  • Treat customer outcomes, quantified impact, and external certification claims as future proof points unless formal evidence exists.
  • Keep the printed checklist with local meeting notes so pilot decisions remain traceable.

Troubleshooting

  • If the team is still deciding whether senco is the right type of tool, start with /compare.
  • If the team already agrees on the category but needs confidence on governance, start with /trust.
  • If the team is ready to discuss pilot shape, owner roles, and phased rollout, return to /schools-and-trusts.
  • If someone asks for an onboarding checklist, use /schools-and-trusts/checklist and the Print checklist button.