One of the biggest risks in project management is not always an obvious problem.
Sometimes, it is a project that looks healthy on paper.
The status report is green. Milestones appear to be on schedule. Meetings are happening. Action items are being closed. Leadership sees progress.
But beneath the surface, the project may be carrying unresolved decisions, incomplete testing, unclear ownership, limited stakeholder engagement, or growing resource constraints.
In other words, a project can be green today and still be heading toward red.
Green Should Mean More Than “Nothing Has Failed Yet”
Traditional project reporting typically focuses on:
- Schedule
- Budget
- Scope
- Risks and issues
- Milestone completion
These measures are important, but they often tell us where the project stands today, not where it is heading.
For example:
- A project may be on schedule even though several critical activities are slipping behind the scenes.
- A testing milestone may be marked complete even though major process gaps remain unresolved.
- A project may be within budget while pending scope decisions create future cost exposure.
If reporting focuses only on what has already happened, leadership may not recognize the risk until the impact becomes unavoidable.
A strong status report should answer two questions:
- Where is the project today?
- Where is the project heading?
Activity Is Not the Same as Progress
Projects can be extremely busy without becoming more ready for delivery.
Teams may attend workshops, complete hundreds of tasks, update trackers, and participate in weekly meetings. But activity alone does not prove progress.
Consider the difference:
- A completed workshop is activity. An agreed business process is progress.
- A completed testing session is activity. A validated end-to-end process is progress.
- A closed action item is activity. A resolved project risk is progress.
- A milestone date reached is activity. Confirmed business readiness is progress.
Project Managers need to report outcomes, not simply completed events.
The question should not only be, “Did the milestone happen?”
It should also be, “Did the milestone make the project more ready for success?”
Warning Signs That RAG Status May Miss
Some of the strongest warning signs are difficult to represent with a simple Red-Amber-Green indicator.
Repeatedly Delayed Decisions
One unresolved decision may not immediately affect the timeline. Several unresolved decisions can eventually block configuration, testing, training, or deployment.
Unclear Ownership
If the team repeatedly asks who owns a process, action, or decision, that ambiguity will likely create delays later.
Testing That Is Still Discovering Requirements
Testing should increasingly validate the solution. If the team is still defining basic requirements or deciding how the business should operate, the project may be less mature than the schedule suggests.
Limited Stakeholder Availability
The project plan may assume business resources are available for testing, decision-making, and validation. If those stakeholders are regularly unavailable, the status may remain green until the missed work catches up with the schedule.
A Growing Number of Open Issues
Individual issues may not appear critical. However, a consistent increase in open issues can reveal a negative trend that deserves attention.
Dependencies Without Resolution Dates
A dependency may not have caused a delay yet, but that does not mean the risk is low. Dependencies without clear owners and resolution dates can quickly become schedule blockers.
These warning signs may not justify changing a project immediately to red. However, they should affect how confidently the project is reported as green.
A Status Report Should Show Trajectory, Not Just Position
A more effective status report shows both the project’s current position and its trajectory.
For example:
- Green, trending Amber: The schedule remains achievable, but testing is identifying more gaps than expected.
- Amber, trending Green: Major issues have clear owners, agreed resolution dates, and active executive support.
- Amber, stable: Risks remain, but they are understood and being managed without further deterioration.
These situations require very different leadership responses, even when the current RAG status is the same.
Adding trajectory helps answer an important question:
Is the project becoming healthier or less healthy?
That may be more valuable than the colour itself.
Readiness Should Influence Status
Schedule alone should not determine whether a project is green.
Before a major milestone such as testing, deployment, or go-live, Project Managers should establish clear readiness criteria.
Ask:
- Are critical business processes defined?
- Are high-priority gaps resolved or formally accepted?
- Have integrations been validated?
- Are data and reporting requirements ready?
- Are business owners prepared to provide sign-off?
- Is training sufficiently complete?
- Are operational teams ready to support the new processes?
A project may technically reach its milestone date while failing several of these criteria.
In that situation, reporting the project as fully green can create false confidence. A more useful message would be:
“The target date remains achievable, but our readiness confidence is declining.”
That gives leadership time to act before the milestone is officially missed.
Green Does Not Mean Risk-Free
Complex projects will almost always have risks and issues.
Green should not mean:
“There are no problems.”
It should mean:
“The project remains achievable, and the current risks have credible mitigation plans, clear ownership, and enough time to respond.”
This definition allows project teams to raise concerns early without creating the impression that the project is failing.
In fact, a project reporting no meaningful risks may deserve more scrutiny than one that identifies them openly and manages them well.
Project Managers Must Be Willing to Challenge the Colour
Project Managers are often under subtle pressure to maintain a positive status.
Nobody wants to be the person who changes a project from green to amber, especially when the schedule has not technically slipped.
But the purpose of project reporting is not to make everyone comfortable. It is to help leadership make informed decisions while there is still time to act.
An experienced PM should be able to explain:
- Here is what the dashboard shows.
- Here is what I am seeing behind the dashboard.
- Here is what may happen if we do not respond.
- Here is the decision or support the project needs.
That context is where project management becomes more than reporting.
The Best Status Reports Create Action
A good status report should not simply describe the project. It should make the project easier to manage.
Leadership should be able to quickly understand:
- Where the project stands
- Where it is heading
- What could change its direction
- Which decisions are required
- What support the team needs
- Whether the next milestone is genuinely achievable
If a project remains green until the moment a deadline is missed, the reporting process has not done its job.
The strongest Project Managers identify warning signs while there is still time to respond.