<\/p>\nPicture this: it is late in the week, your brain is foggy from back-to-back classes, and suddenly every teacher announces or reminds you that something important is due on Friday. Internal Assessments, a TOK presentation draft, CAS reflections, a math assignment, plus a practice paper\u2014all piling up like an avalanche. If you are in the IB Diploma Programme, you know this scene well. It is not just about work; it is about feeling stretched thin at the end of every week.<\/p>\n
This article is a friendly two-year road map and a set of down-to-earth routines to keep your Fridays calm instead of chaotic. I will walk you through how to plan across both DP years, set up weekly systems, triage when deadlines collide, and build the mental habits that prevent the pileup from happening in the first place. Expect real examples, a sample roadmap table, a weekly schedule, and straightforward tactics you can try tonight.<\/p>\n
<\/p>\n
There are three reasons the pileup becomes a recurring pattern: (1) multiple teachers align their internal deadlines toward the end of the week for their own marking needs, (2) human tendency to procrastinate or underestimate task size, and (3) lack of a shared, student-owned schedule that tracks medium- and long-term milestones. The IB DP multiplies this because assessments are varied\u2014exam practice, Internal Assessments (IAs), the Extended Essay (EE), Theory of Knowledge (TOK) work, and CAS activities all need different kinds of time and energy.<\/p>\n
Understanding the architecture of your workload is half the battle. When you recognize the different types of work\u2014creative production (like art or EE writing), practice and retrieval (past paper practice), and administrative deliverables (IA submissions and reflections)\u2014you can allocate the right kind of time instead of reacting to whatever landed on your desk that morning.<\/p>\n
Think of the DP as a two-year project with many moving parts. Planning across both years helps you avoid last-minute scrambles: some pieces take months (Extended Essay), some take a few weeks (most IAs), and others are continuous (CAS, language practice, and exam revision). A roadmap gives you perspective: if a large task is due in the second year, you can break it into first-year prep and second-year execution.<\/p>\n
| Phase<\/th>\n | Academic priorities<\/th>\n | Concrete goals<\/th>\n | Weekly time budget (hours)<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|---|
| Start of the DP (induction)<\/td>\n | Subjects, assessment types, initial EE ideas, CAS planning<\/td>\n | Choose subjects, draft EE topic, set CAS goals<\/td>\n | 4\u20136<\/td>\n<\/tr>\n |
| Early Year 1<\/td>\n | Skill building and baseline assessments<\/td>\n | Complete baseline IAs, refine EE proposal, start CAS activities<\/td>\n | 6\u20138<\/td>\n<\/tr>\n |
| Mid Year 1<\/td>\n | IA progress, regular exam practice, time for SL vs HL differentiation<\/td>\n | Finish 1\u20132 IAs, set EE timeline, schedule TOK milestones<\/td>\n | 8\u201310<\/td>\n<\/tr>\n |
| Late Year 1<\/td>\n | Consolidate notes and skills, prepare summer tasks<\/td>\n | Complete EE first drafts\/notes, finish remaining IAs<\/td>\n | 6\u201310<\/td>\n<\/tr>\n |
| Break \/ transition<\/td>\n | Focused EE research, light revision, CAS documentation<\/td>\n | Polish EE outline, plan Year 2 work blocks<\/td>\n | Variable<\/td>\n<\/tr>\n |
| Early Year 2<\/td>\n | Major IAs, TOK essay prep, ramp up exam-style practice<\/td>\n | Submit major IAs, draft TOK essay, begin timed past-paper cycles<\/td>\n | 10\u201315<\/td>\n<\/tr>\n |
| Mid Year 2<\/td>\n | Revision cycles, final EE edits, mock exams<\/td>\n | Complete EE final draft, targeted revision for HL topics<\/td>\n | 15\u201320<\/td>\n<\/tr>\n |
| Final months<\/td>\n | Exam practice, mental preparation, finalize CAS evidence<\/td>\n | Full past-paper runs, mark with rubrics, manage well-being<\/td>\n | 15\u201325<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n Use the table as a template: replace the goals and hours with what fits your subjects and personal pace. The key is to convert large items into a series of small, scheduled tasks months ahead of the actual deadline.<\/p>\n Weekly systems that stop Fridays from exploding<\/h2>\nSmall, repeatable rituals are what prevent Friday avalanches. You do not need a perfect planner; you need a faithful one. The combination I recommend: a weekly planning session, a daily highlight, and time-blocked study sprints.<\/p>\n Sunday night \/ Monday morning weekly planning ritual<\/h3>\nDaily micro-routines<\/h3>\nPrioritization: stop treating all deadlines as identical<\/h2>\nWhen everything looks urgent, you need a method to tell the difference. Adapt a simple three-tier system:<\/p>\n
|
<\/p>\n