What is the approved method to handle scope changes to avoid cost overruns?

• A. Written change orders or amendments with scope, price, and schedule changes approved by authorized parties.
• B. Verbal change orders confirmed via email
• C. Postponing changes until the next procurement cycle
• D. Approving changes solely by the project manager

Answer: (A)

The main idea here is to control changes with formal, documented processes. Using written change orders or amendments that clearly spell out what is changing in scope, how much it will cost, and how the schedule shifts, and obtaining approval from the appropriate authorities, creates a traceable record. This keeps everyone aligned, ensures the impacts on budget and timeline are analyzed before work begins, and provides a defensible baseline for project governance. When changes are formalized in writing and approved, there’s accountability, and plans aren’t altered on a whim—this is the best defense against cost overruns.

Verbal change orders confirmed by email lack that formal sign-off and traceability, making disputes easier and increasing the risk of uncontrolled scope creep. Waiting to implement changes until the next procurement cycle introduces delays and uncertainty, which can inflate overall costs and push the project off track. Allowing changes to be approved solely by the project manager centralizes authority without proper multi-party review, reducing accountability and increasing the chance that impacts to cost and schedule aren’t fully considered.