Skip to main content
Publishing Strategy12 min readUpdated Jun 6, 2026

PNAS Response to Reviewers: How to Write a Rebuttal That Wins (2026)

A pre-submission and post-decision rebuttal guide for PNAS authors, grounded in pre-submission reviews on PNAS-targeted manuscripts.

Author contextResearch Scientist, Computer Science. Experience with Computer Science Review, Foundations and Trends in Information Retrieval, ACM Computing Surveys.View profile

Readiness scan

Find out if this manuscript is ready to submit.

Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.

Check my manuscriptAnthropic Privacy Partner. Zero-retention manuscript processing.See example reports
Working map

How to use this page well

These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.

Question
What to do
Use this page for
Building a point-by-point response that is easy for reviewers and editors to trust.
Start with
State the reviewer concern clearly, then pair each response with the exact evidence or revision.
Common mistake
Sounding defensive or abstract instead of specific about what changed.
Best next step
Turn the response into a visible checklist or matrix before you finalize the letter.

Quick answer: A winning PNAS response to reviewers opens with a brief note to the handling editor, then answers every reviewer comment point by point. For each resolved comment, reference the exact page and line where the manuscript changed. PNAS returns your revised paper and rebuttal to the original reviewers, so each comment needs a visible action rather than a promise. You have two months to submit the revision before it is treated as a new submission, and multiple rounds are rarely granted. Last reviewed June 6, 2026.

Run the PNAS rebuttal readiness check to flag generic acknowledgments and missing page/line references before you resubmit, or work through this guide manually. For the broader cluster, see the PNAS journal overview.

The page/line rule, up front. The single most-flagged rebuttal mistake at PNAS is writing "we have addressed this concern" without the page and line you must cite for the change. Because the editor returns your reply to the same reviewers, an unverifiable response reads as no change. Reference the exact location for every comment you mark as resolved.

What does a PNAS response to reviewers require?

A PNAS rebuttal is judged on whether the original reviewers can confirm their concerns were resolved. PNAS runs Direct Submission with an editor-led model: a member of the Editorial Board (an NAS member or a Guest Editor they appoint) selects at least two independent reviewers across the relevant disciplines and screens the paper before anyone sees it. When the editor returns a revise decision, your revised manuscript and point-by-point response go back to those same reviewers. That feedback loop is the design constraint that shapes everything below.

How this guide was produced and who it is for. This page is for a PNAS author who just received a revise decision and is drafting the point-by-point reply. We tested its claims against PNAS editorial and reviewer policies (accessed June 6, 2026) and against pre-submission reviews of PNAS-targeted resubmissions. Use this guide before you upload the revision, when the wording of each response still decides whether the original reviewers sign off.

The sources we checked are listed at the foot of the page, and representative recent PNAS papers we cross-checked the report-format conventions against include 10.1073/pnas.2532868123, 10.1073/pnas.2534303123, and 10.1073/pnas.2530977123.

Element
What PNAS expects
What gets flagged
Structure
Point-by-point, each reviewer comment quoted in full
Free-form prose summarizing all comments together
Action language
Specific change plus page and line number
"We have updated the manuscript" with no location
Tone
Neutral, evidence-led, defensive only on substance
Defensive on every minor or stylistic suggestion
Significance Statement
Reworked when reviewers question broad interest
Left untouched after a broad-interest objection
Disagreement
Explained with data or a citation, alternative proposed
Dismissed, deflected, or reframed as a fit dispute
Tracked changes
A clean tracked-changes file accompanies the reply
Revised manuscript with no way to see what moved

Source: PNAS editorial and reviewer policies + Manusights review of PNAS-targeted resubmissions (accessed 2026-06-06).

The PNAS reviewer culture: an editor-led, returned-to-reviewers model

PNAS is not a professional-editor triage journal like Nature, and it is not a biostatistician-gated journal like JAMA. Its defining feature for response-to-reviewers work is the editor-led, returned-to-reviewers model, and that editorial culture shapes what really happens to your rebuttal after you click submit. A member of the Editorial Board owns your paper end to end, chooses the reviewers, and sends your revised manuscript and rebuttal back to those reviewers for a verdict.

Reviews are single-anonymous (single-blind): you do not learn who the reviewers are, but they know who you are and they re-read your paper against your reply.

