RAG Status in Project Management: The Dashboard Everyone Uses, But Few Use Correctly

One of the most common questions executives ask during project reviews is:

"Is the project Green?"

It sounds simple. But behind that single color is often a very complicated reality. Many projects fail not because the team didn't know there was a problem, but because the dashboard stayed Green for too long.

What is RAG Status?

RAG stands for:

🟢Green– The project is on track. Objectives, schedule, budget, scope, and quality remain within agreed tolerances.

🟠Amber (Yellow)– Risks or issues exist that require attention. The project is still recoverable, but we need to take action.

🔴Red– The project cannot achieve its objectives without major intervention, executive decisions, or significant replanning.

The purpose of RAG is not to describe the past. Its purpose is to predict the future.

The Biggest Mistake

Many organizations treat RAG as a performance score. Project managers often hesitate to report Amber or Red because they worry it will appear they are failing.

The result?

Projects remain Green until they suddenly become Red. That's not effective reporting. That's delayed reporting. A healthy project culture encourages early Amber status because it gives leadership time to help.

Green Doesn't Mean "Everything Is Perfect"

A Green project can still have:

• Small risks
• Minor defects
• Resource challenges
• Open issues
• Scope discussions

Green simply means: The team has the situation under control, and current issues are not expected to impact delivery. No project is risk-free.

When Is Red Appropriate?

Red should be used when the project cannot realistically recover without major decisions.

Examples:

• Critical milestone missed
• Budget significantly exceeded
• Regulatory deadline impossible to meet
• Vendor failure blocking delivery
• Major scope changes approved without additional time or budget
• Executive intervention required

Red is not an admission of failure. It is a request for leadership support.

Typical Distribution in a Healthy Portfolio

A mature project portfolio rarely has every project marked Green. Seeing a mix of Green, Amber, and occasional Red often indicates that teams are reporting honestly rather than hiding risks.

A Better Way to Think About RAG

Instead of asking "Why is your project Amber?", ask "What support do you need to get it back to Green?".That single change transforms RAG from a reporting tool into a decision-making tool. When project managers feel safe reporting risks early, organizations gain more time to solve problems and far fewer unpleasant surprises.

The best project managers aren't the ones who keep every project Green. They're the ones who know when to change the color. A Green status builds confidence. An Amber status creates action. A Red status protects the project from failing silently. The real goal isn't having more Green projects. It's making sure every color tells the truth.