Pre-Submission Review for Ecology and Evolution Papers: What Nature Ecology & Evolution Reviewers Expect

Reviewers at Nature Ecology & Evolution, Ecology Letters, and Proceedings of the Royal Society B move fast through an initial screen. In the first read they are testing:

• Whether the claim scope matches the data scope: the strongest sentence in the abstract is scaled to the actual spatial and temporal coverage, not to the principle the authors wish they had shown.

• Whether non-independence is modeled: pseudoreplication, spatial and temporal autocorrelation, repeated measures, and nested designs are handled with mixed models rather than analyzed as if all samples were independent.

• Whether the sampling design is adequate: replication, sample-size justification, environmental covariates, and seasonal/annual variation support the question being asked.

• Whether the comparative or phylogenetic logic is sound: phylogenetic signal, multiple trees or Bayesian posteriors, and appropriate comparative methods (PGLS, MCMCglmm) back any cross-species claim.

• Whether count and zero-inflated data are modeled correctly: overdispersion and zero-inflation are addressed so the statistical inference is reliable.

• Whether data and code are deposited: raw data in Dryad/Figshare, phylogenies in TreeBASE, and documented R/Python code, not "available on request."

• Whether the novelty claim survives the last 18 to 24 months of literature in the target journals and the focal system's subfield.

If two or more of these are unresolved, the paper is a desk-rejection or major-revision risk regardless of how hard-won the fieldwork is.

Across ecology and evolution manuscripts targeting Nature Ecology & Evolution, Ecology Letters, and Proceedings of the Royal Society B, the same failure patterns recur. Each names a manuscript component so you can test your own draft against it.

Local result framed as a broad field principle: The abstract and discussion scale a single-system, single-season finding into a general ecological or evolutionary claim. Reviewers immediately ask whether the replication depth and temporal window justify the framing, and the mismatch between claim scope and data scope is the most common desk-rejection trigger at the broad-significance tier.

Pseudoreplication and unmodeled non-independence: The methods analyze nested, repeated, or spatially autocorrelated samples as if independent, with no mixed model or autocorrelation structure. The statistics then overstate confidence, and reviewers discount every downstream inference until the design is re-modeled.

Comparative or phylogenetic scaffolding too fragile for the claim: A cross-species or selection claim rests on a single tree, no phylogenetic-uncertainty handling, or a comparative method that does not match the data type. For an evolution-leaning paper this is a predictable revision request.

Count data without overdispersion or zero-inflation handling: The results report a Poisson or naive model on overdispersed or zero-heavy count data, so the effect sizes and p-values in the figures are unreliable. Editors at the rigorous tier treat this as a methods-section gap that must be fixed before review.

Data and code transparency incomplete: The data-availability statement promises raw data "on request," the code is undocumented, or the deposited archive does not reproduce the figures. In a field with strong open-data norms this reads as reproducibility treated as optional, and trust drops fast.

Novelty overlap the authors did not pre-empt: A study published 8 to 12 months earlier covered a similar system or comparative question, and the manuscript does not explain why this finding is distinct and additive. This is the single most common avoidable desk-rejection trigger in a fast-moving subfield.

These patterns are why a scope-discipline and sampling-design check before submission is worth more than a faster light pass for this tier.

Public author guidance and reporting standards tell you what these journals enforce even before peer review. Use them as a checklist.

• Nature Ecology & Evolution requires the Nature Portfolio reporting summary: statistics, sample sizes, randomization where applicable, and code-availability disclosures at submission.

• Ecology Letters and Proceedings of the Royal Society B expect explicit statements of replication, non-independence handling, and a data-availability statement with an archive accession.

• Open-data norms apply across the field: Dryad or Figshare for ecological data, TreeBASE or Dryad for phylogenies, and documented analysis code in a citable archive (Zenodo).

• Cross-field reporting and ethics frameworks apply: ARRIVE for animal experiments, collection and CITES permits for field and protected-species work, and benefit-sharing documentation where relevant.

Method note: this page relies on public author guidance and our own anonymized pre-submission review patterns. It is not based on private editorial or reviewer access, and journals update author instructions, so verify current requirements against each journal's live author pages before submission.

For a productive ecology and evolution pre-submission review, send the full package, not just the manuscript:

• The full manuscript with figures and figure legends

• The target journal and any backup journals you are considering

• The sampling design, including replication structure and any nesting

• Underlying raw data, phylogenies, and the analysis code with documentation

• The data-availability statement and any permit or ethics approvals

• Any prior reviewer comments from an earlier submission

A review that is worth paying for ends with a clear instruction to submit, revise, retarget, or diagnose, plus the evidence for that call. Specifically it should deliver:

• A verdict on whether the manuscript clears the bar for the named target journal or a field-journal step-down

• The two or three reviewer objections most likely to appear, in reviewer language

• Component-level fixes: which claim to narrow, which model to re-fit, which figure, which abstract sentence

• A novelty assessment against recent literature in the target journals

• A scope-discipline call on whether the breadth claim matches the sampling design

• A journal-fit edit on title, abstract, and the first two introduction paragraphs

High-value feedback is specific and testable: it references exact claims, models, and likely reviewer comments, and each point changes the acceptance odds if fixed. Low-value feedback stays at writing-style level. For a fast first pass on an ecology manuscript, run a manuscript readiness check.

Use this page when the question is whether an ecology or evolution manuscript is ready for a specific top journal and what a review of it should cover.

Use the ecology submission guide when the question is the step-by-step submission mechanics, use how to choose a journal when the question is venue selection across the field, and use how pre-submission review works when the question is the general service across all fields.

Keeping each job on one page is what lets each rank for its own intent.

Target Nature Ecology & Evolution or Ecology Letters if:

• The finding establishes a principle relevant beyond the focal system

• The replication, temporal depth, and comparative logic genuinely support the broad claim

• You have a conceptual advance, not only a rigorous system-specific result

• The narrative is framed for breadth without overstating universality

Target Proceedings of the Royal Society B if:

• The biological insight is strong and evolutionary context is clear

• The work is broad enough for a general biology audience but not field-defining

Target Ecology, Evolution, or a specialist field journal if:

• The work is rigorous but system-specific without broader implications

• You need a faster decision or a venue whose readers value field-scale rigor

• The honest framing is a narrower claim that a broad-significance desk would reject

Ready to submit if

• the paper's strongest claim is scaled to the actual spatial and temporal coverage

• pseudoreplication, nesting, and covariates are handled explicitly

• code, raw data, and repository plans are ready before submission

Pause first if

• the manuscript is strongest as a rigorous system-specific study rather than a broad-significance piece

• the discussion still suggests universality where the evidence supports a narrower claim

• one missing season, site, or comparative control materially changes the breadth claim

For a manuscript-specific signal before you submit, run an ecology submission readiness check. Or see example reports before you finalize.

• Ecology and evolution teams choosing between a broad-significance venue and a rigorous field journal before first submission

• Authors who need an external check on claim-scope discipline, non-independence handling, and data transparency

• Labs trying to identify likely reviewer objections before upload