Two structural facts follow from this. First, the rebuttal is read twice, once by the editor for completeness and once by each reviewer for whether their specific point was met. Write each response to the reviewer who raised it. Second, PNAS sits on a multidisciplinary, broad-interest bar: the 120-word Significance Statement is the triage tool the editor uses to decide whether a non-specialist would care.

When a reviewer says the broad-interest case is not made, that is a substance objection about the paper's reason to be in PNAS, not a cosmetic note. Reworking the Significance Statement and introduction is usually the highest-leverage move in the whole revision.

PNAS also runs a Consultative Review option for dual-classification work that spans two or more major NAS classifications (for example Physical Sciences and Biological Sciences). Papers that draw on adjacent disciplines may be discussed among Editorial Board members in those disciplines, which adds a few days but means your rebuttal can face cross-disciplinary scrutiny. If your paper went through that route, write the response so a reader from the neighboring field can follow why each change matters.

A copyable PNAS rebuttal letter template

Paste this into your response document and replace the bracketed parts. Keep the editor note short, then go comment by comment. Each response names the action and the location.

Dear Editor,

Thank you for the opportunity to revise our manuscript the manuscript title, submitted to
PNAS as a Direct Submission. We are grateful to both reviewers for their
careful reading. We have revised the manuscript to address every comment and
summarize the major changes below:

  1. We reworked the Significance Statement so the broad-interest case is
     explicit (page 1, lines 12 to 25).
  2. We added the requested control experiment (new Figure 3, page 9).
  3. We clarified the statistical analysis and reported effect sizes with
     confidence intervals throughout the Results.

A point-by-point response follows. Reviewer text is in italics; our response
and the corresponding manuscript change are in plain text with page and line
references. A tracked-changes file is included.

----------------------------------------------------------------------

Reviewer 1

Comment 1.1: "The significance to fields beyond the authors' specialty is
not clear from the Significance Statement."

Response: We agree this was underdeveloped. We rewrote the Significance
Statement to explain what changed and why nearby fields should care, in
plain scientific language (page 1, lines 12 to 25). We also revised the
final paragraph of the Introduction to state the cross-field consequence
explicitly (page 3, lines 4 to 11).

Comment 1.2: "An additional control is needed to rule out the alternative
explanation in lines 210 to 218."

Response: We added the suggested control. The new data appear in Figure 3
and are described on page 9, lines 6 to 19. The control confirms the
original interpretation and rules out the alternative the reviewer raised.

----------------------------------------------------------------------

Reviewer 2

Comment 2.1: "The sample size for the second cohort is not justified."

Response: We added a power analysis and the pre-specified sample-size
rationale to the Methods (page 14, lines 1 to 9) and expanded the
statistical analysis accordingly.

Comment 2.2: "I am not convinced the broader claim in the Discussion is
supported."

Response: We respectfully maintain the claim but have softened its scope and
added two supporting citations [refs 24, 25] (page 16, lines 18 to 24). We
explain our reasoning here: [one to three sentences of evidence-based
justification]. If the reviewer still finds this overstated, we are willing
to narrow it further.

We believe the manuscript is substantially stronger and hope it is now
suitable for publication in PNAS.

Sincerely,
[Corresponding author, on behalf of all authors]

Notice the verbs: reworked, added, clarified, revised, expanded, softened. Every resolved comment carries a page and line reference the reviewer can check. The one disagreement (Comment 2.2) is handled with a citation and an offered concession, never a dismissal.

Tone calibration: defensive versus collaborative

The fastest way to lose a PNAS reviewer is a defensive reply to a comment they consider fair. The fastest way to keep them is a reply that treats the comment as a chance to strengthen the paper. Here are real before-and-after rewrites.

Reviewer comment
Bad (defensive)
Better (collaborative)
"Significance to other fields is unclear."
"The significance is clearly stated in the abstract."
"We agree. We rewrote the Significance Statement to make the cross-field consequence explicit (page 1, lines 12 to 25)."
"An additional control is needed."
"This control is not standard in our subfield and is unnecessary."
"We added the control (new Figure 3, page 9). It supports our interpretation and rules out the alternative the reviewer raised."
"The statistical analysis is underspecified."
"The methods follow standard practice and need no change."
"We expanded the statistical analysis, reported effect sizes with confidence intervals, and added the sample-size rationale (page 14)."
"The broader claim seems overstated."
"We disagree; the claim is well supported."
"We narrowed the claim's scope and added two citations [refs 24, 25] (page 16). Here is our reasoning, and we can narrow further if needed."

