The silence is often the loudest part of the review process. When a submission sits in a quiet discussion period, with no new commentary from reviewers or the area chair after a hopeful set of initial reviews, the ambiguity becomes its own kind of pressure. The researcher is not asking a trivial question about formatting or submission logistics. They are asking a deeper, more practical one: how do you make confident decisions when the system designed to give you feedback goes quiet? This is not just a scheduling conflict between NeurIPS and ICLR; it is a signal that the current workflow for academic research is failing the humans who do the work.
We have seen this pattern before in different forms. For example, the frustrations with automated filtering tools, where genuine reviews get flagged and discarded, show how much damage a lack of clear communication can do. As we noted in Clean Data Starts With Catching AI Slop Before It Skews Your Model, when you remove the signal you need most, the entire model of understanding becomes less accurate. The same principle applies here. The author has a promising paper, but without hearing back from the reviewers, they are effectively operating with a skewed dataset. They have to guess whether the initial enthusiasm was real or a fluke, and that guess determines whether they risk a withdrawal or gamble on a dual submission. The confusion is not a personal failing; it is a structural one.
The practical question about OpenReview flagging a resubmission is valid, but it points to a larger issue. The platform is a tool, but it is not a substitute for a clear editorial process. The researcher is not trying to game the system; they are trying to navigate it with incomplete information. We would tell them this: do not let the silence of others dictate your timeline. If the ICLR abstract deadline is before the NeurIPS announcement, treat it as a strategic hedge, not a betrayal. Submit the abstract, keep the NeurIPS submission active, and let the system sort out the overlap. The worst case is that you withdraw one later; the best case is that you have two chances to get a fair hearing. This is not about being opportunistic; it is about being resilient in a process that often feels arbitrary.
What is most telling is the researcher's admission that they have no idea what the reviewers think. That is not a critique of their preparation; it is a critique of the review culture. When reviewers go quiet after initial positivity, they are not being helpful; they are being negligent. This is why we encourage researchers to explore tools that reduce friction, not add to it. For instance, Exploring Real-World Computer Vision: Deployments, Edge Models, and Current Challenges shows how practical constraints often matter more than theoretical perfection. The same logic applies here: the constraint is the timeline, and the solution is to move forward with what you know, not wait for what you want to hear. The concrete detail to watch is how OpenReview handles this specific overlap. If they flag it as problematic, that tells you the platform is enforcing rules that do not account for the human chaos of research. If they allow it, it is a quiet admission that the system is built for flexibility. Either way, the author should act now, because waiting for clarity from a silent room is a losing game.