Projects rarely fail overnight. They fail because deviations go unnoticed for too long — until the damage is no longer containable. The Overall Status is the early-warning system that prevents exactly that: it compresses two critical performance indicators into a single, instantly readable signal. Green, Yellow, or Red. No spreadsheet diving, no manual calculations — just act.
What Is the Overall Status?
The Overall Status is the traffic light of your project dashboard. It answers two critical questions simultaneously, at a glance: Is the project within budget? And is it on schedule? The result appears as a color signal — and behind it is not the subjective assessment of a project manager, but an objective calculation based on two proven metrics from project controlling.
The two metrics are called CPI (Cost Performance Index) and SPI (Schedule Performance Index). Both come from Earned Value Management, an internationally recognized standard for project controlling. The Overall Status combines them into one clear statement.
How Is the Overall Status Calculated?
The traffic light is based on two threshold values:
Green — CPI ≥ 0.9 AND SPI ≥ 0.9: The project is on track. Budget and schedule are under control. No immediate action is required.
Yellow — CPI ≥ 0.8 AND SPI ≥ 0.8 (but not both ≥ 0.9): Minor deviations are visible. The project is still within an acceptable range, but corrective monitoring is recommended.
Red — CPI < 0.8 OR SPI < 0.8: Significant deviation. Immediate action is required.
What do CPI and SPI mean in concrete terms? The CPI (Cost Performance Index) measures hour efficiency: a CPI of 0.95 means that 1.05 hours are consumed for every planned hour — the project is running slightly over its hour budget. The SPI (Schedule Performance Index) measures work pace: an SPI of 1.22 means the project is progressing 22% faster than planned.
Real-World Example from the Dashboard
A concrete example: in a running project, the dashboard shows the following values:
- CPI = 0.95 — is ≥ 0.9, condition met
- SPI = 1.22 — is ≥ 0.9, condition met
- Both Green conditions are met
Result: Overall Status = Green.
The project is consuming slightly more hours than planned (CPI = 0.95 signals a minor overrun), but it is generating substantially more work progress than was planned for this point in time (SPI = 1.22). Bottom line: a solidly managed project in the green zone.
What Does This Mean in Practice?
The interpretation logic is deliberately kept simple so that all stakeholders — from the project manager to the executive team — can work with it without training.
A green status does not mean there are zero problems. It means deviations are within the normal range of variation and the project has not violated its defined tolerance boundaries. Professional project management accepts that no project runs exactly to plan.
A yellow status is not an alarm — it is a signal for heightened attention. It gives the project manager the chance to intervene early, before a minor deviation becomes a real problem.
A red status requires immediate action. Anyone who waits for red before reacting has already lost valuable time. The traffic light system is therefore most powerful in the early phase: when yellow is still yellow and not yet red.
Three Perspectives on the Overall Status
Project Manager: The Operational Control Level
For the project manager, the Overall Status is the daily starting point in the dashboard. Instead of opening five different reports, one glance at the traffic light signal is enough to know whether steering is needed today. A yellow or red status triggers the workflow: which tasks are driving CPI or SPI downward? Which team member is blocked? What needs to be decided today?
C-Level: The Strategic View
For management and portfolio oversight, the Overall Status solves a classic problem: too many projects, too little time for detailed reporting. The status enables portfolio overview in seconds. Which projects are green? Which are showing yellow or red signals? This gives leadership the ability to focus resources and attention where they are truly needed — not where everything is already running smoothly.
Team Lead: Transparency at Team Level
For the team lead, the Overall Status is also a leadership instrument. A consistently green status signals to the team that their work is having an impact and that the set goals are being met. A yellow status can be communicated transparently without triggering panic — and it creates a shared basis for solution discussions rather than blame.
Typical Errors and Pitfalls
Error 1: Looking at the status in isolation. The Overall Status is a starting point, not the complete analysis. Anyone who sees yellow or red must trace the cause in the task list, hour logs, and resource deployment.
Error 2: Focusing only on CPI and ignoring SPI. A project can be within budget and still be massively behind schedule. Both indices together give the complete picture.
Error 3: Treating the thresholds as absolute truth. A CPI of 0.89 is not automatically a catastrophe. The numbers are reference points for conversations, not a replacement for them. Context determines what actions make sense.
Error 4: Relying on manual status reports. “The project is going well” is not a valid controlling instrument. The Overall Status in zistemo is based on actual time-tracking data, not subjective opinions.
How zistemo Delivers the Overall Status
zistemo calculates the Overall Status fully automatically — based on actually recorded project hours, without any manual input from the project manager.
The live dashboard updates CPI and SPI in real time as soon as a team member logs hours. There is no delay, no month-end close to wait for. Opening the dashboard in the morning shows the current status — based on the previous day’s bookings.
The Project Cockpit displays all running projects with their traffic light status at a glance. Portfolio monitoring in one view: red-flagged projects are immediately visible, green ones provide reassurance. The Team Monitor adds the resource-level perspective: who is working on what right now, and where are the hour deviations?
Time tracking in zistemo — via timer, manual entry, mobile, and desktop — ensures that the data foundation for CPI and SPI is reliable. zistemo automatically separates project hours from vacation and sick leave entries, because only actual project work feeds into CPI and SPI. This clean separation eliminates one of the most common sources of error in manual controlling.
zistemo USPs: Why This Is More Than a Colored Light
All-in-one instead of tool chaos: The Overall Status in zistemo is not an isolated reporting feature that must pull data from five different systems. Time tracking, budget management, and controlling operate in a single platform. That means no data loss during exports, no manual transfer errors, and no outdated Excel files that are already wrong the next day.
Real-time data instead of spreadsheet graveyards: In many organizations, project status is reported once a week or once a month — by which point it is already out of date. zistemo updates the Overall Status with every new time entry. That is the difference between an early-warning system and a post-mortem report.
Out-of-the-box Earned Value: CPI and SPI are core concepts of the PMI standard. In many tools, they must be painstakingly configured, calculated manually, or added via plugins. In zistemo, they are available from day one — no setup, no developer effort required.
Related KPIs
- Progress (Earned Value) — the source of CPI and SPI
- Budget Usage (Hours) — the input side for hour efficiency
Conclusion
The Overall Status is one of the simplest and simultaneously most effective metrics in project controlling. It compresses the complexity of a running project into a signal that everyone understands and can act on immediately. A CPI of 0.95 and an SPI of 1.22 mean Green — the project is solidly positioned, even if it is marginally over budget at individual points. The traffic light signal creates confidence and provides the foundation for fact-based conversations between the PM, team, and leadership.
zistemo delivers this signal automatically, in real time, and without additional effort from the team.
Start Your Free zistemo Trial
Get started today with automatic project controlling and the Overall Status dashboard. No spreadsheets, no manual reporting — just clear signals.
FAQ
Can I adjust the thresholds for Green, Yellow, and Red?
The default thresholds (≥ 0.9 for Green, ≥ 0.8 for Yellow) correspond to the PMI standard and are appropriate for most projects. For industry-specific or company-specific requirements, zistemo enables you to define custom evaluation logic via Custom SQL Reports — without any developer effort.
What happens if the team forgets to log hours?
The Overall Status is only as good as the underlying data. Missing time entries distort CPI and SPI. zistemo therefore supports approval workflows for weekly reports: employees submit their hour reports, managers approve them — creating completeness and accountability.
Does the Overall Status also show future risks?
The Overall Status itself reflects the current state. For forward-looking statements — meaning: how will the project develop until completion? — the metrics A.5 (EAC Hours) and A.6 (EAC Cost) provide the forecast values, also automatically calculated in zistemo.
