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

Brain Response to Reviewers: How to Write a Rebuttal That Holds Up (2026)

A point-by-point rebuttal guide for authors revising for Brain (Oxford University Press), grounded in pre-submission reviews on Brain-targeted manuscripts.

Author contextResearch Scientist, Neuroscience & Cell Biology. Experience with Neuron, PNAS, eLife.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 Brain response to reviewers wins by answering each referee comment one at a time, quoting the comment, stating exactly what changed, and citing the page and line where the change lives. Because Brain's editors and associate editors are research-active translational neuroscientists, referees test two things together: a real disease mechanism and real clinical relevance. The highest-leverage replies strengthen the cohort or sample, harden the statistics, and make the mechanism-to-disease link explicit.

Revision gives no guarantee of acceptance at Brain, so treat the rebuttal as the second half of the paper, not paperwork.

Need a structured check before you resubmit? Run a Brain rebuttal readiness check on your revised manuscript and response letter, or work through this guide by hand. For the wider cluster, start with the Brain journal overview.

How should you structure a Brain response to reviewers?

Brain handles revisions through Manuscript Central at ScholarOne submission portal, where you click "create a revision" against the decision. Open with a short paragraph to the Editor that thanks the referees and summarizes the major changes in two or three sentences.

Then go point by point: quote each referee comment in full, give your response directly beneath it, and end every response with the specific manuscript change and a page and line reference so the referee can verify it without hunting. The single most common rebuttal mistake, across every journal, is writing "we have addressed this" without telling the reviewer where to look.

At Brain that is doubly costly because the response goes into a paste field the referees read line by line, so a vague answer is visibly vague.

This guide was produced and reviewed by a research scientist working in neuroscience and cell biology, and it exists to help authors before submitting a revision to Brain, not to summarize the journal's public pages. The sources used are listed at the end; the editorial patterns below come from how we review Brain-targeted manuscripts.

A practical rule for the referee-vs-author distinction: set the reviewer's quoted text apart visually so it never blurs into your reply. The cleanest convention is to put the reviewer comment in bold or italic (or an indented block), then write your response in normal upright text. Brain's submission system lets you paste formatted text, so use that formatting to make the document scannable. A response where reviewer text and author text run together in one font is the version referees complain about most.

The structure below is the one that holds up at Brain. It is built to be copied, then filled in with your manuscript's specifics.

Dear Editor,

Thank you for the opportunity to revise manuscript [BRAIN-XXXXX] for Brain.
We are grateful to both referees for their careful reading. In response we
have strengthened the cohort, expanded the statistical analysis, and made the
disease-mechanism link explicit throughout. A point-by-point response follows;
all line numbers refer to the revised manuscript with changes tracked.

------------------------------------------------------------
Reviewer 1
------------------------------------------------------------

Comment 1: "The sample size is not justified and the study may be underpowered."

Response: We agree. We have added an a priori sample-size calculation (Methods,
page 7, lines 142 to 156) showing the cohort is powered to detect the primary
effect. We also report the test statistic, degrees of freedom, and exact P
value for each comparison, with 95% confidence intervals (Results, page 11,
lines 233 to 248).

Comment 2: "The clinical relevance of the proposed mechanism is implied rather
than demonstrated."

Response: We have revised the Discussion to state the disease-mechanism link
directly and tie it to the patient phenotype (page 16, lines 360 to 379). We
clarified that the mechanism predicts a measurable clinical feature, and we
added the supporting analysis as new Figure 4 (page 14).

------------------------------------------------------------
Reviewer 2
------------------------------------------------------------

Comment 1: "Were the analyses blinded, and how was randomization handled?"

Response: We have expanded the Statistical analysis section to describe
blinding and randomization (Methods, page 6, lines 110 to 128). We confirm the
relevant reporting checklist (CONSORT/STROBE/ARRIVE as applicable) is included.

Comment 2: "Figure 2 appears over-processed."

Response: We have replaced Figure 2 with the minimally processed version and
archived the unprocessed source files and metadata, as required (page 13). No
further adjustment was applied beyond uniform brightness across the full image.

We believe the manuscript is substantially strengthened and hope it is now
suitable for Brain. We are happy to provide further detail on request.

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

Three structural tokens here are doing the work the rubric rewards and that Brain referees expect: the opening to the Editor, the Reviewer 1 / Reviewer 2 split with numbered comments, action language ("we have added," "we have revised," "we have replaced"), and a page and line reference on every change. Keep all four.

What Brain's reviewer culture means for your rebuttal