Source: Manusights tone-calibration analysis of PNAS-targeted resubmissions (accessed 2026-06-06).

The pattern: lead with agreement or partial agreement where you can, name the change, give the location, and reserve disagreement for the rare comment where you have evidence on your side.

The page/line referencing rule, in detail

For every comment you mark as resolved, point the reviewer to the exact place in the revised manuscript: page number and line number, plus the figure, table, or reference number when relevant. Write "page 9, lines 6 to 19" or "new Figure 3," not "we have updated the Results." This is not a formatting nicety.

PNAS returns your reply to the reviewers, who re-read the manuscript against it; a response they cannot locate reads as no change and tends to draw the same comment again on the next round, which you may not get. Number your responses to match the reviewers' numbering, and include a tracked-changes file so the reviewer can see exactly what moved.

Typography: separate the reviewer's words from your reply

Make the reviewer's text and your response visually distinct so the editor and reviewers can scan the document fast. Put each reviewer comment in italics or a shaded text box, and keep your response in plain upright text below it. A common, clean convention is bold for the reviewer's comment label, italic for the quoted comment, and regular weight for the author response.

Do not run the comment and your reply together in one paragraph; the reviewer should be able to find their own words at a glance and read straight down to your action.

When PNAS revision goes wrong: rejection on revision and the appeal trap

A revise decision is not an acceptance, and at PNAS the gap between the two is real. Reviewers re-read the revised paper and can recommend rejection if the response did not satisfy them. The honest failure modes:

  • Rejection on revision. Multiple revision rounds are rarely permitted at PNAS, and acceptance after revision is not guaranteed. A partial first response, where you defer the hard experiment or only half-answer the significance objection, is the most common way a revise turns into a rejection. Treat the first response as your one full attempt.
  • The novelty/general-interest appeal trap. If the paper is rejected, you may appeal in writing within three months.

But PNAS states that appeals on the basis of novelty or general interest are unlikely to be granted, and if an appeal is rejected, the paper may not be resubmitted.

So reframing a substance rejection as a fit argument in your rebuttal usually fails twice: once with the reviewer and again on appeal.

  • The two-month clock. A revised paper submitted more than two months after the revision decision may be treated as a new submission, which can mean new reviewers and a fresh round of broad-interest scrutiny. Most authors who miss the window did so because the response stalled on one disputed comment.

Roughly half of PNAS submissions are declined at initial evaluation before peer review, so reaching a revise decision already puts you in a strong minority. Do not waste it with a thin response.

In our pre-submission review work with PNAS submissions

In our pre-submission review work with PNAS submissions, the responses that turn a revise into an acceptance share a shape, and the ones that stall share the opposite shape. In our review of PNAS-targeted resubmissions, three named rejection patterns generate the most consistent second-round trouble, and we observe each one often enough that they are testable against your own response document before you upload it. PNAS editors consistently flag the same three gaps; the editorial triage pattern below is what our review data surfaces most.

The unverifiable acknowledgment. This is the most common pattern across our PNAS reviews. The author writes "we have addressed this concern" or "we have revised the manuscript accordingly" with no page or line number. Because PNAS returns the rebuttal to the original reviewers, who re-read the paper against it, a response they cannot locate reads as no change. We flag every resolved comment that lacks a page/line reference, a figure number, or a reference number. The fix is mechanical: name the exact location for every action verb.

The untouched Significance Statement after a broad-interest objection. When a PNAS reviewer says the work matters only to a narrow specialist audience, the author too often defends the existing abstract instead of rewriting the 120-word Significance Statement and the cross-field framing in the introduction. At PNAS the broad-interest case is the reason the paper belongs in the journal, so leaving it untouched answers the wrong question.

In our reviews, the highest-leverage single edit on a PNAS revision is usually a rebuilt Significance Statement that states what changed and why nearby fields should care, paired with a matching final paragraph in the introduction.

The half-answered control or statistical analysis. The third pattern is deferring the experiment or analysis the reviewer actually asked for. An author will add a paragraph of discussion, propose a control as future work, or report a p-value without the effect size and sample-size rationale the reviewer requested, then mark the comment resolved.

