The CTC construct expresses a risk in terms of it's current condition, a transition over time, and possible consequence(s). The format introduced by David P. Gluch is as follows:

• Given that condition then there is concern that (possibly) consequence.

•     Given that there is a lack of programmers, then there is  concern that the project will not be completed on time.

The CTC format can further refine the risk. This refinement contains the attributes of the risk, such as a detailed description of the condition, probability, and impact. The picture below shows how the risk can be decomposed into smaller, more manageable risks.
 
 

The risk " Given that there is a lack of programmers, then there is  concern that the project will not be completed on time." can be described in more detail in the following context:

"We don't have enough programmers that are experienced using Java. In addition, we don't have the funds to buy Java development tools or hire more Java programmers. According to the specifications, at least 4 Java programmers are required to build the product; we only have 3."

Here is an example of how to define the risk in the complete CTC format:

1. Given that there are only three programmers and the planned project documents requires four, the project will not be completed on time.
2. Given that the programs will be written in Java and that the programmers only have a few months experience in using Java, the project will not be completed on time.
3. Given that the budget is too low to buy books and resources on Java available to the programmers, the project will not be completed on time.