Brain is a clinical-neurology flagship, not a general neuroscience home. Its editors and associate editors are research-active translational neuroscientists, which sets the dual bar every referee applies: the paper must explain a neurological disease mechanism and carry genuine clinical relevance at the same time. That is why Brain rejects a large share of submissions before review at all for lack of novelty, studies of normal subjects, serious scientific flaws, or work outside scope.

Original articles that are predominantly methodological, or that present hypotheses and models unsupported by original data, are returned without peer review. Single case studies are not considered.

If your paper cleared that editorial triage and went to referees, you already passed the hardest screen. Brain sends suitable articles to at least two experts, whose reports go to the assigned associate editor and the Editor.

The referees are now testing whether the disease-mechanism claim survives scrutiny, with the clinical-decision impact of the work and methodological rigor weighing heavily, and their comments will concentrate on three places: the cohort or sample, the statistical analysis, and the strength of the mechanism-to-disease argument.

Brain's own instructions are unusually specific about statistics: a dedicated Statistical analysis section, the test statistic, degrees of freedom, the exact probability value, 95% confidence intervals encouraged, and a priori sample-size calculations with blinding and randomization detail. Treat any statistics comment as a request to meet that published standard, not as a stylistic preference.

The clinical-significance bar is the one authors underestimate. A reviewer who writes "the mechanistic finding is interesting but the clinical relevance is unclear" is not asking for a stronger Discussion paragraph. They are asking you to connect the mechanism to a measurable clinical feature, a patient phenotype, or a therapeutic implication, and to do it with data rather than assertion. Answering that comment with rhetoric is the response that draws a second major revision.

Reviewer comment at Brain
What it actually wants
Strong response
"Sample size is not justified"
A priori power calculation, not a post-hoc defense
Add the calculation in Methods; cite the page and lines
"Clinical relevance is unclear"
Mechanism tied to a measurable clinical feature, with data
Add the analysis as a new figure; state the disease link directly
"Statistics are incompletely reported"
Test statistic, df, exact P, 95% CI per comparison
Rebuild the Results to Brain's published statistics standard
"Were analyses blinded?"
Explicit blinding and randomization in Methods
Expand the Statistical analysis section; confirm the checklist
"The mechanism is too basic for our readership"
A clinical-neurology consequence, not basic biology alone
Reframe around disease impact, or consider Brain Communications

Source: Brain General Instructions, Oxford University Press (accessed June 2026), plus pre-submission review of Brain-targeted resubmissions.

Tone calibration: what referees reward at Brain

The tone that works is collaborative, specific, and evidence-led. The tone that backfires is defensive, vague, or dismissive of the clinical-significance concern that defines the journal. Here are the contrasts that matter most for Brain.

Bad phrasing
Better phrasing
"We have addressed this concern."
"We added the requested analysis in Methods (page 7, lines 142 to 156)."
"The clinical relevance is obvious from the data."
"We now state the disease-mechanism link directly and tie it to the patient phenotype (page 16, lines 360 to 379)."
"Our sample size is standard for this field."
"We added an a priori power calculation showing the cohort is adequately powered (page 7)."
"The reviewer misunderstands our statistics."
"We see the source of confusion and have reported the test statistic, df, and exact P for each comparison (page 11)."
"This is outside the scope of our study."
"This is an important point; we have added it to the Discussion as a limitation and noted the experiment that would resolve it (page 18)."

Source: pre-submission review of Brain-targeted response letters, mapped to Brain General Instructions language.

Notice the pattern in the Better column: every reply names a manuscript component and a page or line. That is not decoration. It is the difference between a referee who can confirm your change in five seconds and a referee who has to take your word for it.

The page-and-line referencing rule

State a page and line reference for every change you claim to have made, and put the rule into practice from the first comment, not just when it is convenient. This is the most-cited rebuttal mistake in the literature and the one Brain referees flag most because Brain reads your responses in a paste field rather than a polished PDF.

Before you write the response letter, generate the revised manuscript with line numbering on and changes tracked, so the numbers you cite are stable. When you renumber after a later edit, re-check every reference. A response letter that points to "page 14" when the change moved to page 16 reads as careless to a referee who is already deciding whether your revision is thorough.

A second discipline that pays off at Brain specifically: put your substantive responses in the cut-and-paste field, not only in an attached letter. Brain warns that appended letters are not automatically sent to the referees, so a beautifully formatted PDF that lives only as an attachment may never reach the people deciding your fate. The Editor sees the cover letter; the referees see the paste field. Write for both.

In our pre-submission review work with Brain submissions

In our pre-submission review work with Brain submissions, the same revision-stage failures repeat across manuscripts targeting this journal, and they are testable against your own paper before you resubmit. We see the same Brain editorial culture and triage pattern over and over, and Brain editors routinely flag the same gaps. These are the named failure patterns that most consistently turn a revisable Brain manuscript into a second major revision or a rejection.

