Managing Scope Changes During Development
New information can change a project, but the effect on delivery should be made explicit. A small-looking request may affect content, data or testing beyond the visible screen.

Record the proposed change and its impact
Explain the requested behaviour, why it is needed and which existing work it affects. Review dependencies before agreeing the change. Update the acceptance criteria and schedule where necessary, keeping the original scope understandable for everyone involved.
Practical checklist
- Describe the change clearly.
- Assess related pages and workflows.
- Agree priority and impact.
- Record the approved decision.
How to review the result
Avoid implementing an ambiguous request simply because it seems quick. A short written agreement helps prevent different expectations about what was included.