7 warning signs your project may be less healthy than the status report suggests
Written by Andrew McDonald, Founder & Principal at Carpadium· Published 24 September 2026
A Green status report does not necessarily mean a project is healthy. Delivery problems often develop gradually beneath headline reporting before they become significant enough to change the project’s formal status.
For executives and project sponsors, the challenge is knowing which signals warrant closer attention. Schedule movement, unresolved dependencies, increasing cost pressure and declining business readiness can all indicate that reported status and underlying delivery health are beginning to diverge.
Executive guide | Project Health
BEYOND THE STATUS REPORT
Project problems rarely appear overnight.
Projects that eventually become Amber or Red often show signs of deterioration well before their formal status changes.
The problem is not necessarily poor reporting. Status reporting simplifies a complex delivery environment into a manageable executive view. In doing so, however, individual indicators can appear acceptable while the overall delivery position is becoming progressively less credible.
Executives therefore need to consider not only what the project is reporting, but whether the underlying evidence continues to support confidence in delivery.
“The important question is not simply whether the project is Green. It is whether the evidence supports confidence that it will remain Green.”
WHAT TO LOOK FOR
Seven signals that deserve executive attention.
No single indicator necessarily means a project is in trouble. The concern increases when several signals appear together or persist across reporting periods.
Milestones keep moving
Schedule movement is normal in complex delivery. Repeated movement without transparent re-baselining is different.
Warning indicators
- milestones repeatedly shifting into future reporting periods
- intermediate dates moving while the final completion date remains unchanged
- increasing reliance on schedule contingency
- activities becoming increasingly concurrent to preserve the headline date
- recovery actions appearing in plans without measurable schedule improvement
Executive question
“What has changed in the critical path over the last three reporting periods?”
Critical dependencies remain unresolved
A project may report its own activities as Green while depending on decisions, systems, vendors or other projects that are not ready.
Warning indicators
- critical dependencies without clear owners
- dependency dates repeatedly moving
- assumptions being used in place of confirmed decisions
- external teams not recognising the same dependency dates
- major milestones dependent on work outside the project’s direct control
Executive question
“Which dependencies could prevent the next major milestone from being achieved?”
Forecast cost is increasing while status remains Green
Cost pressure can provide an early indication that the delivery plan is becoming harder to execute.
Warning indicators
- contingency being consumed earlier than planned
- repeated requests for additional resources
- increasing vendor expenditure
- forecast-to-complete increasing without corresponding scope change
- financial pressure being managed through deferred activity
Executive question
“How much contingency has been consumed, and what risks is the remaining contingency expected to cover?”
Scope is becoming progressively less certain
Projects can appear to remain on schedule by allowing unresolved scope decisions to accumulate.
Warning indicators
- significant requirements remaining unresolved late in delivery
- increasing numbers of change requests
- scope being deferred to later releases without clear impact assessment
- different stakeholders holding different views of what will actually be delivered
- acceptance criteria remaining unclear
Executive question
“Is the organisation still expecting the same outcome that the delivery team is planning to provide?”
Business readiness is falling behind technical delivery
Technical progress does not automatically mean the organisation will be ready to use what is being delivered.
Warning indicators
- operating-model decisions remaining unresolved
- training, communications or transition activity starting late
- business resources unavailable for testing or implementation
- process changes not agreed
- benefits ownership remaining unclear
Executive question
“If the technology were ready tomorrow, would the business actually be ready to adopt it?”
Governance is spending more time explaining status than making decisions
Effective governance should resolve issues, make trade-offs and create the conditions for successful delivery.
Warning indicators
- the same risks appearing across multiple Steering Committee meetings
- decisions repeatedly deferred
- papers dominated by activity reporting
- significant issues being discussed outside formal governance
- unclear accountability for difficult decisions
Executive question
“Which material decisions have remained unresolved for more than one governance cycle?”
Stakeholder confidence and reported status are diverging
Sometimes an important early signal is that stakeholder confidence no longer aligns with the position suggested by formal reporting. This does not mean perception should replace evidence. It means the divergence should trigger closer examination of the evidence.
Warning indicators
- sponsors repeatedly asking for additional detail
- executives seeking informal assurance outside normal reporting
- stakeholders expressing concerns not reflected in project status
- confidence in forecasts declining
- increasingly defensive explanations of project performance
Executive question
“What evidence would demonstrate that the current reported status remains credible?”
THE PATTERN MATTERS
One warning sign may be manageable. Several together tell a different story.
Complex projects will always experience issues. The presence of an individual issue is therefore less important than the pattern developing across the project.
For example, a milestone moving may be entirely reasonable. But when milestone movement occurs alongside increasing cost forecasts, unresolved dependencies and declining business readiness, the combined evidence may indicate that the delivery position is materially weaker than headline reporting suggests.
Underlying evidence
Independent assurance examines the combined evidence rather than relying on any single indicator.
TEST THE EVIDENCE
Five questions can quickly test delivery confidence.
Has the critical path changed?
What has moved, why has it moved and what assumptions now protect the final milestone?
Is forecast-to-complete increasing?
Understand cost trends, contingency consumption and the financial implications of remaining risks.
Are critical dependencies genuinely under control?
Identify dependencies that could prevent major milestones regardless of progress within the project itself.
Will the business actually be ready?
Examine operational readiness, adoption, transition, capability and benefits—not simply technical completion.
Does the evidence support the reported status?
Test whether schedule, cost, scope, risk, governance and readiness collectively support the project’s stated position.
The objective is not to challenge a Green status for the sake of it. It is to understand whether Green remains credible.
WHY CONFIDENCE DETERIORATES
Projects rarely turn Red because of one event.
More commonly, delivery confidence deteriorates through the accumulation of unresolved issues, optimistic assumptions and decisions that are progressively deferred.
PRESSURE EMERGES
Milestones move, dependencies slip or costs begin increasing.
WORKAROUNDS DEVELOP
Teams protect headline commitments through contingency, concurrency, assumptions or scope deferral.
DELIVERY FLEXIBILITY REDUCES
Contingency disappears, options narrow and unresolved decisions become critical.
STATUS CATCHES UP
The formal RAG position changes only once the impact can no longer reasonably be absorbed.
By the time status turns Red, many of the easiest intervention options may already have disappeared.
WHEN CONFIDENCE IS UNCERTAIN
Test the position before attempting to fix it.
When several warning signs are present, the first response should not automatically be a recovery program, additional governance or more detailed reporting.
The priority is to establish the actual delivery position: what is working, what is deteriorating, which risks are material and whether the current plan remains credible.
PROJECT PULSE
A rapid independent perspective where executives need a focused view of a specific concern or delivery question.
PROJECT HEALTH CHECK
A point-in-time, evidence-based assessment of overall project health and delivery confidence.
PROJECT RECOVERY
Appropriate where delivery confidence has materially deteriorated and the initiative requires stabilisation, reprioritisation or replanning.
COMMON QUESTIONS
Project warning signs FAQs
Yes. Complex projects routinely carry risks while remaining healthy. The important question is whether those risks are understood, owned, adequately mitigated and reflected in forecasts and decision-making.
Not necessarily. Individual milestones can move for legitimate reasons. Repeated movement, erosion of contingency or changes that are not transparently reflected in the delivery baseline warrant closer examination.
Project sponsors, Steering Committees and accountable executives should test whether the evidence supports reported status. Independent assurance can provide additional challenge where confidence is uncertain or the initiative is particularly complex or material.
A Health Check can be useful when multiple warning signs persist, executives lack confidence in reported status, major investment or stage-gate decisions are approaching, or significant delivery milestones are at risk.
No. Independent review provides an additional perspective on complex delivery. Its purpose is to test assumptions and evidence, not to replace project management or governance.
Findings should be prioritised according to their impact on delivery confidence. Some issues may require targeted corrective action, while materially deteriorated initiatives may require a structured recovery response.
WRITTEN BY
Andrew McDonald
Founder & Principal, Carpadium
Andrew leads and delivers Carpadium’s independent project and program assurance, health check and recovery engagements, working directly with executives, sponsors and governance forums across the Australian market.
INDEPENDENT PROJECT & PROGRAM HEALTH CHECKS
Concerned that the status report isn’t telling the whole story?
Independent perspective. Senior-level judgement. Evidence before opinion.
Carpadium provides independent Project and Program Health Checks for complex Australian organisations, helping executives understand the evidence behind reported status and determine whether intervention is required.