The Astrophysical Journal Response to Reviewers: How to Write a Rebuttal That Wins (2026)

State the exact section and line number for each manuscript change, and reference the specific figure, table, equation, or appendix you revised. This is the single most-cited rebuttal failure at The Astrophysical Journal. Because ApJ usually runs one referee, that single reader has no co-reviewer to cross-check against, so a change they cannot locate reads as evasion straight away.

A referee who can click to Section 3.2, lines 14 to 28, and see the new systematic-error budget finishes faster and re-reviews more favorably. Three habits make every change findable:

• Never write "we have addressed this in the manuscript" without a location.
• Use line numbers from the revised file, not the original.
• Note when a change lands in an appendix or a machine-readable table rather than the main text, since AAS data editors check those separately.

The referee sees your tone across every comment in a single document, and the scientific editor reads the same letter when deciding whether to adjudicate. A dismissive reply to one comment colors how the referee reads the rest. Calibrate.

The pattern that works at ApJ: concede where the referee is right, re-run the analysis, point to the exact section, and push back only on a request that is genuinely out of scope, with a physical reason and an alternative. Demanding a new referee instead of answering the uncertainty critique is the one move that almost never helps.

One referee, one working-astronomer editor

The Astrophysical Journal runs on a single-referee model by design. The journal states that ApJ articles are generally sent to one reviewer, although at the discretion of the scientific editor two or more may be used. That editor is a working astronomer, not a full-time professional editor, and owns the decision.

If a substantive issue cannot be resolved, the editor may seek a second reviewer to adjudicate. This is the closest thing ApJ has to a new-referee path, and it is the editor's call, not the author's demand. The practical consequence: your response is a document for two readers, the referee and the editor, and the editor uses your cover letter to judge whether the exchange has stalled.

ApJ also offers optional dual-anonymous review on request. If you chose that route at submission, keep your reply anonymized and route any identity-revealing detail through the editor.

Most ApJ refereeing is collegial. Astronomy referees are largely supportive, and once authors return a revision that takes the recommendations seriously, most papers are accepted, sometimes after a second round and occasionally with a second referee brought in to break a deadlock. You may consult co-authors freely while revising, but public dissemination of the referee report and editorial correspondence is inappropriate. After you submit a revision, the convention is to wait roughly six weeks before sending a brief, professional status request through the AAS system.

The uncertainty bar carries hardest into revision

The bar that gets carried hardest into the revision is uncertainty and statistical rigor. Error bars must appear on all measurements where uncertainties exist, and reporting only statistical errors when systematic effects are present draws a revision request on its own. A detection or measured value stated without a quantified uncertainty is the fastest way to a second round. When a referee questions whether an effect is real, the answer is the false-alarm probability or the systematic-error budget, not a hedge added to the Discussion.

The AAS data and software policy is a revision checkpoint

The second structural bar is the AAS data and software policy, which becomes a checked, fixable item at revision. The specifics AAS expects:

• A data availability statement, with well-documented data deposited under an open license (Zenodo and Harvard Dataverse are preferred, and AAS asks you to submit the deposit to its AAS Journals Community).
• Software cited in a persistent archive with a version number using the \software command, rather than embedded as a tar or zip archive.
• A machine-readable table for any table longer than about 200 data rows, with the manuscript carrying only a sample table once a table exceeds about 400 rows.

AAS data editors review the data content and software citation on nearly every submission and verify MRT conversions at acceptance. So a referee or editor request to deposit a catalog or release the reduction code is not optional polish; it is a compliance gate you clear in the rebuttal.

Open-access charges make a stalled revision expensive

One more thing shapes the revision: ApJ is fully gold open access and you pay on acceptance, so the work in your rebuttal protects a real sunk cost. The journal bills on a digital-quanta model where 350 words equals one quantum, and each figure, table, and data component counts too.

Source: Article Publication Charges and Licensing Agreements, AAS Journals, accessed June 2026.

Authors retain copyright under a CC-BY 4.0 license, and the AAS waiver culture means no paper is rejected for inability to pay. If a referee's uncertainty or data concern stalls the revision into a rejection, that is a charge you do not get to recover, which is one more reason to re-run the analysis the first time. For a short, high-impact result, the companion Astrophysical Journal Letters caps articles at 10 journal pages and turns review around faster.

How ApJ compares for rebuttal calibration

How this compares to the rest of the field matters for calibration. A response at Physical Review Letters faces a length cap and a multi-referee APS culture, while at Nature Astronomy a professional editor integrates two or three reports and a major revision often means new observations.

ApJ sits apart: usually one referee, a working-astronomer editor, no strict page limit, and a revision bar built around quantified uncertainty and AAS data compliance rather than novelty theater. Because the decision can rest on a single referee, the comprehensiveness and tone of your point-by-point response carry more weight here than at a journal where three reviewers dilute any one read.

In our pre-submission review work with Astrophysical Journal manuscripts, the rebuttals that stall into a second referee round share a small set of recurring weaknesses. These are the same ones the single referee flags at re-review, and because ApJ runs on one referee, each weakness costs more than it would at a multi-reviewer journal. In our analysis of Astrophysical Journal rebuttals, each weakness below maps to a specific, named failure pattern in the AAS editorial culture, and each is testable against your own draft response before you upload it.

