Assign with intent
Start from a class, subject, board, topic or homework goal so the evidence has a clear classroom use.
Teacher workflow evidence
How StudyVector supports teachers without taking over judgement
For classroom teachers, HoDs, year leads and school reviewers | Updated June 2026
This guide explains how StudyVector should fit a teacher workflow: assign practice, track completion and weak topics, review evidence, and choose one next action. It is written for practical classroom use, not inflated automation claims.
Review usable signals
Focus on completion, accuracy and weak-topic patterns instead of a raw feed of every student action.
Keep judgement human
StudyVector supports intervention decisions; teachers and schools still own assessment and follow-up.
Classroom workflow
Assign, track, then follow up with one action.
The guide keeps StudyVector anchored to the teacher loop: practice should create a useful signal, and that signal should lead to a bounded next step.
1. Assign practice with a clear purpose
A useful teacher workflow starts with a specific class, subject, board, topic or homework goal.
- Use short starters, homework links or scoped class assignments when the class needs a common diagnostic signal.
- Keep the task tied to the topic or mark-loss pattern the teacher wants to inspect next.
- Do not use a generic practice link as evidence that every course, board or learner need is covered.
2. Track the signal teachers can act on
The valuable data is not every click. It is the pattern that helps a teacher decide what to do next.
- Review homework completion, topic accuracy, weak-area patterns and class-level misconception signals.
- Compare StudyVector signals with classwork, homework records and teacher judgement before escalating support.
- Avoid turning class dashboards into daily surveillance or unrestricted student monitoring.
3. Follow up with one next action
The best teacher evidence loop ends with a small, named intervention instead of a broad instruction to revise more.
- Choose one classroom action, one homework repair, one low-focus weak-topic set or one reteach point.
- Record who owns the next step and when the signal should be reviewed again.
- Do not promise a grade change; frame each action as the next evidence-led step.
4. Keep marking and family evidence bounded
Draft marking support and parent-shared summaries can help, but teacher judgement and school communication routes stay central.
- Treat MarkVector output as draft feedback support until reviewed by a teacher or authorised adult.
- Use parent summaries as one evidence point alongside classwork, homework and school assessment.
- Keep private messages, diagnoses, payment details and full answer-by-answer logs out of routine teacher review.
Data boundaries
Useful class evidence without unrestricted monitoring.
Teacher access should match the school role and review question. These boundaries make the decision visible before a school trial expands.
Teachers can see
- Safe to review
- Assigned work, homework completion, topic accuracy, weak-area patterns, class-level misconception signals and draft marking workflow for their class or school role.
- Keep out
- Private tutor messages, parent-only notes, payment details, unrelated classes, diagnoses or a full answer-by-answer feed by default.
HoDs and year leads can review
- Safe to review
- Cohort, class, subject, board, topic and intervention summaries for the agreed school workflow.
- Keep out
- Open-ended student monitoring, informal family records, safeguarding case notes or access outside the agreed school role.
Families can share
- Safe to review
- Teacher-safe summaries: weekly question volume, homework completion, weak-topic labels and one question for school to check.
- Keep out
- Private family context, diagnoses, account settings, payment details, private tutor messages or every attempted answer.
Family and school handoff
Parent-shared summaries stay teacher-safe.
If a family shares a StudyVector summary, the teacher workflow should record only the classroom-relevant signal, verify it against school evidence, and close with one practical next step.
Protocol 1
Start with the family signal
Ask which StudyVector parent-dashboard signals triggered the concern: question volume, homework completion, weak-topic list, or target/current trajectory.
Do not ask families to share private tutor messages, account settings, a feed of every answer, or diagnoses. Accessibility or SEND preferences should be shared as study adjustments only with consent.
Protocol 2
Choose one classroom action
Pick one next action the family can understand: a homework repair, a short low-focus weak-topic set, a lesson-starter check, or a target-setting conversation.
Do not promise a grade change; frame the action as the next evidence-led step.
Protocol 3
Close the loop
Reply with the next action, who owns it, and when the parent or guardian should check progress again.
Parent access stays student-controlled; school communication should not override the student's account controls.
Teacher-safe intake
What to record from a parent summary.
Keep the record small enough to act on. The summary should help the teacher choose a classroom action, not create a parallel private record.
Record summary signals only
- Record
- Weekly question volume, study days, homework completion, weak-topic labels, and target/current trajectory.
- Verify
- Check whether those signals match classwork, homework records, and your own classroom judgement.
- Boundary
- Do not ask for private tutor messages, account settings, payment details, diagnoses, or full answer-by-answer logs.
Separate support preferences from diagnoses
- Record
- Only note access or SEND-related study adjustments the student is comfortable sharing.
- Verify
- Translate any shared adjustment into classroom support language: low-focus cards, extra structure, reading support, or homework chunking.
- Boundary
- Do not request medical detail or treat a family preference as a formal diagnosis.
Choose one shared next step
- Record
- One classroom action, one family low-focus step or homework step, and one review point.
- Verify
- Review after the next homework cycle or lesson checkpoint before asking for more home study.
- Boundary
- Do not turn the parent summary into daily monitoring or treat the signal as a forecast.
Classroom actions
Each feature has to end in learning work.
Classroom teacher
Lesson starter
A short weak-topic check that reveals one topic, misconception or mark-loss pattern before the lesson moves on.
A starter is diagnostic support, not a complete assessment or grade prediction.
Teacher or homework lead
Homework follow-up
Completion, accuracy and topic evidence from assigned work, reviewed against class context.
Routine auto-marked checks can reduce admin, but formal assessment decisions stay with the school.
Teacher or authorised reviewer
Draft marking review
Draft feedback, rubric notes and likely mark-loss patterns that a teacher reviews before final feedback.
Draft feedback is not official examiner marking or a replacement for teacher judgement.
Teacher and family
Family check-in
Summary signals shared by the family and compared with classwork, homework and teacher judgement.
Keep the reply inside school-approved communication channels and do not request private raw records.
Public boundary
Teacher evidence should support professional judgement. It should not become surveillance, official marking, a safeguarding case-management system, or a grade guarantee.
Related evidence
Use the route that matches the decision.
Trial scope
A school trial should agree the cohort, subjects, boards, staff roles and review question before any wider rollout or student-data import.
Request scoped school trial