Free download β’ Use as a template β’ Print or share
A 5 Metrics To Track For Project Management template is a structured operational document that defines, measures, and reports the five core performance indicators β schedule performance, budget performance, scope adherence, quality rate, and resource utilization β that together give project managers and stakeholders a complete, data-backed picture of project health. Rather than relying on informal status updates or gut-feel assessments, this free Word download gives teams a repeatable framework with built-in formulas, baseline fields, variance calculations, and corrective-action sections that can be completed in under 20 minutes per reporting cycle and exported as PDF for distribution.
Projects fail most often not because teams lack effort, but because the warning signals β a schedule slipping by a few days each week, a utilization rate creeping above 90%, a defect rate doubling between sprints β go undetected until they become unrecoverable. Without a defined set of metrics and a consistent reporting format, each status update is a narrative shaped by whoever is presenting it rather than a factual comparison against an agreed baseline. Sponsors make resourcing decisions on incomplete information; teams waste time in status meetings debating whether performance is acceptable rather than acting on clear data. This template removes that ambiguity: it establishes what you measure, what the targets are, and what a red, yellow, or green status actually means β before the first reporting period begins. For project managers juggling multiple workstreams, it also creates an audit trail of period-by-period performance that feeds directly into closure reports, portfolio reviews, and retrospectives.
| If your situation is⦠| Use this template |
|---|---|
| Reporting project status to executive sponsors weekly | Project Status Report |
| Tracking a full project lifecycle from initiation to close | Project Plan |
| Managing a portfolio of simultaneous projects | Project Portfolio Dashboard |
| Capturing lessons learned and metric outcomes at project close | Project Closure Report |
| Tracking only budget and cost performance for finance reporting | Project Budget Template |
| Running agile sprints where velocity and burn-down are the core metrics | Sprint Planning Template |
| Assessing risks that could cause metric deviation | Risk Management Plan |
Why it matters: Adding eight or ten KPIs dilutes attention and makes it harder to identify the two or three signals that actually require action. Stakeholders disengage from reports that take more than five minutes to parse.
Fix: Commit to the five core metrics in this template for every project. Add one or two project-specific indicators only when the project type genuinely demands them β and remove them at close.
Why it matters: A CPI of 0.92 or a utilization rate of 78% is meaningless without a target to compare it to. Stakeholders cannot assess whether performance is acceptable or alarming.
Fix: Establish and document baseline targets for all five metrics before the first reporting period begins. Reference the approved project plan as the source.
Why it matters: A green light with no data behind it erodes trust over time. When a project that has been green for six weeks suddenly fails, stakeholders lose confidence in the entire reporting process.
Fix: Every status indicator must be backed by the formula or count that produced it, visible in the same report section. If the data is unavailable, the status is yellow β not green.
Why it matters: Projects that are on track today can fall off track by the next cycle. A brief forward-looking note on emerging risks β even when all metrics are green β keeps the team in a proactive stance.
Fix: Include a brief 'watch items' row in the corrective-action section every period, noting any metric trending toward yellow even if it has not crossed the threshold yet.
Why it matters: Quietly adjusting baseline values to eliminate variance is data manipulation. It destroys the historical record and makes it impossible to measure true project performance.
Fix: Any change to the approved baseline requires a documented change-control decision β sponsor sign-off, new baseline date, and a note explaining why the re-baseline was approved.
Why it matters: Tables of numbers without interpretation force every reader to do their own analysis. Stakeholders with competing priorities will skip the data and make uninformed decisions.
Fix: Open every metrics report with a three-sentence executive summary: overall project health, the single most important issue, and the action being taken. Keep it to the top of page one.
Fill in the project name, PM, reporting period, and the original approved baseline for schedule, budget, scope, quality, and utilization. These baseline numbers are the fixed reference point for every subsequent report.
π‘ Lock the baseline on the day the project is formally approved β changes after kickoff require a documented re-baseline decision, not a quiet edit.
Divide Earned Value by Planned Value to get SPI. Then count milestones completed on time versus total milestones due in the period. Both figures together give a fuller picture of schedule health than either alone.
π‘ If you do not have a formal EV system, use percentage of deliverables completed on time as a proxy SPI β it is less precise but far better than no measure at all.
Divide Earned Value by Actual Cost to get CPI. Then project total cost at completion using Budget at Completion divided by CPI to calculate Variance at Completion.
π‘ A CPI below 0.9 for two consecutive periods almost never self-corrects β flag it for sponsor review immediately rather than waiting for end-of-phase reporting.
Log all approved change requests by number and check for work being performed that has no change order. Count both, and calculate the percentage of original scope still intact.
π‘ A weekly scope-change audit β comparing the work log to the approved scope statement β catches unapproved additions before they compound.
Count deliverables reviewed in the period, how many passed on first review, and how many defects or rework items were logged. Calculate the first-pass acceptance rate as a percentage.
π‘ Set your quality threshold before the project starts β for example, a 90% first-pass acceptance rate. Without a defined threshold, teams debate whether the number is acceptable every single reporting cycle.
Divide total hours logged to the project by total available team hours for the period. Flag anyone consistently above 85% or below 60% for workload rebalancing.
π‘ Distinguish between logged hours on project tasks and total hours worked β overtime padding the denominator can mask genuine over-allocation.
For every metric showing yellow or red, write one specific action, assign it to a named team member, and set a resolution date no more than one reporting cycle out.
π‘ If the same corrective action appears for three consecutive periods, escalate to the project sponsor β it signals a structural constraint the team cannot resolve independently.
Enter the target value for each metric in the next reporting cycle, adjusting for any re-baselines. Export as PDF and distribute to stakeholders before the next status meeting.
π‘ Send the report at least 24 hours before the status meeting so stakeholders arrive with questions rather than spending meeting time reading the data.
The five most universally applicable project management metrics are schedule performance (SPI), budget performance (CPI), scope adherence, quality rate, and resource utilization. Together they cover time, cost, scope, quality, and people β the five dimensions where projects most commonly fail. Tracking all five gives a complete health picture; tracking fewer creates blind spots that surface as surprises late in the project.
Weekly reporting is standard for active projects with a duration of 4β26 weeks. For longer programs or lower-risk phases, bi-weekly reporting is acceptable. Milestone-based reporting β updating the metrics at each defined checkpoint rather than on a calendar cadence β works well for projects with highly variable sprint lengths. The key is consistency: irregular reporting makes trend analysis unreliable.
Schedule Performance Index (SPI) equals Earned Value divided by Planned Value. Earned Value is the budgeted cost of work actually completed; Planned Value is the budgeted cost of work that should have been completed by now. An SPI of 1.0 means you are exactly on schedule; above 1.0 means ahead; below 1.0 means behind. An SPI of 0.85, for example, means you have completed 85 cents of work for every dollar of work that was planned.
A target range of 65β85% is widely used in project management practice. Below 65% typically indicates under-assignment or poorly defined tasks. Above 85% leaves no buffer for unplanned work, quality checks, or coordination overhead, and consistently high utilization is a leading indicator of missed deadlines and quality issues. The ideal number varies slightly by industry and role type, but staying within this range is the most reliable way to sustain throughput without burning out the team.
A project status report is a narrative update β it describes what happened, what is planned, and any issues, often with a high-level RAG (red/amber/green) indicator. This metrics template is the data layer underneath that narrative: it provides the specific formulas, baselines, actuals, and variance calculations that give the status report its factual basis. Used together, the metrics template feeds the status report; used alone, it serves as a standalone performance dashboard.
Yes, with minor adaptation. Replace SPI with sprint velocity and milestone completion rate, replace VAC with remaining budget versus remaining backlog cost, and track story-point acceptance rate instead of deliverable first-pass rate. The resource utilization and scope sections apply directly to agile contexts without change. The five-metric structure is flexible enough to accommodate waterfall, agile, and hybrid delivery models.
A red metric requires three immediate steps: identify the specific root cause (not a vague description like 'team bandwidth'), assign a named corrective action with an owner and a resolution date, and notify the project sponsor in the same reporting cycle β not the next one. A red metric that is acknowledged, root-caused, and actioned is manageable; a red metric that is quietly monitored for several cycles becomes a project failure.
Research on team cognitive load suggests that more than seven KPIs per project leads to reduced engagement and slower response to warning signals. The five metrics in this template cover the most critical dimensions. If a specific project type requires additional indicators β for example, a customer satisfaction score for a client-facing deliverable β add no more than two and remove one of the standard five if it is genuinely not applicable to that project.
The baseline values and reporting cadence should be agreed with the project sponsor at kickoff β they define what 'on track' means and align expectations before the first report goes out. The metric definitions themselves do not require approval for internal use. For client-facing projects, confirm which metrics and thresholds will be included in external reporting before the first delivery, since clients sometimes have contractual KPI requirements that must be reflected.
A project status report is a narrative stakeholder update that describes progress, risks, and next steps in prose. This metrics template is the structured data layer β formulas, baselines, actuals, and variances β that substantiates the status report's conclusions. Use both together: the metrics template populates the data; the status report communicates it.
A project plan defines scope, tasks, dependencies, timeline, and resource assignments before execution begins. This metrics template measures actual performance against that plan during execution. The project plan sets the baseline; the metrics template tracks whether you are hitting it.
A risk management plan identifies and prioritizes threats that could affect project outcomes. This metrics template surfaces actual deviations as they occur. Risk plans are forward-looking and probabilistic; metrics tracking is backward-looking and factual. Red metrics often signal that a previously identified risk has materialized.
A project closure report documents final outcomes, lessons learned, and a post-mortem comparison of planned versus actual performance. This metrics template is the source data for that closure report β accumulated period-by-period records of the five core KPIs become the evidence base for the lessons learned and performance narrative.
Sprint velocity, defect escape rate, and deployment frequency supplement the core five metrics to reflect agile development cycles.
Schedule and budget metrics map directly to earned value tracking on phased builds, with resource utilization covering subcontractor hour management.
Utilization rate and scope adherence are the most commercially critical metrics for billable engagements where time overruns directly erode margin.
Quality rate and compliance milestones carry elevated weight in healthcare IT and clinical program projects due to regulatory submission deadlines.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Project managers and team leads running single or small numbers of projects without a dedicated PMO | Free | 30β60 minutes to set up per project; 15β20 minutes per reporting cycle |
| Template + professional review | PMO directors standardizing metrics across a portfolio or integrating reporting into an existing governance framework | $500β$2,000 for a PMO consultant to configure and train | 1β2 weeks |
| Custom drafted | Enterprises requiring metrics integration with project management software (Jira, MS Project, Smartsheet) or automated executive dashboards | $5,000β$20,000+ for tool configuration and dashboard development | 4β12 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Free Forever PlanΒ Β·Β No credit card required
