---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Communicating the outcome of a problem

# Communicating the outcome of a problem {#ariaid-title1}

Document the cause and resolution of a problem to resolve incoming incidents quickly and
avoid further problems to be raised on the same issue.
* **[Communicate workaround for Problem](https://www.servicenow.com/docs/Ff1TL7mTHGXnW~fdavbWiA#communicate-workaround)**   
  Document and communicate workaround to let others know that you are aware of the issue. The workaround is a temporary way to restore service failures and lessen the impact of a Problem for which an actual resolution is not yet available.
* **[Communicate a fix](https://www.servicenow.com/docs/3_W6Zo~QMoHpIXxMrXDttQ)**   
  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.
* **[Knowledge articles from problems](https://www.servicenow.com/docs/bPCCwqGjsGfUUIDd5QU_PA)**   
  Knowledge bases house the information an organization wants to keep and share. The Problem form includes four options for creating knowledge and communicating information.
* **[Create a known error article](https://www.servicenow.com/docs/vfcrA3WshW8VWR9N3h95RA)**   
  Create known error articles as reference material. The known error articles document the root cause and the workaround of the problem to help with deflecting incidents.
* **[Post knowledge](https://www.servicenow.com/docs/BhIE9bPFklWTuBEXgSfs3Q)**   
  You can create a knowledge article from the problem immediately, and not wait for when the problem is closed.