What the CAS coordinator is accountable for
Creativity, activity, service is one of the three core elements every Diploma Programme student completes. It carries no marks and contributes no points, and a student who does not complete it does not receive the diploma. That asymmetry is the whole job.
The coordinator is not accountable for what students choose to do. They are accountable for being able to say, for every student in the cohort, that the student engaged over the required period, undertook experiences across the strands, completed a CAS project, reflected meaningfully, and demonstrated each of the learning outcomes.
The IB's current CAS guide and the Diploma Programme assessment procedures are the authority on the requirements. What follows is about running it across a cohort, which is the part no document covers.
The three strands, and what counts
Creativity covers exploring and extending ideas leading to an original or interpretive product or performance. Activity covers physical exertion contributing to a healthy lifestyle. Service covers collaborative and reciprocal engagement with a community in response to an authentic need.
Students must undertake experiences across all three, and the most common argument a coordinator has is about whether something counts. The useful test is not the category but the shape: is there a goal, is the student stretched by it, is there something to reflect on afterwards, and in the case of service, was the need identified with the community rather than assumed on its behalf.
The unhelpful test is hours. Counting hours produces students who log time and learn nothing, and the requirement is engagement over a period rather than an hours total.
The seven learning outcomes
Every student must demonstrate all seven outcomes at least once across their programme, and the reflections are the evidence that they have.
They cover identifying strengths and areas for growth, taking on new challenges and developing new skills, planning and initiating an experience, showing commitment and perseverance, working collaboratively, engaging with issues of global significance, and recognising the ethical implications of one's choices and actions.
Two are consistently the last to be met, and a coordinator who knows which two can intervene early. Initiating and planning an experience is hard for students who join existing activities rather than starting anything. Engaging with issues of global significance is hard for students whose experiences are all local and personal. Both are fixable in Year 1 and painful to fix in the final term.
The CAS project
Every student completes at least one CAS project, which is a collaborative undertaking of at least a month involving one or more strands, taken through investigation, preparation, action, reflection and demonstration.
It is the component most likely to be left late and most likely to be done badly when it is. The failure pattern is a group of friends who agree on an idea in the final year, hold two meetings, run an event and write it up. Technically complete, educationally empty.
The intervention that works is requiring the project to be proposed and approved early, with a named group and a real duration, and then checking in during it rather than at the end.
The three interviews
The programme is structured around three documented conversations between each student and the coordinator or a CAS adviser.
The first comes at the start and is about planning: what the student intends, where the gaps in the strands are likely to be, and which outcomes will be hard for this particular student. The second comes around the end of the first year and is the one that actually saves students, because it is the last point at which a thin programme can be turned around without panic. The third is summative, near the end, where the student sets out how they have met the outcomes.
The second interview is the one schools most often let slip, usually because it falls in a busy term. A coordinator who protects nothing else in the calendar should protect that one.
Reflection, and why most of it is not worth reading
Reflection is the evidence base for the entire requirement, and most of what students produce is a description of events.
The difference between a log and a reflection is that a reflection says something the student did not know before. What was harder than expected, what they got wrong, what they would do differently, what it revealed about them. A coordinator asking for more reflections when the existing ones are descriptive will get more description.
Two practical fixes: ask for fewer reflections of better quality rather than a fixed frequency, and let students reflect in whatever medium suits them. A video, a sketch or a recorded conversation is often more honest than the paragraph a student writes because a form demanded one.
Evidence: what to ask for and what not to
Evidence exists to support the claim that an outcome was met. It is not a scrapbook and it is not a compliance exercise, and treating it as either produces enormous volume and no information.
Photographs are weak evidence of learning and strong evidence of attendance. Supervisor confirmation is useful for participation. The student's own reflection, tied to a named outcome, is what actually carries the case. A coordinator reviewing a portfolio should be able to point at each of the seven outcomes and find the moment the student demonstrated it, which means the tie between reflection and outcome has to be explicit rather than inferred later.
- Ask which outcome each reflection is evidence for, at the time it is written
- Prefer one considered reflection to four descriptive ones
- Use supervisor confirmation for participation, not for learning
- Check the strand spread and the outcome spread separately
The eighteen months, and the students who drift
CAS runs across the Diploma Programme for a minimum engagement period of around eighteen months, undertaken regularly rather than in bursts. Students fail CAS by not engaging regularly, by not meeting every outcome, or by providing so little reflection that no case can be made.
Drift is the real risk, and it is invisible in aggregate. A cohort can look healthy while a dozen students have logged nothing since the spring. The coordinator's core operational problem is therefore not gathering evidence but noticing absence, early, per student, across a cohort of a hundred or more.
That is a reporting problem, and it is the argument for running CAS somewhere you can query rather than in a shared folder.
Running CAS across a cohort, in practice
This section names our own product, so take it as that. Everything above holds regardless of what you use, including paper.
skodle models CAS the way the requirement is actually shaped. A CAS experience is a record with a goal, learning goals attached to it, a named supervisor, a start and due date, milestones through the middle, and the student's reflection held against it — the same structure that carries the PYP exhibition, the MYP personal and community projects and service as action, so a continuum school has one model rather than four.
Alongside that, CAS sits in the DP core tracker with internal assessment, the extended essay and theory of knowledge, and the components run through milestones per student. A risk view over the core surfaces students who are behind, which is the answer to the drift problem: the coordinator sees who has logged nothing since March without opening a hundred portfolios to find out.
The limits, plainly. skodle does not decide whether an outcome has been met, and it should not; that is the coordinator's judgement and the interview is where it is made. It also does not carry the official IB route for registration or coursework submission.
When a student has not met an outcome in March
It happens every year, and the response matters more than the prevention at that point.
The first move is to establish whether the outcome is genuinely unmet or merely unevidenced, because they need different fixes and students routinely have done the thing and never written about it. If it is unevidenced, a considered reflection on an experience that already happened is legitimate and quick. If it is genuinely unmet, the student needs an experience designed around that outcome, small and real, with time to reflect afterwards.
What does not work is inventing a retrospective claim, which is both dishonest and obvious to anybody reading the portfolio.
What to hand over when you leave
CAS coordination turns over often, and the handover is usually a folder and a conversation. It should be more.
The next coordinator needs the cohort's current state per student, the calendar of interviews with what was said, the list of approved projects, the school's own interpretation of what counts, and the record of decisions made on hard cases. That last item is the one nobody writes down and the one that makes a new coordinator inconsistent with the old one in their first term.
