Ocean Engineering Submission Guide: How to Submit to OE (Elsevier)

Ocean Engineering publishes research papers, review articles, short communications, and technical notes. The format you choose drives how reviewers weigh completeness against length.

Research papers have no single fixed word cap. Length is governed by completeness and clarity rather than a hard limit, which means an over-long paper is judged on whether every section earns its space. A manuscript that runs well past 8,000 words because the contribution is buried under repeated background is judged harshly even though no rule was technically broken.

There is no hard ceiling on figure count either, but a paper that needs more than 12 figures to make its case usually signals that the main story is not yet clear; each artwork file should be supplied at the resolution Elsevier specifies and kept under the portal's per-file size guidance of roughly 10 MB.

Highlights are required as a separate editable file and must consist of 3 to 5 bullet points, each a maximum of 85 characters including spaces. They should capture the novel result and any new method, not restate the abstract.

A graphical abstract is encouraged but optional, submitted as a separate file at a minimum of 531 by 1328 pixels. Generative-AI artwork is not permitted for it.

For declarations, you must include a data availability statement, a declaration of competing interests, CRediT author contributions, and ORCID iDs. A cover letter is accepted and useful for flagging scope fit and suggested reviewers, but it cannot substitute for an abstract that already makes the ocean-engineering application clear. Elsevier provides a LaTeX template (elsarticle) and accepts standard manuscript formats.

Before the format and declarations are locked, an Ocean Engineering validation and scope readiness check can confirm whether the validation evidence and application framing genuinely clear the bar, or whether the work needs more before it is submitted.

Ocean Engineering assigns submissions to a handling Editor who manages them through Editorial Manager. Community-reported data puts the first review round in a wide band, with about 2.7 reports per submission and around 2.3 review rounds before a final decision. Treat the stages below as planning ranges, not commitments.

• Day 0: Submission and PDF build. Editorial Manager ingests your files and builds a PDF. You proof it, confirm the data availability statement, competing-interests declaration, CRediT contributions, and highlights, and submit.

• Days 1 to 7: Editorial screening. Editorial staff and the handling Editor check scope fit against the journal's explicit inclusion and exclusion lists, application relevance, completeness, and language quality.

The fastest returns happen in this window: out-of-scope topics, purely theoretical work, and manuscripts with no marine application rarely reach external review.

• Days 7 to 21: Reviewer assignment. The handling Editor decides whether to send the manuscript out and invites reviewers in the relevant ocean, coastal, offshore, or naval-architecture area.

CFD papers with no validation and incremental parameter studies are commonly returned at this stage rather than burdening reviewers.

• Days 21 to 140: Peer review. Reviewers return reports, typically two to three, on a multi-week cadence.

SciRev community data points to a first round that can land near a month when reviewers are secured quickly, but several months when they are not, which is the single largest source of timeline variance at this journal.

• Days 60 to 150: Decision and revision. Reject, major revision, minor revision, or accept. A revised manuscript must be accompanied by a response letter addressing each reviewer point.

Most papers that survive review go through at least one major-revision round, which is why round count averages above two.

• Days 180 to 210: Final decision and production. Total handling time for accepted manuscripts commonly runs to roughly six to seven months from submission, with faster outcomes for clean, well-validated papers and slower ones for multi-round studies with contested validation.

In our pre-submission review work with Ocean Engineering submissions, four patterns generate the most consistent early returns. None of them are about the analysis being wrong. They are about application relevance, validation, and contribution shape that this journal screens for before peer review begins.

In our review of marine and offshore engineering manuscripts, each of these is a named rejection pattern you can check your own draft against, and each reflects an editorial triage pattern specific to how handling Editors at this journal read submissions. The journal's explicit scope and exclusion lists raise the stakes on every one of these, because the editor has a written basis to return work that does not fit.

Editors consistently screen for these before sending a manuscript out for review.

Ocean Engineering's guide for authors and Elsevier's author resources define the mechanics below; the patterns describe how manuscripts coming through pre-submission review for this journal most often fall short of them. SciRev community data on this journal, where authors report a first round that varies from about a month to several months and around 2.7 reports per submission, is consistent with what we see: a large share of attrition happens at the editorial screen, before reviewers ever weigh in, and these four patterns are why.

CFD or numerical work presented with no experimental or field validation. A large share of Ocean Engineering submissions are computational studies of wave loads, hydrodynamics, mooring dynamics, or offshore-structure response. The single most common stall we see on numerical manuscripts is a results section that reports forces, motions, pressure fields, or spectra entirely from simulation, with no experimental comparison, no field measurement, and no validation against an established benchmark or model-test dataset.

