Printable pilot checklist

School and trust deployment-readiness checklist for a governed senco pilot.

Use this checklist before live use to align ownership, workflow scope, non-diagnostic boundaries, retention expectations, and operational evidence. It supports local governance discussions; it is not a substitute for safeguarding, data protection, procurement, or clinical decision-making.

Back to rollout guidance

Keep this checklist attached to a pilot readiness conversation. The wording is intentionally non-diagnostic: senco helps teams review observed patterns and workflow evidence, not assign diagnostic labels to pupils.

Pilot ownership

Name the accountable school or trust sponsor for the pilot.
Name the day-to-day SENCO owner for observation review and follow-up.
Confirm who monitors urgent safeguarding and SENCO-review escalation tasks.
Decide whether clinicians, central trust staff, or safeguarding leads join from day one.

Workflow scope

Choose the first cohort, year group, school, or workflow area.
Confirm whether the pilot starts with observations, escalation tasks, pathway packs, or collaborative review.
Agree how teachers will be told what to record and what not to record.
Confirm the route for concerns that must follow existing safeguarding procedures outside senco.

Governance checks

Review non-diagnostic wording expectations with the pilot team.
Agree retention expectations for pathway pack attachments and audit exports.
Confirm who can invite team members and manage organisation settings.
Decide how calibration feedback from SENCOs or clinicians will be captured during the pilot.

Readiness evidence

Capture one observation-to-reviewed-report walkthrough before expanding usage.
Check that escalation owner assignment, due dates, notes, and acknowledgement work as expected.
Review an example pathway pack before any external sharing.
Run an audit export or timeline review so accountable leads understand the evidence trail.

Use the checklist in a short, evidenced review.

Confirm pilot purpose, scope, and accountable owners.

Review non-diagnostic use boundaries and local safeguarding pathways.

Agree initial users, roles, notification expectations, and review responsibilities.

Walk through observation review, escalation ownership, pathway packs, and audit evidence.

Define what must be true before adding more cohorts, schools, or trust-level users.

Proof to review

Operational details firm enough to discuss now.

Access and roles

The product already has organisation-scoped workspaces and role-aware flows for pilot teams.

BetterAuth magic-link sign-in
Team invitations for SENCO, staff, clinician, and owner users
Protected APIs for student, review, escalation, audit, import, and calibration workflows

Governed evidence trail

Observation, review, escalation, and export actions are designed to leave traceable records.

Initial extraction versus human-reviewed behaviour comparison
Escalation notes, owner changes, checklist activity, and attachment history
Admin audit timeline with filters, saved export presets, and background export jobs

Retention and operations

Public proof can reference concrete controls without implying a full compliance certification.

Pack retention settings and scheduled enforcement endpoint
Retention cron health monitoring for production scheduler setup
Attachment expiry, export status, download count, and re-download metadata

Reasoning governance

Model-backed reasoning is wrapped in professional review and calibration governance.

Human review before report finalisation
SENCO/clinician calibration feedback and analytics
Versioned calibration proposals, releases, rollbacks, and safe synthetic provider probes

Ready to publish now

senco is non-diagnostic and supports professional SEND review workflows.
Schools should define accountable owners before live use.
Retention, audit exports, and pathway wording are configuration decisions for each organisation.
Public analyser use is non-persistent; dashboard use is for authenticated organisation workspaces.

Not yet a public claim

No public customer outcomes, case studies, or quantified impact claims have been published yet.
No legal/compliance certification page should imply external accreditation before formal review.
No universal onboarding timeline should be promised because school and trust governance varies.
No diagnostic accuracy claims should be made.