November 16, 2026

How to Turn Author Guidelines into a Submission Checklist That Actually Ships Your Paper

Most rejection-before-review emails are not about the science. They are about missing statements, wrong file formats, a bypassed reporting guideline, or a contributor form someone forgot to sign. The author guidelines ar

Written byWisPaper TeamAI Research Workflow Team
Editorial illustration for How to Turn Author Guidelines into a Submission Checklist That Actually Ships Your Paper

Most rejection-before-review emails are not about the science. They are about missing statements, wrong file formats, a bypassed reporting guideline, or a contributor form someone forgot to sign. The author guidelines are the contract, but a contract on the journal website is not the same as a working checklist next to your manuscript. This article shows clinicians and medical researchers how to convert a 20-page guideline document into a short, checkable sequence that turns into the final submission packet — with explicit exit criteria at each stage and a worked example you can adapt.

What is the reader actually trying to solve?

You are not trying to “read the guidelines.” You are trying to know, before you press submit, that every journal requirement is represented as a concrete item you can mark done. The underlying problem is translation: guidelines are written as prose, bullets, and nested policy pages, while submission readiness is a flat set of verifiable states. A usable checklist therefore has three properties:

  • It is itemized by submission material, not by the order of the guideline document.
  • Each item has a completion criterion, not just a reminder to “check” something.
  • It includes the evidence weak points — reporting standards, conflict disclosures, registration numbers, and file-specific formatting — because those are where author guidelines demand external documents that the manuscript text alone cannot prove.

ICMJE notes that authors should follow the selected journal’s current instructions for article type, format, required statements, and submission materials. That means the checklist cannot be generic. Two journals in the same specialty may accept the same study but require different abstract structures, different reporting checklists, or different blinding conventions. The checklist is always a per-journal artifact.

How do you diagnose the starting state before you build anything?

Start by separating what you already have from what the journal will require. The most efficient diagnostic is a three-column table:

MaterialJournal requirement (verbatim clue from guidelines)Current state in your draft
Manuscript bodyStructured abstract, ≤300 wordsDraft exists, 412 words, needs cut
Reporting checklistCONSORT checklist required for RCTsNot started
Cover letterRequired to state originality and prior presentationDrafted, missing displacement statement
Data availabilityMust state where supporting data can be accessedPolicy chosen but text not written

Completing this table against the actual guideline document reveals two distinct problems. The first is formatting drift, where your draft violates a countable requirement such as word count, reference style, or abstract structure. The second is missing artifacts, where an entire document or statement does not exist yet. The checklist should treat these differently: formatting drift is fixed inside the manuscript, while missing artifacts generate new files or submission fields. Confusing the two is why many checklists feel long but still fail at the portal.

Which reporting guideline applies to your study?

For medical research, the reporting standard is often a separate checklist with its own line items. The EQUATOR Network organizes reporting guidelines by study type and specialty. The decision is not stylistic; the journal may require a specific guideline and ask you to upload the completed checklist or include a page-number map. Wrong guideline choice means revision, not a minor correction.

To choose correctly, identify:

  1. The primary study design, not the broad topic. A secondary analysis of trial data follows the trial reporting pathway, not a generic observational checklist.
  2. The specialty-specific module, if one exists, such as design-specific modules described by APA JARS for quantitative, qualitative, and mixed-methods research.
  3. Whether the journal asks for a filled checklist, a checklist statement in the methods, or both.

The reporting guideline then becomes a second checklist layered onto the journal checklist. Keep the two separate during preparation. Merge them only at the final verification pass, because the journal checklist answers “did we satisfy this journal” while the reporting checklist answers “did we make the conduct and analysis evaluable.”

What does a submission checklist actually look like?

A submission checklist works best as a short artifact with four columns: checkpoint, artifact, completion criterion, and evidence. The completion criterion is the important column. “Submit cover letter” is a task; “cover letter states originality, prior presentation, and the correct article type in the first paragraph” is a criterion you can verify with your eyes.

The artifact list for a standard clinical research submission typically includes:

  • Manuscript file with the required sections in the required order
  • Title page with all author names, affiliations, and the corresponding author’s institutional email
  • Structured abstract matching the journal’s headings and word limit
  • Keywords using the journal’s controlled vocabulary, when required
  • Main text with line numbers and the journal’s reference format
  • Reporting guideline checklist and page-number map
  • Figures and tables with resolution, file type, and legend requirements met
  • Title and abstract as separate submission fields, when the portal requires them
  • Declaration of interests for every author
  • Funding statement, including grant numbers where applicable
  • Ethics approval and, for interventional studies, trial registration number and registry name
  • Data availability statement
  • Author contributions statement
  • Suggested reviewers, when requested, with names, institutions, and emails
  • Cover letter

ICMJE’s guidance to follow journal-specific requirements for required statements and submission materials supports treating this list as the skeleton you populate from the selected journal. The list is not itself the checklist until each row carries the journal’s exact requirement and your completion criterion.

Worked example: a stepped-wedge trial submission

Consider a focused clinical case: a stepped-wedge cluster randomized trial of a pharmacist-led medication review in three hospital wards, with the primary outcome being the proportion of patients with at least one medication error at discharge within 30 days. The target journal requires a 250-word structured abstract, CONSORT with its cluster extension, trial registration, an ICMJE conflict form for each author, and figures at 300 dpi in TIFF or EPS.

