Enter the risk name and description of the risk. The creation date will automatically populate. Choose an author from the people who have roles on the project, and same for the risk owner. Categories are definable, so click the to create a category if the one you want does not exist. Note the asset(s) under risk by this particular risk, and quantify the aggregate value of asset(s).
The scale seeks to clarify the size of the risk to the organization, like here it is 100,000,000, which may be a small amount of money to a huge company, but represent an existential threat to a mid-sized company. Exposure represents the total dollar amount of the aggregate 'value of asset(s)' that is at risk. Here there is 100% exposure. The probability represents the probability of occurrence, which must be between 1-99%. Why? Because if 0% then it's not a risk, and if 100% then it has been realized and is now an issue and/or problem. Proximity can be described at the closeness or timing of the risk. Response categories provided are typical for risk management. The activity captures all the steps taken to capture, update, track, assess, report, manage and close this risk. Risk status informs stakeholders of the current status of a risk.
The entry status is a reporting measure to indicate the risk status at-a-glance. means realized or imminent realization, means realized imminently unless measures are taken, means risk is managed as described. The entry trend is also a reporting measure to indicate the risk status at-a-glance. It is used to indicate the status of the risk as it compares to the previous status. To go from to should warrant the strongest downward arrow for example. Comments are for you, and you can upload whatever documents you wish to provide more detail on the risk.
Like all entities in TCP, the provides a field-by-field account of all changes that have taken place since the beginning of the project. It provides the detail in tabular form for your auditing and exporting pleasure.