--- title: Create regulatory event alerts manually description: Create a manual entry of the regulatory changes or updates so that they can be routed to the correct subject matter experts for further analysis. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/regulatory-change-management-service-portal/submit-creation-of-regulatory-event-alerts-manually.html release: australia product: Regulatory Change Management Service Portal classification: regulatory-change-management-service-portal topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Manage regulatory tasks, Regulatory Change Management, Governance, Risk, and Compliance] --- # Create regulatory event alerts manually Create a manual entry of the regulatory changes or updates so that they can be routed to the correct subject matter experts for further analysis. ## Before you begin Role required: sn\_grc\_reg\_change.manager ## About this task Users with the sn\_grc\_reg\_change.manager role can create the regulatory alerts manually. Creating the regulatory alerts manually provides the following benefits: - Recognize and fix human instinctive errors accurately. - Assign an ad-hoc or the submitted regulatory event alert to the subject matter experts for further review and analysis, thus ensuring accountability. - Ensure that the data entered manually in the system has high quality and a high level of integrity. ## Procedure 1. Navigate to **All** > **Regulatory Change Management** > **Compliance Workspace** > **Regulatory alerts** > **Unassigned Alerts**. The Regulatory Change Management application in the Compliance Workspace is displayed. 2. Select **New**. The Create New Regulatory alert form is displayed. 3. On the **Details** tab, fill in the form.
| Field | Description |
|---|---|
| Title | A short summary title of the regulatory alert. |
| Source | Displays the data source type identified for creating a regulatory event record. The default option for the input source type is Manual. **Note:** This field is locked for editing for the purpose of internal reporting and business configuration management. |
| Type | Type of regulatory alert. |
| Description | Description and a summary of the event. |
| Provider | Name of the alert provider.**Note:** This field is locked for editing for the purpose of internal reporting and business configuration management. |
| Provider URL | URL of the alert that is received from the provider. |
| Regulatory body URL | URL of the regulatory body that is associated with 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. |
| Comments date | Date until when the comments can be provided for the regulatory event. |
| Effective date | Date when the regulatory event is going to be applicable. |
| Compliance date | Date by which the regulatory event is going to be compliant. |
| Expiration date | Expiry date for the regulatory event. |
| Activity Journal | |
| Additional comments | Additional comments related to the alert. |