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

This is what separates an ACS Nano rebuttal from a generic one. ACS Nano reviewers evaluate "originality, technical quality, clarity of presentation, and importance to the field," and at this journal that resolves into two non-negotiable demands: a mechanism the data actually demonstrate, and a nanomaterial characterization package a reviewer can audit from the figures.

The Associate Editor is a working nanoscience researcher, not a professional editor, so the standard is the one they would apply to their own lab's paper. ACS Nano has published its own editorials on what makes a strong report and how authors should engage referees: see "The Best Referee Report" (doi.org/10.1021/nn800067t) and "In Response" (doi.org/10.1021/nn3019046), which frame referees as the expert core of the process.

The PLOS Ten Simple Rules (doi.org/10.1371/journal.pcbi.1005730) formalize the same point-by-point discipline.

The author guidelines are explicit that for new substances "authors are expected to provide firm evidence to establish both the identity and the purity of new substances" using "spectroscopic, crystallographic, chromatographic, electrophoretic, or other analytical methods." For electron microscopy the guidelines ask for "one image showing the distribution of particles being analyzed."

Translated into rebuttal terms: when a reviewer asks for a quantified size distribution, a control, or a chemical-state assignment, that is the journal's published bar talking, not a reviewer being difficult. Conceding and adding the data is almost always the right move.

The practical consequence for your response letter: a rebuttal that argues a mechanism in prose loses, and a rebuttal that shows the mechanism in a new control figure wins. ACS Nano is screening for nanoscale significance with a real functional payoff, so "we believe the mechanism is X" must become "the added control in Figure 4b isolates pathway X." The same logic governs characterization.

A reviewer who flags TEM without quantified size distributions, XRD without peak indexing, or XPS without chemical-state assignment is naming the exact gap that turns a major revision into a reject if you answer it with words instead of data.

Every change you claim must carry a location. In the point-by-point response, follow each action with the page and line number in the revised manuscript, plus the figure or Supporting Information panel where the new data live. Reviewers read the rebuttal before the paper, so a claim they cannot locate reads as a claim that did not happen.

"We added a control" is a promise; "we added the untreated control in Figure 5a, lanes 1 and 2, and report n = 3 at page 13, lines 8 to 15" is verifiable. The single most common reason an ACS Nano rebuttal draws a second major revision is that the reviewer could not confirm a claimed change and assumed the worst.

The Associate Editor and the original reviewers both read your tone. Defensiveness on a characterization or control request signals that you do not understand the journal's bar. Calibrate every response toward the action you took.

The pattern is consistent: replace conviction language with the location of the evidence. Reviewers do not want to be persuaded that you were right; they want to see what you changed.

A strong response letter does not rescue a weak evidence package. At ACS Nano a major revision can still end in rejection, and the rebuttal is not the deciding factor when the underlying gap is structural. Roughly 50 to 60 percent of submissions are declined at the Associate Editor desk screen, and most papers that clear the screen still face a reject or major-revision decision before acceptance.

Among manuscripts that reach revision, the ones that get rejected on the second round are usually the ones where the reviewer asked for a functional demonstration or a missing control and the authors answered with argument instead of new data.

Three situations where the honest move is not a better rebuttal but a different journal. First, if reviewers ask for experiments you cannot run, a polished letter cannot substitute for the data; budget the weeks to generate it or transfer the paper. Second, if the central claim rests on computation or design without experimental validation, no rebuttal closes that gap, and the work likely belongs at a sister venue.

Third, if the nanoscale framing is decorative rather than decisive, ACS Nano reads the work as general materials science wearing a nano label, and the right next step is a materials title such as Advanced Materials or Small. ACS's Manuscript Transfer Service can carry your files and any completed reviews into a better-fit ACS journal, so a reject on revision is often a redirect, not a dead end.

• The point-by-point response quotes every reviewer comment verbatim and answers each one individually in a font or color distinct from the reviewer text.
• Every accepted comment names the new figure, control, or quantified characterization, plus the page and line where the change lives in the revised manuscript.
• Each mechanism question is answered with an added control or measurement, not a paragraph of reasoning.
• The cover letter to the Associate Editor summarizes the changes at a high level and stays separate from the detailed rebuttal.
• You push back on only the rare comment that is genuinely out of scope, and you back the disagreement with a reference rather than conviction.

In our pre-submission review work with ACS Nano submissions, the rebuttals that fail on revision fail in the same few ways. These patterns come from manuscripts we screened before resubmission to ACS Nano and peer nanoscience venues; they are the gaps an Associate Editor and the original reviewers flag first, and you can test your own draft against each one.

Generic acknowledgment with no location. The single most common failure we see in ACS Nano rebuttals is a response that says "we have revised the manuscript accordingly" with no page, line, or figure reference. Because the revised paper goes back to the original reviewers, a claim they cannot locate reads as a claim that was not made.

The fix is mechanical: every accepted comment ends with the figure, the control, or the page and line where the change lives. Manuscripts coming through our pre-submission review pipeline for ACS Nano that adopt strict location-tagging clear revision rounds faster than those that summarize loosely.

Mechanism answered with prose instead of a control experiment. Across our ACS Nano pre-submission reviews, the highest-leverage rebuttal fix is converting a mechanism argument into a control. When a reviewer writes that the mechanism is asserted but not demonstrated, authors often respond with a paragraph of reasoning and a citation.

ACS Nano reviewers are working nanoscience researchers who want the mechanism shown, so the rebuttal that adds an isolating control figure survives and the one that argues does not. Check whether your mechanism response points to a new control panel, not a new sentence.

Characterization gaps answered without the missing data. ACS Nano reviewers consistently flag TEM without quantified size distributions, XRD without peak indexing, and XPS without chemical-state assignment. In our review work, the rebuttals that draw a second major revision are the ones that defend the original characterization rather than adding the quantified figure the reviewer asked for. Make every characterization claim in your response confirmable from the figure alone: a size-distribution histogram with a stated N, an indexed diffraction pattern, an annotated spectrum.

Declining a requested control or replicate. The statistical-analysis and controls comment is where rebuttals quietly lose at ACS Nano. When a reviewer asks for an untreated control, a vehicle control, or a replicate number, declining on scope grounds is read as the evidence package being incomplete. We see this most in biological-application nanoparticle papers. The fix is to add the control and report the replicate count explicitly in the methods and the figure legend rather than arguing it was unnecessary.

Over-pushback that signals scope misunderstanding. A rebuttal that disagrees with more than a small fraction of comments reads, to an Associate Editor, as an author who does not accept the journal's bar. In our pre-submission reviews we flag any response letter where the author pushes back on more than roughly a fifth of comments without strong data behind each disagreement. Concede on characterization and controls; reserve genuine disagreement for the rare comment that is factually out of scope, and back it with a reference rather than conviction.

These five patterns are testable against your own response letter before you upload it. Run an ACS Nano characterization and rebuttal readiness check to see which an ACS Nano reviewer would flag first, or run a broader manuscript and rebuttal scan on the revised paper.

The point-by-point discipline this guide describes is the same discipline documented across the published rebuttal-craft canon. The most widely cited reference is the PLOS Ten Simple Rules for Writing a Response to Reviewers, which formalizes the quote-the-comment, state-the-action, locate-the-change structure. See PLOS Computational Biology, Ten Simple Rules for Writing a Response to Reviewers.

A more recent treatment in Nature Computational Science reaches the same conclusion: a rebuttal that points reviewers to verifiable changes outperforms one that argues. The structure adapts cleanly to ACS Nano because the journal's demand for mechanism and complete characterization maps directly onto the "state the action and point to the evidence" rule.