Key takeaways
- The Question: Which KPIs should a construction project track, how is each one calculated, and how do you collect the data so nobody argues with the result?
- The Answer: Use a short set covering schedule, cost, quality, safety, productivity and commercial control, mix leading indicators with lagging ones, define every formula before the project starts, and feed the numbers from records rather than opinions. Then improve them in small, repeated steps instead of chasing one big fix.
- The YelloSKYE Angle: Construct IQ supplies the physical-progress half of most KPIs: dated drone, 360° and fixed-camera captures on the DEX platform, compared with the planned schedule, so installed quantities and completion dates come from evidence.
Construction KPIs (key performance indicators) are a small number of measured values that tell a project team whether the job is on track for time, cost, quality and safety, early enough to act. A useful set has a clear formula for each KPI, a named owner, a fixed review rhythm and a data source that does not rely on someone's impression of the site. Most of the numbers depend on knowing how much work is physically in place, which is why we treat site capture through Construct IQ as part of the KPI system rather than a separate reporting exercise.
This guide gives a working KPI set with formulas, explains which are leading and which are lagging, and covers how to collect and review them. For the arithmetic behind cost and schedule indices in depth, see our guide to earned value management.
What makes a KPI worth tracking
Plenty of numbers can be produced on a construction project. Few of them change what anyone does on Monday morning. Before adding a KPI to the dashboard, test it against five questions:
- Does it drive a decision? If the value moves, someone should know what to do differently: add a crew, release a work area, escalate a design query.
- Is the formula written down? "Progress" or "quality" means nothing until the numerator, denominator and period are defined.
- Can the data be collected without opinion? A KPI built on estimates turns into a negotiation.
- Does it have one owner? Shared ownership usually means no one chases it.
- Is it reviewed at a set rhythm? A weekly KPI looked at monthly is a history lesson.
A KPI that fails two or more of these questions is usually reporting noise. It costs time to produce and teaches the team to ignore the dashboard.
A core KPI set with formulas
The table below is a starting set that suits most building and infrastructure projects. Adjust the names to your contract and reporting system, but keep the definitions fixed for the life of the project so that trends mean something.
| Area | KPI | Formula | Leading or lagging | Typical data source |
|---|---|---|---|---|
| Schedule | Schedule performance index (SPI) | Earned value ÷ planned value | Lagging | Cost-loaded programme and measured progress |
| Schedule | Milestone hit rate | Milestones achieved by baseline date ÷ milestones due in period × 100 | Lagging | Programme and dated site records |
| Schedule | Percent plan complete (PPC) | Tasks completed as committed ÷ tasks committed for the week × 100 | Leading | Weekly work plan |
| Schedule | Make-ready rate | Constraints cleared before task start ÷ constraints logged × 100 | Leading | Lookahead constraint log |
| Cost | Cost performance index (CPI) | Earned value ÷ actual cost | Lagging | Cost ledger and measured progress |
| Cost | Contingency burn ratio | Share of contingency used ÷ share of work complete | Leading | Cost report and progress |
| Quality | First-time inspection pass rate | Inspections passed at first attempt ÷ inspections held × 100 | Leading | Inspection and test records |
| Quality | Defect age | Average days from defect raised to defect closed | Leading | Snag or defect log |
| Quality | Rework cost ratio | Cost of rework ÷ construction cost to date × 100 | Lagging | Cost codes for rework |
| Safety | Injury frequency rate | Recordable or lost-time injuries × base hours ÷ hours worked | Lagging | Incident register and hours |
| Safety | Hazard close-out rate | Hazards closed within target time ÷ hazards raised × 100 | Leading | Safety observation log |
| Productivity | Output per labour hour | Quantity installed ÷ labour hours booked to it | Lagging | Measured quantities and timesheets |
| Productivity | Performance factor | Budgeted hours for work done ÷ actual hours spent | Lagging | Estimate, quantities and timesheets |
| Commercial | Change approval time | Average days from change request to signed instruction | Leading | Change register |
| Commercial | Payment certification time | Average days from progress payment claim to certificate | Lagging | Payment records |
| Commercial | Cash flow variance | Actual net cash ÷ forecast net cash for the period | Lagging | Finance system |
The base hours in the injury frequency rate differ by country and by company. Some use 200,000 hours, roughly 100 full-time workers for a year, while others use one million hours. Use whichever base your client and regulator expect, state it on the report, and never compare rates calculated on different bases.
Schedule KPIs
SPI says whether the value of work done is keeping pace with the plan, but late in a project it drifts back towards 1.0 even when the job is late, so pair it with milestone dates. PPC and the make-ready rate look forward: if fewer constraints are being cleared this week, next fortnight's progress is already at risk. Our lean construction guide explains how PPC sits inside weekly planning.
Cost KPIs
CPI tells you how much value each unit of spending buys. The contingency burn ratio is a simpler early signal for owners and directors: if half the contingency is gone when a third of the work is in place, the remaining risk is underfunded.
Quality KPIs
First-time pass rate and defect age move before rework cost does. A falling pass rate on one trade usually points to a method, supervision or information problem that will show up as cost a month later. Studies by the Construction Industry Institute have put direct field rework at around 5 per cent of construction cost, so even a modest improvement is worth measuring.
Safety KPIs
Injury rates are essential but slow, because serious incidents are, thankfully, rare on any single project. Leading safety KPIs, such as how quickly reported hazards are closed, give the team something to act on between incidents. Our guide to construction safety monitoring covers how imagery helps with the conditions behind those numbers.
Productivity KPIs
Output per labour hour only means something within one activity on one kind of work. Comparing square metres of partitioning with cubic metres of concrete is meaningless, and comparing the same activity across two very different buildings needs care. The performance factor gets round this by expressing every activity against its own budget.
Commercial KPIs
Slow change approvals and slow payment certification damage relationships with subcontractors and often lead to slower work on site. They are also among the easiest KPIs to improve, because the delay is usually in an office, not on the site.
Leading and lagging indicators
Most dashboards are dominated by lagging KPIs because the data is already collected for other reasons: cost, injuries, completed milestones. They are necessary for reporting and accountability but arrive too late to change the period they describe.
Leading KPIs measure the conditions that produce those results. A practical habit is to pair each lagging KPI with at least one leading one:
- Late milestones pair with make-ready rate and PPC.
- Cost overrun pairs with contingency burn ratio and change approval time.
- Rework cost pairs with first-time pass rate and defect age.
- Injuries pair with hazard close-out rate.
When the leading KPI moves the wrong way, the team has a week or two to respond before the lagging one confirms the damage.
Collecting KPI data objectively
The weakest input to most construction KPIs is physical progress. Cost comes from the ledger and hours from timesheets, but "how much is installed" is still often a supervisor's estimate entered into a spreadsheet. Every KPI that uses earned value, installed quantity or completion date inherits that estimate. Our guide to percent complete explains why those reported figures drift from the site.
Three habits make the data harder to dispute:
- Define "complete" in a way a camera can confirm. "Ceiling boarded and taped" is checkable; "ceiling 80 per cent" is not.
- Capture on a fixed rhythm, aligned with the reporting period, so every KPI value has dated evidence behind it.
- Measure where the work is measurable. Earthworks, slabs and facades can be quantified from aerial or scanned data; interior trades can be checked room by room from 360° walks.
This is where Construct IQ fits. Drone flights, 360° walks and fixed cameras sit on one timeline in DEX, which overlays what was built on the 4D programme, so the progress used in SPI, CPI and milestone KPIs comes from a record every party can open. On our aerial progress capture project, a weekly flight routine gave the site management team back over 15 hours each week that had gone on compiling reports by hand, and stakeholder meetings fell from two hours to 30 minutes. For owners comparing several sites, the portfolio monitoring use case shows how a common capture standard lets leadership review more than ten sites in about 30 minutes.
Reviewing KPIs at the right level
Different people need different KPIs at different speeds. A single dashboard for everyone tends to suit no one.
| Who | Rhythm | KPIs they act on |
|---|---|---|
| Trade foremen and supervisors | Daily and weekly | PPC, make-ready rate, output per labour hour, hazards open |
| Project manager | Weekly | SPI, milestone hit rate, first-time pass rate, defect age, change approval time |
| Commercial manager | Monthly | CPI, contingency burn ratio, payment certification time, cash flow variance |
| Directors and owners | Monthly or quarterly | Milestone hit rate, CPI, injury frequency rate, trend across projects |
Keep the review short and fixed. Look at the trend, not one week's value, and end each review with an action and an owner for any KPI that moved outside its agreed range.
Improving through small gains
The value of KPIs comes from what the team changes because of them. Large restructures are rare on a live project; small, repeated adjustments are not. A simple improvement loop works well:
- Pick one KPI that is drifting, for example first-time pass rate on mechanical first fix.
- Look at the reasons, not just the number. Group failed inspections by cause: missing information, wrong material, poor access, workmanship.
- Change one thing about the most common cause, such as a pre-start check of the latest drawings.
- Measure again over the next two or three periods before deciding whether it worked.
- Keep what works and move on to the next cause or the next KPI.
Each change may move the KPI only a little. Over a project with hundreds of repeated tasks, those small gains add up, and they carry into the next project as standard practice.
Mistakes that make KPIs useless
- Too many KPIs. Thirty metrics on a slide means none of them gets discussed.
- Targets used as punishment. When missing a target brings blame, people learn to report numbers that look good. PPC is especially easy to inflate by committing only to safe tasks.
- Averages that hide the spread. A project-wide pass rate of 90 per cent can hide one trade at 60 per cent.
- Changing definitions mid-project. A new formula resets the trend and invites suspicion.
- Estimated inputs. A KPI is only as reliable as its least reliable input, which is usually physical progress.
Getting started: a KPI checklist
- Choose one or two KPIs in each of the six areas, no more than twelve in total.
- Write the formula, data source, owner and review rhythm for each one.
- Pair every lagging KPI with a leading one.
- Agree definitions of complete for the main activities so progress can be verified.
- Set up a capture routine aligned with the reporting period, so physical progress has dated evidence.
- Hold short, fixed reviews and end each with actions and owners.
- After a month, drop any KPI that has not led to a decision, and add one that the team wished it had.
