PNAS Nexus 'Under Review': What the Status Means

The first PNAS Nexus status period is a file-and-scope checkpoint, not the full scientific review. The submission system can show movement because the record is technically handleable: files open, author details are present, disclosure fields are complete, data and funding statements are visible, and the manuscript appears within PNAS Nexus scope. A fast move to Under Review is therefore a routing signal. It does not prove that two reviewers have accepted, and it does not mean the handling editor has finished evaluating broad interdisciplinary fit.

During intake, the useful author action is to preserve a clean evidence record. Check that the submission-system metadata, cover letter, abstract, significance statement, figure order, data availability statement, and supplement describe the same contribution. For PNAS Nexus, a mismatch between broad-scope language and narrow technical evidence can create routing friction before peer review even begins.

For PNAS Nexus, the file package should make the manuscript has broad-science or cross-field value rather than a specialist result dressed in generalist language visible before a reviewer has to hunt for it.

At this point the manuscript is being read for fit. The editor is not only asking whether the manuscript is polished, but whether the manuscript has broad-science or cross-field value rather than a specialist result dressed in generalist language. In interdisciplinary science, emerging fields, health, biological sciences, physical and mathematical sciences, sustainability, engineering, social and political sciences, and cross-disciplinary methods, a manuscript can be technically competent and still difficult to route if the abstract promises one contribution while the methods, figures, or supplementary files support another.

The editor may be matching the manuscript to PNAS Nexus academic editors, broad-readership reviewers, disciplinary specialists, reproducibility reviewers, and methods or statistics readers. That matching process can take time because the editor needs reviewers who can evaluate the central claim without reconstructing the manuscript's logic from scratch. That single label can span both reviewer recruitment and active review.

At PNAS Nexus, the handling editor is usually making two decisions at once: whether the submission deserves outside assessment and which reviewer pool can test it fairly across fields. That editorial culture matters because a broad-scope journal can need domain reviewers, methods readers, statistics readers, and sometimes data or reproducibility judgment for one manuscript. Under Review is therefore best read as an editorial-routing state: the handling editor may still be testing scope, article type, evidence traceability, conflicts, and reviewer availability while the portal label looks static to the author.

Authors should prepare for comments on broad-readership title, significance statement, data and code plan, statistical detail, cross-field rationale, figure alt text, article-type fit, and reproducibility package while the handling editor is still shaping the review path.

In parallel, the PNAS Nexus editor may be looking for reviewers who can cover the manuscript's field claim and its evidence standard. A computational biology paper may need one reader for method validity and another for biological interpretation; a sustainability paper may need domain and policy-aware judgment; a physics or materials manuscript may need a reviewer who can audit both measurement and claimed application. Recruiting that mix can take 7 to 21 days, so Under Review can still include reviewer search rather than active reports.

For authors, the useful question is not "has someone accepted yet?" The useful question is "if a reviewer accepts today, would the manuscript's broad-readership title, significance statement, data and code plan, statistical detail, cross-field rationale, figure alt text, article-type fit, and reproducibility package make the claim easy to evaluate?" That is the difference between passive waiting and productive waiting.

This is the main period in which reviewers evaluate the manuscript. For PNAS Nexus, the review often turns on whether a neighboring discipline can audit the core claim without local shorthand. Reviewers are likely to check whether the conclusion follows from the methods, whether the strongest comparison or control is present, whether figures and tables support the stated claim, whether code or data access is credible, and whether limitations are proportional to the evidence.

Active review is the point where status anxiety has the least diagnostic value. A quiet submission-system record does not tell you whether one invited reviewer declined, one accepted reviewer is late, the handling editor is waiting for a second report, or reports are already being synthesized. The reliable response is to prepare material that will help under every plausible outcome: a revision map, a transfer plan, and a claim-boundary note.

For PNAS Nexus, use the waiting window to produce a reviewer-response map organized around the paper's interdisciplinary claim. Put the likely objection in one column, the exact manuscript location in another, the strongest supporting figure, table, dataset, or code file in a third, and the limitation language in a fourth. If the decision is revise, the map saves time. If the decision is reject or transfer, it clarifies which journal can fairly evaluate the next version.

After reports arrive, the PNAS Nexus handling editor has to convert reviewer comments into one decision. The portal can still show a label such as Under Review, Reviews Complete, or Decision in Process, depending on the stage. Silence in this window is not a rejection signal by itself. It can mean the editor is reconciling a methods-heavy review with a domain-heavy review, checking whether a reviewer misunderstood the interdisciplinary scope, or deciding whether another opinion is needed.

The synthesis window is where PNAS Nexus editorial judgment matters most. If one reviewer asks for a deeper reproducibility package while another asks for tighter broad-reader framing, the handling editor has to decide which request governs the revision. That delay is procedural evidence, not outcome evidence. Authors should avoid speculative rewrites until the decision letter names the actual dependency.

Not automatically. The most common explanation is reviewer recruitment or a delayed report, not a hidden rejection. The more useful reading is whether elapsed time matches the stage, and at PNAS Nexus active review runs roughly day 21 to 70. If the paper moved to Under Review quickly and then stayed there, the editor may still be waiting on one reviewer. If it changed after several weeks, the editor may be in synthesis, which at PNAS Nexus tends to fall around day 60 to 100. If there has been no movement past 10 weeks, a polite inquiry is reasonable.

What you should not do is rewrite the manuscript in panic or submit elsewhere. Prepare the response materials that will matter if the decision is revise, reject with comments, or transfer.

Source limitations: this page uses public official-source guidance plus Manusights manuscript-risk interpretation; it cannot see the private reviewer invitations, report status, or handling-editor notes inside your manuscript record.

Public PNAS Nexus guidance can tell you the portal, article-scope language, submission route, and broad peer-review policy. It cannot tell you whether your specific paper has reviewers assigned, whether a reviewer has missed a deadline, or whether the editor is leaning toward revision or rejection. That is why this page separates official-source facts from practical interpretation: the sources anchor the workflow; Manusights translates the status label into manuscript-level risk preparation.

• PNAS Nexus submission guide

• PNAS Nexus review time

• PNAS Nexus journal hub

• PNAS Nexus editorial-screen guide

• PNAS Nexus submission guide

Before you wait another month, run a PNAS Nexus reviewer-risk check and prepare the revision map reviewers are most likely to force you to build later.

The dashboard is a workflow signal, not a scientific verdict. Protect the manuscript from speculative edits while no concrete editorial evidence exists.

Source-specific notes:

• OUP guidance says PNAS Nexus is format-neutral at initial submission but still requires core manuscript, data, funding, and author information.

• The author page says PNAS Nexus does not consider manuscripts under consideration elsewhere.

• The guidance gives the editorial-office email for submission questions and describes statistical-analysis expectations.