IB Peer Feedback Technique | How to Use Peer Review to Improve IA & EE Quality

Peer feedback is one of the most underused tools in the IB toolkit. Most students treat it as a formality—swapping drafts five minutes before a deadline, scribbling a few encouraging words, and moving on. But used properly, peer review can sharpen both the work you submit and the way you think about assessment criteria. The short version: giving good feedback is itself a study skill, and it pays dividends on your own IA, EE, and beyond.

Why Does Peer Feedback Actually Help Your Own Work?

The act of evaluating someone else's draft forces you to read an assessment rubric not as a test-taker, but as an examiner. That perspective shift is genuinely difficult to manufacture any other way.

When you read your own writing, your brain fills in gaps automatically—you already know what you meant to say, so you don't notice where the argument breaks down. A classmate's draft has no such shortcuts. Every logical leap that isn't explained on the page registers immediately. Once you've spotted that flaw in someone else's work, you can't un-see it in your own.

There is a second, quieter benefit. Reading a range of approaches to the same IA question or EE topic exposes you to structural decisions you would never have considered in isolation—different ways to frame a research question, organise a methodology section, or situate a conclusion within broader context. That exposure widens your repertoire.

For a deeper look at how IB assessments are structured and where marks tend to cluster, the IB Internal Assessment (IA) の書き方｜高得点を取る型と進め方 and IB Extended Essay (EE) の書き方 guides are worth reading before your first peer session.

What Separates a Useful Comment from a Vague One?

The most common failure in peer feedback is the impressionistic comment: "This section feels a bit unclear" or "Good job, I liked your analysis." Neither remark gives the writer anything actionable to do next.

Useful feedback has three components:

For example, instead of "Your methodology isn't clear," a structured comment might read: "In paragraph three, you describe collecting data 'over several weeks,' but you don't specify the sampling interval or how you controlled for [variable]. According to the methodology criterion in the subject guide, the examiner needs to be able to assess reproducibility—adding a brief procedural table here would address that directly."

Notice what that comment does: it locates the problem precisely, links it to a criterion, and offers a specific remedy. The writer now has a clear next action.

How Should You Structure a Peer Review Session?

A session without structure tends to drift into either uncritical praise or unfocused complaint. A consistent format prevents both.

Before the session: agree on a checklist

IA and EE have different focal points. An IA peer review for Economics will look very different from one for English A—the criteria are distinct, and the conventions of the disciplines diverge sharply. Before each session, spend ten minutes building a shared checklist of three to five specific things to look for, drawn directly from the relevant assessment criteria. This keeps both reviewers focused and prevents feedback from defaulting to surface-level comments about grammar and formatting.

During the session: the two-pass method

First pass — read without annotating. Read the draft straight through as a reader, not an editor. Note your overall impression: Does the argument hold together? Is the research question answered? Where did you lose the thread? Write these down as questions, not corrections.

Second pass — annotate against the checklist. Go back through with the criteria in hand. For each item on your checklist, find the corresponding section in the draft and write a claim–evidence–suggestion comment.

After the session: verbal exchange

A written comment on a page can be misread. After sharing written notes, spend fifteen to twenty minutes talking through the major points. The writer should be able to ask "What did you mean by this?" and the reviewer should be able to explain their reasoning aloud. This verbal exchange also surfaces disagreements that written notes tend to flatten.

How Are Peer Review Priorities Different for IA vs. EE?

IA and EE are different beasts, and conflating them produces feedback that misses the mark for both.

For the EE, it is worth asking your peer reviewer to summarise your argument back to you in two or three sentences without looking at the draft. If their summary doesn't match what you intended, the structure needs work—no amount of sentence-level polishing will fix a structural problem.

For subject-specific IA guidance, the IB Economics HL 完全ガイド｜評価・15マーク問題・IAの書き方 is a useful model for how IA expectations differ from general writing criteria.

How Should You Respond to Feedback You've Received?

Receiving feedback well is its own skill, and it is more cognitively demanding than giving it.

The most productive habit is to write a feedback response log—a short document (it doesn't need to be long) in which you record every substantive comment you received, and then for each one, note either:

• What you changed, and specifically why the change addresses the criterion or improves the argument, or
• Why you chose not to change it, with a reasoned explanation.

This isn't about defending your original draft. It's about making an active decision rather than passively accepting every suggestion or reflexively dismissing them. An examiner evaluates the final product, not the process—but the discipline of explaining your choices forces you to develop the critical judgment that distinguishes a student who understands what they're doing from one who is simply following instructions.

How Do You Keep Peer Feedback Sessions from Wasting Time?

A few common failure modes, and how to avoid them:

Session drift into proofreading. Grammar and spelling matter, but they are the last thing to address, not the first. If your session keeps getting pulled toward surface corrections, put a rule in place: no commenting on language until both reviewers have completed their criteria-based pass.

Feedback without accountability. If there's no follow-up, the feedback loop is incomplete. Agree at the end of each session on a specific date when both parties will share a revised draft—even a section, not necessarily the whole piece. The knowledge that a follow-up is coming creates productive pressure.

Uneven expertise. If you're reviewing a draft in a subject where your peer knows the content far better than you, your feedback on discipline-specific claims will be limited—but your feedback on argument clarity, research question precision, and structural logic remains entirely valid. Be explicit about what you can and can't reliably comment on.

Conflating your stylistic preferences with criteria-based feedback. "I wouldn't have written it this way" is not useful unless you can link the difference to a specific criterion. Peer review is not about imposing your voice on someone else's work.

IB demands a lot of independent judgment, and most of that judgment develops through practice—not just on your own work, but in dialogue with others navigating the same criteria. If you find you want more structured support developing these skills, Quick IB's one-on-one sessions with IB graduates can help you build both the feedback instincts and the subject-specific knowledge to use them well.