01 / Understand the request before defending the plan.
A new request often signals a need that was not clear at the start. Ask what the requester is trying to achieve and what prompted the change. Understanding the reason helps you find an appropriate response instead of immediately treating every addition as a conflict.
02 / Compare it with the agreed work.
Check whether the request changes an existing deliverable or introduces a new one. Compare it with the brief, feedback round, and approval history. Describe the difference in plain language. The goal is to make the decision concrete enough for everyone to discuss the same thing.
03 / Make the trade-offs visible.
Ask the people doing the work what the change affects. It may alter the sequence, require another input, or move a review. Present the impact and the available choices to the person authorized to decide. Do not promise a timeline or fee adjustment on another person’s behalf.
04 / Record the new agreement.
Once the decision is made, update the tracker, brief, and relevant team members. Mark superseded direction clearly. A change is not fully managed when it has been discussed; it is managed when the team has a reliable understanding of what to do next.
A useful message to adapt.
“This adds a new deliverable to the current scope. I’ll confirm the production and review impact with the team, then share the options so we can agree the next step.” It acknowledges the request, identifies the issue, and offers a clear route forward without creating an unapproved commitment.
Choose one idea from this note and apply it to the next brief, update, or handover you prepare.
Talk through a project with me ↗