The Programme Is Updated. Is the Site Working to the Same Plan?
A current master programme is not enough if short-term plans, instructions, procurement, labour, plant and actual progress are working to different assumptions.
The short answer
An updated master programme does not mean the site is working to the same plan. The programme becomes operational only when its near-term activities are translated into workfaces, instructions, material dates, labour and plant requirements, design information, access conditions and measurable progress. If those decisions are maintained in separate meetings and spreadsheets, the master programme can be technically current while daily production follows a different reality.
The control objective is therefore not simply to update dates. It is to create one executable planning chain: approved programme logic sets priorities; short-term planning tests readiness; procurement and resources are aligned to those priorities; site teams record what actually happened; and the resulting evidence updates the next forecast. A plan that cannot be traced from programme activity to field action is a reporting document, not a control system.
A project example
Consider a building project entering a congested services and finishes phase. The master programme shows ceiling closure in Zone B beginning next Monday. The planner has updated the sequence after a client instruction, but the mechanical supervisor is still working from last week's lookahead. The latest approved drawing has not reached one subcontractor, a delivery is booked for Wednesday, the mobile access platform has been allocated elsewhere, and a preceding inspection is not yet closed.
On paper, the activity can start. On site, it cannot. The gap is not a scheduling calculation; it is a coordination failure between programme, information, procurement, resources and workface readiness. By Thursday the planner records delay, while operations describe the week as unusually busy. Both descriptions are true, but neither helps management understand why planned output was missed.
A stronger model treats the programme activity as a decision hub. The start date is supported by prerequisites, each prerequisite has an owner and required date, and actual progress is recorded against the same package and location. When one condition changes, the consequence becomes visible before the weekly progress meeting.
Follow the site-planning control chain
The same planning problem appears in six recurring situations. Teams must control the drawing revision that reaches the workface, decide which activity receives shared crane capacity, connect labour hours to installed output, verify that an inspected area is genuinely ready for the next trade, preserve evidence behind delay notices and plan commissioning and closeout as real completion work. These are not separate administrative topics. They are points where the formal programme either becomes executable or loses contact with site reality.
Why master programmes drift away from daily work
A master programme serves several purposes at once. It communicates contractual milestones, sequencing logic and overall forecast. Site teams, however, need a much shorter planning horizon and a more detailed description of readiness. A programme activity such as “install containment Level 7” may hide several workfaces, multiple crews, drawing releases, access requirements and material batches. If the short-term plan is created independently, it may no longer preserve the logic or priorities of the master programme.
Different functions also use different identifiers. Planning thinks in activities, procurement in packages and purchase orders, supervisors in zones and tasks, commercial teams in cost codes, and document control in drawing packages. Without stable relationships between these structures, a delayed material or unresolved instruction cannot be linked confidently to the activity it affects. The planner hears about the problem after the fact and adjusts dates without a complete explanation.
The result is a familiar pattern: a monthly programme appears governed, a weekly lookahead appears practical, and daily coordination appears energetic, yet the three levels do not reconcile. Management sees percentage complete but cannot tell which constraint prevented the planned sequence or whether tomorrow's work is genuinely ready.
Translate programme logic into executable work
A useful short-term plan should answer more than “what do we intend to do?” For each meaningful work package or workface, it should show the programme activity it supports, the planned location and quantity, the crew and plant demand, required information, required materials, preceding approvals, access conditions and the next handover. The level of detail should be enough to make a start/no-start decision before resources arrive.
This does not require turning the master programme into a field checklist. The two views have different purposes. The important point is traceability: the short-term task should be mapped to the controlling programme activity and the evidence of completion should be mapped back. That relationship allows site facts to change the forecast without manual interpretation.
A project-centric ERP can support this relationship by keeping common project, package, location and cost identities across planning, procurement, site and finance records. Saturn should be considered in that context—as an ERP foundation for connected project information, not as a replacement for professional scheduling judgement or specialist planning tools.
Use readiness, not optimism, to protect starts
Many missed starts are known before the planned date. A drawing is still under review, a material delivery is uncertain, the access route is blocked, a permit has not been issued, or the preceding trade has not released the area. The problem is that those facts live in different logs and are not evaluated together.
A readiness check should be simple enough to use repeatedly. For a near-term activity, identify the few prerequisites that would genuinely stop productive work. Give each a clear state: ready, at risk, not ready or not applicable. Record the owner and the date by which the condition must be resolved. Then review the exceptions, not every green item.
This changes planning behaviour. Instead of asking whether the team “expects” to start next week, the review asks which required conditions are not yet proven. Optimism remains useful for solving problems, but it is no longer a substitute for evidence.
Connect procurement to required-on-site dates
Purchase order status is a weak planning signal. “Ordered” says nothing about approved submittals, fabrication, inspection, transport, unloading, storage or the specific workface that needs the material. Procurement control becomes more useful when every critical package has a required-on-site date derived from the executable plan, not simply from the supplier's quoted lead time.
The date also needs context. If the programme sequence moves, the required date should be reassessed. If the supplier confirms a later milestone, the affected activities should become visible. Where partial deliveries are possible, the project should distinguish the quantity needed to start from the total order quantity. This prevents both false alarms and false confidence.
Procurement and planning then share one conversation: which work is becoming constrained, what decision can still change the outcome, and by when? That is more actionable than separate “late material” and “programme delay” lists.
Plan labour and plant against workface priorities
Resource plans should follow ready work, not merely historical habit. A crew scheduled to an unready area creates hidden productivity loss even if every timesheet is complete. A crane allocated to the loudest request can delay a critical lift elsewhere. Short-term planning should therefore show resource demand together with activity priority and readiness.
The project does not need false precision. Labour forecasts can be crew-level; plant requirements can be time windows; productivity assumptions can be ranges. What matters is that the assumptions are visible and that actual use can be compared with installed output. When resources move, the reason and programme consequence should be recorded rather than disappearing into the next revision.
Shared decision rules also reduce conflict. Critical-path impact, committed delivery windows, safety constraints, readiness and recovery value can be agreed in advance as factors for plant allocation. The final decision remains a management judgement, but the basis is transparent.
Record actual progress in a way the programme can use
A statement such as “80% complete” is difficult to govern unless the basis is known. Useful actual progress identifies the work package, location, installed quantity or milestone, date, and where appropriate supporting evidence. This does not mean photographing every task; it means using evidence proportional to the importance of the decision.
The progress record should answer two questions. First, what was physically achieved? Second, what does that achievement mean for remaining work and downstream activities? A task may be 80% complete but still block the next trade because the final 20% contains testing, access release or a critical interface.
Connecting actual progress to the same work structure used for planning also improves forecasting. Remaining duration and resource demand can be reviewed from observed performance rather than simply extending the original curve.
Manage instructions as planning events
Site instructions are often treated primarily as document or commercial events. They are also planning events. A revised sequence, changed detail, access restriction or additional scope can alter labour, plant, procurement and follow-on work even before the commercial value is agreed.
The project should therefore connect the instruction to affected work packages and programme activities as early as practical. Record what is known, what remains uncertain, who owns the response and what assumptions the current plan is using. Do not wait for every commercial issue to be settled before acknowledging an operational effect.
This is especially important for recovery planning. If teams quietly absorb changes into revised dates, management loses the baseline needed to understand why productivity or margin moved. A controlled record preserves both the current executable plan and the history that explains it.
Create one planning rhythm across horizons
Good programme control uses several horizons without allowing them to become separate truths. The master programme provides the governed baseline and forecast. A four-to-six-week lookahead exposes constraints and procurement needs. A one-to-two-week plan allocates workfaces and resources. Daily coordination reacts to immediate conditions while preserving the agreed priorities.
Each horizon should feed the next. The lookahead is not copied from the programme and forgotten; it identifies constraints that may change the forecast. Daily actuals are not merely reported upward; they update remaining work and readiness. Weekly planning is therefore both execution and forecasting.
A practical review rhythm is exception-led. Ask what planned work did not become ready, what started but underperformed, what new instruction changed the sequence, which resource conflicts need a decision, and which constraint threatens the next milestone. Those questions keep meetings focused on controllable actions.
Align codes without forcing one universal code
Construction organisations often try to solve integration by imposing one coding structure on every discipline. That can create as much friction as it removes. Planning, cost, procurement, document control and field operations legitimately need different levels of detail.
The better objective is governed mapping. A programme activity can relate to one or more work packages; a work package can relate to cost codes, procurement items, locations, drawings and progress measures. Those relationships should be defined during mobilisation and updated through controlled change.
With stable mapping, a manager can move from a delayed activity to the material package, the outstanding drawing, the responsible subcontractor and the cost exposure without rebuilding the connection manually. The system preserves context while each discipline keeps the structure it needs.
What management should measure
Milestone dates and percentage complete remain important, but they are lagging or compressed signals. Pair them with leading indicators that describe the health of the planning chain:
- near-term activities with unresolved readiness constraints;
- critical procurement items without confirmed required-on-site alignment;
- planned labour or plant assigned to workfaces not yet ready;
- activities with progress updates that lack a defined quantity or milestone basis;
- instructions not yet assessed for programme impact;
- repeated movement of the same activity without a documented cause;
- handovers where the receiving trade has not accepted readiness.
The purpose is not to create a bigger dashboard. It is to identify where the programme and the site are beginning to diverge while there is still time to act.
Frequently asked questions
Is a master programme enough if it is updated every week?
No. Frequency does not guarantee operational alignment. The master programme needs a traceable relationship to short-term tasks, workface readiness, procurement, resource allocation and actual progress. A weekly update that receives only summary percentages may still lag behind the decisions being made on site.
Should the planner own all short-term planning information?
No. The planner governs programme logic and forecast, but supervisors, engineers, procurement, document control, subcontractors and commercial teams own many of the conditions that make work executable. The control model should make those dependencies visible without transferring every responsibility to the planning function.
How detailed should workface planning be?
Detailed enough to support a reliable start, resource and handover decision. If a task description cannot identify the location, prerequisites, intended output and receiving activity, it is probably too broad for near-term control. Excess detail that no one updates is equally unhelpful.
Does connected ERP replace specialist scheduling software?
Not necessarily. Specialist planning tools can remain the best place for complex programme logic. The ERP value is in connecting approved programme references with procurement, labour, plant, documents, site evidence, cost and commercial records so the wider business can act on the same project context.
Where should a contractor start?
Choose one live project and one four-week window. Map planned activities to work packages and locations, identify the few constraints that can prevent each start, and connect actual completion evidence back to the same structure. Review the exceptions weekly before expanding the method.
A 30-day starting plan
In the first week, agree the planning hierarchy: master programme, lookahead, weekly plan and daily coordination. Define which level is controlled, who can change it and how activities map to packages and locations. In week two, select the readiness conditions that repeatedly stop work and assign owners.
In week three, connect one critical procurement stream and one shared resource to the near-term plan. Test whether a changed delivery or resource conflict becomes visible against the affected work. In week four, compare planned and actual output for a small set of workfaces and review whether the evidence is strong enough to update the forecast.
Do not judge success by the number of fields completed. Judge it by whether the project can answer, quickly and consistently: what should happen next, what is preventing it, who owns the decision, and how today's outcome changes the plan.