Section: Volume D
Explanation:
Monitoring and Controlling Process Group
4.4 Monitor and Control Project Work
4.5 Perform Integrated Change Control
5.5 Validate Scope
5.6 Control Scope
6.7 Control Schedule
7.4 Control Costs
8.3 Control Quality
10.3 Control Communications
11.6 Control Risks
12.3 Control Procurements
13.4 Control Stakeholder Engagement
Process: 7.4 Control Costs
Definition: The process of monitoring the status of the project to update the project costs and managing changes to the cost baseline.
Key Benefit: The key benefit of this process is that it determines the cost baseline against which project performance can be monitored and controlled.
Inputs
1. Project management plan
2. Project funding requirements
3. Work performance data
4. Organizational process assets
Tools & Techniques
1. Earned value management
2. Forecasting
3. To-complete performance index (TCPI)
4. Performance reviews
5. Project management software
6. Reserve analysis
Outputs
1. Work performance information
2. Cost forecasts
3. Change requests
4. Project management plan updates
5. Project documents updates
6. Organizational process assets updates

Section: Volume D
Explanation:
Process: 4.1. Develop Project Charter
Definition: The process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Key Benefit: The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project.
Inputs
1. Project statement of work
2. Business case
3. Agreements
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project charter

Section: Volume C
Explanation:
4.5.3.2 Change Log
A change log is used to document changes that occur during a project. These changes and their impact to the project in terms of time, cost, and risk, are communicated to the appropriate stakeholders. Rejected change requests are also captured in the change log.
13.3.1.3 Change Log
Described in Section 4.5.3.2. A change log is used to document changes that occur during a project. These changes-and their impact on the project in terms of time, cost, and risk-are communicated to the appropriate stakeholders.

Section: Volume E
Explanation/Reference: https://4squareviews.com/2018/10/19/6th-edition-pmbok-guide-process-13-3-manage-stakeholder- engagement-outputs/