Track CAS Progress Across a Whole Cohort by October

By October, an IB Diploma Programme coordinator should know which students are engaging consistently with CAS, which portfolios need attention, and which students require direct support. The most effective way to track CAS progress across a whole cohort is to combine a central dashboard with portfolio sampling, documented conversations, and clear red-amber-green indicators.

October is not an official IB deadline. It is a useful internal checkpoint because it reveals problems early enough for students and staff to correct them before academic demands intensify.

Start with the official CAS requirements

A tracking system should measure what CAS requires rather than reward students for accumulating hours or uploads. According to the IB overview of creativity, activity, service, CAS is a compulsory DP core component, but it is not formally assessed with marks.

Students are expected to:

• Participate regularly in CAS for at least 18 months

• Maintain a reasonable balance across Creativity, Activity, and Service

• Complete a range of CAS experiences

• Complete at least one collaborative CAS project lasting at least one month

• Maintain a portfolio containing evidence and reflection

• Demonstrate all seven CAS learning outcomes across the programme

• Participate in the school’s required CAS interviews and monitoring

The official IB CAS project guidance explains that a project can address one, two, or all three strands. It must involve collaboration and a sequence of experiences, not a single event.

The IB does not prescribe a fixed number of hours, reflections, or October outcomes. Schools may set local deadlines, but coordinators should identify them as school procedures, not universal IB rules.

Define appropriate October progress

For students who began DP1 in August or September, reasonable October indicators include:

• The initial CAS conversation has taken place

• At least one suitable experience is active or approved

• Opportunities across the three strands have been considered

• Initial goals, evidence, or reflections appear in the portfolio

• A realistic CAS project pathway has been discussed

• Approval, safeguarding, access, and supervision issues have been addressed

These are recommended management benchmarks rather than official requirements. Schools starting the DP at another point should adjust the checkpoint accordingly.

For DP2 students, the October review should examine sustained participation, evidence for every learning outcome, project completion or a credible schedule, portfolio gaps, and readiness for final verification.

Build one cohort dashboard

The dashboard should answer three questions quickly: Who is on track? What is missing? Who must act next? It should summarise evidence held in the portfolio platform rather than duplicate every entry.

Avoid converting CAS into a points system. Several photographs and short entries do not necessarily demonstrate more progress than one sustained, well-documented experience. The dashboard supports professional judgement; it does not replace it.

Access should be restricted appropriately. Do not copy sensitive personal reflections into a widely shared spreadsheet.

Apply consistent RAG definitions

A red-amber-green system works only when staff interpret each category consistently.

Status should reflect the barrier’s seriousness, not merely the number of missing items. A student awaiting school approval may need coordinator action, while a student producing vague retrospective entries may need instruction about evidence and reflection.

Run a September-to-November cycle

September: establish the baseline

Explain CAS requirements, the portfolio platform, approval procedures, acceptable evidence, and routes for raising concerns. Complete or schedule initial interviews and record each student’s starting position.

Students needing ideas should be guided toward sustainable experiences connected to genuine interests or areas for growth. Avoid assigning identical activities simply because they are easy to track.

Early October: sample portfolios

Review every student’s headline information, then sample underlying evidence rather than reading every word. Check that experiences are suitable, participation appears authentic, and reflections address decisions, challenges, learning, or change.

The RevisionDojo guide to what coordinators want from CAS reflections helps distinguish genuine reflection from an activity summary.

Mid-October: intervene

Filter the dashboard for amber and red students. Give each student one specific next action, such as requesting approval, adding recent evidence, revising a descriptive reflection, or meeting an adviser about an accessible project.

Record the barrier, required action, person responsible, school support, and review date. This distinguishes non-compliance from practical barriers involving cost, disability access, transport, timetables, or supervision.

November: review and escalate

Recheck every amber and red student. Change the status only when evidence supports the decision, and refer persistent concerns through the school’s normal pastoral or academic monitoring process.

The RevisionDojo explanations of CAS minimum requirements and CAS verification can reinforce coordinator guidance. School procedures remain authoritative for local deadlines and approvals.

Monitor quality rather than volume

Useful portfolio evidence can include plans, schedules, drafts, products, attendance records, feedback, communications, photographs collected with appropriate consent, and supervisor confirmation. Reflection should explain what the student noticed, decided, learned, or changed.

A claim such as “I demonstrated collaboration” is weak unless the student explains the shared decision, difficulty, contribution, or result supporting it. The RevisionDojo CAS documentation guide offers prompts for moving beyond narration.

Do not require every entry to address every learning outcome. By October of DP1, coordinators should look for emerging understanding, not complete outcome coverage.

Common mistakes include treating CAS as an hours race, counting uploads as proof of progress, and waiting until the end of term to intervene. Coordinators must also distinguish an ordinary experience from the collaborative project. RevisionDojo’s comparison of a CAS project and CAS experience clarifies this difference.

Conclusion

By October, coordinators need a defensible overview of engagement, documentation, strand planning, project readiness, and barriers. A concise dashboard, consistent RAG definitions, portfolio sampling, and scheduled interventions provide that overview without reducing CAS to hours or upload totals.

RevisionDojo and Jojo AI can support students who need help interpreting requirements or improving reflection, while approval and completion decisions remain the school’s responsibility.