Analytic Methods in Accident Research Submission Process

This page was built from the current official ScienceDirect journal page, the AMAR Guide for Authors, the ScienceDirect Journal Insights page, and Manusights pre-submission review patterns for accident-methods, crash-frequency, injury-severity, transportation-safety, causal-inference, and econometric-method manuscripts. Last reviewed: July 17, 2026.

Official sources define the public workflow. ScienceDirect describes AMAR as a journal for the development and/or application of innovative statistical and econometric methods to vehicle crashes and other transportation and non-transportation accidents. The Guide for Authors states that submissions are initially assessed by editors for suitability and, if suitable, are typically sent to at least two reviewers under single-anonymized review. The same guide requires editable source files, a concise abstract of no more than 250 words, 1 to 7 keywords, highlights of 3 to 5 bullets with each bullet no more than 85 characters, data availability at submission, relevant declarations, and a complete submission checklist.

Source limitation: this guide does not inspect a private live AMAR submission session. It uses public official-source guidance and Manusights review experience to explain the process layer authors need to manage before and after upload.

AMAR's process is not mainly deciding whether the manuscript is polished. It is deciding whether the package deserves review as accident-methods work.

The editor is usually asking five questions:

• Does the manuscript develop or apply an innovative statistical or econometric method for accident research?
• Does the abstract make the reusable method visible before the applied safety result?
• Does the method solve a real accident-data problem, such as severity heterogeneity, rare events, exposure uncertainty, endogeneity, temporal instability, spatial correlation, or crash-frequency overdispersion?
• Does the validation package let a methodological reviewer judge the claim?
• Is AMAR the right venue, or is the paper actually a better fit for Accident Analysis & Prevention, Safety Science, Transportation Research Part C, Transportation Research Part F, Transportation Research Part B, or Transportation Science?

That is why this page is separate from a submission guide. The submission guide tells you what to prepare. The submission process tells you what the uploaded package is being tested against.

Do not treat the first submission screen as the start of the process. For AMAR, the process starts when the manuscript package becomes stable enough for a method-first editorial read.

Before upload, the title, abstract, cover letter, first figure, methods section, validation section, data statement, and supplementary files should all answer the same question: what reusable analytic move does this paper contribute to accident research?

If the package cannot pass that table, the submission process will expose the problem quickly.

The official ScienceDirect AMAR page links the submission route and Guide for Authors. The upload mechanics are standard Elsevier mechanics: manuscript metadata, author details, editable source files, figures, highlights, declarations, data statement, supplementary material, and final submission checklist.

The current AMAR Guide for Authors creates several process checks authors should handle before the last confirmation screen:

• source files should be editable, with Word files in .doc or .docx and LaTeX files in .tex
• the abstract should be concise, factual, and no more than 250 words
• keywords should be 1 to 7 indexing terms
• highlights should be a separate editable file with 3 to 5 bullets, each no more than 85 characters
• the data statement is required at submission
• research data should be deposited, cited, and linked when possible, or the manuscript should explain why data cannot be shared
• generative-AI use in manuscript preparation must be declared when relevant
• the submission checklist should confirm the corresponding author, full contact details, files, references, permissions, and open-access payment responsibility where applicable

These items are not just clerical. For AMAR, they signal whether the author can support a reusable method claim. A methods journal is more likely to notice missing data, unclear implementation detail, weak supplementary material, or an abstract that cannot explain the method under the word cap.

The initial quality check is where the package proves it is complete enough for an editor to read without operational friction. For AMAR, that check should not be reduced to "all files uploaded." A method paper depends on a coherent administrative and reproducibility package.

Before submission, confirm:

• authorship and CRediT contribution details are consistent across the manuscript and metadata
• competing interests and conflict of interest declarations are complete
• funding statements explain sponsor involvement or state that no specific funding supported the work
• ethics approval or data-source ethics language is included where accident, crash, injury, video, human-subject, or restricted administrative data require it
• data availability statement explains what can be shared, what is restricted, and how replication can be evaluated
• supplementary material contains code, pseudocode, robustness tables, sensitivity checks, or implementation detail where the method claim needs it
• the final submission checklist matches the manuscript files, figures, highlights, permissions, and corresponding-author details

This stage is where an otherwise strong AMAR paper often loses force. If the data statement is generic, the supplement is thin, and the highlights summarize only applied findings, the paper enters editorial triage looking less like reusable accident-methods work.

After upload, the editor first decides whether the manuscript belongs in AMAR. Elsevier's public process describes an initial editor assessment for suitability before review. For AMAR, suitability means more than "about crashes" or "uses a model."

The editorial screen usually separates four manuscript types:

The cover letter should not try to hide this routing question. It should state why AMAR is the correct process owner: the paper contributes a method that changes how accident researchers estimate, validate, interpret, or generalize accident evidence.

AMAR follows single-anonymized review, often called single-blind peer review: reviewers can see author identities, but authors do not see reviewer identities. Elsevier's Guide for Authors says suitable submissions are typically sent to at least two reviewers for independent expert assessment of scientific quality.

