RIDAC form fields
Learn about the fields of the RIDAC form.
|
Field |
Description |
|---|---|
|
Number |
System-generated ID number with a configurable prefix. |
|
State |
Current state of the risk. All new risks are created in the Pending state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. |
|
Risk status |
Status of the risk. It provides information on current status of the risk, whether it is achieved or mitigated or accepted. The available options are: Pending, Achieved, Not Achieved, Avoid, Mitigate, Transfer, and Accept. |
|
Probability |
The likelihood that the event described in the risk will occur. The available options are: Absolute, High, Moderate, and Low |
|
Impact |
Impact of the risk event on the outcome of the project. |
|
Estimated cost |
Estimated cost the risk event generates. |
|
Risk rank |
A value and color assigned to the risk. This value is calculated using risk probability and impact. You can configure the color and value using Risk Value Lookup. For more information, see Configure custom Risk rank and Risk value for a project. |
|
Risk owner |
Primary resource who is responsible for monitoring and managing the risk. |
|
Assigned to |
Primary resource assigned to work on the risk. |
|
Risk value |
A value calculated from Risk Value Lookup. For more information, see Configure custom Risk rank and Risk value for a project. |
|
Due date |
Requested date for the assigned resource to resolve the risk or the date on which the risk must be closed or addressed if not assigned to any resource. |
|
Show on project status report |
Option to specify whether the risk information should be included in the project status report. |
|
Task |
Project to which this risk belongs. |
|
Short description |
Brief description of the event and its potential impact on the success of the project. If the risk is created from the risk library, then this field displays the Risk Statement name. |
|
Description |
Details of the event and its potential impact. If the risk is created from the risk library, then this field displays the Risk Statement short description. |
|
Actual cost |
Cost generated by the risk event. This information gets added when and if the event occurs. |
|
Mitigation plan |
Brief description of efforts taken to mitigate the risk. |
|
Field |
Description |
|---|---|
|
Number |
System-generated ID number with a configurable prefix. |
|
State |
Current state of the issue. All new issue records are created in the Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped |
|
Priority |
Urgency of resolving or managing the issue based on possible impact. |
|
Estimated cost |
Estimated cost the issue generates. |
|
Impact |
Impact on the outcome of the project if the issue remains unresolved. |
|
Due date |
Requested date for the assigned resource to resolve the issue or the date on which the issue must be closed or addressed if not assigned to any resource. |
|
Assigned to |
Primary resource assigned to work on the issue resolution. |
|
Parent |
Project to which this issue belongs. |
|
Show on project status report |
Option to specify whether the issue information should be included in the project status report. |
|
Short description |
Brief description of the issue and its potential impact on the success of the project. As you start typing the title for your issue, related issues that potentially match your issue are displayed. Select the suggestion icon ([Omitted image "suggestions-icon.png"] Alt text: Suggestion icon) to select from the list of predefined issue descriptions. |
|
Description |
Details of the issue and its potential impact. |
|
Work notes |
Information to record and track the work accomplished for resolving the issue. |
|
Field |
Description |
|---|---|
|
Number |
System-generated ID number with a configurable prefix. |
|
State |
Current state of the decision. All new decision records are created with Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped |
|
Priority |
Urgency of approving or implementing the decision based on possible impact. |
|
Decision status |
Status of the decision. The available options are: Pending, Approved, and Rejected. |
|
Impact |
Impact on the outcome of the project if you do not implement the decision. |
|
Approval required |
Option for determining whether approval of the decision is required. |
|
Estimated Cost |
Estimated cost of implementing the decision. |
|
Due date |
Requested date on which the decision must be approved or implemented. |
|
Assigned to |
Primary resource assigned to work on the decision. The default value is the name of the user creating the decision record. |
|
Parent |
Project number to which this decision belongs. |
|
Show on project status report |
Option to specify whether the decision information should be included in the project status report. |
|
Short description |
Brief description of the decision such as what the decision is about, who made it, what it affects, and the decision outcome.As you start typing the title for your decision, related decisions that potentially match your decision are displayed. Select the Suggestion icon ([Omitted image "suggestions-icon.png"] Alt text: Suggestion icon) to select a description from the list of predefined decision descriptions. |
|
Description |
Details of the decision and its potential impact. |
|
Work notes |
Information to record and track the status of decision implementation or approvals. |
|
Field |
Description |
|---|---|
|
Number |
System-generated number with a configurable prefix. |
|
State |
Current state of the action. All new action records are created with the state set to Open.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped |
|
Priority |
Urgency for implementing or approving the action based on impact. |
|
Estimated Cost |
Estimated cost the action generates. |
|
Impact |
The impact on the outcome of the project if you do not implement the action. |
|
Approval |
Status of approval from the stakeholders for the action. A user with approval administrator role can only change the status of approval. |
|
Assigned to |
Primary resource assigned to implement the action. |
|
Due date |
Requested date on which the action must be approved or implemented. |
|
Parent |
The project to which this action belongs. |
|
Show on project status report |
Option to specify whether the action information should be included in the project status report. |
|
Short description |
Brief description of the action such as what the action entails, how to implement the action, who it affects, and the action outcome.As you start typing the title for your action, the related actions that potentially match your action title appear. Select the Suggestion icon ([Omitted image "suggestions-icon.png"] Alt text: suggestion icon) to select a description from the list of predefined actions. |
|
Description |
Details of the action and its potential impact. |
|
Work notes |
Information about the action. Add work notes to communicate about the status of action approval, rejection, or implementation with other users. |
|
Field |
Description |
|---|---|
|
Number |
System-generated ID number with a configurable prefix. |
|
State |
Current state of the request change. All new request change records are created in the Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped |
|
Priority |
Urgency for approving the requested changes based on impact. |
|
Estimated Cost |
Estimated cost the requested changes generate. |
|
Impact |
Impact on the outcome of the project if you do not approve the requested changes. |
|
Approval |
Status of approval from the stakeholders for the requested changes. |
|
Assigned to |
Primary resource assigned to work on the request change. |
|
Due date |
Requested date to complete the request change. |
|
Category |
Entity for which you are creating the request change. The options are: Resource, Scope, Cost, and Schedule. |
|
Parent |
Project number to which this request change belongs. |
|
Show on project status report |
Option to specify whether the request change information should be included in the project status report. |
|
Title |
Title for the change request. |
|
Description |
Details of the request change and its potential impact. |
|
Business Justification |
Reason for requesting the proposed change in the project and its impact on the business. |
|
Work notes |
Additional information to indicate progress on the project request change. |
--- title: RIDAC form fields description: Learn about the fields of the RIDAC form. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/project-management/ridac-forms.html release: australia product: Project Management classification: project-management topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 7 breadcrumb: [Form field information for Project Management, Project Management reference, Project Management, Project Portfolio Management, Strategic Portfolio Management] --- # RIDAC form fields Learn about the fields of the RIDAC form. <table id="tbl_RiskFields"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> System-generated ID number with a configurable prefix. </td></tr><tr><td> State </td><td> Current state of the risk. All new risks are created in the Pending state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. </td></tr><tr><td> Risk status </td><td> Status of the risk. It provides information on current status of the risk, whether it is achieved or mitigated or accepted. The available options are: Pending, Achieved, Not Achieved, Avoid, Mitigate, Transfer, and Accept. </td></tr><tr><td> Probability </td><td> The likelihood that the event described in the risk will occur. The available options are: Absolute, High, Moderate, and Low </td></tr><tr><td> Impact </td><td> Impact of the risk event on the outcome of the project. </td></tr><tr><td> Estimated cost </td><td> Estimated cost the risk event generates. </td></tr><tr><td> Risk rank </td><td> A value and color assigned to the risk. This value is calculated using risk probability and impact. You can configure the color and value using Risk Value Lookup. For more information, see [Configure custom Risk rank and Risk value for a project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/risk-value-lookup-project.md). </td></tr><tr><td> Risk owner </td><td> Primary resource who is responsible for monitoring and managing the risk. </td></tr><tr><td> Assigned to </td><td> Primary resource assigned to work on the risk. </td></tr><tr><td> Risk value </td><td> A value calculated from Risk Value Lookup. For more information, see [Configure custom Risk rank and Risk value for a project](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/risk-value-lookup-project.md). </td></tr><tr><td> Due date </td><td> Requested date for the assigned resource to resolve the risk or the date on which the risk must be closed or addressed if not assigned to any resource. </td></tr><tr><td> Show on project status report </td><td> Option to specify whether the risk information should be included in the project status report. </td></tr><tr><td> Task </td><td> Project to which this risk belongs. </td></tr><tr><td> Short description </td><td> Brief description of the event and its potential impact on the success of the project. If the risk is created from the risk library, then this field displays the Risk Statement name. </td></tr><tr><td> Description </td><td> Details of the event and its potential impact. If the risk is created from the risk library, then this field displays the Risk Statement short description. </td></tr><tr><td> Actual cost </td><td> Cost generated by the risk event. This information gets added when and if the event occurs. </td></tr><tr><td> Mitigation plan </td><td> Brief description of efforts taken to mitigate the risk. </td></tr></tbody> </table>|Field|Description| |-----|-----------| |Inherent risk|This field gets auto-populated with the risk scores when the risk assessor assesses the inherent risk.| |Elevated to enterprise risk|This option gets selected automatically when the risk is elevated to enterprise risk by the project manager.| |Residual risk|This field gets auto-populated with the risk scores when the risk assessor assess the residual risk.| |Enterprise inherent risk|This field gets auto-populated with the risk scores when the risk assessor assesses the enterprise inherent risk.| |Enterprise residual risk|This field gets auto-populated with the risk scores when the risk assessor assesses the enterprise residual risk.| <table id="table_dbt_pd2_zfc"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> System-generated ID number with a configurable prefix. </td></tr><tr><td> State </td><td> Current state of the issue. All new issue records are created in the Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped </td></tr><tr><td> Priority </td><td> Urgency of resolving or managing the issue based on possible impact. </td></tr><tr><td> Estimated cost </td><td> Estimated cost the issue generates. </td></tr><tr><td> Impact </td><td> Impact on the outcome of the project if the issue remains unresolved. </td></tr><tr><td> Due date </td><td> Requested date for the assigned resource to resolve the issue or the date on which the issue must be closed or addressed if not assigned to any resource. </td></tr><tr><td> Assigned to </td><td> Primary resource assigned to work on the issue resolution. </td></tr><tr><td> Parent </td><td> Project to which this issue belongs. </td></tr><tr><td> Show on project status report </td><td> Option to specify whether the issue information should be included in the project status report. </td></tr><tr><td> Short description </td><td> Brief description of the issue and its potential impact on the success of the project. As you start typing the title for your issue, related issues that potentially match your issue are displayed. Select the suggestion icon \(\[Omitted image "suggestions-icon.png"\] Alt text: Suggestion icon\) to select from the list of predefined issue descriptions. </td></tr><tr><td> Description </td><td> Details of the issue and its potential impact. </td></tr><tr><td> Work notes </td><td> Information to record and track the work accomplished for resolving the issue. </td></tr></tbody> </table><table id="table_rkg_qd2_zfc"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> System-generated ID number with a configurable prefix. </td></tr><tr><td> State </td><td> Current state of the decision. All new decision records are created with Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped </td></tr><tr><td> Priority </td><td> Urgency of approving or implementing the decision based on possible impact. </td></tr><tr><td> Decision status </td><td> Status of the decision. The available options are: Pending, Approved, and Rejected. </td></tr><tr><td> Impact </td><td> Impact on the outcome of the project if you do not implement the decision. </td></tr><tr><td> Approval required </td><td> Option for determining whether approval of the decision is required. </td></tr><tr><td> Estimated Cost </td><td> Estimated cost of implementing the decision. </td></tr><tr><td> Due date </td><td> Requested date on which the decision must be approved or implemented. </td></tr><tr><td> Assigned to </td><td> Primary resource assigned to work on the decision. The default value is the name of the user creating the decision record. </td></tr><tr><td> Parent </td><td> Project number to which this decision belongs. </td></tr><tr><td> Show on project status report </td><td> Option to specify whether the decision information should be included in the project status report. </td></tr><tr><td> Short description </td><td> Brief description of the decision such as what the decision is about, who made it, what it affects, and the decision outcome.As you start typing the title for your decision, related decisions that potentially match your decision are displayed. Select the Suggestion icon \(\[Omitted image "suggestions-icon.png"\] Alt text: Suggestion icon\) to select a description from the list of predefined decision descriptions. </td></tr><tr><td> Description </td><td> Details of the decision and its potential impact. </td></tr><tr><td> Work notes </td><td> Information to record and track the status of decision implementation or approvals. </td></tr></tbody> </table><table id="table_lyx_zd2_zfc"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> System-generated number with a configurable prefix. </td></tr><tr><td> State </td><td> Current state of the action. All new action records are created with the state set to Open.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped </td></tr><tr><td> Priority </td><td> Urgency for implementing or approving the action based on impact. </td></tr><tr><td> Estimated Cost </td><td> Estimated cost the action generates. </td></tr><tr><td> Impact </td><td> The impact on the outcome of the project if you do not implement the action. </td></tr><tr><td> Approval </td><td> Status of approval from the stakeholders for the action. A user with approval administrator role can only change the status of approval. </td></tr><tr><td> Assigned to </td><td> Primary resource assigned to implement the action. </td></tr><tr><td> Due date </td><td> Requested date on which the action must be approved or implemented. </td></tr><tr><td> Parent </td><td> The project to which this action belongs. </td></tr><tr><td> Show on project status report </td><td> Option to specify whether the action information should be included in the project status report. </td></tr><tr><td> Short description </td><td> Brief description of the action such as what the action entails, how to implement the action, who it affects, and the action outcome.As you start typing the title for your action, the related actions that potentially match your action title appear. Select the Suggestion icon \(\[Omitted image "suggestions-icon.png"\] Alt text: suggestion icon\) to select a description from the list of predefined actions. </td></tr><tr><td> Description </td><td> Details of the action and its potential impact. </td></tr><tr><td> Work notes </td><td> Information about the action. Add work notes to communicate about the status of action approval, rejection, or implementation with other users. </td></tr></tbody> </table><table id="table_hwp_yd2_zfc"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> System-generated ID number with a configurable prefix. </td></tr><tr><td> State </td><td> Current state of the request change. All new request change records are created in the Open state.The available states are: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped </td></tr><tr><td> Priority </td><td> Urgency for approving the requested changes based on impact. </td></tr><tr><td> Estimated Cost </td><td> Estimated cost the requested changes generate. </td></tr><tr><td> Impact </td><td> Impact on the outcome of the project if you do not approve the requested changes. </td></tr><tr><td> Approval </td><td> Status of approval from the stakeholders for the requested changes. </td></tr><tr><td> Assigned to </td><td> Primary resource assigned to work on the request change. </td></tr><tr><td> Due date </td><td> Requested date to complete the request change. </td></tr><tr><td> Category </td><td> Entity for which you are creating the request change. The options are: Resource, Scope, Cost, and Schedule. </td></tr><tr><td> Parent </td><td> Project number to which this request change belongs. </td></tr><tr><td> Show on project status report </td><td> Option to specify whether the request change information should be included in the project status report. </td></tr><tr><td> Title </td><td> Title for the change request. </td></tr><tr><td> Description </td><td> Details of the request change and its potential impact. </td></tr><tr><td> Business Justification </td><td> Reason for requesting the proposed change in the project and its impact on the business. </td></tr><tr><td> Work notes </td><td> Additional information to indicate progress on the project request change. </td></tr></tbody> </table>**Parent Topic:**[Form field information for Project Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/project-management/form-field-information-for-project-management.md)
| title | RIDAC form fields |
| description | Learn about the fields of the RIDAC form. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/it-business-management/project-management/ridac-forms.html |
| release | australia |
| product | Project Management |
| classification | project-management |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 7 |
| breadcrumb | Form field information for Project ManagementProject Management referenceProject ManagementProject Portfolio ManagementStrategic Portfolio Management |