---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Communicate a fix

# Communicate a fix {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
After you have completed root cause analysis of a problem and have come up with a
resolution or fix for that problem, submit change requests to get the problem fixed.
Documenting and communicating fix helps user to know the solution to a problem.

## Before you begin

Role required: admin, problem_admin, problem_manager or problem_coordinator

## About this task

When you communicate a fix, notification is sent to related incidents that a fix is available. The Incident process is designed to use the fix information or to notify the user of the same. For more information on notification, refer [Synchronization between incident and problem records](https://servicenow-prod.fluidtopics.net/gmiztXusKzs6aRp7mUhcjw "Change in a Problem record impacts related Incident records. Notification is sent to the user for each such update.").  
Note:  
The topic applies to Problems where you have activated the Problem Management Best Practice --- Madrid (com.snc.best_practice.problem.madrid) plugin.

## Procedure

1. Navigate to AllProblemOpen.
2. Open the Problem record.
3. Enter the information in the Resolution InformationFix notes field.
4. Save the record.
5. Under Related Links, click Communicate Fix.  
   The fix information is copied from the Fix notes field on the Problem form to the Additional Comments field on the Incident form. An email notification is sent to the caller and the user who is assigned to the Incident.
{#communicate-a-fix__steps_wzy_q5q_pfb}

*[\>]: and then