<\/p>\nEvery Extended Essay (EE) that earns high marks closes with a conclusion that feels inevitable: the research question is answered directly, the evidence lines up, and the reader finishes with a clean sense of what the investigation has shown. Yet many students fall into the opposite trap \u2014 making claims that outpace their data. Overclaiming doesn’t just risk marks for misrepresentation; it weakens the credibility of everything you worked to build. This post is a practical, gently frank guide for IB DP students working on EE, IA, and TOK: how to write conclusions that are persuasive without being puffed up, that respect limits without sounding timid, and that leave the examiner convinced because your reasoning is clear and honest.<\/p>\n
<\/p>\n
Overclaiming is a surprisingly common mistake. It usually arises from good intentions: you want your research to feel important, the limits of your data look like small annoyances, or you\u2019re tempted to make a neat, sweeping conclusion that ties everything together. But examiners reward precision and appropriate caution. A confident but qualified conclusion suggests maturity: you understand what your methods can show and what they can\u2019t. An overclaim, by contrast, invites correction and undermines the trust built through your analysis.<\/p>\n
Although EE, IA and TOK have different forms and assessment criteria, their conclusions share a common purpose: to bring the argument to a reasoned close while accurately reflecting what the investigation has delivered. In an EE you must return to the research question and show how your evidence answers it. In an IA, the conclusion often connects to a practical task and reflects on process and outcomes. In TOK, conclusions are about the limits of knowledge claims and the interplay between different ways of knowing. In all three, the best conclusions balance claim and caveat \u2014 they say what you can reasonably say and state what remains open.<\/p>\n
Use these guiding principles as you draft and revise:<\/p>\n
Below is a compact table of common overclaims and safer alternatives. Use it as a mini-thesaurus when you edit: swap absolute words for measured verbs and insert brief limitations where needed. This table is designed to be a practical editing tool you can copy into your draft and apply line by line.<\/p>\n
| Overclaim<\/th>\n | Why it\u2019s problematic<\/th>\n | Safer alternative (phrasing)<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|
| This proves that X causes Y.<\/td>\n | Claims causation without experimental control or sufficient evidence.<\/td>\n | This suggests a possible causal link between X and Y, though further controlled study would be needed to confirm causation.<\/td>\n<\/tr>\n |
| All students will benefit from this method.<\/td>\n | Generalizes beyond the studied sample and context.<\/td>\n | Students in contexts similar to the study appeared to benefit; broader generalization requires wider sampling.<\/td>\n<\/tr>\n |
| These results show that theory Z is correct.<\/td>\n | Declares a theory true based on limited data.<\/td>\n | These results are consistent with theory Z within the study\u2019s parameters, but alternative explanations remain plausible.<\/td>\n<\/tr>\n |
| The experiment solved the problem completely.<\/td>\n | Overstates completeness and ignores residual uncertainty.<\/td>\n | The experiment reduced the problem under the tested conditions, but some issues remain unresolved.<\/td>\n<\/tr>\n |
| This changes how we should think about X everywhere.<\/td>\n | Extends findings to all contexts without justification.<\/td>\n | This offers a perspective that may be useful in contexts similar to the study; its broader applicability is a topic for future research.<\/td>\n<\/tr>\n |
| The data clearly contradict previous work.<\/td>\n | \u2018Clearly\u2019 ignores methodological differences and may misread uncertainty.<\/td>\n | The data differ from some previous findings, possibly because of methodological or contextual differences; further comparative work would clarify this discrepancy.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nStep-by-step: drafting a conclusion you can stand behind<\/h3>\nTry this short workshop as you write or revise your conclusion. Each step maps to a sentence or two; a solid EE conclusion usually sits between 150\u2013350 words (depending on your argument\u2019s complexity and the subject), but the quality of content matters far more than length.<\/p>\n
|
<\/p>\n