Teacher marks as usual, then records the outcomes
The workflow begins with the marking teachers already do. Record your classes' outcomes in your private workspace — or start with sample data if you want to explore first.
Teacher remains the authority
AI suggestions are drafts
Private teacher workspace
Privacy and data-control first
How It Works
Marking -> mastery signals -> misconception clusters -> teacher-approved interventions -> HOD visibility.
Beta data safety
Your classes, assignments, and marking records stay inside your own sign-in-protected workspace, and you can have your data deleted if you leave. Keep student personal identifiers out of uploads. Automated reading of scanned answer scripts is still in testing — sample scripts are provided for that step.
Learn more about beta data safetyThe workflow begins with the marking teachers already do. Record your classes' outcomes in your private workspace — or start with sample data if you want to explore first.
The system surfaces class-level mastery signals, high-friction questions, and misconception clusters from the marking evidence teachers already create.
AI suggestions are drafts. Teachers review the evidence, adapt suggested interventions, and approve final judgement before anything feeds post-marking intelligence.
HODs see department-level mastery and misconception trends for curriculum support, moderation, and resourcing without asking teachers to write extra reports.
Teacher-approved interventions can become remedial packs, reteaching prompts, or department support actions depending on the evidence.
In authorised future workflows, teacher-approved follow-up evidence can support the next review cycle. Real student scripts are not currently processed.
Marking results become mastery signals. Mastery signals become draft interventions. Teachers approve final actions before any records feed post-marking intelligence or department-level trends.