Your team is almost finished, and the work has already been reviewed. Then, just before the deadline, someone asks for one more change.
Maybe it is only a line of copy. Maybe it changes the offer behind the whole project. Either way, a quick yes can create an impossible promise when work has already moved downstream.
Before you accept a late project change, take a moment to find out what it will touch. Strong leaders do not reject every late request, but they do not agree automatically, either. These seven questions will help you respond without creating unnecessary confusion.
Why Does a Quick Yes Create Bigger Problems?
A quick yes often feels helpful. It shows flexibility and keeps the conversation positive. However, the person making the request may not see the work that has already been approved or the vendors that are already moving.
Before committing, look beyond the requested edit. The goal is not to make a simple change feel complicated. It is to identify the real work involved and show the available choices. That protects the result everyone expects.
1. What Exactly Needs To Change?
Start by turning the request into a specific action. Comments such as “make it stronger” or “update the look” can mean different things to different people. Ask what should look or read differently when the work is finished.
Repeat the request in your own words and confirm that you have it right. For example: “You would like the opening slide to focus on the new service, while the remaining slides stay the same.” That short summary gives the team a defined task and prevents the request from expanding during production.
2. Why Does the Change Need To Happen Now?
The reason behind the request helps determine its priority. An error or a change in customer information may need immediate attention. A personal preference may be valuable, but it may not justify disrupting work that is nearly complete.
Ask what changed since the last approval and what would happen if the request waited. This is not a challenge to the requester’s authority. It is a practical way to separate a necessary correction from an optional improvement.
3. Which Completed Work Will the Change Affect?
Next, trace the change through the project. Begin with the item being revised, and then follow anything else that relies on it.
A pricing update, for example, might affect both a proposal and a sales handout. It may also appear in other materials that reuse the same figures. The true size of the request is the amount of connected work, not the size of the first edit.
Ask the people closest to the work what will need to be reopened or checked again. Their answers may reveal dependencies that are invisible from the project plan.
4. What Has To Give?
When a meaningful change arrives late, something else may need to move. The team may need more time or a smaller revision. In other cases, the delivery plan may have to change. Pretending that nothing will move simply transfers the pressure to the people doing the work.
Present the options plainly:
- Keep the deadline, but reduce the size of the change.
- Complete the full change, but move the delivery date.
- Keep the change and deadline, but approve the added cost or support required.
Avoid presenting one option as the only reasonable answer. Your role is to show what each choice requires so the decision-maker can choose with accurate information.
5. Who Can Approve the Tradeoff?
Late changes become especially difficult when several people give separate instructions. Decide who can approve the revised scope before the team resumes work. That person should also have authority over any change to the deadline or cost.
Assigning one final decision-maker and a firm review window can also prevent approval delays from putting the revised schedule at risk. Other stakeholders can provide input, but their feedback should be consolidated into one clear response.
Be explicit about what needs approval and when. Instead of asking, “Does this look good?” try, “Please confirm the revised message and the Friday delivery date by 2 p.m. today.” A focused request is easier to answer and gives the team a dependable point at which work can continue.
6. Which Deliverables Can Still Meet the Deadline?
Internal edits are only part of the schedule. Outside vendors or required reviews may follow timelines that your team cannot speed up.
Check those downstream requirements before accepting the new deadline. Ask whether updated files can be prepared and reviewed in time. Then confirm that any outside vendor can still deliver them on schedule. When physical campaign materials are involved, make sure the files and production details can still support tight campaign launch deadlines without creating problems elsewhere.
If one part of the process cannot move faster, say so right away. A phased delivery or temporary alternative may preserve the most important goal without forcing every component into an unrealistic schedule.
7. How Will You Record the Final Decision?
Once the change is approved, record it where everyone involved can find it. The note does not need to become a long report. It should state what changed and who approved it. Name the final version and the next owner. If the deadline moved, record that too.
Send the summary to the requester and the people completing the work. Ask them to flag anything that does not match their understanding. This creates one reliable reference and reduces the chance that an outdated instruction will return later.
How To Give a Clear Answer
After answering the seven questions, you will know whether you can accept the late project change as requested. If not, you can say yes with conditions or move it to a later phase.
Yes: The change is clear and fits the deadline.
Conditional yes: The change can be completed if the delivery date moves or added support is approved.
Not now: The request has value, but it should be scheduled for a later phase rather than disrupting the current delivery.
Explain the reasoning briefly and focus on the project’s goal. A conditional yes is not poor service, and “not now” does not have to mean the change will never happen. Both can be responsible decisions when they protect the work and give the team a fair chance to deliver.
How To Stay Flexible Without Overpromising
A late change does not have to derail a project. Trouble starts when a small request receives a quick promise before anyone checks the work behind it.
Asking these questions before you commit gives the decision-maker a realistic choice, and your team will know exactly what to do next.