IB DP EE Planning: A Calm, Powerful Week-by-Week Roadmap for DP1 and DP2

Take a breath. The Extended Essay is one of the most rewarding parts of the IB Diploma: a chance to own a question, learn real research techniques, and show the clarity of your thinking. But because it unfolds over many months, it can feel like a slow, heavy ship to steer. The trick is to steer it with a weekly habit—small, steady moves add up to a completed, well-polished essay.

This guide gives you a practical, human, week-by-week plan you can adapt to your school rhythm. It is written for both DP1 and DP2 students: if you’re starting early, you’ll use the DP1 weeks to lay the foundations; if you’re in DP2, you’ll use the DP2 weeks to finish smartly. Expect flexibility, not a rigid timetable—treat each marked week as a checkpoint, not a penalty box.

Photo Idea : Student at a desk surrounded by books, a laptop, and colorful sticky notes on a wall calendar

How to use this guide

Read the overview first to understand phases, then scan the week-by-week section and pick a rhythm that matches your school terms and exam schedule. Block a regular weekly time slot (two to six hours on average, more when you’re drafting and analysing). Use the plan as a scaffold: if a week takes longer, shift the following weeks but keep the sequence intact—topic refinement before full data collection, analysis before final edits.

Quick tools and preparation

Choose a citation manager (Zotero, Mendeley or similar) and a consistent referencing style early.
Set up a single working folder (cloud plus local) for notes, drafts, and data backups.
Keep a research journal: short, dated entries after each work session make supervisor meetings richer.
Block weekly calendar reminders for supervisor check-ins and draft milestones.

Phase overview: the roadmap in five phases

At a glance, your EE moves through five clear phases. The table below maps those phases to rough week ranges, goals and deliverables so you can see the big picture before we dive into the week-by-week details.

Phase	Approx. Weeks	Primary Goal	Key Deliverables	Weekly Hours
Topic & Question Refinement	Weeks 1–10	Find a focused, researchable question	Shortlist of topics, refined research question, proposal	2–4
Literature & Method Setup	Weeks 11–24	Map literature, choose methods, pilot tests	Annotated bibliography, methodology plan, pilot results	3–5
Data Collection & Initial Analysis	Weeks 25–44	Collect quality data and start analysis	Collected dataset/field notes, preliminary analysis	4–7
Drafting	Weeks 45–66	Write up full draft with figures and citations	Full draft submitted to supervisor, TOK link notes	6–10
Revision & Submission	Weeks 67–80	Polish language, structure and criteria alignment	Final version, abstract, final bibliography	4–8

Detailed week-by-week plan (80 weeks — adaptable)

Below is a pragmatic week-by-week schedule. Your school calendar, holidays and other deadlines may shift the order slightly—use it as a master plan and adapt the tempo. Regularly check your work against the IB assessment criteria for your subject.

Week 1: Brainstorm broad subject areas; list 3–5 topics that genuinely interest you.
Week 2: Skim a few reputable sources on each topic; note surprises and questions.
Week 3: Talk to potential supervisors; capture quick feedback and feasibility notes.
Week 4: Narrow to one topic and write three possible research questions.
Week 5: Test each question for clarity, scope and available sources; drop the too-broad ones.
Week 6: Draft a one-page research proposal: question, why it matters, and likely method.
Week 7: Build a preliminary reading list of 10–15 sources and start an annotated bibliography.
Week 8: Map keywords and search terms; practice database and library searches.
Week 9: Discuss ethics or permissions needed for your research with your supervisor.
Week 10: Finalise the research question and get supervisor sign-off on the proposal.
Week 11: Deepen literature review: summarise main arguments and identify gaps.
Week 12: Draft a detailed methodology section and timeline for data collection.
Week 13: Create data collection instruments (surveys, interview prompts, lab setup).
Week 14: Pilot your tools on a small sample; record what changes are needed.
Week 15: Revise instruments and prepare consent forms or lab protocols if needed.
Week 16: Final checklist for data collection: backup plans, ethical notes, logistics.
Week 17: Begin formal data collection; keep daily logs of what you do.
Week 18: Continue data collection and resolve early practical issues.
Week 19: Mid-collection check: compare initial data to your expectations.
Week 20: Continue and complete the first main block of data collection.
Week 21: Back up and organise all raw data; create a master file and codebook.
Week 22: Start basic analysis: coding themes or descriptive stats to find patterns.
Week 23: Return to literature: add sources that speak to emerging themes.
Week 24: Refine analysis approach and check for missing variables or gaps.
Week 25: Begin drafting the Methods and Data sections with clear steps illustrated.
Week 26: Draft a concise context and rationale for your Introduction.
Week 27: Create a detailed outline for the whole essay with word estimates.
Week 28: Write the first full version of the literature review subsection.
Week 29: Build initial Results/Findings pages with tables and selective quotes.
Week 30: Write a preliminary Discussion tying findings to specific sources.
Week 31: Share draft sections with your supervisor and request targeted feedback.
Week 32: Revise using supervisor notes; focus on argument flow, not just grammar.
Week 33: Add TOK links or methodological reflection paragraphs where relevant.
Week 34: Polish citations and ensure every claim is supported by a source.
Week 35: Conduct a peer review or tutor review to catch weak spots in logic.
Week 36: Rework the argument structure based on external feedback.
Week 37: Deepen analysis: additional tests, alternate codings, or richer quotes.
Week 38: Prepare figures, tables and appendices; label everything clearly.
Week 39: Ensure word counts per section meet criteria and keep space for conclusion.
Week 40: Second full draft: smooth transitions and stronger topic sentences.
Week 41: Intensive rewrite of Results and Discussion for clarity and precision.
Week 42: Tighten the introduction so it directly frames your findings.
Week 43: Draft a clear, focused abstract that reflects the completed essay.
Week 44: Review and refine methodology language to match what you actually did.
Week 45: Copy-edit for academic tone, sentence rhythm and logical connectors.
Week 46: Check referencing meticulously: every citation, every bibliography entry.
Week 47: Run a final quality-check on formatting, footnotes and appendices.
Week 48: Ask your supervisor for a final read and request any last clarifications.
Week 49: Incorporate final supervisor comments and tighten arguments where needed.
Week 50: Proofread for spelling, punctuation and typographical consistency.
Week 51: Final check of word count, citations and assessment criteria alignment.
Week 52: Prepare the final PDF in the exact format your school requires.
Week 53: Compile a short reflective note about limitations and future work (useful for TOK).
Week 54: Final supervisor sign-off: get confirmation that everything is ready.
Week 55: Ensure backups are complete; save a timestamped copy of final version.
Week 56: Submit. Then step away: allow yourself a full rest day to reset.
Week 57: If external viva or presentation is required, prepare concise talking points.
Week 58: Reflect: write a short learning log about research skills you acquired.
Week 59: Convert key findings into a short summary useful for university applications.
Week 60: Archive your research materials with clear filenames for future reference.
Week 61: Revisit the EE with fresh eyes if corrections are requested by your school.
Week 62: Prepare any required documentation for final submission records.
Week 63: Finalize any administrative steps and celebrate the milestone privately.
Week 64: Extract lessons learned: what worked in your research workflow?
Week 65: Draft a short guide for future students in your cohort—hand it to your supervisor.
Week 66: Optional: create a short poster or presentation summarizing your EE.
Week 67: Reconnect EE insights to TOK or IA projects before those assessments close.
Week 68: File any final paperwork and confirm your final grade submission timeline.
Week 69: Share gratitude with mentors and anyone who assisted you during the project.
Week 70: Store your supervisor comments and your own reflections for future reference.
Week 71: If you plan to publish or reuse parts of your EE, check permissions and ethics again.
Week 72: Consider whether parts of the research can be expanded for university study.
Week 73: Maintain your research folder so it can support university essays or interviews.
Week 74: Keep a shortlist of sources that were most useful for future reading.
Week 75: Revisit any unresolved questions and jot down next-steps ideas.
Week 76: Reassess your time-management: what weekly habits will you keep?
Week 77: Write a short piece connecting your EE to broader academic interests.
Week 78: Share the finished product with a mentor outside school for feedback.
Week 79: Archive final data with clear metadata and retention notes.
Week 80: Close your project file and carry forward the research skills you have earned.