Conceding the error in the letter but not re-running the analysis. The most common and most expensive pattern in our Astrophysical Journal pre-submission reviews is a response that agrees the referee is right about a missing systematic uncertainty, then adds a sentence to the Discussion instead of re-running the error budget.

At ApJ, where the statistical-rigor bar carries into revision, conceding a flaw without fixing the analysis reads worse than a respectful disagreement. The referee asked for a quantified uncertainty; the only answer that moves the decision is the recomputed number in the revised Section, not an acknowledgment.

Demanding a new referee instead of addressing the uncertainty critique. Because the scientific editor, not the author, decides whether to bring in a second referee, a rebuttal that argues the referee is wrong and should be replaced almost always backfires.

In our Astrophysical Journal pre-submission reviews we see this most when a referee questions a detection significance: the author treats it as a personality problem rather than running the false-alarm probability the referee actually wants. Address the substantive concern in the revised statistical analysis, and let your cover letter, not a demand, signal to the editor if you genuinely believe the exchange has stalled.

Leaving the data or code the editor requires undeposited. A rebuttal that promises open data but names no repository, or cites software without a version, draws an immediate compliance comment.

In our pre-submission review work with Astrophysical Journal manuscripts, responses that skip the Zenodo or Dataverse deposit, omit the \software citation, or ignore the machine-readable-table requirement for a large catalog consistently add a round, because AAS data editors check these at acceptance. Deposit the data, cite the code with its version, convert the long table to an MRT, and point to each in the response.

Treating one referee as low-stakes. Because there is usually a single referee, some authors answer tersely, assuming one reader is easy to satisfy. The opposite is true: that one referee holds the decision.

In our Astrophysical Journal pre-submission reviews, the responses we flag hardest are the ones that answer half the comments fully and the rest with one-line dismissals. The same letter, rewritten to address every numbered comment comprehensively and respectfully, with the re-run results and the deposited data shown, reads as the work of an author the referee can recommend.

Re-run the analysis, deposit the data, answer every comment, and let the editor adjudicate. That four-part discipline is what separates an Astrophysical Journal rebuttal that clears one referee round from one that stalls into a second. Check whether your Astrophysical Journal point-by-point response answers the uncertainty critique → before you submit.

Source: Manusights pre-submission reviews of Astrophysical Journal-targeted resubmissions, 2025 cohort.

Authors consistently underestimate the re-analysis effort and overestimate the writing effort. This breakdown is about workload, not the journal's decision clock; for the end-to-end decision schedule, see the Astrophysical Journal review time guide.

Source: Manusights pre-submission reviews of Astrophysical Journal resubmissions, 2025 cohort, last updated June 7, 2026.

A revision invitation at The Astrophysical Journal is not a soft acceptance. The revised manuscript and your point-by-point response go back to the same single referee, and the paper can still end in rejection after re-review if the referee's core concern is not resolved, or if the scientific editor, having brought in a second referee to adjudicate, sides with the unresolved critique.

Most rejections at this stage trace to one cause: the author conceded an uncertainty or systematic-error problem in the response letter but did not re-run the analysis to fix it. The second most common is an undeposited dataset or uncited code that the AAS data editors would have flagged at acceptance anyway.

Think twice before you resubmit if any of these are true:

• The response uses generic "we have addressed this" language with no section or line numbers.
• A referee questioned a detection or an uncertainty and you answered with text instead of a re-run analysis.
• The data availability statement still names no repository, or the software citation has no version.
• The rebuttal asks for a new referee rather than answering the substantive concern.
• The methods or sample selection a referee called unreproducible are still missing from the revised draft.

Fixing these before resubmission is what keeps a second referee round from becoming a rejection.

Before you upload, scan your own response for the patterns that draw an immediate re-review comment. Each is a specific, checkable thing in your draft, not a vague quality dimension.

• A reply with no location. Any "we have revised the manuscript" with no section and line number reads as evasion the moment the referee cannot find the change.

• A conceded error with no re-run. You agreed the systematic uncertainty was missing but only added a sentence to the Discussion.

This is the single most common cause of a second round at ApJ.

• A new-referee request. Asking the editor to replace the referee instead of answering the critique signals you could not address the concern on the science.

• A data statement that names no repository. A promised open dataset with no Zenodo or Dataverse DOI, or software cited with no version, fails AAS compliance the editor will enforce.

The official AAS and IOP guidelines tell you to submit a cover letter with a point-by-point response and to deposit data and cite software. What they leave out is the part that changes how you write every reply at ApJ specifically:

• The decision usually rests on a single referee, not a panel.
• Only the scientific editor can bring in a second referee to adjudicate.
• The bar carried hardest into revision is uncertainty and statistical rigor.
• The top cause of rejection on revision is a conceded error left un-re-run.

The patterns above come from our pre-submission reviews of Astrophysical Journal rebuttals, and they are testable against your own draft today, not theoretical concerns. Run a final Astrophysical Journal manuscript readiness check before you upload the revision.

• Manusights pre-submission reviews of Astrophysical Journal-targeted manuscripts (2025 cohort)