Rejected from Communications of the ACM? Where to Submit Next

Audit the Communications of the ACM rejection before choosing another journal.

A desk rejection from Communications of the ACM usually says the editor could not justify external review for its audience, contribution threshold, visible evidence, or article type. That can be a routing problem, but it can also expose a weak abstract, hidden contribution, incomplete controls, or unsupported framing.

A post-review CACM rejection after external review is deeper evidence. Comments on assumptions, design, measurement, baselines, figures, reporting, interpretation, and limitations are portable. Another masthead will not erase them. Resolve the strongest repeated or editor-endorsed concern before resubmission.

A CACM transfer offer or referral, when available, identifies a possible destination rather than an acceptance path. The receiving editor decides independently. Compare the offered title with the alternatives below, revise first, and follow the live Communications of the ACM decision instructions.

For this field, the paper should make the following chain inspectable: computing problem -> timely insight -> defensible evidence -> cross-specialty meaning -> practitioner or policy consequence. Mark each connection as directly measured, validated, inferred, hypothesized, or absent. The destination should match the strongest demonstrated link, not the most ambitious sentence.

Read the CACM title, abstract, first figure or table, methods, central result, discussion, limitations, data statement, and supplement as one package. If those components do not jointly support a consequential computing idea explained to the broad ACM community, repair the inconsistency before selecting a venue.

ACM Queue

Best for: Practitioner-facing systems lessons, architecture, operations, and expert technical explanation. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the article has no concrete engineering practice or operational depth. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

IEEE Computer

Best for: Broad computing technology, practice, trends, and accessible cross-field synthesis. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the argument is too specialist or too lightly evidenced. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

ACM Computing Surveys

Best for: Comprehensive, reproducible, critical surveys that organize a computing field. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the manuscript is an essay rather than a systematic synthesis. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

interactions

Best for: Human-computer interaction practice, design, community, and reflective field narratives. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the main contribution is an algorithm or systems benchmark. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

Information and Organization

Best for: Sociotechnical, organizational, institutional, and critical information-systems research. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the organizational theory is incidental to a technology opinion. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

Technology in Society

Best for: Social, policy, ethical, institutional, and public consequences of technology. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: the article remains an internal computing-method discussion. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

Use one row per Communications of the ACM editor or reviewer concern. Quote only enough to preserve meaning, then record the affected claim and evidence. The minimum CACM extraction dimensions are:

• Article type: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Broad acm relevance: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Timeliness: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Evidence base: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Technical accessibility: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Practice or policy consequence: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Counterargument: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.

Add CACM ledger columns for owner, required work, dependency, expected artifact, and completion evidence. A concern is resolved only when its figure, method, analysis, source, or bounded claim changes and the revision can be located.

1. CACM title: name the demonstrated contribution without prestige language, unsupported causality, or breadth the sample cannot carry.
2. CACM abstract: align the question, data, method, decisive result, uncertainty, and bounded implication. Remove claims absent from the evidence.
3. CACM introduction: identify the reader's decision and precise gap. Distinguish missing knowledge from a missing application.
4. CACM related work or theory: compare the nearest alternatives, define constructs and assumptions, and explain what changes.
5. CACM data and sampling: document inclusion, exclusion, provenance, missingness, observation unit, leakage, and context boundary.
6. CACM methods: expose assumptions, controls, preprocessing, parameter choices, software, validation units, and reproducibility details.
7. CACM results: report effect size or performance with uncertainty, negative findings, sensitivity checks, and failure cases.
8. CACM figures and tables: make denominators, units, sample sizes, legends, exclusions, baselines, and uncertainty readable.
9. CACM discussion and limitations: separate observation from mechanism, test alternatives, and state where transport or application stops.
10. CACM supplement, data, and code: provide a testable audit trail with ethical, privacy, license, and access limits.
11. Next-journal cover letter: explain why the revised Communications of the ACM paper belongs to the destination and list substantive repairs.

Run a clean read from each CACM claim to its artifact. Every use of “novel,” “robust,” “general,” “effective,” “causal,” or “practical” should point to evidence proportional to that word.

Check the repaired manuscript and destination fit before resubmitting.

Use a CACM transfer when the offered journal matches the revised a consequential computing idea explained to the broad ACM community contribution, the current publisher process is acceptable, and the team can address prior advice before evaluation. Treat reviewer reports as part of the record unless the instructions say otherwise.

