StudyVector schools

School evidence overview

For UK school, college, MAT and tutoring-centre review | Updated May 2026

This one-page pack explains how StudyVector fits intervention, what staff can review, and where the current product boundaries are. It is a review document, not an endorsement document.

1. How it fits intervention workflows

Assign board-aligned practice by class, cohort, topic and exam board.
Use weak-topic, completion and accuracy views before mocks expose gaps.
Run a scoped 30-day pilot with a review question agreed before launch.

2. What teachers and leaders can see

Class, cohort and topic-level accuracy for intervention follow-up.
Homework completion and attempted work without manual mark entry.
Student supports including dyslexia-aware reading mode and calmer pacing.
No private tutor messages, parent-only summaries or unrelated classes are included in school reporting by default.

3. Procurement and data review materials

Public security, privacy, school DPA, subprocessor and accuracy pages.
Exam-board alignment page with independence boundaries, official-source cross-checks and correction route.
No student personal data is needed for the first enquiry or fit check.
School trials agree a named contact, escalation route and review point.

4. How it saves marking time

Auto-marked practice gives completion, accuracy and misconception signals without teachers collecting every answer manually.
Teachers can focus review time on exceptions, weak topics and longer written responses rather than routine retrieval checks.
Homework evidence is visible as status and topic data, so department follow-up can start from the same record instead of a separate spreadsheet.

5. Current status and boundaries

StudyVector is early-stage; coverage and feature status are updated on-site.
SSO/MIS sync and larger trust automation are planned, not assumed live.
No DfE, Ofqual, exam-board, UCAS, university or school approval is claimed.

Procurement readiness

The questions a school team can answer before a pilot

Use this checklist before bringing StudyVector into a wider internal review. It separates the evidence available today from the boundaries that should stay explicit during procurement.

Intervention fit

Head of department, head of year or intervention lead

Evidence to review: A named cohort, priority subjects, exam boards, the intervention question, and the 30-day review signal your team wants to inspect.
Boundary to keep clear: A pilot should support a rollout decision; it should not be presented as a public success claim.

Data protection review

DPO, data lead or operations manager

Evidence to review: Privacy policy, school DPA, subprocessor list, retention and deletion notes, and the current manual setup model.
Boundary to keep clear: No student personal data is needed for the first enquiry or fit check.

Safeguarding and responsible AI

DSL, SLT or trust digital lead

Evidence to review: Bounded revision tasks, no open student social feed, no private school messaging channel, and an agreed escalation contact for the pilot.
Boundary to keep clear: StudyVector is not a safeguarding case-management system or a replacement for school safeguarding processes.

SEND and access

SENCO, inclusion lead or intervention team

Evidence to review: Reading mode, read-aloud support, calmer pacing, reading guide, access-boundary copy, and student support settings.
Boundary to keep clear: These are accessibility supports for learning; they are not diagnosis, treatment, or a promised outcome.

Rollout decision

SLT, trust lead or procurement owner

Evidence to review: A clear checkpoint to expand, refine scope or pause, based on completion, topic accuracy, weak-area recovery and teacher workflow observations.
Boundary to keep clear: SSO and MIS sync are planned procurement features; current pilots use scoped setup unless integrations are explicitly agreed.

Pilot review rubric

How a school can judge whether the pilot is worth expanding

Agree these signals before launch so the review meeting is about evidence, not sales pressure. The decision can be to expand, refine the setup, or pause.

Usage signal

Evidence to review: Activation, study days, questions attempted, assigned homework completion, and whether the agreed cohort reached the learning loop.
How leaders use it: Separates product fit from rollout friction before leaders judge wider adoption.
Boundary to keep clear: Do not present pilot usage as public social proof or a school success claim.

Learning signal

Evidence to review: Topic accuracy, weak-area recovery, misconception clusters, and the next reteach or intervention group suggested by the data.
How leaders use it: Shows whether StudyVector is giving teachers actionable next steps before mocks or assessments.
Boundary to keep clear: No guaranteed grade improvement; teacher judgement and school assessment evidence remain the authority.

Teacher workflow signal

Evidence to review: How many routine checks were reviewed without manual mark entry, which exceptions still needed teacher review, and whether homework follow-up became clearer.
How leaders use it: Helps HoDs decide whether the tool reduces low-value admin while preserving professional judgement.
Boundary to keep clear: Longer written work, safeguarding concerns, and formal assessment decisions still need school-owned review.

