---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Assign a regulatory event alert to a coordinator

# Assign a regulatory event alert to a coordinator {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Log in to the GRC: Regulatory Change Management application, review the
regulatory event alert, update the details, and assign it to a coordinator.

## Before you begin

Role required: sn_grc_reg_change.manager, sn_grc_reg_change.user

## About this task

In the following procedure, step 4 and after describe various actions that users with
the sn_grc_reg_change.manager role or sn_grc_reg_change.user role can perform.

## Procedure

1. Log in with the sn_grc_reg_change.manager user role.
2. Navigate to AllRegulatory Change ManagementCompliance Workspace.  
   The Regulatory Change Management application in the Compliance Workspace is displayed.
3. Navigate to ListsAssigned Regulatory Alerts view.
4. In the Assigned Alerts list, select a regulatory event alert.  
   The detailed view for the selected regulatory event alert is displayed.
5. In the Details tab, fill in the form.  
   {#perform-actions-on-reg-alerts-using-ws__table_qk5_sx2_rmb__entry__2}

   | Fields | Description |
   |-|-|
   | Title | Title of the alert as received from the provider. This field is automatically set to display the title. |
   | Description | Description and a summary of the event. This field is automatically set to display the description. |
   | Provider URL | URL of the alert that is received from the provider. This field is automatically set to display the provider URL. |
   | Regulatory body URL | URL of the regulatory body that is associated with the alert. This field is automatically set to display the regulatory body URL. |
   | Provider | Name of the alert provider. This field is automatically set to display the name of the alert provider. |
   | Type | Type of regulatory alert. This field is automatically set to display the type of the alert. |
   | Coordinator | User that the alert is assigned to. |
   | Overall impact | Overall impact of the alert. |
   | Dates ||
   | Source publication date | Date when the regulatory event is published by the regulatory body. This field is automatically set to display the source publication date. |
   | Comments date | Date until when the comments can be provided for the regulatory event. This field is automatically set to display the comments date. |
   | Effective date | Date when the regulatory event is going to be applicable. This field is automatically set to display the effective date. |
   | Compliance date | Date by which the regulatory event is going to be compliant. This field is automatically set to display the compliance date. |
   | Expiration date | Expiry date for the regulatory event. This field is automatically set to display the expiration date. |
   | Series data ||
   | Series name | Series name of the alert. This field is automatically set to display the series name from the provider. |
   | Sequence number | Sequence number of the alert. This field is automatically set to display the sequence number from the provider. |
   | Activity Journal ||
   | Additional comments | Additional comments related to the alert. |
   | Compose ||
   | Compose section | Additional comments related to the alert. |
   | Activities | Log of the activities related to the alert. |
   | Highlighted details ||
   | Taxonomy | Taxonomy details associated with the alert. This field is automatically set to display the taxonomy details of the alert. |
   [Table 1. Details tab]

   {#perform-actions-on-reg-alerts-using-ws__table_qk5_sx2_rmb}  
   Note:  
   Beginning with the ServiceNow® Australia release, the taxonomy section in the form is not available to the new installations.
6. In the Coordinator field, assign the regulatory event alert to a coordinator with the sn_grc_reg_change.user user role and select Save.

## Result

The regulatory event alert is assigned to the selected coordinator.

## What to do next

[Assess the impact of a regulatory event alert](https://servicenow-prod.fluidtopics.net/tO3mq39jM_3VYQrNHY1oPw "Assess the impact of a regulatory event alert by creating an assessment on the regulatory event alert. Assign the impact assessment to the owner of the business entity that is affected by the alert.")

*[\>]: and then