Get your Journal of Computing in Civil Engineering paper right the first time: a ready-made structure with the right abstract and citations, so editors see your science, not formatting slips.
4.9
Authored by Sumalatha Gangadhar | Published on 17 August, 2026
Submitting to Journal of Computing in Civil Engineering goes smoothly when your draft already matches the journal's own rules. Editors screen new manuscripts against the Journal of Computing in Civil Engineering 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 Journal of Computing in Civil Engineering. 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 Journal of Computing in Civil Engineering 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 Journal of Computing in Civil Engineering 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 Journal of Computing in Civil Engineering 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 the journal's submission system.
| Element | J Computing Civil Eng requirement |
|---|---|
| Abstract | Structured abstract required with 5 mandatory sections: (1) Background - context, motivation, and research gap; (2) Purpose/Hypothesis - research question(s) addressed; (3) Design/Method - research design, data collection, and analysis methods; (4) Results - key findings; (5) Conclusions - key conclusion(s) based on findings. No word limit explicitly stated in guidelines, but mathematics and references are not permitted in the abstract |
| Main text | Technical Papers: maximum 30 double-spaced manuscript pages including references, figures, tables, appendices, and captions. Technical Notes: maximum 7 double-spaced manuscript pages. Case Studies: maximum 30 double-spaced manuscript pages. State-of-the-Art Reviews: maximum 45 double-spaced manuscript pages. Data Papers: maximum 30 double-spaced manuscript pages |
| Declarations | Ethics approval/consent as applicable; competing interests; funding; data availability |
| Figures/tables | Publication-ready; cited in order |
| Supplemental | Upload separately when used |
| Keywords | - The official ASCE author guidelines do not explicitly mention keyword requirements for manuscript submissions |
| References | Author-date citation style (ASCE standard). In-text citations use author last name(s) and year (e.g., Smith 2004 or Smith and Jones 2004). References section lists all references alphabetically by last name of first author. References must be published works only, with exceptions for theses, dissertations, and 'in press' articles |
| Peer review | Single-blind peer review. Reviewers remain anonymous to authors, but author identities are known to reviewers. The official ASCE guidelines state that 'The names of reviewers shall not be released by the editors or editorial staff,' confirming single-blind process where reviewers remain anonymous while reviewing manuscripts with author information visible |
| Submission | ascelibrary.org/submit/jccee5 |
Read the Journal of Computing in Civil Engineering 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 Journal of Computing in Civil Engineering in under a page.
Skim two or three recent J Computing Civil Eng 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 Journal of Computing in Civil Engineering journal page requires it. Disclose any preprint or conference version with identifiers in the cover letter.
Do one focused pass against the Journal of Computing in Civil Engineering guide for authors: scope, length, reference style, required declarations, and figure quality. Then submit through the journal's submission system.