Assess a Consulting Project Change Before You Commit

A client asks for one more analysis, another stakeholder interview, or a revised deliverable. The request may sound small, but its impact rarely stays in one place.

Before you commit, run a short change impact assessment. The goal is not to slow the client down. It is to show what the change affects so you can make a deliberate tradeoff together.

Restate the requested outcome

Start by confirming what the client actually wants to achieve. “Add a dashboard” describes an output, not the decision or behavior it should support.

Ask what will be different if the change succeeds, who will use it, and when it becomes valuable. You may discover that a smaller adjustment meets the need without changing the project plan.

Write the request in one sentence:

Add a regional comparison to the findings so country leads can decide which implementation sequence to use.

That sentence gives you something specific to assess.

Check five areas of impact

Review the request against the parts of the engagement it can change:

Do not estimate from the request alone. Look at the work around it. One new interview also creates scheduling, preparation, synthesis, and review work.

Identify what can be exchanged

A change does not always require a longer schedule. Sometimes the best response is to replace lower-value work.

Offer clear options:

1. Add the request and move the affected milestone.

2. Add the request and remove or simplify another output.

3. Defer the request to a later phase.

4. Keep the current plan unchanged.

Avoid promising to absorb the work without naming the consequence. Unplanned effort usually reappears as rushed delivery, reduced quality, or work outside the agreed boundary.

Put the decision in writing

Summarize the request, the assessed impact, the options, and your recommendation. Keep the message short enough to decide from.

For example:

Adding the regional comparison will require two additional data cuts and a review with the country leads. We can move the findings review from September 18 to September 22, or replace the planned channel appendix and hold the current date. I recommend replacing the appendix because the comparison supports the implementation decision more directly. Please confirm by Thursday.

This gives the client a bounded choice. It also prevents two people from remembering different versions of the agreement.

Update every affected source of truth

Once the client decides, update the project plan, decision log, scope record, and relevant dates. Do not leave the approved change only in an email thread.

Record:

• what changed
• who approved it
• which option was selected
• the new scope or acceptance criteria
• any changed milestone or dependency
• any follow-up action and owner

If the change affects pricing, fees, or contract terms, follow the approval process in your agreement before beginning the work.

Review patterns, not just individual requests

One change may be reasonable. Repeated changes can reveal an unclear outcome, missing stakeholder, or weak decision process.

During project reviews, look for patterns. Are requests arriving after every sponsor meeting? Is the same deliverable being revised because acceptance criteria were never agreed? Is new work being added without removing anything?

Use that evidence to improve the working agreement or reset the plan with the client.

Make the tradeoff visible before saying yes

A change impact assessment turns an informal request into a shared decision. It helps you remain responsive without making hidden commitments.

The next time a client asks for an addition, restate the outcome, check the five areas of impact, offer options, and document the choice. A few minutes of clarity can prevent days of avoidable rework.

Related: A Scope Change Script Consultants Can Use | How to Use a Decision Log on Consulting Projects