IB DP CAS Portfolio Strategy: How to Prove Persistence in CAS (The Evidence Checklist)
Persistence is the secret ingredient that turns a collection of activities into a meaningful CAS profile. Teachers and assessors look for sustained engagement, growth and thoughtful reflection—not just a string of one-off events. If you want your CAS portfolio to show real commitment, you’ll need a strategy: concrete evidence, clear timelines, and reflections that connect what you did to what you learned.

What “persistence” really looks like in CAS
Let’s be honest: persistence isn’t just doing something every week. It’s a pattern. It’s showing that you started with a goal, worked through setbacks, adjusted your approach, and arrived at measurable progress. In CAS that might mean a sports season with progressive training logs, a community service project with repeated events and expanding reach, or a creative project that develops in complexity over multiple iterations.
When assessors scan your portfolio, they’re trying to answer three simple questions: Did this student stick with it? Did they reflect on the process and learn from it? Is there evidence that the experience developed new skills or attitudes? Your job is to make those answers obvious.
Why focusing on evidence beats listing hours
Many students think CAS success is about tallying hours. Hours matter, but evidence matters more. A neat, well-documented set of artifacts and reflections that map continuity will communicate persistence far better than a long log without proof. The evidence shows not just presence, but purpose and progress.
How assessors read a CAS portfolio (and how you can shape that reading)
Assessors look for continuity, connections to learning outcomes, and honest reflection. If your portfolio clearly maps an activity across time, includes supervisor confirmation, and ties reflections to concrete milestones, you’ve already made their job easy. That increases the chance your activity will be judged as sustained engagement and meaningful personal growth.
- Chronology: Do entries show consistent engagement across weeks or months?
- Progress: Are there notes, logs, or artifacts that show development?
- Reflection: Do reflections evolve from simple descriptions to critical analysis?
- Verification: Are supervisors or community partners able to confirm involvement?
Evidence types that prove persistence (the workable checklist)
Below is a practical checklist—items you can collect now and add to each activity to demonstrate that persistence is real, not claimed.
| Evidence Item | Why it shows persistence | How to collect | Example |
|---|---|---|---|
| Timestamped attendance/logs | Proves repeated participation | Weekly sign-in sheet, digital check-ins, or calendar entries | Weekly choir rehearsal logs with dates and duration |
| Progress snapshots | Shows development over time | Photos, drafts, recorded performances saved at intervals | Before/after photos of a community garden across months |
| Supervisor confirmations | Independent verification of continuity | Signed notes, emails, or short supervisor reports | Coach email confirming attendance and increasing responsibilities |
| Milestones & certificates | Concrete achievements across the timeline | Event posters, registration receipts, certificates for stages | Completion of first-aid course, then later led training session |
| Reflections at intervals | Shows evolving thinking and learning | Initial plan, mid-point reflection, final synthesis | Journal entries showing skill set growth and changed goals |
| Project artifacts | Demonstrates tangible outputs and continuity | Design files, lesson plans, community reports, code commits | Versions of a club website showing new features added monthly |
How to make each piece of evidence count
- Annotate everything. A photo without context is just a picture. Add a 1–2 sentence note: what, when, why, and what changed since the last entry.
- Link artifacts across time. If you have a training log, reference the sessions that produced the attached photos or the reflection that references a challenge you overcame.
- Keep supervisor comments short and specific. A line about reliability, improvement, or new responsibility is stronger than a generic compliment.
Organizing your portfolio so persistence is obvious
Structure the portfolio so continuity is visible at a glance. Use a combination of timelines, folders, and summary pages that map each activity from start to finish.
A recommended folder structure (simple and scalable)
- Activity Summary (one-paragraph overview and your learning goals)
- Timeline & Logs (dated entries and sign-ins)
- Artifacts (photos, drafts, certificates — saved in chronological order)
- Supervisor Confirmation (emails, signed forms)
- Reflections (initial, midpoint, final — linked to learning outcomes)
Set up this structure for every sustained activity. Even if a particular entry is short, the folder pattern signals consistency.
Digital tips
- Use clear filenames: YYYY-MM-DD_activityname_shortdesc. That instant date stamp makes chronology undeniable.
- Keep a single, backed-up master folder for CAS assets. Duplicate important confirmations (email + signed note).
- If you use video or audio, include a short transcript or timestamp markers that point to the moment you want assessors to notice.
Reflection strategy: telling the story of persistence
Reflection is where persistence becomes meaningful. A well-structured reflection shows not just that you were present, but how you engaged, adapted and learned.
Three-stage reflection template
- Initial reflection (planning): What are your goals? What skills do you hope to build? What are the risks?
- Midpoint reflection (diagnostic): What’s working? What challenges did you hit? How did you change your plan?
- Final reflection (synthesis): What did you learn? How did your attitudes or skills change? What evidence supports that?
Keep each reflection pointed and evidence-linked. For example, in your midpoint reflection, reference a dated log or a photo that shows a turning point—this ties your narrative to proof.
Language that demonstrates persistence
Avoid vague language like “I improved.” Instead use specifics: “Between week three and week eight my 400m time dropped by 6 seconds; I tweaked my warm-up routine after coach feedback and tracked splits in my training log.” Specifics show deliberate practice.
Examples of portfolio entries that prove persistence
Here are condensed examples you can model for your own entries. Keep the pattern: timeline → artifact → supervisor note → reflection.
Example 1 — Community Tutoring
- Timeline: Weekly tutoring sessions for 24 weeks with attendance log.
- Artifacts: Copies of lesson plans, student work before/after, screenshot of scheduled sessions.
- Supervisor confirmation: Library coordinator email noting consistent turnout and increased responsibilities.
- Reflections: Initial: set learning goals for tutees; Midpoint: adapted teaching style after noticing gaps; Final: compiled before/after test scores and reflected on leadership growth.
Example 2 — Environmental Action Project
- Timeline: Monthly clean-ups, community workshops, progression to leading a student team.
- Artifacts: Project plan drafts, attendance sheets, event posters, grant application responses.
- Supervisor confirmation: Local council note acknowledging ongoing collaboration.
- Reflections: Chronological notes that link each event to long-term impact and skills built (project management, negotiation).
Practical templates you can copy into your portfolio
Here are short templates you can paste into each activity folder to make consistency automatic.
- Activity Summary (one paragraph): What I did, where, how often, and my initial goal.
- Timeline (bullet list): Date — short note about what happened.
- Artifact list: Filename — why it matters.
- Supervisor confirmation: Name, role, contact — short quote or paraphrase.
- Reflections: Initial / Midpoint / Final — 150–300 words each with links to artifacts.

