Each clarification goes through a number of states as it is answered / developed.  These states / statuses reflect the process that has been developed over the years to answer clarifications.  The process is slightly different for private and public clarifications.  Private clarifications are created by teams; public clarifications are created by the ICMs.

Here is the basic process and the corresponding statuses:



this is the state where the clarification is being drafted. The author can work on the clarification over a period of time.  At this point they can delete the clarification, however, more often then not, the author will submit the clarification which will move it to the submitted state.



the goal is to answer clarifications within a few days of them being submitted.  ICMs typically work in pairs and devise a plan as to who will make the first attempt to answer the clarification. Each of the ICMs adopts one of the ICM states (ICM 1 review or ICM 2 review).  If you are ICM 1, putting the clarification in ICM 1 review state, indicates you are working on it.


icm 1 & 2 review

While in a specific ICM state, that ICM can work on an answer or make notes in the discussion area.  At the point that ICM wants input from the other ICM, they set the state to the alternate ICM state.  In this way a dialog can go on between the 2 ICMs as they come up with answer.  Once they are done or if they need input from the program directors, they set the state to DIHQ 1 review.  This indicates it is time for the program directors to review.


dihq 1 & 2 review

Like the ICMs, the PDs adopt a state that indicates they are or need to review specific clarifications.  They can pass the clarification to the other PD by changing the state.  They can pass the clarification back to the ICMs by setting the clarification back to one of the ICM states. At some point the answer to the clarification has been developed and the clarification state is then set to final.



The state final indicates a clarification is ready to be sent back to the team.



Transitioning a clarification to answered will email the answer to to team.

While this may seem like a lot of states, it has proven over the years to support the actual process.  For example, for repeat clarifications, the DIHQ states might be by-passed.  This still allows someone to read the final answers for typos and grammar before it is sent back to the team.

Lets also look at the differences between private and public clarifications:

  • private clarifications are created by team
    These clarifications arrive for the ICMs to review when they are placed in the submitted state. The team is notified when a clarification is submitted and answered.
  • public clarifications are created by the ICMs
    The submitted state is of less relevance to public clarifications.  Once drafted, the ICM and DIHQ states are useful in working on the text.  When a public clarification enters the  state, it become visible to other using the clarifications site such as teams and challenge masters.

ICMs and PDs can set a clarification to any of these states provided by the website.  By convention, the PDs handle the transition to answered. 

Two state transitions result in email being sent for private clarifications:

  • to submitted
  • to answered

The following people are emailed using the email address in their DI Account:

  • the author of the clarification
  • all the team managers
  • the ICMs for that challenge
  • the PDs