Academy of Management Annals Under Review: What the Status Means

Three Annals-specific patterns deserve attention while the journal controls the timeline. They test corpus boundaries, synthesis logic, and theoretical consequence without treating a portal label as evidence of reviewer sentiment.

Annals pattern 1: the corpus boundary is invisible

Explain databases or discovery routes, terms, dates, disciplines, inclusion logic, and treatment of influential work outside the formal corpus. A narrative synthesis still needs a defensible evidence boundary. Readers should know what could change the conclusion if it were added.

Annals pattern 2: coverage substitutes for integration

Organize literature around mechanisms, tensions, boundary conditions, methods, or competing explanations rather than one paragraph per paper. A useful table compares constructs, assumptions, evidence, limitations, and unresolved conflict. Citation volume alone does not create a theoretical contribution.

Annals pattern 3: the agenda is detached from the synthesis

Each proposed question should follow from an identified contradiction, missing population, measurement limit, theoretical boundary, or evidence gap. Remove generic calls for longitudinal, cross-cultural, or multi-method research unless the synthesis shows why that design resolves a named uncertainty.

Build a control table with reviewer question, synthesis claim, evidence for, evidence against, affected section or figure, and current limitation. Check whether the abstract and conclusion state the same theory change. Reconcile citations, appendices, author details, acknowledgments, conflicts, and any proposal commitments across the record.

Add influential exceptions to the evidence table rather than hiding them in limitations. Explain whether disagreement comes from population, level of analysis, operationalization, design, period, or theory. A useful Annals manuscript tells readers when a conclusion should change, not only which conclusion appears most often.

Then audit the visual argument. Every framework figure should encode a relationship the synthesis actually established, not merely arrange familiar constructs. Every evidence table should expose comparison, boundary, or contradiction rather than function as an expanded reference list. If the same conclusion would survive after removing the table or figure, the artifact may be decorative.

Finally, check the proposal-to-manuscript trace when a proposal preceded the article. Record how the final corpus, structure, theoretical focus, or contribution changed and why. A defensible evolution is stronger than silently drifting away from the approved reader job. Preserve scope decisions, excluded literatures, and terminology choices so a reviewer can understand the synthesis boundary.

Pay special attention to level of analysis. Individual, team, organizational, institutional, and field-level evidence cannot be combined without an explicit bridge. Mark where a mechanism is observed directly, inferred from patterns, or proposed for future testing. That distinction makes the theoretical consequence more credible and makes a later response easier to verify.

Assign every synthesis claim a traceable support path: included studies, coding or comparison rule, contradictory evidence, boundary condition, and the section where the inference is explained. Then ask a coauthor who did not draft that section to reconstruct the claim from the table alone. If they reach a different conclusion, the manuscript is relying on tacit judgment that reviewers cannot audit. Record the disagreement and either make the rule explicit, narrow the claim, or show why multiple interpretations remain theoretically useful.

• An editor-stated or official expectation is materially exceeded.
• All proposal or manuscript tasks are complete.
• The message identifies the record and asks whether authors need to act.

In our analysis of the observable Annals record, the useful split is between a dated editorial event and a synthesis decision the authors control. We map the latter to the proposal, concept figure, evidence table, and manuscript section without predicting a private review outcome.

Academy of Management Annals has a synthesis job, so the useful record is more than a portal timeline. Save the accepted proposal or editorial framing, the manuscript outline, the corpus and inclusion boundaries, major terminology decisions, and every change requested by the journal. Then check whether the current manuscript still delivers the promised field map. Drift can occur when authors add literature during drafting but do not update the organizing question.

If the review is narrative rather than systematic, explain how sources were selected and how influential exceptions were handled. Transparency does not require pretending the process was a meta-analysis.

Read the manuscript by section function. Each major section should compare, judge, reconcile, or reorganize evidence. A section that merely lists studies needs a stronger synthesis move. Check whether the paper distinguishes a disagreement in terminology from a disagreement in mechanism, and whether apparent consensus is supported across settings and methods.

Then test the figures and tables. A conceptual figure should make a relationship easier to see, not decorate the same prose. A literature table should expose variation or boundary conditions, not become a compressed bibliography. If a research-agenda item cannot name a mechanism and an evidence route, it is probably too generic.

The portal does not reveal whether reviewers agree, whether the editor is leaning positive, or how the decision will resolve. Keep those unknowns outside the plan.

Follow an editor-stated or official expectation when one exists. If materially exceeded, send one concise inquiry with record ID, title, relevant date, and a question about whether anything is needed from the authors. Silence is not evidence of a negative decision.