Rejected from IEEE TPWRS? Choose the Next Journal

The current IEEE PES Author's Kit defines TPWRS scope across power-system analysis, dynamics, operations, and planning, while explicitly excluding several topics that belong elsewhere. Use that boundary before interpreting “out of scope” as a quality judgment.

Diagnose whether the TPWRS rejection is about scope, evidence, or operational value.

The current TPWRS publication page states that a rejected paper should not be resubmitted without substantial revision, may not be resubmitted sooner than three months after rejection, and is treated as a new submission. It also states that a second rejection closes further resubmission and that authors must briefly explain modifications in the letter to the editor. Verify the live policy before acting because requirements can change.

If routing from one IEEE PES journal to another, the same page requires disclosure of the original PES journal and manuscript reference in the letter. Do not hide the prior submission. A new journal assignment is not permission to ignore the prior technical record.

A desk rejection is mainly evidence about scope, audience, contribution, or visible fit. A post-review rejection also carries reviewer comments about methods, models, controls, and evidence. A transfer offer is an administrative option, not an editorial endorsement. Treat these as three different records before deciding what to revise.

IEEE Transactions on Smart Grid

Best for: digital infrastructure, distributed intelligence, sensing, communication, data, cyber-physical interaction, or advanced distribution operation as the central contribution.

Think twice if: the core is conventional bulk-system planning or operation. Reframe around a real smart-grid capability and include communication, observability, latency, privacy, and security assumptions when they matter.

IEEE Transactions on Power Delivery

Best for: equipment and delivery-system work, including protection, insulation, lines, cables, substations, power quality, and electromagnetic behavior.

Think twice if: the novelty is a market, planning, or system-operation method. The TPWRS Author's Kit excludes several delivery topics, but a scope correction should not relabel an optimization paper as equipment research.

IEEE Transactions on Sustainable Energy

Best for: renewable generation or storage integration that is indispensable to the problem, method, and system consequence. The official scope covers design, implementation, integration, and control.

Think twice if: sustainability is only a test-case label for a generic algorithm. Test variability, network constraints, realistic device behavior, and the interaction with transmission or distribution operation.

IEEE Transactions on Energy Markets, Policy and Regulation

Best for: market architecture, policy, regulation, incentives, risk allocation, and participant behavior in power and energy systems.

Think twice if: the novelty is primarily a network-control or device method. If network feasibility is modeled, make the economic mechanism and institutional consequence central rather than presenting another dispatch algorithm.

Applied Energy

Best for: integrated power, buildings, transport, heat, industry, storage, fuels, or sustainability analysis with an application-level energy consequence.

Think twice if: the paper remains specialist power-system theory with thin application evidence. A broad energy narrative cannot replace network constraints, realistic operation, or validated performance.

Electric Power Systems Research

Best for: sound contributions across electric-power-system analysis, planning, operation, control, and emerging technologies whose audience is the broad specialist community.

Think twice if: breadth is being used to preserve unrealistic assumptions, weak comparisons, or incomplete validation. The grid experiment still needs to support the stated scope and consequence.

Map every decision-letter criticism to the network input, equation, constraint, scenario, baseline, figure, and claim it affects. This prevents a prose-only revision that leaves the grid experiment unchanged.

Revise the title, abstract, introduction, network model, equations, methods, algorithm, scenario definitions, baseline tables, result figures, supplementary material, data and code availability statement, discussion, and conclusion together. The system assumptions and claim boundaries must remain consistent across every component.

1. Define the system job: name the operator, planner, market participant, device controller, or policymaker and the decision improved.
2. Audit network physics: document topology, parameters, power-flow model, dynamics, devices, controls, and approximations.
3. Audit information: state what is measured, forecast, communicated, delayed, private, missing, or estimated.
4. Stress uncertainty: use calibrated distributions, temporal and spatial dependence, forecast errors, tails, and out-of-sample periods.
5. Test contingencies: include credible outages, limits, corrective actions, and security criteria relevant to the claim.
6. Match baselines: equalize network data, scenarios, constraints, tuning, compute, and stopping rules.
7. Scale honestly: vary network size, horizon, scenario count, device penetration, and runtime; report infeasibility and failure.
8. Validate behavior: compare with trusted tools, historical operations, hardware, field data, or independently implemented references.
9. Quantify tradeoffs: report reliability, cost, emissions, fairness, robustness, and computational burden where applicable.
10. Bound the claim: state where approximations, data access, control authority, or market rules make the method unsuitable.

Audit assumptions, contingencies, and operational coverage before rerouting.

Appeal only when a documented factual or procedural error could change the decision. Point to the exact scope provision, supplied evidence, or misunderstood premise. Do not use appeal as a way around the current three-month and substantial-revision rules.

Choose later TPWRS resubmission only when the revised work still squarely belongs to power-system analysis, operation, dynamics, or planning and the technical response is substantial. Treat the second-chance limit seriously.

Choose another journal when the system layer or audience is different. Disclose prior PES submission details when current IEEE policy requires it, and never submit the manuscript to another journal in parallel.

In our pre-submission review work with TPWRS manuscripts, we trace the network model, information set, equations, constraints, scenarios, baseline tables, result figures, code record, and operational claims before judging journal fit. These are qualitative manuscript patterns, not claims about private IEEE decisions or acceptance rates.

Pattern 1: a network assumption creates the result

In TPWRS candidates, the method often appears robust because congestion, reactive power, losses, ramping, device dynamics, reserve, or contingency constraints are absent from the equations. We rerun the central result as assumptions are restored, record infeasibility, and compare the affected tables and figures. The contribution is credible only if the advantage survives or the operating boundary is stated in the abstract and conclusion.

Pattern 2: perfect information is mistaken for deployability

Another TPWRS pattern gives the algorithm exact loads, renewables, prices, and outages while the discussion claims operational use. We reconstruct the information available at each decision time, then impose forecast errors, delayed measurements, missing data, and scenario shift. We examine how controls and violations change, not only expected objective value. The revised methods and abstract must say what information exists before action.

Pattern 3: the baseline is not allowed to compete

TPWRS baseline tables can give the proposed optimizer or learner better forecasts, more scenarios, a longer time budget, or tailored constraints. We equalize the information and compute budget, tune strong baselines, use the same contingency set and stopping rules, and report matched-feasibility performance. We keep nonconverged runs in the result record. A smaller but real benefit is more useful than an inflated one.

Pattern 4: the objective improves while the system becomes less trustworthy

The final TPWRS pattern is an expected-cost result that improves while violations, tail risk, instability, unfair curtailment, or corrective-action burden rises. We report distributions, worst credible cases, feasibility, reliability metrics, and operator interventions across the supplementary scenarios. We then make the discussion distinguish an optimization gain from an operational improvement. The destination follows the system consequence, not the favored objective.

Choose a destination when the revised abstract can state the system problem, information available, physics retained, uncertainty and contingencies tested, baseline contract, operational consequence, and boundary. Recheck the live IEEE PES policy, scope, page limits, fees, and disclosure requirements before submission.

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.