Inclusion and access signal

Evidence to review: Use of low-focus mode, dyslexia-aware reading support, read-aloud tools, calmer pacing, and any student support preferences agreed for the pilot.
How leaders use it: Shows whether more learners can participate without adding pressure or over-sharing personal data.
Boundary to keep clear: Accessibility supports are learning adjustments, not diagnosis, treatment, or promised outcomes.

Rollout decision

Evidence to review: The agreed checkpoint: expand, refine scope, pause, or wait for planned features such as SSO/MIS before wider rollout.
How leaders use it: Keeps procurement honest by tying the next step to product fit, staff workflow, and current implementation status.
Boundary to keep clear: Nothing beyond the agreed pilot scope is implied unless the school and StudyVector approve the next step.

Student privacy

What a school evidence export should and should not contain

When staff circulate pilot evidence internally, keep the pack focused on teaching decisions. Share the minimum useful signal, and leave private student context out unless the school has a documented reason and role-based access.

Cohort and class review

Pilot lead or school data owner

Safe to include: Class, cohort, subject, exam board, topic, completion status, accuracy bands and weak-area patterns.
Keep out unless separately approved: Private tutor chats, parent-only summaries, payment status, account settings or unrelated classes.

Named student follow-up

Teacher, SENCO or pastoral lead

Safe to include: The learner, class, assigned work, support preference and one next teaching action when staff need a direct intervention.
Keep out unless separately approved: Full answer-by-answer logs, diagnoses, safeguarding notes or private family context unless school processes already permit that sharing.

Leadership and procurement pack

SLT, trust lead or procurement owner

Safe to include: Aggregate pilot usage, teacher workflow observations, inclusion settings used, risk notes and a clear expand, refine or pause decision.
Keep out unless separately approved: Ranked student lists, public case studies, outcome claims or school endorsements without explicit written approval.

Content-quality correction review

Content quality owner or named school contact

Safe to include: Question ID, subject, board, topic, reported issue, review status and whether public wording changed.
Keep out unless separately approved: Student identity or full attempt history unless needed to reproduce the issue and approved by the school contact.

Public-claim boundary

Keep public claims aligned with the security, privacy, school DPA, subprocessor and accuracy policy pages.

StudyVector schools

School evidence overview

For UK school, college, MAT and tutoring-centre review | Updated May 2026

This one-page pack explains how StudyVector fits intervention, what staff can review, and where the current product boundaries are. It is a review document, not an endorsement document.

1. How it fits intervention workflows

Assign board-aligned practice by class, cohort, topic and exam board.
Use weak-topic, completion and accuracy views before mocks expose gaps.
Run a scoped 30-day pilot with a review question agreed before launch.

2. What teachers and leaders can see

Class, cohort and topic-level accuracy for intervention follow-up.
Homework completion and attempted work without manual mark entry.
Student supports including dyslexia-aware reading mode and calmer pacing.
No private tutor messages, parent-only summaries or unrelated classes are included in school reporting by default.

3. Procurement and data review materials

Public security, privacy, school DPA, subprocessor and accuracy pages.
Exam-board alignment page with independence boundaries, official-source cross-checks and correction route.
No student personal data is needed for the first enquiry or fit check.
School trials agree a named contact, escalation route and review point.

4. How it saves marking time

Auto-marked practice gives completion, accuracy and misconception signals without teachers collecting every answer manually.
Teachers can focus review time on exceptions, weak topics and longer written responses rather than routine retrieval checks.
Homework evidence is visible as status and topic data, so department follow-up can start from the same record instead of a separate spreadsheet.

5. Current status and boundaries

StudyVector is early-stage; coverage and feature status are updated on-site.
SSO/MIS sync and larger trust automation are planned, not assumed live.
No DfE, Ofqual, exam-board, UCAS, university or school approval is claimed.

Procurement readiness

The questions a school team can answer before a pilot

Use this checklist before bringing StudyVector into a wider internal review. It separates the evidence available today from the boundaries that should stay explicit during procurement.

Intervention fit

Head of department, head of year or intervention lead

Evidence to review: A named cohort, priority subjects, exam boards, the intervention question, and the 30-day review signal your team wants to inspect.
Boundary to keep clear: A pilot should support a rollout decision; it should not be presented as a public success claim.

Data protection review

DPO, data lead or operations manager

