How to Use Teacher Feedback in IB | 3 Steps to Turn Comments into Scores
Getting feedback from your teacher is only half the battle—what you do with those comments determines whether your next submission actually improves. Here's a practical system to make every piece of feedback count.
Teacher feedback in the IB Diploma is one of the most underused score-improvement tools available to you. Most students read a comment, feel briefly motivated or deflated, and then file it away. The students who consistently move up through the grade boundaries do something different: they treat feedback as structured data and work it systematically.
The short answer is this — sort feedback by criterion, log every comment in a three-column table, run a diff check after each revision, and diagnose recurring patterns before they become permanent habits. Done consistently, this process converts passive reading into active score recovery.
Why Does Most Feedback Go to Waste?
The honest reason is format mismatch. Teacher comments arrive as prose scattered across a document or a rubric sheet, but your brain needs a decision tree: what exactly is wrong, where does it sit in the assessment criteria, and what do I do next?
Without that structure, feedback triggers one of three dead ends:
- Cosmetic editing — you fix the sentence the teacher underlined but miss the conceptual issue underneath
- Selective reading — you focus on comments that feel manageable and avoid the ones that require real rethinking
- Memory decay — you act on the feedback once, then forget the pattern by the time the next assignment arrives
The three-step system below is designed to close all three gaps.
Step 1: How Do You Sort Feedback So It Actually Tells You Something?
Before you read a single comment in detail, do one thing: map every piece of feedback to an assessment criterion.
Every IB assessment component — whether it's an Internal Assessment (IA), an Extended Essay (EE), or a TOK essay — is marked against a published set of criteria. Open the relevant subject guide and list those criteria as column headers. Then, for each teacher comment, assign it to the criterion it most directly affects.
This immediately does two things:
- It shows you which criteria are generating the most comments — those are your priority revision targets.
- It exposes comments that feel vague in isolation but become precise once tied to a criterion descriptor.
What if a comment seems to touch multiple criteria?
Assign it to the criterion that, if addressed, would produce the biggest mark improvement. When in doubt, ask your teacher directly: "Is this comment primarily about [Criterion X] or [Criterion Y]?" That question alone signals to your teacher that you're engaging seriously, and the answer gives you an exact target.
Step 2: How Do You Turn a Comment into a Concrete Next Step?
Once feedback is sorted by criterion, build a three-column feedback log. This is the core tool of the whole system.
| What was pointed out | Why it matters (criterion link) | How I will fix it |
|---|---|---|
| "Your analysis here is descriptive rather than evaluative." | Criterion relevant to evaluation/analysis — currently not reaching the upper band descriptor | Add a clear claim, support it with evidence, then explicitly assess its significance or limitation |
| "Sources are not consistently cited in the correct format." | Criterion relevant to academic integrity / formal presentation | Review the required citation style in the subject guide; apply it uniformly across all references |
| "The research question is too broad to investigate meaningfully." | Criterion relevant to focus and scope | Narrow the variable or context; model it against a sample RQ from your teacher or the guide |
The third column is the most important one, and it's the column most students skip. A log without the "how I will fix it" column is just a complaint list. The fix column forces you to think in terms of specific actions, not general intentions.
Keep this log in a shared document you can return to across assignments. Over time, it becomes a personal diagnostic history of your academic writing.
Step 3: How Do You Know Whether Your Revision Actually Worked?
Revision without verification is hope, not improvement. After you make changes, run what programmers call a diff check — a deliberate comparison of your revision against the original feedback.
The process is simple:
- Pull up your feedback log and the original teacher comments side by side with your revised draft.
- For each item in the log, ask: Does the revised version directly address the specific issue that was flagged?
- Mark each item as resolved, partially addressed, or still open.
This step catches the most common revision error: fixing the surface while leaving the underlying problem intact. For example, if a teacher noted that your argument "lacks critical engagement," adding two more sentences of description does not resolve the issue — the diff check will make that visible.
What Should You Do When the Same Feedback Keeps Appearing?
Recurring feedback is a diagnostic signal, not just a nuisance. When you see the same comment appear across two or more assignments, you need to distinguish between two root causes:
Conceptual gap — you don't fully understand what the criterion is asking for. The solution is not more effort on the same approach; it's a targeted conversation with your teacher, or a close re-read of the criterion descriptor with examples.
Execution gap — you understand the concept but consistently fail to apply it under the pressure of real writing. The solution is deliberate practice: write short, focused practice paragraphs targeting that single criterion and ask for quick feedback before it compounds across a full draft.
| Type of recurring feedback | Likely cause | Targeted fix |
|---|---|---|
| "Your evaluation doesn't go deep enough" | Conceptual — unsure what "evaluation" means at the required level | Ask teacher for a model example at the upper band; annotate what makes it evaluative |
| "You keep switching tense inconsistently" | Execution — habit under pressure | Write a checklist item; do a dedicated tense pass as a final editing step |
| "The structure doesn't follow a logical progression" | Could be either — diagnose first | Map your argument structure visually before writing; show the map to your teacher |
If conceptual gaps are involved, the most efficient move is a targeted follow-up question — not "what should I do?" but something precise: "In the criterion descriptor, it says a top-band response should do X. In my draft, I tried to do X by doing Y. Where does my version fall short of that descriptor?" That question gives your teacher a concrete reference point and produces a much more useful answer.
How Does a Feedback Log Carry Value Across the Whole IB Programme?
This is where the system compounds. A well-maintained feedback log is not assignment-specific — it becomes a cross-component learning asset.
Patterns in your IA feedback almost always predict weaknesses in your EE. Vocabulary issues flagged in a TOK essay often surface in English A assessments. Analytical depth comments in one subject frequently reflect a writing habit that affects every subject.
By keeping one log that tracks feedback across all your components, you can:
- Spot cross-subject patterns that no single teacher would see
- Carry forward resolved issues as a checklist for new drafts
- Walk into supervisor or teacher meetings with specific questions rather than vague anxiety
For IAs specifically, your feedback log from early drafts is essentially a free revision guide provided by someone who has read the subject guide carefully. Treat it as such.
If you are managing the time pressure of running IAs, an EE, and exam preparation simultaneously, a structured feedback loop also helps you triage: you can see clearly which criterion gaps are costing you the most and direct your limited revision time accordingly. A reliable system for this kind of prioritisation is one of the central themes in the IB time management guide.
A Note on Getting Better Feedback in the First Place
The quality of your feedback log depends on the quality of the feedback you receive. You can influence that.
When you submit a draft, include a short note to your teacher: "I'm most uncertain about [Criterion X]. Could you give specific feedback on whether my approach meets the upper-band descriptor?" Teachers working with forty students have limited time; a targeted prompt helps them focus their comments on what you actually need.
This is also worth remembering: your teacher's feedback reflects their professional reading of your work against an assessment framework they know well. Even a brief, apparently casual comment often carries precise meaning when read against the criterion it relates to. The mapping step in Step 1 is what unlocks that precision.
Working through this system on your own is entirely possible. If you find yourself hitting a wall — particularly on recurring conceptual gaps — having an IB-experienced tutor walk through your feedback log with you can compress the diagnostic process significantly. At Quick IB, our tutors have been through the programme themselves and can help you interpret feedback precisely and build revision strategies that target the right criteria.