On the flip side of writing a review is writing a rebuttal. Many conferences (such as CHI) have a two-round review process during which authors have a chance to communicate with the reviewers by writing a rebuttal after the first initial round of reviews. This is an opportunity for you to justify the importance of your work and address misinterpretations.

The purpose of the rebuttal is to convince reviewers (especially 1AC and 2AC) that the concerns they pointed out are minor and fixable within the conference review cycle. I recommend adopting the following steps, based on the guidelines and blogs written by D. Vogel, N. Elmqvist, and others.

Review analysis

  1. Read the reviews thoroughly
  2. Group comments by themes
  3. Write individual responses and action plans

Rebuttal writing

Usually, you are only given a week to write the rebuttal. So we need to be efficient. Within one or two days, you should complete the above Steps 1 and 2, as well as hold a meeting with your co-authors (including me) to discuss the rebuttal strategies. Within another two days, you should have an initial draft of the rebuttal, and send it to me for advice. We may need to hold another meeting to discuss the rebuttal, and we should have a polished rebuttal at least one day before the submission deadline. For ease of discussion, you should keep these files in a shared folder or a Google Doc with three tabs:

  1. a document for the original reviews, with color-coded highlighted concerns;
  2. a document for the grouped reviews, with themes and sub-themes, etc., as well as draft responses and action plans under each (sub-)theme;
  3. a document for the rebuttal draft, with headers for themes and polished responses.

D. Vogel provides a more specific methodology of writing rebuttals and formatting strategies of organizing the documents (see this), which are useful to follow along.

Based on the above review analysis: