eLife Submission Guide

Source: eLife author guide, eLife submit page, accessed May 2026.

ELife editorial workflow at Elifesciences author instructions runs on the Publish-Review-Curate model. Editors screen for significance, methodology, and preprint-readiness in the first read.

Day 1-3: Receipt and tech-check

The eLife submission system confirms file integrity, the preprint identifier (bioRxiv / medRxiv / submitted preprint), the abstract (~150 words), the cover letter, author declarations, and the data + code availability statement. Submissions without a preprint posting (or commitment to post during submission) get a tech-return.

Day 3-14: Editor evaluation (no-cost screen)

A handling editor (often a Senior Editor) evaluates whether the manuscript fits eLife's significance threshold and methodological standards. If the editor commits to peer review, the $3,000 APC is charged at this point. If the editor declines review, no APC is charged and the preprint remains on bioRxiv / medRxiv.

Week 3-10: External peer review

Two or three referees report. eLife reviewers know their identities will be visible (signed reviews are encouraged; anonymized public reviews are the default). Reviewers and handling editor produce a consolidated eLife Assessment plus Public Reviews.

Week 10-14: Reviewed Preprint publication

ELife publishes the Reviewed Preprint within ~2 weeks of review completion. This includes the paper, the eLife Assessment (significance + strength of evidence), Public Reviews, and the author response if provided. There is no traditional accept/reject decision; every reviewed paper publishes as a Reviewed Preprint.

Week 14-30+: Author iteration + Version of Record

Authors choose whether to revise + respond. After substantial revision and a satisfactory eLife Assessment, authors can request a Version of Record. The Version of Record is the eLife-curated final version with updated Assessment.

Editors screen eLife uploads against the following artifacts at the submission system tech-check (Elifesciences author instructions). Missing the preprint identifier is the most common trigger for technical-return.

The required artifacts are the cover letter (with significance + scope framing and any prior-rejection history), the manuscript file in standard biological-sciences format (no fixed template), the preprint identifier (bioRxiv / medRxiv DOI;

eLife transfers from these venues directly), the abstract (~150 words, one paragraph), ORCID for the corresponding author (required), the author contributions statement (CRediT taxonomy encouraged), the conflicts of interest declaration, the funding statement and source listing, the data availability statement (open data required where possible), the code availability statement (where applicable), the ethics approval and consent statement (IRB / IACUC for human / animal work), the suggested reviewers (3-5 non-conflicted experts;

eLife uses these), and the supplementary information (extended methods, additional figures, datasets).

Most official and generic pages for "eLife submission guide" summarize the reviewed-preprint workflow or list author instructions. That is necessary, but it does not answer the author-risk question: whether a specific manuscript should enter a model where peer reviews and the editor assessment become public artifacts.

This guide translates eLife's model into editorial screen logic. Official publisher guidance cannot tell you whether the manuscript's missing controls would become damaging public review language, whether the data and code package is ready to be inspected, or whether the author team is aligned on publishing a visible eLife Assessment.

This page is about package readiness, not post-submission workflow.

Use it when you are still deciding:

• whether the manuscript is ready to be a preprint and a reviewed preprint

• whether the evidence is strong enough for a public assessment

• whether the data, code, and methods are open-science ready

• whether the authors are genuinely comfortable with the model

If you want the post-upload workflow and timing, that belongs on the submission-process page.

Many weak eLife submissions are not weak because of the science alone. They are weak because the team has not fully accepted what submitting to eLife means in practice.

The manuscript needs to be public as a preprint or ready to become one during submission. If the team still needs confidentiality, competitive delay, or private circulation before making the paper publicly accessible, that is already a fit problem regardless of how strong the science is. Preprint readiness is not optional at eLife; it is part of the submission standard.

The authors should also be able to tolerate public reviews, public criticism, and an eLife Assessment that may be less flattering than a private decision letter. If that feels unacceptable, the right answer is often another journal rather than hoping for a more favorable public outcome. Teams that submit to eLife expecting a conventional private review process are consistently surprised by how much the model differs from that expectation.