Checkpoint 1 — Article type and format. The journal’s article type is “Research Article.” The structure is Introduction, Methods, Results, Discussion. Completion criterion: manuscript opens with an unstructured title page, followed by a structured abstract with Background, Methods, Results, Conclusions, Trial Registration. Evidence: a 250-word abstract exactly matching those headings.

Checkpoint 2 — Reporting and registration. The trial is registered in a WHO-recognized registry, and the CONSORT cluster extension checklist is completed. Completion criterion: the registry name and identifier appear in the abstract and at the end of the Methods; every CONSORT cluster item has a manuscript page or section named, with no blank cells. Evidence: the completed checklist PDF and two matching registration statements.

Checkpoint 3 — Disclosures and funding. All five authors complete the journal’s conflict form, not just the corresponding author. Completion criterion: the declaration section matches every completed form, and the funding statement includes the grant number. Evidence: five signed PDFs and a one-paragraph funding statement.

Checkpoint 4 — Figure readiness. The two flowcharts and one forest plot are exported at 300 dpi with figure legends on a separate page. Completion criterion: each file opens correctly at the target resolution, legends do not repeat results text, and abbreviations are defined. Evidence: three files named to the journal’s convention.

Checkpoint 5 — Portal mapping. The submission system has separate fields for title, abstract, and keywords. Completion criterion: paste-versions of the title and abstract are free of formatting artifacts, and keywords use the journal’s MeSH-style list. Evidence: a filled portal preview screen.

The completion criteria here are specific enough that a co-author could verify them without reading the full guideline document. That is the test of a good checklist.

Where do you check the evidence strength inside your own manuscript?

Submission readiness is not only about matching formats. At research-evidence level, you should also check that your manuscript distinguishes evidence strength, applicability, indirectness, and limitations. For the stepped-wedge example:

  • Strength comes from the randomized allocation and pre-specified primary outcome, but the number of clusters is small, which limits precision.
  • Applicability is limited to wards with similar pharmacist staffing and electronic prescribing.
  • Indirectness appears if the primary outcome is a surrogate for patient harm rather than harm itself.
  • Limitations include secular trends that a stepped-wedge design can confound with time.

A submission checklist should include one criterion under the Discussion: “The limitations paragraph names the design-specific threat: time trend confounding, and the applicability paragraph names the staffing context.” This prevents a technically complete submission from being weak where reviewers will look first.

How does the checklist fit with your existing research organization?

The checklist is not only a final-week tool. It should sit inside the research environment where the manuscript and its supporting materials already live. If you keep paper versions and notes across folders, the checklist becomes the integration layer. A practical sequence is:

  1. Collect the author guidelines as a saved document in the project where the manuscript lives.
  2. Extract the reporting guideline for the study design and add it to the same project.
  3. Store the current manuscript and the generated submission materials as named files.
  4. Run the verification questions against the papers and references you are citing.

For researchers working inside WisPaper, Research Projects is the natural home for the guideline document, the reporting checklist, and the manuscript versions. The project boundary keeps the submission artifacts together without turning your general library into a folder of drafts. If the manuscript team is still assembling references, My Library is where uploaded papers and saved references live before they become the citation list.

How do you verify the reference list without carrying the risk forward?

One of the least visible failure modes is a reference that looks real but does not resolve. A hallucinated or malformed citation in a BibTeX export can pass an internal eyeball check and surface only when an editor or reviewer tries to find it. Before you lock the manuscript, screen the exported BibTeX against real academic databases. WisPaper’s TrueCite is built for exactly this pass: it checks BibTeX entries against real academic databases to flag references that cannot be traced. Route the final .bib file through this step after the last citation edits, because references often change during co-author revisions.

This is an artifact-level check. Journals may have their own reference style, and citation verification covers existence against academic databases rather than restyling. The separation matters: style check against the journal, existence check against the database. Both appear as separate checklist rows.

How do you gather the guideline details you may have missed?

Author guidelines change, and the version you read six months ago may not match the portal today. Before you finalize the checklist, search the journal’s current instruction pages and any recent accepted examples that show how the required statements are phrased. For the wider literature search and evidence-checking steps, WisPaper search lets you find academic papers through a scholarly search interface, which is useful when you need to confirm how similar studies described their registration or reporting in a target journal. If the checklist work sits inside a broader literature review, Scholar Agent is the area for longer research tasks such as literature reviews, inspiration, or reproduction use cases. Both belong before the final verification pass, not after the portal is open.

When is the submission packet actually ready?

Readiness is a conjunction of five confirmable states, not a feeling:

  1. Every required artifact exists as a named file or completed portal field.
  2. Every completion criterion has been visibly checked by at least one person other than the writer.
  3. Every formatting requirement has been inspected in the final exported file, not just in the word processor.
  4. The reporting guideline has no unresolved items and every item maps to a page or section.
  5. The reference list has passed a database existence check after the final edit.

If all five are true, the packet is ready to upload. If any is only “probably true,” the packet is not ready. The value of the checklist is that “probably” becomes a marked item instead of a vague worry.

FAQs

Create one canonical checklist document and copy the exact requirement language from each page into the relevant row. Do not paraphrase until after the requirement is captured. The canonical document becomes the audit trail, so when two pages conflict — for example, on word limits — the conflict is visible before submission instead of discovered by the editorial office.