TOPIC: Change process - What comes first?

I am finding it confusing to understand what comes first in the Change Process - evaluate impacts and identify options or submit change request?

Project managers usually evaluate the impacts first. Change request occurred when there is a difference in your planned vs. actual performance. When you submit change requests, you may have to provide information on estimated cost impacts and/or schedule impacts and also possible risks. Therefore, without any evaluation or estimates, it will be difficult for the CCB to review and approve your change request.

Hi Cynthia,

I found the following link in the Forum: www.dummies.com/careers/project-manageme...-certification-exam/

It says that the change request comes first, which is why I was confused. Or does it mean that impacts have to be assessed both before and after submitting the change request? Please confirm.

Page 115 of PMBOK stated "...change requests may require information on estimated schedule impacts and estimated cost impacts prior to approval";
Page 117 Section 4.6.1.4 stated "change requests that have an impact on project baselines should normally include information about the cost of implementing the change....";
Page 120 section 4.6.2.5 stated that in a change control meetings "assessing the impact of the changes is an essential part of the meeting" for decision-making;
Putting the above together, you will need some initial estimates on how much that change will impact the baselines so that the CCB can use that information to make a decision. Once a change request has been approved and implemented, you are require to determine whether there is a deviation between your actual performance vs. your estimates.

In essence, before submitting the change request, you will do some estimation on how the change will impact your baselines and then when change is approved and implemented, you will evaluate your planned vs. the actual performance.