Skip to main content
Journal Guides6 min readUpdated May 22, 2026

ACM Computing Surveys Submission Guide

A practical ACM Computing Surveys (CSUR) submission guide for computer scientists evaluating whether their proposed survey meets the journal's comprehensive synthesis bar.

By Senior Researcher, Physics
Author contextSenior Researcher, Physics. Experience with Physical Review Letters, Physical Review B, Nature Physics.View profile

Readiness scan

Find out if this manuscript is ready to submit.

Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.

Check my readinessAnthropic Privacy Partner. Zero-retention manuscript processing.See example reports
Submission map

How to approach ACM Computing Surveys

Use the submission guide like a working checklist. The goal is to make fit, package completeness, and cover-letter framing obvious before you open the portal.

Stage
What to check
1. Scope
Scope check
2. Package
Formatting check
3. Cover letter
Editorial screening
4. Final check
Peer review

Quick answer: This ACM Computing Surveys submission guide is for computer scientists evaluating whether their proposed survey meets CSUR's comprehensive-synthesis bar. CSUR accepts unsolicited submissions but requires an original taxonomy, analytical framework, or comparison methodology that organizes the literature.

A chronological catalog of recent papers is not a CSUR-quality survey.

Run an Acm Computing Surveys pre-submission readiness check before clicking submit, or work through this guide manually.

If you're considering CSUR, the main risk is not formatting. It is submitting a literature review rather than a survey with original organizing structure, choosing a scope too narrow for comprehensive treatment, or proposing a topic that overlaps a recent CSUR piece.

From our manuscript review practice

Of submissions we've reviewed for ACM Computing Surveys, the most consistent rejection trigger is the literature review vs. survey distinction. CSUR explicitly requires original taxonomy, analytical framework, or comparison methodology that organizes the literature, not just a chronological catalog of recent papers.

How this page was created

This page was researched from ACM Computing Surveys's author guidelines, ACM editorial-policy materials, Clarivate JCR data, SciRev community reports on ACM journals, and Manusights internal analysis of CSUR submissions and adjacent venues (ACM Computer Surveys, IEEE journals review issues, Foundations and Trends).

It owns the submission-guide intent: scope evaluation, what makes a viable survey, what editors look for in the comprehensive-synthesis bar, and what should be true before upload. It does not cover review-time interpretation or impact-factor analysis, which belong on separate pages.

The failure pattern we observe most often is the literature-review vs. survey distinction. CSUR explicitly requires original organizing structure, and submissions framed as comprehensive literature reviews without taxonomy or framework are routinely rejected.

ACM Computing Surveys Journal Metrics

Metric
Value
Impact Factor (2024 JCR)
17.8
5-Year JIF
~24+
CiteScore
28.7
Acceptance Rate
~20-30%
First Decision
2-4 months
APC (Open Access)
$1,800 (2026)
Publisher
Association for Computing Machinery
Article Types
Survey, Tutorial, Perspective

Source: Clarivate JCR 2024, ACM editorial disclosures (accessed April 2026).

CSUR Submission Requirements and Timeline

Requirement
Details
Submission portal
ACM Manuscript Central: ScholarOne submission portal
Article types
Survey, Tutorial, Perspective
Survey length
30-50 pages typical
References
100-300+ for comprehensive surveys
Display items
Taxonomy/framework figures, comparison tables expected
Cover letter
Required; should establish original contribution beyond literature catalog
Suggested reviewers
4+ recommended
Pre-submission inquiry
Accepted but not required
First decision
2-4 months from submission
Peer review duration
2-4 months
Revision window
2-3 months for major revisions
Total to acceptance
6-12 months

Source: ACM Computing Surveys author guidelines, ACM.

What happens after you submit to ACM Computing Surveys?

CSUR's upload step is deceptively simple because the decisive check is the survey architecture, not the form. Use ACM Manuscript Central at ScholarOne submission portal only after the package can show its taxonomy, reference boundary, and recent-survey differentiation in the first read. The editor and associate editor should not have to infer whether the manuscript is a CSUR survey rather than a long literature review.

Day 0: submit the manuscript, cover letter, suggested reviewers, conflict disclosures, ACM rights and authorship information, source files, figures, and supplementary material through Manuscript Central.

Day 1 to 7: administrative and editorial-office checks confirm that the file set is usable, the author list is stable, conflicts are declared, and the paper can be routed.

Day 7 to 21: the editor or associate editor reads for CSUR fit: original taxonomy, comprehensive scope, overlap with recent CSUR surveys, and whether the paper advances an organizing argument.

Day 21 to 60: if the fit screen is passed, reviewers are recruited for breadth, methodology, and topic coverage. Specialized or very new areas can take longer.

Day 60 to 120: the first decision usually separates reject, major revision, and continue-review paths. Edge cases are slower when reviewer recruitment is difficult or the manuscript spans several computing communities.

Submission snapshot

