Rejected from IEEE Transactions on Evolutionary Computation? Where to Submit Next

Use these facts as routing checks, not as automatic resubmission reasons.

Verify the current IEEE CIS TEVC publication page, information-for-authors page, submission-guideline page, page-charge page, and live submission route before quoting any workflow, title, abstract, keyword, page-charge, or review detail in a cover letter.

This page was researched from current IEEE CIS TEVC publication, information-for-authors, guidelines-for-paper-submission, and page-charge pages; the TEVC ScholarOne route; existing Manusights TEVC sibling pages; and adjacent Manusights pages for IEEE TPAMI, IEEE TIP, and Applied Soft Computing.

The non-obvious layer is center-of-gravity diagnosis. A rejected TEVC manuscript may still be a TEVC paper if the decision exposed a repairable archival-contribution, mechanism, benchmark, statistics, reproducibility, article-shape, or cover-letter problem.

It may be IEEE Transactions on Cybernetics if systems, cybernetics, control, or broad machine intelligence owns the work. It may be IEEE TNNLS if neural learning, representation, or training behavior owns it. It may be IEEE Transactions on Fuzzy Systems if fuzzy logic, uncertainty modeling, or fuzzy inference owns it. It may be ACM Transactions on Evolutionary Learning and Optimization or Evolutionary Computation if theoretical or EC-specific contribution owns it. It may be Applied Soft Computing if the applied soft-computing result is useful but not archival TEVC material. It may be a domain journal if the application community, not EC reviewers, would use the contribution.

In our review work with TEVC-targeted manuscripts, the repeated pattern is performance without field consequence. The manuscript may have a new metaheuristic, benchmark improvements, CEC results, ablations, parameter studies, and a compelling application, but the abstract and first figure still do not show what the evolutionary-computation field learns.

Do not treat rejection as automatic downgrade. Sometimes the stronger move is lateral retargeting into the venue whose reviewers value the actual contribution.

Use these labels to turn the decision letter into a repair plan.

Benchmark-without-lesson gap: the manuscript wins on benchmarks, but it does not explain what the EC community learns about representation, selection, variation, search dynamics, multiobjective tradeoffs, constraint handling, or hybridization.

Application-owns-the-paper gap: the domain problem is interesting, but the evolutionary-computation method is mainly a tool. If the application reader would care more than the EC reader, TEVC may not be the owner.

Decorative-evolutionary-layer gap: the paper uses evolutionary terminology, but the evolutionary component could be replaced by a generic optimizer without changing the scientific claim.

Statistics-and-runs gap: the manuscript reports best or average performance without enough repeated-run design, statistical testing, effect-size interpretation, parameter sensitivity, or fair baseline control.

Reproducibility-artifact gap: code, pseudocode, parameters, random seeds, datasets, problem instances, implementation details, or hardware/runtime context are not enough for reviewers to audit the result.

Transactions-depth gap: the paper reads like a conference extension because analysis, theory, ablation, limitations, benchmark diversity, or failure-case discussion does not justify archival treatment.

These labels prevent cosmetic retargeting. A benchmark-without-lesson gap is not fixed by adding one more table. An application-owns-the-paper gap is not fixed by moving to another IEEE Transactions title. A reproducibility-artifact gap is not fixed by a stronger cover letter.

The right next venue is the one where the strongest evidence becomes central rather than defensive.

Rebuild for TEVC only if the manuscript still clears the journal's core fit test: it makes an archival evolutionary-computation contribution and gives the field a reusable lesson.

Route back toward TEVC if:

• the editor invited a revised submission or the rejection reason is narrow and repairable
• the title and abstract can name the EC contribution without hiding behind the application
• Figure 1 can show the evolutionary mechanism, not only a workflow or domain system
• the benchmark table can prove fair baselines, repeated runs, statistical testing, and effect interpretation
• ablations, parameter sensitivity, runtime, failure cases, and limitations can be strengthened without changing the central claim
• code, pseudocode, seeds, datasets, problem instances, and implementation details can be made audit-ready
• the cover letter can explain why TEVC is better than IEEE TCYB, TNNLS, TFS, ACM TELO, Evolutionary Computation, Applied Soft Computing, or a domain journal

