How Does a Daily Feedback Loop Improve Construction Performance? The Live Loop
Ask two questions of every planned task, every day: did it happen, and if not, why not? Rank the reasons, fix the biggest one within 60 days, then move to the next. In a 12-month rollout for a national contractor, Percent Plan Complete (PPC), the share of planned tasks done as planned, rose from the high 50s to the high 70s: about 20 points.
Last reviewed: November 2026
Most construction businesses learn too slowly to matter. Problems are reviewed monthly, in a meeting, from a report written by someone who wasn’t there. By the time the cause is understood, the job has moved on and the same failure is happening on the next one.
The Live Loop is the opposite: a short, daily cycle that finds the biggest cause of late work, fixes it, and moves on to the next.
What is a continuous feedback loop in construction?
A continuous feedback loop captures what actually happened to each day’s planned work, while it’s still fresh. Unlike traditional reporting, it asks two questions of every task:
- Did the task happen?
- If not, why not?
That’s it. The power isn’t in the questions. It’s in asking them every day, on every site, and doing something visible with the answers.
How is it different from monthly reporting?
Monthly reporting tells you what went wrong. A daily loop tells you why, while you can still act.
| Monthly reporting | The Live Loop | |
|---|---|---|
| When | Weeks after the event | The same day |
| What it records | Progress against programme | Every missed task and its reason |
| Who sees it | The board, in a summary | Site, operations and board, from the same data |
| What happens next | A discussion | The biggest cause is fixed within 60 days |
How does the Live Loop work, step by step?
I call it whack-a-mole, because there is always a next cause. In practice it runs in four steps:
- Capture at scale. Roll out one simple way to record the two answers, on every site at once. Daily data from many sites replaces gut feeling and the loudest anecdote.
- Find the biggest cause. Within weeks, one reason for late tasks stands clearly ahead of the rest. That’s the one you fix first.
- Fix it within 60 days. Not a long study. Design a targeted solution with the people affected and put it in place inside two months.
- Move to the next. Once the top cause is dealt with, the second becomes the first. Repeat every cycle.
The Live Loop
Reasons for late tasks, ranked
Once the top cause is dealt with, the second becomes the first.
The Live Loop: capture, cause, rank, fix, repeat. The top cause is fixed first while the next one waits. Bar lengths are illustrative, not data.
The data is captured once, at source, by the people doing the work, and never rewritten on its way to the board. The same record gives the site its daily list, operations its pattern across jobs, and the directors their view. One source, three views.
What results can you expect, and how fast?
In my experience, clear patterns appear within the first two to four weeks of data, and the first measurable gains come within the first 60-day cycle.
In a 12-month rollout for a national contractor, across up to 20 live projects, PPC rose from the high 50s to the high 70s, about 20 points. That is my own result, not published research. It came from fixing one cause at a time, not from any single breakthrough.
As the old saying goes, getting to the top is difficult; staying there is harder. What matters is targeting your biggest weakness, continuously. Forever.
Measure adoption before results. In the first weeks, the question isn’t whether completion has improved. It’s whether every site is recording honestly every day. The ability arrives long before the habit, and the results follow the habit.
How does it relate to the Last Planner System?
Closely, and it’s worth being clear about what’s borrowed and what’s new.
The Last Planner System, developed by Glenn Ballard and Greg Howell, measures Percent Plan Complete (PPC): the share of tasks planned for a week that were actually completed. It also records the reasons tasks weren’t completed, so they can be fixed. Ballard’s research set out to lift plan reliability above 70% PPC, the level earlier work had linked to productivity gains (Ballard, The Last Planner System of Production Control, PhD thesis, University of Birmingham, 2000). The Lean Construction Institute reports that, on average, only 54% of work planned for a given week is completed within the allotted schedule (as cited in Going for Gold, chapter 5), though it gives no study behind the figure. Published studies show a wide range: across 119 projects in Brazil, the median PPC was 76% (Formoso and Moura, IGLC-17, 2009).
In my experience, reliable sites run in the 80s, not the 50s.
The Live Loop uses the same core idea, reasons for non-completion, and adds three things:
- daily, not weekly, so the reason is recorded while people remember it;
- across every site at once, so the biggest cause is found from the whole business, not one job;
- one fix at a time, on a 60-day clock, so improvement is a rhythm, not an initiative.
It sits alongside the planning method we teach, the Live Programme Method: the programme says what should happen, and the Live Loop learns from what didn’t.
Why is 100% completion not the goal?
If you hit every target every day, you aren’t pushing hard enough. A 100% success rate usually hides slack in the plan or a lack of ambition. The goal is to understand and steadily reduce the failure rate, by targeting the biggest cause each time, not to plan so cautiously that nothing can fail.
Where does it fit with the rest of the business?
The Live Loop is step 2 of the 2026 productivity playbook, and it only works in a culture where a missed task can be reported without blame. That’s the black box idea. It’s also how we embed improvement in a contractor’s business: business improvement, and collaborative planning workshops to get the planning right first.
The bottom line: improvement isn’t a project. It’s a loop: ask why every day, fix the biggest cause, then the next, for as long as you’re in business.
FAQs
What is a continuous feedback loop in construction?
A daily system that records, for every planned task, whether it happened and if not why not, then fixes the biggest cause and repeats.
What is Percent Plan Complete (PPC)?
A Last Planner System measure: the share of tasks planned for a week that were completed as planned. Published figures vary widely, from the Lean Construction Institute’s 54% to a median of 76% across 119 projects in one study.
How long does it take to see results from a feedback loop?
Patterns usually show within two to four weeks, and the first gains within the first 60-day cycle, in the author’s experience.
Why is 100% task completion not the goal?
Because a perfect score usually means the plan has slack in it. The aim is to reduce failure steadily by fixing its biggest cause.
Sources
- Lean Construction Institute: “On average, only 54% of work planned for a given week is completed within the allotted schedule” (as cited in Going for Gold, chapter 5). LCI is a body that promotes the method and gives no underlying study for the figure.
- Ballard, G., The Last Planner System of Production Control, PhD thesis, University of Birmingham, 2000.
- Formoso, C. and Moura, C., “Evaluation of the impact of the Last Planner System on the performance of construction projects”, Proc. IGLC-17, 2009 (119 projects, Brazil). The PPC result (high 50s to high 70s in 12 months), the 60-day cycle, “reliable sites run in the 80s” and the patterns-within-weeks timing are the author’s own experience.
Andy Pritchard MCIOB
CIOB Gold Medal, Construction Manager of the Year 2019. Founder of Constructing Culture and author of Going for Gold. About Andy →