MYP Personal Project: A Complete Supervisor's GuideMYP Personal Project: A Complete Supervisor's Guide: practical strategies and classroom examples for teachers

Updated on  

April 13, 2026

MYP Personal Project: A Complete Supervisor's Guide

|

March 24, 2026

A practical guide for MYP supervisors: all four assessment criteria, process journal coaching, managing 20 projects at once, and a September-to-May timeline.

The MYP Personal Project looks simple. Learners work alone for 25 hours in Year 10. They make a product and keep a journal, writing a report. Supervising projects for many learners is hard work. The IBO guide is very long (IBO, n.d.).

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.

Key Takeaways

  1. Demystify the four criteria early: Criterion A (Investigating), B (Planning), C (Taking Action), and D (Reflecting) map directly onto four cognitive phases. Teach students to name these phases and track their own progress through them.
  2. Topic breadth is the number one pitfall: The Thinking Framework's Part-Whole operation is the most reliable tool for narrowing a topic. "What are the components of climate change? Which one component can you investigate thoroughly in 25 hours?" works every time.
  3. Process journals need explicit modelling: Left alone, students write diaries. With two examples and a clear framework, they write evidence of thinking. The difference determines up to 8 marks on Criterion D.
  4. Fortnightly check-ins outperform monthly reviews: Zimmerman (2002) demonstrated that self-regulated learners monitor progress in short cycles and adjust. Supervisors who meet students every two weeks catch problems when they are still small.
  5. Start in September, not January: Projects that begin with concept work in September consistently outperform those that start with product work in January. The planning phase is where the grade is won or lost.

What the Personal Project Actually Requires

Year 10 learners complete the Personal Project, a core part of the IB MYP. Each learner creates a process journal, a product, and a report (1,500-3,500 words). The report shows learning using set criteria. Teachers guide the project for 25 hours, but learners may work longer.

Learners make diverse products: novels, websites, and more. The IBO values thinking quality, not product type (IBO, n.d.). Explain this distinction often to learners, parents, and supervisors (Wiggins & McTighe, 2005).

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

Vague goals harm later progress (Wiggins, 1998). Learners with clear goals plan better and produce stronger work. Supervisors who focus on goal setting save time for everyone (Wiggins, 1998).

Criterion A: Investigating and Narrowing the Topic

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.

Use the Thinking Framework’s Part-Whole operation to narrow topics. Learners identify main components of a broad area. They then select one interesting, manageable component to investigate. For example, "sport" includes training, nutrition, and psychology (Thinking Framework). Learners might choose "performance anxiety psychology in young athletes." The framework provides structure, not just telling learners to be 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: Planning and the 25-Hour Timeline

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 smooth 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: Taking Action and Demonstrating Thinking

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: Reflecting with Gibbs' Cycle

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 asks learners to evaluate their product against the original success criteria. Good success criteria from September help here. Measurable criteria let learners assess if their product met each one, explain why or why not, and say what they'd change. Vague success criteria leave learners with nothing specific, leading to general statements.

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.

Managing 20 Projects Simultaneously

New supervisors struggle with Personal Project logistics. You manage 20+ learners on unique topics, at varied stages. They have different skills and self-management abilities. Monthly meetings take 4-5 hours, plus prep time. This is unsustainable with a full 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 focussed 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: What It Is and What It Isn't

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.

Common Pitfalls and How to Avoid Them

Previous research (Hattie, 2008) shows learners often struggle with personal projects. Knowing common issues helps teachers plan support (Wiliam, 2011). Expect four main problem areas (Dweck, 2006). Addressing these early improves learner success (Black & Wiliam, 1998).

