Written and maintained by CASRAI Editorial Board
Published
On this page
Management Science submission guidelines cover the manuscript, ScholarOne submission and research disclosures. For studies covered by its data policy, prepare an AsCollected project at submission and plan the replication package needed at acceptance. These are separate requirements: a provenance record does not replace reproducible research files.
Ask CASRAI · free to tryQuestion about this guide? Ask CASRAI answers with linked sources. 2 free questions a day, no account.
What the Management Science submission guidelines cover
The guidelines apply to the INFORMS journal Management Science. Its editorial statement describes a journal concerned with understanding management through rigorous research, including theoretical, experimental and empirical contributions. It welcomes work across disciplinary boundaries while requiring relevance to management and interest beyond a narrow specialist audience.
INFORMS’ general author guidance makes journal fit the first submission decision. Read the editorial statement and published papers before preparing the submission. The title and abstract should identify the problem and findings concretely; the introduction and conclusion should communicate with a broader research audience. A technically competent analysis still needs a clearly explained contribution.
For an author, the practical task is to connect three things: the managerial problem, the evidence supporting the contribution and the materials that allow others to understand how the results were produced. A submission checklist organized around those three things is more useful than treating formatting as the entire preparation process.
Who runs the journal and what it covers
Management Science is published by INFORMS, the Institute for Operations Research and the Management Sciences. The journal’s editorial statement covers management in firms, public institutions and other organizational settings. Its departmental statements include accounting, finance, information systems, operations management, organizations, strategy and other areas.
Department selection should follow the paper’s contribution. A dataset involving a business does not, by itself, establish the relevant department: explain what the research changes in the understanding of the managerial problem. The departmental statements supply the journal’s own descriptions of the work each department seeks.
INFORMS also recommends examining the style and methodological character of articles in the intended outlet. This helps separate a contribution that belongs in a broad management journal from one developed primarily for a different specialist readership. The original data table below organizes the documents needed at different stages, drawing together the submission, provenance and replication policies.
How to submit through ScholarOne
The journal documents these seven ScholarOne stages. Use the Management Science submission link on its official guidelines page.
- Type, Title & Abstract: choose the department; keep the abstract within 250 words.
- File Upload: upload anonymous manuscript files without a title page.
- Attributes: provide three to five keywords.
- Authors & Institutions: enter every author and affiliation, including the submitting author’s ORCID iD.
- Reviewers & Editors: suggest five reviewers and three associate editors without conflicts.
- Details & Comments: provide the cover letter, disclosures and department-editor preference.
- Review & Submit: inspect the generated PDF and select Submit.
Manuscript format and anonymity
Use at least 1.5 spacing, 11-point type and one-inch margins. Initial regular submissions have no fixed page ceiling, but excessive length can lead to rejection. Invited revisions allow 47 pages at 25 lines per page or 32 pages at 33 lines per page; an online appendix is excluded. Remove author names, institutions and acknowledgments from the review manuscript.
The ethics policy describes double-anonymous peer review: reviewers do not receive author identities, while the editorial team knows them. Anonymity therefore concerns what reviewers see, rather than an instruction to withhold author information from the journal.
ORCID describes its iD as a persistent researcher identifier linked to a record of contributions and affiliations. Its purpose is reliable identification across disciplines and institutions. An identifier and a manuscript’s anonymous presentation serve different purposes; supplying an ORCID through the submission system does not mean placing identifying information in the review file.
Prepare the AsCollected disclosure
The journal’s AsCollected instructions cover submissions using data, code, experiments, surveys, simulations or observational datasets. Prepare the manuscript title, author details, data sources, collection or acquisition information, cleaning and analysis details, and contributor roles.
Create the project, select the applicable research designs and complete the questions for each datasource. The options include lab data, online studies, field experiments, private data, public data and code-only projects. Multiple categories can apply. Complete the author-roles table and inspect the project summary for missing studies or sources.
ScholarOne needs the editable URL for the specific project, not the AsCollected homepage, a login page or a listing of projects. The instructions describe a seven-character project code with an underscore in the fourth position. An incorrect URL can cause the submission to be returned. The project remains editable after submission and does not replace the acceptance-stage replication package.
Establish data rights and provenance
The Data Provenance Policy requires authors to have the right to use their data and publish the resulting research. Required corporate or other permissions must be obtained before submission. Public visibility alone does not settle whether data may be used for the proposed research.
The policy also distinguishes harm caused by obtaining data from an unwelcome finding produced through analysis. Its discussion of online data collection addresses material harm from collection practices, while its treatment of originally stolen or hacked data requires explicit permission for research use. These are the journal’s publication conditions, rather than a general legal determination about a particular dataset.
A practical implication is to keep the permission question separate from the replication question. Documenting how a file was acquired is part of research data provenance; explaining how another researcher can repeat an analysis addresses a different part of the submission package.
Plan replication and restricted-data disclosure
The Code and Data Disclosure Policy requires authors to explain their intended disclosure approach at submission. For accepted numerical or computational work, the materials needed to replicate the essential results must be supplied before production. This includes empirical studies, experiments, simulations and numerical algorithm tests.
Licensed datasets need access instructions and the authors’ own code. Restricted or sensitive data can require an alternative plan, such as a transformed dataset, a subset, synthetic data or documentation enabling comparable data to be constructed. These possibilities are subject to editorial assessment; an author cannot declare an exception approved merely because access is difficult.
The Department Editor evaluates acceptability with the relevant data editor and editor-in-chief. The policy’s purpose is reproducibility of the central research contribution. Describe the restriction and the proposed means of supporting replication together, so the disclosure plan addresses the actual research rather than offering only a statement that the data are confidential.
Acceptance-stage replication package checks
The journal’s replication checklist translates disclosure into concrete files. It distinguishes compulsory items from strongly encouraged items, so preserve that distinction when using the original form.
Its checks cover code and data for results, instructions for obtaining public or commercial data, a readme, software and package versions, and data dictionaries. Code should use relative paths and include the commands needed to load data. A master script should execute the analysis in order, and the code should run without errors on another computer.
Study-specific checks include experimental instructions and questionnaires, survey materials and computational test problems. The form also covers logs, intermediate processing and final packaging. Use the checklist itself to determine which entries apply to the study and which are encouraged rather than compulsory.
For the research team, this creates an earlier planning question: who can explain and rerun the path from the supplied inputs to each reported result? Assigning that responsibility before files are assembled helps make the later technical checks concrete.
Confirm ethics, overlap and author approval
The journal’s ethics guidelines require accurate reporting, appropriate citation and disclosure of overlapping work. Concurrent submission of the same manuscript to multiple journals is prohibited. Related work must be acknowledged, with an explanation of the new contribution.
The submitting author must ensure that appropriate coauthors are included and that all coauthors have reviewed and approved the final manuscript and agreed to submission. Financial support and relevant conflicts must be disclosed. Generative AI tools cannot be authors; human authors remain responsible for the accuracy, originality and integrity of the work.
These requirements connect the author list to the substance of the paper. A contributor record, an authorship decision and approval of the submitted version should therefore agree. They are different checks, each addressing a different responsibility in the publication process.
Strengths and limits of the submission process
The policies make several expectations explicit: editorial fit, documented research provenance, identifiable contributor responsibilities and a replication plan. Their practical value is that authors can identify preparation tasks before the submission reaches editorial assessment.
The limits are equally specific. A completed provenance form cannot establish that an analysis reproduces; an executable analysis cannot establish that data permissions exist. The journal assesses alternative disclosure plans, so documenting a restriction is part of the discussion rather than an automatic exemption.
The official Submission Fee FAQ describes a fee for original submissions and exemption or waiver routes, including membership, eligible country affiliations and an honor-based option for authors unable to pay. Invited revisions are excluded. The FAQ states that ability to pay is not visible to the review team and does not influence editorial decisions. The official schedule and waiver policy govern the payment step.
Alternatives when the journal scope differs
These INFORMS journals publish their own scope and submission rules. The table compares their stated research focus, rather than predicting acceptance or recommending simultaneous submissions.
| Journal | Stated focus | Submission distinction |
|---|---|---|
| Information Systems Research | Theoretically grounded research on significant information systems phenomena. | Research Articles, Research Commentaries and Research Notes have distinct purposes. |
| Organization Science | Organizations and their processes, structures, technologies, identities and people. | Its own transparency compliance and conflict-of-interest requirements apply. |
| Operations Research | Analytical methods that advance decision-making. | Focused Technical, Context and Challenge, Regular and Lengthy submissions follow different specifications. |
Information Systems Research asks authors to identify their intended audience and ground the contribution in theory. Organization Science describes a portfolio spanning several disciplines concerned with organizations. Operations Research emphasizes advancement of analytical decision methods. Compare those statements with the central contribution before adapting the paper to another outlet’s formatting rules.
Worked example: an empirical manuscript with restricted data
Illustrative composite: a fictional team has analyzed a company dataset and written a management research manuscript. One collaborator obtained the records, another prepared the analysis files and a third checked the results. The company agreement restricts redistribution.
A useful preparation exercise is to place four items side by side: the permission record, the datasource description, the contributor record and the proposed replication materials. The permission record answers whether the team may use the records and publish the findings. The datasource description explains where the inputs came from. The contributor record identifies responsibility for the work. The proposed package shows what a reader could use to examine the analysis.
The team can then identify the unresolved decision precisely: its restriction requires a disclosure proposal for editorial consideration. Completing an AsCollected project would document the project, while testing the analysis would evaluate execution. Neither action, by itself, resolves permission or approves the alternative plan. This separation keeps the submission documents consistent without implying that a particular restricted-data proposal will be accepted.
Sources
- INFORMS: Management Science Submission Guidelines, checked 2026-11-17.
- INFORMS: Management Science Editorial Statement, checked 2026-11-17.
- INFORMS: General Submission Guidelines, checked 2026-11-17.
- INFORMS: Code and Data Disclosure Policy, checked 2026-11-17.
- INFORMS: AsCollected.org Author Instructions, checked 2026-11-17.
- INFORMS: Management Science Data Provenance Policy, checked 2026-11-17.
- INFORMS: Code and Data Replication Package Checklist, checked 2026-11-17.
- INFORMS: Guidelines for Ethical Behavior in Publishing, checked 2026-11-17.
- INFORMS: Submission Fee FAQ, checked 2026-11-17.
- ORCID: About ORCID, checked 2026-11-17.
- INFORMS: Information Systems Research Submission Guidelines, checked 2026-11-17.
- INFORMS: Organization Science Submission Guidelines, checked 2026-11-17.
- INFORMS: Operations Research Submission Guidelines, checked 2026-11-17.
Data: Management Science submission and replication documents
Original compilation matching journal preparation documents to their stage and function, assembled from the official submission guidelines, AsCollected instructions, data provenance policy and replication checklist.
Period covered: 2026-11-17.
| Document or record | Stage | Function | Policy source |
|---|---|---|---|
| Anonymous manuscript | Initial submission | Research narrative for review; omit the title page. | Management Science Submission Guidelines |
| AsCollected project | Initial submission for work covered by the data policy | Research provenance and contributor documentation; supply the editable project URL. | AsCollected.org Author Instructions |
| Required data permissions | Before submission | Establish rights to use the data and publish the research results. | Management Science Data Provenance Policy |
| Replication package | Acceptance, before production for applicable numerical or computational work | Supply data, code and sufficient information to reproduce the essential research results. | Code and Data Disclosure Policy |
| Replication checklist | Final manuscript files | Record applicable checks for the package, readme, code and study materials. | Code and Data Replication Package Checklist |
Sources
- INFORMS: Management Science Submission Guidelines (accessed 2026-11-17)
- INFORMS: Code and Data Disclosure Policy (accessed 2026-11-17)
- INFORMS: AsCollected.org Author Instructions (accessed 2026-11-17)
- INFORMS: Management Science Data Provenance Policy (accessed 2026-11-17)
- INFORMS: Code and Data Replication Package Checklist (accessed 2026-11-17)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







