RevisionDojo for IB coordinators is a whole-school teaching, practice, and analytics platform that connects student activity with class, subject, and cohort-level oversight. Coordinators and heads of department can use it to establish common revision routines, assign targeted resources, monitor weaknesses, and evaluate interventions across an IB programme.
Its value is not simply providing more resources. It comes from creating a consistent cycle in which teachers diagnose needs, assign suitable work, review evidence, and adjust teaching or support. This guide explains how to implement that cycle without treating platform data as a substitute for teacher judgement or official IB assessment procedures.
What RevisionDojo provides at school level
RevisionDojo for Schools combines examiner-written materials, assignments, automatic grading, progress tracking, and strength-and-weakness analytics. Resources include Study Notes, Mini Lessons, videos, a Questionbank, Test Builder, Predicted Papers, and AI-supported coursework feedback.
Students use learning and practice tools, teachers manage classes and assignments, and authorized leaders examine broader patterns where account permissions allow.
| Level of oversight | Useful question | Appropriate response |
|---|---|---|
| Individual student | Which topics or skills are causing difficulty? | Assign focused practice or teacher support |
| Class | Is a weakness shared across the group? | Reteach, model an answer, or run a diagnostic |
| Subject | Are parallel classes progressing consistently? | Coordinate assessment through the department |
| Cohort | Are patterns appearing across subjects? | Review workload and intervention priorities |
A cohort average can conceal substantial differences. Coordinators should move from broad patterns to the underlying class and student evidence before deciding what action is justified.
How IB cohort tracking should work
Effective IB cohort tracking begins with a defined question. A coordinator should decide whether a review concerns engagement, curriculum coverage, topic mastery, assessment skills, or improvement over time.
RevisionDojo's teacher dashboard and analytics guidance describes assignment results, learning-objective progress, and student strengths and weaknesses. These views can help distinguish between:
- A student difficulty requiring individual support
- A class misconception requiring further teaching
- A subject or cohort pattern requiring departmental action
Prioritize trends across several comparable tasks rather than isolated scores. One low result may reflect absence, unfamiliar content, poor timing, or unusual task difficulty; repeated errors across similar assessments provide stronger evidence.
The IB's official Programme standards and practices requires schools to capture and use data that informs programme operation, sustainability, and implementation. It does not require a particular platform, and RevisionDojo is not an official IB reporting system. Its evidence should be considered alongside teacher assessments, pastoral information, attendance, coursework progress, and school records.
Assigning resources from evidence
Analytics should lead to an instructional response. If a class struggles with one topic, assigning a complete subject paper may create unnecessary workload and obscure the original problem.
A focused sequence is:
- Diagnose: Use a short common task or Questionbank set to locate the gap.
- Explain: Provide relevant Study Notes, videos, or teacher instruction.
- Practise: Assign questions matched to the topic and assessment skill.
- Review: Examine errors, feedback, and completion patterns.
- Retest: Use a fresh but comparable task to check independent improvement.
The RevisionDojo Questionbank supports targeted exam-style practice, while Test Builder can help departments create common diagnostics. Jojo AI can explain ideas and provide feedback, but students should also complete independent tasks so teachers can evaluate unaided performance.
Departments should agree assignment standards, including naming conventions, completion windows, mark-scheme use, and retesting expectations. Shared standards make reports more comparable and prevent uneven digital workloads between classes.
A practical whole-programme rollout
A successful rollout begins with one clear purpose rather than every available feature. A school might first use RevisionDojo to identify gaps after mock examinations, then introduce weekly retrieval practice or coursework feedback once teachers understand the workflow.
Before launch
- Appoint an implementation lead.
- Confirm the programmes, subjects, year groups, and access roles included.
- Review privacy, retention, safeguarding, accessibility, and AI-use requirements.
- Establish consistent class and cohort naming conventions.
- Give departments time to inspect resources.
- Decide what evidence will be reviewed and when.
Schools should request current institutional terms rather than assuming individual subscription conditions apply. The school licensing guide recommends confirming seats, staff permissions, included subjects, provisioning, support, security, contract length, and reporting capabilities.
During the first month
Begin with a short baseline in selected subjects. Teachers can assign focused Study Notes or Questionbank practice, then review results during a departmental meeting.
Weekly reviews may suit teachers during an intervention, while monthly meetings are often more appropriate for programme-level patterns. The aim is timely action, not continuous surveillance. The guide to coordinator-led progress tracking recommends defining priorities before generating reports so meetings focus on decisions rather than large quantities of descriptive data.
Common assessments and mock examinations
Common assessments support comparison when classes have completed similar teaching under consistent conditions. Departments must align the task, timing, permitted support, and marking approach before comparing outcomes.
Full mocks should be treated as diagnostic evidence rather than final judgements. RevisionDojo's guide to using IB mock exams recommends identifying where marks were lost and retesting targeted weaknesses after further practice.
Predicted Papers can develop timing, stamina, and exam technique, but they are simulations rather than guarantees of examination content. Departments must not narrow teaching or omit published syllabus content. Official examination administration, secure materials, predicted grades, and submitted assessment remain governed by IB rules and school policy.
Governance, academic integrity, and responsible AI
Any IB school software must operate within school governance. Before students use Jojo AI or coursework feedback, leaders should define acceptable assistance, explain when AI use must be acknowledged, and ensure submitted work remains authentic.
The IB's academic integrity policy requires schools to teach academic integrity, apply policies consistently, and communicate expectations. RevisionDojo feedback should support revision, not replace teacher supervision or supply text for students to submit as their own.
Access should follow role and necessity. Schools should confirm permissions, retention arrangements, export options, and deletion procedures during procurement rather than assuming every feature is included in every plan.
Turning dashboard information into decisions
A coordinator meeting should end with a recorded action. For each pattern, identify the evidence, responsible staff member, response, review date, and success measure.
If several history classes show weak evaluation, the department might teach a shared modelling lesson and compare performance on a later task. If only three students show the weakness, individual support is more proportionate. The whole-school analytics guide explains how shared information can reveal engagement gaps and differences between classes, but dashboard indicators should never become automatic judgements about students or teachers.
Conclusion
RevisionDojo for IB coordinators is most effective as a structured improvement system rather than a passive resource library. Coordinators should define an objective, establish a baseline, agree common practices, and interpret trends using multiple sources of evidence. RevisionDojo for Schools, Questionbank, Test Builder, Study Notes, Mock Exams, Jojo AI, and analytics can support this consistent programme-wide cycle.
Sources and referenced URLs
- RevisionDojo for Schools
- RevisionDojo teacher dashboard and analytics guide
- RevisionDojo IB Questionbank
- RevisionDojo for IB schools licensing guide
- How coordinators can track student progress
- RevisionDojo guide to IB mock exams
- Whole-school improvement through RevisionDojo analytics
- IB Programme standards and practices
- IB academic integrity policy
