Rebuttal Letter: A Complete, Annotated Guide

Let’s be honest: you just received reviewer comments. Maybe they were thorough and constructive. Maybe one reviewer went three paragraphs over on how “fundamentally flawed” your study is. Either way, you have a deadline, and the first thing you need is to see exactly what a good response looks like.

This article gives you a complete, realistic rebuttal letter — not just a template, not just a couple of snippets, but a full letter from cover paragraph to closing statement, with annotations explaining the strategic reasoning behind every decision. You can read this from top to bottom and understand precisely how a professional response-to-reviewers letter should be structured and written.

If you need structural guidance on how to write one, see our guide to responding to peer reviewer comments. If you need a concrete example to model your own letter after, you just found it.

The Scenario

The following is a fictional but realistic example. The manuscript is a hypothetical clinical study, the reviewers’ comments are representative of what you might receive, and the annotations explain why each part of the letter is written the way it is.

You can adapt this framework to your own manuscript — just replace the specifics with your real comments, changes, and journal context.


Complete Rebuttal Letter with Annotations

Below is the full letter. Each section includes an annotation (in italics) explaining the strategic reasoning behind it.


Letter Header

Manuscript ID: JCM-2026-0847
Title: Effects of Continuous Glucose Monitoring on Hypoglycemia Management in Type 2 Diabetes: A Randomized Controlled Trial
Date: 21 November 2026

Dear Dr. Helena Voss, Editor-in-Chief, Journal of Clinical Medicine

Annotation: The header identifies the manuscript unambiguously. Including the manuscript ID, title, date, and editor name (when known) saves the editor time — they can confirm they’re looking at the right resubmission in seconds. This is the first thing your letter will be judged on: does it respect the editor’s workflow?


Cover Paragraph

Dear Dr. Voss,

Thank you for the opportunity to revise our manuscript (JCM-2026-0847). We are grateful to both reviewers for their careful and constructive feedback, which has substantially strengthened the paper. We have addressed every comment below, with manuscript changes shown in tracked changes and referenced by page and line. Our point-by-point responses follow.

A clean copy and a tracked-changes version of the revised manuscript are both included in this submission. We have also added the requested GRADE assessment as a new Supplementary Table S3.

Annotation: This cover paragraph does three jobs simultaneously. First, it opens with gratitude — not flattery, but genuine acknowledgment. Second, it gives a high-level summary of what changed (page-line reference system, tracked-changes version, new supplementary table). Editors skim this section in about 10 seconds; the point is to confirm that you followed the process correctly. Third, it flags new material not directly requested by reviewers (the GRADE table) so nothing looks like an unexplained addition. This transparency is one of the green flags editors look for.


Reviewer 1 — Comments and Responses

Reviewer 1, Comment 1: “The sample size was calculated using a two-sample t-test, but the outcome is binary (hypogloglycemic event vs. no event). This is a methodological error. Please recalculate using the appropriate formula for proportions.”

Annotation: Note that this comment targets your methodology directly. The reviewer is correct: a two-sample t-test is inappropriate for a binary outcome. This is an “easy fix” — you agree, you can fix it quickly, and it shows good faith.

Response: We thank the reviewer for catching this. You are correct that a two-sample t-test is inappropriate for a binary outcome. We have recalculated the sample size using the formula for comparing two proportions (Casagrande, Pike, and Thomas, 1978) with a significance level of α = 0.05 and 80% power, assuming a control-group event rate of 35% and a detectable relative risk reduction of 20%. The revised calculation yields a required sample size of n = 248 (124 per group), and we have updated the Methods section accordingly (page 8, lines 14-22).

Annotation: The response opens with acknowledgment and agreement, describes the exact change made, cites the specific formula used, and provides the precise location in the revised manuscript. Every element of this response is verifiable. The editor can open the tracked-changes document, go to page 8, lines 14-22, and see the revision immediately. No ambiguity, no hand-waving.

Reviewer 1, Comment 2: “The discussion of subgroup effects (Figure 3) is overstated. The interaction p-value is 0.18, which is not statistically significant, yet the text presents subgroup differences as if they were findings.”

Annotation: This comment asks you to tone down an interpretation. It’s a valid concern — overinterpreting non-significant interactions is a common reviewer concern. The correct response: agree, tone down the language, and show where.

Response: We agree that the subgroup analysis should not be presented as a primary finding. We have revised the Discussion section (page 14, lines 5-19) to reframe the subgroup observations as exploratory and explicitly note the non-significant interaction (p = 0.18). The revised text now reads: “Exploratory subgroup analyses suggested a larger effect in patients aged ≥65 years compared with younger patients, although this interaction was not statistically significant (p = 0.18) and should be interpreted with caution.”

Annotation: The response is brief and decisive. It agrees with the reviewer, describes the revision, and even quotes the new text so the reviewer can see exactly how the tone changed. Providing the revised text in the response is optional but highly effective — it lets the reviewer verify the fix without opening the manuscript.

