The IB Middle Years Programme Personal Project is, on paper, a straightforward assessment. A student works independently for approximately 25 hours over the course of Year 10, produces a product of their choosing, keeps a process journal throughout, and writes a report. Simple enough. In practice, supervising 20 or more Personal Projects simultaneously is one of the most logistically demanding tasks a teacher takes on, and the official IBO guide runs to more than 50 pages before the student has written a single word.
This guide strips away the policy language and gives you the practical version. What does a supervisor actually do? How do you help students narrow topics without writing their project for them? How do you manage 20 students at different stages of 20 completely different projects without losing track? And how do you get students to produce genuine reflection rather than a diary of events? Those are the questions this guide answers.
The Personal Project is a compulsory component of the IB Middle Years Programme completed by students in Year 10 (MYP Year 5). Every student produces three things: a process journal kept throughout the project, a product (which can be almost anything), and a report of 1,500 to 3,500 words that demonstrates their learning across all four assessment criteria. The total guided time is approximately 25 hours, though many students invest considerably more.
The product itself is deliberately open. Students have produced novels, websites, sculptures, business plans, documentary films, performances, social media campaigns, cookbooks, engineering prototypes, and community events. The IBO does not value one product type over another. What it assesses is the quality of the thinking process that produced the product, not the product itself. This distinction matters enormously and needs repeating to students, parents, and new supervisors throughout the year.
Assessment uses four criteria, each worth a maximum of eight marks:
| Criterion | Focus | What the student must demonstrate |
|---|---|---|
| A: Investigating | Goal, prior learning, research | A clear goal, understanding of existing knowledge, a range of research sources used critically |
| B: Planning | Design, milestones, self-management | A realistic plan with success criteria, evidence of self-management, adjustments made in response to challenges |
| C: Taking Action | Skills, thinking, product creation | ATL skills applied to the creation of the product, evidence of thinking about decisions made |
| D: Reflecting | Product quality, personal growth | Honest evaluation of the product against the original goal, reflection on what the project revealed about the student as a learner |
The criteria are cumulative in the sense that a weak Criterion A (a vague goal) makes every subsequent criterion harder to achieve. Students who define a clear, specific, measurable goal in September write better plans in October, produce more coherent products, and have more to reflect on in April. Supervisors who invest time in Criterion A early save students and themselves significant difficulty later.
The single most common reason for a low Criterion A mark is a topic that is too broad. "I want to investigate climate change." "My project is about mental health." "I'm going to write about sport." These are not goals; they are areas. A goal is specific, product-linked, and achievable in 25 hours. "I will design and produce a 20-page illustrated guide to reducing food waste for secondary school students" is a goal. "Climate change" is not.
The most reliable tool for narrowing a topic is the Thinking Framework's Part-Whole operation. Teach students to ask: what are the main components of this broad area? Then: which single component is both interesting to me and specific enough to investigate thoroughly? A student interested in "sport" maps the components: physical training, nutrition, psychology, history, economics, equipment design, inclusion, community impact. They choose "the psychology of performance anxiety in junior athletes" and the goal becomes achievable. The Thinking Framework operations are particularly powerful here because they give students a structured thinking process rather than an instruction to "be more specific."
Research skills are assessed under Criterion A, not separately. Students need to demonstrate that they have identified and used a range of sources, evaluated their reliability, and connected their research to their goal. Common problems: students rely on Wikipedia or the first three Google results, do not explain why they chose particular sources, and treat research as a list of facts rather than as evidence for a developing argument. Supervisors should ask at the first check-in: "Where did you find this? How do you know this source is reliable? What does this tell you about your goal that you didn't know before?"
Criterion A also asks students to explain their prior learning, specifically, what prior knowledge or experience connects them to this topic. This is often misunderstood as biographical background ("I have always liked art"). What the IBO wants is a connection between the student's existing MYP learning and the new investigation: "My study of biology in MYP Year 4 gave me an understanding of nutrition that I will apply to my investigation of plant-based diets for athletes." That sentence demonstrates prior learning. A list of personal interests does not.
Criterion B assesses whether the student can design a realistic plan, set success criteria, and demonstrate self-management over the course of the project. The planning template you provide students directly shapes the quality of what they produce. Vague prompts produce vague plans. A structured planning document produces plans that are actually usable.
The most effective planning tool for Year 10 students is a fortnightly milestone chart mapped against the 25 hours. Use the Thinking Framework's Sequence operation to do this explicitly: "What are the steps from where you are now to a finished product? Put them in order. Estimate how long each step will take. Now count up the total. Does it fit in 25 hours?" Most students discover their first plan is either massively over-ambitious or, less commonly, far too sparse. The planning conversation is where this becomes visible, not at submission.
| Fortnightly milestone | Target activity | Hours |
|---|---|---|
| September (week 4) | Topic area identified, goal drafted | 2 |
| October (week 2) | Research complete, sources evaluated | 4 |
| October (week 4) | Goal finalised, success criteria written, plan approved | 2 |
| November (weeks 2–4) | Product creation begins, journal entries recorded | 6 |
| December (week 2) | Mid-point review: product halfway complete, plan adjusted | 3 |
| January (weeks 1–3) | Product creation completed | 4 |
| February (weeks 1–2) | Report Criteria A and B written | 2 |
| February (weeks 3–4) | Report Criteria C and D written | 2 |
Success criteria deserve more attention than they typically receive. Many students write success criteria that are essentially descriptions of the product: "My website will have five pages and a contact form." This is not a success criterion; it is a specification. A success criterion answers the question "how will I know if this is good?" For the website example: "A reader with no prior knowledge of this topic will be able to explain the three main arguments after reading the site." That is a standard you can evaluate against. Teach students the difference between specification and evaluation criteria before they start planning.
Criterion B also assesses self-management, specifically whether the student adjusted their plan when things did not go as expected. Supervisors who check in fortnightly and ask "what has changed since last time? What did you need to adjust?" give students the language and the evidence to write about self-management genuinely. Students who never adjusted their plan have either had a frictionless project (unlikely) or never noticed when they deviated from it (common). Metacognitive awareness of one's own planning process is precisely what Criterion B rewards.
Criterion C is where the product gets made. It assesses whether the student applied relevant skills, demonstrated thinking throughout the creation process, and connected their ATL skills to the decisions they made. Students often conflate Criterion C with "doing the project," but the criterion is about how the student thought while they were doing it, not just what they produced.
The most useful prompt for Criterion C is the Compare operation from the critical thinking repertoire: "At this point in your project, you had two options. What were they? How did you compare them? Why did you choose one over the other?" Students who can articulate that they considered multiple approaches and made a reasoned choice produce much stronger Criterion C evidence than students who describe what they did without explaining why. The decision log is the evidence; the product is merely the outcome of those decisions.
ATL skills assessed under Criterion C include thinking skills, communication skills, research skills, self-management skills, and social skills. Students need to name the skill and provide evidence of using it. "I used thinking skills" is not evidence. "When my first design prototype did not meet my success criterion for accessibility, I used systems thinking to identify which elements of the design needed to change and in what order" is evidence. Supervisors should train students to use this structure: skill name, specific situation, what the student actually did.
The ATL skills framework maps directly onto the five skill categories assessed in Criterion C. Students who are familiar with ATL from their MYP subjects have an immediate advantage here because they can name their thinking processes using a shared vocabulary. If your school uses the ATL skills planning approach described in our teacher guide, students will already have practice connecting cognitive operations to specific tasks. This is exactly what Criterion C requires.
Self-assessment checkpoints throughout the process, not just at the end, are essential for Criterion C evidence. A simple fortnightly prompt works well: "Compare your product as it stands today with your success criteria. What matches? What does not yet match? What will you do differently in the next two weeks?" Students who complete this prompt fortnightly have a Criterion C evidence bank by submission time. Students who reflect only at the end are reconstructing rather than reporting.
Criterion D is the most frequently under-achieving criterion, and it is almost entirely within the supervisor's control to change this. The reason students underperform on Criterion D is not that they lack the capacity to reflect; it is that no one has taught them how. Left without a framework, most 15-year-olds write a description of what happened. What they need is a structure for evaluating what happened and connecting it to their development as learners.
Gibbs' Reflective Cycle (Gibbs, 1988) is the most widely used reflective framework in education for good reason: it provides a sequence of prompts that take a student from description through analysis to future planning. Adapted for Year 10 students, the cycle has five stages: description ("what did I do and what happened?"), feelings ("how did I feel about this?"), evaluation ("what went well and what went less well?"), analysis ("why did this happen? what does the research say about this?"), and future application ("what would I do differently? what have I learned about myself as a learner?"). The IBO's Criterion D descriptors map almost precisely onto the Gibbs stages.
The most important Criterion D question is the one directly connected to the IB Learner Profile: "What did you learn about yourself as a learner?" This question requires students to move from describing the project to reflecting on their own cognitive and personal development. A student who writes "I learned that I need to start earlier" has described a logistical observation. A student who writes "I learned that I underestimate how long research takes because I conflate reading with understanding. I can read a source quickly, but extracting and evaluating its argument takes three times as long. This changed how I plan all my academic work" has genuinely reflected on themselves as a learner. That is a high-band Criterion D response.
Criterion D also asks students to evaluate the quality of the product against the original success criteria. This is where the investment in good success criteria in September pays off. A student who wrote measurable, evaluable success criteria in Criterion B can now systematically assess whether their product met each one, explain why it did or did not, and identify what they would change with more time. A student whose success criteria were vague has nothing specific to evaluate against and defaults to global statements ("I think it turned out well").
Introduce Gibbs' Reflective Cycle in September alongside the project introduction, not in March when report writing begins. Give students a one-page template with the five stages and a worked example using a fictional project. Then practise the cycle during check-ins: "Let's do a quick Gibbs on the research you did this week. What happened? How did you feel about it? What worked? Why do you think it worked?" The cycle is a habit that needs to be practised across the year, not a framework introduced at the point of assessment.
The logistical challenge of supervising a cohort of Personal Projects is the aspect of the role that least experienced supervisors find hardest. You are responsible for 20 or more students, each on a completely different topic, at potentially different stages of the process, with different strengths and very different levels of self-management. Monthly one-to-one meetings for 20 students would consume four or five hours a month before you factor in preparation. That is unsustainable alongside a full teaching timetable.
The solution is not longer meetings but more frequent, shorter ones. A three-minute standing check-in at the start of a lesson or during registration accomplishes most of what a 30-minute meeting accomplishes, if the student comes prepared. The rule: every student completes a fortnightly progress card before meeting the supervisor. The card has three fields: what I have done since the last check-in, what I plan to do before the next check-in, and one thing I am stuck on or uncertain about. The supervisor reads the card in 30 seconds and the conversation is focused immediately.
Tracking 20 projects requires a simple spreadsheet, not a complex system. Five columns are enough: student name, current criterion focus, last check-in date, next check-in date, and a brief status note. Update it after every contact. Colour-code by RAG (red: at risk, amber: progressing but needs attention, green: on track). This takes less than two minutes per student per fortnight and means you are never surprised by a student who has done nothing for six weeks.
The Thinking Framework provides a shared vocabulary across all 20 projects, which is the real reason it is worth introducing at the start of the year. When every student knows what Compare, Sequence, Part-Whole, and Perspective mean as cognitive operations, your check-in questions become reusable across completely different project types. "Which Thinking Framework operation did you use this week? Show me how." Works for the student writing a novel and the student building a prototype circuit in the same check-in round. The Thinking Framework is the supervisor's efficiency tool, not just the student's thinking scaffold.
Stagger start dates by one week between form groups or tutor groups where possible. If all 20 students submit their goal statements on the same day, you face a marking pile. If group A submits in week 3 of September and group B submits in week 4, you have a manageable spread. The same logic applies to plan approvals, mid-point reviews, and draft report feedback. Small administrative decisions in September save significant time in February.
The process journal is, in the experience of most MYP coordinators, the most misunderstood element of the Personal Project. Students routinely produce journals that are detailed diaries of activity and almost entirely devoid of thinking. "On Monday I looked at three websites about nutrition. On Wednesday I started writing my plan." This is a log. It is not a process journal. It will not contribute meaningfully to any criterion.
A process journal is a record of thinking in progress. It captures decisions made and the reasoning behind them, problems encountered and how they were addressed, connections made between research and the evolving product, and moments of uncertainty or insight. The test for any journal entry is: if a stranger read this, would they understand how this student thinks, not just what they did?
| Weak entry (diary) | Strong entry (process journal) |
|---|---|
| Today I researched food waste. I found some interesting statistics about how much food is wasted each year. | I compared two sources on food waste statistics. The WRAP report (2019) focuses on household waste; the FAO (2011) report includes the whole supply chain. I decided my guide should focus on the point of consumption, not production, because my audience is secondary students who have no control over supply chain decisions. |
| I changed my plan because I wasn't making enough progress. | My original plan had the illustrated sections completed by week 6, but I have only completed two of five. I identified two causes: I underestimated illustration time (each takes 90 minutes, not 45) and I spent two sessions re-researching after finding conflicting information. I adjusted the timeline by removing one illustration and adding a written explanatory section instead, which is faster to produce and still meets my success criteria for clarity. |
| I used communication skills this week. | I tested my guide with a Year 8 student to check whether the language was accessible. She understood the main argument but was confused by the term "embodied carbon." I revised that section to use "the carbon produced during manufacturing" instead. This feedback loop improved the clarity of my writing for the target audience. |
Show these examples to students in September. Show them again in November. The diary instinct is strong. Many students have been praised for detailed diaries in junior school and do not understand why the same approach fails at MYP5. Naming the distinction explicitly, with side-by-side examples, changes behaviour more reliably than any amount of general guidance about "reflecting on your thinking."
The format of the process journal is flexible. It can be handwritten, digital, audio recorded, visual, or a combination. The IBO does not specify a format. Some students produce beautiful sketchbook journals with annotations. Others keep a running document with dated entries. Some use bullet points; others write paragraphs. The format is irrelevant. The presence of thinking is what matters.
Most Personal Project failures are predictable and preventable. They fall into four categories, and supervisors who know them in advance can build countermeasures into the supervision schedule from the start.
Starting too late. Students who begin active work in January face a compressed timeline that makes genuine research, iterative product development, and meaningful reflection impossible. The project becomes a scramble rather than an inquiry. The countermeasure is structural: require a topic exploration document in September, a goal statement in October, and a plan approval in November. Students who have not submitted these documents by the deadlines should have a conversation with the supervisor, not a reminder email. Three minutes of direct conversation is more effective than three email reminders. The task avoidance research is clear on this: avoidance is driven by anxiety about getting started, not by lack of motivation. A supervisor who normalises starting early removes the psychological barrier.
Choosing a topic they cannot access. A student who wants to investigate the experience of refugees but has no access to refugees, no relevant contacts, and no appropriate way to conduct primary research has chosen a topic they cannot investigate properly. The same applies to topics that require equipment, access, or expertise the student does not have. Supervisors should ask at goal-setting: "How will you actually investigate this? What sources are available to you? What can you do that no one else has done?" If the answer is "I'll search the internet," the topic needs revision.
Product versus process imbalance. Students who fall in love with their product and forget to document their thinking produce polished products and weak reports. The supervision check-in is the corrective: "Your product is looking good. Show me three process journal entries from the last two weeks that explain a decision you made." If the student cannot produce them, they have a problem that needs addressing now, not at submission.
Plagiarism in the digital age. AI-generated text is now a serious concern in Personal Project reports, particularly in the reflective sections. The IBO's academic integrity policy applies, and supervisors are in the best position to detect voice inconsistency between check-in conversations and written submissions. A student who speaks tentatively about their project in check-ins and submits a report with confident, polished academic prose has almost certainly received inappropriate assistance. Familiarity with each student's voice, developed through regular check-ins, is the most reliable detection mechanism available to supervisors.
Parent communication about the Personal Project is where schools create problems they then spend the year managing. Parents, understandably, want their children to do well. Many parents interpret "your child is responsible for this project" as "you should help your child with this project." The result is projects that are competently organised by a parent and weakly owned by the student. Parents who write their child's goal statement, structure their research, or produce elements of the product are actively harming their child's Criterion A, B, and C marks, because the evidence of the student's own thinking will be absent.
The parent communication letter should address three things directly. First, the supervisor's role: the supervisor checks in fortnightly, provides formative feedback, and ensures the student is on track. The supervisor does not direct the project, correct the work, or tell the student what to do. Second, the student's independence requirement: the Personal Project is an assessment of the student's independent thinking and self-management. Third, where parents can help. Parents can provide logistical support (buying materials, driving to a location for research, providing access to a printer), moral support (showing interest, creating time and space for the student to work), and accountability (asking "did you do your project work today?" without asking "shall I help you with it?"). Parents who understand the distinction between logistical support and academic assistance are genuinely helpful. Those who do not can undermine months of the student's work in a single weekend.
Send the parent communication in September at the project launch, not in February when the work is underway. A parent who understands the project from the start is a supervisor's ally. A parent who only hears about it when their child is panicking in February is a variable that is much harder to manage.
The Personal Project outcome in May is almost entirely determined by decisions made in September. Schools that treat the project as something students do in the second half of the year produce weaker projects than schools that begin concept development in the first week of term. The September setup takes approximately three timetabled hours across the year group, and it returns those hours many times over in reduced crisis management and stronger student outcomes.
The sequence from September to May should look like this:
September: Introduce the project concept. Show examples of strong and weak projects from previous years (with names removed). Explain the four criteria in plain language. Give students the Part-Whole brainstorming tool and ask them to generate five possible topic areas. No commitment required; this is exploration. Introduce the Thinking Framework operations students will use throughout the project. Assign the first process journal entry: "Write about a topic area you are considering and why it interests you."
October: Topic exploration deepens. Students narrow from five areas to two using the Part-Whole operation. First supervisor check-in. Goal statement drafted. Research begins. Students evaluate two sources using the Compare operation and write a process journal entry about the comparison.
November: Goal statement finalised and approved by supervisor. Success criteria written. Planning timeline completed. Plan formally approved before the end of the month. This is the critical gate: no student should begin creating their product without a supervisor-approved plan. Students who skip this gate almost always struggle with Criterion B.
December: Product creation begins. Fortnightly check-ins continue. Mid-point review at the end of term: product is assessed against success criteria for the first time. Adjustments to the plan are documented. The scaffolding the supervisor provides here, structured prompts rather than direct instruction, determines how independently students develop their self-management skills.
January to March: Product creation completed. Report writing begins in February with Criteria A and B. Criteria C and D written in late February and early March. Draft report submitted to supervisor. Formative feedback given. Students revise. The reflection sections take longer than students expect; build two full weeks for Criterion D.
April: Final report submission. In some schools, students also present their project to a panel. If your school includes a presentation, allow two weeks between final report submission and the presentation so students can prepare without compressing report writing time.
May: Moderation and submission to the IBO. Supervisors should have reviewed all projects before submission and confirmed that product, process journal, and report are all present and complete. Missing components are a moderation risk that is entirely preventable with a submission checklist.
The executive function demands of the Personal Project are significant for every student, not just those with identified learning differences. Self-directed work over eight months, with infrequent formal checkpoints, requires planning, monitoring, and self-correction at a level many 15-year-olds are still developing. Supervisors who build external structure into the process through regular check-ins, milestone documents, and reflection prompts are not reducing the intellectual challenge of the project. They are providing the scaffolding that allows students to work at the edge of their current capability rather than collapsing under the weight of open-endedness.
The International Baccalaureate Personal Project is, when supervised well, one of the most valuable learning experiences a secondary student can have. It develops research skills, self-management, reflective practice, and the capacity to pursue a goal independently over an extended period. These are not just IB competencies; they are the skills that distinguish high-performing students across every academic pathway that follows. The supervisor's role is not to manage the project for the student but to build the conditions in which the student can manage it for themselves.
These studies underpin the supervisory strategies described in this guide.
Self-Regulated Learning and Academic Achievement: An Overview View study ↗
Zimmerman, B. J. (2002). Educational Psychologist.
Zimmerman's overview of self-regulated learning shows that students who monitor their progress in short cycles and adjust their strategies outperform those who rely on end-point assessment alone. This finding directly supports the fortnightly check-in model for Personal Project supervision and explains why students with weak self-monitoring skills need external structure rather than simply more time.
Metacognition and Learning: Conceptual and Methodological Considerations View study ↗
Flavell, J. H. (1979). Developmental Psychology.
Flavell's foundational work on metacognition establishes that awareness of one's own cognitive processes is learnable and developable. For Personal Project supervisors, this means that process journal prompts which ask students to name their thinking operations are not a bureaucratic requirement but a genuine intervention in developing their capacity for independent academic work.
Improving Secondary Pupils' Engagement with Reflective Writing View study ↗
Gibbs, G. (1988). Oxford Polytechnic: Oxford. (Adapted discussions in: Assessment and Evaluation in Higher Education)
The research base on structured reflective frameworks consistently shows that students produce more substantive reflection when given a sequence of prompts than when asked to reflect openly. The Gibbs Cycle's five-stage structure, adapted for secondary students, produces measurably richer Criterion D responses than unstructured journal writing alone.
Improving Secondary Students' Metacognitive Skills View study ↗
Education Endowment Foundation (2018). Metacognition and Self-Regulated Learning.
The EEF guidance report on metacognition identifies explicit teaching of planning, monitoring, and evaluation strategies as having a high impact (equivalent to an additional seven months of progress) at relatively low cost. For Personal Project supervisors, this positions the check-in model and structured reflection frameworks not as administrative overhead but as high-impact pedagogical interventions.
MYP: From Principles into Practice View study ↗
IB Organisation (2014). International Baccalaureate Organisation: Geneva.
The IBO's own framework document sets out the design principles behind the Personal Project, including the emphasis on student agency, the role of the ATL skills, and the importance of the process over the product. Reading the official framework alongside this practical guide helps supervisors understand which flexibilities are genuine and which constraints are non-negotiable.
The IB Middle Years Programme Personal Project is, on paper, a straightforward assessment. A student works independently for approximately 25 hours over the course of Year 10, produces a product of their choosing, keeps a process journal throughout, and writes a report. Simple enough. In practice, supervising 20 or more Personal Projects simultaneously is one of the most logistically demanding tasks a teacher takes on, and the official IBO guide runs to more than 50 pages before the student has written a single word.
This guide strips away the policy language and gives you the practical version. What does a supervisor actually do? How do you help students narrow topics without writing their project for them? How do you manage 20 students at different stages of 20 completely different projects without losing track? And how do you get students to produce genuine reflection rather than a diary of events? Those are the questions this guide answers.
The Personal Project is a compulsory component of the IB Middle Years Programme completed by students in Year 10 (MYP Year 5). Every student produces three things: a process journal kept throughout the project, a product (which can be almost anything), and a report of 1,500 to 3,500 words that demonstrates their learning across all four assessment criteria. The total guided time is approximately 25 hours, though many students invest considerably more.
The product itself is deliberately open. Students have produced novels, websites, sculptures, business plans, documentary films, performances, social media campaigns, cookbooks, engineering prototypes, and community events. The IBO does not value one product type over another. What it assesses is the quality of the thinking process that produced the product, not the product itself. This distinction matters enormously and needs repeating to students, parents, and new supervisors throughout the year.
Assessment uses four criteria, each worth a maximum of eight marks:
| Criterion | Focus | What the student must demonstrate |
|---|---|---|
| A: Investigating | Goal, prior learning, research | A clear goal, understanding of existing knowledge, a range of research sources used critically |
| B: Planning | Design, milestones, self-management | A realistic plan with success criteria, evidence of self-management, adjustments made in response to challenges |
| C: Taking Action | Skills, thinking, product creation | ATL skills applied to the creation of the product, evidence of thinking about decisions made |
| D: Reflecting | Product quality, personal growth | Honest evaluation of the product against the original goal, reflection on what the project revealed about the student as a learner |
The criteria are cumulative in the sense that a weak Criterion A (a vague goal) makes every subsequent criterion harder to achieve. Students who define a clear, specific, measurable goal in September write better plans in October, produce more coherent products, and have more to reflect on in April. Supervisors who invest time in Criterion A early save students and themselves significant difficulty later.
The single most common reason for a low Criterion A mark is a topic that is too broad. "I want to investigate climate change." "My project is about mental health." "I'm going to write about sport." These are not goals; they are areas. A goal is specific, product-linked, and achievable in 25 hours. "I will design and produce a 20-page illustrated guide to reducing food waste for secondary school students" is a goal. "Climate change" is not.
The most reliable tool for narrowing a topic is the Thinking Framework's Part-Whole operation. Teach students to ask: what are the main components of this broad area? Then: which single component is both interesting to me and specific enough to investigate thoroughly? A student interested in "sport" maps the components: physical training, nutrition, psychology, history, economics, equipment design, inclusion, community impact. They choose "the psychology of performance anxiety in junior athletes" and the goal becomes achievable. The Thinking Framework operations are particularly powerful here because they give students a structured thinking process rather than an instruction to "be more specific."
Research skills are assessed under Criterion A, not separately. Students need to demonstrate that they have identified and used a range of sources, evaluated their reliability, and connected their research to their goal. Common problems: students rely on Wikipedia or the first three Google results, do not explain why they chose particular sources, and treat research as a list of facts rather than as evidence for a developing argument. Supervisors should ask at the first check-in: "Where did you find this? How do you know this source is reliable? What does this tell you about your goal that you didn't know before?"
Criterion A also asks students to explain their prior learning, specifically, what prior knowledge or experience connects them to this topic. This is often misunderstood as biographical background ("I have always liked art"). What the IBO wants is a connection between the student's existing MYP learning and the new investigation: "My study of biology in MYP Year 4 gave me an understanding of nutrition that I will apply to my investigation of plant-based diets for athletes." That sentence demonstrates prior learning. A list of personal interests does not.
Criterion B assesses whether the student can design a realistic plan, set success criteria, and demonstrate self-management over the course of the project. The planning template you provide students directly shapes the quality of what they produce. Vague prompts produce vague plans. A structured planning document produces plans that are actually usable.
The most effective planning tool for Year 10 students is a fortnightly milestone chart mapped against the 25 hours. Use the Thinking Framework's Sequence operation to do this explicitly: "What are the steps from where you are now to a finished product? Put them in order. Estimate how long each step will take. Now count up the total. Does it fit in 25 hours?" Most students discover their first plan is either massively over-ambitious or, less commonly, far too sparse. The planning conversation is where this becomes visible, not at submission.
| Fortnightly milestone | Target activity | Hours |
|---|---|---|
| September (week 4) | Topic area identified, goal drafted | 2 |
| October (week 2) | Research complete, sources evaluated | 4 |
| October (week 4) | Goal finalised, success criteria written, plan approved | 2 |
| November (weeks 2–4) | Product creation begins, journal entries recorded | 6 |
| December (week 2) | Mid-point review: product halfway complete, plan adjusted | 3 |
| January (weeks 1–3) | Product creation completed | 4 |
| February (weeks 1–2) | Report Criteria A and B written | 2 |
| February (weeks 3–4) | Report Criteria C and D written | 2 |
Success criteria deserve more attention than they typically receive. Many students write success criteria that are essentially descriptions of the product: "My website will have five pages and a contact form." This is not a success criterion; it is a specification. A success criterion answers the question "how will I know if this is good?" For the website example: "A reader with no prior knowledge of this topic will be able to explain the three main arguments after reading the site." That is a standard you can evaluate against. Teach students the difference between specification and evaluation criteria before they start planning.
Criterion B also assesses self-management, specifically whether the student adjusted their plan when things did not go as expected. Supervisors who check in fortnightly and ask "what has changed since last time? What did you need to adjust?" give students the language and the evidence to write about self-management genuinely. Students who never adjusted their plan have either had a frictionless project (unlikely) or never noticed when they deviated from it (common). Metacognitive awareness of one's own planning process is precisely what Criterion B rewards.
Criterion C is where the product gets made. It assesses whether the student applied relevant skills, demonstrated thinking throughout the creation process, and connected their ATL skills to the decisions they made. Students often conflate Criterion C with "doing the project," but the criterion is about how the student thought while they were doing it, not just what they produced.
The most useful prompt for Criterion C is the Compare operation from the critical thinking repertoire: "At this point in your project, you had two options. What were they? How did you compare them? Why did you choose one over the other?" Students who can articulate that they considered multiple approaches and made a reasoned choice produce much stronger Criterion C evidence than students who describe what they did without explaining why. The decision log is the evidence; the product is merely the outcome of those decisions.
ATL skills assessed under Criterion C include thinking skills, communication skills, research skills, self-management skills, and social skills. Students need to name the skill and provide evidence of using it. "I used thinking skills" is not evidence. "When my first design prototype did not meet my success criterion for accessibility, I used systems thinking to identify which elements of the design needed to change and in what order" is evidence. Supervisors should train students to use this structure: skill name, specific situation, what the student actually did.
The ATL skills framework maps directly onto the five skill categories assessed in Criterion C. Students who are familiar with ATL from their MYP subjects have an immediate advantage here because they can name their thinking processes using a shared vocabulary. If your school uses the ATL skills planning approach described in our teacher guide, students will already have practice connecting cognitive operations to specific tasks. This is exactly what Criterion C requires.
Self-assessment checkpoints throughout the process, not just at the end, are essential for Criterion C evidence. A simple fortnightly prompt works well: "Compare your product as it stands today with your success criteria. What matches? What does not yet match? What will you do differently in the next two weeks?" Students who complete this prompt fortnightly have a Criterion C evidence bank by submission time. Students who reflect only at the end are reconstructing rather than reporting.
Criterion D is the most frequently under-achieving criterion, and it is almost entirely within the supervisor's control to change this. The reason students underperform on Criterion D is not that they lack the capacity to reflect; it is that no one has taught them how. Left without a framework, most 15-year-olds write a description of what happened. What they need is a structure for evaluating what happened and connecting it to their development as learners.
Gibbs' Reflective Cycle (Gibbs, 1988) is the most widely used reflective framework in education for good reason: it provides a sequence of prompts that take a student from description through analysis to future planning. Adapted for Year 10 students, the cycle has five stages: description ("what did I do and what happened?"), feelings ("how did I feel about this?"), evaluation ("what went well and what went less well?"), analysis ("why did this happen? what does the research say about this?"), and future application ("what would I do differently? what have I learned about myself as a learner?"). The IBO's Criterion D descriptors map almost precisely onto the Gibbs stages.
The most important Criterion D question is the one directly connected to the IB Learner Profile: "What did you learn about yourself as a learner?" This question requires students to move from describing the project to reflecting on their own cognitive and personal development. A student who writes "I learned that I need to start earlier" has described a logistical observation. A student who writes "I learned that I underestimate how long research takes because I conflate reading with understanding. I can read a source quickly, but extracting and evaluating its argument takes three times as long. This changed how I plan all my academic work" has genuinely reflected on themselves as a learner. That is a high-band Criterion D response.
Criterion D also asks students to evaluate the quality of the product against the original success criteria. This is where the investment in good success criteria in September pays off. A student who wrote measurable, evaluable success criteria in Criterion B can now systematically assess whether their product met each one, explain why it did or did not, and identify what they would change with more time. A student whose success criteria were vague has nothing specific to evaluate against and defaults to global statements ("I think it turned out well").
Introduce Gibbs' Reflective Cycle in September alongside the project introduction, not in March when report writing begins. Give students a one-page template with the five stages and a worked example using a fictional project. Then practise the cycle during check-ins: "Let's do a quick Gibbs on the research you did this week. What happened? How did you feel about it? What worked? Why do you think it worked?" The cycle is a habit that needs to be practised across the year, not a framework introduced at the point of assessment.
The logistical challenge of supervising a cohort of Personal Projects is the aspect of the role that least experienced supervisors find hardest. You are responsible for 20 or more students, each on a completely different topic, at potentially different stages of the process, with different strengths and very different levels of self-management. Monthly one-to-one meetings for 20 students would consume four or five hours a month before you factor in preparation. That is unsustainable alongside a full teaching timetable.
The solution is not longer meetings but more frequent, shorter ones. A three-minute standing check-in at the start of a lesson or during registration accomplishes most of what a 30-minute meeting accomplishes, if the student comes prepared. The rule: every student completes a fortnightly progress card before meeting the supervisor. The card has three fields: what I have done since the last check-in, what I plan to do before the next check-in, and one thing I am stuck on or uncertain about. The supervisor reads the card in 30 seconds and the conversation is focused immediately.
Tracking 20 projects requires a simple spreadsheet, not a complex system. Five columns are enough: student name, current criterion focus, last check-in date, next check-in date, and a brief status note. Update it after every contact. Colour-code by RAG (red: at risk, amber: progressing but needs attention, green: on track). This takes less than two minutes per student per fortnight and means you are never surprised by a student who has done nothing for six weeks.
The Thinking Framework provides a shared vocabulary across all 20 projects, which is the real reason it is worth introducing at the start of the year. When every student knows what Compare, Sequence, Part-Whole, and Perspective mean as cognitive operations, your check-in questions become reusable across completely different project types. "Which Thinking Framework operation did you use this week? Show me how." Works for the student writing a novel and the student building a prototype circuit in the same check-in round. The Thinking Framework is the supervisor's efficiency tool, not just the student's thinking scaffold.
Stagger start dates by one week between form groups or tutor groups where possible. If all 20 students submit their goal statements on the same day, you face a marking pile. If group A submits in week 3 of September and group B submits in week 4, you have a manageable spread. The same logic applies to plan approvals, mid-point reviews, and draft report feedback. Small administrative decisions in September save significant time in February.
The process journal is, in the experience of most MYP coordinators, the most misunderstood element of the Personal Project. Students routinely produce journals that are detailed diaries of activity and almost entirely devoid of thinking. "On Monday I looked at three websites about nutrition. On Wednesday I started writing my plan." This is a log. It is not a process journal. It will not contribute meaningfully to any criterion.
A process journal is a record of thinking in progress. It captures decisions made and the reasoning behind them, problems encountered and how they were addressed, connections made between research and the evolving product, and moments of uncertainty or insight. The test for any journal entry is: if a stranger read this, would they understand how this student thinks, not just what they did?
| Weak entry (diary) | Strong entry (process journal) |
|---|---|
| Today I researched food waste. I found some interesting statistics about how much food is wasted each year. | I compared two sources on food waste statistics. The WRAP report (2019) focuses on household waste; the FAO (2011) report includes the whole supply chain. I decided my guide should focus on the point of consumption, not production, because my audience is secondary students who have no control over supply chain decisions. |
| I changed my plan because I wasn't making enough progress. | My original plan had the illustrated sections completed by week 6, but I have only completed two of five. I identified two causes: I underestimated illustration time (each takes 90 minutes, not 45) and I spent two sessions re-researching after finding conflicting information. I adjusted the timeline by removing one illustration and adding a written explanatory section instead, which is faster to produce and still meets my success criteria for clarity. |
| I used communication skills this week. | I tested my guide with a Year 8 student to check whether the language was accessible. She understood the main argument but was confused by the term "embodied carbon." I revised that section to use "the carbon produced during manufacturing" instead. This feedback loop improved the clarity of my writing for the target audience. |
Show these examples to students in September. Show them again in November. The diary instinct is strong. Many students have been praised for detailed diaries in junior school and do not understand why the same approach fails at MYP5. Naming the distinction explicitly, with side-by-side examples, changes behaviour more reliably than any amount of general guidance about "reflecting on your thinking."
The format of the process journal is flexible. It can be handwritten, digital, audio recorded, visual, or a combination. The IBO does not specify a format. Some students produce beautiful sketchbook journals with annotations. Others keep a running document with dated entries. Some use bullet points; others write paragraphs. The format is irrelevant. The presence of thinking is what matters.
Most Personal Project failures are predictable and preventable. They fall into four categories, and supervisors who know them in advance can build countermeasures into the supervision schedule from the start.
Starting too late. Students who begin active work in January face a compressed timeline that makes genuine research, iterative product development, and meaningful reflection impossible. The project becomes a scramble rather than an inquiry. The countermeasure is structural: require a topic exploration document in September, a goal statement in October, and a plan approval in November. Students who have not submitted these documents by the deadlines should have a conversation with the supervisor, not a reminder email. Three minutes of direct conversation is more effective than three email reminders. The task avoidance research is clear on this: avoidance is driven by anxiety about getting started, not by lack of motivation. A supervisor who normalises starting early removes the psychological barrier.
Choosing a topic they cannot access. A student who wants to investigate the experience of refugees but has no access to refugees, no relevant contacts, and no appropriate way to conduct primary research has chosen a topic they cannot investigate properly. The same applies to topics that require equipment, access, or expertise the student does not have. Supervisors should ask at goal-setting: "How will you actually investigate this? What sources are available to you? What can you do that no one else has done?" If the answer is "I'll search the internet," the topic needs revision.
Product versus process imbalance. Students who fall in love with their product and forget to document their thinking produce polished products and weak reports. The supervision check-in is the corrective: "Your product is looking good. Show me three process journal entries from the last two weeks that explain a decision you made." If the student cannot produce them, they have a problem that needs addressing now, not at submission.
Plagiarism in the digital age. AI-generated text is now a serious concern in Personal Project reports, particularly in the reflective sections. The IBO's academic integrity policy applies, and supervisors are in the best position to detect voice inconsistency between check-in conversations and written submissions. A student who speaks tentatively about their project in check-ins and submits a report with confident, polished academic prose has almost certainly received inappropriate assistance. Familiarity with each student's voice, developed through regular check-ins, is the most reliable detection mechanism available to supervisors.
Parent communication about the Personal Project is where schools create problems they then spend the year managing. Parents, understandably, want their children to do well. Many parents interpret "your child is responsible for this project" as "you should help your child with this project." The result is projects that are competently organised by a parent and weakly owned by the student. Parents who write their child's goal statement, structure their research, or produce elements of the product are actively harming their child's Criterion A, B, and C marks, because the evidence of the student's own thinking will be absent.
The parent communication letter should address three things directly. First, the supervisor's role: the supervisor checks in fortnightly, provides formative feedback, and ensures the student is on track. The supervisor does not direct the project, correct the work, or tell the student what to do. Second, the student's independence requirement: the Personal Project is an assessment of the student's independent thinking and self-management. Third, where parents can help. Parents can provide logistical support (buying materials, driving to a location for research, providing access to a printer), moral support (showing interest, creating time and space for the student to work), and accountability (asking "did you do your project work today?" without asking "shall I help you with it?"). Parents who understand the distinction between logistical support and academic assistance are genuinely helpful. Those who do not can undermine months of the student's work in a single weekend.
Send the parent communication in September at the project launch, not in February when the work is underway. A parent who understands the project from the start is a supervisor's ally. A parent who only hears about it when their child is panicking in February is a variable that is much harder to manage.
The Personal Project outcome in May is almost entirely determined by decisions made in September. Schools that treat the project as something students do in the second half of the year produce weaker projects than schools that begin concept development in the first week of term. The September setup takes approximately three timetabled hours across the year group, and it returns those hours many times over in reduced crisis management and stronger student outcomes.
The sequence from September to May should look like this:
September: Introduce the project concept. Show examples of strong and weak projects from previous years (with names removed). Explain the four criteria in plain language. Give students the Part-Whole brainstorming tool and ask them to generate five possible topic areas. No commitment required; this is exploration. Introduce the Thinking Framework operations students will use throughout the project. Assign the first process journal entry: "Write about a topic area you are considering and why it interests you."
October: Topic exploration deepens. Students narrow from five areas to two using the Part-Whole operation. First supervisor check-in. Goal statement drafted. Research begins. Students evaluate two sources using the Compare operation and write a process journal entry about the comparison.
November: Goal statement finalised and approved by supervisor. Success criteria written. Planning timeline completed. Plan formally approved before the end of the month. This is the critical gate: no student should begin creating their product without a supervisor-approved plan. Students who skip this gate almost always struggle with Criterion B.
December: Product creation begins. Fortnightly check-ins continue. Mid-point review at the end of term: product is assessed against success criteria for the first time. Adjustments to the plan are documented. The scaffolding the supervisor provides here, structured prompts rather than direct instruction, determines how independently students develop their self-management skills.
January to March: Product creation completed. Report writing begins in February with Criteria A and B. Criteria C and D written in late February and early March. Draft report submitted to supervisor. Formative feedback given. Students revise. The reflection sections take longer than students expect; build two full weeks for Criterion D.
April: Final report submission. In some schools, students also present their project to a panel. If your school includes a presentation, allow two weeks between final report submission and the presentation so students can prepare without compressing report writing time.
May: Moderation and submission to the IBO. Supervisors should have reviewed all projects before submission and confirmed that product, process journal, and report are all present and complete. Missing components are a moderation risk that is entirely preventable with a submission checklist.
The executive function demands of the Personal Project are significant for every student, not just those with identified learning differences. Self-directed work over eight months, with infrequent formal checkpoints, requires planning, monitoring, and self-correction at a level many 15-year-olds are still developing. Supervisors who build external structure into the process through regular check-ins, milestone documents, and reflection prompts are not reducing the intellectual challenge of the project. They are providing the scaffolding that allows students to work at the edge of their current capability rather than collapsing under the weight of open-endedness.
The International Baccalaureate Personal Project is, when supervised well, one of the most valuable learning experiences a secondary student can have. It develops research skills, self-management, reflective practice, and the capacity to pursue a goal independently over an extended period. These are not just IB competencies; they are the skills that distinguish high-performing students across every academic pathway that follows. The supervisor's role is not to manage the project for the student but to build the conditions in which the student can manage it for themselves.
These studies underpin the supervisory strategies described in this guide.
Self-Regulated Learning and Academic Achievement: An Overview View study ↗
Zimmerman, B. J. (2002). Educational Psychologist.
Zimmerman's overview of self-regulated learning shows that students who monitor their progress in short cycles and adjust their strategies outperform those who rely on end-point assessment alone. This finding directly supports the fortnightly check-in model for Personal Project supervision and explains why students with weak self-monitoring skills need external structure rather than simply more time.
Metacognition and Learning: Conceptual and Methodological Considerations View study ↗
Flavell, J. H. (1979). Developmental Psychology.
Flavell's foundational work on metacognition establishes that awareness of one's own cognitive processes is learnable and developable. For Personal Project supervisors, this means that process journal prompts which ask students to name their thinking operations are not a bureaucratic requirement but a genuine intervention in developing their capacity for independent academic work.
Improving Secondary Pupils' Engagement with Reflective Writing View study ↗
Gibbs, G. (1988). Oxford Polytechnic: Oxford. (Adapted discussions in: Assessment and Evaluation in Higher Education)
The research base on structured reflective frameworks consistently shows that students produce more substantive reflection when given a sequence of prompts than when asked to reflect openly. The Gibbs Cycle's five-stage structure, adapted for secondary students, produces measurably richer Criterion D responses than unstructured journal writing alone.
Improving Secondary Students' Metacognitive Skills View study ↗
Education Endowment Foundation (2018). Metacognition and Self-Regulated Learning.
The EEF guidance report on metacognition identifies explicit teaching of planning, monitoring, and evaluation strategies as having a high impact (equivalent to an additional seven months of progress) at relatively low cost. For Personal Project supervisors, this positions the check-in model and structured reflection frameworks not as administrative overhead but as high-impact pedagogical interventions.
MYP: From Principles into Practice View study ↗
IB Organisation (2014). International Baccalaureate Organisation: Geneva.
The IBO's own framework document sets out the design principles behind the Personal Project, including the emphasis on student agency, the role of the ATL skills, and the importance of the process over the product. Reading the official framework alongside this practical guide helps supervisors understand which flexibilities are genuine and which constraints are non-negotiable.
{"@context":"https://schema.org","@graph":[{"@type":"Article","headline":"MYP Personal Project: A Complete Supervisor's Guide","description":"A practical guide for MYP supervisors covering all four assessment criteria, process journal coaching, managing 20 projects simultaneously, and the September-to-May timeline.","datePublished":"2026-03-24T00:00:00.000Z","dateModified":"2026-03-24T00:00:00.000Z","author":{"@type":"Person","name":"Paul Main","jobTitle":"Founder & Educational Consultant"},"publisher":{"@type":"Organization","name":"Structural Learning","logo":{"@type":"ImageObject","url":"https://cdn.prod.website-files.com/5b69a01ba2e409e5d5e055c6/5b69a01ba2e409e5d5e055c8_structural-learning-logo.svg"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.structural-learning.com/post/myp-personal-project-supervisors-guide"},"about":[{"@type":"Thing","name":"IB Middle Years Programme","sameAs":"https://www.wikidata.org/wiki/Q1523785"},{"@type":"Thing","name":"Project-Based Learning","sameAs":"https://www.wikidata.org/wiki/Q1419083"},{"@type":"Thing","name":"Metacognition","sameAs":"https://www.wikidata.org/wiki/Q614686"}],"wordCount":3800},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.structural-learning.com"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.structural-learning.com/blog"},{"@type":"ListItem","position":3,"name":"MYP Personal Project: A Complete Supervisor's Guide","item":"https://www.structural-learning.com/post/myp-personal-project-supervisors-guide"}]}]}
