AI drafts the feedback. Teachers stay in control.
MarkVector is the StudyVector marking layer for homework-first draft feedback, rubric comments and teacher-reviewed final responses. It is built to reduce marking workload without pretending AI is an official examiner.
Teachers, tutors and students
This product sits under Vector Learning Technologies and uses StudyVector as the shared public platform, account path and learning context.
One learning intelligence system
Built as connected StudyVector products, not separate microsites.
The page is intentionally clear about status. Live, early-access and planned features are labelled so the ecosystem can grow without inventing traction or capability.
Homework answers queued for draft marking
Evidence-tier labels on every result
Teacher review before final feedback
Common missed marks grouped by class
Weak-topic repair signals after publishing
Audit trail for model and review evidence
No official examiner or exam-board claim
Teacher assigns written, explain-back or exam-style homework
MarkVector drafts marks, missed points and the fastest route to full marks
Teacher reviews, edits and publishes final feedback
Published feedback feeds StudyVector weak-topic repair and next practice
StudyVector constellation
One account, one learning profile, multiple role-specific planets.
Product system
Every Vector planet now has a defined buyer, primary user, system job, privacy scope and first workflow. That keeps the product roadmap and public marketing tied to what the platform can actually support.
Teachers reviewing practice answers and written responses
Student answers used for draft marking should not become final marks until an authorised adult reviews the output.
The public page is not a data dashboard. It explains the intended architecture: shared account identity, shared learning profile and permissioned insights across the StudyVector constellation.
The shared MarkVector contract now labels answer-key, worked-solution, mark-scheme, examiner-note and teacher-moderated feedback differently.
Homework uses MarkVector tasks, results and teacher reviews while legacy assignment submissions remain compatibility data.
Feedback sync is designed to connect published marking comments with StudyVector weak-topic and error-log repair.
Draft marking support is not official examiner feedback and is not a replacement for teacher judgement or centre policy.
Compliance readiness
MarkVector is positioned as draft feedback support. It must not replace teacher judgement, centre policies, official mark schemes or exam-board decisions.
Reviewed against public guidance
Source set reviewed 22 May 2026. This is a product-readiness framework, not legal advice and not a claim of DfE, exam-board, Ofqual, UCAS, university or school approval.
AI output is treated as a draft. A teacher, tutor or authorised adult reviews marks and comments before they are shared as final feedback.
Assessed work follows school and JCQ rules. MarkVector copy avoids presenting AI help as allowed for every assessment context.
Rubric feedback can be examiner-style for practice, but it is not official examiner feedback and does not imply exam-board endorsement.
These records keep product, procurement and partnership conversations inspectable before school, exam-board or university discussions move further.
Security and privacy practice
StudyVector’s school and teacher ecosystem is marketed around reviewable controls: privacy boundaries, human-reviewed marking, assessment-integrity wording and evidence packs that schools can inspect before rollout.
Reviewed source posture
Source set reviewed 22 May 2026. Designed against public DfE, ICO, Ofqual and JCQ guidance. This does not imply approval, certification or endorsement by those bodies.
AI support is framed around reducing teacher workload: draft marking, lesson prep and follow-up suggestions. Feedback that affects a learner stays reviewable by a teacher or authorised adult.
Human review before final feedback
School review materials prioritise collecting only the data needed for the workflow, keeping sensitive support notes permissioned and making privacy notices, DPA and retention evidence easy to find.
DPA, DPIA and retention links
MarkVector and teacher workflows avoid presenting AI as an official marker. Practice feedback is separate from regulated assessment decisions and school or awarding-body rules remain the source of truth.
No AI-as-sole-marker claim
Exam-board, DfE, Ofqual, UCAS and university names are treated as protected claim areas. Public copy can cite guidance, but approval or partnership language requires written proof and approved wording.
No endorsement by default
These references help teachers, DPOs, SLT and exam-board contacts understand the boundaries we are building toward.
Future Vector products are designed to sync through controlled StudyVector learning data: user profiles, mastery, mistakes, marking feedback and dashboard views. Public pages never expose private learner data.
The ecosystem is designed to share learning context while keeping each workflow clear.
Students and families
Board-aware revision practice for GCSE, A-Level and beyond.
Independent tutors and tutoring teams
The AI workspace for modern tutors.
Heads of department, SLT and school teams
Learning intelligence for schools and departments.
MarkVector is part of the wider Vector roadmap. Early conversations help keep the product useful, honest and connected to real learning workflows.
AI drafts the feedback. Teachers stay in control.
MarkVector is the StudyVector marking layer for homework-first draft feedback, rubric comments and teacher-reviewed final responses. It is built to reduce marking workload without pretending AI is an official examiner.
Teachers, tutors and students
This product sits under Vector Learning Technologies and uses StudyVector as the shared public platform, account path and learning context.
One learning intelligence system
Built as connected StudyVector products, not separate microsites.
The page is intentionally clear about status. Live, early-access and planned features are labelled so the ecosystem can grow without inventing traction or capability.
Homework answers queued for draft marking
Evidence-tier labels on every result
Teacher review before final feedback
Common missed marks grouped by class
Weak-topic repair signals after publishing
Audit trail for model and review evidence
No official examiner or exam-board claim
Teacher assigns written, explain-back or exam-style homework
MarkVector drafts marks, missed points and the fastest route to full marks
Teacher reviews, edits and publishes final feedback
Published feedback feeds StudyVector weak-topic repair and next practice
StudyVector constellation
One account, one learning profile, multiple role-specific planets.
Product system
Every Vector planet now has a defined buyer, primary user, system job, privacy scope and first workflow. That keeps the product roadmap and public marketing tied to what the platform can actually support.
Teachers reviewing practice answers and written responses
Student answers used for draft marking should not become final marks until an authorised adult reviews the output.
The public page is not a data dashboard. It explains the intended architecture: shared account identity, shared learning profile and permissioned insights across the StudyVector constellation.
The shared MarkVector contract now labels answer-key, worked-solution, mark-scheme, examiner-note and teacher-moderated feedback differently.
Homework uses MarkVector tasks, results and teacher reviews while legacy assignment submissions remain compatibility data.
Feedback sync is designed to connect published marking comments with StudyVector weak-topic and error-log repair.
Draft marking support is not official examiner feedback and is not a replacement for teacher judgement or centre policy.
Compliance readiness
MarkVector is positioned as draft feedback support. It must not replace teacher judgement, centre policies, official mark schemes or exam-board decisions.
Reviewed against public guidance
Source set reviewed 22 May 2026. This is a product-readiness framework, not legal advice and not a claim of DfE, exam-board, Ofqual, UCAS, university or school approval.
AI output is treated as a draft. A teacher, tutor or authorised adult reviews marks and comments before they are shared as final feedback.
Assessed work follows school and JCQ rules. MarkVector copy avoids presenting AI help as allowed for every assessment context.
Rubric feedback can be examiner-style for practice, but it is not official examiner feedback and does not imply exam-board endorsement.
These records keep product, procurement and partnership conversations inspectable before school, exam-board or university discussions move further.
Security and privacy practice
StudyVector’s school and teacher ecosystem is marketed around reviewable controls: privacy boundaries, human-reviewed marking, assessment-integrity wording and evidence packs that schools can inspect before rollout.
Reviewed source posture
Source set reviewed 22 May 2026. Designed against public DfE, ICO, Ofqual and JCQ guidance. This does not imply approval, certification or endorsement by those bodies.
AI support is framed around reducing teacher workload: draft marking, lesson prep and follow-up suggestions. Feedback that affects a learner stays reviewable by a teacher or authorised adult.
Human review before final feedback
School review materials prioritise collecting only the data needed for the workflow, keeping sensitive support notes permissioned and making privacy notices, DPA and retention evidence easy to find.
DPA, DPIA and retention links
MarkVector and teacher workflows avoid presenting AI as an official marker. Practice feedback is separate from regulated assessment decisions and school or awarding-body rules remain the source of truth.
No AI-as-sole-marker claim
Exam-board, DfE, Ofqual, UCAS and university names are treated as protected claim areas. Public copy can cite guidance, but approval or partnership language requires written proof and approved wording.
No endorsement by default
These references help teachers, DPOs, SLT and exam-board contacts understand the boundaries we are building toward.
Future Vector products are designed to sync through controlled StudyVector learning data: user profiles, mastery, mistakes, marking feedback and dashboard views. Public pages never expose private learner data.
The ecosystem is designed to share learning context while keeping each workflow clear.
Students and families
Board-aware revision practice for GCSE, A-Level and beyond.
Independent tutors and tutoring teams
The AI workspace for modern tutors.
Heads of department, SLT and school teams
Learning intelligence for schools and departments.
MarkVector is part of the wider Vector roadmap. Early conversations help keep the product useful, honest and connected to real learning workflows.