Do not rebuild for TEVC if the real contribution is a useful application, a black-box optimizer, a weakly modified metaheuristic, a domain-specific engineering result, or a machine-learning method whose evolutionary component is incidental.

IEEE Transactions on Cybernetics is cleaner when the manuscript's center is systems, control, cybernetics, machine intelligence, human-machine systems, or broad intelligent systems. If the EC layer is one component in a wider cybernetic system, TEVC may not be the right owner.

IEEE TNNLS is cleaner when neural learning owns the paper: architecture search, learning dynamics, representation, training, generalization, or neural optimization. Do not use it if the manuscript's value is still a field-level evolutionary-computation insight.

IEEE Transactions on Fuzzy Systems is cleaner when fuzzy inference, uncertainty modeling, neuro-fuzzy logic, or fuzzy decision systems own the contribution. It is weaker when fuzzy logic is only a small design choice in an EC algorithm.

ACM TELO or Evolutionary Computation can be cleaner when the EC-specific theory, algorithmic principle, or evolutionary-learning contribution is strong but the paper needs a different editorial culture than TEVC. The same benchmark and reproducibility burden still applies.

Applied Soft Computing is cleaner when the method is a useful soft-computing contribution demonstrated on a real-world problem, but the TEVC rejection shows the general EC lesson is not strong enough. Compare Applied Soft Computing when the application and measured payoff are central.

A domain journal is cleaner when the application community owns the value. Robotics, scheduling, logistics, power systems, smart grids, finance, transportation, manufacturing, medical informatics, and design-optimization papers often fail TEVC not because they are weak, but because the reader who would use the result is not primarily an EC theorist or algorithm designer.

For a domain route, rebuild the paper honestly. The abstract should lead with the domain decision, system constraint, or engineering outcome, while the EC method becomes the mechanism that supports the application.

In our review work with TEVC-targeted manuscripts, the worst retargeting mistakes happen when authors treat evolutionary computation, cybernetics, neural networks, fuzzy systems, soft computing, optimization, and domain journals as interchangeable. We observe the same failure when a rejection is treated as a prestige problem rather than a map of contribution ownership, benchmark rigor, statistics, reproducibility, and reviewer routing. We separate the decision letter into testable patterns before recommending the next journal.

TEVC field-lesson pattern: the manuscript has a strong benchmark table, but the abstract does not state what the EC field learns. In this pattern, the next move is not another leaderboard table. The title, abstract, Figure 1, method section, ablation plan, benchmark table, and limitations paragraph must show the reusable lesson about search dynamics, representation, selection, variation, constraint handling, hybridization, or multiobjective tradeoffs.

TEVC application-owner pattern: the problem domain is more compelling than the EC method. The paper may be valuable for robotics, power systems, scheduling, logistics, manufacturing, medicine, or finance, but TEVC reviewers will ask what is generalizable for evolutionary computation. If the answer is mostly domain performance, the title and abstract should be rebuilt for a domain journal instead of another computational-intelligence venue.

TEVC statistics-and-reproducibility pattern: the rejection may look like novelty or fit, but the weak point is repeated-run design, statistical testing, parameter sensitivity, random seeds, code, instances, pseudocode, or fair baseline control. This pattern should usually be repaired before transfer. The next reviewers will not forgive missing artifacts just because the target journal changed.

TEVC transactions-depth pattern: the manuscript reads like an expanded conference paper: more experiments, but not enough explanation, theory, ablation, limitations, failure analysis, or reproducibility detail. If the paper cannot be deepened, Applied Soft Computing or a domain journal may be more honest than another transactions venue.

The better retargeting move is usually more specific: identify the reusable contribution, choose the reviewer pool, rebuild the abstract around that contribution, then decide whether the next journal's format, evidence burden, and reader expectations fit.