September 21, 2026 • 4 Min Read

The team is confident. The year-end delivery date has not moved. But, the testing may have slipped, an important decision may still be open, or the same critical resources may be supporting several initiatives at once.

None of those issues alone may be enough to turn a project red. Yet together, they may mean the project has lost something more important: its ability to recover. A project can technically remain on schedule even when the assumptions behind the schedule have become unrealistic. If the year-end date now depends on every remaining decision happening on time, every dependency holding and no major problems emerging in testing, the project is no longer comfortably on track.

That is what leaders need to identify now in September, before all flexibility has disappeared. Early fall still leaves options. Scope can be reduced. Resources can be moved. Decisions can be escalated. Work can be sequenced differently. A phased launch may make more sense than a full implementation. In some cases, resetting the deadline may be better than forcing the organization toward an outcome it is no longer prepared to deliver.

Those choices become much harder with every day that goes by. And the usable calendar is often shorter than it looks. Holidays, year-end close, technology freezes, vacations and competing business priorities can turn a December 31 deadline into a mid-December one.

Look at What Has Moved to the End

One of the clearest warning signs is work steadily accumulating at the back of the plan.

Testing gets compressed. Training moves closer to go-live. Integration begins overlapping with activities that were supposed to follow it. Data remediation continues later than expected. Each adjustment can seem manageable in isolation. The problem is the pattern.

Leaders should ask whether the delivery date has been preserved by repeatedly pushing important work into a smaller and smaller window.

Unresolved decisions can create the same kind of hidden pressure.

Teams can often work around an open decision for a while, particularly early in a program. But eventually downstream work begins depending on assumptions that have not yet been confirmed.

Leaders therefore need to look beyond task completion. Which decisions still have to be made? Who owns them? When do they become critical? And what happens if they slip another two weeks?

Those questions can reveal more about the health of a project than a percentage-complete number.

Look Across the Portfolio, Not Just at Individual Projects

Some year-end risks are difficult to see from inside a single project.

Five initiatives may each have reasonable resource plans, for example, while all five depend on the same finance leaders, data specialists, cybersecurity team or business process owners during the fourth quarter.

Individually, the plans work. Collectively, they may not.

Leaders need to look across the portfolio for places where critical resources, decision-makers, testing environments or change capacity are being counted more than once.

Organizational timing matters too. A technology implementation may be ready to launch in December, but the business may simultaneously be managing financial close, annual planning and several other major changes.

Watch What Teams Start Sacrificing

Another warning sign appears when teams begin protecting the deadline at the expense of the implementation.

Testing gets reduced. Training is shortened. Documentation is pushed beyond launch. Data issues are deferred. Change-management activity becomes little more than communications.

This is where leaders need to distinguish between meeting the date and achieving the outcome. A project that launches on December 15 but creates workarounds, weak adoption or operational problems in January has not necessarily succeeded.

When the activities that make the change sustainable are being cut to protect the schedule, the deadline itself may need to be questioned.

Run a Year-End Viability Review

For major initiatives expected to deliver before year-end, leaders may need a different kind of project review. Rather than asking teams to walk through current status, work backward from the promised outcome.

What absolutely must be true by October 1? By November 1? Before December begins?

Then test the assumptions underneath those milestones.

Which decisions must be made? Which dependencies have to close? Which people are essential? How much testing remains? Where is the plan relying on resources that may not actually be available?

And perhaps most important:

What happens if one more thing slips?

If a two-week delay can still be absorbed, the project may have enough runway. If it would unravel the year-end plan, leadership needs to know now.

The goal is not to turn more projects from green to yellow or red. It is to determine whether there is still a credible path from where the project stands today to the outcome the organization has promised.

A project does not become risky the day it misses its deadline. By then, leaders are simply seeing the result. The opportunity is to recognize much earlier when a project that still looks healthy is quietly running out of runway.