Roles and responsibilities of Change Coordinator

1.0             Change Coordinator: The primary role of the change coordinator is to coordinate the flow of documents surrounding any changes to an ongoing project or large system.

1.       Ensure documentation of the request must include the actual item to be changed, the business rational for the request, and the expected benefits and risks inherent with the request.

2.       Registers changes and applies the correct change model and change detail.

3.      Schedules changes according to the plan created previously.

4.      Creates the change tasks for building, testing, and implementing a change.

5.      Coordinates the assessment phase of the change and creates change planning based upon the assessment information.

6.      Verifies that the change passed the test criteria.

7.      Verifies that the change is implemented successfully in the production environment.

8.      After implementation, evaluates the change handling and closes the change.

9.      After or during a change implementation failure, activates the remediation plan to return the system to a pre-change state.

10.   Evaluate its risk: determined by impact and complexity.

11.    Evaluate its Priority: Determined by the Urgency and importance of the change.

12.    Business Assessment – How will the change benefit the customer?  Will SLAs be impacted?  Is the change within scope of the contract?

13.   Technical Assessment – Why do we need to do this change and what will happen if we don’t do the change?

14.   Ensure “Step-by-Step” Installation Instructions, Back out Plan, Back out duration, Customer Impact, Post Checks.

15.   Pre-implementation test results ,

16.   Detailed Instructions for support groups, Communications, documentation updates/locations, and contacts. Technical and business feasibility.

17.   Responsibility to ensure that all requests are approved by the appropriate person. By requiring approval from senior staff, all requests must be explained to a member of the management team, who may have a different perspective and see additional risks or benefits.

18.    Check the timing of the check; ensure this change is not clashed with other changes.

19.   Check the if the duration of the change is within the change window.

20.  Check if all the required approvers are added to change record and change is approved by all the relevant parties.

21.    If a change is rejected, the person rejecting the change should add a note specifying why the change was rejected. Notification should be made to the assignee/requester so that the situation can address quickly.

22.   Verify the change results.

23.   Check if change is implemented within the agreed upon window.

                                       Change Management Process Flowchart For Reference