A project can be reporting progress as planned and still carry significant exposure. The difference often lies in what the current status depends on, how much of the difficult work remains and whether the assumptions behind the forecast are still holding.
A Project Can Look Healthy on Paper
One of the most common situations in project reviews is a project that appears to be under control based on the information being reported. Progress is close to plan, the schedule shows most activities moving as expected, costs are within the approved budget and the project is reported as “on track.”
Yet, when the project is discussed in more detail, management may discover that several important decisions are still pending, critical approvals are taking longer than expected, procurement commitments have not been secured or a number of technical issues remain unresolved.
None of these issues necessarily mean that the project is already in trouble. The concern is whether they could affect the expected outcome and whether there is still enough time to respond effectively.
This is where the difference between current status and future exposure becomes important.
“On Track” Is a Statement About the Current Position
Project status reporting generally answers questions such as how much work has been completed, what activities are delayed, how much has been spent and what the latest forecast shows.
These are important measures. But an “on track” status can sometimes hide the conditions supporting that assessment.
A project may be showing 65% progress against 62% planned progress. On the surface, that looks positive. But if the remaining 35% includes the most technically difficult activities, long-lead procurement, system integration, testing and commissioning, the overall project position may be very different from what the progress percentage suggests.
The issue is not that the reported progress is wrong. The issue is that progress alone does not provide enough context to understand the likely outcome.
Why a Project Can Remain “Green” While Exposure Is Increasing
Several situations can cause this.
1. The Difficult Work May Still Be Ahead
Not all project work has the same level of complexity or risk.
Completing drawings, fabrication or routine installation may contribute significantly to reported progress. However, the remaining work may involve system integration, approvals, commissioning, performance testing or activities dependent on several other parties.
A project that is 80% complete is not necessarily 80% of the way to a successful completion.
The remaining 20% may contain a much higher concentration of risk than the work already completed.
2. The Forecast May Depend on Events That Have Not Happened Yet
A project forecast is based on assumptions.
A supplier may be expected to recover a delivery delay. An approval may be expected by a particular date. A design issue may be expected to close without significant rework. A client decision may be expected within an agreed timeframe.
As long as these events remain part of the expected sequence, the forecast may continue to appear reasonable.
But the confidence behind the forecast should change when the assumptions supporting it become less certain.
3. Risk Registers May Not Reflect the Real Project Exposure
A project can have a well-maintained risk register and still have limited visibility of its actual exposure.
A risk may be assigned an owner, probability and mitigation action, but management may not know what its materialisation would mean for the project's final cost or schedule.
The issue is therefore not simply whether risks are being recorded. It is whether the risks that matter are being connected to the project's expected outcome.
4. Functional Performance Can Hide Interface Problems
Engineering may be progressing according to its plan. Procurement may also be reporting acceptable performance. Construction may be mobilised as planned.
Yet the project can still face a problem if the output from one function is required by another and that dependency is not being actively managed.
This is particularly relevant in complex projects where engineering, procurement, manufacturing, construction, commissioning, clients and multiple contractors are working together.
Individual functions may appear to be performing well while the interfaces between them are becoming the real constraint.
5. Management Information May Arrive Too Late
A project team may know that a problem is developing, but the issue may only appear formally in a monthly management review.
By then, the available options may have reduced.
The timing of information therefore matters. Good project controls are not only about accuracy. They are also about providing information early enough for management to do something with it.
A Simple Example
Consider a project scheduled to complete in four months.
The latest report shows:
| Measure | Current Position |
| Actual project progress | 72% |
| Planned project progress | 70% |
| Cost | Within approved budget |
| Major milestones | On track |
| Reported project status | Green |
At first glance, there appears to be little reason for concern.
However, the project also has several unresolved conditions. Final engineering approval is still pending for an important system. One long-lead item has not yet reached the site. Integration between two packages has not been fully tested. Several client decisions remain open, and a number of changes are being discussed but have not yet been commercially resolved.
The project may still complete on time. But the confidence behind that forecast should not be the same as it was when these conditions were not present.
This is the distinction that project leaders need to recognise.
A project can be on track based on its current position while becoming less predictable based on what lies ahead.
What Makes an “On Track” Assessment Reliable?
The usefulness of an “on track” assessment depends on how it has been established. A status should not be based only on whether activities are progressing according to the current plan. It should also reflect whether the assumptions behind that plan remain valid.
For example, if a milestone is still forecast to be achieved because a supplier is expected to recover a two-week delay, the project status is partly dependent on that recovery actually happening. If a critical approval is expected next week, the forecast may also depend on that decision being received as assumed.
This does not mean that every assumption needs to become a formal risk or that every project review needs another reporting layer. It means that project leaders should understand what is supporting the current status and how much reliance is being placed on events that have not yet occurred.
A useful “on track” assessment therefore has some context behind it. It should be possible to explain not only why the project is currently considered on track, but also what would need to change for that assessment to change.
The Difference Between Being On Track and Being Safe
These two conditions are not necessarily the same.
A project may be on track because the current plan is still achievable. At the same time, the margin for achieving that plan may be reducing.
For example, a project may originally have had four weeks of schedule float on a critical activity. After several changes, the activity may still be forecast to finish on the required date, but the available float may have reduced to a few days.
The project is still technically on track.
However, its tolerance for further disruption has reduced.
This distinction matters because management attention should not begin only after the project moves into a red status. By then, some of the options for recovery may already have become more expensive, more difficult or unavailable.
When “Green” Needs More Explanation
A green status is useful when everyone understands what it means and what supports it.
Management should be cautious when “green” is being maintained primarily because:
- The forecast assumes several future events will happen as planned.
- Schedule float has reduced significantly but the milestone date has not yet moved.
- Remaining activities are more complex than the work already completed.
- Critical decisions or approvals are still pending.
- Dependencies between functions or contractors are not fully resolved.
- Commercial or contractual issues are still being assessed.
- Recovery actions are being assumed rather than demonstrated.
None of these conditions automatically mean that a project should be classified as red.
They indicate that the confidence behind the current status deserves closer attention.
A Practical Test for the Next Project Review
When a project is reported as “on track,” ask a slightly different question:
What would have to happen for this project to move from on track to at risk?
The answer can reveal more than another review of the current status.
If the project team can clearly identify the conditions that could change the status, those conditions can be monitored and addressed while there is still room to respond.
If the answer is unclear, the project may not have sufficient visibility of what is actually supporting its current forecast.
This is not about making project reviews more complicated. It is about making the “on track” assessment more meaningful.
Practical Takeaway
A project being “on track” is not necessarily a problem. The important question is how much confidence there is behind that status and how much tolerance remains for things to change.
Current progress, cost and schedule performance tell us where the project stands. They become more useful when we understand the assumptions supporting the forecast, the difficulty of the remaining work, the dependencies between functions and the conditions that could change the current assessment.
The objective is not to classify every uncertainty as a problem.
It is to recognise when a project is still technically on track but becoming increasingly vulnerable to the next disruption.
That is often the point at which management attention can make the greatest difference.
Is Your Project Really On Track?
If your project is reporting progress as planned but management has concerns about the confidence behind the forecast, we can discuss the situation and identify where greater visibility or intervention may be required.
Vaibhav Ganpule Consulting helps organizations strengthen project governance, performance visibility, recovery and commercial management through practical, execution-focused advisory.
Project Execution Excellence is the firm's core focus.