Balancing CAS with a heavy academic term is mainly a question of consistency, scope, and scheduling. From September to November, maintain a small number of meaningful experiences, reduce their intensity during assessment peaks, and document significant moments before reflections accumulate.
This protects time for tests, internal assessments, the Extended Essay, TOK, university applications, sleep, and recovery. The guidance below separates official IB expectations from practical recommendations because schools set their own CAS deadlines and documentation procedures.
What CAS officially requires
According to the IB overview of creativity, activity, service, CAS is a compulsory Diploma Programme core element, although it receives no numerical grade. Students must provide evidence that they have achieved the seven CAS learning outcomes.
The official IB CAS subject brief states that CAS should continue regularly for at least 18 months, with reasonable balance across:
- Creativity: developing ideas toward an original or interpretive product or performance
- Activity: physical exertion contributing to a healthy lifestyle
- Service: collaborative, reciprocal engagement responding to an authentic community need
Students must complete at least one CAS project, defined as a collaborative series of sequential experiences lasting at least one month. The official CAS project guidance confirms that it may address one strand or combine several.
There is no universal IB requirement for a particular number of CAS hours per week. Reasonable balance also does not require equal time for all three strands every week. Your school may impose approval procedures, checkpoints, or reflection deadlines, so consult its handbook and CAS coordinator.
Use a September-November maintenance model
The fall term commonly combines new units, tests, IA milestones, EE work, TOK tasks, and applications. Instead of expanding every CAS experience, use a maintenance model that preserves regular participation while allowing weekly intensity to change.
Choose 2-3 anchor experiences that are predictable and worthwhile, such as weekly sports training, rehearsals, design work, tutoring, or community support. Existing routines may qualify when they genuinely meet CAS expectations and receive approval, but ordinary responsibilities should not simply be relabelled as CAS.
A practical baseline is one fixed weekday session, one optional weekend block, a 10-15 minute documentation window after meaningful sessions, and a weekly calendar review. These are planning suggestions, not official quotas.
| Month | Academic pressure | Sensible CAS priority |
|---|---|---|
| September | New routines and early coursework | Confirm approvals, select anchor experiences, and schedule recurring sessions |
| October | Tests, IA development, EE work, or applications | Maintain core experiences, limit new commitments, and collect evidence promptly |
| November | Cumulative revision and clustered deadlines | Reduce intensity when necessary, audit the portfolio, and plan the next phase |
In September, place academic deadlines, core milestones, CAS sessions, and personal commitments in one calendar. The RevisionDojo full IB timetable guide explains how to coordinate competing responsibilities.
During October, refuse unnecessary expansion when it would weaken existing commitments. In November, review evidence, reflections, strands, and learning outcomes rather than merely counting activities. Discuss genuine gaps with your coordinator before starting anything new.
Build a schedule that survives peak weeks
Enter fixed classes, travel, meals, sleep, training, and service first. Add coursework and assessment preparation, then place CAS in the remaining realistic spaces. A calendar containing more work than available time is inaccurate, not ambitious.
Use three workload levels:
- Normal week: complete anchor experiences and documentation.
- Peak week: maintain one established experience, meet essential project obligations, and postpone optional expansion.
- Recovery week: restore sleep, update the portfolio, contact collaborators, and rebuild the schedule.
A peak week does not justify disappearing from a collaborative project. Communicate early, complete tasks others depend on, and renegotiate non-essential work. The RevisionDojo deadline management guide recommends defining concrete outputs. “Confirm Saturday volunteers and upload the rota” is more manageable than “work on CAS.”
Keep reflections specific and timely
CAS reflection should reveal learning from significant decisions, challenges, interactions, or changes. It is not necessarily a diary entry after every routine action, although your school determines the required format and frequency.
After a meaningful session, save evidence and answer four questions:
- What happened that was significant?
- What challenge, decision, or interaction required thought?
- What did I learn about myself, others, or the issue?
- What will I change next time, and which learning outcome does this support?
“I tutored for one hour” is description, not reflection. A stronger entry explains why an explanation confused the learner, how you adapted it, and what you will change next time. See the RevisionDojo CAS reflection guide for further examples.
Avoid common heavy-term mistakes
Do not treat CAS as an hourly competition. Sustained engagement, the project, portfolio evidence, and demonstrated learning outcomes matter more than accumulating an arbitrary total. The CAS minimum requirements guide clarifies the distinction between official expectations and common school practices.
Avoid starting too many experiences because each one adds planning, travel, communication, and documentation. Do not leave evidence until November, when details will be harder to reconstruct. Most importantly, protect sleep and recovery instead of turning every non-academic hour into CAS.
What to do if you are behind
Begin with a portfolio audit rather than a new activity. List approved experiences, dates, evidence, reflections, strands, and learning outcomes, then ask your coordinator which gaps actually require action.
Restore one repeatable commitment and one weekly documentation window. If a project is slipping, contact collaborators and reduce its output while preserving its purpose. The RevisionDojo guide to balancing CAS with real life offers a framework for reducing scope without abandoning continuity.
Never fabricate dates, evidence, comments, or reflections. Honest analysis of a setback and your response may provide valid evidence of planning, perseverance, collaboration, or ethical consideration.
Conclusion
To balance CAS with a heavy academic term, prioritize regularity over volume, maintain a few sustainable experiences, and reduce scope during peak weeks. Keep one calendar, document significant moments promptly, and confirm local expectations with your coordinator.
RevisionDojo can support focused academic work through the IB Questionbank, Study Notes, Flashcards, and Jojo AI while CAS continues at a manageable level.
Sources and referenced URLs
- IB creativity, activity, service overview
- Official IB CAS subject brief
- Official IB CAS project guidance
- RevisionDojo full IB timetable guide
- RevisionDojo deadline management guide
- RevisionDojo CAS reflection guide
- RevisionDojo CAS minimum requirements guide
- RevisionDojo guide to balancing CAS with real life
- RevisionDojo IB Questionbank

