ssenco
Log inSign up

Public Trust and Comparison Pages

What we publish, and how we compare.

What it does

This guide explains the public pages that help schools, trusts, clinicians, safeguarding leads, and procurement stakeholders understand how senco differs from spreadsheets, generic chatbots, and diagnosis-style classifiers. It also shows where to review the public trust and auditability posture before a pilot.

Where to find it

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

Step by step

  1. Open /compare if you want a side-by-side explanation of how senco differs from spreadsheets, generic chatbots, and diagnosis-style classifiers.
  2. Open /trust if you need public assurance on non-diagnostic AI, audit trails, retention controls, and escalation governance.
  3. Use the CTAs on either page to:
  • Start governed workspace
  • Review trust centre
  • Read governance guides
  1. Return to / if you want the broader landing-page overview and the role-specific entry points.
  2. Open /schools-and-trusts if the conversation shifts from trust posture to rollout-readiness and phased pilot planning.
  3. Open /schools-and-trusts/checklist when the group needs a printable worksheet for a pilot-readiness meeting.

What each screen shows

/compare

  • A comparison matrix covering natural-language observations, human review, audit trails, non-diagnostic posture, and governance readiness.
  • Procurement and governance proof cards showing implementation readiness, operational controls, and pilot-readiness signals.
  • Workspace and trust-centre CTAs for users who want to continue deeper.

/trust

  • Trust messaging for non-diagnostic SEND support, audit trails, retention controls, and safe escalation governance.
  • Governance commitments and trust pillars tied to real product behaviours such as reviewer comparison, retention enforcement, and calibration releases.
  • Operational proof cards that point to implemented controls such as role-aware access, governed evidence trails, retention operations, and reasoning governance.
  • A governance FAQ and a route into the comparison page when stakeholders want to weigh alternative approaches.

/

  • A shorter comparison preview section highlighting why senco is different from spreadsheets, chatbots, and classifier-style tools.
  • A governance section linking directly to the trust centre and comparison page.

/schools-and-trusts

  • Public rollout-readiness guidance for schools, MATs, and trusts.
  • Phased onboarding content covering discovery, operational readiness, and controlled pilot rollout.
  • School-level and trust-level readiness checklists.
  • Onboarding artefacts for pre-pilot setup, first review cycle checks, and expansion readiness.
  • Publishing boundaries that separate current product proof from future claims such as case studies, certification, or quantified outcomes.

/schools-and-trusts/checklist

  • A print-friendly pilot-readiness worksheet for ownership, workflow scope, governance checks, and readiness evidence.
  • A readiness meeting agenda and public proof cards that keep the discussion tied to implemented product controls.

Tips

  • Start with /compare when you need to explain why a governed SEND workflow matters, not just why AI can be helpful.
  • Start with /trust when procurement or safeguarding stakeholders want to verify data handling, governance, or operational controls.
  • Use these public routes before sign-in meetings so every stakeholder sees the same non-diagnostic product posture.
  • Use the publishing-boundary section on /schools-and-trusts when stakeholders ask what is safe to claim publicly today.
  • Use /schools-and-trusts/checklist when the discussion needs a concrete artefact to attach to meeting notes.

Troubleshooting

  • If someone asks whether senco diagnoses pupils, direct them to /trust first.
  • If someone compares senco to a spreadsheet or chatbot, direct them to /compare.
  • If someone asks for implementation-readiness detail, direct them to /schools-and-trusts.
  • If someone asks for a practical readiness worksheet, direct them to /schools-and-trusts/checklist.
  • If someone needs product-operation details after reading the public pages, continue with the relevant authenticated workflow guides in docs/guides.

Related guides