Before the formal submission starts, the package should already contain:

• a manuscript ready to exist publicly as a preprint

• evidence strong enough to survive a public "strength of evidence" assessment

• data, code, and methods that are genuinely transparent enough to inspect

• an author team aligned on the reviewed-preprint model

• a cover letter that explains why eLife is the right publication model

When those pieces are still unstable, the problem is not the portal. It is that the package is not ready for eLife yet.

ELife editors are not only asking whether the paper is good. They are asking:

• does the manuscript make a real contribution in the life sciences?

• is the evidence strong enough to justify public review?

• will the reviewed-preprint model help rather than hurt this paper?

• does the submission fit the journal's open-science posture?

That is why a technically strong paper can still be a weak eLife submission if the authors are not ready for the model itself.

The cover letter should do three things:

• state the scientific contribution plainly

• explain why eLife is the right audience and review model

• signal that the team understands the reviewed-preprint path

It should not sound like a conventional prestige pitch. That usually signals model mismatch.

The easiest mistake here is to treat eLife like a conventional journal with a slightly unusual workflow. That misses the real decision. A conventional submission can still succeed when the manuscript is promising but the authors expect the private review process to help stabilize the package. eLife works better when the package is already stable enough to stand in public.

That usually means an editor can see four things quickly.

The preprint version should already look like something the team is comfortable having colleagues, competitors, and future reviewers read as a finished public object. If the team still thinks of the paper as "almost ready" or is counting on the review process to help stabilize the package, eLife is usually the wrong choice at this stage. Papers that depend on private review to define what the missing experiments should be are better served by journals where that negotiation happens confidentially rather than in a public assessment attached to a preprint.

At eLife, the public record is not only whether the paper moved forward. It is also how the editors and reviewers describe the strength of evidence. That means vulnerability matters differently here. A paper with obvious missing controls, unstable statistics, or a methods section that still depends on informal lab knowledge can end up carrying that weakness visibly.

This is not just a box-checking issue. If the code, data, methods, and availability statements are weak or incomplete, the submission feels culturally mismatched with the journal even before anyone reads the science. eLife's core posture treats data and code availability as a baseline expectation, not an optional supplement. Editors assess whether the transparency posture is genuine before routing a submission for public review, and packages where open-science materials are clearly retrofitted or provisional are identified as premature regardless of the scientific quality of the findings themselves.

The corresponding author may be ready for transparent review while coauthors are not. That mismatch becomes a real submission problem later. Before submitting, make sure the whole team understands that the reviews, assessment, and preprint presence are part of the product rather than a temporary step on the way to a hidden decision.

Many borderline eLife submissions are really unresolved journal-choice decisions. The manuscript may be strong enough to publish, but the team is still choosing between transparent assessment and a more traditional private process.

This comparison matters because the wrong choice here creates a bad experience even when the science is good. The problem is not that eLife "rejected" the paper. The problem is that the authors asked the wrong publication model to solve the wrong problem.

The first page of a strong eLife submission usually feels calmer and more disciplined than authors expect. It does not rely on prestige language or dramatic framing. Instead, it makes the paper look ready for a public expert conversation.

That usually means:

• the abstract states the real contribution without overselling certainty

• the limitations are not hidden or apologized away

• the methods and availability posture look deliberate, not retrofitted

• the central claim is strong enough to survive visible criticism

If page one still depends on rhetorical momentum, the manuscript is often better suited to another route first.

• eLife Submission Process

• eLife Pre-Submission Checklist

• Is eLife a Good Journal?

• eLife journal overview

Before you submit, run your manuscript through a eLife submission readiness check to catch issues that will look worse once reviews are public.

ELife operates a fundamentally different editorial model:

The key difference: eLife doesn't reject papers after review. Instead, it publishes them with a public "eLife assessment" that rates the strength of evidence and significance of claims. This means getting into review is the hard part. Once reviewed, your paper gets published regardless of the outcome.

Choose eLife if:

