Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Business Management
Table of Contents
Choose your release version
    Home Orlando IT Business Management IT Business Management Project Portfolio Management Demand Management Use Demand Management RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a demand

    RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a demand

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a demand

    RIDAC is an acronym for Risk, Issue, Decision, Action, and Request Changes records. Create a risk record for your demand that you can convert to other records during the demand life cycle to track issues and to avoid having to manually copy relevant details in related records. This conversion and association of records helps you analyze and identify patterns, trends, and probable resolution for planning future demands.

    As a demand progresses through the demand life cycle, a risk might result in an issue or a new issue might occur. Once you have a risk record, you convert that record into related records such as issues, actions, or decisions. The ability to convert records provides you with the following advantages:

    • Ability to create related records without having to repeatedly manually enter the relevant information.
    • Helps you analyze and identify patterns, trends, and probable resolution for planning future demands.
    • Enables you to view a consolidated list of all RIDAC records using the View RIDAC related link on the Demand form.
    Consider the following points before converting or associating RIDAC records:
    • You can convert one record to another only in the RIDAC sequence. For example, you can convert a risk to an issue, decision, action, or request change but you cannot convert an issue to a risk or a decision to an issue. The following diagram illustrates the RIDAC process flow. Diagram for explaining RIDAC process flow
    • You can convert one record into multiple RIDAC records. For example, you can create multiple issue records from one risk record.
    • You can associate one record with multiple different records. For example, you can link one issue record to multiple different risk, decision, action, or request change records. For more information, see Associate existing RIDAC (risks, issues, actions, decisions, and request changes) records for a demand.
    • Add risks for a demand

      Add a risk to a demand to identify, analyze, prioritize, plan, and track a risk during any phase of the demand life cycle. Assess potential problems and the severity of their impact to take informed decisions about the demand.

    • Add issues for a demand

      Add an issue to a demand to escalate a risk or to track an unexpected problem such as a technical malfunction or resource unavailability that occurs during any phase of the demand life cycle. If the issue remains unresolved, unnecessary conflicts, delays, or even a failure can occur.

    • Add decisions for a demand

      As a demand manager, develop a plan to manage risks and issues proactively with solutions. Add the solution for a risk or issue to a demand in the form of a decision. You can also convert a risk or an issue to a decision or a decision to an action or a request change.

    • Add actions for a demand

      Add actions that are required for resolving an issue or risk for a demand. You can also convert a risk, issue, or decision to an action based on your analysis and plan for resolution of a risk or issue.

    • Add Request Changes to a demand

      As a demand manager, you might create a request change as the outcome of the action taken to resolve an issue or mitigate a risk. The request change might result in changing the demand's scope, resource requirement, cost, or schedule to minimize the impact of a risk or issue.

    • Convert one RIDAC (Risk, Issue, Decision, Action, and Request Change) record to another for a demand

      Convert one RIDAC record (risk, issue, action, decision, and request changes) to another, in that order, to retain the record information instead of having to create a new record manually and to more easily track the issue.

    • Associate existing RIDAC (risks, issues, actions, decisions, and request changes) records for a demand

      Link existing RIDAC records (risks, issues, actions, decisions, and request changes) to one another for your demand. Associating RIDAC records with each other enables you to keep a record of risks or issues and their outcome for analysis at demand closure and planning. It also helps to track the risks and issues throughout the demand life cycle.

    Related tasks
    • Submit an idea from Self-Service or Service Catalog
    • Create a demand
    • View demands
    • Reset a demand to Draft state
    • Delete demands
    • Move and resize a demand
    Related concepts
    • Assess demands
    • Demand tasks
    • Actual cost and effort calculation for a demand and demand task
    • Add details to demands
    • Composite fields
    Related reference
    • Stage fields

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a demand

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a demand

      RIDAC is an acronym for Risk, Issue, Decision, Action, and Request Changes records. Create a risk record for your demand that you can convert to other records during the demand life cycle to track issues and to avoid having to manually copy relevant details in related records. This conversion and association of records helps you analyze and identify patterns, trends, and probable resolution for planning future demands.

      As a demand progresses through the demand life cycle, a risk might result in an issue or a new issue might occur. Once you have a risk record, you convert that record into related records such as issues, actions, or decisions. The ability to convert records provides you with the following advantages:

      • Ability to create related records without having to repeatedly manually enter the relevant information.
      • Helps you analyze and identify patterns, trends, and probable resolution for planning future demands.
      • Enables you to view a consolidated list of all RIDAC records using the View RIDAC related link on the Demand form.
      Consider the following points before converting or associating RIDAC records:
      • You can convert one record to another only in the RIDAC sequence. For example, you can convert a risk to an issue, decision, action, or request change but you cannot convert an issue to a risk or a decision to an issue. The following diagram illustrates the RIDAC process flow. Diagram for explaining RIDAC process flow
      • You can convert one record into multiple RIDAC records. For example, you can create multiple issue records from one risk record.
      • You can associate one record with multiple different records. For example, you can link one issue record to multiple different risk, decision, action, or request change records. For more information, see Associate existing RIDAC (risks, issues, actions, decisions, and request changes) records for a demand.
      • Add risks for a demand

        Add a risk to a demand to identify, analyze, prioritize, plan, and track a risk during any phase of the demand life cycle. Assess potential problems and the severity of their impact to take informed decisions about the demand.

      • Add issues for a demand

        Add an issue to a demand to escalate a risk or to track an unexpected problem such as a technical malfunction or resource unavailability that occurs during any phase of the demand life cycle. If the issue remains unresolved, unnecessary conflicts, delays, or even a failure can occur.

      • Add decisions for a demand

        As a demand manager, develop a plan to manage risks and issues proactively with solutions. Add the solution for a risk or issue to a demand in the form of a decision. You can also convert a risk or an issue to a decision or a decision to an action or a request change.

      • Add actions for a demand

        Add actions that are required for resolving an issue or risk for a demand. You can also convert a risk, issue, or decision to an action based on your analysis and plan for resolution of a risk or issue.

      • Add Request Changes to a demand

        As a demand manager, you might create a request change as the outcome of the action taken to resolve an issue or mitigate a risk. The request change might result in changing the demand's scope, resource requirement, cost, or schedule to minimize the impact of a risk or issue.

      • Convert one RIDAC (Risk, Issue, Decision, Action, and Request Change) record to another for a demand

        Convert one RIDAC record (risk, issue, action, decision, and request changes) to another, in that order, to retain the record information instead of having to create a new record manually and to more easily track the issue.

      • Associate existing RIDAC (risks, issues, actions, decisions, and request changes) records for a demand

        Link existing RIDAC records (risks, issues, actions, decisions, and request changes) to one another for your demand. Associating RIDAC records with each other enables you to keep a record of risks or issues and their outcome for analysis at demand closure and planning. It also helps to track the risks and issues throughout the demand life cycle.

      Related tasks
      • Submit an idea from Self-Service or Service Catalog
      • Create a demand
      • View demands
      • Reset a demand to Draft state
      • Delete demands
      • Move and resize a demand
      Related concepts
      • Assess demands
      • Demand tasks
      • Actual cost and effort calculation for a demand and demand task
      • Add details to demands
      • Composite fields
      Related reference
      • Stage fields

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login