IB DP EE Supervisor: How to Document Your Thinking Without Sounding Fake

EE Supervision: Documenting Your Thinking with Authenticity

Being an EE supervisor in the IB Diploma Programme often feels like walking a tightrope: you want to guide, protect academic integrity, and help a student improve without taking their work or sounding like every other generic comment a marker has ever read. The trick isn’t clever phrasing—it’s honest, compact notes that record your thinking, your interventions, and the student’s responses in a way that anyone reading later (examiner, coordinator, or the student themselves) can follow the reasoning and see how the work evolved.

In practice that means trading empty praise for evidence-rich observations, and trading long lectures for short, time-stamped nudges. Whether you are supporting an Extended Essay, an Internal Assessment, or a Theory of Knowledge piece, this approach preserves student ownership while creating a clear, honest paper trail of learning.

Why “sounding fake” happens—and why it matters

We all fall into canned phrases when time is short: ‘Excellent work,’ ‘Good insight,’ ‘Well-structured.’ Those lines are comforting to write and read, but they reveal nothing about process and can sound performative. A supervisor note that says only ‘Good job’ tells an examiner nothing about how the student arrived at their claims, nor whether the supervisor contributed substantial ideas (and if so, what they were).

Fake-sounding notes matter because the IB values student agency and authentic thinking. Examiners and coordinators need to see evidence of intellectual development, teacher guidance, and, where appropriate, remedial action. A precise, restrained style does that better than a torrent of superlatives or a checklist of platitudes.

Why your notes matter for EE, IA and TOK

Your documentation is a record of pedagogy as much as it is a record of progress. For Extended Essays, it clarifies how the research question developed, which methods were chosen and why, and how ethical or methodological issues were addressed. For Internal Assessments, it helps explain decisions about experimental design, sample selection, or scoring rubrics. For TOK, your notes can show how you probed a student’s understanding of knowledge questions and encouraged perspective-taking.

Clear notes protect both the student and the supervisor: they show what guidance was offered, whether the student followed it, and how you handled problems—without dictating answers or rewriting the student’s thinking.

Five principles for authentic supervisor documentation

• Be specific: Point to what changed, what was suggested, and what the student actually did. Specificity transforms vague praise into useful records.
• Record process, not just outcome: Note decisions, not only results. A sentence about why a student chose a method is more valuable than a sentence about how ‘good’ the result looks.
• Use evidence: Reference drafts, page numbers, figures, or the student’s notes. ‘See draft v2, paragraphs 3–5’ is better than ‘needs work.’
• State your role clearly: Use ‘I suggested,’ ‘I recommended,’ ‘The student implemented,’ or ‘We discussed.’ This keeps boundaries clear and documents collaboration.
• Keep it concise and time-stamped: Short entries that include date and context (meeting, comment thread, email) are easier to interpret later than long, retrospective essays.

If you adopt these principles consistently, readers will see a transparent trail: what the student thought, what you intervened on, and how the project developed.

Concrete language to use (and what to avoid)

Language choice is the fastest route from ‘fake’ to ‘real.’ Here are practical swaps you can make immediately.

• Avoid: ‘Excellent work.’ Use: ‘The literature review now includes three peer-reviewed sources that address the methodological gap discussed in paragraph 2.’
• Avoid: ‘Shows critical thinking.’ Use: ‘The student questioned the sample selection by comparing two datasets and justified excluding data collected with different instrumentation.’
• Avoid: ‘Good structure.’ Use: ‘I recommended moving the methods section before the results to clarify how the data were collected; the student reorganized pages 4–7 accordingly.’
• Avoid: ‘Needs more depth.’ Use: ‘Consider expanding the discussion of limitations to include measurement error and sampling bias; a paragraph linking this to reliability would help.’

Short, action-orientated verbs—’observed,’ ‘recommended,’ ‘clarified,’ ‘adjusted,’ ‘confirmed’—help the reader see what happened and what remains to be done.

Practical templates and sample comments

When in doubt, adopt a tiny template for each entry. A four-part micro-template works well: 1) Context, 2) Observation, 3) Intervention or suggestion, 4) Student response / next step. Keep each entry to one or two sentences.

These examples are intentionally concise—each entry is easy to scan and ties to an artifact (a file, a draft version, a meeting). When you pair this kind of note with an attached draft or a screenshot of comments, it becomes a robust piece of evidence of supervision.

Short sample RPPF-style entry (micro example)

Context: Meeting (virtual) about methods. Observation: Student uncertain about sampling frame. Intervention: Suggested restricting sample to two neighborhoods and piloting instrument with five respondents. Student response: Agreed; completed pilot and uploaded pilot results. Next step: Revise survey and begin data collection.

