From Rejection to Acceptance: What Changes in the Revision

Rejection is information, and the papers that succeed on the next round change in predictable ways rather than arguing harder with the same manuscript.

Explainer · 9 min read · Directive Publications Editorial Team

Start by classifying the rejection

Rejections are not one thing, and the type decides most of what you do next.

A desk rejection arrives quickly and without external reports. It is a statement about scope, article type or basic readiness — nobody evaluated the science. Rewriting your discussion in response to one is wasted effort. The fix is a different journal, or occasionally a different article type at the same journal.

A rejection after review comes with reports, and the reports contain the actual reason. It is rarely the whole list. Look for the objection two reviewers raised in different words, or the one the editor repeated in their own paragraph — that is the decision, and the rest is context. The editor's letter outranks the reviewers' comments here as it does everywhere else.

A "reject and resubmit" or "reject with encouragement" is not a rejection in the ordinary sense. It is a major revision with the clock reset, often because the journal does not want a file sitting in revision for months. Treat it as an invitation: go back to the same journal, quote the previous manuscript number, and answer the reports the way you would answer a major revision.

Give yourself a few days before deciding anything. Then reread the reports with a pen and mark each comment as fit, claim, clarity, methods or disagreement. Those buckets are the rest of this post.

What often actually changed

1. Journal fit — resubmitted to a better-matched scope
2. Claim size — conclusions narrowed to evidence
3. Clarity — figures and structure made reviewable
4. Methods transparency — enough detail to evaluate
5. Response craft — point-by-point, calm, complete

Journal fit is the cheapest change available and the one authors skip, because changing journals feels like giving up rather than fixing something. Check it before you touch the manuscript. Read the aims and scope, then read the titles in the last few issues and ask whether your paper would look out of place beside them. A mechanistic study in a journal that publishes clinical outcomes is not a weak paper; it is a paper in the wrong room. One more signal worth taking seriously: if the journals that dominate your own reference list are not the journal you submitted to, that mismatch is worth explaining to yourself before an editor has to explain it to you.

Claim size is the commonest substantive fix. The claim in your abstract has to be the claim your data can carry, and the gap between the two is usually visible in the verbs. "Shows", "demonstrates" and "establishes" are promises; "is consistent with", "was associated with" and "suggests" are descriptions. The same applies to population and setting. If you measured one cohort at one site, that belongs in the claim itself and not only in the limitations paragraph. So "X reduces Y" becomes "in this single-site cohort, higher X was associated with lower Y." That is not a weaker paper, it is a defensible one — reviewers seldom object to a modest claim fully supported by the evidence, and they reliably object to a large claim resting on part of it.

Clarity matters because a reviewer who cannot follow something has to assume the worst about it. Reviewing happens in the evening, in one or two sittings, by someone who is not in your lab. Give each figure one message, label the axes with units, put the sample size in the caption, and check that the figure survives being read before the paragraph that explains it. Then check the structure: does each results subsection answer a question the introduction actually raised, in the order the introduction raised it? Confusion is not neutral in review. It gets written up as doubt.

Methods transparency means enough detail for a competent stranger to evaluate what you did. Concretely: software and version numbers, the exact model specification rather than "regression analysis", how missing data were handled, exclusion criteria with the number excluded at each step, instrument settings or reagent sources, and where the data and analysis code can be found. Where something genuinely cannot be shared, say so in a sentence and say why. Brevity in methods reads as concealment, and a reviewer who cannot check a step tends to recommend rejection rather than ask a question about it.

Response craft is what turns the work into an acceptance. Number every comment as the reviewers numbered it, reproduce each one verbatim rather than paraphrasing, and answer in three parts: what you understood the comment to ask, what you changed, and where the change appears — section and line, taken from the final file. Answer the easy ones too; "corrected, thank you" is a complete response to a typo. Keep the letter shorter than the reviews. A response longer than the review it answers usually means you are arguing instead of revising.

What rarely works

• Submitting the identical file everywhere
• Inflating novelty language
• Ignoring the hardest reviewer point

All three assume the problem was the reader.