Appeal a Communications of the ACM decision only when a specific factual or procedural error could alter it. Follow the publisher policy linked below. Disagreement with novelty, significance, scope, or editorial judgment is normally better handled through revision and a new destination.

Submit the revised CACM paper fresh when its audience lies elsewhere, major changes alter it, or the offered venue is convenient but wrong. Do not submit elsewhere while a Communications of the ACM appeal, transfer, or parallel evaluation remains active. Never make a simultaneous submission.

Before uploading the former CACM manuscript, write a 150-word editor test naming its problem, intended readers, contribution, design, strongest evidence, uncertainty, consequence, and limitation. Then answer four questions:

1. Would the destination publish this CACM article type and scientific center according to its current scope?
2. Does the revised first page reveal why its readers care without inheriting Communications of the ACM prestige framing?
3. Did the revision resolve the controlling CACM rejection reason in evidence, not only prose?
4. Can the next editor identify the former Communications of the ACM paper's contribution and boundary without the supplement?

If the same CACM editor test fits every destination unchanged, routing is unfinished. Rewrite it until the audience and evidence obligations become specific to a consequential computing idea explained to the broad ACM community.

We audit each Communications of the ACM claim across the components its editor and reviewers can inspect. These are not acceptance-rate estimates; they are CACM repair patterns that determine whether a rejected paper becomes coherent.

Pattern 1: Communications of the ACM and the broad-interest claim is asserted, not demonstrated

We observe this in Communications of the ACM manuscripts when reviewers question affected communities, scale, urgency, decision owner, alternatives, and consequences of inaction. We audit the opening, evidence boxes, examples, conclusion, and headline. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the the broad-interest claim is asserted, not demonstrated pattern, we compare the strongest CACM claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.

Pattern 2: Communications of the ACM and specialist vocabulary survives every revision

We observe this in Communications of the ACM manuscripts when reviewers question undefined terms, notation, architecture assumptions, benchmark conventions, and community-specific shorthand. We audit the title, standfirst, diagrams, captions, body, and glossary. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the specialist vocabulary survives every revision pattern, we compare the strongest CACM claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.

Pattern 3: Communications of the ACM and a provocative thesis outruns its evidence

We observe this in Communications of the ACM manuscripts when reviewers question case selection, denominators, contrary cases, uncertainty, incentives, costs, and stakeholder effects. We audit the argument map, citations, tables, sidebars, and limitations. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the a provocative thesis outruns its evidence pattern, we compare the strongest CACM claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.

Pattern 4: Communications of the ACM and recommendations ignore implementation

We observe this in Communications of the ACM manuscripts when reviewers question ownership, resources, sequencing, governance, adoption friction, failure recovery, and measurable outcomes. We audit the practice section, case study, checklist, conclusion, and call to action. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the recommendations ignore implementation pattern, we compare the strongest CACM claim with its weakest supporting artifact, reproduce the relevant analysis or comparison where possible, and state any boundary the data cannot cross. That review often changes the destination and the wording of the title, abstract, and conclusion.

Across CACM reviews, we inspect contradictions between the clean manuscript, supplement, figures, reporting statements, code or data availability, and cover letter. A repaired analysis absent from the abstract, or a narrowed conclusion paired with an unchanged title, leaves two versions of the Communications of the ACM contribution.

We observe that the strongest CACM rerouting decisions often lower one claim while increasing trust. A paper improves when it states a narrower population, mechanism boundary, application-stage result, or specialist readership. The goal is to make a consequential computing idea explained to the broad ACM community evidence and audience agree.

Choose the next journal only when the revised manuscript can state computing problem -> timely insight -> defensible evidence -> cross-specialty meaning -> practitioner or policy consequence without skipping an unsupported link. Recheck live scopes and author instructions immediately before submission because policies and article types can change.

For Communications of the ACM, we checked current publisher pages, official author and appeal guidance, destination scopes, the Manusights URL inventory, and live exact-query results on July 13, 2026. Official sources establish policy and scope; the CACM matrices and review patterns are Manusights analysis.

The Communications of the ACM source cluster recorded 0 impressions and 2 preview starts in available demand evidence. That is a journal-level or product-intent proxy, not proof of exact rejected-from query volume. Read final Search Console data after 14 complete days; at 21 days, keep, revise, consolidate, or stop the CACM owner.