Academy of Management Perspectives Submission Process

Before upload, run an Academy of Management Perspectives process check to test whether the file package, article type, AI disclosure, abstract, evidence display, and practitioner-facing claim are aligned. This page owns the after-target-choice workflow.

The mistake is treating AMP as a softer version of a research-first AOM journal. AMP is selective in a different way. The process checks whether the paper is built for evidence-based management practice and policy from the first screen, not whether an AMJ, AMR, AMD, or Annals manuscript can add a manager-facing paragraph at the end.

The AMP process is smoother when four questions have already been answered.

If those answers are weak, ScholarOne will not fix them. AOM's process can collect the fields, but AMP editors still read the package as evidence of whether the authors understand the journal's relevant, rigorous, and readable standard.

Prepare the package before starting the online form. AMP's process has enough journal-specific checks that generic business-journal habits create avoidable risk.

You should have:

• Microsoft Word manuscript file with title page and author-identifying references removed
• cover letter that includes acknowledgements, fit rationale, and AI-use disclosure when relevant
• article-type choice: Standard Article, Constructive Confrontation, Practitioner Perspective, or Book Brief
• abstract of no more than 200 words that helps readers decide whether the article is relevant to them
• title and keywords that point to a management-practice or policy issue, not only a theory gap
• tables, figures, examples, and evidence displays that are readable to non-specialized readers
• disclosure plan for conflicts, funding, human-subjects or organizational-data constraints, and AI use
• supplementary files, instruments, data notes, or appendices that support the evidence base without turning the main paper into a technical report
• proposal record or proposal discipline for Practitioner Perspectives and Constructive Confrontations when applicable
• source file and final PDF preview checked for author identifiers, file corruption, and inconsistent metadata

This is not only administration. AOM says each journal has specific submission guidelines and workflows to check ethical and procedural requirements. For AMP, the practical problem is that a technically complete record can still look misrouted if the article type, abstract, and evidence path do not match the journal's mission.

AMP submissions start at https://mc.manuscriptcentral.com/amp. AOM's author resources send authors to the journal-specific ScholarOne site and describe the core preparation sequence.

The practical upload sequence is:

1. prepare the anonymized Microsoft Word manuscript
2. prepare the cover letter and acknowledgements
3. access the AMP ScholarOne site
4. enter submission information, article type, title, abstract, keywords, and author details
5. complete disclosure and AI-use fields
6. upload manuscript, cover letter, figures, tables, and supporting files
7. review the generated submission record
8. complete final submit and save the confirmation record

Do not treat the review-and-submit step as optional. A partially complete ScholarOne record is not a submitted manuscript. Before final submit, check that the paper in the preview is the anonymized version, the cover letter has the right AMP-specific disclosures, and the article type is not forcing the editor to guess whether this is a Standard Article, Constructive Confrontation, Practitioner Perspective, or Book Brief.

Use these as planning ranges, not promises. AOM publishes submission requirements, article-type guidance, AI policy, and the ScholarOne route, but it does not publish a guaranteed manuscript-level decision clock.

For planning, use a first decision range of 4 to 5 months for manuscripts sent into full review, with complex article-type fit, specialized practitioner reviewers, cross-disciplinary evidence, or ambiguous AMP versus AMJ or AMR routing creating delayed edge cases. Papers that fail the early fit screen can move faster.

The first check is not the full editorial verdict. It is whether the record can be handled without forcing the office or editor to reconstruct the submission.

For AMP, intake should be treated as an authorship, conflict of interest, ethics statement, AI-disclosure, data availability statement, anonymization, plagiarism screen, and file-integrity check.

Common intake delays:

• manuscript submitted as the wrong file type or with broken formatting
• author names, acknowledgements, institutional identifiers, or self-citation language remain in the anonymized file
• cover letter omits acknowledgements or the fit rationale
• AI use is not disclosed in the cover letter and acknowledgements when AI tools were used
• article type is selected mechanically even though the manuscript's shape points elsewhere
• Practitioner Perspectives or Constructive Confrontations are submitted without proposal discipline
• supplementary files are missing, unclear, or inconsistent with the main evidence claim
• conflict, funding, human-subjects, or organizational-data issues are not clear enough for handling

Fix these before upload. Administrative friction is not fatal, but at AMP it makes an editor read a weaker package before reaching the question the article is supposed to help managers, educators, executives, consultants, or policy makers answer.

Once the package is complete, the editor tests whether the paper is actually an AMP paper. AOM's AMP pages define the fit test as relevant, rigorous, and readable. They also warn authors not to paste managerial implications onto a standard academic article.

The editor usually sees the title, abstract, article type, cover letter, opening section, evidence display, and author disclosures before reading deeply. The question is not "is this a polished management paper?" It is "does this paper organize rigorous evidence around an issue of management practice or policy that AMP readers can use?"

Strong process signals:

• the abstract names the management-practice or policy issue before the theory gap
• the article type matches the paper's actual evidence and audience
• the cover letter explains why AMP is the intended reader, not a backup destination
• evidence displays are readable to non-specialized readers without losing rigor
• AI-use reporting, acknowledgements, conflicts, and data constraints are clear
• the opening section frames a decision, misconception, policy problem, or practice debate

Weak process signals:

• the manuscript reads like AMJ, AMR, AMD, or Annals until the final implications section
• the article type is chosen because of page length rather than editorial purpose
• the proposal route is ignored for Practitioner Perspectives or Constructive Confrontations
• the evidence base sounds like consulting advice without scholarly grounding
• AI use is disclosed vaguely or only after the editor asks

