Handling a scope change during the sales conversation
A requested change should not become a promise simply because it sounds minor.
A practical approach
Record the change and explain what needs to be reviewed before it can be included. Check whether it affects price, timing or technical requirements. Issue an updated proposal through the normal process when appropriate. Avoid handwritten adjustments that leave different teams with conflicting versions of the scope.
Put it into practice
- Capture the requested change
- Review its dependencies
- Issue a controlled revision
General workflow guidance. Confirm current responsibilities, availability and terms with the appropriate team. This article is not a project-specific technical assessment or a promise of compensation.