IB DP IA + EE + TOK: How to Prevent “Draft Fatigue” Across Assessments

IB DP IA + EE + TOK: How to Prevent “Draft Fatigue” Across Assessments

If you’ve ever stared at a blinking cursor and felt your energy leak away, you’re not alone. Draft fatigue is the quiet, stubborn slowdown that turns the final sprint of your IB journey into a slog: you start strong, make progress, then watch momentum evaporate into endless rewording, worry, and tiny revisions that never quite finish.

This is especially familiar when you’re juggling three different beasts: Internal Assessments (IAs) that demand sharp, criterion-focused work; the Extended Essay (EE), which asks for deep, sustained research and structure; and Theory of Knowledge (TOK), a different kind of intellectual tightrope. Each asks for a different muscle, and switching between them without a plan is how fatigue sneaks in.

What we mean by “draft fatigue”

Draft fatigue looks like any of these: rewriting the same paragraph for hours, delaying submission because it “isn’t perfect yet,” losing sight of assessment criteria, or bouncing between IA calculations, EE references, and TOK arguments without making measurable progress in any. It’s not lack of intelligence—it’s an efficiency problem, a focus problem, and often a feedback problem.

Good news: draft fatigue is solvable. With targeted routines, clearer pass goals, and a few structural habits, you can turn anxious tinkering into confident, visible progress across all three IB tasks.

Why IA, EE, and TOK are a tricky trio

Understanding where each assessment drains your energy gives you a fighting chance. They’re not identical, and treating them as if they are is a fast track to burnout.

How each assessment triggers fatigue differently

Mindset: small wins beat perfect drafts

Start by shifting the way you measure “good work.” Instead of asking whether a paragraph is perfect, ask whether the paragraph advances a specific assessment criterion. Instead of deleting whole sections, make a quick pass that marks what to keep and what to move. This reframes drafting as a series of small, measurable wins.

Here are three mental moves that reduce fatigue fast:

• Pass-or-do-not: Decide ahead of time whether a session is for drafting new material or editing—don’t mix both.
• Criterion-first editing: Open the rubric before you open your document and pick one or two criteria to address in that session.
• One-thing focus: Choose one micro-goal (e.g., “write 300 new words on EE methodology” or “tighten IA graphs”) and stop when that’s done.

Practical routines: planning that protects your attention

Routine isn’t about rigidity; it’s about reducing friction. With the right structure, you spend less energy deciding what to do and more energy doing it.

1. Plan by passes, not by perfection

Most students fatigue because they try to solve every problem in a single pass. Instead, design a small number of focused passes. Below is a simple five-pass approach that’s flexible enough for IA, EE, and TOK:

What matters is not how long each pass takes—you can split them into short sessions. The key is the mindset: each pass has a single, measurable job. When your brain knows the job, it wastes less energy deciding what to do next.

2. Use micro-deadlines and interleave tasks

Alternate short bursts on IA, EE, and TOK rather than slamming one assessment for a whole week. Interleaving tasks keeps mental freshness and helps transfer insights across assessments—for example, a clearer TOK counterclaim structure might inspire a stronger EE concession paragraph.

Sample weekly flow (example of interleaving):

• Monday: 60–90 minute EE research/writing sprint.
• Tuesday: Short IA experiment/data check (45 minutes) + 30-minute TOK planning session.
• Wednesday: Feedback session with a teacher or peer for one assessment (45 minutes).
• Thursday: EE revision pass (60–90 minutes).
• Friday: TOK drafting and polishing (60 minutes).
• Weekend: Light formatting, citations, or rest—small tidy tasks (30–60 minutes).

3. Time-box with sprints, not marathons

Sprints (e.g., 25–50 minute focused sessions) are lifesavers. They lower the cognitive cost of starting and make it easier to measure small wins. Use a single pass goal per sprint and record what you accomplished. That log is proof of consistent progress—an antidote to the feeling that nothing is moving.

4. Targeted feedback and smart revision

