How not to get your paper rejected — From the editors’ notebook
Other text in scientific journal, 2026
Objective: This editorial reflects on the increasing frequency of desk rejections at IST. It aims to clarify the rationale behind these decisions and address the challenge of providing meaningful feedback.
Methods: We analyzed submission trends from 2025, specifically focusing on the characteristics and common pitfalls of manuscripts that were rejected without entering the full peer-review process. Results: Our analysis reveals that desk rejections are often the result of misalignment with the journal’s scope, insufficient empirical validation, or failure to follow appropriate reporting guidelines. Because the high volume of papers does not allow for individualized feedback for every rejected manuscript, these commonalities serve as a baseline for editorial decisions.
Conclusions: To improve the likelihood of acceptance, authors should ensure their work provides clear contributions to software technology and adheres to rigorous methodological standards. This editorial provides a set of actionable guidelines designed to help authors avoid desk rejection and successfully navigate the IST publication pipeline.
Novelty
Empirical software engineering
Research impact
Publication process
Research scope
Guidelines
Author
Miroslaw Staron
Chalmers, Computer Science and Engineering (Chalmers), Software Engineering (Chalmers)
University of Gothenburg
Guilherme Travassos
Federal University of Rio de Janeiro
Barbara Russo
Free University of Bozen-Bolzano
Sudipto Ghosh
Colorado State University
Information and Software Technology
0950-5849 (ISSN)
Vol. In Press 108197Subject Categories (SSIF 2025)
Software Engineering
Information Systems
DOI
10.1016/j.infsof.2026.108197