IB DP EE Supervisor: What to Bring to Each Meeting (So It’s Not a Waste)

IB DP EE Supervisor: What to Bring to Each Meeting (So It’s Not a Waste)

If you’ve ever left an Extended Essay (EE) or Internal Assessment (IA) meeting feeling like you could’ve stayed in bed and gotten the same result, this piece is written for you. Meetings with your EE supervisor and your TOK advisor are short, precious, and often the difference between a stalled project and steady progress. The trick isn’t fancy vocabulary or perfect drafts — it’s showing up prepared with the right things at the right time.

This guide is a practical, student-friendly roadmap for what to bring to each meeting — from the first chat where the idea is half-formed to the final review before submission. It covers IB Extended Essay, Internal Assessments, and Theory of Knowledge sessions, giving you checklists, mini-templates, and realistic expectations for supervisor roles. There’s also a short section mentioning how targeted support such as Sparkl‘s tutoring and study plans can complement what your supervisor offers.

Why preparation matters (for you and your supervisor)

Supervisors want your project to succeed; they don’t want to write your essay for you. A meeting that wastes both of your time usually lacks focus or materials. Come prepared and you’ll get focused feedback rather than generic encouragement. Preparation creates clarity: you show your supervisor where you are, what you tried, and what you need. That clarity yields precise advice — the kind that actually changes your draft or research approach.

How supervisors typically use meeting time

• Clarifying research questions and methodology.
• Identifying gaps in evidence or reasoning.
• Pointing to structural or argument problems (not line-editing whole paragraphs).
• Checking ethical or subject-specific requirements.
• Setting clear next steps and realistic timelines.

Quick mindset checklist before every meeting

• Arrive with a 1–2 sentence update on progress (what you did since last time).
• Bring a clear goal for the meeting (one or two specific questions).
• Bring all relevant evidence or draft excerpts — not the entire thesis unless requested.
• Be ready to note action points and who does what next.

Meeting-by-meeting checklist: what to bring

Below is a practical phase map that works for EE, IA, and TOK. The headings show typical meeting phases; the content lists concrete items you should bring and the short-term goal for that meeting.

Phase details: what ‘bring’ looks like in practice

Let’s unpack each phase, with precise things you can bring that make feedback actionable.

1) Initial idea / proposal meeting

Bring a one-line research question. Yes, one line. If your question is still fuzzy, write two versions: a broad one and a tightened version. Also bring a short rationale (4–6 sentences) that explains why you care and what type of sources you expect. This helps your supervisor assess feasibility quickly.

• Example for EE: “How does X technique influence Y outcome in Z context?”
• Example for IA: “A concise list of what you will measure or compare and why.”
• Example for TOK: “A draft knowledge question and two real-life examples to explore.”

2) Methodology and planning meeting

Bring a short plan of how you will answer your question: methods, sources, and ethical considerations. If your project involves experiments, bring a protocol outline; if it’s literature-based, bring an annotated bibliography of key sources. For TOK, bring a skeletal structure showing where claims, counterclaims, and real-world examples will sit.

3) Midpoint check-in

Bring tangible evidence of progress: data tables, a 500–800 word section of writing, or summaries of the main literature. Crucially, include a short list of the three things you think are blocking you. That lets the supervisor use the meeting to unblock, not re-teach basics.

4) Draft review

Bring the draft or the critical extract your supervisor most needs to see. Add a short list of your specific concerns: “I’m worried this paragraph is repetitive” or “I can’t decide if this evidence supports claim X.” Focused questions lead to focused answers.

5) Final check

Bring the near-final version, a final bibliography, and any reflections required by your school or the IB. Confirm formatting and any other formal checklist items your supervisor requests.

Templates you can use — copy, adapt, bring

Here are concise templates students can bring as printed handouts or shared documents. Supervisors love a tidy, copyable format.

Meeting Agenda (one-page)

• 1 sentence: Current status.
• 2–3 bullets: Evidence brought to the meeting (draft extracts, data, bibliography).
• 2 focused questions for the supervisor.
• 1 clear output desired by the end of the meeting (e.g., “Agree the new research question,” or “Prioritize three revisions”).

Meeting Notes (what to record)

• Date and time.
• Decisions made and why.
• Action points with owners and deadlines.
• Any resources or references recommended by the supervisor.

Practical things to bring (formats, files, physical copies)

Think like a consultant: make it easy for the supervisor to find what you want them to look at.

• Digital: Share a PDF or a single Word file with clear headings; include page numbers so you can say, “See page 6.”
• Physical: Bring a printed copy of the page or paragraph you most want feedback on — marking is easier on paper.
• Data: A small table or CSV extract, with column labels and a one-line legend describing how the data were collected.
• Bibliography: A short annotated bibliography showing which sources are central and why.
• Timestamps: If you used recordings or multimedia, bring a short timecode list of critical clips.

What NOT to bring

