Desk Rejection: Why a Fast "Not for Us" Serves Authors, and Who Should Make the Call

Desk rejection is when a journal editor declines a manuscript without sending it to external peer review. The editor, sometimes with an editorial assistant or an associate editor, reads the submission, decides it will not go further at this journal, and tells the author, often within a week. Journals do it because expert review is limited: a paper that does not fit the journal's scope, or does not meet its basic requirements, uses reviewer time that belongs to papers the journal could publish.

Most of what you will find online about desk rejection is written for authors who just received one. This guide is for the other side of the desk: editors and publishing teams deciding when to desk reject, how to do it fairly, and what to automate along the way. Much of the evidence comes from editors and publishing leaders who spoke on Prophy Roundtable, the monthly panel convened by Prophy, which builds reviewer-finding and conflict-of-interest tools for publishers.

What is a desk rejection, and how is it different from rejection after review?

A desk rejection ends a manuscript's journey at the editorial office. A rejection after review comes later, with reviewer reports attached. Both are "no", but they cost very different amounts of everyone's time.

A content analysis of rejection reports from one journal, the Indian Journal of Psychological Medicine, puts a number on the gap. The median time to a desk rejection was 3 days. The median time to a rejection after peer review was 42 days. The most common reasons for desk rejection at that journal were lack of novelty and being out of scope. That is one journal, so read it as an illustration, not a benchmark.

How often it happens varies by journal, and not every journal publishes the figure. PLOS ONE does: 30.8% of its submissions were rejected without peer review in January to June 2023, against 21–23% in each half-year from 2020 to 2022 (PLOS ONE journal information). The rate also depends on who reads the submission. When the three co-editors-in-chief of the International Journal of Public Health pre-screened the same 30 manuscripts independently, they would have desk rejected 47%, 80% and 60% of them, and they agreed fully on only 43% (Künzli et al., 2026).

Why do journals desk reject papers?

Journals desk reject for four broad reasons, and only some of them are about quality.

1. Scope. The paper is sound but belongs to a different community.
2. Contribution. The work does not add enough for this journal's readers. At the Indian Journal of Psychological Medicine, lack of novelty was among the two most common reasons.
3. Requirements. The submission is missing declarations, data statements or the formatting the journal requires.
4. Integrity signals. Something in the submission needs a human look before anyone invests review time.

The first two are editorial judgment about a specific readership, which is also where editors disagree most. The last two are where tools help, and where who decides matters most.

Is a fast "not for us" a service to authors?

Yes, when the message is honest and the decision is quick. An author who hears "this is not for us" in three days can submit elsewhere that week. An author who hears it after ten weeks has lost a season.

