IB DP EE Supervisor: How to Ask for Feedback Without Asking for “Approval”

IB DP EE Supervisor: How to Ask for Feedback Without Asking for “Approval”

There’s a small, tricky language problem that trips up lots of IB students: asking a supervisor for “approval.” It sounds safe and sensible—after all, you want to be sure you’re doing the right thing—but in the IB context, asking for approval can push supervisors into an awkward position and can blur the line between guidance and authorship. This post gives you practical, human ways to ask for feedback so your supervisor knows exactly how to help, you keep your academic integrity, and your Extended Essay (EE), Internal Assessment (IA), or Theory of Knowledge (TOK) work moves forward with clarity and confidence.

Why “approval” is the wrong word — and why words matter

When you ask for “approval,” the supervisor may hear you asking for a green light on something only you should be responsible for—your argument, original analysis, or final wording. In the IB philosophy, supervisors are guides; they offer advice, help you shape research questions, point to resources, and flag major issues. They are not co-authors, and they shouldn’t be asked to take responsibility for the intellectual content of your work. Using the word “approval” may unintentionally invite more intervention than is allowed or comfortable for your supervisor.

Words shape expectations. If you ask for feedback instead of approval, you give your supervisor permission to comment, critique, and point you in better directions without being put on the hook to “sign off” on your final product. That’s kinder to them and better for you.

What supervisors can help with — and what they usually won’t do

• Help refine your research question or hypothesis so it’s manageable and assessable.
• Suggest useful resources and methodologies that fit your subject and question.
• Point out structural issues, gaps in logic, and places where evidence is weak or missing.
• Clarify assessment criteria and how your work maps onto them.
• Offer limited feedback on clarity and organization—without rewriting.
• Verify that work is authentic and follows academic integrity expectations.

Conversely, supervisors generally should not write, substantially rephrase, or fill in large sections of your work. They should not provide modeled answers or do the analysis for you. Keeping those lines clear protects both of you and preserves the authenticity of your assessment.

How to ask for feedback — phrasing that works

The secret is to be specific about what you want. Instead of a vague “Please approve,” try targeted requests that make it easy for your supervisor to respond quickly and usefully. Below are practical phrases and templates you can adapt to emails, comments, or conversation starters for meetings.

Simple, high-impact phrasing

• “Could you please comment on whether my research question is focused enough for the EE?”
• “I’d value feedback on the structure of this draft—does the argument flow logically from section to section?”
• “Would you point out two or three places where my analysis is weakest?”
• “Can you check whether my citations meet the required standard for referencing?”
• “I’m deciding between two approaches to this IA experiment—could you advise which is more manageable for the assessment criteria?”

Email & conversation templates

Use concise subject lines and lead with a one-sentence context. Supervisors are busy; clarity and brevity are gifts.

• Subject: Feedback requested on EE research question and outline

  Hi [Supervisor name],
  I’ve drafted a refined research question and a one-page outline. Could you please focus on whether the research question is narrow enough and whether the planned sources/methods will allow strong analysis? Attached are the question and outline; I’d appreciate two brief suggestions for improvement. Thanks—[Your name]

• Subject: Quick check: IA methodology options

  Hi [Supervisor name],
  I’m torn between Method A and Method B for the IA. Could you tell me, in a sentence or two, which is more appropriate given the assessment criteria and why? I’ve summarized both options below. Best, [Your name]

• In-person ask: “I have 15 minutes—could you look over section 3 and tell me whether my reasoning on pages 4–5 is convincing, or point out the weakest sentence?”

Quick reference table: what to ask, why, and sample wording

Timing and practicalities: when to ask and what to send

Timing changes how a supervisor responds. If you only ask at the last minute, feedback will tend to be hurried and small. Plan multiple short, focused check-ins instead of one big “approve this” moment.

Recommended checkpoints (flexible for EE, IA, TOK)

• Initial idea: Ask whether your topic is feasible and appropriately focused.
• Research plan / methodology: Ask about sources, methods, and ethical considerations.
• First draft of key sections: Ask for structural feedback and the three biggest weaknesses.
• Near-final draft: Ask for clarity on argument and whether the conclusion is supported.
• Final check: Ask only for authentication/confirmation of academic integrity procedures (if required), not content approval.

What to send with your request

• A one-paragraph summary of what you want them to focus on.
• A highlighted section or numbered list of 3–5 questions you want answered.
• A realistic deadline—give at least a few days if you want useful feedback.
• A short note on what you’ve already tried or changed since the last feedback.

Practical tactics to control the conversation

Make your feedback easy to deliver. Supervisors respond well to structured requests that respect their time. Here are practical tactics you can use in messages or meetings.

1. Ask for a targeted number of comments

“Could you please point out up to three places where my argument is weakest?” is better than “Please tell me what’s wrong.” That constraint helps them prioritize and helps you act.

