Programme drift usually develops gradually. Decisions take longer than expected, priorities change and unresolved issues begin to affect other parts of the work. Teams are still busy, but the plan becomes less reliable and confidence in meeting key milestones starts to fall.
When that happens, there is understandable pressure to act quickly. But committing to a new completion date before understanding what has gone wrong can leave teams facing the same problems under greater pressure. Recovery starts with an honest assessment of the current position and agreement on what needs attention first.
Establish Where the Programme Stands
Bring together the available information on scope, schedule, cost, risk, contracts and resources. Where figures conflict or information is missing, make those gaps clear so people understand the limits of what they are reviewing. The immediate priority is to establish a sufficiently reliable picture for decisions to be made. That becomes difficult when teams are working to different assumptions about progress, outstanding work or available resources.
Focus on the Issues Holding Delivery Back
A struggling programme can quickly generate a long list of actions, each competing for attention. Leaders need to identify which problems are having the greatest effect and understand what is causing them. A missed milestone, for example, may stem from unresolved design information or a decision that nobody has the authority to make. Addressing those underlying constraints gives teams a better chance of making progress than repeatedly chasing the activities affected by them.
Give People Clear Ownership and Authority
Recovery needs people who know what they are responsible for and have the authority to act. Each priority should have a named owner, a clear deadline and an agreed route for escalating anything they cannot resolve. Meetings should help those decisions happen, with the right people present and actions followed through. Adding more reporting and approval stages can consume time the team needs for recovery, so any changes to governance should have a clear purpose.
Build a Plan the Team Can Deliver
A recovery plan needs to reflect the people, resources and time available, along with the dependencies and contractual requirements shaping the work. Test assumptions with the teams responsible for delivery, including whether activities can realistically overlap and what needs to happen before others can start. Where the proposed approach involves trade-offs, make them visible. Setting achievable milestones for the next few weeks also gives everyone a way to assess whether the recovery is working and where further adjustments are needed.
Keep Commercial and Risk Controls Working
The pressure to regain time can lead to changes being agreed hurriedly or records falling behind. That can make it harder to understand the consequences of decisions and create further problems later. Keep change control, risk reviews and commercial records up to date throughout recovery. Where NEC contracts apply, relevant early warning and notification processes also need continued attention. Delivery and commercial teams should work closely so that decisions account for their potential effects on time, cost and contractual obligations.
Be Honest About Progress
Stakeholders need to understand what has gone wrong, what is being done and where their input is required. Be clear about what the recovery plan can achieve, which assumptions it depends on and what remains uncertain. Regular updates should explain progress against agreed milestones and address setbacks openly. Confidence is rebuilt when commitments are realistic and people can see evidence that actions are making a difference.
Nexgen Infrastructure works alongside teams in live programmes to assess delivery problems, establish practical recovery plans and strengthen the controls needed to keep progress on track.
