Is Your Paper Ready for IEEE Transactions on Intelligent Transportation Systems? A Pre-Submission Readiness Check

These are the current, public submission limits and policies that bear on readiness. Confirm them on the journal's own IEEE ITS Society page before you submit, since the page-charge schedule and keyword lists both change.

Source: IEEE Transactions on Intelligent Transportation Systems author guidelines and aims and scope on the IEEE ITS Society site, and the IEEE Author Portal (accessed June 2026). The journal reports a 2024 JCR journal impact near 8.4; verify the live figures before submitting.

The headline that matters for readiness: the scope gate is real and applied early. The guidelines require a clear application to transportation systems and run an automated overlap check on every submission. Treat both the transportation-application test and the conference-extension disclosure as gating, not as polish.

T-ITS uses a single-anonymous model where an editor screens the paper first against scope and contribution before a reviewer reads it. Each named rejection pattern below maps to a specific triage decision, and editors consistently reject for these before the technical review begins.

A generic deep-learning model with a transportation dataset and no ITS contribution. The most common fast return. The architecture is sound and the accuracy is competitive, but the paper never explains what a transportation operator, planner, or safety engineer learns from it. The tell is consistent: the abstract leads with the model, the experiments section is all benchmark tables, and the word "transportation" mostly appears in the dataset name.

This is a framing and contribution fix, not a results fix, and it is the first thing to test on your own manuscript.

Simulation-only validation with no real-data or testbed grounding. A method evaluated entirely on a toy network or an uncalibrated simulator, with no real-world trace, field experiment, or realistic-scenario calibration. Reviewers in this community ask whether the result would survive contact with a real corridor, a real sensor stream, or real driver behavior. A paper whose only evidence is synthetic reads as preliminary, regardless of how clean the curves are.

Scope drift to a sister venue. The contribution is really vehicular radio or hardware (IEEE Transactions on Vehicular Technology territory), a single automated vehicle's perception stack (IEEE Transactions on Intelligent Vehicles), a communications-theory result with a transportation example (a communications transaction), or an image-processing method that belongs at a computer-vision conference. Editors return these to keep T-ITS centered on transportation-system contributions.

A missing methodology or application keyword. The journal requires 1 to 2 keywords from its methodology list and 1 to 2 from its application list. A submission with only generic ML keywords and no application term signals that the author has not located the work inside the ITS scope, and it triggers an administrative return.

An undisclosed conference precursor or excessive overlap. The automated overlap check flags submissions over 40 percent against prior work. An author who fails to cite a conference version, or who submits a journal paper that is mostly the conference paper, triggers a return that reads as a research-integrity concern rather than a scope problem.

Walk each manuscript component before you submit. The order below mirrors what a T-ITS editor reads first.

Abstract. 150 to 250 words, single paragraph, no equations. It must name the transportation problem and the transportation-system benefit in the first two sentences. If a transportation-systems editor cannot see why the result matters to a transportation system from the abstract alone, the paper is not ready.

Keywords. At most 6, with 1 to 2 methodology terms and 1 to 2 application terms from the required lists. This is the fastest signal that you have located the work inside ITS scope, and a missing application keyword is a preventable return.

Introduction and contribution claim. State the transportation-systems contribution explicitly, not the model. The contribution sentence should survive the first-paragraph test: would an ITS researcher outside your sub-area find it useful?

Methods and baselines. The design must match the transportation question, and the baselines must be ITS-relevant, not just a leaderboard of generic models. Reviewers notice when the comparison set ignores the transportation literature.

Experiments and validation. Real data, a real testbed, or a calibrated, field-realistic simulation. Simulation-only on a toy network is the most common validation weakness. State the data source, the scenario realism, and the limits of transfer to a real system.

Figures. Lead with a figure that shows the transportation system or deployment context. A paper whose first figures are only loss curves and confusion matrices reads as generic ML before the editor reaches the transportation framing.

Cover letter and conference disclosure. State the transportation contribution in one sentence, and disclose any conference precursor with the citation, the overlap level, and exactly what is new. This is where the extension policy is satisfied or failed.

References. Recent, complete, and engaging the transportation-systems literature, not only the ML literature your method borrows from.

If you want a manuscript-specific signal across all of these components before you submit, run a free readiness scan.

If the readiness check says the work is strong but not a T-ITS fit, route it deliberately rather than dropping a tier and blasting it out.

For a paper rejected on scope, the IEEE Open Journal of Intelligent Transportation Systems is often the path of least resistance within the same society: same ITS scope, an open-access model, and a higher acceptance rate. Choose a sister venue only when its scope genuinely fits your contribution, not just because it is convenient.

In our pre-submission review work with IEEE Transactions on Intelligent Transportation Systems manuscripts, four readiness gaps separate papers that clear the scope triage from those that come back as out of scope. Three of the four are fixable before you submit, and recognizing which one applies to your paper is the difference between a clean submission and a wasted out-of-scope return.

The contribution gap: a generic ML method wearing a transportation label. This is the readiness failure we see most often in T-ITS submissions. The architecture is competitive and the benchmark numbers are real, but the paper never names a transportation-systems insight. The tell is consistent: the abstract opens with the model, the experiments section is all generic benchmark tables, and the only transportation-specific element is the dataset. The fix is not new accuracy.

It is rewriting the introduction and abstract so the transportation contribution leads, the baselines become ITS-relevant, and Figure 1 shows the transportation system rather than a network diagram of the model. Across the T-ITS manuscripts we review, this single reframing changes more scope outcomes than any other intervention.

The validation gap: simulation-only with no real-data grounding. T-ITS reviewers in transportation expect evidence that a result transfers to a real system. We repeatedly see methodologically clean manuscripts that are not ready because the only validation is a toy or uncalibrated simulation. The right move before submission is to add a real-data trace, a field-realistic scenario, or at least an honest calibration and transfer-limits discussion. When that is impossible, an open-access ITS venue or a simulation-friendly conference is a better target than arguing realism to skeptical transportation reviewers.

The scope gap: the paper belongs at a sister venue. We routinely flag manuscripts where the real contribution is vehicular hardware (IEEE Transactions on Vehicular Technology), a single automated vehicle's perception or planning stack (IEEE Transactions on Intelligent Vehicles), a communications-theory result, or an image-processing method bound for a computer-vision conference.

The diagnostic is the abstract and Figure 1: if the protagonist is the device, the vehicle, the channel, or the image rather than the transportation system, T-ITS will read it as out of scope. Retargeting early saves a full review cycle.

The disclosure gap: an undisclosed or thin conference extension. The automated overlap check is unforgiving, and the cover letter is where the extension policy is satisfied or failed. The weakest submissions we see either omit the conference precursor entirely or extend it with cosmetic additions that leave overlap near or over 40 percent. A ready submission cites the precursor, keeps overlap under 40 percent, and states in the cover letter exactly which experiments, analysis, or theory are new. Same underlying work, different disclosure, different desk outcome.

The practical takeaway: the contribution, validation, and disclosure gaps are readiness fixes you make before submitting. The scope gap is a signal to change the target venue, not to keep arguing transportation relevance to an editor who has already decided the work belongs elsewhere. Our internal analysis of these submissions points to the same conclusion every time: at T-ITS, the transportation-contribution framing and the realism of validation decide more scope outcomes than raw method quality.

Before you commit, an IEEE Transactions on Intelligent Transportation Systems scope and readiness check tests your manuscript against these exact gaps, so you find them before an editor does.