Reviewer 1, Comment 3: “Please include a flow diagram (CONSORT) showing participant allocation and attrition.”

Annotation: Another easy fix — a figure that should have been included anyway. The reviewer is right.

Response: Thank you for this suggestion. A CONSORT flow diagram has been added as Figure 4, showing participant enrollment, allocation, follow-up, and analysis groups.

Annotation: Even for a straightforward request, you still need to acknowledge and respond. A one-line response is perfectly acceptable here. The key is to confirm the action was taken and, if possible, provide the location (Figure 4 in the revision).


Reviewer 2 — Comments and Responses

Reviewer 2, Comment 1: “The statistical analysis section does not mention how missing data were handled. Multiple imputation is preferred over complete-case analysis for longitudinal studies with attrition.”

Annotation: This is a substantive methodological request. You may or may not agree with the suggestion to use multiple imputation — it depends on your data. In this example, let’s say the original analysis used complete-case analysis and the attrition rate was low (5%), so you could justify keeping it, but you should still respond thoughtfully.

Response: We appreciate the reviewer’s attention to this important point. Our attrition rate was 5.2% (n = 14 of 270), which falls within the range where complete-case analysis is generally considered acceptable (Morton et al., 2021). However, we ran a sensitivity analysis using multiple imputation (10 imputations, 15 predictors) and found that the results were robust to this approach: the point estimate changed by less than 3% and the confidence intervals were virtually identical. We have added this sensitivity analysis to the Methods section (page 10, lines 8-25) and reported the results in Supplementary Table S2. We have retained the complete-case analysis as the primary approach but now document both methods, which strengthens the credibility of our findings.

Annotation: This is where the response letter earns its keep. The reviewer asked for multiple imputation. The authors chose not to fully comply but did the following: acknowledged the concern, explained why their original approach was justified (low attrition rate, cited literature), ran the suggested analysis anyway as a sensitivity check, reported the results, and documented both methods. This is a model of evidence-based engagement. It shows the editor: “We took this seriously. We tested it. The results support our original approach. Here’s the proof.” If you simply said “we used complete-case analysis and that’s sufficient,” the reviewer would push back. By running the sensitivity analysis and reporting it, you demonstrate engagement without unnecessary defensiveness.

Reviewer 2, Comment 2: “The abstract states that ‘CGM reduced hypoglycemic events by 45%.’ This relative-risk reduction overstates the clinical effect. The absolute risk reduction is only 4.2 percentage points.”

Annotation: The reviewer is pointing out a reporting issue — using relative risk reduction without absolute numbers is a common problem in clinical papers. This is a real editorial issue. The correct move: concede, revise, and explain.

Response: We agree that the abstract should report the absolute risk reduction alongside the relative effect. We have revised the abstract (page 1, lines 18-21) to read: “Continuous glucose monitoring reduced hypoglycemic events by 45% relative to control (absolute risk reduction: 4.2 percentage points; 95% CI 1.1 to 7.3; p = 0.007).”

Annotation: Acknowledge the point, quote the exact revised text, and cite the location. This is exactly how to handle a reporting-quality concern. The reviewer gets confirmation their point was taken seriously, the editor gets a properly reported effect size, and your credibility goes up because you responded in good faith.

Reviewer 2, Comment 3: “The authors cite Smith et al. (2018) as evidence supporting their intervention. This paper was retracted in 2021. The reference should be replaced.”

Annotation: This is the “you cited a retracted paper” scenario. It’s potentially embarrassing but entirely fixable. The response should: acknowledge the error directly, show you’ve already corrected it, and avoid making excuses.

Response: We thank the reviewer for this critical observation. You are correct that Smith et al. (2018) was retracted. We have replaced this reference with Chen and Okafor (2022), which addresses the same clinical question using a similar design. The revised reference list and the corresponding text (page 3, line 12) now cite the correct source. We appreciate the reviewer’s vigilance — this was an oversight on our part and should not have appeared in the submitted manuscript.

Annotation: This response does three things well. First, it doesn’t defend or explain — it accepts the error. Second, it shows the fix was already made (replaced reference, specific location). Third, it acknowledges the reviewer’s contribution (“your vigilance”) without being overly deferential. This is how you turn a potentially career-damaging mistake into a demonstration of thoroughness. Never get defensive about a retracted reference.

Reviewer 2, Comment 4: “Table 2 lists ‘compliance rate’ as a secondary outcome but provides no definition or measurement method. Please clarify.”

Annotation: This is the “you forgot to define something” scenario. The reviewer caught an omission. The correct response: acknowledge, define, and point.

Response: We apologize for this omission. Compliance was defined as the percentage of days within the intervention period during which the patient wore the CGM device (≥20 hours/day recorded) as measured by device logging software. This definition has been added to Table 2 (page 9, lines 1-3) and the Methods section (page 7, lines 30-33).

Annotation: Brief, precise, and corrective. The reviewer asked for a definition. You provided it, quoted the new text, and cited the location. No padding, no explanation of why it was forgotten.

