How do I assess the impact of a late change before agreeing to it?

Treat it as a decision to evaluate, not a commitment you have already made. Restate the agreed outcome and the request in plain terms. Then ask whether the request adds something, replaces something, or changes what counts as finished.

Look at completed, in-progress, and planned work that may need revisiting. Also note decisions or tasks that rely on the current version. Keep facts separate from assumptions, and write down what you do not yet know. The goal is to make the consequences discussable, not to invent an effort or time estimate.

Use one row per request, with these prompts:

• Request and outcome: What exactly is being asked, and what would count as meeting it?
• Current agreement: Which goal, deliverable, or acceptance condition would change?
• Work touched: What is complete, in progress, or planned that may need revisiting?
• Dependencies: Which decisions, people, or tasks rely on the current version?
• Trade-offs: What might be removed, deferred, or handled differently?
• Unknowns and decision owner: What needs clarification, and who can choose among options?

For example, suppose the agreed deliverable is an event announcement for one audience. A late request adds a second audience and another approval step. The wording may need revisiting, and you would need to clarify whether the new reviewer approves the whole announcement or only the added section. Those are impact questions—not a claim about how much time the change will take.

Possible options to discuss are keeping the original announcement, replacing or deferring another item, or considering a revised plan. Mark any unconfirmed requirements or dependencies as open questions.

Acknowledge the purpose of the request, then describe what is known and what remains open. For the example, you could say:

“Thanks for raising this. I understand the goal is to include [second audience]. The current agreement covers [original deliverable]. The request may affect [wording or review], and we still need to clarify [approval question]. We could keep the agreed version, swap [existing item] for this change, or discuss a revised plan after we confirm the requirements. Which outcome should we prioritize?”

Replace the brackets with specifics you can support. Do not present an option as feasible if you do not know what could be displaced or who has authority to choose. You can say that you need to check before proposing a firm plan.

Give a clear interim answer without accepting an unassessed change: “I can confirm the impact after I check [open question] and compare it with [affected work or outcome]. Until then, I can’t confirm that the current scope and plan still hold.”

Keep the discussion focused on the decision: the agreed outcome, the specific change, affected work, unknowns, and a small set of options. If the request changes during the conversation, restate it and update the worksheet rather than treating earlier assumptions as settled. End by confirming who decides, what option they chose, and what still needs checking. Record any revised expectation only after the relevant people agree.