What to pressure-test
What should already be true before upload
Original organizing structure
Manuscript provides a taxonomy, analytical framework, or comparison methodology, not just chronological literature catalog
Scope breadth
Topic supports a 30-50 page comprehensive treatment with broad CS-community relevance
Reference completeness
Coverage is genuinely comprehensive (typically 100-300+ refs)
Topic timing
No comparable recent CSUR survey on the same topic in last 3-5 years
Cover letter
Letter explains the original contribution beyond literature aggregation

What this page is for

Use this page when you are still deciding:

  • whether your proposed survey has an original taxonomy or framework, not just a literature catalog
  • whether the scope justifies comprehensive treatment
  • whether reference coverage is truly comprehensive
  • how to position the cover letter to establish the original contribution

What should already be in the package

Before a credible CSUR submission goes into the system:

  • a clear original taxonomy, framework, or comparison methodology
  • comprehensive reference coverage (100-300+ references typical)
  • a comparison table or analytical figure that organizes the literature
  • a discussion section identifying open problems or future research directions
  • a cover letter that establishes the original contribution beyond literature aggregation

Package mistakes that trigger early rejection

  • Literature review framing without original taxonomy. A chronological catalog of recent papers without an original organizing structure is the most common rejection.
  • Scope too narrow. A survey on a topic with only 30-50 relevant papers typically doesn't justify CSUR's 30-50 page treatment.
  • Reference coverage gaps. A survey claiming to cover [topic] without referencing key foundational papers or recent state-of-the-art work.
  • Comparable recent CSUR coverage. A survey overlapping a CSUR piece from the last 3-5 years without a clearly distinct angle.
  • Cover letter argues comprehensiveness, not contribution. Editors look for what's new about your survey, not just that you covered many papers.

What makes ACM Computing Surveys a distinct target

CSUR is the flagship comprehensive-survey venue in computer science, with an editorial standard tuned to original organizing structure rather than literature aggregation.

Taxonomy or framework requirement: CSUR surveys must contribute an original way of organizing the field's knowledge, not just compile recent work. This distinguishes CSUR from IEEE journal review issues or workshop survey papers.

The 100-300+ reference standard: comprehensive reference coverage is expected. Surveys with 50-100 references are routinely flagged as insufficient.

The 3-5 year timing window: CSUR rarely accepts a survey on a topic covered in a recent CSUR piece without a clearly distinct angle.

The package needs:

  • an original taxonomy or framework figure in the introduction
  • a comparison table organizing the surveyed literature
  • comprehensive reference coverage
  • a discussion identifying open research directions

Article structure

Article type
Key requirements
Survey
30-50 pages; original taxonomy or framework; 100-300+ references; comparison tables and analytical figures
Tutorial
Comprehensive technical introduction to a topic with worked examples
Perspective
Argument-driven opinion on a CS research direction

Before submitting to ACM Computing Surveys, an ACM Computing Surveys submission readiness check identifies whether the package meets the editorial bar before you commit to the submission.

What a strong CSUR cover letter sounds like

The strongest CSUR cover letters establish the original contribution upfront.

They usually:

  • state the survey's original taxonomy or framework in one sentence
  • explain why this organizing structure is needed (existing surveys lack it, the field has fragmented, new techniques require new categorization)
  • distinguish from existing CSUR or IEEE survey coverage briefly
  • establish comprehensive reference coverage scope

Diagnosing pre-submission problems

Problem
Fix
Manuscript is a literature review, not a survey
Add an original taxonomy, framework, or comparison methodology that organizes the surveyed literature; if no original structure can be added, repropose to a workshop or a less-stringent venue
Scope is too narrow
Either expand the scope to a topic with broader CS-community relevance, or repropose to a Foundations and Trends piece or specialty journal review
Reference coverage gaps
Add foundational papers and recent state-of-the-art work; reviewers will request these and the cycle delay is worse than the bibliographic effort

How CSUR compares against nearby alternatives

Factor
ACM Computing Surveys
Foundations and Trends in [topic]
IEEE journal review issues
ACM journal review issues
Best fit
Comprehensive survey with original taxonomy or framework, broad CS audience
Long-form monographs on focused CS topic, deep treatment
Survey on focused topic for IEEE journal community
Survey on focused topic for ACM journal community
Think twice if
Scope is narrower than CS-community relevance
Survey is comprehensive across the broader topic rather than focused
Topic is broader than the journal's scope
Topic is broader than the ACM journal's scope

Submit If

  • the survey has an original taxonomy, framework, or comparison methodology
  • reference coverage is genuinely comprehensive (100-300+ refs)
  • the topic supports 30-50 pages of comprehensive treatment
  • no comparable CSUR piece appeared in the last 3-5 years
  • the cover letter establishes the original contribution clearly

Think Twice If

  • the manuscript is a literature catalog without original organizing structure
  • reference coverage is below 100 refs
  • a comparable CSUR survey appeared recently
  • the cover letter cannot name the synthesis question that the taxonomy answers
  • the proposed reviewer list is concentrated in one lab network or one subfield
  • the topic is too narrow for CSUR's comprehensive treatment

CSUR pre-submission checklist

