Rejected from ACM Computing Surveys? Where to Submit Next

Audit the ACM Computing Surveys rejection before choosing another journal.

A desk rejection from ACM Computing Surveys 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 ACM CSUR 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 ACM CSUR 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 ACM Computing Surveys decision instructions.

For this field, the paper should make the following chain inspectable: community question -> explicit corpus -> taxonomy -> comparative synthesis -> unresolved contradictions -> research agenda. 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 ACM CSUR 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 field-organizing computing survey with critical synthesis, repair the inconsistency before selecting a venue.

ACM Transactions on Intelligent Systems and Technology

Best for: Ai systems surveys with a clear intelligent-systems audience and technical 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 topic is broader computing or the survey lacks system-level insight. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

ACM Transactions on Software Engineering and Methodology

Best for: Software engineering evidence, methods, tools, and empirically grounded 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: software engineering is only one example in a cross-domain survey. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

IEEE Transactions on Pattern Analysis and Machine Intelligence

Best for: Authoritative vision, pattern recognition, and machine-learning surveys with deep technical comparison. 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 review is primarily bibliometric or lacks a sharp technical thesis. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

IEEE Communications Surveys & Tutorials

Best for: Communications and networking surveys that teach architecture, methods, standards, and open problems. 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 has no communications or networking center. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

Journal of Systems and Software

Best for: Systematic reviews and mapping studies that advance software systems and practice. 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 work does not yield actionable software-engineering knowledge. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

Information Fusion

Best for: Surveys centered on multimodal, multisensor, ensemble, or decision-level information fusion. This route works when the revised abstract, evidence, and discussion all serve that readership rather than merely replacing the journal name.

Think twice if: fusion is incidental rather than the organizing scientific problem. Resolve that mismatch before submission; a broader scope does not make an unsupported claim publishable.

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

• Corpus boundary: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Search reproducibility: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Taxonomy validity: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Technical comparison: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Evidence quality: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Contradictions: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.
• Research agenda: record what the editor or reviewers said, identify the affected manuscript component, and mark the repair as required, optional, or already supported.

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

Run a clean read from each ACM CSUR 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 ACM CSUR transfer when the offered journal matches the revised a field-organizing computing survey with critical synthesis 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 ACM Computing Surveys 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 ACM CSUR 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 ACM Computing Surveys appeal, transfer, or parallel evaluation remains active. Never make a simultaneous submission.

Before uploading the former ACM CSUR 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 ACM CSUR article type and scientific center according to its current scope?
2. Does the revised first page reveal why its readers care without inheriting ACM Computing Surveys prestige framing?
3. Did the revision resolve the controlling ACM CSUR rejection reason in evidence, not only prose?
4. Can the next editor identify the former ACM Computing Surveys paper's contribution and boundary without the supplement?

If the same ACM CSUR editor test fits every destination unchanged, routing is unfinished. Rewrite it until the audience and evidence obligations become specific to a field-organizing computing survey with critical synthesis.

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

Pattern 1: ACM Computing Surveys and coverage claims exceed the search ledger

We observe this in ACM Computing Surveys manuscripts when reviewers question databases, query variants, cut-off dates, venues, languages, preprints, and backward or forward chaining. We audit the Methods, flow diagram, corpus table, supplement, and data repository. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the coverage claims exceed the search ledger pattern, we compare the strongest ACM CSUR 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: ACM Computing Surveys and taxonomy labels do not perform analytical work

We observe this in ACM Computing Surveys manuscripts when reviewers question category definitions, edge cases, multi-label rules, coder agreement, and examples that challenge the scheme. We audit the taxonomy section, figures, appendix, 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 taxonomy labels do not perform analytical work pattern, we compare the strongest ACM CSUR 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: ACM Computing Surveys and tables count papers instead of comparing evidence

We observe this in ACM Computing Surveys manuscripts when reviewers question assumptions, datasets, metrics, compute, baselines, deployment setting, reproducibility, and failure regimes. We audit the comparison tables, narrative synthesis, figures, and agenda. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the tables count papers instead of comparing evidence pattern, we compare the strongest ACM CSUR 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: ACM Computing Surveys and future work is detached from the review

We observe this in ACM Computing Surveys manuscripts when reviewers question unresolved findings, measurement conflicts, missing benchmarks, theory gaps, and engineering constraints. We audit the Discussion, open-problem map, conclusion, and abstract. The correction must leave an evidence trail another editor can verify; changing the cover letter alone does not alter the underlying manuscript.

For the future work is detached from the review pattern, we compare the strongest ACM CSUR 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 ACM CSUR 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 ACM Computing Surveys contribution.

We observe that the strongest ACM CSUR 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 field-organizing computing survey with critical synthesis evidence and audience agree.

Choose the next journal only when the revised manuscript can state community question -> explicit corpus -> taxonomy -> comparative synthesis -> unresolved contradictions -> research agenda without skipping an unsupported link. Recheck live scopes and author instructions immediately before submission because policies and article types can change.

For ACM Computing Surveys, 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 ACM CSUR matrices and review patterns are Manusights analysis.

The ACM Computing Surveys 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 ACM CSUR owner.