reviewpaper.ai
RoboticsML

CoRL 2025 deadline

The Conference on Robot Learning
September 28-30, 2025 · Seoul, Korea

Official call for papers

All deadlines for this edition have passed.

Key dates

  1. Abstract / registration

    Wed, Apr 23, 2025 · 23:59 AoE

  2. Full paper

    Wed, Apr 30, 2025 · 23:59 AoE

  3. Conference

    September 28-30, 2025 · Seoul, Korea

What CoRL reviewers will look for

CoRL reviewers write section-by-section reviews with heavy weight on real-robot evidence (simulation-only work is acceptable when the simulator is realistic and the link to real robots is clear) and check that the mandatory Limitations section is honest; a frank limitations section is not a weakness. Papers without any weak-accept-or-better score may be rejected before rebuttal; the one-page rebuttal targets factual errors.

Overall score
Rating, 1–4 (top: “Strong accept”)
Written fields
Summary · Strengths · Weaknesses · Limitations · Questions
Author checklist
CoRL author requirements, 4 items

Where the bar sits. CoRL 2026 accepted roughly a third of ~2,100 submissions (secondary source; 2024: ~39%). Papers need at least one weak accept to survive the first round. On this modeled 1–4 scale a mean of ≥ 2.75 is a rough proxy for acceptance.

LLM policy for reviewers

CoRL 2026 reportedly allows AI help for literature search, clarifying concepts and polishing wording, but forbids uploading manuscripts to tools without enterprise confidentiality and requires reviewers to disclose tools used; judgments must be the reviewer's own. (Official page currently empty; unverified.)

Official policy
The full CoRL review form, field by field

Deadline data from ccf-deadlines (MIT license), refreshed every 6 hours. We check the headline venues against their official calls for papers where we can, but deadlines move: always confirm on the official site before you plan around a date. “Estimated” dates are projected from the previous edition and are not announcements.

Times are shown in AoE (Anywhere on Earth, UTC−12) and in your local timezone. Spot an error? Report it upstream so everyone gets the fix.