<\/p>\nThere\u2019s a tricky, familiar moment for many IB students: your supervisor sits across from you, genuinely keen to help, and by the end of the conversation you\u2019re holding page-long edits, a suggested conclusion you didn\u2019t write, or an instruction that feels like a shortcut through your learning. It\u2019s flattering, but it doesn\u2019t always feel right. And for IA, EE and TOK work\u2014where authenticity, critical thinking and student ownership are the core of assessment\u2014too much direction can quietly erode everything you\u2019re supposed to be demonstrating.<\/p>\n
<\/p>\n
This article is a practical, human guide for students navigating that middle ground: how to notice when guidance becomes directive, how to respond calmly and constructively, and how to preserve your voice without creating conflict. You\u2019ll find everyday phrases you can use, meeting rituals to reduce friction, a simple table that translates supervisor signals into student responses, and specific tips tailored to Internal Assessments (IA), the Extended Essay (EE) and Theory of Knowledge (TOK).<\/p>\n
Most supervisors mean well. They\u2019ve seen students struggle with research scope, analysis or argument structure and want to prevent wasted time. Too often, eagerness turns into specificity: the supervisor suggests exact words, prescribes an approach, or rewrites paragraphs. That can save time in the short term, but it can also remove the intellectual work you need to show.<\/p>\n
The issue matters for three reasons. First, assessment: IB examiners look for student-authored thinking and reasoning. Second, learning: you will learn more by working through arguments and methods yourself. Third, fairness: if supervisory input becomes substantive, it can breach academic honesty expectations. Knowing the difference between support and direction protects your progress\u2014and your integrity.<\/p>\n
Understanding motive helps you respond without accusing. Supervisors may be directive because they want to protect you from failure, because they\u2019re pressed for time and think a quick fix is kinder, or because they\u2019re used to a teaching style that models answers. Sometimes they simply have institutional pressure or nervousness about authenticity checks. Recognizing the why lets you choose language that acknowledges good intent and redirects the help productively.<\/p>\n
The heart of this approach is calm clarity: signal appreciation, state your needs, and invite collaborative boundaries. Here are concrete steps you can use across IA, EE and TOK supervision.<\/p>\n
People respond better to invitations than to corrections. Try these conversational moves when a supervisor starts offering too much detail:<\/p>\n
Send a brief email summary that both confirms what was agreed and creates a paper trail. Keep it neutral and appreciative\u2014this is about clarity, not accusation. Example structure:<\/p>\n
| Supervisor Behavior<\/th>\n | What it might mean<\/th>\n | Short Student Response (tone: collaborative)<\/th>\n<\/tr>\n |
|---|---|---|
| Suggests whole paragraphs or writes sentences for your essay<\/td>\n | Trying to solve clarity problems quickly<\/td>\n | “Thanks \u2014 could you point to the idea here that I should be expressing, and I\u2019ll draft it in my own voice?”<\/td>\n<\/tr>\n |
| Dictates the structure step\u2011by\u2011step<\/td>\n | Wants to ensure coherence; may be anxious about deadlines<\/td>\n | “I appreciate the structure. Can we agree on the key moves, and I\u2019ll propose a two-paragraph outline to check next time?”<\/td>\n<\/tr>\n |
| Interprets your results for you<\/td>\n | Worries about accuracy, or assumes you need an example<\/td>\n | “Could you show me the approach you\u2019d use to interpret this, so I can try it first and then compare notes?”<\/td>\n<\/tr>\n<\/table><\/div>\nTemplates you can use: short scripts and email phrasing<\/h2>\nKeep language short and matter-of-fact. Here are three templates you can adapt.<\/p>\n In-meeting script to redirect help<\/h3>\n“I really appreciate that example. For this draft I want to keep the wording in my voice so the examiners see my thinking\u2014could you point to the places you feel are weakest and suggest the kind of reasoning I should use instead?”<\/p>\n Follow-up email (after a meeting)<\/h3>\n“Thank you for meeting today. To confirm: I will revise my research question and send the next 800 words by Friday; you suggested focusing feedback on the argument structure and one issue with my method. Please let me know if I misunderstood anything.”<\/p>\n Short boundary-setting note (if pattern repeats)<\/h3>\n“I’ve noticed I do my best learning when I draft solutions and then receive high-level critique. Would you be open to a compact where I send a draft and you comment only on three priority areas rather than line-editing? I think that will help me develop my independent reasoning.”<\/p>\n Specific guidance: IA, EE and TOK<\/h2>\nEach assessed piece has its own expectations and typical supervisory pitfalls. Below are tailored tips to keep your work authentic without cutting yourself off from useful support.<\/p>\n Internal Assessments (IA)<\/h3>\nExtended Essay (EE)<\/h3>\nTheory of Knowledge (TOK)<\/h3>\nDocumenting the process: meeting logs, annotated drafts, and evidence<\/h2>\nDocumentation isn\u2019t about suspicion; it\u2019s good practice. It helps you remember guidance, shows your evolution of thought, and protects both you and your supervisor if concerns arise. Simple records are all you need:<\/p>\n
|
<\/p>\n