IEEE Transactions on Vehicular Technology Submission Guide

Official TVT pages explain where to submit and what the journal covers. They do not tell you whether your manuscript reads like TVT rather than T-ITS, T-COM, TPEL, TTE, or IEEE Access. That is the main decision before upload.

After the official guidance, the practical screen is the set of specific failure patterns we see when the abstract, figures, validation setup, conference-extension statement, and cover letter do not make the IEEE TVT contribution class obvious.

If you want the quick pre-upload call, run an IEEE Transactions on Vehicular Technology manuscript fit check before opening the IEEE Author Portal.

For the underlying journal profile, see IEEE Transactions on Vehicular Technology.

Verify the current Editor-in-Chief and handling-editor list on the journal's editorial-team page before quoting any name in a submission cover letter.

The most important operational change is simple: Manuscript Central is no longer used for new TVT submissions. New manuscripts go through the IEEE Transactions on Vehicular Technology IEEE Author Portal, and the portal requires an IEEE account. Authors with older submissions already under review finish those through the old system, but new work belongs in the Author Portal.

The page-limit rule is also stricter than many authors expect. Initial regular papers may not exceed 14 double-column pages, including references and biographies. Initial correspondence papers may not exceed 5 pages. Revised or final regular papers may extend to 16 pages, and correspondence to 6 pages, but that does not save an overlong first submission.

The practical consequence is that TVT submissions need a tight contribution architecture. The abstract, first-page framing, scope-area fit, benchmark design, and conference-extension explanation have to be visible without turning the paper into a thesis chapter.

The IEEE VTS editorial policy states that papers not relevant to core TVT topics may be rejected, with microgrid work called out as belonging elsewhere. That is a useful warning for authors whose manuscript uses vehicles as an example but is really about a non-vehicular power, control, or communications problem.

TVT says submitted papers are reviewed by experts in four areas:

If your paper does not clearly fit one of those lanes, it may still be an IEEE paper, but it is not automatically a TVT paper.

The four-lane structure is not just taxonomy. It changes what evidence should appear before upload.

Use that table as a pre-upload screen. If the manuscript cannot name the lane and match its evidence to that lane, the editor may have to route the paper by topic label instead of by technical contribution. That is a fixable risk before submission.

TVT's stages match IEEE Vehicular Technology Society policies and what TVT authors report through community channels. Treat these as planning ranges, not promises.

• Day 0: IEEE Author Portal upload. The portal accepts the package, runs page-limit and originality checks, and assigns an Associate Editor in the matching scope area.
• Days 1 to 14: Administrative review and editor assignment. Editorial staff verify the 14-page initial limit, IEEE format compliance, and originality declarations; the Associate Editor evaluates scope fit and decides whether to send for external review.
• Days 14 to 30: Reviewer invitations. TVT typically invites three reviewers with expertise in the specific vehicular-systems area. Finding reviewers in active subfields (V2X, autonomous-vehicle control) can take longer than mature areas.
• Days 30 to 120: Peer review. Reviewer reports return on a 6 to 12 week cadence depending on paper length and methodological complexity. Long simulation-heavy papers extend the timeline.
• Days 90 to 180: First editorial decision. Major revision is the most common outcome for papers that pass desk review. Accept-without-revision is rare at IEEE Transactions.
• Days 180 to 360: Revision rounds and acceptance. Single-revision acceptances run roughly 8 to 10 months; multi-round revisions push closer to 12 months.

The mistake is choosing TVT because the application uses vehicles. The better test is whether the technical contribution becomes different because vehicles, mobility, vehicular networks, or on-board systems are central to the problem.

TVT explicitly warns authors about conference extensions. If a new submission is based on a published or accepted conference paper, the prior work must be cited, the new contribution must be substantive, and the difference must be explained. The instructions also say the previous conference PDF and summary of differences should be uploaded as supporting documents. Failure can lead to immediate rejection.

That rule matters because TVT receives many conference-extended manuscripts. A longer version is not automatically a journal contribution. The journal version needs additional analysis, new experiments, stronger theory, broader validation, clearer scope fit, or a contribution that was not already present in the conference paper.

Three questions usually decide whether the manuscript looks like a serious TVT submission.

First, is the vehicular contribution intrinsic? A generic MIMO, reinforcement-learning, optimization, battery, or control paper with a vehicle example can look opportunistic. A TVT paper should show that mobility, road dynamics, vehicular channel behavior, on-board constraints, CAV safety, or transportation-system conditions change the method or evaluation.

Second, is the scope lane obvious? TVT is broad, but broad does not mean vague. A manuscript that cannot say whether it is wireless communications, wireless networks and mobile services, vehicular electronics and systems, or connected/autonomous vehicle systems creates routing friction before review.

Third, does the evidence match the claim? Vehicular papers often overclaim from clean simulations. If the paper claims deployment value, it needs realistic mobility, channel, traffic, hardware, control, or safety assumptions rather than only idealized test cases.

The sources above define the mechanics; the harder question is whether this draft earns review. The review tells you whether YOUR paper passes the IEEE Transactions on Vehicular Technology fit screen before upload, especially around vehicular framing arriving after the abstract so the editor cannot place the work in the VTS lane, conference-extension without journal-level delta where the IEEE Author Portal similarity check flags overlap, and simulation-only evaluation with operating realism stripped so aggressively that the result no longer reads as vehicular. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.

In our pre-submission review work with IEEE Transactions on Vehicular Technology manuscripts, three recurring decision risks matter most across submissions that TVT editors filter out at the desk-screen stage. (Per IEEE VTS author instructions, TVT enforces a 14-double-column-page initial limit for regular papers and a 5-page initial limit for correspondence, and papers outside core TVT topics may be rejected before external review.) Use the three checks below before you open IEEE Author Portal upload slot.