Sending the identical file to the next journal ignores how small reviewer pools are inside a field. The same person may well see it again; and even where they do not, the objection that persuaded one set of reviewers will persuade the next set, because it was usually a real objection. If nothing about the manuscript changed, you have bought a second rejection with three more months.

Inflating novelty language does the opposite of what it is meant to do. Words like "first", "novel" and "paradigm" arrive in editorial inboxes constantly and carry no information; worse, a reviewer told that a result is unprecedented starts hunting for the precedent, and often finds one. Write the contribution sentence in plain terms and let the reader reach the conclusion themselves.

Ignoring the hardest reviewer point is the expensive one. It is the hardest point precisely because you cannot easily answer it, which is exactly why the next reviewer will land on it too. If you genuinely cannot address it — the data do not exist, the experiment would take two years, the design cannot test causal direction — then name it. Say what you cannot rule out, put it in the limitations in your own words, and state what study would settle it. An acknowledged weakness is reviewable. A concealed one is a rejection waiting for someone who notices.

If you are moving to a different journal

Confirm the first decision is final and the manuscript is formally out of that journal's system before you submit anywhere else. Holding the same paper under consideration at two journals at once is a genuine ethical breach rather than a technicality, and it is easy to trigger by accident if you assume a rejection closed the file for you.

Then treat the reformatting as real work and give it a day. Rebuild the structure, reference style and word limits to the new journal's guidelines, redo the title page and declarations in their wording, and check the figure specifications. Write a new cover letter whose fit sentence names something specific about this journal rather than something true of any journal.

Two disclosure questions come up. You are under no obligation to announce that a different, unrelated journal rejected the paper. But if you arrived through a transfer inside the same publisher, say so plainly and say whether reviews travelled with you — it is trivially checkable and looks bad when hidden. Some journals also invite you to attach the previous reviews and your responses voluntarily, which can shorten the round when your revision genuinely answered them. Read the submission guidelines rather than assuming either way.

A revision sprint (2 weeks)

Week 1: structural fixes and analyses
Week 2: response letter + co-author read

The two weeks matter less than the boundary around them. Rejected manuscripts fail more often from drift than from difficulty: the file goes into a folder, the postdoc leaves, the data become awkward to rerun, and a paper that needed nine days of work is still unpublished two years later. Put dates in a calendar and tell your co-authors what they are.

A workable week one is Monday to decide the destination journal and confirm fit, Tuesday and Wednesday for analyses and anything a reviewer asked you to rerun, Thursday for figures and structure, Friday for methods detail. Week two: Monday and Tuesday to draft the point-by-point response against the final file, Wednesday for co-authors to read the manuscript and the letter, Thursday to make the changes they send back, Friday for submission-system admin.

Ask co-authors for one specific thing rather than for general comments. "Mark any sentence in this letter that sounds annoyed" and "tell me whether the abstract claim matches the results section" each take a reader ten minutes and catch what you can no longer see yourself.

If week one shows that the fix is not a fix but a six-month experiment, stop the sprint and say so. That is a different decision, made with your co-authors, about whether the paper goes to a more suitable journal now or waits for new data. Either answer is fine. Discovering it in week two of a sprint you have already announced is not.

Before you resubmit

1. The rejection type is clear, and you are answering the one you actually received
2. The destination journal's scope has been checked against your paper, not assumed
3. The abstract claim matches what the results section shows
4. Every figure carries one message, labelled axes and a sample size
5. Methods name software versions, exclusions, and where data and code live
6. The hardest reviewer point is addressed somewhere a reviewer will find it
7. Every numbered comment has a response, including the ones you accepted outright
8. The previous journal's decision is final and the file is closed there
9. A co-author has read the letter for tone as well as for accuracy

Guides: Peer Review Process · Responding mindset via Directive Academy

Bottom line

None of this is persuasion. Fit, claim size, clarity and methods detail all push in the same direction: they reduce the number of things a reviewer has to take on faith. A reviewer who can check your claims will engage with them. A reviewer who cannot check them has to guess, and guessing is what produces rejections.

Acceptance is usually earned by making the paper easier to trust — not louder to sell. For Authors · Submit