How to Write an IEEE T-ITS Cover Letter (With Template)

The order matters. T-ITS associate editors are scanning for ITS signal density, then checking that the IEEE paperwork is clean. A letter that makes the transportation case, states the contribution, and closes the declarations in that sequence is easier to route.

Every IEEE submission needs an explicit originality statement. IEEE defines a multiple submission as an article concurrently under active consideration by two or more publications, and it must be disclosed. Include this sentence verbatim:

This manuscript has not been published previously and is not under consideration for publication elsewhere, and all authors have read and approved the submission.

That single sentence carries both required declarations: not under review elsewhere, and all authors approved. Keep it in the letter even if the portal also asks the same question in a form field. IEEE policy is explicit that questions in the submission form should also be documented in the cover letter.

State the intended paper type in the first line, because each type is screened against a different page budget. Submitting in the wrong type is one of the most common causes of return-for-format at T-ITS before review begins.

Source: IEEE T-ITS Paper Submission Guidelines, IEEE T-ITS on ITSS, accessed June 2026.

Authors may exceed the suggested length by up to 6 additional pages, and accepted papers pay $175 per overlength page after acceptance. If your contribution is a 16-page tutorial, it is a Survey Paper, not a long Regular Paper. If you are pitching a deployed corridor system, a Practitioners Paper signals that fit better than a Regular Paper would. For full upload mechanics across all four types, see the IEEE T-ITS submission process guide.

Three declarations are non-optional at T-ITS, and getting them wrong stalls the desk screen.

Conference-version disclosure. If any part of the work appeared at a conference, cite it explicitly and state the delta. T-ITS automatically allows submissions with less than 30 percent overlap, manually reviews 30 to 40 percent overlap, and auto-rejects above 40 percent. Name the concrete additions: new experiments, an additional dataset, expanded theory, or new analysis. "Extended journal version" without a stated delta is not a disclosure; it is a flag.

Suggested and excluded reviewers. A list of 3 to 5 reviewers helps the associate editor, provided none has a conflict of interest. IEEE cautions authors to avoid suggesting anyone with a real, perceived, or potential conflict, which includes co-authors, recent collaborators, and institutional colleagues. You may also request exclusions: the Editor-in-Chief generally grants an exclusion request if you state the reason. Put both lists in the letter.

Competing interests. State competing interests plainly, or state that there are none. For a resubmission of a previously rejected T-ITS paper, also reference the prior paper ID and summarize what changed.

A T-ITS declarations and scope readiness scan checks these against your manuscript before you submit.

When we read a T-ITS-bound cover letter the way an associate editor does, we are running one triage question on the first paragraph: is the transportation contribution load-bearing, or is it decoration on a method that belongs at IEEE TVT, the IEEE Internet of Things Journal, or a control journal? If we have to read into the Methods to find the ITS decision, the paper is already competing at a disadvantage.

The second pass is mechanical: is the conference disclosure honest, are the suggested reviewers free of obvious conflicts, is the paper type matched to the page budget? A clean letter on both passes earns a fast routing decision. A letter that buries the scope argument and skips the conference delta earns a slower one, and at a 15-to-20-percent acceptance rate, slow is rarely on your side.

In our pre-submission review work with IEEE Transactions on Intelligent Transportation Systems submissions, the cover letter failure patterns are remarkably consistent, and almost all of them are fixable in an afternoon. In our analysis of T-ITS-bound cover letters, the editorial culture rewards an explicit transportation argument and punishes a buried one, and these are the four named failure patterns that most often predict a scope redirect or a return-for-format before the manuscript is read.

The method-paper-in-disguise. The single most common named failure pattern across our T-ITS reviews is a cover letter that pitches a model or algorithm with transportation as the test set rather than the contribution. We see this repeatedly: the letter names a benchmark (NGSIM, PeMS, METR-LA) but never names the ITS decision the work changes. The associate editor reads that as a method paper and redirects it to a vehicular, IoT, or control venue.

The fix is to rewrite the opener so the ITS-scope framing is explicit: lead with the road, vehicle, traffic, or mobility decision, then introduce the method as the thing that enables it. We flag this in roughly the majority of T-ITS cover letters we screen.

The missing or vague conference-extension disclosure. A large share of T-ITS submissions extend a prior conference paper, yet the cover letter either omits the disclosure or writes "extended version" with no delta. Because T-ITS runs an automated overlap check that auto-rejects above 40 percent and manually reviews 30 to 40 percent, a vague disclosure invites exactly the manual scrutiny authors are hoping to avoid.

The high-leverage fix is to name the new experiments, datasets, or theory in one sentence and state that overlap is below 30 percent. This is a manuscript-component claim the editor can verify, so it earns trust.

Suggested reviewers with built-in conflicts. In our IEEE Transactions on Intelligent Transportation Systems reviews, a meaningful fraction of cover letters suggest reviewers who are recent co-authors or same-institution colleagues. IEEE policy treats that as a conflict, and an associate editor who spots it discounts the entire suggested list, which removes a lever you wanted.

The fix is to suggest reviewers who know the ITS subarea but have no co-authorship or institutional tie in the last several years, and to use the exclusion mechanism with a stated reason when there is a genuine adversarial relationship.

Paper-type and page-budget mismatch. We repeatedly see manuscripts pitched as Regular Papers that are really 18-page surveys, or 6-page Short Papers padded toward Regular-Paper length. Because T-ITS screens each type against a different page budget, this triggers a return-for-format before review.

The fix is to match the paper type to the contribution in the first line of the cover letter: a taxonomy-driven synthesis is a Survey Paper, a deployed corridor system is a Practitioners Paper, and a single focused result is a Short Paper. Naming the right type up front signals you understand how T-ITS is structured, and that the evaluation and baselines in the manuscript are scoped to match.

These patterns are testable against your own draft. Before you upload, read your cover letter and ask whether an editor outside your exact subarea could tell, from the first paragraph alone, that this is an ITS contribution and not a method paper. If not, the scope framing is the highest-leverage thing to fix.

The recurring failure is not bad English. It is weak editorial judgment about what the associate editor needs. Editors triage on the first paragraph, so a buried scope argument costs you before the manuscript is read.

Mistake 1: Writing an abstract with a different heading. The abstract summarizes the paper for readers. The cover letter argues scope fit and routing to an editor. If the letter mainly repeats results, it is answering the wrong question.

Mistake 2: Hiding the ITS decision. If the transportation contribution is not in the first paragraph, the editor has to hunt for it, and at this acceptance rate, that hunt rarely ends in your favor.

Mistake 3: A conference disclosure with no delta. "Extended version" is not a disclosure. Name the new material and state the overlap is below 30 percent.

Mistake 4: Conflicted reviewer suggestions. A suggested list full of collaborators reads as an attempt to steer review, and the editor discards it.