Evidence to review: Privacy policy, school DPA, subprocessor list, retention and deletion notes, and the current manual setup model.
Boundary to keep clear: No student personal data is needed for the first enquiry or fit check.

Safeguarding and responsible AI

DSL, SLT or trust digital lead

Evidence to review: Bounded revision tasks, no open student social feed, no private school messaging channel, and an agreed escalation contact for the pilot.
Boundary to keep clear: StudyVector is not a safeguarding case-management system or a replacement for school safeguarding processes.

SEND and access

SENCO, inclusion lead or intervention team

Evidence to review: Reading mode, read-aloud support, calmer pacing, reading guide, access-boundary copy, and student support settings.
Boundary to keep clear: These are accessibility supports for learning; they are not diagnosis, treatment, or a promised outcome.

Rollout decision

SLT, trust lead or procurement owner

Evidence to review: A clear checkpoint to expand, refine scope or pause, based on completion, topic accuracy, weak-area recovery and teacher workflow observations.
Boundary to keep clear: SSO and MIS sync are planned procurement features; current pilots use scoped setup unless integrations are explicitly agreed.

Pilot review rubric

How a school can judge whether the pilot is worth expanding

Agree these signals before launch so the review meeting is about evidence, not sales pressure. The decision can be to expand, refine the setup, or pause.

Usage signal

Evidence to review: Activation, study days, questions attempted, assigned homework completion, and whether the agreed cohort reached the learning loop.
How leaders use it: Separates product fit from rollout friction before leaders judge wider adoption.
Boundary to keep clear: Do not present pilot usage as public social proof or a school success claim.

Learning signal

Evidence to review: Topic accuracy, weak-area recovery, misconception clusters, and the next reteach or intervention group suggested by the data.
How leaders use it: Shows whether StudyVector is giving teachers actionable next steps before mocks or assessments.
Boundary to keep clear: No guaranteed grade improvement; teacher judgement and school assessment evidence remain the authority.

Teacher workflow signal

Evidence to review: How many routine checks were reviewed without manual mark entry, which exceptions still needed teacher review, and whether homework follow-up became clearer.
How leaders use it: Helps HoDs decide whether the tool reduces low-value admin while preserving professional judgement.
Boundary to keep clear: Longer written work, safeguarding concerns, and formal assessment decisions still need school-owned review.

Inclusion and access signal

Evidence to review: Use of low-focus mode, dyslexia-aware reading support, read-aloud tools, calmer pacing, and any student support preferences agreed for the pilot.
How leaders use it: Shows whether more learners can participate without adding pressure or over-sharing personal data.
Boundary to keep clear: Accessibility supports are learning adjustments, not diagnosis, treatment, or promised outcomes.

Rollout decision

Evidence to review: The agreed checkpoint: expand, refine scope, pause, or wait for planned features such as SSO/MIS before wider rollout.
How leaders use it: Keeps procurement honest by tying the next step to product fit, staff workflow, and current implementation status.
Boundary to keep clear: Nothing beyond the agreed pilot scope is implied unless the school and StudyVector approve the next step.

Student privacy

What a school evidence export should and should not contain

Cohort and class review

Pilot lead or school data owner

Safe to include: Class, cohort, subject, exam board, topic, completion status, accuracy bands and weak-area patterns.
Keep out unless separately approved: Private tutor chats, parent-only summaries, payment status, account settings or unrelated classes.

Named student follow-up

Teacher, SENCO or pastoral lead

Safe to include: The learner, class, assigned work, support preference and one next teaching action when staff need a direct intervention.
Keep out unless separately approved: Full answer-by-answer logs, diagnoses, safeguarding notes or private family context unless school processes already permit that sharing.

Leadership and procurement pack

SLT, trust lead or procurement owner

Safe to include: Aggregate pilot usage, teacher workflow observations, inclusion settings used, risk notes and a clear expand, refine or pause decision.
Keep out unless separately approved: Ranked student lists, public case studies, outcome claims or school endorsements without explicit written approval.

Content-quality correction review

Content quality owner or named school contact

Safe to include: Question ID, subject, board, topic, reported issue, review status and whether public wording changed.
Keep out unless separately approved: Student identity or full attempt history unless needed to reproduce the issue and approved by the school contact.

Public-claim boundary

Keep public claims aligned with the security, privacy, school DPA, subprocessor and accuracy policy pages.