Rejected from IEEE T-ITS? The 6 Best Journals to Submit Next

T-ITS is the top of one specific ladder, and the smartest resubmission keeps the manuscript on a rung where its real contribution is legible. The IEEE Author Portal also lets editors recommend a transfer to a sister venue, which carries your reviews forward. Match the rejection reason to the rung:

Tier 1, same society, same selectivity. If the science is strong and the rejection cited competition for slots, IEEE Transactions on Intelligent Vehicles is the lateral move for autonomous-vehicle and perception work. The reviewers overlap with T-ITS, so a manuscript that already named its transportation phenomenon transfers cleanly.

Tier 2, broader transportation venue. If T-ITS said the work was too applied, too policy-adjacent, or too far from a core ITS method, Transportation Research Part C is the next target. It is a destination for emerging-transportation technology rather than a step down, and its decision cadence is faster.

Tier 3, method venue. If the redirect was "this reads as a vehicular, communications, or IoT method, not ITS," send it where the method is the protagonist: IEEE Transactions on Vehicular Technology for in-vehicle systems, IEEE Internet of Things Journal for connected sensing and networking. Do not re-frame a method paper as ITS twice; the second editor will redirect it the same way.

Tier 4, open-access and rapid backstops. IEEE Open Journal of ITS keeps the work in the ITS society with a 100 percent open-access model and is the obvious target if T-ITS offered a transfer. IEEE Access is the rapid, multidisciplinary backstop when a 4-to-6-week decision matters more than the venue.

A find a better-fit transportation journal in 30 seconds check can rank these against your actual abstract before you commit.

In our pre-submission review work with IEEE Transactions on Intelligent Transportation Systems submissions, the rejections we see are rarely about weak engineering. They are about a transportation contribution that the editor cannot find quickly enough. In our analysis of the most recent T-ITS submissions we reviewed, three named rejection patterns generate the most consistent desk-stage redirects, and each is a specific, testable failure pattern you can check against your own manuscript before you resubmit anywhere.

The T-ITS editorial culture is methods-first: the IEEE Author Portal at mc.manuscriptcentral.com/t-its routes a 10-page Regular Paper, an 18-page Survey, or a 6-page Short Paper to an Associate Editor whose first move is to decide whether the transportation system is the contribution or just the setting.

The abstract and Figure 1 read as generic AI, not ITS. This is the single most common reason a technically serious paper gets redirected out of T-ITS. The abstract opens with "we propose a transformer-based prediction model" or "we develop a model predictive controller," and Figure 1 is a neural-network block diagram, not a road network, intersection, vehicle, or mobility scenario.

T-ITS editors apply a blunt test: if you delete the road, vehicle, traffic, or infrastructure context and the contribution still stands, the paper belongs at IEEE Transactions on Vehicular Technology, a communications transactions, or a control journal, not T-ITS.

The fix before resubmission is to put the transportation phenomenon (lane-change prediction at urban intersections, V2X handoff, signal-timing control, fleet routing, EV charging dispatch) into the title and the first two sentences of the abstract, and to make Figure 1 a labeled transportation schematic. This is the pattern to resolve before you decide between an ITS venue and a method venue, because it tells you which way to cascade.

Comparison uses bespoke data instead of established ITS benchmarks. T-ITS reviewers are ITS researchers who actively track the benchmark literature, so a comparison table anchored on a private single-region dataset reads as strategically incomplete. The reviewers expect at least one established benchmark in the main results: NGSIM or HighD for trajectory data, METR-LA, PeMS, or PEMS-BAY for traffic prediction, BDD100K or KITTI for perception, nuScenes for multi-modal sensing, CARLA or Apollo for simulation.

Manuscripts that show only bespoke datasets draw revision requests that add two to three months, or a redirect. Before resubmission, add a recognized benchmark to the primary comparison table, document the split protocol in the methods section, and keep the bespoke dataset for a generalization claim rather than the headline result.

A conference extension lacks a clear delta or disclosure. Many T-ITS submissions extend an IEEE ITSC, IEEE IV, or TRB conference paper, and the journal version is rejected for insufficient new contribution or for an undisclosed overlap the portal's similarity check flagged. T-ITS asks authors to disclose prior presentation or publication, and the journal exists to publish material not otherwise available.

The fix is mechanical: disclose the predecessor in the cover letter, cite it in related work, and list the specific additions (new ablation studies, expanded experiments, theoretical extension, deployment data, a larger benchmark) that justify a journal-length paper. A thin delta is a reason to do more work before resubmitting, not a reason to send the same paper to a faster venue.

If you are unsure which of these triggered your rejection, an IEEE T-ITS desk-rejection risk check reads your abstract and figures against the same screen the editor applies.

Don't just resubmit the same PDF down the ladder. A T-ITS rejection that says "reads as generic AI" will read the same way to a TVT editor unless you change what the abstract and Figure 1 lead with. Some of these rejections mean the paper needs real work before any venue will take it, not a faster portal.

The most expensive resubmission mistake we see is treating a scope redirect as a formatting problem: authors swap the template and resubmit unchanged, then collect a second rejection and lose three months.

Sort your rejection into one of two buckets first. A scope-fit redirect ("better suited to a vehicular / control / communications venue") means change the framing and move journals.A quality concern (missing baselines, weak ablations, an undisclosed conference overlap) means do the work before you submit anywhere, because the next set of ITS reviewers will raise the same gaps.

If reviewers asked for an established benchmark or a clearer transportation contribution, that is real work, not a journal-shopping problem. Be honest about which bucket you are in; it is the difference between a fast accept elsewhere and a slow second rejection.