PNAS Nexus Pre-Submission Checklist: 12 Evidence Checks
Before submitting to PNAS Nexus, verify 12 source-backed checks covering interdisciplinary fit, evidence, reproducibility, reporting, and package consistency.
Next step
Choose the next useful decision step first.
Use the guide or checklist that matches this page's intent before you ask for a manuscript-level diagnostic.
Quick answer: The PNAS Nexus pre-submission checklist below tests whether the manuscript presents a broad, reproducible contribution and whether its files, declarations, data, and cover letter support the same claim. Use it before upload because a technically complete submission can still fail editorial triage when scope, evidence, or reporting signals conflict.
Evidence basis: We reviewed the current PNAS Nexus author instructions and aims and scope on 2026-08-24. Official journal sources establish the documented requirements below. Manusights judgment converts them into a practical readiness sequence; it cannot predict an individual editorial decision.
- Check the evidence: the abstract, figures, methods, and data statement should support the same contribution.
- Check the action: repair a scope, reproducibility, reporting, or declaration conflict before upload.
- Hold submission when: the cover letter must explain away a gap that remains visible in the manuscript.
Each check is grounded in the current public author instructions. The page does not claim a private first-decision benchmark.
Run the PNAS Nexus pre-submission readiness check to score your manuscript against this checklist automatically, or work through the items manually below. Need broader cluster context? See the PNAS Nexus journal overview.
The Manusights PNAS Nexus readiness scan. Check whether the broad contribution, reproducibility record, declarations, and uploaded files support the same claim. The scan evaluates author-controlled evidence; it does not predict editorial triage.
The current instructions say initial submission is format-neutral, but required content still includes the manuscript, author and competing-interest information, data-sharing plans, and funding information. Research Reports prefer 6 pages and allow up to 12 pages; the current page describes 6 pages as approximately 4,000 words, 50 references, and 4 medium-size graphical elements. Verify the live article-type rules before upload.
What does the PNAS Nexus (NAS) pre submission checklist look like?
For PNAS Nexus-targeted manuscripts, the 12 items below organize into 5 verification groups tuned to PNAS Nexus's specific desk-screen patterns. Three items address scope and significance, calibrated to the broad-impact research signal that PNAS Nexus editors look for in the abstract and cover letter. Three items cover methods and data with PNAS Nexus's reviewer-pool expectations on protocol detail, repository deposits, and code availability. Two cover ethics and compliance against PNAS Nexus's declarations regime.
Two items address reference integrity. Two items cover submission-package framing, including figure accessibility and consistency with the selected article type. Each item is verifiable before you click submit through the current Oxford Academic route.
Scope and significance
- [ ] Scope-fit named in abstract. The abstract names broad-impact research within the first 100 words. PNAS Nexus editors triage on scope-fit at the abstract level; manuscripts that defer the contribution to the discussion section get desk-screened.
- [ ] Cover letter explicit on contribution. The cover letter explicitly addresses why this paper fits PNAS Nexus's editorial scope, not generic "we believe this work would be of interest." Editors at PNAS Nexus look for that fit signal in the first paragraph.
- [ ] Significance visible in title. The title makes the contribution visible without requiring specialist translation. Two-line titles with subordinate clauses signal scope-bounded papers, which PNAS Nexus editors triage out faster.
Methods and data
- [ ] Methods section reviewer-complete. PNAS Nexus reviewers expect protocol and reproducibility detail in the main text rather than supplementary materials. Manuscripts without explicit data-availability and code-availability statements extend editor review.
- [ ] Data-availability statement names a repository. "Available on request" is not accepted at most PNAS Nexus-tier journals. Use a repository with a DOI: Zenodo, Dryad, or a domain-specific equivalent, with the DOI active at submission time.
- [ ] Code-availability statement (where applicable). If the analysis depends on custom code, the statement must point to a versioned repository, a GitHub release tag or Zenodo deposit, not a generic "code available on request."
Ethics and compliance
- [ ] Ethics declarations complete for PNAS Nexus. IRB approval ID with institution name for human-subjects research at PNAS Nexus, animal-care protocol number for animal research, or explicit statement that the work does not require ethics approval. PNAS Nexus's editorial team returns manuscripts with generic "ethics approval was obtained" wording that lacks identifiers, particularly when the methods involve sensitive materials, biological samples, or any context that warrants explicit ethical oversight.
- [ ] Conflict-of-interest disclosure follows ICMJE. All authors complete the ICMJE COI form. Funder statements include grant numbers.
Citation cleanliness
- [ ] Reference list audited against Crossref + Retraction Watch. Citing a retracted paper without a retraction-notice acknowledgment is an automatic desk-screen flag.
- [ ] References reflect current state of the field. Reference list contains citations from the last 18 months covering the headline finding's most recent counter-evidence. PNAS Nexus reviewers frequently flag manuscripts that ignore work published after the project started.
Submission-package framing
- [ ] Any requested reviewer information is current and conflict-aware. Follow the live portal and journal instructions; do not rely on a copied quota from another journal.
- [ ] Figures and tables follow the current article-type constraints. Include editable tables, separate figure files, legends in the manuscript, and alt text as required by the current instructions.
Readiness check
Run the scan to check your manuscript against this list.
See your readiness score, top issues, and journal-fit signals in 1-2 minutes.
What manuscript requirements does PNAS Nexus enforce?
Requirement | PNAS Nexus expectation | What desk-screen flags |
|---|---|---|
Abstract and article length | 250-word abstract; article-type page limits apply | The selected article type and package disagree |
Methods placement | Reviewer-complete in main text | Methods deferred to supplementary materials extends review rounds |
Data availability | Repository DOI named | "Available on request" gets returned |
Reference list | Clean of retracted DOIs | Cited retractions get desk-screen flag |
Reviewer information | Follow the current portal request and conflict rules | A copied reviewer quota or conflicted suggestion is used |
Cover letter | Explicit scope-fit framing | Generic framing extends editorial-board consultation |
Source: current PNAS Nexus author instructions, checked 2026-08-24.
Desk-screen risks we see before submission
Use three evidence checks before submission:
Scope-fit ambiguity in the abstract. PNAS Nexus editors move fastest on manuscripts whose contribution is obviously aligned with the journal's editorial scope (broad-impact research). The named failure pattern: manuscripts without explicit data-availability and code-availability statements extend editor review. Check whether your abstract reads to PNAS Nexus's scope
Methods package incomplete. The current instructions require data-sharing plans and the information needed to evaluate the manuscript. Make the reproducibility record inspectable rather than assuming supplementary material will repair a thin main account. Check if your methods package is reviewer-complete
Reference record is unreliable. Verify corrections and retractions and explain any necessary citation of retracted work. Check citation integrity
Complete the checks in dependency order
- Confirm the journal and article type own the manuscript's reader job.
- Reconcile the title, abstract, significance statement, main figures, and conclusion.
- Finish the protocol, data, code, ethics, funding, and competing-interest record.
- Verify figures, tables, legends, alt text, references, and supplementary files.
- Open the current submission route and reconcile every portal field against the final files.
Do not estimate a universal completion time. A clean package can move through this sequence quickly; a missing repository deposit, ethics record, or cross-file correction needs the time required to fix it properly.
Build the reproducibility dependency chain
PNAS Nexus is format-neutral at initial submission, but format-neutral does not mean evidence-neutral. Before upload, connect each major claim to the artifact another researcher would need to inspect or reproduce it.
Claim type | Minimum supporting record | Question to answer before submission |
|---|---|---|
Experimental result | Protocol, exclusions, replicates, raw or processed data, and analysis code where applicable | Can a reader reconstruct how the reported number was produced? |
Computational result | Versioned code, environment, parameters, inputs, and seed or stochastic controls | Can the result be rerun without guessing hidden defaults? |
Dataset or resource | Provenance, consent or license limits, schema, quality checks, and access route | Can another group use it without violating the conditions? |
Cross-field conclusion | Definitions, units, uncertainty, and the bridge between disciplinary conventions | Will readers outside the home field interpret the evidence correctly? |
Do this before polishing the prose. If a central result has no inspectable record, fix the record before strengthening the novelty sentence. If a record cannot be shared, state the restriction and provide the most useful lawful access path.
Use the journal directory to compare PNAS Nexus with adjacent targets before locking the submission package.
Evidence basis: This checklist was checked against current PNAS Nexus author guidance and journal policies. The grouped readiness sequence is Manusights synthesis and cannot predict acceptance or an editorial outcome.
Submit If
- The headline finding fits PNAS Nexus (NAS)'s editorial scope (broad-impact research) and the abstract names that fit within the first 100 words.
- The methods section is detailed enough for PNAS Nexus reviewers to evaluate without follow-up; protocol and reproducibility detail are in the main text.
- All cited DOIs verified clean against Crossref + Retraction Watch.
- Any reviewer information requested by the live portal is current, relevant, and free of disallowed conflicts.
Think Twice If
- The methods section relies on a single subgroup analysis or post-hoc figure to carry the headline claim that PNAS Nexus reviewers will probe.
- The cover letter spends a paragraph on background before the new finding appears in the abstract; PNAS Nexus's editorial culture treats this as a scope-fit warning.
- The reference list cites a paper that has since been retracted without acknowledging the retraction notice.
- The protocol section relies on more than 3 figures of supplementary methodology that should be in the main text for PNAS Nexus's reviewer pool.
Frequently asked questions
It covers broad interdisciplinary fit, article type, manuscript length, significance statement, methods, data and code access, ethics, conflicts, figures, alt text, and package consistency.
There is no universal duration. A complete package may be checked quickly, while unresolved data, ethics, reporting, or cross-file conflicts require substantive repair.
The official author instructions provide the controlling submission requirements. This guide reorganizes those requirements into an author workflow and labels Manusights judgment separately.
Repair the named evidence or reporting gap before submission, or reconsider the journal if the paper's real audience is narrower than the proposed interdisciplinary audience.
Sources
- PNAS Nexus author instructions (checked 2026-08-24)
- PNAS Nexus aims and scope (checked 2026-08-24)
- Crossref retraction registry (retracted-DOI checks against the PNAS Nexus corpus, accessed 2026-05-08)
- Retraction Watch database (cross-checked PNAS Nexus retractions, accessed 2026-05-08)
- ICMJE recommendations (ethics + COI requirements, accessed 2026-05-08)
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Private API processing. Your manuscript is not used to train models.
Put the guidance to work
Turn the guide into a complete submission package.
Use one final checklist, then verify the journal rule that controls the files, declarations, and reporting details you will submit.
Where to go next
Same journal, next question
- PNAS Nexus Submission Guide: What to Prepare Before You Submit
- How to Avoid Desk Rejection at PNAS Nexus (2026)
- PNAS Nexus Impact Factor 2026: 4.8 (2025 JIF)
- PNAS Nexus Acceptance Rate: What the Journal Publishes
- PNAS Nexus Review Time: What Authors Can Actually Expect
- PNAS Nexus 'Under Review': What the Status Means