Evidence before decision
Reviewers should see product status, source links, privacy boundaries and current setup assumptions before any rollout decision.
Organisation review
A review route for schools, trusts, providers and exam bodies
For UK education organisations reviewing StudyVector evidence | Updated June 2026
This guide separates practical review evidence from public endorsement. It explains what StudyVector can share, who should review it, and what must not be claimed unless there is written agreement and approved wording.
No review-as-endorsement
A conversation with a school, trust, provider or awarding body stays separate from public approval wording.
Decision record
Each review should close with a clear next step: proceed, pause, relabel, correct, or request more evidence.
Review audiences
Different reviewers need different evidence.
A useful review route points each organisation to the evidence that matches its decision, while keeping student data and public claims controlled.
Schools, colleges and MATs
Check intervention fit, teacher-visible data, privacy, safeguarding boundaries and current setup status before a pilot.
- Evidence to share
- School evidence overview, school DPA, privacy and subprocessor notes, current SSO/MIS status, pilot rubric and access boundaries.
- Boundary
- A pilot is internal review evidence. It should not become a public success claim or school endorsement without explicit approval.
Tutoring providers and learning organisations
Check learner-data scope, tutor visibility, parent-summary boundaries and provider rollout assumptions.
- Evidence to share
- TutorVector provider boundaries, student privacy, parent progress guide, access-owner notes and support-summary limits.
- Boundary
- Provider review does not create permission to expose unrelated learners, private messages, diagnoses or answer-by-answer feeds.
Exam boards and awarding organisations
Check that board names, specification routes, source links and public wording stay independent and accurate.
- Evidence to share
- Exam-board alignment page, content-quality review pack, route owner, source-link set, correction status and public reply boundary.
- Boundary
- Review conversations are not endorsement, approval, partnership, official status or access to confidential future papers.
Data, safeguarding and procurement reviewers
Check security posture, data minimisation, retention assumptions, model-training position and escalation routes before student data is shared.
- Evidence to share
- Security overview, student privacy, legal accuracy policy, content-quality review pack and current product-readiness notes.
- Boundary
- StudyVector is not a safeguarding case-management system, legal adviser, official certifier or substitute for school-owned approval processes.
Evidence packet
What a serious review should record.
The packet keeps the review specific: route, owner, evidence and boundary. It is designed to stop vague approval language before it reaches public copy.
Route and product status
StudyVector product owner
Which product route is being reviewed, whether it is live, early access or planned, and which current workflow the reviewer should inspect.
Do not present planned features as live or imply readiness beyond the current product state.
Data and access boundary
School, provider or data owner
Who can see what, whether access is student, parent, tutor, teacher or organisation-led, and which records are excluded by default.
Do not request or share student identities, diagnoses, private messages or full answer histories for first review.
Curriculum and source boundary
Curriculum or awarding-organisation reviewer
Qualification, board, subject, topic, public source links, correction route and whether wording is generic, board-aware or under review.
Alignment is not affiliation. Source links support checking; they do not create official approval.
Public-claim control
StudyVector comms and reviewer contact
Exact wording that might appear publicly, the evidence behind it, written permission where needed, and review date.
No testimonial, case study, certification, partnership, approval or endorsement wording should appear without explicit permission.
Review workflow
How a review should close.
Step 1
Identify the review owner
Decide whether the first reviewer is curriculum, data protection, safeguarding, IT, procurement, tutor-operations, or awarding-body wording.
The response routes evidence to the right owner instead of sending a generic sales pack.
Step 2
Share evidence without student personal data
Send public routes, policy pages, status notes and review boundaries first. Student-level data waits until a rollout route and data agreement exist.
The organisation can judge fit without unnecessary learner exposure.
Step 3
Record the public-claim boundary
If a reviewer checks wording, record what was checked, what changed, what remains under review and what cannot be claimed.
Corrections improve product quality without becoming social proof.
Step 4
Close with a next decision
The next step should be explicit: proceed to pilot, request more evidence, relabel wording, pause a route, or leave unchanged after source check.
The organisation leaves with a decision record, not vague assurance.
What this route must not become
- No DfE, Ofqual, exam-board, UCAS, university, school, trust or provider approval is claimed.
- No private future papers, confidential examiner material or grade-boundary certainty is claimed.
- No school, provider, trust or awarding-body review is treated as endorsement without written approval.
- No student personal data is needed for first review, procurement triage or public wording checks.
Related evidence
Start with the evidence route, then ask for review.
Public boundary
Use this page as an evidence map. It is not legal advice, certification, endorsement or public-sector approval.