Skip to content

ICML — writing guide

Make the learning question and the comparison contract explicit. A reader should be able to identify the new knowledge, the assumptions or controls supporting it, and the setting in which it holds. A new architecture, diagnostic study, theorem and position argument need different evidence—not the same decorative outline.

This guide draws on the ICML 2026 oral program, including Main and Position Paper tracks. It separates official requirements, inspected examples and editorial recommendations. An accepted-paper corpus cannot establish which writing choices caused acceptance.

Learn the patterns before inspecting individual papers

Section titled “Learn the patterns before inspecting individual papers”

The corpus atlas provides a searchable paper ledger, caption counts and approximate section spans. The contribution-type guides turn those observations into conditional outlines and artifact plans. The visual gallery shows examples directly, with conditions and caption checklists.

Frame one question, then expose the intervention

Section titled “Frame one question, then expose the intervention”

Name the problem and closest comparison before listing components. If the contribution is empirical, formulate questions that could return an inconvenient answer. If it is theoretical, introduce the setting and assumptions before the guarantee. Keep a conjectured explanation distinct from a controlled intervention.

The midtraining study uses question-led sections and compact findings. Its representation analysis is explicitly descriptive; it does not turn a similarity matrix into proof of a new causal mechanism.

An architecture diagram should expose data, representation, computation and training signals. For a procedural method, include a small execution trace or pseudocode where ordering, state or credit assignment matters. Define all axes and symbols in the caption. Do not use a theorem box merely to give an empirical claim a formal appearance.

ThreadWeaver pairs a concrete token trace with a request timeline. WeDLM separates physical token order from logical positions and shows the corresponding attention pattern. These are explanations of computation, not generic pipeline decoration.

Make every performance comparison interpretable

Section titled “Make every performance comparison interpretable”

State the dataset or workload, evaluation unit, metric direction, sampling and resource budget near the result. Separate same-backbone controls from comparisons to externally reported systems. Show uncertainty where the experiment supports it, retain non-winning outcomes, and distinguish an average of ratios from a ratio of averages.

The ThreadWeaver evidence study separates token latency, measured wall-clock latency and the extra GPUs used. TokSuite explains why a fixed token budget does not imply equal raw-text exposure and checks an alternative budget. Those details are part of the argument, not optional fine print.

Write the tested claim, not its most exciting interpretation. Distinguish observed, consistent with, hypothesized and proved. Reuse the same term for the same object across the abstract, equations, figures and conclusion. Explain the consequence of a result rather than repeating a table row.

Keep exceptions beside the claim they qualify. A frontier can reveal a useful trade-off without universal superiority; a controlled model collection can improve attribution without isolating every design choice.

Treat supporting material as a navigable evidence record

Section titled “Treat supporting material as a navigable evidence record”

Keep the defining method, essential assumptions and main evaluation contract in the body. Route readers to full proofs, exact prompts, data construction, hyperparameters and extra conditions through named appendix references. A contents list helps long appendices; a collection of unreferenced tables does not.

ICML 2026 permits an attached appendix in the same PDF, including a one-column appendix. Its rules page distinguishes eight initial content pages from nine final content pages and records conflicts between current instructions and older template wording. Do not infer submission allowances from a long published PDF.

A position paper should state a contestable thesis, define its scope, address substantial alternative views and explain practical implications. It need not invent a model or benchmark to resemble a Main Track method paper. ICML 2026 specifically requires an Alternative Views section in the main body and a Position: title prefix; its impact-statement and lay-summary exceptions are edition-specific.

Use the position drafting route for a claim–evidence matrix, alternatives and a concrete action plan. These editorial suggestions are separate from the official requirements.

Each edition keeps its own inventory, source versions, rule conflicts and measurements. The conference overview provides reusable lessons; the edition pages provide the evidence behind them.

ICML submission deadlines, event periods and locations are listed below, independently of the inspected writing editions. Unannounced dates are not estimated.

Dates for ICML only, newest edition first. Submission dates can fall in the previous calendar year. AoE means Anywhere on Earth (UTC−12); other stated timezones are retained. Reconfirm official instructions before submission or travel.

Compare all conferences on the Research Writing timelines →

ICML 2027

Submission
Not announced
ConferenceSouth America — city and country unannounced
Dates not announced
  • Only the region is announced. Submission deadlines, event dates, city, country, and venue were not announced in the official sources checked; no dates are extrapolated from 2026.

Checked Oct 21, 2026.

ICML 2026

Abstract
AoE (UTC−12) · clock time not separately specified
Full paper
AoE (UTC−12) · clock time not separately specified
ConferenceSeoul, South Korea
Jul 6–11, 2026COEX Convention & Exhibition Center
  • The call for papers explicitly gives the abstract cutoff as January 24, 2026 at 12:00 noon UTC and the full-paper cutoff as January 29, 2026 at 12:00 noon UTC. The listed AoE dates are preserved without rounding those UTC cutoffs to 23:59.
  • The displayed event period includes tutorials/expo on July 6, the main conference on July 7–9, and workshops on July 10–11.

Checked Oct 21, 2026.

  1. Write one bounded contribution sentence and the closest alternative it changes.
  2. Map each claim to a control, theorem, measurement or substantive argument.
  3. Sketch only the diagrams and result displays needed to make those links intelligible.
  4. Check budget definitions, metric units, uncertainty and exceptions against every headline.
  5. Audit the compiled PDF and the exact edition’s official instructions before submission.

Use the argument worksheet and structure and visual-design workbench for the drafting pass.