This documentation applies to the 8.1 version of Change Management, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Closed stage - Completing change requests

In the Closed stage of the change request's lifecycle, the change manager reviews all the implemented changes to make sure that each objective was met. A request cannot be closed until all tasks are closed. When all the tasks related to a request are closed due to success, cancellation, or failure, the requester and the change manager are notified that the change is resolved.


Change requests can be closed by users with the functional role of a Change Manager or Change Coordinator.

In this final stage, the process of closing the change request varies based on whether the request requires Close Down approval:

  • If no approval is required, the requester can set the request to Closed after confirming that the request was resolved to his or her satisfaction. If the requester does not close the change request within the allowed response time of it being resolved, the request is closed automatically after a specified period of time. The Status Reason for the request indicates that the request was automatically closed.
    The allowed response time depends on how the application administrator configured the BMC Remedy Change Management application. The default is 10 days. If the requester is not satisfied with the change request, the requester can reopen it. The change manager is notified that the request is reopened, and must respond.
  • If the request requires Close Down approval, the change request moves to the Completed status with the status reason Final Review Pending. The approvers approve it and moves the change to the status Final Review Completed. When moved to the next stage, the change request is set to status Closed with a status reason of Successful. After IT and the business unit (BU) have completed the review, no further activities are performed on this request.


User must also update CI Unavailability records as required during the final stage.

Closing change requests

To reach Closed status, you must enter actual start and end dates. You must also enter a performance rating from 1 (the worst rating) to 5 (the best rating) for the entire change process. You should consider all aspects of the change request's performance. This includes looking at how the change manager performed, how well things went with this operational Category Type and Item (CTI), and any other risk factors. The performance rating stored on the request is then used, in combination with previous historical ratings, to compute an overall performance for each of the risk factors.The performance history of a change manager becomes more meaningful as more changes are accomplished. The performance rating is an average of the performance of the assigned manager or the chosen operational CTI. This in turn helps a more accurate risk assessment to be performed on new requests.


Performance ratings for requests are not rolled into the average performance until the request is Closed. A request in Completed status does not have the performance rating averaged into the overall rating yet.

When a change request fixes a known error, the owner of the known error is notified, so that its status can be updated.

Was this page helpful? Yes No Submitting... Thank you


  1. Sidhdesh Punaskar

    CRQ cannot be closed with change user permission and with role of change coordinator or manager,

    It requires Change Master permission to close the CRQ.

    The filter CHG:CRQ:PermsnLockDown_NoWriteAccess seems to be new in 8.1.1.


    This is fixed in defect SW00439527.

    May 20, 2014 10:19
    1. Ash Hall

      I have raised ISS04384425 concerning this Sidhdesh as in 8.1 SP1 the 'Change Coordinator' is still unable to close the Change Request, and SW00439527 looks only applicable to 8.1.00 and doesn't alter the above mentioned Filter.

      Nov 05, 2014 05:56
  2. Martin Penev



    In version 8.1 there is no Default User View of the change form. How do we set the performance rating then? I was not able to find such a functionality when Best Practice View is used. Is this functionality deprecated now?




    Mar 13, 2015 09:53