ssenco
Log inSign up

Pilot Checklist

What to have in place before a pilot starts.

What it does

The pilot checklist gives schools, MATs, and trusts a printable readiness worksheet before using senco with live organisation data. It helps teams align ownership, pilot scope, governance checks, and readiness evidence while keeping the product posture non-diagnostic.

Where to find it

  • Public checklist page: /schools-and-trusts/checklist
  • Schools and trusts rollout page: /schools-and-trusts
  • Public footer: Rollout -> Pilot checklist

Step by step

  1. Open /schools-and-trusts/checklist.
  2. Read the introductory note and confirm stakeholders understand that senco supports professional SEND review rather than diagnosis.
  3. Use Print checklist if you want a paper or PDF copy for a readiness meeting.
  4. Work through the four checklist groups:
  • pilot ownership
  • workflow scope
  • governance checks
  • readiness evidence
  1. Use the suggested readiness agenda to structure the meeting.
  2. Review the operational proof cards so stakeholders can connect public claims to implemented product controls.
  3. Review the publishing-boundary cards so the team avoids unsupported claims about outcomes, certification, onboarding timelines, or diagnostic accuracy.
  4. Return to /schools-and-trusts if you need the broader phased rollout guidance.

What each screen shows

/schools-and-trusts/checklist

  • A printable pilot-readiness checklist for school and trust stakeholders.
  • A non-diagnostic usage statement that should be retained when the checklist is shared.
  • Checklist sections for owners, scope, governance, and readiness evidence.
  • A short readiness meeting agenda.
  • Operational proof cards covering roles, evidence trails, retention/operations, and reasoning governance.
  • Public-claim boundary cards explaining what can be said now and what should wait for formal evidence.

Tips

  • Use the checklist before creating a full pilot workspace or inviting a wider group of staff.
  • Keep the checklist with meeting notes so later rollout decisions can be traced back to agreed ownership and scope.
  • Treat the operational proof cards as talking points, not as a replacement for procurement, DPIA, safeguarding, or local policy review.
  • Do not remove the non-diagnostic statement when sharing the checklist.

Troubleshooting

  • If the checklist feels too detailed, start with pilot ownership and workflow scope before reviewing governance checks.
  • If stakeholders need broader context, open /schools-and-trusts first.
  • If stakeholders are comparing senco with spreadsheets or generic AI tools, open /compare.
  • If stakeholders need assurance about audit, retention, and model governance, open /trust.

Related guides