Write and submit a paper

Move a research manuscript from a venue template through drafting, coauthor review, final checks, and submission.

Use this workflow when the required result is a LaTeX manuscript and submission package. The venue's current author instructions remain authoritative; CorTeX helps you keep the source, collaboration, compilation, and recovery steps in one project.

For literature you read alongside the draft, the personal Library can collect PDFs and bring citations into the project after sign-in. The reading collection remains personal when you share the manuscript; a Template library starter is a separate choice for the manuscript’s format.

Start from the required format#

1. Read the venue's current author instructions, including the submission stage.
2. Search the template library by venue or publisher and verify the selected starter's official source. Create a project from it, or import the current kit as a ZIP.
3. Open the paper's root file and confirm the engine and TeX Live snapshot. If several papers share the project, set its opening default separately.
4. Compile before changing anything and save a named Template baseline in Version history.

Do not remove unfamiliar class options, style files, or bibliography settings until the venue instructions explain their purpose. A clean baseline separates template problems from changes introduced while writing.

Organize the manuscript#

Keep one main file and split longer sections, figures, and bibliography data into clear project paths. A practical starting tree is:

main.tex
sections/introduction.tex
sections/methods.tex
sections/results.tex
figures/
references.bib

Follow Split a LaTeX project into files before several coauthors begin editing. Add figures with descriptive captions and alt text, and keep literature records in the bibliography system required by the template.

Draft and review in milestones#

Compile after a coherent edit rather than waiting until the entire paper is assembled. Resolve the first current Problem, verify cross-references and citations, and make sure the visible PDF is not the last successful result from older source.

Invite coauthors with the smallest role and file scope that lets them work. Use comments for questions and decisions, and save named versions before a broad rename, assistant patch, response-to-reviewer revision, or submission candidate. Resolve a comment only after its requested change is represented in the source.

Prepare the candidate submission#

Before the deadline:

1. Read the current venue checklist again, including anonymity, page count, supplemental files, fonts, and bibliography rules.
2. Compile from a clean project state and inspect every page at normal size.
3. Check warnings, unresolved references, figure and table placement, metadata, and accessible descriptions.
4. Save a named version such as Submission 1.
5. Export the exact PDF and source package the venue requests.
6. Open the downloaded files outside CorTeX before uploading them.

Your submission is ready when the downloaded artifact matches the venue requirements and can be traced to a named project version. Inspect that file, even if the in-browser preview looked correct. Use the submission package checklist for the final preflight.