Journal of Management Information Systems Submission Guide
A source-checked JMIS guide for testing organizational information-systems fit, theory and practice value, evidence, and submission readiness.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
This guide is one part of a 3-source submission path.
The Journal Submission Source Map separates the official pages that resolve Scope & fit, Review model & anonymity, and Package requirements for Journal of Management Information Systems.
Journal overview
- Journal home and scope
- Resolves: Scope & fit
- Required for the mapped core job
Author workflow
- About this journal
- Resolves: Package requirements
- Required for the mapped core job
How to approach Journal of Management Information Systems
Use the submission guide like a working checklist. The goal is to make fit, package completeness, and cover-letter framing obvious before you open the portal.
Stage | What to check |
|---|---|
1. Scope | Confirm organizational IS fit |
2. Package | Prepare an anonymous review package |
3. Cover letter | Submit through the current journal route |
4. Final check | Pass editorial screening |
Quick answer: Submit to the Journal of Management Information Systems when the manuscript advances understanding of an organizational information-systems problem and the evidence supports both a scholarly contribution and a non-trivial implication for practice. Before upload, make the technology-to-organization mechanism visible in the title, abstract, theory, results, and discussion, then prepare a genuinely anonymized review file.
Use this Journal of Management Information Systems submission guide to test the argument and files as one package before you send them.
Use this guide to decide whether a manuscript is ready for JMIS, not merely whether it mentions information technology. The journal's current scope includes organizational systems, digital platforms, analytics, AI and machine learning in organizational IS, social and collaborative systems, sourcing, knowledge management, and the human element in organizational computing.
Evidence basis: We checked the current JMIS journal overview, JMIS aims and scope, and Taylor & Francis double-anonymous peer-review guidance on August 18, 2026. Publisher facts are sourced; the readiness framework below is Manusights editorial judgment. Recheck the live author instructions and portal fields before submission.
Source limitation: The public materials define scope and review conventions, but they do not reveal manuscript-level desk decisions. The diagnostic tests below therefore organize official guidance; they do not claim access to JMIS editorial deliberations.
This guide cannot predict editorial priority, reviewer assignment, or acceptance. It is a preparation and fit audit.
From our manuscript review practice
JMIS is an organizational information-systems journal. A technically strong digital or AI artifact still needs a consequential organizational question, a defensible knowledge contribution, and credible implications for practice.
JMIS decision at a glance
Gate | What the editor needs to see | Hold when |
|---|---|---|
Organizational IS ownership | Technology changes an organizational behavior, capability, decision, relationship, or policy outcome | The paper is primarily a new algorithm or interface benchmark |
Knowledge contribution | The study changes what the IS field understands, not only what happened in one setting | The theory appears after the results as decoration |
Practice consequence | The finding says something non-obvious for people who manage information resources | The managerial section repeats the abstract in simpler words |
Evidence fit | Design, measurement, identification, and analysis support the claimed mechanism | Causal verbs outrun the design or sample |
Review package | Anonymized manuscript, tables, figures, declarations, and metadata agree | Identity clues or conflicting versions remain |
Start with the organizational question
JMIS describes itself as a forum for work that advances the understanding and practice of organizational information systems. That boundary matters. A paper about a large language model, platform, dashboard, security control, or digital marketplace is not automatically an IS contribution.
State the organizational question in one sentence: When a defined actor uses or encounters this information system, what behavior, capability, decision, coordination problem, or policy outcome changes, and why? If the sentence can be answered with model accuracy or system latency alone, the manuscript probably needs a stronger organizational bridge or a more technical venue.
Build the contribution as a chain
Manuscript layer | Question to answer | Evidence that closes it |
|---|---|---|
Phenomenon | What consequential IS problem is unresolved? | Current literature and a precise setting boundary |
Mechanism | Why should the system produce the proposed effect? | Explicit constructs, process logic, or design principles |
Test | Can the design distinguish that explanation from plausible alternatives? | Sampling, measures, identification, robustness, and transparent analysis |
Knowledge gain | What should scholars believe or investigate differently? | A bounded theoretical revision, not a list of significant paths |
Practice value | What decision can an organization make more intelligently? | A specific action plus conditions and trade-offs |
This sequence should survive across the abstract, model or framework, methods, results, discussion, and cover letter. If each section tells a different version of the contribution, reviewers have to reconstruct the paper before they can evaluate it.
Match common study types to the JMIS bar
Quantitative field studies need a credible identification story, measurement validity, and robustness tests aligned with the strength of the claim. Statistical significance does not resolve selection, simultaneity, common-method, or construct-validity problems.
Experiments should connect the manipulation to an organizational IS mechanism and explain external boundaries. A clean online effect can still be theoretically thin or operationally remote.
Qualitative studies need transparent case selection, data provenance, analytic movement from observations to concepts, and evidence for rival interpretations.
Design and analytics research should connect artifact performance to an organizational problem. Explain why the design knowledge transfers, which conditions matter, and how the artifact changes work or decisions.
Anonymize the argument, not just the title page
JMIS states that papers are refereed through a double-anonymized process. Remove author names and affiliations, but also inspect acknowledgments, self-citations, repository links, filenames, document properties, ethics statements, grant identifiers, and phrasing such as “our prior work.” Preserve necessary scholarly context by referring to prior research in the third person rather than deleting it.
Keep a separate title page with author details for the submission system. Open the final review PDF in a clean browser session and search for surnames, institutions, cities, laboratories, grants, and identifying URLs.
Worked example: an organizational AI study
Imagine a manuscript showing that an AI decision aid improves forecast accuracy. A weak JMIS package emphasizes the model, reports average performance, and adds a generic claim that managers can make better decisions.
A stronger package asks when managers rely on the aid, how explanation or accountability changes that reliance, and whether the human-to-AI allocation improves the organizational decision under realistic incentives. It distinguishes algorithm quality from use, measures the process that links the system to the outcome, tests boundary conditions, and identifies where the aid causes complacency or conflict. The manuscript now owns an organizational IS contribution rather than only an engineering result.
Failure patterns we see in JMIS drafts
In our pre-submission review work, JMIS drafts most often weaken at the boundary between a technologically interesting result and an organizational explanation. We test the abstract, model, decisive table, and discussion opening together because those surfaces reveal whether the paper has one contribution or four partial ones.
The artifact outruns the organization. A predictive model, interface, or platform feature performs well, but the manuscript never tests how organizational actors interpret, adopt, contest, or govern it. Repair this by making the organizational mechanism part of the research design rather than adding implications afterward.
The theory names variables without explaining change. Established constructs are connected in a diagram, yet the paper cannot say what current theory gets wrong. Write a before-and-after contribution statement, then remove paths that do not help establish that change.
The practice claim is generic. “Managers should invest in AI capabilities” is not a JMIS implication. Name the manager, decision, alternative, constraint, and likely unintended consequence. This often exposes a missing moderation, process measure, or boundary condition.
Anonymization damages the scholarship. Authors sometimes delete essential prior work to hide identity. Keep the citation and refer to it neutrally in the third person. The review manuscript should be blind without becoming intellectually incomplete.
The current submission route is ScholarOne for JMIS. Verify the destination from the journal's live author link before entering metadata, because publisher workflows can change.
Readiness check
Run the scan against the requirements while they're in front of you.
See score, top issues, and journal-fit signals before you submit.
JMIS submission checklist
- Name the organizational information-systems problem in the first paragraph.
- Make the theoretical or design-knowledge gain explicit and bounded.
- Align causal language with the study design.
- Show a non-obvious practice consequence and its limits.
- Reconcile tables, figures, supplements, and the main text.
- Remove identity clues from the review manuscript and file metadata.
- Verify authorship, ethics, data, funding, conflicts, permissions, and AI-use disclosures.
- Inspect the compiled submission proof before approval.
Common questions
These questions resolve the final fit and package ambiguities that often remain after the decision audit. Recheck the live journal instructions whenever a portal or policy detail controls the upload.
What research fits JMIS?
JMIS publishes work that advances understanding and practice of organizational information systems. The technology should be tied to an organizational, managerial, policy, or societal IS problem rather than evaluated only as a technical artifact.
Does JMIS use anonymous review?
The current journal overview says full-scale research submissions receive double-anonymized review. Remove identity clues from the review manuscript and recheck the live instructions before upload.
Is JMIS a good fit for an AI paper?
Potentially, when the paper explains an organizational information-systems phenomenon or consequence. Model performance without a defensible organizational question, theoretical contribution, or practical implication is a weaker fit.
Does this guide guarantee external review?
No. It helps test fit, contribution, evidence, and package consistency before upload. Editors retain all screening and publication decisions, and a well-prepared package cannot substitute for editorial priority or reviewer judgment.
What to read next
Browse the journal directory, then compare the MIS Quarterly submission guide, Information Systems Research submission guide, European Journal of Information Systems submission guide, and JAIS submission guide. Use a free manuscript readiness scan to test whether the contribution, evidence, and package support the same JMIS decision.
Official sources accessed 2026-08-18.
- Journal of Management Information Systems, Taylor & Francis.
- JMIS aims and scope, Taylor & Francis.
- Anonymous peer review, Taylor & Francis Author Services.
Submit If
Submit when the technology is inseparable from a meaningful organizational question, the evidence can carry the claimed contribution, and the manuscript offers something non-obvious to both IS scholarship and practice.
Think Twice If
- The paper would read the same if every organization and user were removed.
- A technical benchmark is being presented as organizational insight.
- The abstract names familiar variables, but the model and results never explain the mechanism connecting them.
- The discussion and cover letter offer practical implications that could apply to almost any digital study.
- Double-anonymous review is compromised by the files or prose.
Frequently asked questions
JMIS publishes significant research that advances understanding and practice of organizational information systems. The technology must be tied to an organizational, managerial, policy, or societal information-systems problem rather than evaluated only as a technical artifact.
The current journal overview says full-scale research submissions receive double-anonymized review. Remove identity clues from the review manuscript and check the live instructions before upload.
Potentially, when the paper explains an organizational information-systems phenomenon or consequence. A model-performance paper without a defensible organizational question, theory contribution, or practice implication is usually a weaker fit.
No. It helps authors test fit, contribution, evidence, and package consistency. Editors retain all screening and publication decisions.
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Private API processing. Your manuscript is not used to train models.
Put the guidance to work
Turn the guide into a complete submission package.
Use one final checklist, then verify the journal rule that controls the files, declarations, and reporting details you will submit.