Why is it important to document the reasons for delays in Last Planner?

The Last Planner System is an effective method for planning, controlling, and continuously improving production in construction projects. With it, the project team jointly agrees which tasks will be carried out during the following week and ensures that the prerequisites for completing those tasks are in place.

Many construction sites actively track the PPC figure, which shows what share of agreed tasks were completed as planned. PPC is an important metric, but on its own it does not explain why tasks succeeded or failed. That is why documenting the reasons for delays is an essential part of making full use of Last Planner.

The PPC figure alone does not tell the whole truth

Percent Plan Complete, or PPC, shows what proportion of planned tasks were completed as agreed. For example, if PPC is 75 percent, we know that one quarter of the tasks were not completed as planned.

Without documenting the reasons for delays, however, we do not know what caused the deviations. Was it due to missing designs, delayed materials, a shortage of resources, an unfinished work area, or an overly optimistic weekly plan?

PPC shows the symptom. The reason for the delay shows what needs to be improved in production.

The reasons for delays reveal the real bottlenecks in production

On a construction site, a single delay may seem like a minor problem. However, when reasons are recorded week after week, a bigger picture of recurring production constraints begins to emerge.

For example, if a large share of delays is caused by missing designs, the problem is not an individual task but the coordination between design and production. If delays are often related to material deliveries, improvement measures should be directed at procurement, logistics, and supply chain control.

Identifying root causes enables continuous improvement

The core goal of Last Planner is not only to monitor performance, but to improve production reliability. This can only be achieved when deviations are used as a systematic source of learning.

When a reason is recorded for every task that was not completed as planned, the project team can review which problems recur and which have the greatest impact on the schedule. This means improvement is based on real data instead of individual opinions or memory-based assessments.

Documentation shifts the discussion from blame to processes

Addressing delays can easily turn into a search for someone to blame. A well-executed Last Planner process, however, guides the discussion away from individuals and toward processes.

The purpose is not to ask who failed, but why the agreed task was not executable. This improves collaboration, increases openness, and strengthens trust between the different parties in the project.

When the reasons for delays are documented openly, the site learns to solve problems instead of hiding them.

Fact-based management improves decision-making

In construction projects, decisions are often made under time pressure. If reliable information about the reasons for delays is not available, improvement measures may be directed at the wrong issues.

Documented reasons help project management see which constraints have the greatest impact on production progress. Based on this information, it is possible to decide whether more resources are needed, advance planning should be improved, procurement processes should be changed, or design management should be tightened.

Reason data also helps future projects

Information collected during one project is already valuable for that specific site, but its value increases further when it is also used in future projects.

When an organization collects reasons for delays across multiple projects, it can identify recurring risks and improve its operating models. This helps create more realistic schedules, improve procurement forecasting, and develop production control practices at the organizational level.

Which reasons should be documented?

The classification of delay reasons should be simple enough to be used consistently in everyday work. An overly complicated classification slows down recording and reduces the quality of the information.

• Missing or incomplete designs
• Delays in materials or deliveries
• Resource shortages or crew availability problems
• The work area was not ready
• The preceding work phase was delayed
• Quality defect or rework
• Weather conditions or an external disruption
• Overly optimistic or unclear task planning

The most important thing is that reasons are recorded using the same logic week after week. This makes the information comparable and allows it to be used reliably in reporting and in planning improvement measures.

Summary

The real value of Last Planner does not come only from weekly planning or tracking the PPC figure. The greatest value comes from documenting the reasons why tasks were not completed as planned and learning from them.

Recording the reasons for delays helps identify production bottlenecks, supports fact-based management, improves collaboration, and enables continuous improvement both in the current project and in future projects.

For every task that is not completed as planned, it is worth asking one simple question: why was this not completed as planned? When the answer is documented, it becomes valuable information for developing the entire project and organization.