ACM Journal Cover Letter

Snapshot for ACM Transactions and journals (TOSEM, TOPLAS, TOCS, TOIS, TODS, TOG, ...). ACM editors value reproducibility and well-defined contributions.

Tone

• Contribution-led: enumerate what is new compared to prior art, including the author's own prior conference work.
• Reproducibility-aware: if artifacts are available, mention them (and the artifact evaluation badge if applicable).

Opening

• First sentence names the contribution category (technique, theory, empirical study, tool) and the system or problem it targets.
• Name the manuscript type explicitly.

Contribution Framing

• Three to four enumerated contributions, each tied to a section of the manuscript.
• For each contribution, state the evidence type (proof, benchmark, user study, ...).
• Mention artifact availability and reproducibility status.

Journal Fit

• Two to three sentences connecting the work to the journal's stated scope.
• Reference one or two prior papers from the same journal.

Declarations (Required for ACM)

• Originality and exclusivity.
• Conference extension disclosure (typical bar: ≥30% new content).
• Competing interests.
• Artifact evaluation: note if you intend to submit artifacts for evaluation.

Conditional declarations and venue practice

• AI disclosure location: ACM requires prominent disclosure of generative-AI use within the Work itself (not the cover letter); basic word-processing assistance is exempt, and "when in doubt, disclose." Do not add an AI paragraph to the letter unless the venue asks.
• Suggested / excluded reviewers: handled through the submission system, not added to the letter by default.

Length

• Hard ceiling: 500 words.

Common Desk-Reject Triggers

• Conference extension without disclosure or with insufficient new content.
• Missing reproducibility statement when claims depend on artifacts.
• Overly general contribution claims (e.g., "we improve software engineering practice" without a specific subfield).