Rejected from Production and Operations Management? Where to Submit Next

Diagnose the POM rejection before selecting another journal.

POM uses double-blind review and a department-editor structure, but the important post-rejection fact is procedural: its author instructions require disclosure of prior related work and prior POM rejection history. They also state that a rejected paper may not be resubmitted to a different POM department unless the decision explicitly allows a revised resubmission. Treat that as a closed-route check, not a tactical formatting detail.

An editorial rejection can reflect department fit, visible contribution, or a weak first-page account of the operational decision. A post-review rejection exposes evidence, model, data, or interpretation concerns that another editor can see as well. An invited resubmission is conditional, not acceptance. In all cases, keep one active evaluation path at a time.

The revised paper should make this chain inspectable: managerial decision -> operational mechanism -> model or empirical design -> identification or validation -> result -> boundary condition -> decision consequence. Mark each link as measured, identified, modeled, stress-tested, inferred, or missing.

This chain prevents a common rerouting error: moving from POM to a neighboring venue while keeping a claim that assumes a general operational effect without a generalizable mechanism. The next journal may be narrower, but it still needs an evidence-to-decision connection its readers can evaluate.

1. Title and abstract: name the operational decision and demonstrated contribution, not only the setting or method.
2. Introduction: explain the managerial problem, what existing work cannot decide, and the specific mechanism under test.
3. Related work: distinguish shared data, shared constructs, and the new paper's contribution from every close predecessor.
4. Model or empirical design: expose assumptions, observation unit, timing, selection, counterfactual, and the alternative explanation the design addresses.
5. Evidence: report robustness, sensitivity, missingness, model fit, and failure cases proportionately to the claim.
6. Tables and figures: make denominators, units, scenarios, baselines, uncertainty, and decision consequences independently readable.
7. E-companion: place supporting proofs, extended tables, and supplementary analyses there only after the main paper remains auditable on its own.
8. Discussion: separate the observed result from the proposed mechanism and from the managerial action it can justify.
9. Destination cover letter: disclose the prior evaluation when required, state the substantive repairs, and explain the new reader fit.

Audit the revised POM manuscript before resubmission.

Before selecting a destination, classify the revised manuscript by the evidence it can carry. An analytical paper needs a decision model, assumptions that matter to that decision, a result that survives meaningful sensitivity analysis, and a boundary on where the result applies. An empirical paper needs a credible unit of observation, timing, comparison, identification argument, and a clear separation between association and a decision recommendation. A behavioral or field study needs the operational actor, decision context, measurement logic, and a result that is not merely a general management observation. A design-science or applied paper needs a usable artifact or method, a transparent benchmark, and validation tied to an operations consequence.

This classification is not a way to lower the contribution standard. It is a way to stop asking a destination journal to infer a contribution that the manuscript never demonstrates. Rewrite one sentence in the abstract for the selected type: "We model the decision under [constraint] and show [conditional result]"; "Using [design], we estimate [effect] for [decision] under [boundary]"; or "We evaluate [method] against [benchmark] for [operational outcome]." Then test whether the first figure, first result, and conclusion substantiate that sentence. If they do not, repair the evidence or choose a narrower claim before choosing the journal.

Appeal only when a factual or procedural error could change the decision. Do not appeal to relitigate a contribution, novelty, department-fit, or editorial judgment disagreement.

Resubmit to POM only when the decision letter explicitly permits it and the revision satisfies that path. Start fresh when the reader decision or contribution changed. Do not submit to another POM department after rejection unless the letter permits it, and never make a simultaneous submission.

In our pre-submission review work with Production and Operations Management manuscripts, we look for the point where a technically competent paper stops being an operations-management contribution. We test the abstract, model or empirical design, related-work disclosure, tables, e-companion, and conclusion as one argument. The patterns below are Manusights repair observations, not POM rejection statistics.

The managerial problem is broad but the operational decision is not named

We see this when an introduction says that a setting is important but never identifies the allocation, inventory, capacity, sourcing, service, scheduling, pricing, or policy decision that the evidence changes. We compare the abstract, first figure, methods, and conclusion. A repaired paper names the decision, the mechanism, the relevant constraint, and the condition under which the result applies.

A contribution is claimed before related work is separated

We inspect the related-work section, cover letter, data disclosures, and robustness tables for overlap in data, setting, construct, or result. A Production and Operations Management claim of novelty cannot survive if readers cannot see how the current manuscript differs from the closest papers. The repair is an explicit contribution ledger, not a longer citation list.

The model result is treated as a managerial prescription

We compare the model assumptions, calibration or identification, sensitivity analysis, baselines, tables, and discussion against the action the paper recommends. When the evidence supports a conditional result, the conclusion needs a conditional decision rule. That boundary often identifies the next journal more accurately than a journal-tier comparison.

The e-companion carries the evidence that the main paper needs

We check whether a reader can evaluate the operational mechanism, key assumptions, primary results, and decision consequence without opening a separate file. If a robustness check or proof is essential to the central claim, the main text must signpost and summarize its role. Moving evidence out of sight is not a contribution repair.

Choose the next journal only when the revised manuscript can state its managerial decision -> operational mechanism -> design -> validation -> boundary -> consequence without an unsupported jump. Recheck the live scope, article type, and disclosure rules before upload.

We checked POM's current author instructions, the current SAGE journal page, the Manusights owner inventory, and live exact-query results on July 13, 2026. Official sources establish the double-blind, page-limit, disclosure, and resubmission boundaries. The repair ledger, evidence chain, and routing matrix are Manusights analysis.

The POM cluster recorded two 90-day preview starts in the portfolio baseline. That is a product-intent proxy, not proof of exact rejected-from query demand. Read final Search Console data after 14 complete days; at 21 days, keep, revise, consolidate, or stop this owner.