2. Use a specific rubric or criterion

Bring a criterion from the subject guide and ask how your draft meets it. Framing feedback around assessment objectives helps keep comments focused on quality rather than rewriting.

3. Offer short, incremental tasks

Rather than asking for a full read-through, ask for a short review of a single section or a one-paragraph summary. Smaller tasks are easier to schedule and more likely to produce meaningful feedback.

4. Show how you’ll use the feedback

Include a brief plan: “If you suggest changes to section 2, I’ll rework sections 3 and 4 by next week.” That demonstrates responsibility and reassures supervisors you’re not asking them to do the work.

Language to avoid — and why

• “Please approve” — suggests they must sign off on final content.
• “Can you rewrite this?” — requests authorship rather than guidance.
• “I need a perfect version” — unrealistic and shifts responsibility.

Instead, replace these with specific, actionable invitations for feedback. That preserves the ethical boundary while getting you the help you need.

Examples: bad vs good requests (realistic samples)

Seeing both versions makes the difference concrete.

• Bad: “Please approve my EE draft.”
• Good: “Could you read the conclusion and tell me whether it answers the research question and ties back to the analysis? If possible, could you point out two sentences that feel weakest?”
• Bad: “Rewrite my IA methodology.”
• Good: “I’m unsure whether my experimental design is replicable. Could you check steps 2–4 for clarity and tell me if anything could be misinterpreted?”

Handling conflicting feedback

Different teachers and supervisors might suggest different routes. Here’s a method to reconcile conflicting advice thoughtfully and respectfully:

1. Identify the precise disagreement: Is it about method, interpretation, or presentation?
2. Check the assessment criteria: Which piece of advice better helps you meet those objectives?
3. Ask a clarifying question: “Could you explain how this change would strengthen the analysis in terms of the rubric?”
4. Make an informed choice and note it—document why you chose that path in your reflections or viva voce if required.

How to act on feedback: a practical revision workflow

Feedback is only useful if you turn it into a plan. Here’s a repeatable workflow that works for EE, IA, and TOK.

• Summarize feedback in 3 bullet points.
• Translate each bullet into 1–2 concrete tasks (e.g., rewrite paragraph, gather one more source, re-run analysis).
• Estimate how long each task will take and make a mini-deadline.
• Execute the tasks and note changes clearly (use versioned filenames or a revision log).
• Report back to your supervisor with a short note: what you changed and why—this closes the loop without asking for approval.

Simple revision log example

Tools and techniques for sharing drafts

How you share a draft influences the kind of feedback you get. Options that make feedback easy include:

• Annotated PDFs or shared documents with numbered comments.
• A short cover note that lists three things you want them to focus on.
• Versioned filenames (EE_Title_v1.3).
• A one-page summary or abstract for supervisors pressed for time.

When extra support helps

Sometimes you need a little more structure than a school supervisor can give—especially if you want tailored practice on academic writing, time management, or research planning. A structured tutoring approach can complement supervisor feedback without replacing it. For example, Sparkl‘s personalized tutoring can provide one-on-one guidance, tailored study plans, expert tutors, and AI-driven insights to help you turn feedback into clear steps. Using an external tutor for practice drafts and technique coaching can leave your supervisor free to focus on subject-specific guidance and assessment-related questions.

Common questions students ask

• Can my supervisor correct grammar? They can usually point out persistent language problems and suggest how to improve clarity, but substantial rewriting is your responsibility.
• What if I disagree with my supervisor? Respectfully ask for the reasoning and link it back to the assessment objectives. If necessary, document your decision-making process.
• How many drafts should I show? Quality beats quantity. A few focused drafts with clear questions are more useful than many unfocused submissions.

Final checklist before you request feedback

• Have you stated one clear question or goal for the feedback?
• Have you attached only the relevant section to be reviewed?
• Have you noted what you’ve already changed or tried?
• Have you given a realistic timeline for a response?
• Have you avoided asking for “approval” and instead asked for targeted help?

Putting it into practice: a brief role-play

Imagine a 10-minute meeting with your supervisor. Start by saying: “I have 10 minutes. I’d like you to read the conclusion and tell me whether it answers my research question and refers back to the analysis. I’d appreciate two moments where I should tighten the argument.” Then hand them a one-page summary and the conclusion. That focused exchange delivers clear, actionable feedback and respects both your supervisor’s time and the boundaries of their role.

Closing thought

Learning to ask for feedback in a clear, respectful, and targeted way is itself an important academic skill. It helps you get the most useful guidance from supervisors while protecting the integrity and ownership of your work. By framing requests around specific goals, offering context, and showing how you’ll use the suggestions, you make it simple for supervisors to help effectively. That approach will make your EE, IA, and TOK work stronger and keep the relationship with your supervisor professional and productive.