A project team installed software, transferred knowledge to operations, sent the final report, and celebrated. One week later the client sends a list of unmet requirements and asks for fixes within the original budget. What should the project manager have done to prevent this?

The correct answer is to review the acceptance criteria and obtain formal client approval. This is a critical step in project closure. Formal acceptance ensures the client agrees that all requirements have been met according to the defined criteria, preventing later disputes about unmet expectations. Without this formal sign-off, the project is not truly complete, and the team remains liable for perceived deficiencies. Allocating a risk budget for post-release improvements is a reactive measure and doesn't address the root cause of unmet requirements. Conducting a pilot might help understand performance but doesn't guarantee formal acceptance of all requirements. Holding regular meetings is good practice for communication but doesn't substitute for the formal sign-off on deliverables against agreed-upon acceptance criteria.