Trust and procurement

Ask the questions that survive implementation

Use evidence-led trust pages to turn vague procurement promises into specific controls, owners, deployment checks, and contractual questions.

Choose a question

Start with the page closest to your decision

Each page includes workflow steps, responsible teams, implementation detail, boundaries, evidence links, and FAQs.

Validate for rollout
Schoolyi security architecture
Review authentication, role-based access, data boundaries, sessions, audit visibility, and operational controls before rollout.
Read the page
Validate for rollout
Data residency and backups
Turn hosting region, retention, recovery, export, and backup expectations into concrete questions for a school deployment.
Read the page
Validate for rollout
DPA and subprocessors review
Prepare the questions a school needs answered about processing roles, subprocessors, integrations, transfers, and deletion.
Read the page
Validate for rollout
Availability and support expectations
Define support ownership, service windows, incident communication, scheduled jobs, and recovery expectations for school operations.
Read the page
Validate for rollout
Accessibility for school portals and public pages
Evaluate keyboard access, readable content, mobile layouts, form errors, contrast, and family support across public and portal journeys.
Read the page
Available now
School software procurement questionnaire
A practical questionnaire for evaluating school software across workflows, data, security, implementation, support, and total cost.
Read the page

Bring your school’s workflow, roles, and first-term priorities to a focused walkthrough.

Already using Schoolyi? Sign in