The cohort that gets described instead of defended. Across our Brain pre-submission reviews, the most common referee-triggering weakness is a cohort or sample size that is reported but never justified. Brain referees, working from a journal that requires a priori sample-size calculations, read an unjustified cohort as a power problem.

The fix is not more participants; it is a power calculation in the Methods and an honest statement of what the cohort can and cannot detect. Check whether your sample size is justified or merely stated, because a referee will.

Clinical significance asserted in the Discussion, not demonstrated in the data. This is the Brain-specific trap. Manuscripts coming through pre-submission review for Brain frequently carry a strong mechanism and a Discussion paragraph that claims clinical relevance without an analysis behind it. Because Brain's editors are translational neuroscientists, that gap is the first thing referees probe. The manuscripts that survive revision add a figure or analysis linking the mechanism to a measurable clinical feature; the ones that stall keep arguing the point in prose.

Statistical reporting below Brain's published standard. Of the Brain-targeted manuscripts we pre-screen, a recurring referee comment is incomplete statistics: a P value with no test statistic, no degrees of freedom, no confidence interval, no sample-size rationale. Brain's General Instructions spell out exactly what the Statistical analysis section must contain, so this comment is fully predictable and fully avoidable. We flag any Results section that reports significance without the full apparatus Brain asks for.

The mechanism that is real but too basic for the clinical readership. Some Brain-targeted manuscripts are excellent neuroscience that never makes contact with neurological disease. When a referee writes "too basic for our readership," the honest read is often that the paper belongs at a mechanism-led venue or at Brain Communications, the open-access sister journal. We help authors decide before they burn a revision cycle defending a clinical angle the data cannot support.

Defensive responses to substantive comments. Across our Brain pre-submission reviews, the response-letter tone that predicts trouble is pushing back on cohort, statistics, or clinical-significance concerns without new evidence. These are the exact dimensions Brain referees are mandated to test, so contesting them with opinion rather than data reads as the author not understanding the journal. The strongest revisions concede early on substance and reserve pushback for clear factual misreadings, supported by pointing to the existing figure or analysis.

Each of these is checkable against your manuscript right now. Run a Brain cohort and clinical-significance check on the revised version before you paste your responses into Manuscript Central.

Submit your Brain revision if

  • Every referee comment is quoted, answered, and tied to a specific manuscript change with a page and line reference.
  • The cohort or sample now carries an a priori power calculation, not just a description.
  • The clinical-significance concern is answered with a new analysis or figure that links the mechanism to a measurable clinical feature, not with a rewritten Discussion paragraph.
  • The Statistical analysis section reports the test statistic, degrees of freedom, exact P value, and confidence intervals that Brain's instructions ask for.
  • Substantive responses are pasted into the response field, with only a short summary in the Editor cover letter.

Think Twice If

A revision is not a promise: only about 13% of submissions are ultimately recommended for publication at Brain, and most papers that reach revision still need a second round or face rejection on revision. Reconsider your resubmission timing if any of the following is true.

  • Your response uses "we have addressed this" without a page and line reference. Brain referees read the responses directly, so a vague answer is immediately visible.
  • You pushed back on a cohort, statistics, or clinical-significance comment with opinion rather than new data. These are the dimensions Brain referees are mandated to test.
  • A referee wrote "too basic for our readership" and your revision argues the clinical angle in prose the data cannot support.

That pattern usually belongs at a mechanism-led venue or Brain Communications.

  • The revised reference list cites a paper that has since been retracted, which undermines an otherwise strong revision. Verify every DOI is clean before resubmitting.

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

Honest friction: rejection on revision at Brain

A revision invitation at Brain is real progress, but it is not a promise. Brain states directly that revision gives no guarantee of acceptance, and that revised articles are rejected when the improvements are insufficient or when new issues arise during re-review. The numbers make the stakes concrete: after peer review, about 16% of submissions are recommended for revision or publication, and roughly 13% are ultimately recommended for publication. The gap between those two figures is the rejection-on-revision zone, and it is where a weak rebuttal does its damage.

The most common reasons a Brain revision fails on re-review: the cohort or statistical concern was acknowledged but not actually fixed, the clinical-significance gap was answered with prose instead of data, or a new flaw surfaced because the revision was rushed. There is also a tone failure mode: a response letter that argues with the referees on the journal's core dimensions reads as a misread of what Brain is, and that perception is hard to recover from in a second round.

If the science is sound but the priority or breadth fell short of Brain rather than the rigor, the Brain Communications transfer is the honest off-ramp. Brain Communications is the open-access sister journal, and the transfer carries your files and reviewer reports across so you do not resubmit from scratch.

