Changing control of a project isn't always a bad thing. there is a process to follow, each company has a specific protocol to follow but they all guide you to end up with the same results, which is changing the control of a project. From my experience, when my team received the analyzed data from the statistician, the project manager and my team came to a decision to change the control of the project just to improve the outcome/data. A change of control protocol forms were filled out and sent to upper management for approval. 

Changes are inevitable during the course of a project development. Some of the reasons why these changes occur are technical, procedural, financial and more. All these changes are dependent on the baseline performance. All changes must be evaluated before a decision can be reached. The change control system has various process, tools and techniques to make any changes to the ongoing project.

Overall, change controls are influencing factors that create change to ensure beneficial results. Change controls are to determine that change has occurred as well as manage the change as it happens. The inputs or requirements to change control are the baseline performance according to the project plan, performance reports and change requests, oral or written. All changes must be evaluated before a decision can be made through a change control system and/or board. The outputs are project plan updates, corrective actions and ultimately lessons learned. There is no one thing that causes change but change isn't bad. Actually, if controlled correctly, these changes should be a good thing and cause the project to head in better directions.