Tell the true story of your passion project โ and make it shine
Every IB DP student who pours heart and time into a passion project wants it to read like a small triumph: clear purpose, meaningful learning, real outcomes. The temptation to blow up every detail into something grander than it was is understandable โ admissions readers and assessors notice impressive-sounding projects. But the quiet secret is this: clarity, specificity, and honest reflection create a stronger impression than exaggeration ever will.

This post is for the student who wants to communicate impact without overselling, to build a portfolio thatโs both compelling and credible. Youโll find practical language swaps, ways to document evidence, a table to translate risky claims into accurate phrasing, and simple checks to use before you file your reflection or submit your portfolio. Along the way, youโll see how structured feedback โ including targeted 1-on-1 guidance like Sparkl‘s tailored study support โ can help refine wording so your voice comes through without the shine of overclaiming.
What “overclaiming” looks like โ and why it matters
Definitions, in student terms
Overclaiming is the act of describing your role, results, or learning in ways that make them seem bigger, more independent, or more conclusive than they actually were. Itโs often subtle: a verb choice here, an omitted collaborator there, or a sweeping phrase about impact that has no attached evidence. Readers who know the IB context โ teachers, examiners, university admissions officers โ can usually tell when language has been stretched, and that can damage trust.
Typical ways students overlap into overclaiming
- Using absolute outcomes without linking to evidence (“This project fixed X”).
- Implying solo leadership when a team or mentor played a major role.
- Describing short pilots as large-scale interventions.
- Using inflated verbs (“transformed,” “revolutionised”) instead of process verbs (“piloted,” “evaluated”).
- Listing intended outcomes as if they had already occurred.
How assessors and readers evaluate project claims
Assessors look for a consistent narrative: a clear role, a coherent method, evidence that supports your conclusions, and thoughtful reflection on what you learned. University readers similarly prize authenticity and curiosity โ they want to see what you actually did and how you thought about it, not just what you wish you had done.
| Claim type | Why it’s risky | How to present it accurately | Examples of supporting evidence |
|---|---|---|---|
| Impact statements (“I changed the community”) | Hard to verify without data or witness accounts | Describe measurable outcomes and the scope of the change | Attendance lists, survey results, photos, short testimonies |
| Leadership claims (“I led a city-wide campaign”) | Vague scale and unclear role | Specify your responsibilities, scale, and collaborators | Email threads, planning documents, minutes, role description |
| Independence claims (“I did it alone”) | Likely untrue in formal contexts | State what you did independently and what support you had | Mentor notes, citations of resources, timelines showing milestones |
Practical steps for writing with accuracy and impact
1. Begin with a precise role statement
Open your project description with one or two sentences that say exactly who you were and what you did. Avoid vague leadership claims; name the tasks you carried out.
- Good: “I designed and delivered three community workshops on basic digital literacy, focusing on seniors in my neighbourhood.”
- Less good: “I ran a community-wide campaign to increase digital access.”
2. Anchor claims in process rather than grand outcomes
Describe what you tried, how you tried it, and what you observed. The spotlight should be on your method and learning, because process is where assessors find validity.
- Explain the steps you took and why you chose them.
- Include an honest appraisal of what worked, what didnโt, and what you would change next time.
3. Use measured, evidence-backed language
Prefer verbs like “piloted,” “facilitated,” “coordinated,” “evaluated,” and “collaborated” to verbs that imply total success. When you describe impact, attach a piece of evidence or explain how you measured it.
- Quantify when appropriate: number of participants, hours spent, pre/post reflections.
- When you donโt have numbers, describe observable effects: participant feedback themes, changes in behaviour, or a notable quote from a participant.
4. Be explicit about collaboration and support
If teachers, community leaders, or peers helped, say so. Explain the specific contribution they made โ mentoring, funding, venue support โ and which parts you led. That clarity strengthens the credibility of your claim instead of weakening it.
5. Show limitations as part of the learning
Assessors appreciate mature reflection. When you talk about limits โ small sample size, short timeline, variables you couldnโt control โ pair each limitation with what you learned and what you would test next. That transforms a limitation into evidence of critical thinking.
Concrete phrasing swaps: what to write instead
Here are side-by-side phrasing swaps to make your writing more accurate and stronger.
- Instead of “I solved the problem of X,” try “I tested an approach to reduce X and observed Y in a small pilot.”
- Instead of “I single-handedly led the initiative,” try “I coordinated the planning team and was responsible for X activities.”
- Instead of “This project changed attitudes,” try “Participant feedback suggested a positive shift in understanding in the short term.”
How to document evidence for your portfolio
Good documentation is simple, organized, and directly tied to claims you make in your reflection. Think of evidence as the notes that let a reader verify what you say; it doesnโt have to be perfect, but it must be honest and accessible.
What to collect
- Primary artifacts: photos, PDF copies of handouts, recordings of sessions (with permission).
- Process logs: short dated entries showing progress and decisions.
- Stakeholder feedback: short emails, quotes, or a one-paragraph witness statement from a collaborator.
- Quantitative markers where possible: attendance numbers, pre/post survey summaries.
Sample evidence-log table to include in your portfolio
| Date | Activity | Your role | Evidence file name/location | Notes (1โ2 lines) |
|---|---|---|---|---|
| 01 March | Pilot workshop | Facilitator; designed materials | workshop_notes_march.pdf | 12 attendees; short survey showed increased confidence |
| 12 April | Follow-up session | Coordinator; collated feedback | feedback_summary_april.docx | Participants requested more hands-on time |
Tone, language, and a quick verbs cheat-sheet
The verbs you choose shape perception. Hereโs a simple list to keep handy while you write and edit.
- Prefer: piloted, evaluated, facilitated, coordinated, designed, collaborated, documented, adapted.
- Avoid (or use sparingly): transformed, solved, revolutionised, single-handedly, guaranteed.
Examples โ before and after
Seeing real examples helps. Below are typical student sentences revised to sound accurate and confident.
- Before: “I led a project that fixed wasted food in my city.”
After: “I piloted a community redistribution scheme focused on two local cafรฉs; over six weeks we collected surplus food and coordinated deliveries to a local shelter, documenting quantities and recipient feedback.” - Before: “My campaign changed students’ attitudes about recycling.”
After: “Post-campaign questionnaire responses suggested improved awareness about recycling; participants noted three practical behaviours they planned to adopt.” - Before: “I improved maths results at my tutoring centre.”
After: “I delivered weekly targeted sessions to a small cohort and compared formative assessment results before and after the programme, noting gains in specific topic areas.”