Take it when reviewers liked the work but felt it was not quite a Brain-level clinical advance, and when you can fund the article processing charge, which runs around £2,906 for Brain Communications. Do not take it as a way to dodge a cohort or methods concern that will follow the paper wherever it goes. For how Brain handles a manuscript once it is under review, see the Brain under review guide.

A realistic Brain revision workflow

Step
What you are doing
Why it matters at Brain
Read both referee reports twice
Separate substance from style; flag every cohort, statistics, and clinical-significance comment
These three are the dimensions Brain referees are mandated to test
Decide comply vs push back
Comply on substance; reserve pushback for clear factual misreadings
Defensive replies on substance draw a second major revision
Do the work before the letter
Run the added analysis, the power calculation, the new figure
A response promising a fix the manuscript does not contain fails on re-review
Renumber with tracked changes on
Generate stable page and line numbers
Brain reads responses in a paste field; wrong references read as careless
Write point by point
Quote each comment, respond, cite page and line
Vague answers are visibly vague in the paste field
Paste responses into the right field
Substance in the cut-and-paste field, summary in the Editor cover letter
Appended letters are not auto-sent to referees
Verify before resubmitting
Co-author sign-off; confirm every cited DOI is clean
A retracted citation in the revised reference list undermines a revision

Source: Brain General Instructions, Oxford University Press (accessed June 2026), plus pre-submission review of Brain-targeted resubmissions.

Across the response-to-reviewers craft literature, the durable guidance is the same one this guide applies to Brain: respond to every point, make the changes easy to find, and keep the tone collaborative even when you disagree.

The canonical reference is Ten Simple Rules for Writing a Response to Reviewers by William Stafford Noble in PLOS Computational Biology, and recent guidance in Nature Computational Science reinforces the same point-by-point discipline. Both pair well with Brain's own statistics and reporting standards. This guide was last reviewed against Brain's General Instructions on June 6, 2026.

Before you click resubmit, run a final Brain submission readiness check on the revised manuscript and the response letter together, or do a manual pass against the workflow above. The goal is simple: make the referee's job of confirming your changes faster than their job of doubting them.

  • Manusights pre-submission review corpus, Brain-targeted manuscripts

Frequently asked questions

Brain handles revisions through Manuscript Central. In the Author Centre you click 'create a revision' next to the decision, which assigns an R1 (then R2) suffix. There is a dedicated field where you cut and paste your point-by-point responses so the referees can read them directly. You can also attach a cover letter to the Editor, but Brain warns that appended letters are not automatically forwarded to reviewers, so your substantive responses belong in the paste field, not only in an attachment.

Brain's editors and associate editors are research-active translational neuroscientists, so referees test two things at once: whether the work explains a neurological disease mechanism, and whether it has real clinical relevance. Revision requests cluster around strengthening the cohort or sample, hardening the statistical analysis (exact P values, degrees of freedom, a priori sample-size justification, 95% confidence intervals), and making the disease-mechanism link explicit rather than implied.

Yes. Brain states plainly that revision gives no guarantee of acceptance, and revised articles are rejected when the improvements are insufficient or when new issues surface during re-review. Roughly 16 percent of submissions are recommended for revision or publication after review and about 13 percent are ultimately recommended for publication, so even reaching the revision stage does not make acceptance the default.

There is no fixed page limit, but a major revision at Brain typically runs several pages because each referee comment is quoted in full, answered, and tied to a specific manuscript change with a page and line reference. A one-page summary that groups comments together reads as evasive to referees who expect a point-by-point reply.

Comply on anything that strengthens the cohort, the statistics, the controls, or the mechanism-to-disease link, because those are the exact dimensions Brain referees are mandated to test. Push back only when you have evidence the reviewer misread the paper, and do it by pointing to the existing data, figure, or analysis rather than by restating an opinion. Defensive replies on substantive clinical-significance concerns are the fastest route to a second major revision or a rejection.

References

Sources

  1. Brain General Instructions, Oxford University Press (accessed June 2026)
  2. Brain Communications General Instructions, Oxford University Press (accessed June 2026)
  3. Ten Simple Rules for Writing a Response to Reviewers, PLOS Computational Biology (DOI 10.1371/journal.pcbi.1005730, accessed June 2026) - Reporting guidelines Brain requires:
  4. CONSORT 2010 (DOI 10.1136/bmj.c332), STROBE (DOI 10.1016/j.jclinepi.2007.11.008), ARRIVE 2.0 (DOI 10.1371/journal.pbio.3000410)
  5. Retraction Watch database (accessed June 2026)

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