Which process ensures that changes to a project are documented for future reference?

The documentation process is essential in any project as it provides a structured way to record changes, decisions, and important information throughout the project's lifecycle. This practice ensures that all modifications are captured in an organized manner, making it easier for team members to reference the history of the project and understand the rationale behind various changes. This not only facilitates continuity when team members change but also helps in maintaining a clear record for future projects or for auditing purposes.

By documenting changes, teams can communicate more effectively, establish accountability, and create a valuable resource that can be consulted in the future. This practice is crucial for managing project scope and maintaining alignment with stakeholders' expectations, as it provides a clear timeline and context for all decisions made throughout the project.

In contrast, processes like risk management focus primarily on identifying and mitigating potential risks, while quality assurance is about ensuring the outputs meet specific standards. The review phase is typically a part of the process where evaluations happen, but it does not inherently include ongoing documentation of changes. Thus, the documentation process is the correct choice as it specifically addresses the need for systematic recording of changes for future reference.