The gap between L2 and site reality
An L2 programme is essential for contract administration and management reporting, but it is too aggregated to run the day-to-day construction process. Between major milestones, the actual project consists of short-duration activities, access interfaces, crew movements, concrete pours, equipment cycles, material releases and handovers.
If those short activities are not visible in a near-term schedule, constraints frequently appear only during the next periodic review—after they have already affected production.
What an L4 schedule changes
- Look-ahead visibility: a rolling 2–6 week window shows what must start, finish and interface next.
- Constraint visibility: resource-linked activities reveal likely clashes between crews, equipment, access and materials.
- Early detection: frequent progress updates show variance while it is measured in days rather than months.
Three conditions that make L4 useful
1. Resources integrated with activities
An activity without its required crew, equipment and material assumptions is not a complete execution plan. Resource integration is what converts schedule logic into a constructability test.
2. Frequent progress updating
For critical underground, concrete and interface activities, stale progress data quickly destroys the value of the look-ahead. The update rhythm must match the speed at which site conditions change.
3. Actions tracked to closure
Every emerging constraint needs an owner, target date and escalation path. A constraint register without ownership simply records future delay.