How to Write an IEEE TPAMI Cover Letter (With Template)

Here is the editor-side view. When a TPAMI submission lands in the IEEE Computer Society Manuscript Central queue, the handling Associate Editor reads the cover letter first, before the abstract, to answer three desk-screening questions: is this inside TPAMI's pattern-analysis-and-machine-intelligence scope rather than a sister-journal fit (TIP, TMI, TMM, TCI), is the work genuinely new relative to any cited conference version, and does the article type match the length and contribution expected.

We read cover letters the way an AE does, scanning for the conference-extension delta and the scope claim before anything else, because those are the two things that turn a desk rejection into a sent-for-review decision.

The order matters. The AE is scanning for routing signal density, not prose. A letter that states scope, then the delta, then reviewers, then declarations is faster to process and faster to send out.

IEEE policy requires every author to confirm originality and exclusivity. Drop these two lines into the letter verbatim and adapt the bracketed parts only:

This manuscript is original, has not been published previously, and is not currently under consideration or review at any other venue. All authors have reviewed and approved the manuscript and agree to its submission.

For conference-derived work, add the non-duplication and disclosure line that TPAMI Associate Editors specifically check:

A preliminary version of this work appeared in [Conference, Year]; that paper is cited herein, and this journal submission contains approximately [30%]+ substantive new material as described in Section [N].

Name your article type in the cover letter so the AE applies the correct bar.

Source: TPAMI Information for Authors, IEEE Computer Society author materials (accessed June 2026)

Accepted papers exceeding the Regular length incur Mandatory Overlength Page Charges, so do not promise a 14-page Regular paper in the letter and submit 20 pages of methodology without expecting the AE to flag it.

Three blocks are non-optional for a serious TPAMI submission.

Suggested and excluded reviewers. Offer 3 to 5 reviewers who actually understand the central method or benchmark, with a one-line rationale each. Name anyone you want excluded for a documented conflict. Exclude recent co-authors, advisors, and same-institution colleagues; an obvious conflict in your suggestions reads as either naivety or gaming, and both hurt at the desk.

The conference-prior-work, preprint, and dual-submission declaration. IEEE requires authors to disclose all prior publications, state how the new submission differs, and cite the prior work. For a TPAMI paper grown from CVPR, ICCV, or ECCV, this is the single most-scrutinized line in the letter. If an arXiv preprint exists, disclose the preprint and link or deposit identifier here too.

Every submission also runs through Crossref Similarity Check (iThenticate), so the conference and preprint overlap will be detected; disclosing it up front turns expected overlap into context rather than a misconduct flag.

Competing interests. State "no competing interests" or list them explicitly. Funding and conflicts that touch the benchmark, dataset, or compared baselines belong here.

In our pre-submission review work with IEEE TPAMI submissions, four cover-letter patterns predict a desk outcome before the Associate Editor opens the manuscript file. In our analysis of TPAMI submission packages, each of these is a named failure pattern you can test against your own letter, and each maps to a specific editorial expectation that the official author instructions never spell out for an individual manuscript.

The undisclosed conference paper. Across our TPAMI pre-submission reviews, the most damaging pattern is a manuscript that clearly grows from a CVPR or ICCV paper while the cover letter never says so. Because every TPAMI submission runs through iThenticate similarity checking, the overlap surfaces regardless. We flag these because an undisclosed conference origin reframes legitimate extension work as a possible dual-submission problem; the fix is a single declarative line naming the conference paper, its year, and the citation inside the manuscript.

The unquantified delta. Manuscripts coming through our pre-submission review pipeline for TPAMI routinely claim "we added more experiments" without naming the new methodology, the new ablations, or a percentage. From our submission analysis, TPAMI reviewers read the journal manuscript against the cited conference version specifically to assess the delta, so a vague claim forces them to reconstruct it.

We recommend stating the new material concretely in the cover letter and again in the Introduction: a new loss formulation, three new ablation studies, cross-dataset generalization, roughly 30 percent or more new content. The delta should be inspectable, not asserted.

The scope-blind letter that ignores sister journals. A recurring pattern in our TPAMI reviews is a strong vision paper whose cover letter never argues why it belongs in TPAMI rather than TIP (image processing), TMI (medical imaging), TMM (multimedia), or TCI (computational imaging). We see editors routinely screen for this routing call, and an image-processing-flavored method with no pattern-analysis significance argument is an easy desk redirect. We push authors to write one explicit scope sentence: why the contribution is core pattern-analysis or machine-intelligence methodology, not a sister-journal fit.

The conflicted suggested-reviewer list. Across our TPAMI pre-submission reviews, suggested-reviewer blocks frequently list recent co-authors or same-institution colleagues. The Associate Editor cross-checks names against the author list and recent collaboration records, and a conflicted suggestion costs credibility for the whole package. We advise 3 to 5 names who know the specific benchmark or method, each conflict-free, with a one-line reason the AE can act on.

These are all fixable before submission. An IEEE TPAMI conference-extension delta check can surface an undisclosed conference origin, a weak scope argument, and conflicted reviewer suggestions in a couple of minutes.

Mistake 1: Restating the abstract. The abstract summarizes the paper for readers; the cover letter argues for review and confirms scope and originality for the AE. A letter that repeats the abstract answers the wrong question.

Mistake 2: Burying or omitting the conference disclosure. This is the TPAMI-specific failure. The conference origin is not a weakness to hide; it is the expected publication path. Hiding it converts a routine extension into a misconduct review.

Mistake 3: Promising a length the manuscript does not honor. Naming a Regular paper and submitting survey-length methodology triggers Mandatory Overlength Page Charges and an AE flag. Match the article type to the manuscript.

Mistake 4: A wrong editor name on line one. Editorial boards rotate. Verify the current Editor-in-Chief on the journal's editorial-team page before quoting any name, or address the Editor-in-Chief generically.

If you cannot write a convincing scope sentence without it sounding like a sister-journal paper, that is useful information; the work may fit TIP or TMM better. If the strongest version of your extension delta still reads as "more experiments," the journal version may not yet be enough beyond the conference paper to clear TPAMI's bar. The cover letter is diagnostically useful: it forces you to articulate the delta and the scope before a reviewer does it for you.

How this guide was produced: we reviewed the TPAMI Information for Authors, the IEEE TPAMI page on the IEEE Computer Society, and the IEEE submission and peer-review policies covering originality, prior-publication disclosure, and conference-extension citation.

We then compared those public materials against anonymized patterns from Manusights pre-submission review work on TPAMI and adjacent IEEE vision-journal submissions. The article-type, page-limit, and similarity-check details come from the public IEEE sources; the cover-letter failure patterns come from review experience. Use the guidance as a desk-rejection risk screen, not a guarantee of review outcome, because TPAMI triage reasoning for an individual manuscript is not public.