Responding to Reviewer 2: The FW_REBUTTAL Workflow

JIAPS R2 came back with 18 reviewer comments. Reviewer 2 alone had 11. I classified every comment in 30 minutes, drafted responses in 3 hours, audited tone for 2 more. The submission went through R3 without further major revision.

The workflow wasn't faster because the reviewers were easy. It was faster because classification happened before drafting — not during it.

The Problem With Reacting in Real Time

The instinct is to read each comment and start writing the response. This produces two failure modes.

Defensive capitulation: you're in the emotional phase of receiving criticism, so you give too much ground on points where your original design was correct. You promise revisions you didn't need to make.

Defensive refusal: same emotional state, different direction. You dig in on weaknesses that deserve acknowledgment. You miss the ones where the reviewer is right.

Both failures share the same root: you're deciding how to respond in the same moment you're writing the response. Classification breaks that link.

The Three Classification Categories

Before writing a single response sentence, label every comment:

A — Revise. The reviewer identified a real gap, error, or insufficiency. You're making the requested change or an equivalent improvement.

B — Push back. The reviewer's concern reflects a misreading of your design, a claim your data directly address, or a standard that doesn't apply to your study type. You're arguing, with evidence.

C — Clarify. The reviewer isn't wrong, but the confusion comes from unclear presentation rather than a substantive flaw. You're improving the text without changing the underlying analysis.

JIAPS R2 split as: 8A, 6B, 4C. That ratio mattered — more B than I expected, because several comments read as critiques but were actually based on misreading the Methods section. Without classification, I would have revised what didn't need revising.

Per-Category Response Structure

For A: Acknowledge the concern specifically (not generically). Describe exactly what changed. Cite the manuscript location with line numbers or section heading. Don't over-thank. "The reviewer correctly identifies..." is fine. "We are deeply grateful for this insightful observation..." is not — it's padding that makes subsequent B responses read as defensive by contrast.

For B: Acknowledge the reviewer's concern as a legitimate question before answering it. Then answer it — with citations if the question is empirical, with methodological reasoning if it's a design question. Never imply the reviewer was wrong to ask. They weren't wrong to ask; they're wrong about the answer. That distinction determines whether the response lands.

For C: State what caused the confusion (usually a missing sentence or ambiguous framing). Quote the revised text that addresses it. Cite the location. Keep it brief.

For detailed point-by-point response structure, the per-comment formatting matters too — numbering that mirrors the original review, consistent headers, and response length proportional to comment complexity.

Tone Audit

After drafting all responses, before submitting, read the letter once specifically for tone. The failure mode isn't rudeness — it's something subtler: varying register across categories.

Researchers often sound warmer in A responses (grateful for a correction they agree with) and cooler in B responses (defending a position they feel was unfairly challenged). This tone shift signals to editors which comments you're comfortable with. A reviewer receiving the rebuttal can read it too.

Target: identical register across all three categories. Professional, specific, evidence-grounded. Read your B responses last, as if you were the reviewer receiving them. If any read as dismissive, revise before submitting.

The Revision Cover Letter

The letter accompanying your resubmission is not where to summarize every change you made. The editor has the point-by-point document and the tracked manuscript. They don't need another summary.

What the revision cover letter needs: 2–3 major changes you made, one sentence on how the revision strengthens the core argument, and word count if the journal tracks it. 150–200 words. That's it. Longer signals that you're anxious about the resubmission.

The sequence matters before you get to this stage. Journal selection shapes who reviews you and how hard the revision stage will be — a reviewer mismatch between your study type and the journal's dominant methodology is one of the most common R2 problems that can't be fixed in the rebuttal.

The Rebuttal Letter Framework ($7) at researchcraft.gumroad.com has the A/B/C classification template, per-category response structures, tone audit rubric, and the revision cover letter template — language templates for every reviewer scenario, including the ones where the reviewer is wrong but you still have to respond carefully.