A Six-Week Lookahead That Makes Work Ready

A six-week lookahead should help the team make future work possible. If it is only a printout of activities due to start, it identifies demand without establishing whether the site can meet it.

The useful distinction is between work that is scheduled, work that is ready and work the delivery team can responsibly commit to. A data centre programme needs all three views, connected through consistent activity, location and system references.

Start with the right slice of the programme

Include the activities expected to start or continue within the selected horizon, together with overdue incomplete work that affects them. Check the status date. A lookahead generated from an old update cannot reliably describe the current workfront.

Choose the horizon to suit the decisions involved. Six weeks can be useful for coordination, but it will not expose every long-lead procurement or approval issue early enough. Retain a wider view for constraints whose resolution takes longer than the lookahead period.

Turn each activity into a readiness conversation

Ask what must be available for the work to begin and continue safely: approved information, preceding work, materials, access, resources, plant, applicable permits and inspection arrangements. The relevant list should be agreed with the delivery team rather than applied mechanically to every activity.

“Awaiting design” is too broad to manage well. “Approved support detail for corridor C required before bracket fabrication” identifies a decision, a deliverable and a relationship to the work.

A workfront example

Illustrative scenario: cable installation in a service corridor is planned for week four. Containment completion is forecast for week three, but an unresolved support detail affects the route. The cable drums also require an agreed handling and storage arrangement.

The lookahead should identify the information release, the relevant containment inspection or release, and the delivery arrangements as separate constraints. Each needs an owner and a resolution date. If the detail is late, the team can assess an alternative workfront while there is still time to coordinate labour and materials.

Moving the cable activity by a week without dealing with these conditions merely moves the uncertainty. Adding people does not remove a missing design decision.

Agree commitments from work that is ready

In the weekly coordination meeting, distinguish planned candidates from commitments accepted by the responsible team. Record what was promised, where it will happen and what constitutes completion. If work is conditional on an unresolved item, make that condition visible instead of presenting it as an unconditional commitment.

At the next review, compare delivery with those commitments and discuss the reasons for variance. Categorise recurring causes consistently enough to identify patterns, but do not turn the exercise into a blame score. Repeated design, access or material issues should trigger a management action.

Keep the master programme informed

The lookahead must not become a second, contradictory schedule. Feed verified actual progress, changed remaining durations and agreed sequence revisions back into the controlled programme update. Check the implications for critical and near-critical paths, downstream trades and system milestones.

Plan Academy’s lookahead filter tutorial is a useful software-level reference for selecting upcoming and ongoing activities. The additional management task is to establish whether those activities can actually proceed.

Finish the meeting with a short list of decisions, named owners and dates. A lookahead succeeds when it changes the readiness of the work, not merely the appearance of next week’s report.