Kent Anderson, Founder and CEO of Caldera Publishing Solutions and a former publisher at highly selective journals, described what a desk rejection from such a journal said: it was a relevance judgment, and it was brief. In his words, a quick desk decision "allowed the author to move on, relatively quickly. And I think that that's also a service to authors." (Prophy Roundtable #8, 0:40:00). Tony Alves, Co-Founder of Scholarly Publishing Solutions, speaking as an independent consultant, made the same point: a desk reject is a positive for the researcher because it moves the paper along sooner.

What this means for your journal:

• Publish the window you intend to meet. Tell authors how long a first decision takes, then measure how often you hit it. A promise you keep is part of the service.
• Say why, in a sentence. "Outside our scope" or "not enough new for our readers" gives the author something to act on. Silence does not.
• Judge speed per journal. Different communities value different things. Our post on how long peer review takes covers decision times in more detail.

How should editors decide what to desk reject?

Reviewer attention is a budget, and the desk decision is where an editor chooses what to spend it on. Anderson put the principle plainly: "Peer review is a precious resource that should be allocated to papers that you think are actually relevant." (Prophy Roundtable #8, 0:41:15).

Nobody on that panel argued for fewer desk rejections. The practical move that follows from the principle is a measurement: count how many of last year's manuscripts went to full review and ended in rejection anyway, and how many of those were rejected on relevance. Each of those used reviewer invitations, reminders and reports on a call the editor could have made at the desk. Moving the relevance check earlier, to the first read of the abstract and cover letter, returns that capacity to the papers that deserve it.

Because scope and contribution are judgment calls, two editors can read the same submission differently; in the co-editor study above, "soft" criteria such as novelty drove most of the disagreement. That journal's response was to add a second opinion before a manuscript goes to review, a cheap check for any office.

The editorial board owns the scope and contribution questions. Operations can own the requirements check. That split is where the next section picks up.

Which parts of screening can tools do, and which need a person?

A screening tool may flag a submission. Only a person may reject it.

Michael Willis, Associate Director, Editorial Management Solutions at Wiley, put the principle plainly: "They are there to support the decision making. They're not there as a substitute for decision making." (Prophy Roundtable #8, 0:26:19). He also recalled what happened when a text-similarity checker was first rolled out at scale: some editors wanted to reject automatically anything above a similarity threshold, as if the score were a plagiarism verdict, and editors had to be taught what the score measured, how to read it and what to do with the result.

Alves set out the conditions under which any automated triage could be acceptable: "it needs to be transparent. It needs to be auditable, and people need to be able to appeal it." (Prophy Roundtable #8, 0:44:54). He added that an editor wants to know why a paper was kicked out, what the thresholds are, and who bears the risk if the tool is wrong.

For your pipeline, that becomes a short checklist you complete before a tool goes live:

• Name who sees each flag. Every automated signal should land in front of a named editor or editorial assistant.
• Record why it fired. The person reading the flag needs the underlying evidence, not only a score.
• Write the appeal path. An author who disputes the outcome needs a route to a human who can change it.
• Keep the decision with a person. The tool informs. The editor signs.

The same logic holds for compliance checks. Image forensics, basic statistics and declaration checks need no expert reviewer, so they can sit with editorial staff and tools. The scientific judgment that follows still belongs to people.

How do you cut reviewer workload before a reviewer sees the paper?

The cut starts with the checks reviewers repeat on every paper, and with the question of whether a community could agree a standard that lets a tool run them at submission.

There is a working example. In one field, submissions have arrived with structured, machine-readable data since the 1990s; software validates the data and produces a report the reviewer reads before the first paragraph of the paper. The software is not what makes it work. Any team can build a validator once the community has agreed a data standard, and that agreement came first. Kruna Vukmirovic, Head of Publishing Strategy at the International Union of Crystallography, argued on Prophy Roundtable #9, on whether peer review should be paid, restructured or abolished, that this kind of restructuring, before a reviewer sees the paper, is where reviewer workload can be reduced. The effect on review: "we didn't remove the need for human review, but we made that human review better aimed." (Prophy Roundtable #9, 0:04:51).

Not every field can do this. Common standards are valuable upstream but hard to apply across multidisciplinary research, a point raised on the same panel. The principle still travels: separate the work a reviewer must do from the work that arrives on their desk because nobody filtered it. Screening, verification of methods and data, and the exchange between expert peers are different jobs. Screening needs no expert reviewer at all, and the expert exchange is the scarce part.

Where does reviewer finding fit in the desk-reject workflow?

Reviewer finding sits in the layer just after the desk decision, and it benefits from the same discipline: spend expert time where it is needed. Once a paper passes the desk, an editor still has to find qualified, conflict-free reviewers, and the search itself is slow when it relies on personal networks and memory. For editorial departments that need to find high-quality peer reviewers quickly, Prophy offers an extensive database of over 104 million researchers' profiles. See Referee Finder for how the matching works and how conflicts of interest are checked.

Prophy does not make desk-rejection decisions. It helps the people who do at the next step, the search between "send to review" and the first invitation. For the wider case on speed, quality and editorial control, see peer review at a breaking point and balancing technology and editorial control.

FAQ

How long does a desk rejection take?

It depends on the journal. In the Indian Journal of Psychological Medicine analysis cited above, the median was 3 days, against 42 days for rejection after peer review. Publishing your target window and measuring against it is the best way to know your own number.

How do you desk reject a paper?

Check scope, contribution and the author guidelines, then send the author a decision with one clear reason. If a screening tool raised a flag, the editor reads the evidence behind it and makes the call personally.

Can a tool desk reject a paper automatically?

Tools can flag a submission. Practitioners on Prophy Roundtable were clear that a person should make the rejection, and that any automated triage must be transparent, auditable and appealable by the author.

About the experts

• Kent Anderson — Founder and CEO, Caldera Publishing Solutions. Prophy Roundtable #8: The Speed-Quality Trade.
• Michael Willis — Associate Director, Editorial Management Solutions, Wiley. Prophy Roundtable #8: The Speed-Quality Trade.
• Tony Alves — Co-Founder, Scholarly Publishing Solutions. Prophy Roundtable #8: The Speed-Quality Trade.
• Kruna Vukmirovic — Head of Publishing Strategy, International Union of Crystallography. Prophy Roundtable #9: Should Peer Review Be Paid, Restructured, or Abolished?.

About Prophy Roundtable

Prophy Roundtable is a monthly panel of editors and publishing leaders on where scholarly publishing is heading.

Prophy helps publishers identify relevant reviewers, detect conflicts of interest, and discover related research using a database of 104M+ researcher profiles and 200M+ publication records. Learn more at prophy.ai.