Before using ACM Manuscript Central, make sure the package can survive the CSUR-specific read:

  • the cover letter names the taxonomy, framework, or comparison methodology in the first paragraph
  • the introduction distinguishes the manuscript from recent CSUR and IEEE survey coverage
  • the reference set includes foundational work, recent state-of-the-art work, and adjacent subfield work
  • suggested reviewers are broad enough for the field and free of obvious conflicts
  • authorship, conflicts of interest, funding, data/code availability, source files, and supplementary files are ready

Check taxonomy, reference coverage, and overlap before submitting to ACM Computing Surveys →

Readiness check

Run the scan against the requirements while they're in front of you.

See score, top issues, and journal-fit signals before you submit.

Check my readinessAnthropic Privacy Partner. Zero-retention manuscript processing.See example reports
  • Is ACM Computing Surveys a good journal?

Before upload, run your manuscript through an ACM Computing Surveys taxonomy and reference-coverage readiness check.

This page handles the public submission rules; the draft still needs a journal-specific fit check. The review tells you whether your paper clears the ACM Computing Surveys fit check before upload, especially around literature review framing without original organizing structure, reference coverage below the comprehensive bar, and topic overlap with recent CSUR pieces. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

Source limitations: official journal and publisher pages define scope, article types, and submission mechanics, but they do not publish manuscript-level desk decisions; the patterns below combine public guidance, recent issue review, and anonymized Manusights pre-submission review work.

Decision risks before submitting to ACM Computing Surveys

Across CS survey manuscripts targeting CSUR, three patterns generate the most consistent rejections.

Manusights pre-submission pattern analysis shows many CSUR rejections trace to literature-review framing without original taxonomy or framework. The same pattern analysis often finds these cases involve insufficient reference coverage relative to the topic's comprehensive scope. A related pattern is that these cases often arise from topic overlap with recent CSUR pieces.

Literature review framing without original organizing structure

CSUR editors specifically look for taxonomy, framework, or comparison methodology that organizes the surveyed literature in an original way. We observe that submissions framed as "a comprehensive review of recent work in [topic]" without an original organizing contribution are routinely rejected. SciRev community data on ACM journals consistently shows the original-structure requirement as the dominant filter.

Check literature review framing without original organizing structure before submitting to ACM Computing Surveys →

Reference coverage below the comprehensive bar

CSUR reviewers consistently expect 100-300+ references for a comprehensive survey. We see many manuscripts with 50-100 references that claim comprehensive coverage but lack foundational citations or recent state-of-the-art. These are routinely returned with requests to expand bibliography substantially.

Check reference coverage below the comprehensive bar before submitting to ACM Computing Surveys →

Topic overlap with recent CSUR pieces

Editors at CSUR check the journal's recent volumes. We find that submissions on topics covered in CSUR within the last 3-5 years are routinely rejected unless the new submission articulates a clearly distinct angle (a new taxonomy, a methodological reframing, an emerging subfield). A CSUR taxonomy and reference-coverage readiness check can identify whether the original-contribution case and reference completeness support a CSUR-level submission.

Clarivate JCR 2024 bibliometric data places CSUR among the highest-impact computer science journals. SciRev author-reported data confirms 2-4 month first-decision windows.

Check topic overlap with recent csur pieces before submitting to ACM Computing Surveys →

How this Acm Computing Surveys guide was checked

For the related journal overview, see Acm Computing Surveys submission guide. In our work on Acm Computing Surveys submissions, we observe that editors specifically screen the abstract, first figures, cover letter, and evidence package for whether the manuscript answers the journal's stated fit test; our analysis of Acm Computing Surveys pages treats those checks as submission-risk signals, not as official guidance.

Frequently asked questions

ACM Computing Surveys (CSUR) accepts unsolicited submissions through ACM's Manuscript Central. Pre-submission inquiries are not required but can clarify scope fit for unusual topics. The cover letter should establish the survey's contribution: a comprehensive synthesis with original taxonomy or framework, not just a literature review.

Comprehensive survey articles on computer science topics: algorithms, systems, machine learning, security, networks, databases, software engineering, HCI, and emerging CS subfields. Surveys typically run 30-50 pages with 100-300+ references. The journal also publishes Tutorials and a small number of Perspectives.

Acceptance rate runs ~20-30% across submissions. CSUR has tightened standards in recent years, particularly on the requirement for original taxonomy or analytical framework. Median time from submission to first decision is 2-4 months.

Most common reasons: the manuscript is a literature review (cataloging recent work) rather than a survey with original taxonomy or framework, scope is too narrow for a comprehensive treatment, references are not exhaustive, or a comparable recent CSUR survey covers similar ground.

References

Sources

  1. ACM Computing Surveys author guidelines
  2. ACM CSUR homepage
  3. ACM CSUR open access, ACM Digital Library.
  4. ACM CSUR associate editor guidelines, ACM Digital Library.
  5. ACM editorial policies
  6. ACM author submissions overview, ACM.
  7. Clarivate JCR 2024: ACM Computing Surveys
  8. SciRev ACM journals data

Before you upload

Choose the next useful decision step first.

Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.

Use the scan once the manuscript and target journal are concrete enough to evaluate.

Anthropic Privacy Partner. Zero-retention manuscript processing.

Internal navigation

Where to go next