Request
State the change clearly
Describe what is being added, removed or changed instead of burying the request inside unrelated feedback.
Reason
Explain why it matters
Knowing the objective behind the request often reveals a simpler way to reach the same result.
Impact
Check the consequences
Identify whether the change affects timing, dependencies, testing, content, design, cost or previously approved work.
Priority
Decide what moves
If the new request is urgent, decide whether another item should move later rather than pretending the schedule is unlimited.
Approval
Make the decision visible
Record whether the change is accepted now, deferred, replaced by another solution or declined.
Done
Update completion criteria
When scope changes, the definition of done should change with it so the project has a real finish line.
