Pearls Blog
Why Planners Should Use Lags Carefully In project scheduling
Impact of using lags in a bad way to the construction project Schedule
introduction
lags: defined as delays inserted between activities, can be a practical tool when applied appropriately. They are often used to represent short waiting periods or natural gaps between tasks. However, when lags are overused or applied incorrectly, they tend to introduce more complications than benefits.
For this reason, planners should exercise caution and rely on lags only when absolutely necessary, ensuring that project schedules remain transparent, flexible, and easy to manage.
Reduce Schedule Transparency
Lags reduce the overall transparency of a schedule by embedding waiting periods directly into relationships between tasks, lags hide important information that would otherwise be visible as independent activities.
This makes the schedule harder to interpret, review, and communicate with stakeholders. For example, instead of clearly showing a “Concrete curing (3 days)” activity, a planner might insert a three-day lag between tasks.
While this may seem efficient, it obscures the reason for the delay. A better approach is to explicitly model such durations as separate activities, allowing everyone involved to clearly understand what is happening and why.
Break Logic When Conditions Change
Another critical limitation of lags is their rigidity, Lags are fixed durations, meaning they do not automatically adjust when project conditions change.
In real-world projects, factors such as weather, labor productivity, or resource availability frequently shift. However, a lag remains static unless manually updated.
This can result in outdated or inaccurate schedules, ultimately affecting forecasting and planning decisions. In dynamic environments where adaptability is essential, relying heavily on fixed lags can weaken the overall reliability of the schedule.
Complicate Schedule Updates
Lags also make schedule updating more challenging. Unlike regular activities, lags do not have measurable attributes such as start dates, finish dates, or percentage completion
This means planners can’t directly track their progress or status. As a result, it becomes more difficult to accurately reflect real-world progress in the schedule.
Over time, this limitation can create inconsistencies between planned timelines and actual performance, reducing confidence in the schedule as a management tool.
Distorting the Critical Path
Improper use of lags can also distort the critical path, the sequence of activities that determines the total project duration. Lags can artificially increase or decrease float, which may hide the true critical path.
When the critical path is not clearly identified, project teams may focus their attention on the wrong activities. This can lead to poor prioritization, ineffective resource allocation, and weakened risk management, ultimately jeopardizing project success.
Hide Risk and Assumptions Finally
lags often conceal important risks and assumptions within the schedule. A lag may represent waiting time, external dependencies, or uncertain conditions, but these factors are not explicitly documented. This lack of visibility makes it harder to identify potential risks and respond effectively when issues arise.
If a delay occurs, determining its root cause becomes more difficult, which can slow down corrective actions and impact project outcomes. So it’s preferred to explicit activities over lags Keep logic clear and traceable Use lags only when they add clarity, not hide it
Conclusion
Lags have their place in project scheduling, but they should be used with caution and only when they genuinely add value to the schedule. Overusing lags can reduce transparency, complicate updates, distort the critical path, and hide important risks and assumptions.
A well-built schedule should make the project logic easy to understand, update, and manage. Whenever a waiting period or dependency can be better represented as a separate activity, doing so provides greater visibility and control. The goal is not to eliminate lags completely, but to use them intentionally—keeping the schedule clear, flexible, and reliable for better project planning and decision-making.