How to handle supervisor confirmation and verification
Supervisor verification doesn’t need to be formal. A short email that confirms dates, responsibilities and any changes in role is powerful because it’s independent evidence. If a supervisor is uncomfortable writing much, ask them to confirm the frequency and a single observed development—for example, “Jane volunteered weekly for six months and took on training responsibilities after month three.”
Keep copies of emails, screenshots of messages, or signed notes. If a supervisor prefers phone confirmation, keep a dated note of the call with what was confirmed and who you spoke to.
Common mistakes and how to avoid them
- Thinking photos alone prove persistence — photos must be dated and annotated.
- Submitting reflections that repeat descriptions — focus on learning and change.
- Waiting until the end to collect evidence — it’s harder to recreate a timeline later.
- Relying on a single type of evidence — mix logs, supervisor notes, artifacts and reflections.
Small habit changes that make a big difference
- Spend 10 minutes after each session: annotate one artifact and add a sentence to your log.
- Once a month, write a midpoint reflection linking two artifacts to a learning outcome.
- Keep a “milestone” list and update it as soon as something significant happens (first leadership role, first public showcase, first repeat attendance).
Where to get help when you’re stuck
If you need guided help with time management, structuring reflections, or polishing artifacts, a few students find targeted academic support useful. For example, some use Sparkl‘s personalized tutoring for one-on-one guidance, tailored study plans, expert tutors and AI-driven insights to tighten their reflections and structure their evidence. Use that support to strengthen your thinking—your portfolio must still be authentically yours.
Quick persistent-evidence checklist for each activity
| Item | Kept? (Y/N) | Where stored |
|---|---|---|
| Attendance/log entries | ||
| At least three dated artifacts across timeline | ||
| Supervisor confirmation | ||
| Initial, midpoint, final reflections | ||
| One linked milestone showing growth |
Final polish: what to do the week before submission
- Run the checklist above for each activity and fill the blanks.
- Trim or expand reflections so each follows the three-stage template.
- Confirm supervisor notes are saved and unambiguous.
- Create a one-page index for your portfolio that maps each activity to its evidence and learning outcomes.
Make the assessor’s life easy
Remember: assessors are human. A tidy portfolio that clearly maps persistence to evidence and reflection will stand out more than an impressive-sounding but messy collection. Think of your portfolio as a storybook where every entry is a page with a date, an artifact, a verification and a short reflection—when those pages are arranged in time, your persistence reads loud and clear.
Conclusion
Proving persistence in CAS is less about proving you were busy and more about showing how you kept learning, adapted to challenges, and sustained effort over time. Collect dated artifacts, secure supervisor confirmations, write staged reflections, and organize your evidence so continuity is obvious. With that structure, your CAS portfolio will tell a convincing, honest story of growth and commitment.


No Comments
Leave a comment Cancel