Project progress reports often use the traffic light rating system or RAG status definition as a visual cue to project performance.
However, the effectiveness of this project tracking tool is wholly dependent on the integrity of the project manager and the accuracy of the assigned RAG status.
An inappropriate RAG rating can lead to issue avoidance and ultimately project failure. Its purpose is to show progress and make it clear when the project manager needs the board’s intervention.
Therefore, it makes much sense to understand the meaning behind the traffic light system and the ratings for red, amber, and green.
Understanding RAG Status Ratings
Therefore, the traffic light system should not be used to hide problems. Rather, the RAG rating is a way of tracking project progress and seeking support and guidance from sponsor and senior stakeholders.
Always use a common RAG status ratings to communicate project performance to your stakeholders.
RAG status ratings
|Traffic Light||RAG Status||Action|
|Red||There are significant issues with
The project requires corrective action to meet business objectives.
The issue cannot be handled solely by the project manager or project team.
One or more aspects of project viability—time, cost, scope—exceed tolerances set by the project board.
|The matter should be escalated to the project sponsor and project board immediately.|
|Amber||A problem has a negative effect
on project performance, but can
be dealt with by the project
manager or project delivery team.
We act to resolve the problem or a decision made to watch the situation.
One or more aspect of project viability—time, cost, scope—is at risk. However, the deviation from plan is within tolerances assigned to the project manager.
|The project board should be notified using a progress report or scheduled briefing with the sponsor.|
|Green||The project is performing to plan. All aspects of project viability are within tolerance. However, the project may be late or forecast to overspend.||No action needed.|
How to use a RAG status report
Use the RAG status wisely and report only on a few areas of project performance. For example, overall project progress, project schedule performance, project budget, and scope.
Because the inclusion of too much detail in a RAG status report results in the project manager and project sponsor failing to see and deal with important issues. Quite simply, you can’t see the wood for the trees.
Moreover, always report on progress trend. Compare the current project status with an earlier period. For instance, show the RAG status for this week and the previous week.
Do you use RAG status in your status reports? What would you do different? You are welcome to share your ideas in the comments.