Submission essentials
IEEE Transactions span electrical engineering, computing, automation, communications, signal processing, remote sensing, biomedical engineering, and more, with many specialized titles. Reviewers expect a reproducible technical contribution: not only a new algorithm or system, but clear training details, data splits, implementation environment, compute budget, and fair comparison with strong baselines. Impact factors and annual volumes differ by title, but professional writing and layout are a shared bar — sloppy formatting often creates a poor first impression at initial screening.
Desk rejection is often tied to: topic clearly outside Aim & Scope; a report-like draft that cannot stand alone as a journal article; missing key experiments or overclaimed conclusions; or non-IEEEtran, non–US Letter files that complicate production. If the paper extends a conference version, state the increment explicitly in the Introduction or a dedicated paragraph (new theorems, experiments, theory) and summarize it in the cover letter to reduce duplicate-publication concerns.Associate Editors pick reviewers using the problem statement and contribution list in the abstract and Introduction. State the application setting and metrics early — avoid leaving readers unsure what new problem is solved until page three. The IEEE community values notation tables, algorithm pseudocode, and figure–text consistency: one symbol, one meaning across text, captions, and equations.
Review cycles often run months to over a year; Major Revision is common. Format alone rarely causes rejection, but issues explode at camera-ready: incomplete references, low-res figures, or noncompliant biography/photo delay publication. Adopting the latest template for the target Transactions from the first submission saves total time.
Open access and copyright: IEEE offers several publishing models; OA, APClevels, and copyright terms depend on choices at submission and in the agreement — align with your institution and funders before acceptance. Data and third-party materials: cite public datasets and licenses; explain authorization for non-public data. Third-party figures or code must respect license and attribution, or you may need changes or withdrawal before publication. Headers and manuscript identity: for anonymized review, remove draft watermarks, author metadata in filenames, and identifying LaTeX comments. Some systems use a separate title page; follow the journal’s anonymization rules in the main PDF.Formatting in detail
The following summarizes typical IEEE Transactions expectations; if a specific Transactions title conflicts, follow the IEEE Author Center and that journal’s current Instructions for Authors.
Document class and layout- Use the IEEEtran class.
- Double-column layout; single-column previews are for internal use only if the journal allows.
- Paper: US Letter (8.5×11 in); avoid A4 unless the guide explicitly permits it, to prevent measure drift.
| Edge | Value |
|------|-------|
| Top | 0.75 in |
| Bottom | 1 in |
| Left | 0.65 in |
| Right | 0.65 in |
Do not load geometry or change margins without checking the official template; if the journal supplies a dedicated .cls or example .tex, use that.
- Body: Times New Roman 10 pt (template defaults).
- Title: ~24 pt via IEEEtran — avoid overriding font commands in the preamble casually.
- Section titles, figure and table captions: follow template hierarchy consistently.
- Main text often caps around 14 pages (whether references, author bios, and appendices count is journal-specific).
- Extra pages may cost money or require cuts; move some figures or proofs to supplements if allowed.
Manuscripts usually include: Abstract, Index Terms, Introduction, References. Other sections (e.g. Literature Review, Proposed Method, Experiments, Ablation, Discussion, Conclusion) follow field norms. Some titles require Ethical Statement, Author Contributions, Funding, etc. — use the author checklist.
Figures and multimedia- Prefer vector formats (PDF/EPS); for raster photos, mind DPI and color space.
- Under two columns, complex figures may use the spanning float environment (
figure*in LaTeX); limit floats to avoid a fragmented layout. - Line styles and markers should remain distinguishable in grayscale, matching many reviewers’ print habits.
- Subfigure labels must match the text; if color is online-only, captions should remain interpretable in gray print.
Abstract requirements
- Length: usually ≤250 words.
- Standalone: no equation numbers, figure references, or
[1]-style citations; do not rely on the appendix. - Suggested flow: one sentence of context → problem and motivation → core method (avoid hyperparameter dumps) → key quantitative results → one sentence on impact or application.
- Index Terms: about 3–8 items covering task, method, and data/scenario for IEEE Xplore discovery; avoid filling slots with overly generic terms.
Citations and references
- Style: IEEE numbered citations — order by first appearance, bracketed form such as [12].
- BibTeX: use IEEEtran-compatible styles; for conferences, fill booktitle, address, month; for journals, check volume, issue, pages, year.
- DOI: include when required or available for linking and production.
- arXiv and forthcoming work: label status per IEEE and the target journal; do not cite unpublished work as formally published.
- Repeat citations: same number for the same source; do not create duplicate numbered entries.
Common formatting mistakes
- Not using official IEEEtran, so section numbering, theorem environments, and caption styles diverge from the series.
- A4 or custom marginsinstead of US Letter with 0.75 / 1 / 0.65 in combinations.
- Abstract over 250 words or missing Index Terms.
- Reference order out of sync with text, or author–year mixed with numbered style.
- Two-column figures shrunk so axis labels and symbols are unreadable.
- Double-blindversions that still leak identity (first page, acknowledgments, project IDs).
- Algorithm and equation numbersnot updated after moving paragraphs, breaking cross-references.
Choosing a Transactions title and scope
Many Transactions exist; similar-sounding areas may have multiple journals (e.g. imaging, ML, robotics). Read Aim & Scope and Recent Articles for the last two years to match narrative style: some titles stress theory, others systems and field tests. Mis-targeting lengthens decisions; after a suggested transfer, you often reformat — correct templates early reduce rework.
Conference-to-journal extension
Many groups extend IEEE conference papers. Editors look for substantial extension: new theory, broader experiments, new datasets, or stricter controls. Use a subsection or clear heading for “Contributions beyond the conference version” and cite the conference version properly. Hiding a public conference version raises integrity concerns.
Supplements, code, and reproducibility
Some Transactions encourage supplementary PDFs, code, or data readmefiles. Proofs and extra plots that do not fit the 14-page core can go to Supplementary Materials, but main conclusions must remain self-contained in the main text. If you share code, keep links active during review and document dependencies — “cannot reproduce” hurts reviews.
English usage and IEEE style
IEEE papers often use passive voice and third person for methods, though some venues accept “we” — follow the journal. Avoid stacked subordinate clauses; give intuition before dense notation. Spell out abbreviations at first use (e.g. deep neural network (DNN)). Captions should be self-contained: readers should understand variables from the figure and caption alone.
Ethics, conflicts, and funding
Disclose human subjects, private data, or dual submission as required.Conflict of Interestand Fundingformatting must match the template; grant numbers and acknowledgments should match award letters to reduce proof-stage disputes.
LaTeX tips
Use official documentclass options (e.g. journal) and do not toggle twocolumn/onecolumn unless allowed. Prefer BibTeX + IEEEtranBST over hand \bibitem. Large tables may use table*; place \label after \caption to avoid wrong numbering. Compile enough times to stabilize references and cross-references.
Review timelines and revisions (general)
Cycles vary from months to over a year. For Major Revision, reply point-by-point and highlight changes; if you cannot meet a request, explain honestly with alternative evidence. Minor Revision still needs full checks on template compliance and figure clarity.
IEEE Transactions vs Letters / Magazine
Short, focused contributions may fit IEEE Transactions Letters; Magazine emphasizes tutorials and surveys with different conventions. Compare Recent Papersbefore choosing a venue to avoid repeated resubmission.
How to convert to IEEE Transactions format with AutoSCI
- Upload your paper — PDF or Word
- Select the template — IEEE Transactions
- Export in one click — LaTeX, PDF, or Word
AutoSCI applies the formatting details so your file aligns with IEEE Transactions expectations.
These steps pair well with internal prescreening and language editing to shorten time-to-submission.
Pre-submission checklist
Before clicking Submit: template version matches the target Transactions download; PDF is US Letter and two-column; abstract ≤250 words; Index Terms present; IEEE numbered style throughout; figures clear at 100% zoom and in print preview; author order and affiliations match the system; ORCID, cover letter, highlights, and graphical abstract per the journal list. None of this guarantees acceptance, but it cuts format-only revision rounds.
Build and versions: confirm your TeX distribution compiles the official example with minimal warnings; for online editors, check font embedding and image paths. Submission system: some portals flag PDF versions or metadata — download the system-generated preview and recheck. After acceptance: publishers may request high-resolution figure sources separately — archive vector sources and consistent naming from day one.Authoritative policy updates: IEEE Author Center and the target IEEE Transactions journal page.
If the target title updates its LaTeX package or bibliography style during the year, treat the package README and example .tex as the final word.