Vehicular framing arriving after the abstract so the editor cannot place the work in the VTS lane

In our review work with TVT-targeted manuscripts, we consistently see authors submit technically competent communications, signal-processing, control, or power-electronics work where the title, abstract, and Figure 1 read as generic technology contributions and the vehicular setting appears only by section II or III. TVT senior associate editors specifically check the title-and-abstract pair for explicit naming of the vehicular system (V2X / V2V / V2I / V2N, connected vehicle, autonomous-driving subsystem, in-vehicle network, electric-vehicle powertrain, vehicular mobile-radio channel, intelligent-transportation subsystem, vehicular edge/fog computing), the vehicular operating regime (urban canyon, highway, dense intersection, mixed-autonomy traffic, EV charging-station fleet), and which VTS technical-area lane owns the contribution. Manuscripts without explicit vehicular framing in the abstract get redirected within 1-2 weeks to IEEE T-COM / T-WC for generic wireless, to TPEL / TTE for generic power electronics, to T-ITS for generic transportation systems, to T-AC / T-CST for generic control, or to TSP for generic signal processing. The fix is to rewrite the abstract so the first sentence names the vehicular system and the second sentence names the contribution within that system (e.g., "For V2X dense-platoon scenarios under 5.9 GHz DSRC and C-V2X coexistence, we present..."), make Figure 1 a vehicular-scenario figure (not a generic block diagram or system architecture), and add a "vehicular relevance" paragraph at the end of the introduction that an editor scanning for lane assignment can use.

Conference-extension without journal-level delta where the IEEE Author Portal similarity check flags overlap

In our pre-submission review work, we observe that a substantial fraction of TVT submissions are extensions of prior IEEE VTC / GLOBECOM / ICC / ITSC / IV / VPPC conference papers where the journal version does not make the new contribution visible enough. The IEEE VTS author instructions require authors to cite the prior conference paper, include a summary of differences and new contributions, and upload the prior conference PDF as a supporting document; the instructions warn that failure to do so may result in immediate rejection. In practice, submissions where the journal-level delta is only "more simulation results" or "added one new figure" read as weak even when the portal package is complete. TVT's documented expectation for journal extension is not merely a longer manuscript. The extension should include at least one substantive addition such as new theoretical analysis (convergence proof, closed-form expression, optimality condition, complexity analysis), a new system or design contribution (extended algorithm with new components, new system architecture, new optimization formulation), or substantially extended evaluation (new dataset, new scenarios, new baselines covering a broader experimental scope). The fix is to write the cover letter's originality statement as a side-by-side table of conference-version contributions vs journal-version contributions, cite the earlier paper inside the manuscript, upload the required prior-paper PDF and difference summary, and rewrite copied sections so the editor can see the new TVT contribution rather than a lightly expanded conference version.

Simulation-only evaluation with operating realism stripped so aggressively that the result no longer reads as vehicular

In our pre-submission review work with TVT-targeted manuscripts, the third pattern we see consistently is evaluation that uses simulation environments (MATLAB, NS-3, Veins, SUMO, CARLA, CarSim, custom MATLAB/Python) but with operating-regime simplifications that strip the simulation of vehicular realism. TVT reviewers (most of whom are vehicular-systems specialists) specifically check for: realistic mobility models (SUMO real-network trace or VanetMobiSim Manhattan-grid rather than uniform random waypoint), realistic channel models (3GPP TR 37.885 NLOSv V2X channel rather than free-space path loss, Doppler at relative velocity rather than static), realistic traffic density and mixed-autonomy ratios (cited from real measurement rather than assumed), realistic safety / latency constraints (3GPP 5.9 GHz DSRC packet-delay-budget rather than unbounded delay tolerance), realistic sensor and computation limits (vehicular-grade compute, automotive-grade sensor noise spec), and realistic battery / thermal / powertrain constraints for EV work. Manuscripts where reviewers can show that relaxing any one of these assumptions invalidates the result face revision requests demanding their inclusion or get rejected outright. The fix is to ground every modeling assumption in a cited automotive-industry or 3GPP standard (3GPP TR 37.885, TR 36.885, SAE J3016, IEEE 802.11bd, ETSI TS 103 723), include a sensitivity-to-realism subsection showing how the contribution holds when one or two assumptions are tightened, and use established vehicular benchmarks (NGSIM, highD, INTERACTION, BDD100K, KITTI for perception; nuScenes / Apollo / V2X-Sim for autonomy) rather than bespoke simulations where they exist.

Check whether your TVT manuscript passes the Sullivan-pass substance screen →

A Manusights review checks whether your paper clears the IEEE TVT-specific readiness checks that official IEEE VTS 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.

Check whether your IEEE TVT abstract names the vehicular system early enough →

Check whether your IEEE TVT conference-extension package proves a real journal delta →

Check whether your IEEE TVT validation assumptions are vehicular enough for review →

Before submitting to IEEE Transactions on Vehicular Technology, an IEEE Transactions on Vehicular Technology submission readiness check identifies whether the package meets the editorial bar before you commit to the submission.

• IEEE Transactions on Vehicular Technology journal profile
• IEEE T-WC submission guide
• IEEE Transactions on Intelligent Transportation Systems submission guide
• IEEE Internet of Things Journal submission guide
• IEEE Transactions on Power Electronics submission guide

Last verified: May 2026 against IEEE VTS materials.

If your manuscript is already in the portal, use the IEEE Transactions on Vehicular Technology Under Review status guide to interpret the status window, follow-up threshold, and reviewer-risk preparation while you wait.

If your manuscript is already in the portal, use the IEEE Transactions on Power Electronics Under Review status guide to interpret the status window, follow-up threshold, and reviewer-risk preparation while you wait.