Because multiple revision rounds are rarely permitted at PNAS, a deferred control or an underspecified statistical analysis is one of the most reliable ways a revise becomes a rejection. We flag any response where the action language ("we discuss," "we note") does not match the reviewer's request ("add the control," "justify the sample size").

The fix is to run the analysis, add the new figure or methods text, and cite its location, or to explain with evidence why it is genuinely out of scope and propose a concrete alternative.

A fourth, quieter pattern shows up on cross-disciplinary papers that went through PNAS Consultative Review: the response answers the home-field reviewer well but leaves the adjacent-field reviewer's comment in jargon they cannot follow. When two or more NAS disciplines are in play, write each response so a reader from the neighboring classification can verify the change. Check whether your PNAS rebuttal answers every comment with a verifiable action.

Beyond the PNAS author guidelines

PNAS author guidelines tell you the mechanics: submit the revision within two months, include a tracked-changes file, respond to every comment. They do not tell you what a PNAS reviewer actually does with your reply, or which of your comments will be re-read most skeptically. Pre-submission reviews of PNAS-targeted resubmissions surface the specific failure patterns, the broad-interest substance trap, and the appeal trap that the official guidance leaves implicit.

The PLOS Ten Simple Rules canon below covers universal rebuttal craft; the sections above map that craft onto the PNAS editor-led, returned-to-reviewers model and its broad-interest bar.

Submit your revision if

  • The response addresses every reviewer comment, point by point, with the reviewer's text quoted.
  • Each resolved comment names the exact page and line (and figure, table, or reference number where relevant).
  • The Significance Statement was reworked if any reviewer questioned the broad-interest case.
  • Every requested control, experiment, or statistical analysis was actually performed, not deferred to discussion.
  • A clean tracked-changes file accompanies the reply, and you are inside the two-month window.

Readiness check

Run the scan to see how your manuscript scores on these criteria.

See score, top issues, and what to fix before you submit.

Check my manuscriptAnthropic Privacy Partner. Zero-retention manuscript processing.See example reports

Think twice if

  • Any response says "we have addressed this" without a page/line reference.
  • You left the 120-word Significance Statement unchanged after a broad-interest objection.
  • The rebuttal pushes back on a control or statistical request without evidence, or reframes a substance objection as a fit argument.
  • The response defers the reviewer's core experiment to "future work" while marking the comment resolved.
  • You are past the two-month revision window, which risks treatment as a new submission.
  • Manusights internal pre-submission review corpus (PNAS-targeted resubmissions)

Frequently asked questions

Open with a short note to the handling editor summarizing the major changes, then respond point by point to each reviewer. Quote each comment, give your response, and name the exact page and line where the manuscript changed. Because PNAS returns your revised manuscript and point-by-point reply to the same reviewers, every comment needs a visible action, not a promise.

Yes. For Direct Submissions, the revised manuscript and point-by-point response are returned to the reviewers so they can confirm their concerns were addressed. Write the rebuttal for the reviewer who raised the comment, not just for the editor. Generic acknowledgments without a specific manuscript change tend to draw the same comment again on the next round.

PNAS asks authors to submit a revised paper within two months of the revision decision, or it may be treated as a new submission. If you need more time, notify the editorial office. Multiple revision rounds are rarely permitted and acceptance after revision is not guaranteed, so the first response should be complete rather than partial.

You can, but only with evidence and a neutral tone. Explain why you disagree, cite data or a citation, and propose an alternative rather than dismissing the comment. Appeals to PNAS on the basis of novelty or general interest are unlikely to be granted, so reframing a substance objection as a fit argument rarely works.

Saying we have addressed this without naming the page and line where the change appears. PNAS reviewers re-read the revised manuscript against your reply, and a response they cannot verify reads as no change. The second most common mistake is a defensive tone on the Significance Statement when reviewers say the broad-interest case is not made.

References

Sources

  1. PNAS editorial and journal policies (accessed 2026-06-06)
  2. PNAS reviewer guidelines (accessed 2026-06-06)
  3. Introducing the PNAS Consultative Review Pilot (accessed 2026-06-06)
  4. Ten simple rules for writing a response to reviewers, PLOS Computational Biology (accessed 2026-06-06)

Final step

Find out if this manuscript is ready to submit.

Run the Free Readiness Scan. See score, top issues, and journal-fit signals before you submit.

Anthropic Privacy Partner. Zero-retention manuscript processing.

Internal navigation

Where to go next

Check my manuscript