<\/p>\n
Why assessors care about iteration<\/h3>\n
Assessors are not only interested in polished outcomes; they are looking for evidence of learning, critical thinking, and the traits of the IB learner profile\u2014curiosity, adaptability, risk-taking, and reflection. A failed prototype, low turnout at a workshop, or a code branch that crashed are all meaningful when they are documented and analyzed. They become evidence that you tested hypotheses, gathered data, adjusted plans, and grew intellectually and personally.<\/p>\n
Think of failure as data. Each setback tells a story about assumptions you made, information you lacked, or conditions that changed. Presenting that story clearly shows you can make evidence-based decisions\u2014precisely the skill IB assessment seeks to reward.<\/p>\n
Build the narrative: the arc that sells your learning<\/h3>\n
Your portfolio or CAS journal should tell a compact, honest story. Use an arc that highlights intention, action, setback, analysis, and iteration. This structure helps anyone reading your portfolio understand not just what you did but why each step mattered.<\/p>\n
- \n
- Intention:<\/strong> What did you set out to test or achieve? Be precise about the hypothesis or outcome you expected.<\/li>\n
- Action:<\/strong> What was your first plan and why did you choose it? Include who was involved and what resources you used.<\/li>\n
- Setback:<\/strong> What went wrong or what surprised you? State the facts (what happened), then name the impact (who\/what was affected).<\/li>\n
- Analysis:<\/strong> Why do you think this happened? What evidence did you collect?<\/li>\n
- Iteration:<\/strong> What did you change next? How did the new version differ and why?<\/li>\n
- Outcome & Reflection:<\/strong> What did you learn, and how will this learning affect future practice? Connect it to specific skills or learner-profile attributes.<\/li>\n<\/ul>\n
When you craft each entry with this arc, readers will see a clear chain from problem to learning. Keep entries short, dated, and evidence-linked so your portfolio reads as a set of replicable, thoughtful experiments rather than a list of events.<\/p>\n
Practical things to log in your CAS\/portfolio<\/h2>\n
Good evidence is varied and consistent. Aim for a mixture of visual proof, dated notes, and third-party feedback. The key is to create a trail that proves iterative learning.<\/p>\n
- \n
- Dated reflections:<\/strong> Short entries that capture what happened, why it mattered, and what you changed next.<\/li>\n
- Before\/after photos:<\/strong> Visuals showing changes between versions, preferably with short annotations.<\/li>\n
- Versioned files:<\/strong> Save drafts with version numbers or dates (v1, v2, vFinal; or use timestamps).<\/li>\n
- Mentor or peer feedback:<\/strong> Screenshots, emails, or short notes from someone who observed your work.<\/li>\n
- Quantitative data:<\/strong> Attendance numbers, test scores, time spent, error rates\u2014whatever applies\u2014and a simple analysis of trends.<\/li>\n
- Annotated artifacts:<\/strong> Highlighted scripts, photos with notes, or short screencasts explaining changes you made.<\/li>\n<\/ul>\n
A table that helps you frame common setbacks<\/h3>\n
\n\n
\n \nType of setback<\/th>\n What happened<\/th>\n Learning opportunity<\/th>\n How to document it<\/th>\n<\/tr>\n<\/thead>\n \n Technical failure<\/td>\n Prototype doesn’t function as expected<\/td>\n Teaches troubleshooting, testing protocols, and resilience<\/td>\n Photographs of attempts, error logs, revised design notes, short video demo of corrected version<\/td>\n<\/tr>\n \n Low engagement<\/td>\n Workshop or survey had fewer participants than intended<\/td>\n Demonstrates outreach strategy, audience analysis, and adaptation<\/td>\n Attendance data, revised recruitment messages, annotated timeline of outreach steps<\/td>\n<\/tr>\n \n Time-management slip<\/td>\n Milestones missed due to unrealistic scheduling<\/td>\n Shows planning skills, prioritization, and improved scheduling<\/td>\n Updated Gantt chart or calendar screenshots, reflective entry on task estimates<\/td>\n<\/tr>\n \n Ethical or cultural surprise<\/td>\n Feedback revealed an unintended ethical\/cultural concern<\/td>\n Highlights sensitivity, communication, and ethical decision-making<\/td>\n Feedback excerpts, revised consent forms or guidelines, reflective note linking changes to community impact<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n Language that frames failure as strength<\/h2>\n
Words matter. How you describe a setback defines whether it reads as a weakness or as evidence of thoughtful inquiry. Swap passive or defeatist language for active, analytical phrasing. Be specific, concise, and rooted in evidence.<\/p>\n
Helpful verbs and sentence starters<\/h3>\n
- \n
- “I tested\u2026”<\/li>\n
- “The data showed\u2026”<\/li>\n
- “This revealed an assumption we had about\u2026”<\/li>\n
- “In response, I adapted the design by\u2026”<\/li>\n
- “I measured the change using\u2026”<\/li>\n
- “This iteration improved X by\u2026”<\/li>\n<\/ul>\n
Short reflection examples you can adapt<\/h3>\n
Below are realistic, portfolio-ready snippets you can use as models. Keep each entry focused on evidence, analysis, and next steps.<\/p>\n
Example 1 \u2014 Technical prototype:<\/strong> I built a low-cost water filter prototype and expected a 90% turbidity reduction after the first trial. The initial test reduced turbidity by only 45%. I logged pH and particle size readings, reviewed filter material choices, and consulted a mentor for material alternatives. Based on this, I replaced the media and increased flow-control measures; a second test reached 86% reduction. This process taught me how controlled variables and incremental testing improve experimental reliability.<\/p>\n
Example 2 \u2014 Community engagement:<\/strong> My workshop aimed to recruit 30 students but only 12 attended. I surveyed the target group and discovered timing and messaging were barriers. I rewrote the promotional posts focusing on benefits rather than dates, partnered with a student club to expand reach, and moved the event to a later slot; subsequent workshops averaged 28 attendees. This taught me to test outreach assumptions and adapt logistics based on stakeholder feedback.<\/p>\n
Example 3 \u2014 Research or writing setback:<\/strong> Early literature searches returned limited primary sources for my research question. Instead of forcing the question, I broadened my search terms, reached out to a local practitioner for interviews, and reframed the scope to include comparative case studies. The new approach yielded richer data and taught me how question refinement can be a productive response to limited evidence.<\/p>\n
How to show iteration visually and digitally<\/h2>\n
Visual evidence is immediate and persuasive. A thoughtful combination of dated photos, annotated screenshots, short video clips, and versioned documents paints a clear path of development.<\/p>\n
- \n
- Before vs. after galleries:<\/strong> Put images side-by-side with short captions explaining the change and why it matters.<\/li>\n
- Annotated photos:<\/strong> Use arrows or notes to point out specific fixes or redesigns.<\/li>\n
- Short videos:<\/strong> 30\u201390 second clips showing a demo or a spoken reflection are powerful and personal.<\/li>\n
- Version snapshots:<\/strong> Keep dated filenames and include a one-line note per file explaining its purpose (e.g., “v2 – reduced nozzle diameter to improve flow”).<\/li>\n
- Simple analytics:<\/strong> Use a small chart or table to show improvement over time\u2014attendance, error rate, or performance metrics.<\/li>\n<\/ul>\n
<\/p>\n - Annotated photos:<\/strong> Use arrows or notes to point out specific fixes or redesigns.<\/li>\n
- Before vs. after galleries:<\/strong> Put images side-by-side with short captions explaining the change and why it matters.<\/li>\n
- Before\/after photos:<\/strong> Visuals showing changes between versions, preferably with short annotations.<\/li>\n
- Action:<\/strong> What was your first plan and why did you choose it? Include who was involved and what resources you used.<\/li>\n