ssenco
Log inSign up
Schools and trusts

Public onboarding and deployment-readiness guidance for senco pilots.

Use this page when a school, MAT, or trust wants to understand what should be agreed before a pilot starts. The goal is not to promise instant rollout. It is to show what needs to be ready around role ownership, governance, and operational follow-through.

Start pilot workspaceReview trust centreOpen pilot checklist

What this public rollout page helps answer

Who should be involved in the first pilot decisions

Which workflow and retention choices should be agreed before live use

How to phase a rollout instead of enabling everything on day one

Which pilot artefacts should be prepared before expansion

Where to look next for trust posture, comparison, and role-specific workflow proof

Phased rollout

Use a small, governed start instead of a rushed launch.

1. Discovery and workflow fit

Clarify who will use senco first and which operational workflows the pilot needs to prove.

  • Identify the pilot team across SENCO, clinician, safeguarding, and leadership stakeholders.
  • Choose the first workflows to validate, such as observation review, escalation ownership, or pathway packs.
  • Use the public role pages, trust page, and comparison page to align expectations before sign-in.

2. Operational readiness

Confirm the local decisions that need to be made before sensitive pupil workflows begin.

  • Agree the organisation-level ownership model for SENCO-review and urgent safeguarding pathways.
  • Review retention expectations for pack attachments, export jobs, and audit records.
  • Check whether the pilot needs clinician collaboration, pathway routing, or calibration governance from day one.

3. Pilot rollout

Start with a controlled cohort and validate the governed workflow in practice.

  • Create the workspace and invite the initial role-based team members.
  • Run the first observation and review flows with non-diagnostic language and documented governance expectations.
  • Monitor escalation handling, audit exports, retention health, and feedback loops during the pilot period.
Readiness checklist

Different stakeholders usually need different readiness checks.

For readiness meetings, use the printable checklist to turn these public checks into a practical pilot review worksheet.

Open printable checklist

For schools

  • Named SENCO owner and escalation follow-up model
  • Defined pilot cohort or workflow scope
  • Local expectations for attachment retention and export review
  • Agreed teacher contribution and review process

For trusts

  • Decision on whether rollout is school-led, trust-led, or phased by cohort
  • Governance review of audit exports, retention monitoring, and pathway ownership expectations
  • Agreement on how clinician, safeguarding, or central teams join the pilot
  • Shared success criteria for review quality, accountability, and operational follow-through
Onboarding artefacts

Prepare the operating evidence before expanding a pilot.

These are not promises of a fixed rollout timeline. They are practical artefacts schools and trusts can use to decide whether the pilot is ready to move from discovery to wider use.

Before the pilot starts

  • Named pilot sponsor and day-to-day SENCO owner
  • Pilot cohort, year group, or workflow scope
  • Agreed route for urgent safeguarding concerns outside senco
  • Confirmed list of initial users and roles
  • Decision on whether clinician accounts are included in the first phase

During the first review cycle

  • Sample observation-to-report workflow reviewed by the SENCO owner
  • Escalation owner, due-date, and acknowledgement behaviour checked with real workflow examples
  • Pathway pack wording reviewed before external sharing
  • Retention settings and export expectations confirmed in settings
  • Calibration feedback approach agreed for SENCO/clinician reviewers

Before expanding rollout

  • Audit export reviewed by the accountable lead
  • Notification routing checked for SENCO-review and safeguarding events
  • Training notes shared for teachers contributing observations
  • Parent/carer summary wording reviewed against local policy
  • Success criteria reviewed before adding new cohorts or schools
Operational proof

Public proof should stay tied to implemented controls.

These are the operational details firm enough to publish now because they map to implemented product behaviour rather than future promises.

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
Publishing boundaries

Be clear about what can and cannot be claimed yet.

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.
Public rollout FAQs and next steps

What should a school confirm before starting a senco pilot?

The first pilot should confirm role ownership, escalation follow-up, retention expectations, and the initial workflow scope before sensitive live use begins.

What do trusts usually need to review?

Trust stakeholders usually review organisation ownership, audit and export expectations, retention controls, and how central safeguarding or clinical teams will participate.

Does senco require every feature to be enabled on day one?

No. The public rollout guidance is designed around a phased pilot so schools and trusts can start with the workflows they need to validate first.

Can senco publish a fixed onboarding timeline?

Not yet. The public guidance explains the decisions and artefacts a school or trust should prepare, but rollout duration depends on local governance, users, and workflow scope.

What operational proof is firm enough to share publicly?

The public site can reference implemented controls such as role-based invitations, protected APIs, audit events, retention settings, export jobs, and calibration release governance.

Open pilot checklistSee the SENCO workflowReview trust postureCompare approachesOpen the guide hub