IEEE Transactions on Intelligent Transportation Systems 'Under Review': What the Status Means
If your IEEE Transactions on Intelligent Transportation Systems manuscript shows Under Review, here is what the editor and reviewers are likely doing and when to follow up.
What to do next
Already submitted? Use this page to interpret the status and choose the next step.
The useful next step is understanding what the status usually means, how long the wait normally runs, and when a follow-up is actually reasonable.
Last reviewed: 2026-05-27.
Quick answer: If your IEEE Transactions on Intelligent Transportation Systems manuscript shows Under Review, it usually means the paper has moved beyond file intake into editor routing, reviewer invitation, active review, or editor synthesis. Read the status through elapsed time: Day 0 to 7 is usually intake, Days 7 to 21 is editor routing, Days 21 to 100 is the main review window, and 12 weeks is a reasonable follow-up threshold if nothing has changed.
For a paper-level read before the decision arrives, run a IEEE Transactions on Intelligent Transportation Systems manuscript readiness check.
Submission portal and editorial contact: IEEE Transactions on Intelligent Transportation Systems status should be checked in the official portal at https://ieee.atyponrex.com/journal/t-its. For editorial-office or platform questions, use authors@ieee.org or the message thread inside the manuscript record. The best public status-interpretation sources are https://ieee-itss.org/pub/t-its/, https://ieee-itss.org/wp-content/uploads/T-ITS-Paper_Submission_Guidelines.pdf, https://ieeeauthorcenter.ieee.org/contact-us/, https://ieeeauthorcenter.ieee.org/, https://journals.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/the-ieee-article-submission-process/.
IEEE Transactions on Intelligent Transportation Systems status dictionary
Status | What it usually means | Typical duration |
|---|---|---|
Submitted | Files, metadata, authorship, disclosure, and scope information have entered the portal | Day 0 to 7 |
Initial checks | Editorial office checks completeness, ethics, formatting, scope, and whether the manuscript can move to an editor | Day 0 to 7 |
With editor | The editor is judging fit, article type, evidence package, and whether outside assessment is worth requesting | Days 7 to 21 |
Under Review | Reviewers are being invited, are actively reviewing, or have returned partial reports | Days 21 to 100 |
Reviews complete | Reports are in and the editor is weighing the recommendation | Days 90 to 150 |
Decision in process | The editor or editorial office is preparing the decision letter | 2 to 10 days |
Accepted or production | The manuscript has left peer review and moved to publication checks | Check the production email |
Publisher guidance and editorial-office signals make Day 0 to 7, Days 7 to 21, and Days 21 to 100 useful ranges, not promises. They are planning windows for authors deciding whether to wait, prepare a revision, or send a status inquiry.
Day 0 to 7: File intake and editorial-office checks
The first status period is not the full scientific review. It is the journal checking whether the record can be handled: files open correctly, author metadata is complete, disclosures are included, ethics statements are present, and the manuscript appears to match the journal's scope. For IEEE Transactions on Intelligent Transportation Systems, this stage matters because a small administrative issue can look like a peer-review delay from the author's side. If the status changes quickly to Under Review, read that as a routing signal, not as proof that every reviewer has accepted.
The useful action during this stage is not to ask whether the editor likes the paper. It is to make sure every status email, submission-form field, and manuscript file points to the same claim. A mismatch between the cover letter, abstract, figure sequence, and supplementary files creates editorial friction even when the science is credible. For IEEE T-ITS, the file package should make the manuscript makes an ITS contribution in sensing, connected vehicles, traffic control, planning, mobility systems, safety, or transportation intelligence rather than only a generic AI or communications result visible before a reviewer has to hunt for it.
Days 7 to 21: Editor routing
At this point the manuscript is being read for fit. The editor is not only asking whether the manuscript is polished, but whether the manuscript makes an ITS contribution in sensing, connected vehicles, traffic control, planning, mobility systems, safety, or transportation intelligence rather than only a generic AI or communications result. In intelligent transportation systems, a manuscript can be technically competent and still difficult to route if the abstract promises one contribution while the methods, figures, or supplementary files support another.
The editor may be matching the manuscript to transportation-systems reviewers, connected-vehicle specialists, control and optimization reviewers, AI-for-mobility readers, safety reviewers, and IEEE associate editors. That matching process can take time because the editor needs reviewers who can evaluate the central claim without reconstructing the manuscript's logic from scratch. Under Review can therefore cover both reviewer recruitment and active review.
At IEEE Transactions on Intelligent Transportation Systems, the handling editor is usually making two decisions at once: whether the submission deserves outside assessment and which reviewer pool can test the manuscript fairly. IEEE T-ITS is format-sensitive and scope-sensitive: Regular, Short, Practitioner, and Survey papers have different page expectations, and the editorial read tests whether the paper belongs to intelligent transportation systems rather than to generic control, computer vision, networking, or civil-engineering venues. That editorial culture matters because the status label can look static while the handling editor checks scope, article type, evidence traceability, conflicts, and reviewer availability. Authors should prepare for comments on transportation problem definition, dataset or simulation setting, baseline comparison, deployment relevance, page-limit fit, and IEEE submission metadata while the handling editor is still shaping the review path.
Days 7 to 21: Parallel reviewer search and scope checks
In parallel, the editor may be identifying two or three reviewers and checking whether the manuscript has the right scope for those reviewers. Recruiting reviewers can take 7 to 21 days when the topic sits between fields, depends on a specialized dataset, or requires both methodological and domain expertise. A IEEE Transactions on Intelligent Transportation Systems manuscript can therefore show Under Review while the editor is still securing the right reviewer mix.
For authors, the useful question is not "has someone accepted yet?" The useful question is "if a reviewer accepts today, would the manuscript's transportation problem definition, dataset or simulation setting, baseline comparison, deployment relevance, page-limit fit, and IEEE submission metadata make the claim easy to evaluate?" That is the difference between passive waiting and productive waiting.
Days 21 to 100: Active review
This is the main period in which reviewers evaluate the paper. They are usually checking whether the conclusion follows from the methods, whether the strongest comparison or control is present, whether figures match claims, and whether limitations are honest. In IEEE Transactions on Intelligent Transportation Systems, the common weak point is not always the headline finding. It is often the missing bridge between the manuscript's strongest claim and the evidence a reviewer can audit quickly.
Active review is also where timeline anxiety becomes least informative. A quiet portal does not tell you whether one reviewer is late, whether the editor is waiting for a second report, whether a reviewer declined and had to be replaced, or whether reports are already in synthesis. The strongest response is to prepare the material you will need under every plausible decision path.
Use the waiting window to produce a revision-ready response map. Put the likely objection in one column, the manuscript location in another, the strongest supporting figure or table in a third, and the limitation language in a fourth. If the decision is revise, that map saves days. If the decision is reject, it helps you choose a cleaner transfer or resubmission path.
Days 90 to 150: Editor synthesis
After reports arrive, the editor has to turn them into a decision. This can still look like Under Review, Reviews Complete, Required Reviews Complete, or Decision in Process depending on the portal. Do not assume silence during this period means rejection. It can mean the editor is reconciling mixed reports, checking whether one reviewer misunderstood the scope, or deciding whether the manuscript needs another opinion.
The synthesis window is where the editor tests whether the reviewer concerns are compatible. If one reviewer wants deeper methods and another wants a shorter argument, the decision letter may take longer because the editor has to decide which instruction governs the revision. That delay is procedural, not necessarily negative.
What to do: when to follow up
Do not send a status inquiry during the normal early window. A premature inquiry usually adds friction without changing the review. Use this threshold instead:
- Before Days 7 to 21: wait unless the portal asks for files or an ethics issue appears.
- During Days 21 to 100: assume reviewer invitation or active review is happening.
- At 12 weeks: send one concise inquiry with manuscript ID, title, current status, and submission date.
- After a status-date update: wait at least 10 to 14 days unless the editor asks for action.
The best message is operational, not anxious. Ask whether the manuscript is still awaiting reviewer reports, awaiting editor synthesis, or missing an author action.
Readiness check
While you wait, scan your next manuscript.
The scan takes about 1-2 minutes. Use the result to decide whether to revise before the decision comes back.
"My paper has been Under Review for 12 weeks. Is that bad?"
Not automatically. The most common explanation is reviewer recruitment or a delayed report, not a hidden rejection. The more useful interpretation is whether the elapsed time matches the stage. If the paper moved to Under Review quickly and then stayed there, the editor may still be waiting on one reviewer. If the status changed after several weeks, the editor may be synthesizing reports. If there has been no movement past 12 weeks, a polite inquiry is reasonable.
What you should not do is rewrite the manuscript in panic or submit elsewhere. Prepare the response materials that will matter if the decision is revise, reject with comments, or transfer.
What to prepare while IEEE Transactions on Intelligent Transportation Systems is Under Review
Reviewer focus | Why it matters at IEEE Transactions on Intelligent Transportation Systems | How to prepare |
|---|---|---|
ITS ownership | This is a recurring IEEE T-ITS reviewer-risk area. | Prepare a one-sentence location map naming the figure, method, dataset, limitation, or response block that answers it. |
dataset or simulation realism | This is a recurring IEEE T-ITS reviewer-risk area. | Prepare a one-sentence location map naming the figure, method, dataset, limitation, or response block that answers it. |
baseline weakness | This is a recurring IEEE T-ITS reviewer-risk area. | Prepare a one-sentence location map naming the figure, method, dataset, limitation, or response block that answers it. |
page-limit mismatch | This is a recurring IEEE T-ITS reviewer-risk area. | Prepare a one-sentence location map naming the figure, method, dataset, limitation, or response block that answers it. |
conference-overlap handling | This is a recurring IEEE T-ITS reviewer-risk area. | Prepare a one-sentence location map naming the figure, method, dataset, limitation, or response block that answers it. |
Reporting checklists and study-design signals
STROBE can matter for observational human or crash-data studies, CONSORT for intervention trials, and transparent dataset/protocol reporting matters for simulation-heavy transportation papers. The point is not to stuff checklist names into the manuscript. The point is to make the study design legible before a reviewer turns an avoidable gap into a required revision.
If your paper involves human participants, animal models, survey instruments, observational datasets, omics data, spectroscopy, microscopy, computational pipelines, deposited datasets, or systematic literature selection, check the relevant reporting framework before the reviewer asks. A status page helps because Under Review is the last calm window to align transportation problem definition, dataset or simulation setting, baseline comparison, deployment relevance, page-limit fit, and IEEE submission metadata before a decision letter turns those gaps into required work.
For manuscripts with mixed designs, the best move is to include one short methods paragraph naming the applicable reporting standard, repository, instrument settings, exclusion criteria, or protocol record. That paragraph can make a reviewer more confident even when the journal does not require a formal checklist upload at initial submission.
Manusights submission-review signal for IEEE Transactions on Intelligent Transportation Systems
Across our pre-submission review work with IEEE Transactions on Intelligent Transportation Systems manuscripts, three named status-risk patterns explain most of the productive work authors can do while the portal still says Under Review. These patterns are useful because they are tied to manuscript components a reviewer can inspect, not to generic advice about waiting.
In our pre-submission review work on IEEE Transactions on Intelligent Transportation Systems manuscript packages, each specific failure pattern below turns into a concrete status-window task: inspect the abstract, first figure, methods, cover letter, data files, reporting notes, and limitation language before the reviewer report arrives.
The pages that create the most avoidable status anxiety are not always the obviously weak papers. They are credible papers where authors wait passively during Under Review instead of preparing for the exact review objections most likely to arrive. Official guidance explains the workflow, but it rarely connects the status label to the manuscript components reviewers will test.
- IEEE T-ITS evidence-chain gap: The editor needs to see transportation problem definition, dataset or simulation setting, baseline comparison, deployment relevance, page-limit fit, and IEEE submission metadata without piecing together the claim from scattered files. Prepare a one-page response map that ties the central claim to figures, methods, data files, and limitations.
- IEEE T-ITS reviewer-routing risk: The wrong reviewer pool can make a sound paper look less convincing than it is. Use the waiting window to identify how the abstract, keywords, suggested reviewers, and field framing point to transportation-systems reviewers, connected-vehicle specialists, control and optimization reviewers, AI-for-mobility readers, safety reviewers, and IEEE associate editors.
- IEEE T-ITS source-to-claim friction: Reviewers move quickly from headline claim to evidence traceability. Check that the source data, repository links, supplementary files, figure legends, and methods are easy to audit.
- IEEE T-ITS revision-readiness gap: Revision speed depends on whether authors already know which objection is likely. Draft answer blocks for the two most likely reviewer concerns before the decision letter arrives.
The recurring Manusights pattern is that authors often over-prepare the wrong asset while the manuscript is under review. They polish prose when the likely reviewer objection is a missing control, rewrite the introduction when the likely problem is a benchmark table, or wait for the decision letter when the abstract, methods, figures, and supplementary files already reveal the response strategy. For IEEE Transactions on Intelligent Transportation Systems, the highest-value waiting work is to make the evidence chain explicit enough that a reviewer can test the claim without inventing the authors' logic.
Of the 100 most recent Manusights pre-submission reviews we use as a status-page pattern sample, the useful signal was not the portal label by itself. It was whether the draft already had a journal-specific evidence map before reports arrived. Official guidance explains the workflow, but that is why this page ties Under Review to transportation problem definition, dataset or simulation setting, baseline comparison, deployment relevance, page-limit fit, and IEEE submission metadata instead of only defining the status phrase.
If you want a second set of eyes before the report lands, use the IEEE Transactions on Intelligent Transportation Systems AI review to identify reviewer-risk issues while the manuscript is still under review.
Submit if
- the transportation system is the real object of study
- the method is evaluated against credible traffic, safety, sensing, or mobility baselines
- the paper type and page length are correct before upload
Think twice if
- the paper is a generic deep-learning method with a transportation dataset
- the connected-vehicle claim lacks deployment or traffic-system context
- Transportation Research Part C, IEEE TVT, or an AI venue would own the paper better
Nearby routes to keep in view
Transportation Research Part C, IEEE Transactions on Vehicular Technology, IEEE Transactions on Mobile Computing, and Accident Analysis & Prevention can be reasonable alternatives when the evidence package is strong but the editorial center of gravity does not match IEEE Transactions on Intelligent Transportation Systems. Do not treat transfer planning as pessimism. It is a way to shorten the next move if the decision letter confirms the current venue is one level too broad, too narrow, or too format-specific.
Source limitations
Source limitations: this page uses public official-source guidance plus Manusights manuscript-risk interpretation; it cannot see the private reviewer invitations, report status, or handling-editor notes inside your manuscript record.
Public journal guidance can tell you the portal, article-scope language, submission route, and broad peer-review policy. It usually cannot tell you whether your specific paper has reviewers assigned, whether a reviewer has missed a deadline, or whether the editor is leaning toward revision or rejection. That is why this page separates official-source facts from practical interpretation. The official sources anchor the workflow; the Manusights contribution is the manuscript-level risk translation.
Official sources used for this Under Review interpretation:
- https://ieee-itss.org/pub/t-its/
- https://ieee-itss.org/wp-content/uploads/T-ITS-Paper_Submission_Guidelines.pdf
- https://ieeeauthorcenter.ieee.org/contact-us/
- https://ieeeauthorcenter.ieee.org/
- https://journals.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/the-ieee-article-submission-process/
Source-specific notes from this research pass:
- The IEEE ITSS T-ITS page says submissions are electronic only through the IEEE Author Portal at ieee.atyponrex.com/journal/t-its.
- The same page lists Regular, Short, Practitioner, and Survey paper formats with suggested page lengths.
- The T-ITS submission-guidelines PDF still references Manuscript Central for some workflow stages, so authors should use the current IEEE Author Portal link on the live journal page unless instructed otherwise.
Related IEEE Transactions on Intelligent Transportation Systems pages
- IEEE T-ITS journal hub
- IEEE T-ITS submission guide
- journal-selection guide
- not-ready warning signs
- cover-letter guide
Before you wait another month, run a IEEE Transactions on Intelligent Transportation Systems reviewer-risk check and prepare the revision map reviewers are most likely to force you to build later.
Related status guide
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.
Frequently asked questions
IEEE Transactions on Intelligent Transportation Systems Under Review usually means the manuscript is in editorial routing, reviewer invitation, active review, or editor synthesis. Check the official portal at https://ieee.atyponrex.com/journal/t-its for the live record.
A practical expectation is Days 21 to 100 for the main review window, with follow-up becoming reasonable around 12 weeks if there is no visible status movement.
Do not email during the normal early window. If the status is unchanged around 12 weeks, send one concise message with the manuscript ID, submission date, current status, and a specific status question.
The next step is usually reviews complete, decision in process, revision, rejection, transfer, or production after acceptance. The label by itself does not predict the decision.
Use the official portal at https://ieee.atyponrex.com/journal/t-its. Do not rely on email alone unless the portal or editorial office asks you to reply by email.
Not by itself. Long status time usually points to reviewer recruitment, delayed reports, editor synthesis, or routing complexity. It becomes concerning when it passes 12 weeks without portal movement or editorial-office response.
Sources
- https://ieee-itss.org/pub/t-its/
- https://ieee-itss.org/wp-content/uploads/T-ITS-Paper_Submission_Guidelines.pdf
- https://ieeeauthorcenter.ieee.org/contact-us/
- https://ieeeauthorcenter.ieee.org/
- https://journals.ieeeauthorcenter.ieee.org/submit-your-article-for-peer-review/the-ieee-article-submission-process/
Best next step
Use this page to interpret the status and choose the next sensible move.
The better next step is guidance on timing, follow-up, and what to do while the manuscript is still in the system. Save the Free Readiness Scan for the next paper you have not submitted yet.
Guidance first. Use the scan for the next manuscript.
Anthropic Privacy Partner. Zero-retention manuscript processing.
Where to go next
Same journal, next question
Supporting reads
Conversion step
Use this page to interpret the status and choose the next sensible move.
Guidance first. Use the scan for the next manuscript.