Allows for document changes within the project to be considered in an integrated fashion while reducing project risk, which often arises from changes made without consideration to the overall project objectives or plans.


Reviewing all change requests, approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating their disposition.


The Perform Integrated Change Control process is conducted from project inception through completion and is the ultimate responsibility of the project manager. The project management plan, the project scope statement, and other deliverables are maintained by carefully and continuously managing changes, either by rejecting changes or by approving changes, thereby assuring that only approved changes are incorporated into a revised baseline.

Changes may be requested by any stakeholder involved with the project. Although changes may be initiated verbally, they should be recorded in written form and entered into the change management and/or configuration management system. Change requests are subject to the process specified in the change control and configuration control systems. Those change request processes may require information on estimated time impacts and estimated cost impacts.

Every documented change request needs to be either approved or rejected by a responsible individual, usually the project sponsor or project manager. The responsible individual will be identified in the project management plan or by organizational procedures. When required, the Perform Integrated Change Control process includes a change control board, which is a formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions. Approved change requests can require new or revised cost estimates, activity sequences, schedule dates, resource requirements, and analysis of risk response alternatives. These changes can require adjustments to the project management plan and other project documents. The applied level of change control is dependent upon the application area, the complexity of the specific project, contract requirements, and the context and environment in which the project is performed. Customer or sponsor approval may be required for certain change requests after Change Control Board approval unless they are part of the Change Control Board.

Configuration control is focused on the specification of both the deliverables and the processes, while change control is focused on identifying, documenting, and approving or rejecting changes to the project documents, deliverables, or baselines.

Some of the configuration management activities included in the Perform Integrated Change Control process are as follows:

    • Configuration identification. Identification and selection of a configuration item to provide the basis for which the product configuration is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
    • Configuration status accounting. Information is recorded and reported as to when appropriate data about the configuration item should be provided. This information includes a listing of approved configuration identification, the status of proposed changes to the configuration, and the implementation status of approved changes.
    • Configuration verification and audit. Configuration verification and configuration audits ensure the composition of a project’s configuration items is correct and that corresponding changes are registered, assessed, approved, tracked, and correctly implemented. This ensures the functional requirements defined in the configuration documentation have been met.



  • Project Management Plan
  • Work Performance Reports
  • Change Requests


  • Approved Change Requests
  • Updated Change Log
  • Updated Project Management Plan
  • Updated Project Documents


  • Expert Judgement
  • Meetings
  • Change Control Tools

Task Instructions:

    1. Using the <?>, [the ?] with support from <?> is responsible for …