Submitting to Computer Science Journals: Checklist

Reviewers never see the majority of computer science manuscripts that get rejected. Editors send them back at the desk for reasons such as an off-topic scope, a disregarded template, code that cannot be located or a missing mandatory declaration. This checklist covers what a computer science journal expects at the point of submission, so that your paper is assessed on its research and not on admin errors. A calm final read-through against the author guidelines catches most of these problems.

Common Reasons Computer Science Papers Are Desk-Rejected

Before selecting reviewers, editors screen each new submission. In computer science, a small set of recurring problems explains most early rejections:

You can correct each of these problems before submitting, which is why a ten-minute self-check saves weeks of delay.

Files to Get Ready Before Submitting

1. Manuscript in the journal template. Begin with the Word or LaTeX template supplied by the journal. When using LaTeX, store the .tex, .bib and figure files in one folder — numerous journals request source files upon acceptance.
2. Figures and tables. Save plots in a vector format (PDF/SVG/EPS) or at a resolution of at least 300 dpi. Give axes unit labels, and confirm the colours remain legible in greyscale.
3. Code and data availability statement. State where the code and data are kept, for instance a GitHub repository archived on Zenodo to give it its own DOI, or give the reason they cannot be shared.
4. Cover letter. Keep it to one page: what the paper achieves, why it suits this journal, and a confirmation of originality and that no other journal is reviewing it.
5. Author details. For every author, supply the full name, affiliation, email and an ORCID iD, and add contact information for the corresponding author.

Completing the Online Submission Form

Platforms vary, since journals rely on OJS, ScholarOne, Editorial Manager or portals of their own, yet all request the same essential details:

What to Include in a Strong Cover Letter

• Describe the problem and what you contribute in two or three sentences; the abstract need not be repeated.
• Explain your choice of journal by pointing to its scope and, if possible, one or two related papers it has run.
• A declaration that the work is original, is not being reviewed by another journal, and has the approval of all authors.
• Name any preprint (for example on arXiv) or related conference version, and say how it differs from the submitted paper.
• Any conflicts of interest, and reviewers you would like excluded, each with the reason.

What Follows Once You Press Submit

An acknowledgement containing a manuscript or paper ID should reach you; include that ID in all your emails. Next the editor screens the paper, passes it to reviewers and sends back a decision: accept, minor revision, major revision or reject. Keep the acknowledgement email safe, as it is your proof of when and how you submitted.

When revisions are requested, respond point by point: quote each reviewer comment, state what you altered and where (section and line), and politely explain any disagreement. Do not send the same paper to another journal while the first is still considering it; that is duplicate submission, and most publishers regard it as misconduct.

An Example Cover Letter to Adapt

Make the letter brief and precise. This layout suits most computer science journals:

Dear Editor,

Please consider our manuscript “[Title]” as a research article for [Journal]. It addresses [problem] by proposing [method], which [main quantitative result] on [benchmark/dataset] relative to [baselines].

The topic matches the scope of the journal in [area] and extends recent papers it has published on [topic]. Our manuscript is original, no other journal is considering it, and every author has approved its submission. A preprint can be found at [arXiv link, if any]. Code and data can be accessed at [repository/DOI].

The authors declare that there are no competing interests. We thank you for considering our work.

[Corresponding author, affiliation, email, ORCID]

Fill each bracket with concrete details. A letter that would fit any journal and any paper gives the editor no useful information.

The 10 Most-Searched Questions on This Topic

Here are the ten questions researchers search for most on this subject, each with a direct answer.

1. submit manuscript in computer science journal

   Put together the manuscript in the journal’s template, along with a cover letter, a code and data statement and the author details, and upload everything via the journal’s online portal.

2. computer science journal submission guidelines

   Before finalising your draft, study the journal’s “instructions for authors”, which cover the aims and scope, maximum length, template, citation style and mandatory declarations.

3. LaTeX template for journal submission

   Get the journal’s own template or class file; Overleaf carries many publisher templates. For the final source upload, store your .tex, .bib and figure files in a single folder. Compile the project once more from a clean copy to confirm nothing is missing.

4. keywords for computer science paper

   Pick 4–6 precise terms that readers actually search for (such as “federated learning” or “intrusion detection”) and, when requested, the matching ACM Computing Classification System category.

5. code availability statement example

   “The code and trained models are available at [repository URL], archived at [DOI], under the [licence] licence.” If code cannot be shared, say why.

6. cover letter for journal submission computer science

   A single-page letter that explains the contribution, why the paper suits the journal, its originality, any preprint or conference version, and conflicts of interest.

7. can I submit to two journals at once

   No. Sending a paper to several journals simultaneously counts as misconduct. If you want to move, formally withdraw from the first journal before submitting elsewhere.

8. how long do journals take to respond

   Acknowledgement of receipt normally comes fast, while a first decision may take anywhere from days to months, depending on the journal, the discipline and how soon reviewers are available.

9. what is a manuscript ID

   The tracking number the journal gives your submission. Mention it in all correspondence; resubmitting would create a duplicate record.

10. desk rejection meaning

    An editor’s decision to reject before any peer review, typically because of scope, quality, formatting or similarity concerns. It happens quickly, and you can improve the paper and submit it elsewhere.

How JMVRA Fits In

At-a-Glance Checklist

1. Template usedJournal's own
2. Code availableLink or archive
3. Cover letterContribution and fit
4. Conflicts declaredIn the form
5. ID savedFor every message

Practical Tips for Submitting a Computer Science Manuscript

Computer science papers depend on code, data and experimental detail that reviewers may want to inspect. These tips help you present a submission that is easy to evaluate and hard to misread.

• Make results reproducible by others. Record software versions, random seeds, hardware and hyperparameters in an appendix or repository. A reviewer who can rerun your experiment is far more likely to trust your claims.
• Compare against fair baselines. Include recent, relevant methods and tune them as carefully as your own. Weak or untuned baselines are a common reason reviewers doubt an improvement.
• State limitations and failure cases. Describe where your method struggles, such as particular inputs, scales or datasets. Honest limitations read as confidence, and they pre-empt reviewer objections.
• Check licences for code and data. Confirm that any dataset or library you reuse permits your intended use and sharing. Cite them properly and state the licence of anything you release.
• Test your build before uploading. Compile the document from a clean folder, confirm fonts, figures and references appear correctly and read the final file as a reviewer would, not as the author.

Give reviewers everything needed to reproduce and challenge your results, and be frank about where the method does not work.

Questions Researchers Often Ask