How targeted feedback can help โ including tailored tutoring
Two fresh eyes make a huge difference. A tutor or mentor who understands IB expectations can help you strip away puffed language and highlight genuine learning. If you seek structured support, Sparkl‘s 1-on-1 guidance can be useful: tutors help you craft measured language, build evidence logs, and develop reflective passages that meet assessment mindsets. Their tailored study plans and AI-driven insights are helpful for students who want specific edits and phrasing suggestions rather than generic praise.
A simple pre-submission checklist
Before you finalize any written reflection or portfolio entry, run through this checklist aloud or with a peer:
- Have I described my exact role and responsibilities?
- Do I connect any outcome statements to a piece of evidence?
- Have I acknowledged collaborators and support clearly?
- Have I stated any limitations and what I learned from them?
- Have I avoided absolute language and given scope where needed?
- Does each major claim have at least one supporting artifact or observation?
Quick edits that save credibility
When youโre polishing, make these quick edits:
- Replace “always”/”never” with “often”/”rarely” or a precise frequency.
- Add short parenthetical evidence: (n=12 participants), (email from mentor), (survey summary).
- Swap a grand verb for a process verb and follow it with what you measured or observed.
Final examples of balanced reflection
To finish, here are two compact model reflections that aim for authenticity and clarity.
Model A: “I developed a peer-mentoring pilot to support first-year students with study skills. I recruited and trained four mentors, designed three session plans, and piloted the programme with ten mentees. Pre/post reflections indicated increased confidence around time management. Limitations included a short pilot period and low initial attendance; next steps would extend the pilot and include more targeted recruitment.”
Model B: “I researched local water usage patterns and created a small awareness leaflet distributed to 50 households. Conversations at distribution points revealed common misconceptions that informed a follow-up workshop. The projectโs scale was modest, but it clarified the kinds of questions residents had and shaped my plan for a larger, data-driven intervention.”
Closing thought
Writing well about a passion project is an exercise in clarity: precise role descriptions, process-focused storytelling, modest but supported claims, and honest reflection. When you present the truth well, your learning and initiative naturally stand out.
No Comments
Leave a comment Cancel