Manage Projects With AI

Adapt the Plan When Projects Change

Adapt the Plan When Projects Change

Even a realistic weekly plan can stop fitting. A delivery moves, someone becomes unavailable, work takes longer than expected, or a client asks for something new. Projects don't always run as initially planned, and it's not a problem on its own. Problems start when you act on a new update in isolation, before checking how it affects other tasks, commitments, resources, or projects.

In this lesson, you'll learn how to react to the recent changes and ad hocs and keep all your projects organized.

In Lesson 2, you set up a daily brief that can surface new information. In Lesson 3, you built a feasible weekly view and a health check that shows when the week no longer works. This lesson starts when a change can't be handled with a routine update or the flexibility that's already been agreed. AI can help you trace the impact and compare practical ways to respond.

By the end of this lesson, you'll be able to turn a disruptive change into a reviewed decision, update the affected plans, communicate the approved change, and check that the week works again.

Choose the Right Response to the Change

Evaluate Project Changes Before You React

Projects rarely change in one neat, predictable way. A supplier may move a delivery, a client may request extra work, a contractor may cancel, someone may become unavailable, or a task may take longer than expected. Some changes are small. Others can disrupt several projects at once.

Treat the change as routine when confirmed evidence shows that it fits within already-agreed flexibility and leaves these areas unchanged. It may still require a factual tracker update or a work-block adjustment, but it doesn't require a new tradeoff.

Treat a change as a significant conflict when it could put any of the following at risk:

  • A confirmed scope, price, payment term, acceptance criteria, handoff, or deadline
  • The person, dependency, or shared resource the work needs
  • A project's cost, profitability, or early cash needs
  • Capacity that was already protecting another project
  • A required quality, safety, legal, or compliance condition

If the impact is unclear or several small changes may add up to affect one of these areas, don't classify the change as routine yet. Record the uncertainty and check the combined effect first.

Before changing the plan, check exactly what the new information confirms. Record where it came from and when, then separate confirmed facts from requests, estimates, and missing details. Use that distinction to choose the right response.

Choose the Response

Once you've separated confirmed facts from requests, estimates, and unknowns, decide how much of the plan — if any — needs to change. The impact of the new information determines which of the responses to use. Before you react, check five things:

  • Evidence: Is the change confirmed, or is it still a request, estimate, or missing detail?
  • Commitment: Could it change something you've already promised about the scope, price, result, or timing?
  • Plan: Does it affect a task's Status, owner, dependency, work block, or another project?
  • Capacity and resources: Does the right person or shared resource still have enough room?
  • Business effect: Could the change add meaningful cost, affect cash timing, or require someone's approval?

After you did the check, you can now choose the response option:

  • If the new information doesn't affect current work or commitments, choose No plan change.
  • If a confirmed project fact has changed but the effect fits within already-agreed flexibility and doesn't alter scope, price, ownership, or a commitment, make a Routine update. Update the project tracker, the weekly view and the calendar. Then rerun the health check.
  • If the change may affect scope, price, a confirmed date, ownership, capacity, a shared resource, or another project, mark it Needs a decision. Keep the affected work marked this way until your or another project or task owner approves a workable option. In this lesson, you’ll focus exactly on this type of project change and how to handle it.

Record the Change Without Pretending You've Decided

After you check the impact and classify the response, update the current records with any facts that are already confirmed. If a final response still needs a decision, record those facts now, but leave any proposed changes to dates, owners, scope, or commitments unconfirmed until you approve an option.

Update only the fields supported by the confirmed information. If the change affects a task's current state, update status. For example, if materials are delayed and installation can't start, set installation to Waiting. If the client has only requested a new date, keep the current Status and record the requested date as unconfirmed.

This keeps the tracker accurate without turning an estimate or request into a new promise. You'll update the final action, timing, and commitments after you've chosen and confirmed a response.

For example, the small remodeling business from the earlier lessons manages several client jobs at once and keeps the current project info for each job in a project tracker.

One active job is a kitchen renovation. Its tracker shows materials due Tuesday, installation planned for Wednesday, and a confirmed Friday client handoff. On Monday, the supplier changes the estimated delivery to Thursday. The materials haven't arrived, and the installer hasn't confirmed a new time.

What should the owner do first?

Choose one answer.

Once a change needs a decision, compare it with the current project trackers and weekly view to see what now competes for the same time, person, resource, or money.