The figures look complete, but a handling Editor in ocean engineering reads them and asks the obvious question: how do I know this CFD result reflects a real sea state rather than a well-tuned solver? When the manuscript has no grid-convergence study, no validation case, and no comparison to physical data, the credibility gap is visible immediately.

Ocean Engineering expects numerical work to be anchored to physical reality, and manuscripts that treat the simulation as self-validating are a leading reason computational papers are returned before external review.

Check whether your Ocean Engineering CFD results show experimental or field validation →

Incremental parameter studies with no new mechanism or design insight. The parallel failure on otherwise-competent work is the one-variable sweep. The paper takes a known configuration, a fixed mooring layout, a standard hull, an established turbine model, and reports how one output changes as a single input is varied across a range.

The methods are sound and the figures are clean, but reviewers in this field treat a parameter sweep as a starting point, not a contribution. When the discussion offers no new mechanism, no design rule, and no insight that transfers beyond the specific case studied, the manuscript reads as a routine application of existing methods.

The fix is to state, in the introduction, what general lesson the study delivers that a reader could not have predicted from the underlying model, and to make sure the results section actually earns that claim.

Check if your Ocean Engineering manuscript delivers a transferable design insight →

Scope drift into pure fluid mechanics or pure naval architecture. Ocean Engineering sits at the intersection of several disciplines, and a recurring desk return is a manuscript that has drifted to one edge of that intersection. On one side, the work is really a fundamental fluid-mechanics study, a vortex-dynamics or turbulence-modeling result that happens to use a marine geometry but whose contribution would be evaluated more naturally at a fluid-mechanics journal.

On the other side, the work is a naval-architecture or ship-design study with no advance in ocean-engineering method or understanding. In both cases the marine setting is the context, not the subject. Handling Editors at this journal identify quickly when the real contribution belongs to a neighbor field, and a manuscript whose advance lacks genuine ocean, coastal, or offshore engineering relevance is consistently flagged as a scope mismatch before review.

Check whether your Ocean Engineering manuscript stays in scope or has drifted →

No real-sea-state relevance, or an explicitly out-of-scope topic. The journal maintains a written exclusion list, and a steady stream of submissions are returned because the topic is named on it: marine engines and auxiliary systems, pumps and valves, sediment transport and erosion, chloride penetration, dam-break phenomena, and purely military or dual-use work.

Beyond the named exclusions, the broader pattern is work with no connection to realistic ocean conditions, an idealized study run only in still water or under loads that no real sea state would impose, presented as though it informs marine engineering practice. The introduction frames the work as ocean engineering, but the conditions modeled have no bearing on how a structure, vessel, or device would actually behave at sea.

A manuscript whose results cannot be tied back to a realistic marine, coastal, or offshore scenario is identified as out of scope regardless of its technical quality.

This guide tells you what Ocean Engineering editors look for; a Manusights review tells you whether YOUR paper passes that screen. A Manusights review checks the validation evidence, the contribution shape, the scope framing, and the real-sea-state relevance against the editorial bar this journal applies before peer review. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

Before submitting, an Ocean Engineering validation and scope readiness check tests whether your validation evidence, contribution, and application framing clear the editorial bar this journal applies before peer review.

This guide was built from the Ocean Engineering guide for authors, Elsevier author resources, the Editorial Manager submission system, and Manusights pre-submission review patterns from marine and offshore engineering manuscripts. We checked the scope and exclusion lists, the highlights format, the single-anonymized review model, and the declarations against the journal's own pages, and we cross-checked review-timing ranges against SciRev community data and Clarivate JCR 2024 metrics. The failure patterns describe what we see most often when ocean-engineering manuscripts come through pre-submission review for this journal.

Use this page before you upload, when the official instructions cannot answer the real question: whether your validation evidence, contribution, scope framing, and real-sea-state relevance are already defensible. Source limitation: Elsevier updates format details, charges, and policies after this review date, so confirm administrative specifics against the journal's official pages before submission. To pressure-test the manuscript itself, run a manuscript readiness check.

• Applied Thermal Engineering submission guide
• Composites Part B Engineering submission guide
• For the broader cluster, see the engineering journals overview.

Before you upload, run your manuscript through an Ocean Engineering submission package check to catch the scope, validation, and contribution issues editors filter for on first read. The check is free to run (/ai-review) and takes a single upload.