Few experiences are more deflating than submitting a paper after weeks of polishing, only to receive a rejection notice within days — before any reviewer has even read your work. Desk rejections are handled by area chairs or programme chairs rather than reviewers, and they happen faster than you might expect. The good news is that the vast majority of desk rejections are entirely preventable.
What Is a Desk Rejection?
A desk rejection (also called an editorial rejection or pre-review rejection) occurs when a programme chair or area chair determines that a submission does not meet the basic requirements for the venue and removes it from the review queue before assigning it to reviewers. It is standard practice at most major conferences and protects the reviewer pool from wasting time on papers that were never eligible in the first place. At high-volume venues such as NeurIPS, CVPR, or ACL, programme chairs process thousands of submissions and apply desk-rejection criteria efficiently and without apology.
The Most Common Reasons Papers Are Desk-Rejected
Understanding the typical triggers is the first step toward avoiding them:
- Out of scope: The paper addresses a topic that does not fit the conference's stated areas, no matter how good the work is.
- Formatting violations: Wrong template, wrong font size, non-standard margins, or incorrect bibliography style.
- Over-length submissions: Exceeding the page limit — even by half a page — is an automatic rejection at many venues.
- Anonymity violations: In double-blind conferences, naming the authors in the text, citing your own unpublished work in a way that reveals identity, or linking to a non-anonymised repository.
- Poor English: Some venues explicitly state that papers with language quality below a minimum threshold will not be sent for review.
- Missing required sections: Absence of an ethics statement, reproducibility checklist, broader impact section, or supplementary material where mandated.
- Prior publication overlap: Submitting work that has already appeared at another peer-reviewed venue without meeting the venue's originality requirements.
How to Read the Call for Papers Properly
The Call for Papers (CFP) is not marketing material — it is a binding contract. Read it in full at least twice before you begin preparing your submission. Pay particular attention to the scope statement (it is often more restrictive than the conference name suggests), the formatting requirements, the page limits for both the main paper and the appendix, and any mandatory sections. If you find your paper on a platform like latestconferences.com, always click through to the official conference website and download the author guidelines directly — never rely on a summary.
Building a Formatting Checklist
Create a checklist specific to each submission and work through it methodically in the 24 hours before you submit. A robust checklist covers:
- Correct LaTeX or Word template downloaded from the official site (not a third-party version).
- Page count verified with all required sections included.
- Font sizes and margins not manually overridden.
- References formatted in the required style and within any page or count limits.
- Figures and tables clearly legible when printed in black and white, if required.
- PDF compiled from the submission template, not a personal style file.
- All supplementary materials correctly packaged if required.
Double-Blind Pitfalls to Watch For
Double-blind review is now standard at most top-tier computer science and AI conferences, and anonymity violations are among the most common causes of desk rejection. Remove author names and affiliations from the PDF. Audit your related work section: if you cite your own prior work, refer to it in the third person and consider whether the citation pattern itself reveals your identity. Do not link to your personal website, GitHub profile, or any non-anonymised repository. Be careful with project names and dataset names that are publicly associated with your lab. If you have a preprint on arXiv, check whether the conference's policy permits simultaneous submission and whether you need to remove the arXiv link.
Can You Appeal a Desk Rejection?
Technically yes, but appeals after desk rejection are rarely successful. Programme chairs deal with enormous submission volumes and apply criteria consistently. If you believe a desk rejection was made in error — for example, if the system incorrectly flagged a formatting issue that does not actually exist in your file — a polite, factual email to the programme chairs is appropriate. However, appealing on the grounds that you disagree with a scope decision is almost never productive. Accept the decision, address the issue, and redirect your submission energy to a more suitable venue.
Treating Desk Rejection as a Learning Opportunity
A desk rejection that results from a genuine scope mismatch is useful information: it tells you that your paper's framing or contribution framing needs work before it will land well at venues in that area. Use the time you recover from a desk rejection to revisit the paper's positioning, sharpen the contribution statement, and identify two or three alternative venues whose scope is a better match. Keep a log of the specific reason for each desk rejection — patterns in that log are among the most efficient diagnostics available for improving your submission process.
Prevention Is Far More Efficient Than Recovery
Invest thirty minutes before every submission in a structured checklist review, and desk rejection becomes a near-non-event in your career. The researchers who receive the most desk rejections are typically those who submit under time pressure without re-reading the author guidelines for the current year — because guidelines change between cycles. Build in a mandatory cooling-off day before submission where the only task is compliance checking, not content editing. That one habit will save you weeks of lost submission windows over the course of a research career.