ICLR

Reviewer Obligations at ICLR: Understanding the Paper Count Policy

The ICLR policy is refreshingly blunt: if your name appears on three or more papers, you review, full stop.

4 min readMachine Learning

The ICLR reviewer policy has surfaced a question that feels deceptively simple: if your name appears on three or more papers, you are expected to review. No qualifications are mentioned. The original poster, sitting at two papers, is safe for now. But they ask the sharper question that matters: does a fourth-author slot on three papers, say for a new student like Alex, obligate them to review regardless of readiness? The policy's silence on expertise is not an oversight. It is a signal.

Let's be direct about what this reveals. Conferences like ICLR are not just curators of research; they are the operating system for the field's quality control. When the policy ties reviewer duty to authorship count rather than demonstrated skill, it makes a pragmatic bet: that participation in the research process, even at the margins, builds enough context to be useful. For a student like Alex, who has been in the lab long enough to earn three co-authorships, the assumption is that they have absorbed the norms of peer review, the bar for sound methodology, the difference between a helpful suggestion and a trivial nitpick. That is not an unreasonable bet. But it is a bet placed on the reader's behalf, and the cost of losing it is unevenly distributed. The person who gets a shallow review is not the one who wrote the policy.

Here is where the conversation connects to the broader challenges we have covered, from the practical hurdles of exploring real-world computer vision deployments to the recurring data privacy concerns in ICLR submissions. In each case, the field is leaning on trust in a system that is often opaque to its own participants. If a student reviewer is asked to evaluate a paper on a technique they have only seen in passing, the outcome is not just a bad review. It is a missed opportunity for the author to get feedback that actually improves their work. And it teaches the student that reviewing is a chore, not a craft.

Our take is not that the policy is wrong to require reviewers. It is that the policy is wrong to ignore the support structure that makes reviewing viable. If ICLR wants to count authorship as a proxy for qualification, then it should also provide a lightweight onboarding path: a short guide, a few example reviews, a clear rubric for what constitutes a responsible critique. That is not coddling. It is investing in the same people the policy is asking to carry the load. Without that, the rule will produce reviewers who are technically compliant but practically unprepared. That helps no one, least of all the authors who are also the field's future.

So what would we tell Alex? If you have three papers, you are qualified to start, but you are not obligated to go it alone. Ask for a senior reviewer to co-sign your first assignment. Read two reviews from past cycles on similar topics. And remember that the goal is not to find flaws for sport; it is to help the author see their work more clearly, the same way you would want to be seen. The policy opens a door. It is on you, and on the conference, to make sure the room is not empty. The detail to watch is not whether the policy changes, but whether the support appears. That will tell you more than the rule itself ever will.

From Machine Learning

The ICLR review policy says if your name appears on 3 or more papers, you will need to serve as a reviewer, and it did not say anything about qualifications. I only have 2 so this doesn't apply to me, but I am not sure if I understand it correctly and thus have some concerns. So say if Alex, a new student, was 4th author on 3 papers in their lab, does it mean he needs to review even if he is not qualified?

Read the original at Machine Learning