For AMAR, reviewer routing usually needs two kinds of expertise:

• a methodological reader who can judge the statistical, econometric, causal, machine-learning, spatial, temporal, or crash-modeling contribution
• an accident-research reader who can judge whether the method matters for crashes, injury severity, transportation safety, construction safety, or another unintended-harm setting

If the paper is too methodological without accident-data necessity, one reviewer may see it as misplaced statistics. If it is too applied without method novelty, another reviewer may see it as misplaced Accident Analysis & Prevention work. The strongest AMAR package makes both readers unnecessary to guess.

The final decision is where AMAR's method-first bar becomes explicit. A major revision usually means the editor sees a possible AMAR paper but needs reviewers' concerns answered in the evidence package, not just in prose. A rejection after review usually means the manuscript reached the right kind of scrutiny but failed method novelty, validation, accident-data necessity, or reproducibility.

For complex or delayed edge cases, expect the decision to turn on the slowest part of the proof: reviewer recruitment for the right methodology, access to restricted accident data, simulation recovery, out-of-sample validation, or whether the method can transfer beyond one local crash dataset. That is why a 34-day decision-after-review indicator should be treated as a journal-level signal, not a promise for every complex paper.

ScienceDirect currently lists these AMAR publishing timeline indicators:

Use those numbers carefully. A 1-day first-decision figure can reflect rapid editorial decisions across the journal, including quick suitability decisions. It does not guarantee your manuscript will receive a substantive reviewer decision in one day. A 34-day decision-after-review figure suggests a relatively fast review cycle when the paper reaches review, but reviewer availability, method complexity, data restrictions, and revision depth still matter.

The practical interpretation:

• an early decision usually means the fit or package-readiness signal was clear
• a longer quiet period after the initial screen often means reviewer invitation or report collection
• complex or delayed edge cases can run 45 to 90 days when reviewer recruitment, restricted data, simulation checks, or extra validation slow the process
• a decision after review will focus less on upload mechanics and more on method novelty, validation, benchmark comparison, accident-data necessity, and reproducibility
• a revision request is not just a writing task if reviewers question validation or method transfer

In our pre-submission review work with Analytic Methods in Accident Research manuscripts, the most useful process signal appears before the author opens the submission system. The editor will see the title, abstract, highlights, cover letter, first figures, methods structure, data statement, and supplement as one package. If those components do not tell the same method-first story, the process becomes fragile.

Manusights submission analysis treats these as specific failure patterns, not generic writing advice. Our internal analysis of AMAR-bound packages looks across the abstract, first figure, cover letter, methods, validation, data availability statement, supplementary material, and target-journal rationale to see whether one editorial triage pattern dominates before upload.

Applied finding wearing AMAR language. The manuscript says it is about a method, but the abstract and figures mostly show crash-risk findings, injury-severity correlates, or policy implications. The method may be competent, but it behaves like a tool used to answer an applied safety question. We usually recommend rewriting for Accident Analysis & Prevention or another applied safety venue unless the authors can make the reusable method genuinely central.

Check whether your abstract and first figure make the AMAR method contribution visible →

Complex model without accident-data necessity. The paper uses Bayesian modeling, random parameters, latent classes, spatial econometrics, causal inference, extreme-value modeling, or machine learning, but the manuscript never explains why accident data require that move. AMAR reviewers need to know what the method solves: rare events, exposure uncertainty, temporal instability, crash-severity dependence, reporting bias, unobserved heterogeneity, endogeneity, or policy-counterfactual instability.

Check if your methods section proves accident-data necessity →

Validation package too thin for a methods journal. AMAR process risk often sits in figures and supplements, not in prose. A paper can describe a promising method but still lack out-of-sample validation, simulation recovery, benchmark comparison, sensitivity analysis, code detail, or a replication path. When this is the issue, submitting faster usually does not help. The next journal will see the same weakness.

Check whether your validation package is strong enough for AMAR peer review →

Routing confusion across transportation and safety venues. Some AMAR-bound papers are strong but aimed at the wrong reader. Transportation Research Part C may own technology-system evidence. Safety Science may own risk and organizational safety. Transportation Research Part F may own road-user behavior. Transportation Research Part B or Transportation Science may own broader transportation methodology. The AMAR process is easiest when the manuscript's owner is clear.

The strongest submissions make the method claim auditable before review. The abstract names the accident-data problem. The cover letter explains why AMAR's methods audience is the right audience. The first figure shows why the method matters. The validation section proves the method does more than fit one dataset. The data statement and supplement tell reviewers how much of the method can be inspected or reused.

That is the practical AMAR submission-process test: can a busy editor see, in the first package read, that this is accident-methods work rather than an applied safety paper with advanced modeling?

This guide tells you what AMAR editors look for in the process; the review tells you whether YOUR paper passes that process before upload. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

Check whether your AMAR package is ready for the submission process →

• Analytic Methods in Accident Research journal overview
• Analytic Methods in Accident Research submission guide
• Analytic Methods in Accident Research impact factor
• Analytic Methods in Accident Research under review
• Rejected from Analytic Methods in Accident Research? Where to submit next