Skip to main content

28. After rejection

Most first papers are rejected. *ACL main-conference acceptance rates sit around a quarter, so rejection is the modal outcome. It says little about you or your future. Almost every researcher you admire has a drawer full of rejection letters, and they learned more from those than from their acceptances. The reviews sting first and help second. This chapter is the sibling of After Acceptance. It covers what to do when the decision comes back reject.

First, do nothing​

Read the reviews once, then close the laptop for a day. You will want to fire back a furious response, email the chairs, or rage-post. None of it helps. Reviews you read angry look different from reviews you read calm. Come back when you can treat them as data.

Read the reviews for signal​

Even the bad reviews carry information. Your job is to separate the signal from the noise.

  • Weight by convergence. A weakness two reviewers raise independently is real and must be addressed. A single reviewer's pet peeve may not be.
  • Sort fixable from fundamental. Be honest about which you got. "Add a baseline," "clarify Section 3," "run another seed" are fixable. "The core claim is not supported by the experiments" is fundamental and needs more than a polish.
  • A misreading is a finding. If a reviewer misunderstood your contribution, the paper was unclear there. That is your fault to fix (Reviewer 2 notwithstanding). Even an unfair or AI-flavored review usually contains one true thing; mine it.

Decide: revise, redirect, or rethink​

  • Revise and resubmit when the contribution is sound and the issues are addressable. This is the usual path, and the next section is how it works.
  • Redirect to a better-fit venue when the problem was fit and the quality was fine: a workshop, Findings, a more applied or specialized track. A paper rejected as "too niche for the main track" can be a great fit for a workshop.
  • Rethink when reviewers converge on a fundamental flaw. Sometimes the honest move is a different experiment or a reframed claim. Resubmitting the same paper with the abstract reworded will not fix it.

Do not resubmit the identical paper to the next deadline hoping for a kinder draw. Reviewers can tell, and the same weaknesses resurface. ARR also requires you to disclose the prior version, as the next section explains.

How ARR resubmission works​

At ARR, you address substantive reviewer requests mainly by revising and resubmitting. The in-cycle response (Chapter 26) is the lesser route. When you resubmit to a later cycle, three things matter.

  • Acknowledge the previous version. This is not optional. You provide the OpenReview link to the prior submission. "A paper that has been previously submitted but fails to acknowledge the previous version will be desk rejected." Hiding a rejection to get a fresh start is the one move guaranteed to backfire.
  • Write a real revision note. ARR asks for an explanation of revisions that "summarize[s] the changes made and include[s] a point-by-point response indicating how you have addressed each weakness and suggestion listed by each reviewer (or your justifications for not doing some of the revisions)." A color-coded PDF showing what changed makes the reviewers' job easier and your case stronger.
  • Choose your reviewers deliberately. You can request the same reviewers, who will focus on whether your revisions addressed their concerns. Or you can request all new ones, who do not see the prior reviews until after they submit their own. Same reviewers reward real revision and a strong note. New reviewers reset a relationship that went badly. Pick on purpose.

Make the revision real​

Returning reviewers check the revision note against the paper. Suppose the note says "we have added the significance test (Section 5.2)" and the paper still has no significance test. That is the fastest way to lose the same reviewers twice. Do the work. Use the revision to fix what no reviewer flagged but you now see with fresh distance.

Keep perspective​

  • Rejection is the common case. Many of the papers in Chapter 30 were rejected somewhere first.
  • The reviews are free expert feedback most people would pay for. Keep a list of what you learned.
  • The biggest predictor of a published paper is an author who revised it and sent it back out. Persistence gets most papers in.

Common mistakes​

  • Firing off an angry response to reviewers or chairs. It never helps and the field is small.
  • Resubmitting the identical paper unchanged, hoping for an easier panel.
  • Not disclosing the prior version. It is an automatic desk reject.
  • A revision note that promises changes the paper does not contain.
  • Addressing only the kind reviewer and ignoring the harsh-but-right one.
  • Giving up after one rejection. The reviews are a map to the next version.

Further reading​