Your first review will probably arrive in three parts: an editor's letter, two or more referee reports, and a decision that is rarely as bad as it first reads. The most common outcome for a new submission is not instant acceptance but revision — often major revision — which means the paper is salvageable and the reviewers spent time on it. Surviving peer review, then, is mostly a matter of reading the reports correctly and answering them in a way a third party can follow.
The stakes are real. Publication is how academic work enters the record, and the review process is the gate it passes through. That gate runs on volunteer labor, as Peer Review Runs on Free Labor — and the Bill Is Enormous laid out: the people judging your manuscript are unpaid, busy, and reading on their own time. That fact explains a lot about how reports are written, including the terse ones.
What follows is a practical path through the process: what the decision letter actually means, how to build a response, when to argue back, and what to do if the answer is no.
What does the decision letter actually mean?
Editors usually choose among a small set of outcomes. Reject means the paper is out at this journal. Reject with encouragement to resubmit means the same thing, but with a hint that a substantially different paper might fit. Major revision means the reviewers raised problems the editor thinks you can fix — new analysis, a reframed argument, a sharper literature position. Minor revision means the core of the paper survived; the remaining work is mostly clarification.
Read the editor's letter before the reports. The editor summarizes what matters. If the letter says the contribution is interesting but the method section needs work, that is the assignment. If it says the contribution itself is unclear, no amount of tidying will save the paper — you have a framing problem, and it should be solved first.
One warning: do not treat any revision decision as a promise. A major revision can still be rejected on the second round if the fixes do not hold. The decision describes the current state of the manuscript, not a contract.
How do you read a harsh review without spiraling?
First, separate the tone from the content. Some reviewers write bluntly; a short, sharp sentence can contain the single most useful observation in the report. Strip the adjectives and list the actual requested changes. Most reports, however harsh, resolve into a handful of substantive demands plus some smaller notes.
Second, triage the demands into three buckets: things you must do, things you can do, and things you will push back on. A missing robustness check usually lands in the first bucket. A request for a whole second study may land in the third — but push back with a reason, not with annoyance.
Third, wait before you respond. A day or two away from the reports is not procrastination; it is the cheapest way to lower the temperature of your reply. Reviews read at midnight read worse than reviews read after coffee.
What makes a response letter work?
The response letter is a document with one job: let the editor and reviewers verify that every point was addressed. The standard structure is simple and worth copying.
- Quote each reviewer point, numbered, in full or in close paraphrase.
- Answer directly beneath it, in plain language, stating what you changed.
- Point to the exact location in the revised manuscript — page, paragraph, section.
- Mark changes in the manuscript itself, often with tracked changes or highlighting, so nothing has to be hunted down.
A good response reads like a change log, not an essay. Reviewers skim. If a change is buried, they may conclude it was not made. If every point has a visible answer with a location, the second round goes faster and the tone improves — reviewers who feel heard tend to write shorter second reports.
Include a short cover note to the editor summarizing the major changes in a few sentences. Editors often read only that plus the reports before deciding. Make it easy for them to say yes.
When should you push back on a reviewer?
Push back when the reviewer is factually wrong, when the request exceeds the paper's scope, or when two reviewers contradict each other. Do not push back on style preferences you can cheaply accommodate. The arithmetic is simple: a concession that costs you an afternoon is cheaper than a fight that costs you a month.
When you do disagree, disagree with evidence. Cite the specific literature, the specific data limitation, or the specific methodological constraint. A response that says "we respectfully disagree because the sample cannot support that analysis, as noted in Section 4" is far stronger than one that merely restates the original choice. Where a request is genuinely impossible, say so plainly and explain what you did instead.
If reviewers contradict each other, put the contradiction in front of the editor and ask for a ruling. Resolving it unilaterally — satisfying one reviewer and ignoring the other — invites a bad second round. The editor, not you, owns that call.
What about rude or useless reviews?
Occasionally a report is genuinely unhelpful: no substantive content, or personal in tone. You have two legitimate moves. One is to answer the substantive fragments, if any exist, and let the thinness speak for itself. The other is to flag the report to the editor neutrally — "Reviewer 2's report raises no specific requests; we have addressed the general concerns about positioning in Section 2." Do not attack the reviewer in the response. The editor has seen rude reports before and knows what they look like. We covered a connected angle in The Two-Tier Faculty: What Tenure-Track and Adjunct Economics Look Like.
There is also a systemic point worth knowing as a new author: the same volunteer reviewers judging your paper are, on another day, authors waiting on reviews of their own. The whole exchange is a shared queue, which is part of why the process can be slow and why the economics of it look the way they do. Patience with the queue is not the same as patience with a bad argument — you can hold both.
What if the paper is rejected?
A rejection is a decision about one manuscript at one journal, not a verdict on the research program. The practical steps are short. Read the reports once more for anything that would genuinely improve the paper. Fix those things. Then submit elsewhere, with a cover letter that does not mention the previous journal. Do not resubmit the identical manuscript anywhere; reviewers talk across journals more than new authors expect.
If the rejection came with a resubmit invitation, take it seriously — but treat it as a new submission that happens to have helpful notes attached. Rework the framing, not just the flagged paragraphs.
Our analysis: what actually gets papers through
Across the advice given to new authors, one pattern repeats: the papers that survive review are rarely the ones that met every request. They are the ones where the response letter shows the authors took the process seriously — every point answered, every change locatable, every disagreement argued on the merits. Reviewers are volunteers with finite attention. A response that respects that attention gets better reviews than a brilliant manuscript with a sloppy reply.
The temper part of the brief matters too. Anger at a reviewer is a normal first reaction and a terrible second one. Write the angry draft if you need to, then delete it and write the change log. The reviewer will never know the first draft existed, and your argument will land harder for the calm around it.
What remains unknown is how much of this transfers across fields. Norms differ — a response letter in mathematics looks different from one in psychology, and some venues handle review through public or open channels. The core discipline, though, travels well: read the decision, answer every point, argue with evidence, and keep the red pen pointed at your own manuscript first.
Sources: rottentomatoes.com · primevideo.com · music.youtube.com