How to record your thinking without micromanaging

Supervision is coaching more than editing. Documenting thinking should never replace the student’s intellectual work. Here’s how to keep notes supportive, not prescriptive:

• Ask open questions and note them: ‘What made you choose this data source?’ If the student answers, record the essence of their reasoning.
• Offer choices rather than directives: ‘You could X (e.g., narrow the scope) or Y (use a comparative case). If X, you’d need to do A; if Y, B helps.’ Then note which option the student chose.
• Note small wins: ‘Clarified definition of variable’ is fine—tiny progress matters and is easily verifiable.
• Keep the voice distinct: use first person for your actions (‘I recommended…’), and attribute ideas to the student when they propose them (‘Student proposed…’).

Evidence, artifacts and linking notes to assessment

A note by itself is thin; linked evidence makes it durable. Attach or reference the artifact you relied on: draft filenames, email threads, annotated PDFs, time-stamped comments in a shared document, or the student’s reflection entries. Prefer short references: ‘See draft_v3.pdf, comments in paragraph 4’—this tells a reader where to verify your statement.

Make a habit of anchoring notes to assessment language without parroting criteria. Instead of ‘meets criterion X,’ describe the observable behavior the criterion intends: ‘Uses appropriate primary sources and evaluates their limitations.’ That helps anyone interpreting the record to map your note to assessment standards later, even if the rubric’s wording shifts in future cycles.

When to bring in extra support

Some students need subject-specific coaching beyond what a supervisor can offer—complex statistical techniques, advanced lab methods, or help refining a literature search. When outside help is used, document it briefly: who provided the input, what was covered, and how the student integrated it. For example, ‘Referred student for extra statistical tutoring to clarify assumptions about the chosen test; tutor demonstrated a diagnostic approach and student applied it to their dataset.’

If you coordinate such support, note that as well. If students benefit from targeted tutoring, it can complement supervision rather than replace it. For instance, Sparkl‘s personalized tutoring offers 1-on-1 guidance, tailored study plans, expert tutors and AI-driven insights that can help students strengthen methodology or writing skills; when used, record the contribution and whether the student incorporated the guidance.

Handling tricky situations—wording that keeps things professional

Sometimes you must document problems—missing deadlines, possible academic misconduct, or research that risks ethical issues. The key is to record observable facts and actions taken, not to make speculative statements.

• Fact-based: ‘Student did not submit chapter two by the agreed date; we discussed consequences and revised timeline.’
• Investigatory: ‘Similarity observed between student’s paragraph and source X; asked student to provide development notes and drafts; student supplied earlier outline and notes on independent drafting.’
• Escalation: ‘After unresolved concerns regarding methodology and safety, I informed the coordinator and recommended pausing fieldwork pending review.’

These phrases keep the record professional, traceable, and useful if further action is needed.

Tools, workflows and small habits that make documentation painless

Choose a simple, consistent system and stick with it. A few practical tips:

• Use a shared document with comment threads for draft feedback and keep a separate, short log (the reflection log or RPPF-style file) for supervisory notes.
• Date and label files consistently and briefly (‘EEname_draft_v3’, ‘IA_studentname_results’). Short names + version history = clarity.
• Keep meeting summaries to two or three bullets immediately after the meeting—fresh memory makes notes easier and more accurate.
• Attach or reference the artifact you used when making a note (e.g., ‘see annotated draft_v4’).
• Use comments to encourage student reflection: ‘What surprised you most in this section?’ then summarize their reply in your log.

These small habits reduce the temptation to write a long, post-hoc justification and instead build a live, verifiable record.

Quick checklist: dos and don’ts

• Do write short, specific entries that point to an artifact.
• Do use first‑person verbs to show your role.
• Do document the student’s response or next step.
• Don’t rewrite the student’s work—document suggested directions, not final text.
• Don’t use hyperbole or repeated platitudes.
• Don’t speculate about motives; stick to observable facts.

Final thoughts

Authentic supervisor notes are small, honest acts of pedagogy: they show how thinking developed, what guidance was given, and how a student responded. By being specific, evidence-based, time-stamped, and neutral in tone you protect the student’s ownership, make assessment transparent, and create a usable record for any reader who follows the work. Keep entries short, link to artifacts, use precise verbs, and favor questions and options over directives—do that consistently, and your documentation will read like a thoughtful coaching log rather than a string of clichés.

Vrinda Bhandari Member since March 30, 2026

Loading + Follow Following