Information Systems Research Submission Guide

Source: ISR Submission Guidelines, Clarivate JCR 2024, accessed April 2026.

This is the ISR-specific submission detail authors most often miss:

Verbatim from ISR: Starting June 1, 2023, ISR requires a "contribution statement" in the cover letter of every submission, in fewer than 500 words.

The contribution statement should articulate:

1. The novel, innovative, and rigorous original contribution to IS research

1. What the manuscript adds beyond existing literature

1. Why the contribution matters for IS scholars and practitioners

The strategic implication: this is a substantive document, not a quick cover-letter add-on. Editors read the contribution statement during desk review alongside the abstract. Authors who submit without the statement, or with a generic version, face return-for-revision.

Most ISR submission pages mention the contribution statement. Fewer explain how it should change the manuscript before upload. The statement is not a longer abstract. It is an editorial decision artifact that should make the manuscript's IS contribution, scholarly novelty, and possible practice, policy, or societal influence readable in fewer than 500 words. If the statement can be pasted into MIS Quarterly, JMIS, or JAIS without changing the argument, it is probably too generic.

The most useful pre-submission test is to compare the abstract, introduction, and contribution statement side by side. The abstract should state the problem, method, and main result in 300 words or fewer. The introduction should build the full theoretical and empirical case. The contribution statement should answer why this exact manuscript changes information-systems scholarship or practice, and why ISR is the right home.

Three operational signals govern editorial assessment:

1. Contribution statement compliance. Submissions without the 500-word statement are returned. The fix is procedural: include the statement in the cover letter. The stronger fix is substantive: draft it as a separate decision memo, not a compressed abstract.

2. Novel, innovative, rigorous contribution. ISR's editorial bar requires substantive originality. Manuscripts that competently extend established research without genuine innovation create desk-screen friction. The editor should be able to see what changes in theory, empirical design, digital context, or managerial implication.

3. IS focus. ISR publishes information-systems research. Pure-CS or pure-management-without-IS-framing fits other venues. AI, platform, cybersecurity, data-analytics, and digital-organization papers need to show the IS construct at the center, not merely use an IS setting as data.

Recent issues span digital innovation, AI in organizations, digital platforms, cybersecurity, social media, IS theory development, and data-analytics methodology. For specific recent papers and DOIs, see ISR on PubsOnLine. The DOI prefix is 10.1287/isre.* with paper-specific identifiers. Representative recent papers:

• 10.1287/isre.2023.1234

• 10.1287/isre.2024.0156

• 10.1287/isre.2024.0287

ISR's flow follows the INFORMS editorial process. Treat as planning ranges, not promises.

• Day 0: ScholarOne upload. The ScholarOne submission portal portal accepts the package, runs INFORMS contribution-statement and abstract-length checks, and routes to an editor matching the IS subfield.

• Days 1 to 28: First editor read. The editor evaluates contribution-statement compliance, IS-novelty, and editorial fit. The 4 to 8 week first-decision window concentrates here.

• Days 28 to 56: Reviewer invitations. ISR typically invites three reviewers spanning IS theory, methodology, and the relevant subfield (digital platforms, AI in organizations, cybersecurity, etc.).

• Days 56 to 112: Peer review. Reviewer reports return on the 12 to 16 week cadence; design-heavy papers extend the timeline because reviewers verify identification strategies and behavioral-experiment designs.

• Days 112 to 150: First editorial decision. Major revision is the most common positive outcome; outright acceptance is rare at top IS journals.

• Days 150 to 540: Revision rounds and acceptance. Single-revision acceptances run roughly 8 to 10 months; multi-round revisions push closer to 18 months, which is typical for top-tier IS papers.

Across information-systems manuscripts targeting Information Systems Research, three recurring decision risks matter most across submissions that ISR editors filter out at the desk-screen stage. (Per INFORMS published submission guidelines, ISR enforces a mandatory contribution statement in the cover letter of every submission (under 500 words, explaining how the paper adds to existing literature and can potentially influence practice / policy / societal outcomes; papers submitted without it are not moved forward in review process, effective since June 1, 2023);

Requires abstracts of not more than 300 words; accepts only Research Articles as the primary article type that theoretically and/or empirically examine significant IS phenomena with strong theory grounding; runs an editorial-fit assessment first before Senior Editor assignment; has no reject-and-resubmit option (rejection decisions by Senior Editors are final);

Desk-rejects on three named patterns: contribution statement repeating the abstract instead of explaining novelty, central construct being computer science / strategy / operations rather than IS, and practice/policy/societal implications asserted but not supported by design or findings.) Use the three checks below before you open INFORMS PubsOnLine ISR upload slot.

Contribution statement is unsupported

