Format your manuscript to the Smart Cities requirements — abstract, MDPI numbered references, and required declarations — and submit through the MDPI Submission System (SuSy) without a formatting rejection.
4.6
Authored by Sumalatha Gangadhar | Published on 24 August, 2026
Most manuscripts sent to Smart Cities don’t stumble on the science — they stumble on formatting caught at the first editorial check. This template is built around Smart Cities’s actual requirements — its abstract rules, MDPI numbered references, and the required declarations — so your submission clears screening on the first pass. Everything below tracks the Smart Cities author guidelines; check it directly if anything looks out of date by the time you submit.
It’s a manuscript shell set up to Smart Cities’s specifications for smart cities and urban technology. Smart Cities is published by MDPI. The shell covers the title page, the abstract, a body in Introduction, Methods, Results, and Discussion (IMRaD) order, and a reference list in MDPI numbered style.
Start with the title page (authors, affiliations, and ORCID iDs). The abstract is a single-paragraph abstract of about 200 words. The body follows Introduction, Methods, Results, and Discussion (IMRaD), and the reference list uses MDPI numbered. Close with the declarations block: ethics approval, conflict of interest, funding, and data availability.
The details that trip up most first submissions: an abstract that runs past ~200 words, references not in MDPI format, and not budgeting for the open-access APC. Beyond that, match your article type’s specific limits rather than assuming the defaults apply, keep MDPI numbered formatting consistent from the first draft, and submit only through the MDPI Submission System (SuSy) — email submissions aren’t processed.
The shell mirrors what Smart Cities’s editorial staff check first: abstract format and length, MDPI numbered reference formatting, and a complete declarations block. For the journal’s full aims and scope, see the Smart Cities journal home page. This is a fully open-access title, so budget for the article-processing charge (check the current APC and any discount before submitting). Manuscripts go in through the MDPI Submission System (SuSy), which also tracks your paper through peer review.
| Element | Smart Cities requirement |
|---|---|
| Abstract | a single-paragraph abstract of about 200 words |
| Main text | Introduction, Methods, Results, and Discussion (IMRaD) |
| Declarations | Ethics approval, conflict of interest, funding, and data availability |
| Figures / tables | Captioned, cited in order; check format and resolution rules in the guide |
| Supplemental | Large datasets, extra tables, code — uploaded separately and cited in text |
| Submission | the MDPI Submission System (SuSy) |
Read the Smart Cities author guidelines once before drafting and once before upload. Draft the abstract after your results are stable so it matches the paper. Set MDPI numbered as your reference style before adding a single citation — retrofitting it later is where errors creep in.
Skim two or three recent Smart Cities papers to calibrate depth, structure, and figure style. State your contribution in the first two paragraphs, not on page ten. Write a data-availability statement that names a real repository rather than a placeholder, and disclose any preprint or conference version with identifiers in your cover letter. Confirm current open-access pricing and any institutional agreement before committing to a fee.
Do one focused pass against the Smart Cities author guidelines: scope fit, abstract format, length, MDPI numbered references, required declarations, and figure quality. Re-check the items that most often cause a bounce here — an abstract that runs past ~200 words, references not in MDPI format, and not budgeting for the open-access APC. Then submit through the MDPI Submission System (SuSy).