Changes to formally controlled documentation, plans, etc.

According to the PMBOK® Guide, changes to formally controlled documentation, plans, or other project artifacts to reflect modified or additional ideas or content are specifically defined as updates.

Definition of Updates: An update is a change to a project document or the project management plan that does not necessarily stem from a performance issue or a defect. Instead, it reflects a refinement of the project’s strategy, a change in stakeholder requirements, or the inclusion of more detailed information as the project progresses (progressive elaboration).

Relationship with Change Control: While updates to simple project documents (like the Issue Log) may happen continuously, updates to formally controlled documents—such as the Schedule Baseline or the Scope Statement—must go through the Perform Integrated Change Control process. Once a change request is approved, the resulting modification to the plan is categorized as an update.

Context in the Process: Updates are standard outputs for almost all monitoring and controlling processes. For example, if a risk response is selected, it results in " Project Management Plan Updates " and " Project Document Updates. "

Comparison with Other Options:

Defect Repairs (B): This is a formal change request to modify a nonconforming product or product component. It focuses on fixing something that is " broken " or does not meet quality standards, rather than reflecting " additional ideas. "

Preventive Actions (C): These are intentional activities that ensure the future performance of the project work is aligned with the project management plan. They are proactive and aimed at avoiding potential problems.

Corrective Actions (D): These are intentional activities that realign the performance of the project work with the project management plan. They are reactive and aimed at bringing " actuals " back to the " baseline. "