ACM Computing Surveys Cover Letter: CSUR Template
Use the ACM Computing Surveys cover letter to prove the manuscript is a field-organizing survey, not a renamed literature review.
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.
How to use this page well
These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.
Question | What to do |
|---|---|
Use this page for | A working artifact you can actually apply to the manuscript or response package. |
Start with | Fill the template with real manuscript-specific details instead of leaving it generic. |
Common mistake | Copying the structure without tailoring the logic to the actual submission. |
Best next step | Use the artifact once, then cut anything that does not affect the decision. |
Quick answer: An ACM Computing Surveys cover letter should tell the editor why the manuscript is a field-organizing survey, tutorial, or perspective rather than a chronological literature review. In the first paragraph, name the topic boundary, the original taxonomy or framework, the corpus-coverage evidence, and the reason recent CSUR or adjacent surveys do not already own the same synthesis.
For the broader upload package, use the ACM Computing Surveys submission guide. If the manuscript has already been rejected, use rejected from ACM Computing Surveys: where to submit next. For journal-level context, see the ACM Computing Surveys journal profile.
Check your ACM Computing Surveys cover-letter fit before upload.
How this page was produced
Sources checked on July 15, 2026 include the ACM Computing Surveys author-guideline search result, ACM Computing Surveys journal homepage, ACM Computing Surveys reviewers page, ACM Manuscript Central route for CSUR, ScholarOne author resources, the existing Manusights ACM Computing Surveys submission guide, and the live result set for "ACM Computing Surveys cover letter." Direct ACM Digital Library fetches returned limited content in this environment, so this page records the source limitation and avoids claims that require hidden author-guideline text.
This page owns the cover-letter artifact only. It does not replace the CSUR submission guide, rejection-routing guide, impact-factor content, journal profile, or generic computer-science cover-letter advice.
What the ACM CSUR source set implies
The current ACM Computing Surveys author-guideline result says regular papers are submitted electronically through ACM Manuscript Central at https://mc.manuscriptcentral.com/csur. The CSUR homepage describes the journal as publishing comprehensive, readable surveys and tutorial papers that guide readers through literature and explain topics. The existing Manusights submission-guide source ledger records the key first-pass risk: CSUR expects an organizing contribution, not a bibliography with section headings.
For the cover letter, that means the editor needs a compact answer to five questions:
Cover-letter job | What to say | Weak version |
|---|---|---|
Survey boundary | Define the research area, time span, venues, methods, systems, or application scope. | "We review recent work in machine learning." |
Organizing contribution | Name the taxonomy, framework, comparison method, or tutorial structure. | "We provide a comprehensive overview." |
Corpus evidence | Point to the search ledger, inclusion rules, reference coverage, or table structure. | "We cite many papers." |
Overlap control | Explain how this differs from recent CSUR, IEEE, Foundations and Trends, or survey articles. | "No prior survey is complete." |
Reader payoff | Say what a computing researcher can now decide, compare, build, or teach. | "The topic is important." |
The letter should not repeat the abstract. It should make the editorial fit test easy before the editor opens the full manuscript.
Copyable ACM Computing Surveys cover-letter template
Adapt the bracketed text. Remove bracketed instructions before upload.
Dear ACM Computing Surveys Editors,
Please consider our manuscript, "[FULL MANUSCRIPT TITLE]," for ACM Computing
Surveys. The manuscript is submitted as a Survey, Tutorial, or Perspective on
[COMPUTING TOPIC AND BOUNDARY].
The manuscript's main contribution is [ORIGINAL TAXONOMY OR FRAMEWORK]. It is
not only a chronological literature review because [HOW THE FRAMEWORK ORGANIZES,
COMPARES, OR EXPLAINS THE FIELD].
The corpus covers [SEARCH SCOPE AND CUT-OFF DATE] and uses [INCLUSION RULES,
VENUES, DATABASES, OR BACKWARD-FORWARD CHAINING METHOD]. The manuscript directs
readers to [TAXONOMY FIGURE, COMPARISON TABLES, METHODS LEDGER, OR OPEN-PROBLEM
MAP] so they can verify the coverage and synthesis.
We checked related CSUR and adjacent survey articles. This manuscript differs
from them by [DISTINCT ANGLE, NEW SUBFIELD, UPDATED EVIDENCE BASE, OR NEW
ANALYTICAL METHOD].
This manuscript has not been published previously and is not under consideration
elsewhere. All authors have reviewed and approved this submission. Any preprint,
technical report, workshop version, prior submission, or related manuscript is
disclosed here: [DISCLOSURE OR NONE].
Reviewer suggestions and exclusions have been entered in the submission system.
Sincerely,
[CORRESPONDING AUTHOR NAME, AFFILIATION, EMAIL]Use the live ACM Manuscript Central form first. If the system separates declarations, prior-version disclosure, suggested reviewers, or files into fields, keep the cover letter concise and put each item in the correct field.
The ACM Computing Surveys-specific opener
Weak: Our manuscript reviews recent research on graph neural networks and will be useful to readers of ACM Computing Surveys.
Strong: We present a taxonomy of graph neural network robustness research across threat model, perturbation surface, evaluation protocol, and deployment-risk categories, then use it to compare 214 papers and identify benchmark gaps that current surveys treat separately.
The stronger opener tells the editor what the survey contributes. It names the framework, corpus, comparison function, and gap. It also gives the editor a reason to expect more than an annotated bibliography.
What to include and what to keep elsewhere
Include in the cover letter | Keep in the manuscript or submission system |
|---|---|
Topic boundary and article shape | Full title page, abstract, keywords, and ACM formatting details |
Original taxonomy, framework, or tutorial path | Complete definitions, equations, algorithms, and examples |
Search/corpus evidence at a high level | Full search strings, screening log, inclusion criteria, and reference appendix |
Difference from recent CSUR or adjacent surveys | Exhaustive related-work comparison |
Prior-version, preprint, or related-submission disclosure | Full conflict, funding, rights, ORCID, and license fields |
Reviewer suggestion or exclusion note when the system asks | Full reviewer metadata in Manuscript Central fields |
The editor should finish the letter knowing why the manuscript belongs in ACM Computing Surveys and where to look in the manuscript for proof.
CSUR cover-letter patterns that work
Manuscript shape | Letter emphasis | Avoid |
|---|---|---|
Broad methods survey | Taxonomy that changes how methods are compared, plus clear inclusion rules. | A list of methods grouped by year or venue only. |
Systems or architecture survey | Component model, deployment assumptions, evaluation axes, and reproducibility issues. | Product or paper catalog with no analytical framework. |
Security or privacy survey | Threat model, attacker capability, defense assumptions, benchmark limitations, and open risks. | Treating all attacks or defenses as comparable without context. |
HCI or human-centered computing survey | Population, task, interaction setting, measurement construct, and study-design differences. | Mixing qualitative and quantitative evidence without interpretation. |
AI or machine-learning survey | Dataset, metric, baseline, compute, evaluation leakage, and deployment boundary. | Ranking methods by reported performance without checking comparability. |
Tutorial-style submission | What the reader will understand, implement, or teach after the tutorial. | Repackaging an advanced introduction without field synthesis. |
ACM Computing Surveys readers usually need orientation across a field. The cover letter should show how the manuscript performs that orientation.
In our pre-submission review work with ACM Computing Surveys manuscripts
Across our ACM Computing Surveys pre-submission reviews, the cover letter is useful because it reveals whether the authors can state the survey architecture before the editor reconstructs it from the manuscript. These are Manusights author-side checks, not private ACM criteria, but they map to visible manuscript components: abstract, taxonomy figure, methods section, corpus table, comparison tables, limitations, and open-problem map.
ACM Computing Surveys cover letters say comprehensive but do not prove coverage
We often see CSUR cover letters claim comprehensive coverage while the manuscript has no auditable corpus boundary. The editor can see the risk immediately: missing venues, missing databases, unclear cut-off dates, no forward or backward chaining, and no rule for excluding workshop papers, preprints, duplicates, or non-English sources. A stronger cover letter names the corpus logic and directs the editor to the search ledger, reference table, or methods appendix that makes the coverage claim testable.
The taxonomy labels do not do analytical work
Another common ACM Computing Surveys failure is a taxonomy that renames existing subareas without changing what the reader can compare. A cover letter that says "we propose a taxonomy" is not enough. It should say what decisions the taxonomy supports: comparing assumptions, revealing benchmark gaps, separating deployment settings, distinguishing threat models, showing failure regimes, or connecting theory with system constraints. If the taxonomy does not help the reader reason, it will not rescue a literature-review manuscript.
The cover letter ignores recent survey overlap
CSUR editors and reviewers can search the recent literature quickly. A cover letter that never mentions nearby surveys leaves the overlap concern open. The useful letter names the difference without attacking prior work: a broader corpus, newer post-2024 evidence, different taxonomy, deeper tutorial layer, stronger comparison framework, or a newly emerged subfield. The goal is not to say previous surveys are inadequate. The goal is to show why this manuscript is necessary now.
Tables count papers instead of comparing evidence
Many computing surveys have tables, but not all tables synthesize. If a cover letter says the manuscript includes extensive tables, the editor still needs to know what those tables compare: assumptions, datasets, metrics, hardware, user populations, baselines, failure modes, threat models, or reproducibility artifacts. A CSUR letter should make the comparison unit visible so the editor expects field insight rather than spreadsheet inventory.
Reviewer suggestions and exclusions
Use the ACM Manuscript Central fields first. If the system asks for suggested reviewers or exclusions, enter them there and keep the cover-letter note short.
Reviewer suggestions and exclusions have been entered in the submission system.
We excluded [REVIEWER GROUP] because [CONFLICT REASON], not because of expected
scientific disagreement.Choose 4 reviewers who understand the survey boundary, not only the manuscript's most popular subtopic. Avoid collaborators, same-institution colleagues, recent coauthors, direct competitors with conflicts, or anyone who cannot fairly evaluate the full breadth of the survey. Exclude reviewers only when there is a real conflict. If the manuscript has a preprint, technical report, workshop version, related paper, or prior review history, disclose and link the preprint or prior version consistently in the letter and in the submission fields.
Do not create artificial urgency and significance language. For ACM Computing Surveys, a precise taxonomy, corpus, and overlap statement is more persuasive than saying the topic is rapidly growing.
Submit If
- the first paragraph names the computing topic and boundary
- the letter states the original taxonomy, framework, tutorial path, or comparison method
- the corpus coverage claim is auditable
- the overlap statement distinguishes the manuscript from recent CSUR and adjacent surveys
- the letter points to manuscript components that prove synthesis: taxonomy figure, comparison tables, corpus ledger, limitations, and open-problem map
- any preprint, technical report, workshop version, related manuscript, prior submission, or concurrent submission is disclosed consistently
Readiness check
Run the scan to see how your manuscript scores on these criteria.
See score, top issues, and what to fix before you submit.
Think Twice If
- the letter would still work after changing only the journal name
- "comprehensive" is the main contribution claim
- the taxonomy is a section outline rather than an analytical tool
- reference coverage is impressive but not reproducible
- related surveys are mentioned only in the manuscript, not in the editorial-fit argument
- the manuscript is really a narrow application review that belongs in a specialist transactions journal
Common ACM Computing Surveys cover-letter failure modes
This guide tells you what the letter should make visible: survey boundary, organizing contribution, corpus evidence, overlap control, reader payoff, and disclosure context. Manusights reports include a 60-day money-back guarantee, and submitted manuscripts are not used to train models.
The letter repeats the abstract
The abstract explains the paper. The cover letter should explain why the manuscript is a CSUR-level field synthesis and where the editor can verify the organizing contribution.
Check whether your CSUR cover letter adds route-fit value ->.
The manuscript is a literature review with CSUR branding
If the letter says the manuscript summarizes recent papers but never names the framework, the submission may read as a literature review. The cover letter should make the taxonomy or comparison method impossible to miss.
Check whether your CSUR taxonomy is doing analytical work ->.
The coverage claim cannot be audited
"We reviewed the literature" is not enough. The letter should name the evidence trail: search scope, inclusion rules, screening method, cut-off date, and where the manuscript records the corpus.
The overlap argument is missing
For a high-profile survey journal, the editor needs to know why this survey is not redundant with recent CSUR, IEEE, Foundations and Trends, or specialty-journal surveys. One precise sentence can prevent avoidable first-pass doubt.
The reader payoff is too vague
ACM Computing Surveys is not only a venue for importance claims. The letter should say what readers can compare, implement, evaluate, teach, or investigate after reading the manuscript.
Final pre-upload check
- The letter is short and journal-specific.
- The article shape is named: Survey, Tutorial, or Perspective when applicable.
- The survey boundary is explicit.
- The original taxonomy, framework, or comparison method is stated plainly.
- The corpus and inclusion logic can be verified in the manuscript.
- Recent survey overlap is addressed without overclaiming.
- Reviewer suggestions, exclusions, preprints, prior versions, related manuscripts, and conflicts are consistent across the cover letter and ACM Manuscript Central fields.
- The strongest cover-letter claim matches the abstract, taxonomy figure, corpus table, comparison tables, limitations, and open-problem map.
Practical verdict
The best ACM Computing Surveys cover letter is a compact argument that the manuscript organizes a computing field. It does not need a broad statement that the topic is important. It needs to show the editor the survey architecture: boundary, taxonomy, corpus, overlap, and reader payoff.
Use the ACM Computing Surveys submission guide for the full upload package and the ACM Computing Surveys post-rejection guide if the paper has already been declined. Before upload, an ACM Computing Surveys cover-letter review can check whether the letter's taxonomy, corpus, overlap, and disclosure signals match the manuscript.
Frequently asked questions
It should state the survey's organizing contribution: original taxonomy, analytical framework, comparison methodology, corpus boundary, overlap check, and why the manuscript is more than a literature review.
Keep it short enough for an editor to read before opening the manuscript. One focused page is usually stronger than a long abstract repeat because the letter's job is fit, contribution, disclosure, and route clarity.
No. The abstract summarizes the manuscript. The cover letter should explain the editorial-fit argument: why the manuscript is a CSUR-level survey, how the taxonomy works, and where the corpus evidence appears.
Use the live ACM Manuscript Central fields first. If reviewer suggestions or exclusions are requested, suggest qualified field-spanning reviewers and exclude reviewers only for real conflicts, not expected disagreement.
Name the intended article shape only when it is clear from the live form and manuscript: Survey, Tutorial, or Perspective. Do not force a generic article-type label into the letter if the portal captures it elsewhere.
Address the ACM Computing Surveys editors unless the live submission system names a handling editor or specific destination field. Avoid inventing a named editor when the portal does not assign one.
Reviewer visibility depends on the live submission workflow and file handling. Write the letter as if editors will read it first, and keep confidential conflicts, disclosures, and reviewer-exclusion details in the requested portal fields.
ACM Computing Surveys uses ACM Manuscript Central for submissions. The official search result confirms the CSUR author-guideline route; check the live submission form before upload because cover-letter fields and required declarations can change.
Sources
Final step
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan. See score, top issues, and journal-fit signals before you submit.
Anthropic Privacy Partner. Your manuscript is never used to train any model.