IEEE Transactions on Intelligent Transportation Systems Submission Guide

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

T-ITS publishes four primary article types:

The official T-ITS submission guidelines state that authors may choose among four paper types and should use the IEEE Transactions style before upload. The strategic implication is to identify the right format at submission. A 4-page contribution submitted as Regular faces format mismatch; a 14-page Regular Paper submitted as Short faces hard format-rejection.

The editorial policy states the format choice explicitly, so the submission decision is partly a format-evidence decision before it is a topic decision. We have found that weak T-ITS submissions often choose the paper type by word count after writing, instead of choosing the article type first and building the evidence package around that constraint.

The deeper fit implication is that the article type should match the evidence architecture, not just the page count. A strong Regular Paper usually has a complete method, a transportation-system problem, credible baselines, and figures that show why the ITS setting changes the technical decision. A Short Paper needs a compact advance that can be judged without an overbuilt methods section. A Practitioners Paper needs practical ITS deployment value, not just a shortened Regular Paper.

Verify the current Editor-in-Chief on the journal's editorial-team page before quoting any name in a cover letter. Recent T-ITS editorial direction emphasizes:

• Connected and autonomous vehicles, V2X communications

• Traffic flow modeling, control, and optimization

• AI/ML methods for transportation (deep learning, reinforcement learning, federated learning for ITS)

• Smart-city mobility and integrated multimodal transportation

• Transportation safety, human factors, and driver behavior

• Public transit optimization and shared mobility

• Sustainable transportation, electric and hybrid vehicles

Three operational signals govern editorial assessment:

1. ITS focus and methodological novelty. T-ITS publishes ITS methodology and applications. Pure-vehicular work fits IEEE TVT; pure-control fits TCST; pure-AI/ML without ITS context fits AI/ML conferences. The first-paragraph test: would an ITS researcher outside the immediate sub-area find the contribution useful?

2. Comparison to state-of-the-art using ITS benchmarks. The journal expects rigorous baseline comparison using established ITS datasets and benchmarks (e.g., NGSIM, real-world traffic data, V2X test environments). Manuscripts with limited or bespoke comparison face higher review scrutiny.

3. Format compliance. Manuscripts that exceed the format-specific page limit face return-for-shortening or substantial over-length charges.

In our analysis of the 100 most recent T-ITS papers used when this guide was built, the strongest manuscripts made the transportation-system contribution visible before the model details took over. The abstract named the ITS problem, the first figure made the road, vehicle, network, or mobility setting concrete, and the methods section showed why the chosen benchmark or deployment context mattered.

In Manusights pre-submission reviews, the recurring risk is a technically serious paper that reads like generic AI, control, communications, or optimization until late in the introduction. Editors should not have to infer the transportation-system value from a dataset name alone. The paper needs to show, in the title, abstract, figures, and validation design, why the method belongs in T-ITS rather than TVT, T-COM, TCST, Transportation Research Part C, or an applied AI venue.

Recent issues span connected/autonomous vehicle methodology, deep-learning-based traffic prediction, V2X communications, autonomous driving safety, multi-modal transportation optimization, and sustainable-transportation analytics. For specific recent papers and DOIs, see the T-ITS page on IEEE Xplore. The DOI prefix is 10.1109/TITS.* with paper-specific identifiers.

For initial submission via the IEEE Author Portal:

1. Manuscript in IEEE Transactions format, within the chosen article-type page limit

1. Title page, authors, affiliations with ORCID identifiers for all authors

1. Abstract within standard length

1. Cover letter explaining the ITS contribution and chosen format

1. Suggested reviewers as needed

1. Supplementary material for additional results and proofs

1. Conflict-of-interest disclosure for all authors

1. Author contributions statement following IEEE ITSS author-role guidance

1. Funding statement disclosing grants, sponsor support, or institutional funding

1. Ethics statement where field-trial data, naturalistic driving data, or human-subjects work are involved

1. Data availability statement; repository links for traffic datasets, V2X traces, or driving logs are encouraged

1. Conference predecessor PDF plus a difference-explanation document where the submission extends prior conference work (IEEE ITSC, ICCV, etc.)

A IEEE T-ITS submission readiness check before upload can flag whether the chosen article type is appropriate, whether the page limit is respected, and whether ITS scope fits T-ITS vs sister IEEE/Elsevier transportation journals.

If you want the general version first, start with the IEEE Transactions on Intelligent Transportation Systems submission readiness check.

T-ITS's flow follows IEEE ITSS policies; the official guidelines describe a 3-month-plus review cycle. Treat as planning ranges, not promises.

• Day 0: IEEE Author Portal upload. The portal accepts the package, runs format-and-page-limit checks against the chosen article type, and routes to an Associate Editor.

• Days 1 to 14: Administrative and editor assignment. Editorial staff verify article-type compliance, page limit, and IEEE format; the Associate Editor evaluates ITS-methodology fit.

• Days 14 to 30: Reviewer invitations. T-ITS typically invites three reviewers with ITS expertise spanning traffic modeling, autonomous-vehicle systems, V2X communications, or transit optimization.

• Days 30 to 120: Peer review. Reviewer reports return on a 8 to 16 week cadence; deployment-validation-heavy papers extend the timeline because reviewers verify field-test conditions.

• Days 90 to 150: First editorial decision. Major revision is the most common outcome for papers that pass desk review.

