--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Source record change notifications # Source record change notifications {#ariaid-title1} Release version: Australia Updated August 27, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Source record change notifications The Digital resilience incident reporting (DRIR) application in the Australia release version 23.x.x automatically detects and notifies you of changes made to the incident linked to your DRIR case. This ensures your case record stays updated with the latest incident information, supporting timely and accurate regulatory reporting. Show full answer Show less ## How Notifications Work * **Email notifications** are sent to members of the case watch list and the assigned analyst whenever tracked fields on the linked incident change. * Notifications include details such as the DRIR case number, source incident number, the user who made the change, timestamps, and the specific fields changed with old and new values. * Tracked fields typically include critical incident attributes like State, Impact, and Urgency, though additional fields may be configured in your environment. * Email delivery requires proper mail protocol configuration. ## Benefits for ServiceNow Customers * Receive real-time updates on important incident changes without manual monitoring. * Maintain an audit trail for all source incident modifications, including user actions and timestamps, to support compliance and regulatory needs. * Stay aligned with key reporting deadlines---initial report within 24 hours, intermediate report within 72 hours, and final report by 1 month from incident classification. * Eliminate the need for manual re-checks by automatically receiving notifications of relevant updates. ## Handling Orphaned Pending Updates If a linked incident is deleted or unlinked before you review a pending update, the system flags that update as orphaned but retains it for audit purposes. Orphaned updates cannot be traced back to an active incident and require review with your administrator to determine if manual case updates are needed. ## Recipients of Notifications * All members on the case watch list * The analyst assigned to the case * Note: Notification recipients depend on organizational roles and watch-list memberships as configured by your administrator. ## Next Steps To effectively use this feature, confirm with your administrator which fields are tracked and who receives notifications. Regularly review source record changes within your DRIR cases to ensure case data accuracy and compliance with reporting requirements. When the incident linked to your Digital resilience incident reporting (DRIR) case changes, you receive a notification in the case record and an email alert. You can then review the latest updates. ## Source record changes {#source-record-change-notifications__section_overview} Starting with Digital resilience incident reporting version 23.x.x, the Digital resilience incident reporting (DRIR) application detects modifications to the incident linked to your DRIR case. When field-level changes occur on that source incident, you receive notifications to keep your case current with the latest incident data. This feature tracks changes to critical fields such as state, impact, and urgency. Each time the source incident is modified, the system generates audit-trail records with complete information about the changes. These records include field names, old and new values, the user who made the change, and the timestamp. ## Email notifications {#source-record-change-notifications__section_benefits} These notifications help you stay informed about source incident changes. Review these changes to support your regulatory reporting timelines: * Initial report: 24 hours from incident classification * Intermediate report: 72 hours from incident classification * Final report: 1 month from incident classification By reviewing source record changes promptly, you can update your case data without requiring manual re-checks, which supports staying on track with these timelines. ## How notifications work {#source-record-change-notifications__section_how_notifications_work} Notifications are sent through two channels: Email notification : An email notification is sent to members of the case watch list and the assigned analyst whenever a tracked field changes on the linked source record. Email contents : * A statement that the source record has been updated * The DRIR case number * The source record number (for example, the incident number) * The user who made the change and the timestamp * The names of fields that changed, with old and new values for each * A direct link to the DRIR case {#source-record-change-notifications__ul_zt2_hm5_jkc} : Note: Email delivery requires a configured mail protocol. ## Tracked fields on the form {#source-record-change-notifications__section_tracked_fields} Different fields on the linked source incident trigger notifications when changed, such as State, Impact, and Urgency. Note: Additional fields may be tracked depending on your DRIR configuration. Confirm the complete list of tracked fields with your administrator. ## Orphaned pending updates {#source-record-change-notifications__section_orphaned_updates} If the source incident linked to a pending update is deleted or unlinked from the DRIR case before you review the change, the pending update record remains visible. It is flagged as orphaned. Orphaned pending updates are not automatically removed to preserve the audit trail. However, they can no longer be traced back to an active source record. Note: Review orphaned pending updates with your administrator to determine whether the case data still needs to be updated manually. ## Recipients of the notifications {#source-record-change-notifications__section_who_receives_notifications} Notifications are sent to: * Members added to the case watch list * Assigned analyst for the case Note: Confirm with your administrator which users in your organization receive notifications based on watch-list membership and assigned roles. **Related tasks** * [Review source record changes in a DRIR case](https://www.servicenow.com/docs/lQ_K4BzCijpD2~GlQ6UWtg "When the linked incident changes, review the modifications in your DRIR case or in the email notification to stay current with incident updates.")