Get your IEEE Transactions on Cloud Computing paper right the first time: a ready-made structure with the right abstract and citations, so editors see your science, not formatting slips.
4.2
Authored by Sumalatha Gangadhar | Published on 13 August, 2026
Submitting to IEEE Transactions on Cloud Computing goes smoothly when your draft already matches the journal's own rules. Editors screen new manuscripts against the IEEE Transactions on Cloud Computing guide for authors before peer review, so formatting, structure, and required statements should be right on the first draft rather than repaired during upload. This template sets that structure up for you.
It is a manuscript shell aligned to IEEE Transactions on Cloud Computing. It covers front matter, the abstract the journal expects, a body organized to the journal's article types, and a reference list in the journal's required style. Confirm current scope and article types on the IEEE Transactions on Cloud Computing journal page before you draft.
Prepare the title, authors, affiliations, and ORCID iDs. Write the abstract to the journal's rule and word limit, organize the body to the article type, and apply the required reference style from the first citation. Complete every declaration (ethics, competing interests, funding, data availability) the IEEE Transactions on Cloud Computing guide for authors lists, and cite figures and tables in order.
The common failure modes are formatting or reference style that does not match the guide for authors, missing required statements, and an incomplete portal checklist. Clear all three against the IEEE Transactions on Cloud Computing guide for authors before you submit.
The shell mirrors what editorial staff check first: article-type fit, the abstract rules, required declarations, and the journal's reference style. For more detail see the author resources. When your draft is ready, upload it through ScholarOne (Manuscript Central).
| Element | IEEE Transactions on Cloud Computing requirement |
|---|---|
| Abstract | Regular paper: 100 to 200 words. Short paper: 50 words. Abstract must be self-contained, clearly state the nature and significance of the paper, and must not include mathematical expressions or bibliographic references |
| Main text | Regular paper: 12 formatted pages maximum (double-column, 7.875″ x 10.75″ page with 9.5-point type and 11.5-point vertical spacing), including abstract, references, and author biographies. Short paper: specific limit not stated in general guidelines. Any pages exceeding the 12-page limit for regular papers incur a mandatory overlength page charge (MOPC) of $220 per page |
| Declarations | Ethics approval/consent as applicable; competing interests; funding; data availability |
| Figures/tables | Publication-ready; cited in order |
| Supplemental | Upload separately when used |
| Keywords | Keywords should be selected from the ACM taxonomy provided in ScholarOne Manuscripts. They should be specific and closely aligned with the article's topic. If a closely reflecting word is not found in the ACM taxonomy list, authors may type the appropriate word into the text box |
| References | IEEE style: numbered references in square brackets [1], listed in the order they appear in the body of the paper (not alphabetically). Citations must include full publication information following the IEEE Reference Guide. For journals, in-text reference numbers are formatted in square brackets |
| Peer review | Single-blind. IEEE Transactions on Cloud Computing is explicitly listed as one of the journals that does not offer double-anonymous review option |
| Submission | mc.manuscriptcentral.com/cs-ieee |
Read the IEEE Transactions on Cloud Computing guide for authors once before drafting and once before upload. Draft the abstract after results are stable. Set the reference style before adding citations. Keep a cover letter that states your contribution and fit to IEEE Transactions on Cloud Computing in under a page.
Skim two or three recent IEEE Transactions on Cloud Computing papers to calibrate depth and figure style. Make the novelty clear in the first two pages. Deposit data and code when the policy on the IEEE Transactions on Cloud Computing journal page requires it. Disclose any preprint or conference version with identifiers in the cover letter.
Do one focused pass against the IEEE Transactions on Cloud Computing guide for authors: scope, length, reference style, required declarations, and figure quality. Then submit through ScholarOne (Manuscript Central).