Rejected from IEEE Transactions on Power Electronics? Where to Submit Next

Archive circuit revisions, component part numbers, parasitic assumptions, magnetic design, gate drive, PCB layout, sensing chain, control code, firmware commit, protection settings, simulation models, test equipment, calibration, raw waveforms, switching conditions, thermal images, losses, efficiency calculations, failed devices, excluded runs, and repository state.

Write the contribution as power-conversion problem -> topology or control idea -> model and assumptions -> implementation -> operating envelope -> hardware evidence -> losses and thermal behavior -> dynamic or grid consequence -> application decision. Mark each link as derived, simulated, measured, estimated, or missing.

Diagnose the TPEL rejection before rerouting.

A desk rejection often concerns scope, generic PELS interest, obvious novelty weakness, article type, or missing hardware evidence. TPEL's official scope explicitly excludes work where power-electronics content is not sufficient and demonstrated.

A post-review rejection is a technical audit. Incorrect device models, unmodeled dead time, unfair switching frequency, missing component stress, unstable edge cases, incomplete protection, measurement uncertainty, and selective waveforms will follow the paper.

A transfer offer, forwarding option, or journal suggestion can reduce administrative work, but it does not repair the manuscript or guarantee review. Confirm exactly what files and reports move and whether a revised package can replace them.

IEEE JESTPE

Best for: a revised paper addressing an emerging application, selected technical topic, or special-section theme with substantial power-electronics content. Its remit rewards timely areas and collaboration across PELS and IAS.

Think twice if: the paper is being forced into a call by changing vocabulary. The technical object and evidence must actually serve the selected topic.

IEEE Open Journal of Power Electronics

Best for: broad PELS work where immediate open access is important. The official scope covers components, conversion, control, systems, tools, applications, tutorials, and surveys.

Think twice if: hardware validation, originality, or ethics concerns remain. Open access changes availability and cost, not the scientific floor.

IEEE Transactions on Industrial Electronics

Best for: drives, industrial control, sensing, robotics, automation, power quality, or industrial implementation as the scientific center. Demonstrate the system and operating constraints, not only the converter.

Think twice if: “industrial” appears only as a possible application in the conclusion.

IEEE Transactions on Industry Applications

Best for: work centered on field use, standards, safety, reliability, maintenance, deployment, or industry-specific performance. Real application evidence can be more important than a small peak-efficiency gain.

Think twice if: the prototype never encounters the voltage, load, environment, duty cycle, or protection event of the claimed application.

IEEE Transactions on Power Systems

Best for: grid operation, planning, markets, stability, or system behavior where the converter is a modeled resource inside that question.

Think twice if: the grid case is a small simulation appended to a converter paper. Power-system claims require appropriate network, uncertainty, and operational evidence.

CPSS Transactions on Power Electronics and Applications

Best for: a complete converter, control, component, or application contribution for the broad power-electronics community.

Think twice if: the move is only a selectivity step. The same missing loss analysis, unstable control, or weak hardware comparison can still block publication.

Write an editor test naming the conversion problem, topology or controller, new property, assumptions, implementation, rated and tested envelope, loss evidence, dynamic behavior, and application consequence. If it fits all destinations unchanged, the routing decision is unfinished.

For a converter route, lead with the conversion property and tradeoff. Include switch and passive stress, modulation, losses, volume, control, protection, and fair hardware comparison.

For a control route, define plant model, uncertainty, delay, sampling, saturation, stability, transient tasks, implementation cost, and the baseline controller's tuning budget.

For an industrial application route, specify environment, duty cycle, standard, safety function, reliability, control integration, and field-relevant outcome.

For a power-system route, state network question, model fidelity, operating scenarios, uncertainty, contingency, stability or market measure, and how converter behavior changes the system decision.

Rewrite the title, first two abstract sentences, main schematic, headline waveform, and comparison table for the intended reader. If the route requires hardware, field, or grid evidence absent from the Results, do the work or choose another venue.

For each claimed advantage, record component count and ratings, switching frequency, semiconductor technology, passive volume, cooling, control platform, measurement uncertainty, operating point, comparator tuning, and the condition where the advantage disappears.

Revise the title, abstract, circuit and control diagrams, operating modes, equations, assumptions, device and magnetic design, simulation, prototype, instrumentation, waveforms, efficiency and loss maps, thermal results, dynamics, protection, EMI, baselines, limitations, artifact statement, and conclusion together.