• Days 150 to 360: Revision rounds and acceptance. Single-revision acceptances run roughly 10 months; multi-round revisions push closer to 12 to 14 months. Accepted papers appear on IEEE Xplore early access before print scheduling.

Use the guide for portal, routing, and policy details; use the manuscript check for the editor-facing fit call.

The review tells you whether your paper clears the IEEE Transactions on Intelligent Transportation Systems fit check before upload, especially around abstract and Figure 1 read as generic AI/control/optimization rather than ITS-specific, conference-to-T-ITS extension flagged by similarity-overlap detection without disclosure, and comparison to state-of-the-art uses bespoke datasets rather than established ITS benchmarks.

Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

Across intelligent-transportation manuscripts targeting IEEE Transactions on Intelligent Transportation Systems, three recurring decision risks matter most across submissions that T-ITS editors filter out at the desk-screen stage. IEEE ITSS instructions emphasize the current IEEE Author Portal submission path, IEEE Transactions format, four paper types, article-specific page lengths, and disclosure when a manuscript has been presented, published, or submitted elsewhere. Use the three checks below before you open IEEE Author Portal upload slot.

A Manusights review checks whether your paper clears the IEEE T-ITS-specific readiness checks that official IEEE ITSS instructions cannot evaluate from a generic Author Portal checklist. Paid Manusights reviews include a 60-day money-back guarantee; submitted manuscripts are not used for model training.

Abstract and Figure 1 read as generic AI/control/optimization rather than ITS-specific

Across T-ITS-targeted manuscripts, we consistently see authors submit technically serious papers where the abstract sounds like a generic deep-learning, control-theory, or optimization contribution and Figure 1 is a model-architecture diagram rather than a transportation-system schematic.

The abstract opens with "we propose a transformer-based prediction model" or "we develop a model predictive controller" without naming the transportation phenomenon (traffic flow, vehicle trajectory, lane-change behavior, V2X handoff, signal timing, fleet routing, EV charging dispatch); Figure 1 shows a neural-network block diagram rather than a road network, vehicle, infrastructure setup, or mobility scenario.

T-ITS editors specifically check whether the transportation-system contribution is the load-bearing claim or just the application setting; if removing the road / vehicle / traffic / infrastructure / mobility context leaves the contribution intact, the paper gets redirected to T-COM, T-WC, TCST (Control Systems Tech), or TVT (Vehicular Tech) rather than T-ITS.

The fix is to rewrite the title to name the ITS phenomenon (e.g., "lane-change prediction at urban intersections" rather than "transformer-based sequence prediction"), restructure the abstract so the transportation phenomenon is in the first two sentences, and make Figure 1 a road/infrastructure/vehicle schematic with the ITS scenario explicitly labeled.

Check whether your IEEE T-ITS abstract and Figure 1 make the transportation-system claim visible →

Conference-to-T-ITS extension flagged by similarity-overlap detection without disclosure

We frequently see T-ITS manuscripts extend prior conference papers (IEEE ITSC, IEEE IV, TRB Annual Meeting) without explicit disclosure in the cover letter, which creates avoidable overlap and originality risk.

The T-ITS guidelines tell authors to inform the Editor if the manuscript has been presented, published, or submitted for publication elsewhere, because the primary objective is to publish technical material not otherwise available. Conference extensions can still work when the journal version contains substantial new contributions, but the cover letter, references, methods section, and supplementary files need to make that difference visible.

The fix is to disclose the prior conference paper in the cover letter, cite it in the related-work section, list the new methodological contributions, additional experiments, expanded ablation studies, theoretical extensions, deployment data, or benchmark evidence that justify the journal version, and include the predecessor PDF or difference explanation where the portal requests it.

Check whether your IEEE T-ITS conference-extension disclosure is complete →

Comparison to state-of-the-art uses bespoke datasets rather than established ITS benchmarks

The third recurring pattern in T-ITS-targeted manuscripts is comparison tables that use bespoke single-city or single-region datasets rather than established ITS benchmarks (NGSIM for vehicle trajectory data, METR-LA / PeMS / PEMS-BAY for traffic prediction, BDD100K for autonomous driving, KITTI for perception, nuScenes for multi-modal sensing, CARLA / Apollo for simulation, V2X-Sim for V2X testing).

T-ITS reviewers are ITS researchers who actively track the benchmark literature, and comparison tables anchored on bespoke datasets that aren't reproducible look strategically incomplete: either avoiding harder benchmarks where the method performs worse, or signaling lack of engagement with the standard evaluation infrastructure.

The fix is to include comparison on at least one established ITS benchmark in the main results table, document the benchmark version and split protocol explicitly in the methods section, and reserve bespoke datasets for demonstrating generalization rather than for primary comparison.

Manuscripts that use only bespoke datasets without engaging the standard benchmarks often face revision requests adding 2-3 months to the timeline.

Check whether your IEEE T-ITS benchmark package is reproducible enough →

• Is IEEE T-ITS a good journal?

• IEEE T-WC Submission Guide

• Transportation Research Part C Submission Guide

• Transportation Science Submission Guide

• IEEE TVT Submission Guide

If the paper is already in the portal, use the IEEE Transactions on Intelligent Transportation Systems Under Review status guide to interpret the live status label, decide when to follow up, and prepare the reviewer-risk map before a decision arrives.

Last verified: May 2026 against IEEE T-ITS editorial pages.