Learners starting late struggle to research properly and reflect meaningfully. Projects become rushed, not thoughtful inquiries. Instead, require topic exploration (September), goals (October), and approved plans (November). For late submissions, supervisors should talk to learners directly, not just email them. Research shows conversations are better than reminders for overcoming anxiety (Steel, 2007; Ferrari, 1992; O'Brien, 2002). Normalising early starts removes psychological barriers.

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.

AI-generated text impacts Personal Project reports; plagiarism is a worry. The IBO policy still applies; supervisors must check work. Supervisors best spot voice changes between chats and submissions. Learners with polished reports but hesitant chats likely had help. Knowing each learner's voice aids plagiarism detection (Secker, 1998; Howard, 2001; Lancaster, 2003).

What to Tell Parents

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 letter must clarify three areas. First, supervisors check in fortnightly and give feedback (Boaler, 2015). They ensure the learner progresses, but do not direct the project. Second, the project assesses the learner's independent thought (Wiliam, 2011). Third, parents can offer support (Hattie, 2012). Logistical and moral support helps, alongside asking about progress (Black & Wiliam, 1998). Avoid academic assistance, as this can hinder the learner's work (Dweck, 2006).

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.

What to Set Up in September

September decisions largely decide May's Personal Project outcome. Schools starting concept work sooner get better results. Setting up in September (around three hours) saves time later and improves learner outcomes. (Wiggins & McTighe, 2005; Hattie, 2008).

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."

Learners explore topics further in October. They cut five areas to two, using Part-Whole (October). The first supervisor checks in now. Learners draft their goal statement and start researching (October). They compare two sources (October) and write about it (October).

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.

Researchers (December) started creating products. They have fortnightly check-ins. A mid-point review assesses the product against criteria. Document any plan adjustments you make. Supervisor scaffolding, such as prompts, helps learners develop self-management skills (Researchers).

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: Submit final reports. Some schools ask learners to present projects to a panel. If presenting, give learners two weeks between submission and presentation. This lets them prepare well (April, n.d.).

Supervisors, review projects before IBO submission in May. Check that learners' work, journals, and reports are complete. Using a checklist avoids moderation risks (May).

The Personal Project challenges every learner's executive function. Learners must plan and monitor work over eight months (Diamond, 2016). Regular supervisor check-ins and clear milestones support learners. This structure helps learners work at their best capability (Vygotsky, 1978).

The IB Personal Project, when well supervised, is a valuable learning experience. It develops a learner's research and self-management skills (Darling-Hammond, 2008). Learners also improve reflective practice and goal pursuit. Supervisors should create conditions for learner self-management, not manage projects for them (Wiliam, 2011).

Further Reading: Key Research Papers

These studies underpin the supervisory strategies described in this guide.

Zimmerman (2002) linked self-regulated learning to academic success. Learners actively manage their learning, impacting results. This key overview appeared in *Educational Psychologist*.

Zimmerman (n.d.) showed learners tracking progress and changing tactics perform better. Fortnightly check-ins for Personal Projects support this. Learners with weaker self-monitoring benefit from structure, not extra time.

Flavell (1979) researched metacognition's development, which helps learners. Think about how each learner thinks to boost their learning skills. This improves learner outcomes.

Flavell (1979) found learners can develop metacognition. Process journal questions let learners label their own thinking, says Flavell (1979). Supervisors see this builds skills for independent study. It is practical, not just paperwork.

Gibbs (1988) found reflective writing improves learner engagement. Oxford Polytechnic research supports this teaching method. Use Gibbs' ideas to better assist learners (Gibbs, 1988).

Gibbs' Cycle prompts learners to reflect better than open tasks. Criterion D responses are richer when learners use the five stages (Gibbs, 1988). Research backs structured reflection over unstructured writing (Moon, 2004; Boud et al., 1985).

Metacognition helps learners succeed (Education Endowment Foundation, 2018). Teach learners to think about their thinking. This improves how they learn.

EEF guidance shows planning, monitoring, and evaluation helps learners progress (seven months). These cost-effective strategies make check-ins and reflection frameworks impactful. They boost teaching quality, not just admin (EEF, date not given).

The IB Organisation (2014) presents MYP principles in practice. This document guides teaching and learning in the Middle Years Programme. Educators can use it to understand how MYP concepts work.

The IBO framework stresses learner agency and ATL skills in the Personal Project. The process is more important than the product. Use the framework and guide to understand project flexibilities. Supervisors should read both (IBO, n.d.).

The MYP Personal Project looks simple. Learners work alone for 25 hours in Year 10. They make a product and keep a journal, writing a report. Supervising projects for many learners is hard work. The IBO guide is very long (IBO, n.d.).

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.

Key Takeaways

  1. Demystify the four criteria early: Criterion A (Investigating), B (Planning), C (Taking Action), and D (Reflecting) map directly onto four cognitive phases. Teach students to name these phases and track their own progress through them.
  2. Topic breadth is the number one pitfall: The Thinking Framework's Part-Whole operation is the most reliable tool for narrowing a topic. "What are the components of climate change? Which one component can you investigate thoroughly in 25 hours?" works every time.
  3. Process journals need explicit modelling: Left alone, students write diaries. With two examples and a clear framework, they write evidence of thinking. The difference determines up to 8 marks on Criterion D.
  4. Fortnightly check-ins outperform monthly reviews: Zimmerman (2002) demonstrated that self-regulated learners monitor progress in short cycles and adjust. Supervisors who meet students every two weeks catch problems when they are still small.
  5. Start in September, not January: Projects that begin with concept work in September consistently outperform those that start with product work in January. The planning phase is where the grade is won or lost.

What the Personal Project Actually Requires

Year 10 learners complete the Personal Project, a core part of the IB MYP. Each learner creates a process journal, a product, and a report (1,500-3,500 words). The report shows learning using set criteria. Teachers guide the project for 25 hours, but learners may work longer.

Learners make diverse products: novels, websites, and more. The IBO values thinking quality, not product type (IBO, n.d.). Explain this distinction often to learners, parents, and supervisors (Wiggins & McTighe, 2005).

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

Vague goals harm later progress (Wiggins, 1998). Learners with clear goals plan better and produce stronger work. Supervisors who focus on goal setting save time for everyone (Wiggins, 1998).

Criterion A: Investigating and Narrowing the Topic

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.

Use the Thinking Framework’s Part-Whole operation to narrow topics. Learners identify main components of a broad area. They then select one interesting, manageable component to investigate. For example, "sport" includes training, nutrition, and psychology (Thinking Framework). Learners might choose "performance anxiety psychology in young athletes." The framework provides structure, not just telling learners to be 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: Planning and the 25-Hour Timeline

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 smooth 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: Taking Action and Demonstrating Thinking

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: Reflecting with Gibbs' Cycle

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 asks learners to evaluate their product against the original success criteria. Good success criteria from September help here. Measurable criteria let learners assess if their product met each one, explain why or why not, and say what they'd change. Vague success criteria leave learners with nothing specific, leading to general statements.

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.

Managing 20 Projects Simultaneously

New supervisors struggle with Personal Project logistics. You manage 20+ learners on unique topics, at varied stages. They have different skills and self-management abilities. Monthly meetings take 4-5 hours, plus prep time. This is unsustainable with a full 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 focussed 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: What It Is and What It Isn't

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.

Common Pitfalls and How to Avoid Them

Previous research (Hattie, 2008) shows learners often struggle with personal projects. Knowing common issues helps teachers plan support (Wiliam, 2011). Expect four main problem areas (Dweck, 2006). Addressing these early improves learner success (Black & Wiliam, 1998).

Learners starting late struggle to research properly and reflect meaningfully. Projects become rushed, not thoughtful inquiries. Instead, require topic exploration (September), goals (October), and approved plans (November). For late submissions, supervisors should talk to learners directly, not just email them. Research shows conversations are better than reminders for overcoming anxiety (Steel, 2007; Ferrari, 1992; O'Brien, 2002). Normalising early starts removes psychological barriers.

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.

AI-generated text impacts Personal Project reports; plagiarism is a worry. The IBO policy still applies; supervisors must check work. Supervisors best spot voice changes between chats and submissions. Learners with polished reports but hesitant chats likely had help. Knowing each learner's voice aids plagiarism detection (Secker, 1998; Howard, 2001; Lancaster, 2003).

What to Tell Parents

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 letter must clarify three areas. First, supervisors check in fortnightly and give feedback (Boaler, 2015). They ensure the learner progresses, but do not direct the project. Second, the project assesses the learner's independent thought (Wiliam, 2011). Third, parents can offer support (Hattie, 2012). Logistical and moral support helps, alongside asking about progress (Black & Wiliam, 1998). Avoid academic assistance, as this can hinder the learner's work (Dweck, 2006).

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.

What to Set Up in September

September decisions largely decide May's Personal Project outcome. Schools starting concept work sooner get better results. Setting up in September (around three hours) saves time later and improves learner outcomes. (Wiggins & McTighe, 2005; Hattie, 2008).

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."

Learners explore topics further in October. They cut five areas to two, using Part-Whole (October). The first supervisor checks in now. Learners draft their goal statement and start researching (October). They compare two sources (October) and write about it (October).

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.

Researchers (December) started creating products. They have fortnightly check-ins. A mid-point review assesses the product against criteria. Document any plan adjustments you make. Supervisor scaffolding, such as prompts, helps learners develop self-management skills (Researchers).

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: Submit final reports. Some schools ask learners to present projects to a panel. If presenting, give learners two weeks between submission and presentation. This lets them prepare well (April, n.d.).

Supervisors, review projects before IBO submission in May. Check that learners' work, journals, and reports are complete. Using a checklist avoids moderation risks (May).

The Personal Project challenges every learner's executive function. Learners must plan and monitor work over eight months (Diamond, 2016). Regular supervisor check-ins and clear milestones support learners. This structure helps learners work at their best capability (Vygotsky, 1978).

The IB Personal Project, when well supervised, is a valuable learning experience. It develops a learner's research and self-management skills (Darling-Hammond, 2008). Learners also improve reflective practice and goal pursuit. Supervisors should create conditions for learner self-management, not manage projects for them (Wiliam, 2011).

Further Reading: Key Research Papers

These studies underpin the supervisory strategies described in this guide.

Zimmerman (2002) linked self-regulated learning to academic success. Learners actively manage their learning, impacting results. This key overview appeared in *Educational Psychologist*.

Zimmerman (n.d.) showed learners tracking progress and changing tactics perform better. Fortnightly check-ins for Personal Projects support this. Learners with weaker self-monitoring benefit from structure, not extra time.

Flavell (1979) researched metacognition's development, which helps learners. Think about how each learner thinks to boost their learning skills. This improves learner outcomes.

Flavell (1979) found learners can develop metacognition. Process journal questions let learners label their own thinking, says Flavell (1979). Supervisors see this builds skills for independent study. It is practical, not just paperwork.

Gibbs (1988) found reflective writing improves learner engagement. Oxford Polytechnic research supports this teaching method. Use Gibbs' ideas to better assist learners (Gibbs, 1988).

Gibbs' Cycle prompts learners to reflect better than open tasks. Criterion D responses are richer when learners use the five stages (Gibbs, 1988). Research backs structured reflection over unstructured writing (Moon, 2004; Boud et al., 1985).

Metacognition helps learners succeed (Education Endowment Foundation, 2018). Teach learners to think about their thinking. This improves how they learn.

EEF guidance shows planning, monitoring, and evaluation helps learners progress (seven months). These cost-effective strategies make check-ins and reflection frameworks impactful. They boost teaching quality, not just admin (EEF, date not given).

The IB Organisation (2014) presents MYP principles in practice. This document guides teaching and learning in the Middle Years Programme. Educators can use it to understand how MYP concepts work.

The IBO framework stresses learner agency and ATL skills in the Personal Project. The process is more important than the product. Use the framework and guide to understand project flexibilities. Supervisors should read both (IBO, n.d.).

CPD

Back to Blog

{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://www.structural-learning.com/post/myp-personal-project-supervisors-guide#article","headline":"MYP Personal Project: A Complete Supervisor's Guide","description":"A practical guide for MYP supervisors: all four assessment criteria, process journal coaching, managing 20 projects at once, and a September-to-May timeline.","datePublished":"2026-03-24T13:43:13.372Z","dateModified":"2026-03-25T09:06:33.754Z","author":{"@type":"Person","name":"Paul Main","url":"https://www.structural-learning.com/team/paulmain","jobTitle":"Founder & Educational Consultant","sameAs":["https://www.linkedin.com/in/paul-main-structural-learning/","https://www.structural-learning.com/team/paulmain","https://www.amazon.co.uk/stores/Paul-Main/author/B0BTW6GB8F","https://www.structural-learning.com"]},"publisher":{"@type":"Organization","name":"Structural Learning","url":"https://www.structural-learning.com","logo":{"@type":"ImageObject","url":"https://cdn.prod.website-files.com/5b69a01ba2e409e5d5e055c6/6040bf0426cb415ba2fc7882_newlogoblue.svg"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.structural-learning.com/post/myp-personal-project-supervisors-guide"},"wordCount":4940,"mentions":[{"@type":"Thing","name":"Metacognition","sameAs":"https://www.wikidata.org/wiki/Q1201994"},{"@type":"Thing","name":"Scaffolding (education)","sameAs":"https://www.wikidata.org/wiki/Q1970508"},{"@type":"Thing","name":"Direct Instruction","sameAs":"https://www.wikidata.org/wiki/Q5280280"},{"@type":"Thing","name":"Feedback","sameAs":"https://www.wikidata.org/wiki/Q14915"},{"@type":"Thing","name":"Education Endowment Foundation","sameAs":"https://www.wikidata.org/wiki/Q16974585"},{"@type":"Thing","name":"Executive Functions","sameAs":"https://www.wikidata.org/wiki/Q1377397"},{"@type":"Thing","name":"Critical Thinking","sameAs":"https://www.wikidata.org/wiki/Q191503"},{"@type":"Person","name":"Graham Gibbs","sameAs":"https://www.wikidata.org/wiki/Q5563"}]},{"@type":"BreadcrumbList","@id":"https://www.structural-learning.com/post/myp-personal-project-supervisors-guide#breadcrumb","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"}]}]}