Feedback is fuel—if it’s specific. A broad comment like “needs clarity” is demoralizing; a precise suggestion like “move this sentence to lead paragraph 2 and add a citation” is actionable. When you receive feedback, convert each comment into a single task and place it in the relevant pass slot—don’t treat feedback as a cue to start an unlimited overhaul.

If you want guided, one-to-one help that sets pass goals and provides criterion-aligned feedback, consider Sparkl‘s personalized tutoring, which can bring an external, structured perspective to your draft process.

5. Use checklists, templates, and rubrics

Turn invisible expectations into visible checkpoints. For each pass, keep a short checklist tied to the rubric. For example, an IA pass 3 checklist might include: “clear research question”, “method description matches data presented”, “graph labels and captions present”, “explicit link to criterion B”. Making rubrics operational is a huge energy saver.

Tools and practical resources (non-tech-heavy)

You don’t need fancy software—what you need are habits that reduce decision fatigue.

• Single-document system: Keep one main working draft and a versioning folder for major saved copies (avoid endless ‘final-final-revised’ files).
• Reference snapshot: Keep a one-page note of the key sources and their role in your argument to avoid re-searching.
• Comment-to-task: Turn comments into a simple to-do list that you can tick off during the appropriate pass.

Quick recovery hacks when fatigue hits

• Switch modes: Move from writing to formatting, or from reading to outlining; changing the type of cognitive load gives your brain a reset.
• Do a safety save and set a 20-minute timer to produce one micro-output (e.g., a paragraph, a graph, a slide).
• Limit revision windows: Promise yourself a maximum of two passes in one day to avoid endless tinkering.
• Use the 3-2-1 rule for feedback: pick 3 strengths, 2 things to clarify, 1 fix to make now.

Sample timelines and examples

Below are short, adaptable examples you can copy and tailor. These are not prescriptions—think of them as templates that set reasonable expectations and guard against open-ended tinkering.

Draft-pass schedule (compact view)

Example: how to split a heavy EE week

If a week feels daunting, split it. A practical template:

• Day 1: 90-minute research and note-taking (focus on 2 primary sources)
• Day 2: 50-minute drafting sprint (one subsection)
• Day 3: 30-minute rubric mapping for that subsection
• Day 4: Break or light review (citations, formatting)
• Day 5: 50-minute second draft pass

How to keep feedback useful and deadlines humane

Don’t treat feedback as a final verdict. Treat it as a map. The person giving feedback may not have the same rubric in front of them—your job is to translate comments into the pass structure you are following. If you’re using external help, a tutor or mentor should leave tasks, not just comments. That’s where targeted tutoring is powerful: a tutor can give you a short checklist that feeds directly into your next pass. For example, Sparkl‘s tutors often break feedback into clear tasks so students can act rather than stall.

Version control: save sanity and time

Always label saved drafts by pass and date—e.g., EE_Pass2_Notes_Week6. That way you can restore earlier ideas if a later pass removes something useful. Versioning protects you from the “I liked that sentence better two weeks ago” panic and reduces the urge to re-edit everything.

Final checklist: daily and pre-submission

Use this checklist to close each work session and to run one final sweep before submission. Each item is small and actionable, so it’s easier to do than to dread.

• Session end: Record one concrete achievement (e.g., “EE: wrote 400 words on methods”).
• Rubric check: Have you ticked off at least one rubric point during this session?
• Version save: Save with pass number and date.
• Quick read: Read aloud one paragraph to check clarity.
• Final sweep: Check citations, word count, formatting, and submission instructions.

Conclusion

Draft fatigue is a signal, not a sentence: it tells you your process needs structure, not that you can’t finish well. Reframe drafting as a set of passes, use micro-deadlines, interleave different tasks, and turn feedback into discrete actions. With reproducible routines—clear pass goals, short sprints, versioned drafts, and criterion-aligned checklists—you’ll convert anxiety into momentum and reach submission with clarity and confidence.