PNAS Submission Guide: What to Prepare Before You Submit

In our pre-submission review work with manuscripts targeting PNAS, three patterns generate the most consistent desk rejections. The submission guide on pnas.org tells you what to prepare. This section tells you what actually trips people up.

In our experience, roughly 35% of desk rejections at PNAS trace to scope or framing problems that prevent the paper from competing in this venue. In our experience, roughly 25% involve insufficient methodological rigor or missing validation evidence. In our experience, roughly 20% arise from a novelty claim that outpaces the supporting data.

• The Significance Statement that describes instead of translating. The Significance Statement is the single highest-leverage element in your PNAS submission. Editors read it before the abstract and use it as a triage tool to decide whether a non-specialist would care. We regularly flag statements that describe the study instead of explaining why the result changes something. "We identified a novel pathway linking X to Y" is description. "This finding overturns the assumption that X works by mechanism Y, with implications for therapeutic approaches to Z" is significance. The difference matters in the first 30 seconds of editorial screening.

• Cover letters that read like abstract remixes. PNAS editors want the cover letter to explain what the Significance Statement can't: why this paper belongs in a broad-science journal rather than a specialty venue, who the ideal reviewers would be, and any context about submission history. We've reviewed cover letters where 80% of the word count was a reworded abstract and zero words addressed the readership case. Since the 2022 reform eliminated the Contributed track, reviewer suggestions matter more than ever. PNAS asks for 3 to 6 qualified, non-collaborator reviewers spanning each relevant discipline. For interdisciplinary work, a reviewer list covering only one field is a red flag.

• Broad abstract, narrow results. The abstract claims cross-field significance, but every figure speaks in specialist shorthand. Editors recognize this mismatch within the first page. If the abstract says "implications for developmental biology, regenerative medicine, and synthetic biology" but all 4 figures are Western blots interpreted using terminology only a cell biologist would understand, the breadth case collapses. The strongest PNAS submissions we've seen have figure captions that a scientist one field away can parse without supplementary material.

SciRev community data author-reported review times provide additional community benchmarks when planning your submission timeline.

Verify format requirements against the journal's author guidelines before uploading.

Before you upload, run your manuscript through a PNAS framing and cover letter check to catch the issues editors filter for on first read.

Editors consistently screen submissions against these patterns before sending to peer review, so addressing them before upload reduces desk-rejection risk.

These are the specific manuscript patterns that generate desk rejections. Each is testable against your own paper.

Failure mode 1: The "almost complete" story. The central claim is exciting, but there's one obvious control experiment, validation, or comparison that reviewers would immediately demand. At PNAS, editors see this gap on first read and decline before review. Over 50% of submissions are rejected at initial evaluation. If you can predict the first reviewer criticism, fix it before submission.

Failure mode 2: Data not deposited before submission. PNAS requires all data to be in a public repository with accession numbers at the time of submission, not at acceptance. Manuscripts without accession numbers in the Methods section can be returned without review. This is a mechanical failure that wastes months.

Failure mode 3: The redirected specialist paper. The manuscript was written for a strong field journal (say, Journal of Neuroscience or JACS), then given a broader Significance Statement and submitted to PNAS. The results section still speaks in specialist shorthand while the Significance Statement speaks in general terms. This voice mismatch between the Significance Statement and the results is one of the fastest desk-rejection signals.

Failure mode 4: Reviewer suggestions that only cover one discipline. For interdisciplinary work, a reviewer list where all 6 names come from the same subfield tells editors the paper isn't as broadly relevant as the Significance Statement claims. PNAS explicitly asks for reviewers spanning each relevant discipline.

Standard report format:

• 6 pages maximum for a standard report (roughly 4,000 words, 50 references, 4 figures)
• 12 pages maximum total (for longer reports)
• 120-word Significance Statement (required, read before the abstract)
• ORCID required for the corresponding author
• CRediT author contributions required for all authors
• Data must be deposited in a public repository with accession numbers before submission

Significance Statement tips:

A strong Significance Statement does four things in 120 words:

• Explains what changed (the result, not the method)
• Explains why nearby scientists should care (the consequence, not the topic)
• Uses plain scientific language (not jargon-heavy repetition of the abstract)
• Avoids hype, vagueness, and field-specific terminology

If your Significance Statement still reads like a compressed abstract, the package is weaker than you think. Test it: give the Significance Statement to a scientist in an adjacent field and ask them what changed and why it matters. If they can't answer quickly, rewrite it.

The cover letter should do three things the Significance Statement can't:

• Argue venue fit. Why does this paper belong in PNAS specifically, not a specialty journal? Who in the PNAS readership benefits from this work?
• Suggest reviewers strategically. 3 to 6 qualified, non-collaborator reviewers spanning each relevant discipline. For interdisciplinary work, reviewers from multiple fields are necessary. A single-discipline reviewer list is a red flag.
• Provide submission context. If the paper was previously submitted elsewhere, briefly explain what changed. If there's a timing reason for PNAS (related work about to publish, policy relevance), mention it.

Don't repeat the abstract. Don't argue prestige. Don't write more than 400 words.

• Is PNAS a Good Journal?
• PNAS journal overview
• PNAS vs Science Advances
• Science Advances Submission Guide
• Before submitting, check if your paper is ready for PNAS.

1. Is PNAS a Good Journal?, Manusights.

Last verified against NAS author guidelines and Clarivate JCR 2024 (IF 9.1, 5-yr IF 10.3, JCI 2.91, Q1, rank 8/135 in Multidisciplinary Sciences).