If you've signed up to review for MLSys 2027 and are still staring at an empty assignment dashboard, you're not alone, and that silence is a problem worth naming. The conference's review system appears to be stalled, and for a community that prides itself on rigorous, timely peer review, this kind of operational drift erodes trust. We think it's time to stop treating this as a minor scheduling hiccup and start asking what it reveals about the pressures we're placing on volunteer reviewers.
The story is simple: a reciprocal reviewer for MLSys 2027, u/Sea_Raccoon_9673, reported on a public forum that no papers have been assigned yet and that no timeline has been communicated. Others echo the same uncertainty. This isn't an isolated complaint, it's a symptom of a system that often treats reviewer availability as an afterthought. Compare this to the urgency we saw in the Call for Computer Vision Experts to Join Urgent WACV 2027 Review Panel, where a workshop had to scramble for emergency reviewers under a tight deadline. That call was a fire drill. This MLSys situation is the quiet before the fire, and it's just as worrying.
When a conference can't communicate basic assignment timelines to its own reviewers, it risks more than bruised feelings. It risks losing those reviewers. Reciprocal reviewers are often early-career researchers, senior PhD students, or postdocs who volunteer their time in exchange for visibility and community standing. They are not an infinite resource. If the process feels disorganized or disrespectful of their time, they will simply stop signing up. That leads to exactly the kind of last-minute crisis WACV faced, except now it's for a main conference, not a workshop. The When Presenters Can't Answer Questions, AI Papers Fail the Test piece reminded us that peer review is the first line of defense against low-quality or AI-generated submissions. A rushed or understaffed review process undermines that defense.
Our take: this is not about a single missed email. It's about whether MLSys and conferences like it treat the review process as a core function or as a logistical afterthought. Reviewers deserve clarity on timelines, workload expectations, and a system that respects their commitment. If the organizers haven't communicated yet, they should do so immediately, not with a generic "we're working on it," but with a concrete date and a clear rationale for the delay. The specific consequence to watch: if assignments remain unallocated much longer, the review window will compress, quality will suffer, and the community will notice. That's not a hypothetical future. It's the next few weeks.