Project Health Checker

Enter your project KPIs and metrics to instantly calculate a health score, identify risks, and get actionable recommendations. Built for agile teams and project managers.

Health Score 0–100 Risk Assessment Schedule & Budget Sprint Velocity RAG Status Free · No Login
%
% of total tasks completed so far
%
% of total project duration consumed
%
% of total budget consumed
%
% of budget still available
Number of unresolved risks
Number of high-severity risks
Active blockers or unresolved issues
%
% of tasks past their due date
Story points completed last sprint
Story points originally planned

What This Tool Measures

Schedule Health

Compares task completion % against timeline % to calculate Schedule Performance Index (SPI). Behind schedule = lower score.

Budget Health

Analyzes budget burn rate vs progress. Spending more than earned value indicates cost overrun risk.

Risk Exposure

Weighs open risks and critical risks against project size. High critical risk count triggers immediate alerts.

Issue & Blocker Impact

Overdue tasks and open blockers directly reduce the health score — unresolved issues compound over time.

Sprint Velocity

Compares actual vs planned velocity to detect team performance trends. Below 80% velocity is a warning signal.

Composite Health Score

Combines all metrics into a single 0–100 score with RAG status: Healthy, Caution, At Risk, or Critical.

Project Health Metrics Explained

Schedule Performance Index (SPI)

SPI = Tasks Completed % ÷ Timeline Elapsed %. An SPI of 1.0 means perfectly on schedule. SPI below 0.8 means the project is significantly behind and needs corrective action. SPI above 1.0 means ahead of schedule.

Cost Performance Index (CPI)

CPI = Tasks Completed % ÷ Budget Spent %. A CPI below 1.0 means you're spending more than the value being delivered. CPI below 0.8 is a strong indicator of budget overrun without intervention.

RAG Status

Red/Amber/Green (RAG) is the standard project reporting framework. Green (Healthy 80–100): on track. Amber/Yellow (Caution 60–79): risks present, monitoring needed. Orange (At Risk 40–59): intervention required. Red (Critical 0–39): immediate escalation needed.

Frequently Asked Questions

What makes a project unhealthy?

Common causes of poor project health include scope creep without timeline adjustment, underestimated task complexity, team members blocked by dependencies, budget overrun due to rework, inadequate risk management, poor stakeholder communication causing late requirement changes, and technical debt accumulating faster than it's resolved.

How often should I check project health?

Most project management frameworks recommend weekly health checks for active projects and sprint-by-sprint checks for agile teams. At minimum, check before every status report, steering committee meeting, or milestone review. Early detection of declining health metrics allows corrective action before issues become crises.

What is the difference between project health and project status?

Project status is a point-in-time snapshot of where the project is (e.g., "we completed 40% of tasks"). Project health is a trend-based assessment of whether the project is heading toward success or failure based on performance indicators. A project can be 40% complete (status) but critically unhealthy (health) if it has consumed 70% of its budget.