<\/p>\n
Why DP2 timelines trip people up<\/h2>\n
There are three broad reasons DP2 schedules collapse into stress:<\/p>\n
- \n
- Underestimating feedback loops: Drafting a piece is one thing; getting, digesting and acting on teacher feedback usually takes longer than expected.<\/li>\n
- Mismatched priorities: Treating all tasks as equally urgent leads to frantic, shallow work instead of deep, high-impact effort.<\/li>\n
- Missing buffers: When everything is planned right up to the deadline, there\u2019s no allowance for illness, logistical hiccups, or a last-minute data re-run.<\/li>\n<\/ul>\n
Recognizing which of these is tripping you up is the first step to fixing your timeline.<\/p>\n
The most common DP2 timeline mistakes\u2014and the fixes that actually stick<\/h2>\n
Mistake 1: Waiting until ‘later’ to start big internal assessments<\/h3>\n
Why it happens: The IA or EE feels huge, so you delay. Before you know it, drafts are rushed and feedback cycles compress.<\/p>\n
Fix: Reverse-plan from your submission date and block the first draft deadline at least one feedback cycle before the final submission. Break an IA into specific mini-milestones (topic selection, method, data\/research, analysis, first draft, feedback, revision). Treat each milestone as a non-negotiable appointment.<\/p>\n
Mistake 2: Treating HL and SL like identical workloads<\/h3>\n
Why it happens: You assume you can give the same time to all subjects. HL subjects often require deeper synthesis, more practice and longer IA\/portfolio pieces.<\/p>\n
Fix: Map expected workload by subject and allocate study-weighted blocks (for example: HL subjects get the largest evening block twice per week). During high-stakes windows, prioritize HL revision while keeping SL topped up with shorter bursts.<\/p>\n
Mistake 3: Skipping mock exam calibration<\/h3>\n
Why it happens: Mocks feel like practice, so students skip careful marking and target-setting afterward.<\/p>\n
Fix: Treat mocks as real exams. After each mock, block a two-day remediation plan: identify 2\u20133 recurring mistakes, build a targeted practice set, and re-test under timed conditions.<\/p>\n
Mistake 4: Leaving CAS to the end<\/h3>\n
Why it happens: CAS can feel less urgent than essays or exams, so activities and reflections accumulate.<\/p>\n
Fix: Schedule CAS activities across DP2 with monthly reflection checkpoints. Use small, consistent entries (150\u2013200 words) rather than big, last-minute essays\u2014regular reflection is easier to polish than reconstructing months of learning in one sitting.<\/p>\n
Mistake 5: Not factoring in teacher availability for IA signatures and feedback<\/h3>\n
Why it happens: Coordinators and supervisors have busy calendars; students assume feedback will be immediate.<\/p>\n
Fix: Ask about preferred communication windows early. When you set a draft deadline, add at least one extra week as buffer for your supervisor to respond and for you to revise.<\/p>\n
Mistake 6: Assuming the final draft is a one-pass job<\/h3>\n
Why it happens: After a single revision, students mark work as ‘done’ and miss smaller errors, formatting issues, or coherence problems.<\/p>\n
Fix: Build in a ‘quiet read’ phase\u2014leave the work for 48 hours, then re-read for flow, citations, and word count. Ask a peer to read with a checklist of common issues.<\/p>\n
Mistake 7: Poor file management and submission errors<\/h3>\n
Why it happens: In the rush, students upload wrong files, state incorrect metadata, or forget to create backups.<\/p>\n
Fix: Use versioned file names (example: BIO_IA_v1, BIO_IA_v2), keep a backup in cloud storage, and confirm submission details at least 72 hours ahead. If a submission portal is used, practise a dry-run with mock files.<\/p>\n
Mistake 8: Overcommitting extracurriculars during high-assessment windows<\/h3>\n
Why it happens: Students underestimate the cumulative time of events, rehearsals and matches.<\/p>\n
Fix: Be realistic: mark the high-assessment windows on your calendar and negotiate reduced extracurricular commitments for those weeks. Communicate early and give your supervisors time to adjust.<\/p>\n
Mistake 9: Not using rubrics effectively<\/h3>\n
Why it happens: Rubrics are read as bureaucratic lists rather than tactical maps to score points.<\/p>\n
Fix: Translate rubric bullets into a checklist attached to every draft. After each revision, run the checklist and annotate where each criterion is satisfied; this makes it easy to target weak spots.<\/p>\n
Mistake 10: Waiting to sort predicted grades and references<\/h3>\n
Why it happens: Students believe predicted grades will be handled automatically.<\/p>\n
Fix: Ask about predicted grade timelines early and give teachers the materials they need (subject highlights, lists of extended assignments and achievements) several weeks before university deadlines.<\/p>\n
Mistake 11: Ignoring mental-rest and recovery in a packed calendar<\/h3>\n
Why it happens: Productivity pressure encourages late nights and constant cramming.<\/p>\n
Fix: Schedule micro-breaks and one full rest day every 1\u20132 weeks during intense periods. A rested brain is more efficient; aim for consistent sleep and small restorative habits rather than heroic all-nighters.<\/p>\n
Mistake 12: Believing you can catch up without a plan<\/h3>\n
Why it happens: Students expect that one marathon working day will erase weeks of delay.<\/p>\n
Fix: Use a triage plan (below) that sorts tasks by urgency and impact. Apply the 2:2:1 rule: spend 2 blocks on urgent-high-impact tasks, 2 blocks on important-medium-impact tasks, and 1 block on maintenance activities.<\/p>\n
A compact, visual summary<\/h2>\n
\n\n
\n \nCommon Mistake<\/th>\n Why It Happens<\/th>\n Quick Fix<\/th>\n When to Start<\/th>\n<\/tr>\n<\/thead>\n \n Late IA\/EE starts<\/td>\n Task size leads to avoidance<\/td>\n Reverse-plan and set first-draft deadline<\/td>\n As soon as topics are approved<\/td>\n<\/tr>\n \n Ignoring HL workload<\/td>\n Equal-time fallacy<\/td>\n Weight calendar to HL blocks<\/td>\n Weekly schedule review<\/td>\n<\/tr>\n \n Mocks not analyzed<\/td>\n Seen as practice only<\/td>\n Treat as real: remediate and retest<\/td>\n Immediately after mock results<\/td>\n<\/tr>\n \n CAS crammed<\/td>\n Low perceived urgency<\/td>\n Monthly reflections and small entries<\/td>\n Continuously, with monthly checkpoints<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n Phase-by-phase DP2 roadmap (practical framing, not a fixed calendar)<\/h2>\n
Think in phases rather than dates. Each phase has a focus and clear milestones.<\/p>\n
Phase A \u2014 Transition and setup (first weeks)<\/h3>\n
- \n
- Confirm supervisor allocations and communication preferences for each IA\/EE\/TOK supervisor.<\/li>\n
- Create a master calendar with mock exam dates, submission windows and school-specified deadlines.<\/li>\n
- Set your \u2018first-draft\u2019 dates for each major piece at least one feedback cycle before the final deadline.<\/li>\n<\/ul>\n
Phase B \u2014 Drafting and experiment\/data collection<\/h3>\n
- \n
- Move from idea to evidence: complete experiments, collect primary data, and gather texts or sources.<\/li>\n
- Submit early conceptual outlines to supervisors and ask for a checkpoint meeting within 7\u201310 days.<\/li>\n<\/ul>\n
Phase C \u2014 Feedback, revision, and consolidation<\/h3>\n
- \n
- Have a test-run of timed papers for each subject and mark them against mark schemes.<\/li>\n
- Iterate drafts around teacher comments; prioritise issues flagged by rubrics.<\/li>\n
- Polish CAS reflections and tie activities to learning outcomes as you go.<\/li>\n<\/ul>\n
Phase D \u2014 Final polishing and exam readiness<\/h3>\n
- \n
- Run final formatting and submission checks; backup everything in two places.<\/li>\n
- Move into concentrated exam cycles: timed past papers, targeted weaknesses, and short daily review routines.<\/li>\n<\/ul>\n
Subject-specific timeline pitfalls and fixes<\/h2>\n
Sciences<\/h3>\n
Pitfall: Expecting experiments to work first time. Fix: Plan for repeats and schedule lab windows plus data analysis time. Keep a lab log with dates and raw files organized for easy reference.<\/p>\n
Mathematics<\/h3>\n
Pitfall: Leaving the exploration to the last minute. Fix: Start early with small numerical experiments\u2014quantify progress by checkpoints: idea, dataset, initial analysis, refined approach, write-up.<\/p>\n
Language A and Literature<\/h3>\n
Pitfall: Over-polishing style before arguments are solid. Fix: Prioritize argument clarity and evidence selection first; polish language in the last two revisions.<\/p>\n
Arts and Music<\/h3>\n
Pitfall: Studio work is time-consuming\u2014students under-schedule creation time. Fix: Time-block studio hours and process portfolio updates weekly so the final assembly isn\u2019t a scramble.<\/p>\n
How to recover when you\u2019re already behind: a triage plan<\/h2>\n
If you\u2019ve fallen behind, the most important thing is a realistic, prioritized checklist. Follow these steps:<\/p>\n