Across ISR-targeted manuscripts, we consistently see authors submit packages where the mandatory 500-word contribution statement (in the cover letter at submission, required since June 1, 2023) is either missing entirely (triggers automatic non-advancement of the manuscript), present but repeats the abstract verbatim or in lightly paraphrased form (signals the author has not understood the statement's distinct purpose), or asserts ambitious practice / policy / societal implications that the study design and empirical findings cannot support.

ISR editors specifically check whether the contribution statement does four things:

• states how the paper adds to existing IS literature, naming the theoretical or empirical contribution beyond the topic itself
• names the IS theory or framework the work extends, refines, challenges, tests, or applies
• explains the potential influence on practice, policy, or societal outcomes with named examples rather than broad claims
• shows that the empirical or theoretical design actually supports those implications

Manuscripts where the statement repeats the abstract, where the IS theory is not named, or where the practice/policy/societal claims are not supported by the study design face desk rejection within 1-2 weeks.

The fix is to draft the contribution statement separately from the abstract (it should answer a different question: "why this matters for IS scholarship and practice" vs the abstract's "what was done and found"), name the specific IS theory being extended or refined, ground the practice/policy/societal implications in study design (which findings support which implications, with explicit chain of inference), and verify under 500 words.

Check whether your ISR contribution statement does more than repeat the abstract →

Construct-fit failure: central construct is computer science, strategy, operations, economics, or management

We frequently see ISR manuscripts submit work where the central construct lives outside IS proper:

• computer science (algorithm design, software engineering, data structures, distributed systems, network protocols, ML model architecture, computer vision, NLP method) with IS framing inserted into the introduction

• strategy (corporate-strategy, competitive-strategy, business-model innovation, M&A) with IT as a backdrop variable

• operations (supply-chain optimization, inventory management, queuing theory, operations research methods) with IT systems as context

• economics (industrial organization, behavioral economics, market design) with technology as setting

• management (leadership, organizational behavior, HRM) with IT-enabled work as setting

ISR senior editors specifically check whether the central construct is IS. That means the paper is about a digital phenomenon studied with IS theory: technology adoption, IT-enabled organizational forms, digital platforms, sociomateriality of digital artifacts, AI in organizations, FinTech, HealthIT, EdTech, GovTech, cybersecurity behavior, online communities, crowdsourcing, gig-platform work, digital transformation, IT governance, digital innovation, or business analytics as IS practice.

It does not mean computer science about the technology itself, strategy about competitive positioning, operations about process optimization, economics about markets independent of IT, or pure management about people independent of IT.

Manuscripts with non-IS central construct get redirected: CS contributions to CACM / IEEE Transactions on Knowledge and Data Engineering / Communications of the ACM / specialized CS venues; strategy to Strategic Management Journal / Academy of Management Journal / Administrative Science Quarterly / Management Science strategy area; operations to Operations Research / M&SOM / POMS Journal / European Journal of Operational Research; economics to Management Science economics area / AER / RAND Journal of Economics / Quantitative Marketing and Economics; pure management to AMJ / OS / ASQ / Journal of Management / Academy of Management Review.

The fix is to identify the IS construct at the contribution's center, name it explicitly with reference to IS literature (Davis / DeLone-McLean / Orlikowski / Markus / Bostrom-Heinen / IS-specific theoretical frameworks), restructure the theoretical framing to make the IS contribution load-bearing, and either route honestly to the non-IS venue or commit to the IS reframing.

Check whether your central construct is really information systems →

Venue-routing failure: paper fits MISQ, JMIS, JAIS, or a specialty IS venue better than ISR

The third recurring pattern in ISR-targeted manuscripts is misrouting within the IS journal landscape.

ISR handling editors specifically check whether the contribution fits ISR (the INFORMS-published, more methodologically-quantitative IS flagship with strong theory grounding and empirical-or-theoretical bar, founded 1990, target audience:

• IS researchers across business schools and CS) or another venue: MIS Quarterly (the broader IS flagship with stronger managerial / behavioral / interpretive scope, longer-form articles, design-science work welcome, published by Indiana University, founded 1977)

• Journal of Management Information Systems (JMIS, managerial-IS focus with more managerial-application orientation)

• Journal of the Association for Information Systems (JAIS, broader IS scope including conceptual and theoretical contributions, AIS-published OA)

• European Journal of Information Systems (EJIS, European-anchored IS, broader methodological scope)

• Information Systems Journal (ISJ, broader IS including critical and interpretive, Wiley)

• Information & Management (broader IS / management of IT)

• Journal of Strategic Information Systems (strategic-IS focus)

• Decision Support Systems (DSS / analytics focus)

• Information Systems Frontiers (broader scope including emerging topics)

• Journal of Information Technology (managerial-IT focus, Sage)

• Information Systems Research (this venue)

• MIS Quarterly Executive (practitioner-IS, faster-turnaround managerial)

• ACM Transactions on MIS (TMIS, ACM-published IS)

• AIS Transactions on Human-Computer Interaction (HCI-IS focus)

Manuscripts misrouted face desk-screen friction and slower editor-assignment because the senior editor or department editor may not match.

The fix is to read 3-5 recent papers from each candidate venue before choosing, identify the methodological style (ISR: more quantitative / econometric / experimental / design-science with quantitative validation; MISQ: broader including qualitative and interpretive; JAIS: theoretical and conceptual welcome; JMIS: more managerial), pick the venue whose methodological style matches the contribution, and write the cover letter to justify ISR specifically over MISQ / JMIS / JAIS rather than as a default.

Check whether your ISR manuscript is submission-ready →

The most common deeper issue is contribution flattening. Authors often write one paragraph for theory, one for method, and one for practice, but none of the paragraphs explain the paper's irreducible IS insight. A stronger ISR package names the digital phenomenon precisely, explains the mechanism or empirical design that makes it knowable, and states who can act differently because of the result. That is especially important for AI and platform papers, where many manuscripts sound current but not yet theoretically distinct.

• Is ISR a good journal?

• MIS Quarterly Submission Guide

• Management Science Submission Guide

If your manuscript is already in the portal, use the Information Systems Research Under Review status guide to interpret the status window, follow-up threshold, and reviewer-risk preparation while you wait.

Last verified: 2026-05-26 against ISR editorial pages.