Rejected from IEEE Internet of Things Journal? The 6 Best Journals to Submit Next

Cascade by fit and by rejection reason, not by JIF alone. Drop one tier at a time and match the venue to what your paper actually is.

Source: IEEE Internet of Things Journal author guidelines and Manusights pre-submission review observations (June 2026).

Rejected at desk for scope. If an Associate Editor returned the paper as out of scope before review, the work was not weak, it was misrouted. Reread your contribution and route it: management or orchestration framing goes to IEEE Transactions on Network and Service Management, sensing framing goes to IEEE Sensors Journal, protocol framing goes to Ad Hoc Networks or Computer Networks. Do not resubmit the same framing to another generalist IoT venue and expect a different read.

Rejected after review for thin novelty. If reviewers agreed the work is sound but called the advance incremental, step down to a sound-science venue. IEEE Access is the fast, broad next tier. Sensors (MDPI) works for applied or application-domain papers. Both judge soundness rather than narrative novelty.

Rejected after review for evaluation gaps. This is the case where you should not cascade yet. Simulation-only results, missing baselines, or an untested testbed will be flagged at every serious venue. Fix the evaluation first, then choose the next target based on the strengthened paper.

IEEE does not operate an automatic transfer system the way Nature Portfolio or Cell Press do, so you select and submit to the next venue yourself. That is an advantage: you control the framing and can match it to the venue instead of accepting a default downstream offer.

In our pre-submission review work with IEEE Internet of Things Journal submissions, the rejections we see most often cluster into four patterns, and knowing which one applies to your paper decides where it goes next.

Out-of-scope framing caught at desk screening. IEEE Internet of Things Journal Associate Editors can reject before peer review when a paper reads as a generic machine-learning, optimization, or pure-networking study with a thin IoT wrapper.

We see this as the single most common desk rejection in the IEEE Internet of Things Journal submissions we review: the abstract and introduction never make the IoT system the protagonist, so a reader cannot tell within the first paragraph why this belongs in an IoT venue rather than a generic CS journal. The fix is structural, not cosmetic.

The contribution has to be stated in IoT-system terms, and if it cannot be, the paper belongs at IEEE Access or a networking-specific Elsevier venue instead.

Simulation-only evaluation with no real-IoT validation. The component most IEEE Internet of Things Journal reviewers scrutinize is the evaluation section, and the recurring gap we flag is results produced entirely in a network simulator or a synthetic dataset with no hardware testbed, no real device traces, and no deployment data.

Reviewers in this venue expect the methods to be exercised against conditions that resemble a real IoT system: constrained devices, lossy links, or measured energy budgets. A paper whose entire evidence base is an idealized simulation reads as unvalidated here even when the algorithm is interesting. Before resubmitting anywhere stricter than IEEE Access, add at least a partial testbed or a real-trace evaluation.

Weak or missing baselines and ablations. In our review of IEEE Internet of Things Journal submissions, a consistent reason for rejection is an experiments section that compares the proposed method only against a single dated baseline, or omits the ablation that would isolate where the gain actually comes from. This is a specific, testable rejection pattern: a reviewer who cannot situate your numbers against current work cannot credit the improvement.

Reviewers cannot credit a claimed improvement they cannot situate against current work, so the methods and results read as incomplete. The figures often make this worse: performance plots without confidence intervals or variance bands signal that the statistical significance of the reported gain was never established.

Insufficient extension over a prior conference paper. IEEE policy allows expanded, archival-quality versions of conference papers, but the bar is substantial new content. We regularly see manuscripts rejected because the journal version adds a few paragraphs and one figure to the conference version without new experiments, new datasets, or a deeper analysis. Editors treat this as a near-duplicate and return it. If your submission grew out of a conference paper, the journal version needs genuinely new methods, evaluation, or reproducibility artifacts, not reformatting.

A SciRev community report for IEEE Internet of Things Journal describes a thorough process (around two reviews per round, high-quality reports, a first round near 13 weeks) that still ended in rejection, which is consistent with a venue that screens hard at desk and reviews seriously after. That cadence is worth planning around when you decide whether to revise and resubmit or move on.

Do not just blast the same PDF down the ladder. A second rejection costs more time than a focused revision, and the same evaluation gap will follow the paper to every serious venue.

Be honest about which rejection case you are in. A scope redirect needs reframing, not new data, so it can move quickly. A novelty rejection needs either a sharper positioning of the contribution or a step down to a sound-science venue. An evaluation rejection needs real work: a testbed, real device traces, stronger baselines, or proper statistical reporting on your figures. If your evidence base is simulation-only, fix that first. Add real-IoT validation before resubmitting anywhere stricter than IEEE Access, rather than cascading and collecting the same critique.

When not to resubmit at all: if two independent reviewers both said the core idea is not new and you cannot add a genuinely new method or dataset, submitting the same paper down the ladder usually buys another rejection. Submit only if you can name the specific thing you changed since the last decision.

Appeals are the exception, not the plan. They only work when you can document a factual error in the review, and a desk rejection on scope grounds almost never reverses. Spend that energy on the next submission instead.