Photo Idea : Close-up of hands typing code and creating a chart on a laptop screen

Supervisor meetings: make them count

Supervisor time is precious. Treat each meeting like an investment: prepare a one-page update, a short list of problems, and a specific ask (e.g., help with argument structure, feedback on draft paragraph, or ethics advice). In the early phase, ask about feasibility and scope. In later phases, focus on clarity and alignment with assessment criteria.

Bring dated notes from every week: shows progress and makes feedback precise.
Agree on turnaround times for feedback so you both know expectations.
Record action points at the end of each meeting and send a short follow-up email.

Common pitfalls—and quick fixes

Pitfall: Question too broad. Fix: Break it into a focused, testable sub-question.
Pitfall: Procrastination during data collection. Fix: Calendar-block data days and pair them with a friend or study-buddy.
Pitfall: Overwhelming literature review. Fix: Use a synthesis table and limit to the most relevant debates.
Pitfall: Weak linkage between results and literature. Fix: Revisit the literature and annotate direct connections as you go.

How extra support can fit naturally

It’s normal to need subject-specific guidance for methodology or analysis. If you choose external support, make sure it supplements your own thinking and is transparent to your supervisor. For example, Sparkl‘s 1-on-1 guidance can help you structure drafts, build a tailored study plan, or sharpen methodological choices. Use tutoring to clarify methods, rehearse presentations, or get focused feedback on weak sections—then bring that work back into your supervisor conversations.

Linking the EE to TOK and your IAs

The EE is stronger when it connects to Theory of Knowledge and Internal Assessments: TOK can provide methodological reflection and a language for epistemic limits, while some IA work can offer transferable methods or data. A short TOK paragraph in your EE that reflects on knowledge frameworks or evidence strengthens the reflective dimension of your essay. Keep these links concrete: show exactly where TOK concepts relate to your choice of evidence or interpretation.

Final checklist before submission

Research question is clear and present in the introduction.
Methodology section explains process, sample, tools and limits.
Analysis is directly tied to evidence and literature.
Word count is within the allowed range and each paragraph advances the argument.
Bibliography is complete and consistent with a recognized style.
Abstract succinctly states the question, approach, results and conclusion.
Supervisor has signed off or given clear confirmation of completion.

Planning your EE week by week transforms a distant deadline into a sequence of achievable tasks. Steadily collecting evidence, meeting your supervisor with focused questions, and iterating drafts will take you from a fuzzy idea to a clear, evidence-based essay. Keep the process visible—dated notes, saved drafts and a short log of decisions are your best friends during feedback cycles, and they also make the TOK and reflection elements richer and more honest.

Finish by checking your work carefully against the assessment criteria one last time, confirm the final submission format with your coordinator, and ensure your citations, abstract, and appendices are complete. This disciplined, steady approach is what transforms an Extended Essay into a project you can be proud of.