Transparency standard
Do not invent a subprocessor list or legal commitment in marketing copy; publish only verified current terms.
Trust and procurement
DPA and subprocessors review
Prepare the questions a school needs answered about processing roles, subprocessors, integrations, transfers, and deletion. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
A useful page should answer the next operational question
Prepare the questions a school needs answered about processing roles, subprocessors, integrations, transfers, and deletion.
Who this is for
- Procurement
- Data protection owners
- School leadership
Start with the evidence
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
Follow the handoffs, not just the feature list
A clear sequence makes ownership, exceptions, and the next system action visible.
- 01
Name roles
Document the school, platform, payment, email, storage, and integration responsibilities.
- 02
List processing
Identify which services handle student, family, staff, payment, and support information.
- 03
Review transfers
Confirm regions, contractual safeguards, access pathways, and notification expectations.
- 04
Close lifecycle
Agree deletion, return, retention, and offboarding procedures before signature.
Product truth
What to verify before rollout
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
Procurement question
Capability status
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Teams in the workflow
- Procurement
- Data protection owners
- School leadership
Deep dive
Decisions, handoffs, and boundaries
Use these details to turn a product page into an implementation conversation.
Procurement handoff
The output should be a questionnaire with owners and dates, not a generic trust statement.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Questions, answered
Straightforward answers for visitors evaluating the product.
Can this page replace a DPA?+
No. It is a preparation guide; legal terms must be reviewed and executed for the deployment.
What changes the answer?+
Hosting, email, payment, analytics, AI, support access, and custom integrations can all change the processing picture.
Continue exploring
Related planning and product pages
Follow the next link based on the question your team needs to answer.
Data residency and backups
Turn hosting region, retention, recovery, export, and backup expectations into concrete questions for a school deployment.
Read the pageSchool software procurement questionnaire
A practical questionnaire for evaluating school software across workflows, data, security, implementation, support, and total cost.
Read the page
Turn the page into a rollout conversation
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in