Model the pipeline before interpreting any single review. ECAI runs a single-round, double-blind conference review with a rebuttal — not a journal-style revise-and-resubmit. The most consequential mental shift for authors arriving from a journal (or from a venue with a major- revision decision) is that there is no second submission: the paper you submit, plus one short author response, is the whole story. The current edition, IJCAI-ECAI 2026, follows the IJCAI process because ECAI 2026 is being run jointly with IJCAI.
| Decision | What it means | Author move |
|---|---|---|
| Accept | Contribution and evidence hold | Camera-ready in the correct template; do not expand scope |
| Reject (after full review) | A soundness, significance, or clarity gap the rebuttal did not close | Revise substantively and reroute (AAAI/IJCAI/a specialist venue) or resubmit next ECAI |
| Summary reject | Out of scope, below bar, or a formatting/anonymity violation caught early | Do not appeal into the void — fix the structural issue before any resubmission |
The strategic reading: because there is no major-revision safety net, the submitted paper must already be complete — the proof finished, the baseline fair, the claim matched to the evidence. A gap you were "planning to fix in revision" has nowhere to go.
ecai.cls/ijcai.sty) and governed by
different bodies (AAAI vs EurAI). Never assume shared dates or format.ecai.cls conventions and PAIS co-location return.ecai-topic-selection).Expect several reviewers under an area chair drawn from your topic area — and note that by submitting you volunteer for the reviewer pool yourself (IJCAI-ECAI 2026 policy). Because ECAI spans symbolic AI, planning, KR, multi-agent systems, and ML, matching your topics well is what gets you expert reviewers rather than distant ones. Vague method descriptions get caught in the discussion the area chair runs, not skimmed.
[Before submission] topics/keywords -> area chair + reviewer pool (largest lever)
[Summary-reject risk] scope, formatting, anonymity, page budget correct BEFORE upload
[Rebuttal] correct factual misreadings, supply one asked-for number,
answer the specific objection each reviewer raised
[After reject] no appeal that reopens the decision; reroute or resubmit next cycle
A rebuttal moves borderline papers when it corrects a factual misreading or provides a clarification a reviewer said was missing; it does not move papers when it argues taste or promises future work. With only one response and no revision round, the rebuttal is a precision instrument, not a plan.
Weight reviews before answering. A review that cites your definitions, lemmas, and tables was read closely; its author is your likely advocate if the rebuttal holds. A review that discusses only novelty has left soundness to the others — answer each reviewer on the axis they raised. The area chair, not any single reviewer, drives the outcome in discussion, so a response that gives the AC a clean reason to champion the paper is worth more than one that "wins" against a hostile reviewer.
[Process stage] pre-submission / summary-reject phase / under review / rebuttal / final
[Edition regime] standalone ECAI / joint IJCAI-ECAI (IJCAI process)
[Decision] accept / reject / summary reject, with the criterion driving it
[Criterion map] each review point -> significance | soundness/proof | evidence | clarity | fit
[Leverage plan] the rebuttal move that can actually change this AC's recommendation
[Forbidden moves] identity leak / new unsupported claims / promising a revision that cannot happen