• You want transparent, published peer review alongside your paper

• You're comfortable with public reviewer reports and an eLife Assessment rating

• Your paper is already on a preprint server (bioRxiv, medRxiv) or you're willing to post one

• You value the "publish then review" model, once accepted for review, the paper publishes regardless of outcome

• Speed matters: median time from submission to published Reviewed Preprint is ~91 days

Choose elsewhere if:

• You need a traditional JIF signal for career purposes (eLife was delisted from JCR in 2024 and no longer has a Clarivate IF)

• You're not comfortable with public reviewer reports attached to your paper

• The $3,000 APC is a barrier (though waivers are available for those who can't pay)

• Your institution or promotion committee doesn't recognize eLife's reviewed preprint model

A eLife submission readiness check can help you decide whether eLife's reviewed preprint model is right for your paper or whether a traditional journal submission serves your goals better.

The sources above define the mechanics; the harder question is whether this draft earns review. The review tells you whether your paper clears the eLife fit check before upload, especially around authors not ready for public reviews and visible eLife Assessment, evidence too fragile for public expert scrutiny at submission, and open-science materials incomplete at time of submission. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

For manuscripts targeting eLife, five patterns generate the most consistent submission problems worth knowing before committing to the reviewed-preprint model.

Authors not ready for public reviews and visible eLife Assessment

The eLife submission information positions eLife as a reviewed-preprint journal where reviews and the editorial assessment are published alongside the paper and are permanently part of the record.

Manusights pre-submission pattern analysis shows many teams discover after submission that public reviewer criticism and a visible strength-of-evidence assessment are harder to accept than they anticipated, particularly when the eLife Assessment characterizes the findings as "useful" or "solid" rather than "landmark." Editors specifically screen for teams that have genuinely accepted the model rather than treating it as a conventional private review with unusual branding.

Evidence too fragile for public expert scrutiny at submission

The same pattern analysis often finds many submissions contain methodological vulnerabilities, missing controls, or statistical fragility that would be manageable under private review but become part of the permanent public record when reviewers document them in eLife's public review model. In practice, editors consistently redirect manuscripts where obvious evidentiary gaps would generate public reviewer comments that would attach to the paper indefinitely, because eLife's model means reviewer criticism is a persistent feature of the published record rather than a private negotiation.

Open-science materials incomplete at time of submission

A related pattern is that many submissions arrive with code not yet deposited, data availability statements that are still provisional, or methods sections that rely on informal lab knowledge rather than reproducible documentation. Editors consistently screen for open-science readiness because the journal's core posture treats data and code availability as part of the submission standard, and our analysis of submission difficulties at eLife shows that retrofitting open-science materials after review is treated as an indicator that the submission was premature.

Check open science materials incomplete at time of submission before submitting to eLife →

Team submitting for prestige signal rather than model alignment

A related pattern is that many submissions treat eLife as a high-status traditional journal and frame the cover letter around impact and significance claims rather than explaining why transparent public assessment and the reviewed-preprint model are the right publication route for this specific paper. In our analysis of submission difficulties at eLife, this pattern is most common in groups where the corresponding author has accepted the model but coauthors still expect a conventional binary decision and are not prepared for the public record.

Check team submitting for prestige signal rather than model alignment before submitting to eLife →

Cover letter argues prestige rather than reviewed-preprint fit

A related pattern is that many submissions arrive with cover letters that describe the paper's importance and impact without explaining why eLife's specific model of transparent assessment and preprint publication serves the paper better than a conventional journal would. Editors explicitly consider whether the cover letter demonstrates genuine model alignment before routing the paper for public assessment.

SciRev author-reported review times and Clarivate JCR 2024 bibliometric data provide additional benchmarks when planning your submission timeline.

Before submitting to eLife, a eLife submission readiness check identifies whether your evidence package, open-science materials, and team alignment meet the standards for the reviewed-preprint model before you commit to the submission.

Check cover letter argues prestige rather than reviewed preprint fit before submitting to eLife →