icml-camera-ready

ICML Camera-Ready

The camera-ready is the version the world's readers will see, published on PMLR alongside the original submission, reviews, and discussion. This fact has two consequences: the core content of the paper must remain consistent with what the reviewers saw, and every commitment made in the rebuttal can now be publicly verified.

Communicate with users in their language. Run python scripts/init_workspace.py --root <latex-root> --skill icml-camera-ready, read .icml/venue_facts.md Section 7 (refresh for the current year: camera-ready rules change every year) as well as .icml/rebuttal/promises.md(if it exists).

Basic rules

• Do not change the core content of the paper(claims, main results, methods) relative to the reviewed version. Improvements, clarifications, promised supplementary content, and corrections are all acceptable. If the authors want to make substantive changes, flag them and let them decide whether Program Committee Chair (PC) approval is needed.
• Author list: The order may change, but authors cannot be added or removed; it must match OpenReview. Title changes beyond minor edits require Program Committee Chair permission.
• Do not fabricate numbers or citations(same rules as icml-write and icml-cite).
• Authors handle their own accounts: uploading, signing forms, registering, filling out OpenReview. You are responsible for preparing all materials and giving precise operating instructions.

Workflow

Use references/camera-ready-checklist.md to track progress in .icml/camera_ready.md .

1. Deadlines. Ask for the current year's camera-ready deadline and related dates (2026: camera-ready May 28 AoE, presentation questionnaire May 11). Work backward from them; format checkers and forms take time.
2. Commitments. For each line in promises.md , verify whether it is in the paper (location), and that it matches exactly what was said in the rebuttal (same numbers, from the ledger). Report any missing items. If there is no promises file, reconstruct one from the published rebuttal text.
3. Use the extra page to address reviewer feedback. The main text can be extended to at most 9 pages. Prioritize commitment items and the most common reviewer confusions (run icml-write's paragraph and sentence checks on the revised text). Do not use it for new claims.
4. Deanonymization. \usepackage[accepted]{icml20XX}; the real \icmlauthor and \icmlaffiliation entries match the OpenReview profiles; co-first-author markers; \icmlcorrespondingauthor；\printAffiliationsAndNotice{}(or with {\icmlEqualContribution}); acknowledgments (unnumbered, before the references; funding, grant numbers, computing resource providers, assisting personnel); restore self-citations to first person only if the authors want this; replace anonymous repository links with public archived repositories; remove the "Anonymous" placeholder. Ask the authors for exact names, affiliations, and funding text; never guess.
5. Conflict-of-interest disclosure statement. Ask the authors directly whether any author has a financial or other material conflict of interest (for example, the paper evaluates a model built by an author's company). If so, draft a paragraph titled "Conflict of Interest Disclosure" in the last paragraph of the introduction, stating the authors' initials, the company, and the model. If not, include nothing. Industry employment alone does not constitute a conflict of interest. The authors must confirm the final wording.
6. Impact Statement. Still required (main conference papers). Revisit it based on reviewer comments or ethics comments.
7. References. If icml-cite's check_bib.pyis installed, run it; otherwise check entries manually. Fix every item listed by OpenReview under "Reference Correctness Check". Replace arXiv citations with published versions when a peer-reviewed version exists. Preserve capitalization; update author names and conference names.
8. Lay summary。 Use references/lay-summary-guide.md to draft; give the authors two versions; they choose and edit.
9. Mechanical checks. python scripts/check_submission.py --tex main.tex --pdf main.pdf --mode camera-ready Then compile cleanly (no ??), PDF ≤ 20 MB, US Letter, correct title and title capitalization, abstract as a single paragraph of about 4–6 sentences, vector figures, color-vision-deficiency-friendly charts, and if the source code will be released, remove TL;DR and TODO comments from it.
10. Official format checker. Authors upload the PDF to the ICML paper checker (2026: papercheck.icml.cc) and iterate until it passes; it returns a code for the OpenReview form. Fix every issue it reports; rerun step 9 after each fix.
11. OpenReview form. Prepare exact text for: title and abstract (exactly matching the PDF; minimal TeX math, no custom macros, use TeX commands for accents), lay summary, code URL, author order. List the files to upload (PDF, PMLR publication agreement signed by the corresponding author). Remind them about the ICML publication license (signed by one author), recording permission for oral presenters, and registration requirements (see venue facts).
12. Release. If code/data will be made public: remove .icml/ notes, credentials, internal paths; add a license and README; make links archivable long-term. Confirm with the authors.

After the conference

ICML allows one post-conference revision window for minor corrections. Use the same checks; do not change the core content.

Files

• scripts/check_submission.py — compliance check (--mode camera-ready）。
• scripts/init_workspace.py — shared workspace.
• references/camera-ready-checklist.md — full checklist (copy to .icml/camera_ready.md）。
• references/lay-summary-guide.md — how to write a lay summary.
• references/icml-venue-facts.md、references/workspace-contract.md — shared files.