Format your manuscript to the mSystems requirements — abstract, ASM numbered references, and required declarations — and submit through the ASM submission site without a formatting rejection.
4.4
Authored by Sumalatha Gangadhar | Published on 19 August, 2026
Most manuscripts sent to mSystems don’t stumble on the science — they stumble on formatting caught at the first editorial check. This template is built around mSystems’s actual requirements — its abstract rules, ASM numbered references, and the required declarations — so your submission clears screening on the first pass. Everything below tracks the mSystems author guidelines; check it directly if anything looks out of date by the time you submit.
It’s a manuscript shell set up to mSystems’s specifications for systems-level microbiology, microbiomes, and computational microbial ecology. mSystems is published by the American Society for Microbiology (ASM). The shell covers the title page, the abstract, a body in Introduction, Methods, Results, and Discussion (IMRaD) order, and a reference list in ASM numbered style.
Start with the title page (authors, affiliations, and ORCID iDs). The abstract is an unstructured abstract within the journal's limit. The body follows Introduction, Methods, Results, and Discussion (IMRaD), and the reference list uses ASM 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 over the word limit, missing data/strain/sequence accession statements, and references not in ASM format. Beyond that, match your article type’s specific limits rather than assuming the defaults apply, keep ASM numbered formatting consistent from the first draft, and submit only through the ASM submission site — email submissions aren’t processed.
The shell mirrors what mSystems’s editorial staff check first: abstract format and length, ASM numbered reference formatting, and a complete declarations block. For the journal’s full aims and scope, see the mSystems journal home page. mSystems is fully open access; check the current publication fee and member discounts before submitting. Manuscripts go in through the ASM submission site, which also tracks your paper through peer review.
| Element | mSystems requirement |
|---|---|
| Abstract | an unstructured abstract within the journal's limit |
| 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 ASM submission site |
Read the mSystems author guidelines once before drafting and once before upload. Draft the abstract after your results are stable so it matches the paper. Set ASM numbered as your reference style before adding a single citation — retrofitting it later is where errors creep in.
Skim two or three recent mSystems 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 mSystems author guidelines: scope fit, abstract format, length, ASM numbered references, required declarations, and figure quality. Re-check the items that most often cause a bounce here — an abstract over the word limit, missing data/strain/sequence accession statements, and references not in ASM format. Then submit through the ASM submission site.