• The entire thesis expecting a full rewrite — a supervisor won’t line-edit everything.
• Vague questions without examples or extract points — “Is this okay?” is too broad.
• Random articles that haven’t been skimmed — if you can’t explain their relevance in a sentence, don’t rely on them yet.

How to ask for feedback so it’s actually useful

Feedback works when it’s specific. Try these two simple techniques in your meeting agenda or notes.

• Ask for feedback by scope: “Could you check the logic in this section (pages 4–5)?”
• Ask for feedback by type: “I need help with structure, not citation style.”

When a supervisor offers a suggestion, restate it in your own words and confirm the action: “So you’d like me to move paragraph three to the beginning of the section and add a concrete example — I’ll do that by next meeting.” That reduces ambiguity and prevents repeated time-wasting conversations.

Ethics, academic honesty, and the supervisor’s limits

Supervisors are guides, not ghostwriters. They will advise on framing, method, and ethical issues, but they shouldn’t write or substantially rewrite your work. Bring any concerns about citations, data integrity, or the use of generative tools to your supervisor early so you both know the boundaries. If you’re unsure about school or IB expectations on tools and collaboration, ask your supervisor to point you to official guidance and to document the agreed approach in your meeting notes.

Tips specific to TOK meetings

TOK meetings are often shorter and more conceptual. Bring:

• A sharpened knowledge question — one short sentence.
• Two or three real-life situations you plan to use for examples.
• A sketch of how you’ll structure claim/counterclaim and link to Ways of Knowing or Areas of Knowledge.

Because TOK is about analysis and clarity, practice explaining your argument aloud before the meeting — supervisors often respond well to short verbal walkthroughs.

Sample meeting agenda and a tiny script

Use this 15-minute agenda when time is tight.

• Minute 0–2: Quick status update (one sentence).
• Minute 2–7: Show evidence (one paragraph or a single data table).
• Minute 7–12: Ask two focused questions.
• Minute 12–15: Confirm three action points and deadline.

One-line script to open a meeting

“Since we last met I’ve completed the literature summary and collected X data; I want your input specifically on whether my evidence supports Claim A or whether I should tighten the research question.” That single sentence immediately frames the meeting and signals you value the supervisor’s time and insight.

How to use feedback efficiently after the meeting

After the meeting, send a short email or message with your meeting notes, action points, and any clarifying questions. This creates a record and helps avoid miscommunication. If you make a change based on their feedback, highlight the paragraph or line and write one sentence saying what you changed and why. That makes the next meeting faster: supervisors can verify revisions rather than re-reading everything.

When extra support helps (and how it works with supervision)

Supervisors provide subject-specific guidance and high-level research mentoring. If you need extra, structured coaching — for example in writing, methodology, or managing time — targeted tutoring can fill gaps without replacing supervisor input. Services that offer 1-on-1 guidance, tailored study plans, expert tutors, and AI-driven insights can be useful complements when used responsibly alongside supervisor advice. For convenience, students sometimes pair school supervision with additional tutoring, ensuring both sources agree on academic honesty and the scope of help.

Small habits that make meetings much more productive

• Bring one printed page that summarizes the issue you most need help with.
• Highlight the exact sentence or table you want checked.
• Use the subject line when scheduling: “EE meeting — focus: research question and methods.”
• Track time and try the 15-minute agenda when your supervisor is busy.

Common pitfalls students bring to meetings (and how to avoid them)

• Too many questions at once — pick the two that matter most.
• Bringing only vague anxiety — translate worry into concrete, testable concerns.
• Expecting the supervisor to fix structure — ask for targeted structural suggestions instead.
• Not documenting the outcome — always send brief notes after the meeting.

Quick checklists you can print and bring

Two printable checklists you can copy into a notepad.

Before the meeting

• Write a one-sentence update.
• Write 1–2 focused questions.
• Prepare the exact extract you want feedback on (digital or printed).
• Bring a short list of references or a data extract.

After the meeting

• Send a short summary email with decisions and deadlines.
• Schedule the next meeting with a clear focus.
• Start the highest-priority action immediately, even if it’s just rewriting one paragraph.

Final practical notes

Keep records, keep it simple, and keep the focus narrow. Your supervisor’s time is limited; the clarity of your questions determines the quality of the answers you receive. If you build the habit of preparing a sharp one-sentence status, two focused questions, and the exact extract you want checked, your meetings will stop being a gamble and start being the productive checkpoints that move your project forward.

Treat each meeting as a mini-research sprint: prepare, show evidence, ask for one thing, and record the agreed next steps.

Your supervisor is there to mentor, to keep your project feasible and honest, and to help you learn how to conduct independent research. End each meeting with clear action points and deadlines so the next one begins with progress already made.

This is the end of the guidance on what to bring to each supervisor meeting for EE, IA, and TOK; the emphasis is on clarity, focus, and documented next steps.