Communications of the ACM Submission Guide: What to Prepare Before You Submit

CACM is selective because it is broad, not because it only wants narrow prestige work. The article needs to matter to practitioners and researchers across computing, or at least to a large segment of that audience.

Editors are usually asking:

• does this article serve a broad CACM readership

• can a technically strong but non-specialist reader understand the main point

• does the article explain significance rather than just present results

• is the piece better suited to CACM than to a specialist archival venue

That is why a submission can be scientifically impressive and still not fit. If the article requires substantial subject-matter expertise just to follow the setup, it often belongs elsewhere.

This is the most important structural decision. For example, Research and Advances pieces should provide context, fundamental concepts, comparisons, and significance for a broad audience. Practice pieces should be of clear interest to computing practitioners and generally avoid excessive specialization.

Choosing the wrong section creates a mismatch before anyone debates the substance: review criteria, audience expectations, and editorial framing all differ across CACM sections, so an article that fits well in one category can read as misplaced when submitted to another. Confirm the target section before starting the cover note and before finalizing the framing of the manuscript itself.

Prepare the manuscript, figures, references, and supporting material as one cohesive package. CACM articles are edited heavily for presentation, but the submission still needs to arrive in a readable state. That means the argument should be accessible without sustained specialist context, figures should support a general technical reader rather than only a subfield expert, and the structure should guide the reader through the contribution rather than assuming they can follow it from the results alone.

A conference paper submitted with minimal reframing for a broad computing audience is one of the most consistent fit problems at CACM.

Your submission note should explain:

• what problem or development the article addresses

• why it matters to the computing community broadly

• which CACM section the article is intended for

• why the article is useful to CACM readers specifically

If the note cannot explain readership fit in a few clean sentences, that is often a sign the article is not framed correctly yet.

CACM values readability. Figures, tables, and examples are not decoration here. They help the article carry a broad audience through technical material without losing them. Each figure should advance the reader's understanding of the argument rather than just present data; each example should make the contribution concrete for someone who does not specialize in the exact topic. Weak or missing visual and explanatory material is one of the consistent flags editors use to identify articles that still read like specialist papers rather than CACM features.

Even when the underlying idea is strong, reviewers and editors will test whether the article teaches, contextualizes, and persuades in a CACM voice instead of only reporting specialist work. That means the review process at CACM evaluates two things simultaneously: whether the technical contribution is valid, and whether the article explains it in a way that serves a broad computing readership. Articles that pass only the first test and not the second are consistently asked for substantial revision before any fit decision is made.

Before submitting to Communications of the ACM, a Communications of the ACM submission readiness check identifies whether the package meets the editorial bar before you commit to the submission.

Across computing manuscripts targeting Communications of the ACM, three manuscript-level patterns matter more than upload mechanics.

Conference-paper argument that never becomes a CACM feature

Across computing manuscripts targeting Communications of the ACM, this pattern appears when the manuscript has a real technical contribution but the abstract, introduction, figures, and examples still behave like a conference paper. The author assumes the reader already knows the benchmark, the system family, the prior-art dispute, or the research-program stakes. That can work at SIGCOMM, PLDI, CHI, NeurIPS, or a specialist ACM Transactions venue.

It fails faster at Communications of the ACM because the article must teach a broad computing audience why the issue matters before it asks readers to evaluate the technical details.

The practical fix is not only shortening the paper. Rebuild the first page around the computing problem, the affected audience, and the consequence of the result. Replace a result-table-first opening with a concept figure, a short example, or a before-and-after workflow that a non-specialist computing reader can understand. Move specialist ablations, equations, and implementation details into later sections or supporting material.

In the cover note, name the CACM section and explain why CACM readers need the article, not only why the work was accepted or noticed elsewhere. If the stronger home is ACM Computing Surveys, ACM Transactions on Computer-Human Interaction, IEEE Software, IEEE Computer, or a subfield conference extension, that route is often more honest than forcing a CACM feature shape.

Check broad reader feature before submitting to CACM →

Specialist vocabulary hiding the broader computing consequence

Across computing manuscripts targeting Communications of the ACM, the second pattern is a technically mature article whose significance is visible only to insiders. The methods section may be solid, the references may be current, and the system evaluation may be credible, but the abstract and first figure do not answer the CACM question: what should a broad computing professional now understand differently? Communications of the ACM is not only evaluating novelty. It is evaluating communicability across the computing profession.

The manuscript components that usually expose this problem are the abstract, section headings, figure captions, and first comparative table. If those components use subfield shorthand without translating the stakes, the article asks the editor to do the readership work.

The fix is to add a short significance bridge before the technical claim: what user, engineer, policymaker, researcher, or computing system is affected; what tradeoff changes; and why the article belongs in CACM instead of a specialist journal. Keep the references precise, but make the first citation cluster broad enough to situate the problem for CACM readers.

If the contribution is mainly a technical survey, ACM Computing Surveys may fit better. If it is a practitioner lesson, IEEE Software or ACM Queue may be stronger. If it is a specialized empirical advance, a Transactions journal may serve the manuscript more cleanly.

Check whether your CACM abstract explains the computing consequence fast enough →

Figures and examples that document results but do not teach

Across computing manuscripts targeting Communications of the ACM, the third pattern is a paper whose figures, tables, code snippets, and examples are accurate but not explanatory. CACM's author guidelines explicitly encourage graphics because the article has to be readable as a magazine contribution. A specialist result chart can prove a point to a subfield reviewer, but it may not help a broad reader understand the concept, system, risk, or design decision at the center of the article.

Before submitting, test every display item against one question: would this figure help someone outside the exact subfield follow the argument without rereading the methods? If not, revise the figure before upload. A strong CACM package usually has at least one concept figure, one concrete example, and captions that state the lesson rather than merely naming variables. The cover note should point to those teaching elements as part of the readership case.

When the visual package is still only a set of benchmark plots, the article often belongs in a specialist venue such as ACM Transactions on Graphics, ACM Transactions on Software Engineering and Methodology, IEEE Transactions on Visualization and Computer Graphics, or a top conference proceedings extension.

Check whether your CACM figures teach the broad argument →

The review tells you whether your paper clears the CACM audience-fit check before you spend another cycle on upload mechanics. Manusights checks do not train on your manuscript, and paid reviews include a 60-day money-back guarantee when the report does not meet the stated review scope.