1. State the new conversion property: identify what becomes possible or what tradeoff moves.
2. Prove every operating mode: define intervals, state variables, boundary conditions, and transitions.
3. Model nonideal behavior: include parasitics, dead time, delays, saturation, device characteristics, and losses relevant to the claim.
4. Build a fair comparator: align ratings, devices, switching frequency, cooling, magnetics, control effort, and measurement method.
5. Validate in hardware: test the claim on a prototype or explain the limited inference of simulation or HIL.
6. Report calibrated efficiency: include instrument accuracy, uncertainty, thermal steady state, and full load or voltage maps.
7. Close the loss and thermal budget: reconcile semiconductor, magnetic, passive, auxiliary, and cooling losses.
8. Test dynamics and protection: include steps, start-up, shutdown, faults, saturation, and recovery relevant to use.
9. Bound the application: connect standards, duty cycle, reliability, environment, cost, volume, and maintainability.
10. Package reproducibility: provide parameters, code or models where possible, raw traces, BOM, and enough detail to rebuild the result.

Audit the TPEL evidence chain before resubmission.

Accept an IEEE journal suggestion when the receiving title genuinely owns the revised contribution and the transfer saves useful work. Confirm whether reviews and files move, then upload the corrected package if permitted.

Appeal only when a specific factual or procedural error could change the decision, such as a reviewer claiming no hardware test exists despite a clearly labeled prototype section. Do not use appeal to repeat the novelty claim.

Submit fresh when the center changes to industrial electronics, industry application, a grid question, or an emerging-topic route. Close the prior process. Never submit the same manuscript to another journal simultaneously.

In our review of IEEE Transactions on Power Electronics manuscripts, we inspect circuit operation, models, assumptions, component stress, magnetics, controls, nonidealities, simulation, prototype design, instrumentation, waveforms, loss and thermal budgets, operating maps, dynamics, protection, EMI, comparisons, artifacts, and claims. These are specific rejection patterns grounded in testable manuscript evidence, not private IEEE decisions. Manusights internal analysis maps where equations, simulations, hardware traces, efficiency tables, and application claims disagree. We observe a pattern only when the discrepancy can be tied to a named component or operating condition.

Pattern 1: ideal simulation carries a hardware claim

For IEEE Transactions on Power Electronics candidates, the manuscript may report high efficiency and clean dynamics from ideal switches, lossless passives, perfect sensing, or averaged models. We add device models, parasitics, delay, dead time, magnetic nonlinearity, and a prototype or tightly bounded HIL test.

We align the abstract, model assumptions, simulation figures, prototype section, and conclusion so simulation is not described as demonstrated hardware performance.

Pattern 2: the comparator uses a different design budget

In our IEEE Transactions on Power Electronics review work, the new topology may use faster devices, higher switching frequency, larger magnetics, stronger cooling, or more sensing than the baseline. We construct a component-and-control ledger and normalize ratings, constraints, and optimization objectives.

The corrected comparison often reveals the real advantage: lower stress, fault behavior, wider gain, simpler magnetics, or better partial-load efficiency rather than a universal efficiency win.

Pattern 3: peak efficiency hides the operating envelope

One operating point anchors the headline while light load, voltage extremes, thermal steady state, and transient conditions are absent. We build efficiency, loss, junction-temperature, and dynamic maps across the claimed envelope.

For TPEL candidates, the main comparison table and abstract should cite an envelope or rated condition, not an isolated best point.

Pattern 4: application relevance appears only in the introduction

The paper names EVs, renewables, aerospace, or data centers but does not test the relevant voltage range, isolation, density, EMI, fault, environment, reliability, or control requirement. We either add application evidence or narrow the paper to the converter contribution.

We revise the title, system diagram, test matrix, Discussion, limitations, and conclusion together so the destination can judge the actual object.

Choose the next journal only when the revised abstract can name the conversion problem, topology or control contribution, assumptions, implementation, operating envelope, hardware evidence, loss and thermal behavior, dynamic or grid consequence, application boundary, and failure regime. Verify current scope and submission instructions immediately before upload.

We checked current TPEL and PELS guidance, current destination scopes, the local Manusights owner inventory, and live exact-query results on July 13, 2026. We compared those public boundaries with the converter, control, prototype, and application evidence we inspect in power-electronics reviews. Official sources establish scope and policy; the matrices, ledger, stress test, and review patterns are Manusights analysis.

Read final Search Console data after 14 complete days. At 21 complete days, keep, revise, consolidate, or stop based on indexation, exact-owner impressions, clicks, query fit, and qualified /ai-review starts. The source journal cluster had 10,036 impressions and no preview start; that does not prove exact rejection-query demand.