Jom Review Process

---
name: jom-review-process
description: Use when understanding how Journal of Operations Management (JOM) evaluates submissions — the Department-routed structure, the asymmetric double-anonymous review, the Empirical Research Methods method check, and how to read a JOM decision letter before or after submitting.
---

# Understanding JOM Review (jom-review-process)

## When to trigger

- You want to know what happens to a manuscript after submission
- You received a JOM decision letter and need to interpret it
- You are unsure who sees your identity and who evaluates the operations contribution
- You want to anticipate the method check before submitting

## The Department-routed pipeline

JOM is organized into **12 Departments**, each with its own Department Editors and mission. Your submission is routed to a Department (you named two, one preferred). The Department Editor oversees evaluation within that Department's conversation, typically assigning an Associate Editor who manages reviewers from the Editorial Review Board (ERB) and elsewhere. This is analogous to, but distinct from, INFORMS-style departmental area-editor routing.

## Asymmetric double-anonymous review

Review is double-anonymous, with a specific asymmetry: **author identities are shared with the Editors-in-Chief and Department Editors but not with reviewers or Associate Editors** (and author-blind to those parties; vice versa). Keep the manuscript fully anonymized — reviewers and AEs must not be able to infer you.

## The Empirical Research Methods method check

JOM has a dedicated **Empirical Research Methods Department** that not only publishes methods papers but **performs method checks on incoming empirical submissions**. Expect scrutiny of sampling, measurement, identification, common-method remedies, and reproducibility — an institutionalized methods gate not found at generic top management journals. Weak identification or unvalidated measures can stall a paper here regardless of how interesting the phenomenon is.

## Likely decisions

- **Desk reject / return** — out of scope (e.g., a purely analytical/optimization model), operations not at the heart, over-length, missing checklist, or method too weak to send out.
- **Reject** — fundamental theory, design, or contribution problems.
- **Major revision (R&R)** — promising; substantial empirical/theoretical work required. The norm for papers that progress; first-round acceptance is essentially unheard of.
- **Minor revision** — close to acceptable.
- **Accept** — after one or more developmental rounds.

## Reading the letter

Separate the Department Editor/AE's framing (the decisive priorities) from individual reviewer comments. Identify which concerns are about the **operations contribution**, which are **method-check** issues (often non-negotiable), and which are presentational. Method-check and identification concerns usually must be fully resolved; some reviewer suggestions can be argued.

## Output format

```
【Stage】routed to Department ... / under AE / decision received
【Who sees identity】EICs + Department Editors (not reviewers/AEs)
【Method-check exposure】sampling / measures / identification / reproducibility ...
【Decision read】desk / reject / major-R&R / minor / accept
【Decisive vs. arguable comments】...
【Next step】jom-rebuttal (if R&R)
```