Is Your Paper Ready for Geophysical Research Letters? A Pre-Submission Readiness Check

These are the current, public limits and policies that bear on readiness. Confirm them on AGU's text and graphics requirements before you submit, since the unit budget, summary rules, and data policy all carry exact wording you should match.

Source: AGU text and graphics requirements, AGU author resources, AGU FAIR data and software sharing guidance, and the AGU / Wiley publication-charge schedule (accessed June 2026). Verify the live publication charge and the exact unit definition before submitting, since AGU updates both.

The headline that matters for readiness: the desk decision is fast, but the bar is real. The journal returns over-length manuscripts for shortening before review, and AGU's data and software policy states plainly that "data available from the authors" is not an acceptable availability statement. Treat both the unit limit and the repository deposit as gating, not as polish.

GRL's editors triage fast, against length and significance, before any reviewer sees the paper. Each named failure pattern below maps to a specific editorial triage pattern, and editors consistently flag manuscripts for these before review begins. In our analysis of these submissions, the same five returns recur, and we see this hold across subfields from atmospheric science to space physics.

A full JGR-length study compressed into a letter. The most common fast return. The science is strong, but it needs the methods detail, the secondary analyses, and the figure count of a JGR article, and squeezing it under 12 units leaves a reviewer unable to judge the central claim. This is a venue fix, not a data fix, and it is the first thing to test against your own manuscript.

Over the 12-publication-unit limit. A literal length return. Authors who run (words / 500) + figures + tables and land at 13 or 14 units, or who forget that captions and appendices count, get the paper sent back for shortening before editorial review even starts.

A result with no broad significance. A careful regional case study, a single-site observation, or a model intercomparison whose conclusion never leaves the subfield. The abstract describes the result entirely in local terms and the plain-language summary never answers why anyone outside the niche should care.

A non-compliant data and software availability statement. "Data available from the authors," a statement that points to no repository, or software that is not accessible to reviewers at submission. AGU is explicit that the first of these is not acceptable, and editors flag it at the administrative stage.

A buried headline. An abstract that opens with three sentences of background, or a plain-language summary that reads like a textbook paragraph, so the editor cannot see the high-impact result in the first ten seconds of triage.

Walk each manuscript component before you submit. The order below mirrors what a GRL editor reads first.

Key points and plain-language summary. The three key points and the plain-language summary are where breadth is won or lost. State the single high-impact result and its cross-disciplinary stake in plain terms. If a non-specialist editor cannot see why the result matters from these alone, the paper is not ready.

Title and abstract. The abstract is short, around 150 words, and counts toward the unit budget. Lead with the result, not the background. The title should name the broad finding, not the regional setting.

Methods. Summarize enough for a reviewer to judge the result, and push the full protocol, validation, and sensitivity analyses into supporting information. Methods that demand full JGR length in the main text are the clearest signal you are at the wrong venue.

Figures and tables. The lead figure must carry the headline result and be legible to a non-specialist. Every main figure and table costs one publication unit, so budget them deliberately. A story that lives in the supplementary figures reads as unclear.

Data and software availability. Deposit the data and any central software in a trusted, domain-appropriate repository, cite each in the reference list with a persistent identifier and a license, and confirm reviewers can access both at submission. This is gating, not polish.

References and supporting information. References should be recent and support the broad claim. Supporting information is where the JGR-length detail belongs, so use it to keep the main text under budget without starving reviewers of evidence.

If you want a manuscript-specific signal across all of these components before you submit, run a free readiness scan.

If the readiness check says the paper is sound but not a GRL fit, route it deliberately rather than dropping a tier and blasting it out.

For a paper rejected on length or fit, the AGU transfer path between GRL and the JGR sections is often the route of least resistance: it carries your files and any reviews to a sister journal without a full re-review. Accept a transfer only when the suggested journal genuinely fits your study type, not just because it is convenient.

In our pre-submission review work with Geophysical Research Letters manuscripts, four readiness gaps separate papers that clear the fast triage from those that come back within days. In our analysis of these submissions, these four account for the overwhelming majority of fast returns, and they are a specific failure pattern set you can test against your own draft. Three of the four are fixable before you submit, and recognizing which one applies to your paper is the difference between a clean submission and a wasted return cycle.

This page is built from two things: AGU's own published policies (the text and graphics requirements, the FAIR data and software guidance, and the journal's aims and scope), and the editorial triage patterns we see across the GRL manuscripts we review before submission. Where a claim is a hard rule, it comes from AGU's documentation; where it is a judgment call, it comes from our review work.

The format gap: a JGR-length study wearing a letter format. This is the readiness failure we see most often in GRL submissions. The science is strong and complete, but it needs the methods detail and figure count of a JGR article, and the authors have crammed it under 12 publication units by thinning the methods until a reviewer cannot judge the central result.

The tell is consistent: the main text references a methods section that does most of its work in supporting information, and the figure budget is already spent before the headline result appears. The fix is not new data. It is either restructuring around one result that genuinely fits the letter format, or honestly accepting that a JGR section is the right home.

Across the GRL manuscripts we review, this single venue decision changes more desk outcomes than any other intervention.

The significance gap: a careful result with no broad takeaway. GRL is selective for breadth, and editors want a single high-impact result that a neighboring discipline would act on, not a thorough regional study or a confirmation in a new dataset. We repeatedly see methodologically clean manuscripts that are not ready because the abstract and plain-language summary describe the result entirely in subfield terms.

This is the one readiness gap that reformatting alone does not close at a broad-significance letter journal. The right call is a domain journal or Earth and Space Science, where soundness and useful data are the bar, rather than rewording the same narrow result for the same kind of editor.

The data-policy gap: an availability statement the FAIR rules reject. The quick desk decision is not a light one. We routinely flag manuscripts that are scientifically ready but procedurally not: an availability statement that says "data available from the authors," a dataset with no repository deposit and no persistent identifier, central analysis software that is not accessible to reviewers at submission, or a missing software citation in the reference list.

AGU's FAIR data and software guidance states explicitly that the first of these is unacceptable, and every reputable geoscience journal now expects a real repository deposit, so closing this gap before submission protects the paper wherever it goes next.

The headline gap: a buried result in the key points and summary. GRL editors decide fast, and they read the three key points, the abstract, and the plain-language summary first. The weakest manuscripts we see open with background, state the result in subfield jargon, and never answer the only triage question that matters: why would a geoscientist outside this niche want this result now?

A summary that says "we present new observations of process X in region Y" is not ready; one that says "this is the first evidence that X reshapes a process shared across atmospheres, oceans, and the solid Earth" is. Same study, different framing, different desk outcome.

The practical takeaway: the format, data-policy, and headline gaps are readiness fixes you make before submitting. The significance gap is a signal to change the target journal, not to keep arguing the same narrow result to the same editor. Our internal analysis of these submissions points to the same conclusion every time: at GRL, length discipline and broad-significance framing decide more desk outcomes than raw study quality.

With an estimated acceptance near 35% and a gold open-access share around 79% per LetPub, the journal is both selective and broadly read, so a fast return on a fixable format problem is an expensive one to absorb.

Before you commit, a Geophysical Research Letters scope and readiness check tests your manuscript against these exact gaps, so you find them before a desk editor does.