Reviewer 2, Comment 5: “The study was conducted at 12 sites across three countries, yet the Methods section describes only recruitment from the US sites. The non-US recruitment sites and their IRB approvals should be documented.”

Annotation: This comment is genuinely fair — the Methods section should describe all recruitment sites. But it also asks for work that hasn’t been done yet. You can’t go back and collect historical IRB documentation from sites you enrolled months ago. Here’s how to handle it:

Response: We agree that the Methods section should document the non-US recruitment sites. We have added a paragraph (page 6, lines 12-24) describing the three non-US sites (University Hospital Tübingen, Germany; Johns Hopkins Singapore; and Royal Adelaide Hospital, Australia) and noting that IRB approvals from each site are available in Supplementary File S1. We also added a table (Supplementary Table S1) listing each site, its IRB approval number, and the approval date.

Annotation: This is the “you can do this quickly but it requires effort” response. You didn’t refuse. You didn’t over-promise. You identified what could be added (site descriptions, IRB documentation) and committed to it in a way that’s feasible within the revision deadline. This is the right level of engagement.


Closing Statement

We thank the editor and both reviewers for their time and for feedback that has significantly improved the quality of this manuscript. We hope the revised paper is now suitable for publication in the Journal of Clinical Medicine.

Annotation: Short, professional, forward-looking. No new arguments. No defensiveness. A polite confirmation that you’re ready for the next step. This is the last thing the editor sees before filing your paper — make it count by being gracious and ready to move forward.


Sincerely,

Dr. James Whitfield, on behalf of all authors


What This Example Demonstrates

The letter above includes eight reviewer comments across two reviewers and three types of responses. Here’s what each type teaches:

1. Agree and fix (Comments 1, 2, 3, and 2.2)

Pattern: Thank → Agree → Describe change → Cite location. This is your default response type. It signals that you take feedback seriously and are easy to work with.

2. Evidence-based engagement (Comment 2.1)

Pattern: Thank → Explain original rationale → Run suggested analysis → Report results → Document both approaches. Use this when you partially agree but the exact request isn’t feasible or necessary. The key is doing the analysis, not just explaining why you didn’t.

3. Accept error and correct (Comment 2.4)

Pattern: Thank → Accept → Show fix → Cite location. Never get defensive about a mistake. Fix it fast, show you fixed it, and move on.

4. Define and clarify (Comment 2.5)

Pattern: Apologize for omission → Provide definition → Cite location. When you forgot something, own it and supply the missing detail without making excuses.

5. Feasible effort commitment (Comment 2.6)

Pattern: Agree → Identify feasible fix → Commit to action. When a reviewer asks for something you haven’t done yet, determine what you can do within the deadline and commit to it. Don’t refuse — find the middle ground.


Weak vs. Strong Response Comparison

To see exactly how tone and specificity determine whether a response succeeds or fails, compare these two responses to the same reviewer comment:

Reviewer comment: “The authors claim their intervention reduced dropout rates, but no statistical test is reported to support this claim.”

Weak response: “We have addressed this concern in the revised manuscript. The dropout rate was lower in the intervention group, and we believe this supports our claim.”

Why this fails: It restates the original claim instead of answering the question, names no statistical test, gives no page or line number, and leaves the reviewer nothing to verify.

Strong response: “We agree a formal test was missing. We have added a chi-square test comparing dropout rates between the intervention and control groups (χ² = 6.42, p = 0.011), reported in the Results (p. 8, lines 172–176) and referenced in the Abstract. We have also added the exact dropout counts by group to Table 2, so the comparison can be verified directly.”

Why this works: It agrees explicitly, names the actual test and result, cites a precise manuscript location, and gives the reviewer a concrete way to check. This is the pattern that every comment in the example letter above follows.


Key Rules That Apply to Every Comment

Every response in the example letter follows these five rules:

  1. Quote the comment verbatim before responding. Never paraphrase or summarize — it should be clear that you engaged with what was actually written.
  2. State your disposition immediately. Whether you agree, partially agree, or respectfully decline, make it clear in the first sentence.
  3. Describe exactly what you changed. Never say “we revised the text” without specifying what the revision was.
  4. Cite a precise location. Page number, line number, section heading, or table name. “We clarified this in the Methods” is not a response — it’s a void.
  5. Keep tone professional, even when the reviewer was unfair. This letter is for the editor as much as for the reviewer. The editor is evaluating whether you’re a reasonable collaborator, not whether you’re emotionally resilient.

A professional rebuttal letter follows a simple pattern: thank the editor and reviewers, list every reviewer comment verbatim, respond to each one with agreement or evidence-based engagement, cite exactly where each change appears in the revised manuscript, and close politely. The example letter above shows this process in action across five response types.


Need help crafting your response to peer reviewers? Get expert assistance on our Order page — our writers specialize in response-to-reviewers letters, manuscript revisions, and resubmission packages.