An IB self-study report should be a candid, school-wide evaluation of how consistently the Diploma Programme is implemented. It is not a document for the DP coordinator to write alone shortly before submission. A strong process distributes reflection across stakeholders, tests conclusions against evidence, and turns findings into programme development.
Schools must use the current self-study questionnaire, programme development materials, and instructions provided for their evaluation cycle. Coordinators should obtain these through the Programme Resource Centre and direct IB communications rather than relying on an older template found online.
Understand the purpose of the IB self-study report
The term IB self-study report commonly refers to the completed questionnaire and related programme development documentation. It allows the school community to evaluate implementation against the current Programme standards and practices, or PSP.
The official Programme standards and practices organize implementation into four connected categories:
| PSP category | Central question |
|---|---|
| Purpose | Do the school's mission, strategy, and decisions align with IB philosophy? |
| Environment | Do leadership, staffing, time, facilities, and resources sustain the programme? |
| Culture | Are inclusion, language, integrity, well-being, assessment, and access embedded in practice? |
| Learning | Do curriculum, teaching, assessment, collaboration, and student agency support learning? |
The objective is not to prove that every practice is exceptional. The report should confirm which requirements are in place, identify achievements, evaluate development, and acknowledge areas requiring attention. An unrealistically positive account may suggest that the school has not reflected critically.
Programme evaluation also includes a preliminary review of required documentation. Depending on the arrangements communicated to the school, evaluation may involve a visit or a DP evaluation reading. The IB's programme evaluation nano resources explain the broad process, but the school's current instructions remain decisive.
Establish governance and delegate responsibility
The DP coordinator normally manages the process but should not become its sole author. School leadership must provide authority, protected time, administrative support, and access to institutional records.
Create a steering group that includes the coordinator, a senior leader, curriculum representatives, core leaders, and staff responsible for areas such as inclusion, language, counselling, assessment, or library provision. An administrator can manage permissions, files, and version control. The head of school should remain involved throughout and verify institutional accuracy before submission.
Use a responsibility matrix that distinguishes the evidence owner, discussion leader, draft writer, and approver. This prevents one person from choosing the evidence, making the judgement, writing the conclusion, and approving it without challenge.
Working groups can be aligned with Purpose, Environment, Culture, and Learning. Larger schools may divide Learning into curriculum, teaching, assessment, and approaches to teaching and learning. Each group should have a facilitator and recorder and use the same sequence:
- Identify the relevant practice and programme requirements.
- Review evidence before selecting a judgement.
- Apply the descriptors in the current questionnaire.
- Explain the judgement in school-specific language.
- Record achievements, challenges, and disagreement.
- Propose an action, owner, and review point.
Teams should reach a provisional judgement before drafting polished prose. Otherwise, confident writers can determine the conclusion before quieter stakeholders contribute.
Build a realistic preparation timeline
The formal schedule depends on the school's confirmed evaluation arrangements. A 9-12 month internal timeline is practical for many schools, but it is advice rather than a universal IB deadline.
| Time before submission | Main work |
|---|---|
| 9-12 months | Confirm documents, form the steering group, review previous findings, and assign responsibilities |
| 6-9 months | Audit required documentation, brief stakeholders, and identify evidence gaps |
| 3-6 months | Hold working-group discussions, surveys, interviews, and evidence reviews |
| 2-3 months | Draft responses, moderate judgements, and complete programme development reflection |
| 4-8 weeks | Verify claims, edit for consistency, review permissions, and obtain leadership approval |
| Final 1-2 weeks | Complete platform entry, test files and links, approve, and submit |
Protect meetings in the school calendar. When staff are expected to complete the process through voluntary after-school work, participation and analysis are usually uneven. Programme evaluation is an institutional responsibility and should receive institutional time.
Gather focused evidence and stakeholder perspectives
Evidence should show what the school routinely does and how stakeholders experience it. A policy proves that a document exists, but it does not prove that staff understand it or that implementation is consistent.
Useful evidence includes:
- previous authorization or evaluation findings and the school's response
- policies, revision records, strategic plans, and governance minutes
- staffing, budget, timetable, resource, and professional development records
- curriculum maps, course plans, and collaborative planning records
- assessment calendars, standardization notes, and samples of feedback
- aggregated achievement, participation, attendance, and access data
- student, parent, teacher, and support-staff feedback
- CAS, TOK, and EE monitoring systems
- records showing that concerns produced action and later review
Maintain an evidence register containing the PSP practice, item title, owner, date, location, access level, and what the item demonstrates. Do not upload material merely because it exists. Evidence used internally is not necessarily evidence the IB asks the school to submit.
Participation should extend beyond teachers. Use short surveys to identify broad patterns, focus groups to explore causes, department meetings to examine curriculum, and student panels to discuss workload, agency, support, and feedback. Ask experience-based questions. For example, ask students how academic integrity is taught or whether deadlines are coordinated, rather than asking whether the DP is generally effective.
Record underrepresented perspectives and examine disagreement. If leaders believe collaborative planning is secure but teachers report insufficient scheduled time, the report should investigate that difference rather than average it away.
Digital analytics may supplement this evidence. The RevisionDojo guide for IB coordinators explains how cohort patterns can be considered alongside student work, teacher assessment, and pastoral information. Platform data are not an official IB judgement and still require professional interpretation.
Write analytical responses and moderate judgements
A defensible response connects claim, evidence, interpretation, and action. Consider this example:
Departments meet twice monthly, and minutes show regular discussion of assessment and student progress. Cross-subject planning involving TOK occurred inconsistently, however. The school therefore considers departmental collaboration established but programme-wide collaboration an area for development. One monthly meeting will now be reserved for cross-programme planning, with resulting curriculum changes reviewed each semester.
This is stronger than stating that teachers collaborate regularly. It acknowledges variation, identifies the evidence, and explains the planned response without claiming that meeting frequency alone improves learning.
Before finalizing a judgement, ask whether the requirement is demonstrably in place, whether implementation is consistent across subjects and both DP years, and whether stakeholders support the claim. Teams should also identify what has changed and what remains fragile or dependent on one person.
The IB PSP at-a-glance visual helps introduce the connected framework to staff. Detailed judgements must still use the complete PSP and programme-specific requirements.
Moderation is essential because teams may interpret descriptors differently. Ask each group to defend one strong judgement and one area for development. Reviewers should check internal consistency between ratings and explanations, cross-section consistency between categories, and operational consistency between policies and practice.
For assessment culture, evidence of shared criteria, anchor samples, and recorded moderation may be useful. RevisionDojo's guide to standardizing internal assessments across departments provides a practical model, although current IB subject guidance always takes priority.
Connect findings to programme development
Programme development turns reflection into sustained improvement. A useful plan identifies a focused need, relevant PSP practices, intended benefits for students, baseline evidence, responsibilities, dates, indicators of progress, and opportunities for review.
For example, a school might investigate whether coordinated formative assessment improves students' use of feedback. Departments could establish a baseline, introduce a shared routine, compare student work, and evaluate changes through interviews and assessment evidence.
RevisionDojo's resources on data-informed school improvement and whole-school IB improvement illustrate evidence-led review. Any analytics should be triangulated with student work, observations, stakeholder feedback, and teacher judgement.
Avoid common mistakes and complete final checks
Common weaknesses include allowing the coordinator to write everything, rating before reviewing evidence, treating policies as proof of implementation, using outdated PSP language, collecting irrelevant files, excluding stakeholders, and describing activities without evaluating their effects. Schools should also avoid hiding contradictions or leaving platform entry until the deadline.
Before submission, reviewers who did not draft each section should verify terminology, dates, factual claims, evidence references, and alignment between judgements and explanations. Confirm that every required field is complete, confidential information is handled appropriately, links work for authorized readers, programme development is documented, and the head of school has approved the final version.
Submit early enough to resolve technical problems. Retain a controlled final copy, evidence register, stakeholder findings, meeting records, and agreed actions so that development continues after evaluation.
Conclusion
A credible IB self-study report depends on distributed leadership, focused evidence, honest moderation, and clear programme development priorities. The coordinator designs and quality-assures the process, while the wider school community contributes the perspectives needed to evaluate implementation accurately.
RevisionDojo can support evidence collection through consistent assessment workflows and cohort analytics, but these remain supplementary school evidence. Coordinators seeking a clearer evidence trail can explore RevisionDojo for Schools and use Questionbank diagnostics selectively within the school's broader evaluation system.
Sources and referenced URLs
- IB Programme standards and practices 2020
- IB Programme standards and practices at a glance
- IB programme evaluation nano resources
- RevisionDojo for IB coordinators
- RevisionDojo and data-informed school improvement
- Coordinating whole-school IB improvement
- Standardizing internal assessments across departments
- RevisionDojo for Schools
