Recover from common core and coursework problems
Use evidence and school support to repair a stalled project, incorrect brief or missing submission detail.
Name the problem and its current effect
When coursework goes wrong, write a factual account before changing everything. Identify the task, deadline, completed work, missing step and consequence. Distinguish an argument problem from a procedural problem or an access difficulty. A broad statement that 'the project is ruined' makes planning harder. Concrete details help you choose the next action and explain the situation to a teacher. Check the task's current requirements before relying on a remembered rule. Many avoidable problems begin with an assumption that was never verified.
Confirm the guide before repairing the draft
If you discover that you used an old structure or exemplar, compare it with your current subject, level and session guidance. Ask the teacher which work remains useful and what must change. Do not discard sound analysis simply because headings need revision. Equally, do not assume a cosmetic edit resolves a changed task. The relevant question is whether your work demonstrates what the current assessment requires. Curriculum versions matter, including EE changes from 2027 and mathematics changes first assessed in 2029.
Use honesty when evidence is missing
If data, source access or activity records are missing, explain the gap and identify legitimate alternatives. A smaller approved investigation, revised source set or genuinely completed experience may be possible, depending on the task and timing. Do not invent results, quotations or participation to make the document look finished. Preserve what you have and record the attempted steps. A teacher or coordinator can advise using the actual facts. They cannot make an informed decision if the difficulty is concealed behind a fabricated account.
Work through a practical recovery example
Imagine a student notices that a TOK exhibition draft uses broad symbolic objects with no specific context. The student returns to the prompt and existing object-selection guidance, identifies real objects they can accurately document and checks the proposed revision with the teacher within permitted support. They then rewrite each commentary around a distinct contribution. The recovery addresses the underlying issue instead of adding more abstract terminology. This illustrative sequence depends on time and school arrangements, but it shows how diagnosing the problem makes the revision purposeful.
Make a recovery plan with dependencies
Choose the smallest set of actions needed to resolve the issue and place them before the school deadline. Put approvals and access requests first where later work depends on them. Leave time for checking the repaired deliverable. If the schedule no longer fits, raise the problem promptly with progress details and the blocked steps. Avoid promising an unrealistic overnight solution merely to end the conversation. A credible plan acknowledges uncertainty and explains what evidence will show that each repair is complete.
Prevent recurrence through one changed habit
After resolving the immediate problem, change the practice that allowed it to develop. Possible habits include recording rule sources, testing feasibility early, keeping version history, reviewing CAS evidence regularly or opening the exported file before submission. Choose a change that fits the actual cause rather than installing an elaborate new system. Review whether it works during the next task. A useful recovery leaves you with both a repaired piece of work and a better way to notice the same problem while it is still small.
Your next-step checklist
Checklist choices stay in this browser.
Official references
This is an original practical guide from IBvia. The examples are illustrative; your subject guide, assessment year and school instructions determine the requirements.
Keep working on your next step
Turn DP2 deadlines into a workable plan
Work backwards from your school's dates, spot dependencies and protect time for revisions and exams.
Read the guide ↗
Turn teacher feedback into visible revisions
Translate comments into actions, repair the reasoning first and verify that the revised draft solves the problem.
Read the guide ↗