Case Study 2 — The Response Letter That Saved the Paper

A composite, fictional-but-realistic scenario continuing Dr. Lena Foss's paper through peer review. The reviewer comments and Lena's responses are invented but typical; this is a Deep Dive into the single document that most often decides whether a "major revision" becomes an acceptance.

The situation

Three months after submitting, Lena gets the email. The decision: major revision. Her stomach drops — her first read is "they hated it." Then her advisor reframes it in one sentence: "Major revision means they'll publish it if you fix what they raised. This is good news wearing a frown. Now — the response letter matters as much as the revisions. Let's write it well."

There are three reviewers and eleven total comments. Two comments will require new experiments. One reviewer is sharp to the point of stinging. Lena's job is to write a response to reviewers that addresses every comment, concedes what's right, defends what's defensible — and never once sounds wounded or dismissive. The editor and all three reviewers will read it.

We'll follow three of the eleven comments, because they cover the three situations every response letter contains: a comment you should concede, a comment you disagree with, and a comment you can't fully satisfy.

Comment A — the one to concede

Reviewer 1: "The Methods section does not specify the temperature at which cycling was performed. Since SEI growth is strongly temperature-dependent, this omission makes the results difficult to interpret or replicate."

The reviewer is simply right. Lena left out a critical parameter. There is nothing to defend here, and trying to would be absurd. The move is to concede fully, fix it, and say exactly what changed.

✅ Lena's response: "We thank the reviewer for catching this important omission. The reviewer is correct that cycling temperature is essential for interpreting and reproducing SEI results. All cycling was performed at 25 ± 1 °C; we have added this to the Methods (Section 2.3, para. 1) along with the temperature control method, and we have noted the temperature in the caption of Figure 4. We apologize for the oversight."

Why it works: It thanks the reviewer, agrees explicitly, states precisely what was added and where (so the reviewer can verify in seconds without hunting), and moves on. No defensiveness, no excuses. A conceded point handled this cleanly turns the reviewer into an ally — they see their input directly improved the paper, which is exactly what a reviewer wants.

Comment B — the one to disagree with

Reviewer 3: "The authors should compare their additive against [Additive X], which is the current state of the art. Without this comparison, the contribution cannot be assessed."

Here Lena genuinely disagrees — but she has to disagree carefully, because the reviewer has a fair underlying concern (how does this stack up against the best alternative?) even if the specific demand is off. As it happens, Additive X targets a different failure mode and isn't a valid head-to-head comparison. The defensive instinct is "the reviewer doesn't understand the field." The wise move is to clarify, with evidence, while honoring the legitimate concern beneath the request.

❌ What Lena wanted to write (defensive): "The reviewer is mistaken. Additive X addresses cathode degradation, not SEI growth, so comparing against it makes no sense. This is a basic distinction."

✅ What Lena actually wrote (firm, with evidence, no attitude): "We appreciate the reviewer's emphasis on situating our additive against the state of the art. We did not include a direct comparison with [Additive X] because it targets cathode-side degradation rather than anode SEI growth [ref], so the two are not directly comparable on the capacity-retention metric we report. To address the underlying concern, we have (1) added a paragraph to the Discussion (Section 4, para. 2) clarifying which failure mode our additive addresses and how that differs from cathode-focused additives like [Additive X], and (2) added a comparison against [Additive Y], an SEI-targeting additive that is a valid benchmark, showing our additive achieves comparable suppression with lower conductivity loss (new Table 2). We hope this situates the contribution as the reviewer intended; if a direct [Additive X] comparison is still desired, we are glad to discuss how best to frame it given the different failure modes."

Why it works: It never says "you're mistaken." It honors the legitimate concern (situate the work against the best alternative) while correcting the specific request (X isn't a valid comparison) — with a citation, not an assertion of authority. Crucially, it doesn't just say no; it gives the reviewer something better: the comparison they actually wanted (against a valid benchmark, Additive Y). And it ends with an open door rather than a closed one. The reviewer's concern is fully met; the invalid demand is declined gracefully and replaced with something stronger. That's how you disagree and still get accepted.

Comment C — the one you can't fully satisfy

Reviewer 2: "The authors should demonstrate that the effect holds in full-size commercial cells, not just coin cells, before claiming practical relevance."

This is a reasonable request that Lena genuinely cannot fulfill — her lab has no access to commercial-cell manufacturing, and that scale-up is a multi-year project in itself. She can't do it. The fatal mistakes would be to ignore the comment, or to wave it off as "out of scope." The honest move is to acknowledge the request's validity, explain the real constraint, and offer what she can.

✅ Lena's response: "The reviewer raises a fair and important point: coin-cell results do not guarantee equivalent behavior in commercial-format cells, and practical relevance ultimately requires that demonstration. Full-format cell fabrication is beyond the capabilities of our laboratory and represents a substantial scale-up effort in its own right, so we are not able to include it here. To represent this honestly, we have (1) softened our claims of practical relevance throughout, now framing the work as establishing the mechanism in coin cells rather than demonstrating commercial readiness (Abstract; Discussion, Section 4, para. 5), and (2) added an explicit limitation stating that scale-up to commercial formats remains necessary future work and is required before practical claims can be made (Section 4, para. 6). We agree this is the essential next step."

Why it works: It validates the concern, explains the constraint as a real limit (not an excuse), and — instead of silently dropping the issue — adjusts the paper's claims to match what the evidence supports and adds the limitation explicitly. Lena gave the next-best thing to the experiment she couldn't run: intellectual honesty about exactly what her work does and doesn't show. Editors are reasonable about genuine constraints when you're transparent; they turn hostile only at evasion.

The outcome

The revised paper went back with the eleven-point response letter. Two reviewers recommended accept; the third, who'd been sharpest, wrote: "The authors have addressed my concerns thoroughly and the paper is substantially improved." Accepted with minor revisions. The science was unchanged from three months earlier. What changed: Lena did the genuine work the valid comments required, and wrote a response that made every reviewer feel heard.

The takeaways

1. Address every comment — concede, disagree, or honestly decline, but never ignore. A single skipped comment reads as evasive to the person deciding your fate.
2. Concede what's right, gladly and specifically (Comment A). State exactly what changed and where. A cleanly conceded point makes a reviewer an ally.
3. Disagree with evidence and an alternative, never with attitude (Comment B). Honor the legitimate concern beneath an off-target request, correct the specifics with a citation, and offer something better.
4. When you can't satisfy a request, be transparent and adjust your claims (Comment C). Explain the real constraint, soften any claim the missing evidence can't support, and add the limitation explicitly. Honesty beats evasion every time.
5. The response letter is persuasive technical writing. Treat it with the care you gave the paper — it can save a paper the reviews seemed to doom.

One sentence to remember: The reviewer who criticized your paper is about to decide its fate — write the response that makes them want to say yes, by being right about the science and gracious about the criticism.