---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Act on recommendations for controls

# Accept or dismiss recommendations for regulatory alert impacted controls {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 25, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Accept AI-generated recommendations in Regulatory Change Management to mark specific business areas as impacted so that you can help compliance practitioners capture and address the relevant regulatory alert for controls. You can also dismiss recommendations
to filter out irrelevant or unnecessary information.

## Before you begin

Important:  
This Now Assist skill is turned on by default. The skill will be automatically available to appropriate role users for the application. For more information, see [Now Assist skills, agents, and agentic workflows on by default](https://www.servicenow.com/docs/access?context=now-assist-skills-on-by-default&version=yokohama&pubname=yokohama-intelligent-experiences&ft:locale=en-US).

Role required: To view your assigned regulatory alerts, you need the sn_grc_reg_change.user and sn_grc_comp_genai.reg_change_ai_user roles.  
Important:  
Be sure to check AI-generated recommendations for accuracy. If no information is available, the generated recommendations display "No recommendations available," "None," "No records to display," and so on.

To learn about the related roles and regulatory alerts for a recommendation, see [Types of alerts, user roles, and states of regulatory alerts](https://www.servicenow.com/docs/69by3_lO3WwRzqaHxVX58Q "Different users perform various actions on the alert records based on the type of the alert.").

## About this task

The Recommendation Framework enables dynamic, AI-driven control recommendations by evaluating regulatory alert content against configurable control associations. This enhances impact analysis and improves compliance accuracy.
When a regulatory alert is issued, the system generates relevant control suggestions. After reviewing each recommendation, compliance analysts can accept applicable controls to mark the corresponding business areas as
impacted. For example, a regulatory alert related to Digital Operational Resilience Act (DORA) can prompt recommendations for controls such as Vendor Onboarding Procedures and Incident Response Protocols. After a compliance analyst reviews and accepts these
controls, they can mark the relevant business areas as impacted and take steps to help ensure regulatory compliance while managing regulatory tasks.

You can view the related activity for each recommendation by selecting the summary icon ![]() to open the Feedback trail side-panel.

## Procedure

1. Navigate to one of the following locations:  
   * WorkspacesCompliance Workspace, select the list icon ![]() and then navigate to Regulatory alerts.
   * WorkspacesCompliance Workspace select the Regulatory Change Management dashboard icon ![]() and then in the Activity overview, Tracking, or Trends section, select any segment or value in an Alerts related widget to open the list of regulatory alerts with that state.
   {#manage-recos-for-controls__ul_zck_crf_c2c}
2. Select the regulatory alert that you want and review the recommendations by selecting the Recommendations tab.  
   Note:  
   If recommendations haven't already been generated, you can generate recommendations for a regulatory alert in any state except Closed or Cancelled by completing one of the following.
   * On the Overview tab, select Recommend.
   * On the Recommendations tab, select Show recommendations.

   {#manage-recos-for-controls__ul_qqn_dnm_tgc}For more information, see [Generate recommendations for regulatory alert impacted citations, control objectives, controls, and policies](https://www.servicenow.com/docs/UVan7RzyA2s4VylOo~EpmQ "Generate recommendations to identify and mark potential impact areas, such as citations, control objectives, controls, and policies for regulatory alerts using the corresponding regulatory alert impacted skill. Recommendations simplify the process of associating impacts and creating action tasks.").
3. Review potential impact areas by selecting the Controls tab in the Recommended areas of the impact section.  
   The recommended controls only include controls that are part of the existing inventory.

   Note:  
   The `Suggest business operations affected by regulatory alert recommendation context` provides the recommendations that you see here. For more information, see [Recommendation contexts and templates](https://www.servicenow.com/docs/thMvPjB8pIt83g4xnyqyYQ "By using the Governance, Risk, and Compliance recommendations framework, you can use recommendation contexts and templates to deliver AI-driven insights directly to your users within the user interface. With these insights, your users can make informed decisions and take prompt actions.").  
   If recommendations are available, you can scroll through the generated list of control recommendation cards and review the information about each control, such as its name and compliance status.
4. Select the control recommendation card that you want and review the following sections:  
   {#manage-recos-for-controls__id_o2v_k4c_cfc__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the control. |
   | Status | Status of the control: If it's Compliant, Non Compliant, or Not Applicable. |
   | Function | Operational role of the control. For example, Standard control or Common control. |
   | Owner | Owner of the control. |
   | Entity | Entity associated with the control. |
   | Category | Domain or grouping to which the control belongs to. |
   | Type | Type of control. Specifies whether the control is Manual, Automated, or Continuous. |
   | Description | Description and summary of the control. |
   | Additional Information | Additional information related to the control. |
   | Evaluate affected associations for controls ||
   | Risks | Related risks that can be associated with the control. For each risk, the following information is provided if available. * Name of the risk * Entity that the risk is associated with * Risk statement from which the risk is inherited * Risk statement {#manage-recos-for-controls__ul_a1m_mym_tgc} |
   [ ]

   {#manage-recos-for-controls__id_o2v_k4c_cfc}

   For full descriptions of these fields, see [Create a control objective](https://www.servicenow.com/docs/gIblu0oyLt7qED_NffDD7w "A control objective is an objective, direction, or standard that acts as guidance for company interactions and operations. Control objectives can be categorized, classified, and related to policies."), [Create a policy](https://www.servicenow.com/docs/vqncqI2kfHgB2xPtK9_qFA "A policy defines an internal practice that processes must follow. Policies are defined as policies, procedures, standards, plans, checklists, frameworks, and templates."), [Create a control](https://www.servicenow.com/docs/kZOFgQ18ZccGuuES_xPulg "Controls are automatically generated when you associate a policy with an entity type or an entity type with a control objective. A control is created for each entity listed in the entity type for the control objective. Controls can also be manually created."), and [Create a risk manually](https://www.servicenow.com/docs/fpj5Y~dr5GuZBA3J9K0mhg "Risk administrators can create risk records when they see a potential for a gain or loss of value.").
5. To associate risks with your recommendation, navigate to the Risks tab and select the check box for each risk record you want to include as part of the impacted areas.  
   Each selected risk will be added as an impacted area after you accept the recommendation.  
   Note:  
   The control you're reviewing may not have any risks associated with it. Risks must be mapped to controls in the inventory for them to appear.

6. **Optional:** View the record for a control, refresh your recommendations, or review related activity for each recommendation.

   | Option | Description |
   | Select the details icon ![](). | View the record for a control. |
   | Select the refresh icon ![](). | Refresh the recommendations to reflect the latest data. |
   | Select the summary icon (![]()). | Open the Feedback trail side-panel to review the related activity for the recommendation. |
   |-|-|

   {#manage-recos-for-controls__choicetable_zwf_rnd_ngc}
7. Accept or dismiss the recommendations and their associations.
   * Select Accept and then Confirm to accept a recommendation as an impacted area.
   * Select Dismiss and then Confirm to avoid a recommendation from being shown again.

   {#manage-recos-for-controls__choices_p24_zqm_tgc}  
   Before you act on a recommendation, you see a summary of the impact areas and associations that you're accepting or dismissing.  
   If you accept the recommendation, it's marked as an impacted area and is added to the list of impacts. If you dismiss the recommendation, it's marked as dismissed and isn't shown again for that specific regulatory
   alert.
{#manage-recos-for-controls__steps_rbc_pzw_kgc}

## What to do next

If you accepted any recommendations, confirm the creation of an impacted area by navigating to the Impacted areas tab. If you dismissed all recommendations or must add more impacted areas, you can manually add impacted areas.
For more information, see [Add impacted areas manually to a regulatory alert](https://www.servicenow.com/docs/ZLHahiees6UEw0C57mARKA "Add impacted areas such as citations, control objectives, policies, and more to your regulatory alerts. Adding impacted areas to a regulatory alert captures additional impacts that you identified and impacts that weren’t initially recommended.").

*[\>]: and then