This is why the submission-process page is separate from the submission-guide page. The guide helps decide whether AMP is the target. The process page explains what the uploaded package must survive once that target choice becomes a ScholarOne record.

AMP triage is a package, article-type, audience, and evidence-bridge screen. Manuscripts that look strong for research-first AOM journals can leave the process early when the uploaded record makes practitioner relevance look late, decorative, or unsupported.

Methodology note: this page was created from official AOM, AMP, ScholarOne, and AOM AI-policy source checks, sibling-page overlap checks, and Manusights pre-submission reviews of management manuscripts. We evaluate the same components an editor sees early: title, abstract, article type, cover letter, anonymized file, evidence display, disclosures, AI-use statement, and supplementary files.

The manuscript is AMJ-shaped with an AMP label. The abstract opens with theory, hypotheses, constructs, or method, and the practical issue appears after the results. The upload may be technically complete, but the process record tells the editor that AMP is being used as a fallback rather than the intended audience.

Check whether your AMP abstract and article type match before upload →.

The Practitioner Perspectives path skips the proposal discipline. AOM strongly encourages intended Practitioner Perspectives coauthors to submit a proposal before the full essay. Skipping that step can make the submission look under-tested, especially when the practitioner problem is real but the scholarly bridge is not yet precise.

Check whether your Practitioner Perspectives proposal is ready →.

The AI-use disclosure is treated as a confession instead of reporting. AOM requires authors to identify AI use by research stage and confirm that they reviewed, verified, and accepted AI-involved output. The weak version is a vague "AI was used for editing" sentence that does not say where or how it was checked.

Check whether your AMP AI-use disclosure is specific enough →.

The evidence chain is not visible in the upload package. AMP does not publish opinion pieces. If the title, abstract, tables, examples, and supplementary files do not make the evidence base visible, the paper can sound useful but unsupported. That is a process problem because it appears before peer review.

Our analysis of AMP submission packages treats triage as a document-level test. The component that fails first is usually visible before review: article type, abstract, cover letter, evidence display, proposal record, AI disclosure, or anonymization discipline.

The practical pattern is specific to AMP. A paper can be good management scholarship and still enter the process weakly if the uploaded package makes the editor reconstruct why this is evidence-based management practice or policy work rather than a research-first AOM submission.

We also inspect whether the cover letter names the right reader. The useful line is not "this paper contributes to the literature." It is the management decision, policy question, educator problem, executive misconception, or practitioner debate that the evidence helps resolve. If that line is unavailable, the process is already weaker because the manuscript has not selected its AMP audience.

The reviewer-count expectation should stay flexible. AOM publishes article-type and review-policy guidance, but it does not promise a fixed reviewer count or guaranteed timing path for every manuscript. This guide tells you what AMP editors look for before reviewer routing; the review tells you whether YOUR paper passes that process screen. A paid Manusights review applies the same process split before submission: article type, evidence bridge, practitioner audience, AI disclosure, anonymization, and reviewer-risk checks. Paid reviews include the 60-day money-back guarantee, and Manusights does not train models on submitted manuscripts. We do not train on submitted manuscripts.

If the manuscript clears the editor screen, it can move toward external review. AMP's public materials distinguish peer-review handling by article type. Constructive Confrontations are described as double-blind peer reviewed and written without identifying coauthors. Practitioner Perspectives cannot be fully masked and are single-blind peer reviewed. Standard Articles should be prepared anonymously for the ScholarOne process.

Reviewer assignment can slow when:

• the paper needs both a management scholar and a senior practitioner reader
• the article sits between strategy, organizational behavior, entrepreneurship, policy, leadership, or human resources
• the evidence base uses qualitative cases, organizational data, interviews, field evidence, or synthesis across literatures
• the article type is not clear from the abstract and opening section
• AI-use, organizational-data, ethics, or conflict disclosures need interpretation

Once reviewers agree, they usually test whether the evidence is rigorous enough for AOM, whether the practice or policy issue is central enough for AMP, and whether the writing is readable without becoming a trade-press essay.

The first decision is usually a routing or revision decision, not a clean accept. The useful question is whether the decision points to package-level fixes, article-type fit, or evidence gaps.

The strongest revision response does not only answer comments. It shows that the manuscript now makes the evidence-to-practice bridge easier to evaluate than the submitted version did.

The author-controlled time saver is not a status email. It is a clean ScholarOne record, an anonymized file, a precise article type, a specific AI-use disclosure, and an abstract that makes AMP's management-practice reader visible before review.

Submit to AMP when:

• the manuscript is evidence-based management practice or policy work, not only a standard academic article
• the abstract is no more than 200 words and helps readers judge relevance quickly
• the Word file is anonymized and free of author-identifying references
• the article type is obvious from the title, abstract, cover letter, and structure
• the cover letter handles acknowledgements, fit, AI-use disclosure, conflicts, and unusual circumstances
• Practitioner Perspectives or Constructive Confrontations have proposal discipline when applicable
• tables, figures, examples, and supplementary files make the evidence chain visible
• the ScholarOne preview matches the final intended submission

Source limitations: AOM's official pages define the AMP article types, ScholarOne route, submission requirements, AI policy, and broad review expectations, but they do not show a private handling-editor view of any individual manuscript. Official guidance is useful for rules, but thin on the combined process question: how ScholarOne fields, anonymization, AI disclosure, article type, evidence display, and practitioner-audience framing interact before review.

That gap is the reason this page is process-focused. It does not replace the official AOM instructions. It turns the public rules into an author-side sequence and names the specific failure patterns Manusights sees before AMP reviewers are invited.