Level 2 – Master Programme: A Practical Guide for Contractors and Project Teams

The Level 2 Master Programme is the central planning document on any
construction project. It sits at the heart of the planning hierarchy – detailed enough
to manage the project, high-level enough to be readable and maintainable, and connected
to every other planning document above and below it.

The master programme is the document that the project manager uses to manage the project,
the client uses to monitor progress, the planner uses to assess delay, and the commercial
team uses to support claims and variations. It is the single most important planning
document on the project – and the one most often produced poorly.

This post covers what a master programme must contain, how it is built, how it is
maintained, and what separates a master programme that genuinely drives project delivery
from one that is produced for contract compliance and then ignored.

What the Master Programme Is

The master programme is a logic-linked, resource-loaded schedule that shows:

All major work packages and their activities
The sequence and dependencies between activities
The duration of each activity
The resources required for each activity
The critical path through the project
The float available on non-critical activities
All key milestones and contract dates
Interface events with other contractors, designers and stakeholders

It is typically maintained in a scheduling tool – Primavera P6, Microsoft Project, Asta
Powerproject or similar – and updated monthly with actual progress and revised forecasts.

The master programme is not a summary document. It is a working management tool. It must
be detailed enough to identify the critical path and manage the project, but not so
detailed that it becomes unmanageable. The right level of detail is typically
100–500 activities for most projects, though very large or complex
projects may require more.

What the Master Programme Is Not

Understanding what the master programme is not is as important as understanding what it is.

It is not a Level 1 summary. The master programme has logic links,
resource assignments and float calculations. A Level 1 summary has none of these.
It is not a Level 3 work package programme. The master programme
does not show individual concrete pours, daily crew assignments or shift-by-shift
activities. That level of detail belongs in the Level 3 programme.
It is not a static document. A master programme that is not updated
regularly with actual progress is not a master programme – it is a historical record.
It is not a contract compliance document. A master programme produced
to satisfy a contract requirement and then filed away is a waste of time and money.
The master programme must be used to manage the project.

The Components of a Master Programme

1. Work Breakdown Structure (WBS)

The WBS defines how the project is broken down into manageable work packages. It is the
framework within which all activities are organised. A well-structured WBS makes the
master programme readable and maintainable. A poorly structured WBS produces a programme
that is difficult to navigate and impossible to summarise.

The WBS should reflect how the work will actually be executed – by phase, by area, by
discipline or by a combination of these. It should not simply mirror the contract bill
of quantities, which is often structured for measurement purposes rather than for
construction management.

2. Activities

Each activity in the master programme represents a discrete unit of work that can be
planned, resourced and tracked. Activities at Level 2 are typically work package level –
for example, “Piling – Zone A”, “Structural Steel – Level 1”, “Mechanical Fit-Out –
Unit 3”. The detailed breakdown of each work package into individual tasks belongs at
Level 3.

Key principles for activities in the master programme:

No activity should be longer than the reporting period. If the
project is reported monthly, no activity should be longer than four weeks. Activities
longer than the reporting period cannot be meaningfully tracked for progress.
Every activity should have a measurable output. “Concrete works”
is not a good activity. “Pour foundations – Zone A (450 m³)” is a good activity.
Every activity should have at least one predecessor and one successor.
Activities with no predecessors (other than the project start) or no successors
(other than the project finish) are a sign of incomplete logic.

3. Logic Links

Logic links define the dependencies between activities. They are the most important
component of the master programme – without them, the programme is just a list of
activities with dates, not a model of how the project will be executed.

Every logic link in the master programme should be justified by a real construction
dependency. The planner should be able to explain, in plain language, why Activity B
cannot start until Activity A is complete (or started, or finished). If the explanation
is “because that’s how we’ve always done it” or “because the client wants it that way”,
the link should be questioned.

Common logic link types in construction master programmes:

Finish-to-Start (FS): The most common. Activity B cannot start
until Activity A is complete. Used where one activity must be fully complete before
the next can begin – for example, foundations must be complete before structural
steel can start.
Start-to-Start (SS): Activity B cannot start until Activity A has
started. Used for overlapping activities – for example, formwork and reinforcement
can start together, but reinforcement cannot start until formwork has begun.
Finish-to-Finish (FF): Activity B cannot finish until Activity A
has finished. Used where two activities must complete together – for example,
commissioning cannot finish until testing is complete.

4. Durations

Durations in the master programme must be calculated from production rates, not assumed
or reverse-engineered from a target date. The calculation is:

Duration = Quantity ÷ Production Rate

The production rate comes from the construction methodology – the plant mix, the crew
size and the realistic output of that crew and plant in the specific project conditions.
A duration that is not supported by a production rate calculation is an assumption.
Assumptions should be documented and reviewed.

5. Calendars

Calendars define the working days and hours for each activity. The master programme
typically uses multiple calendars:

Standard working week (5 or 6 days)
Extended working week (7 days for continuous operations)
Weather-restricted calendars for activities that cannot proceed in adverse conditions
Shutdown or possession calendars for activities that can only be done in specific windows

Incorrect calendars are a common source of schedule errors. An activity on a 5-day
calendar that is actually worked 7 days a week will show a longer duration than it should.

6. Milestones

Milestones are zero-duration activities that mark key events. The master programme should
include all contract milestones, handover dates, interface events and major hold points.
Milestones provide the reference points for progress reporting and contract management.

7. Resources

Resource loading assigns plant, equipment and crew to activities. A resource-loaded master
programme allows the planner to:

Check for resource conflicts
Calculate the cost of the programme
Identify peaks and troughs in resource demand
Model the impact of adding or removing resources on duration

Resource loading at Level 2 is typically at the work package level – for example, “2 ×
30 t excavators, 6 × dump trucks, 1 × grader” for an earthworks package. The detailed
crew and shift assignments belong at Level 3.

8. Constraints

Constraints are fixed dates imposed on activities. They should be used sparingly and
always justified by a real-world requirement. Every constraint should be documented with
the reason it exists. Constraints that cannot be justified should be removed – they
override the logic network and prevent the schedule from calculating correctly.

Building the Master Programme

The master programme is built from the Level 1 construction strategy. The process is:

Step 1 – Establish the WBS

Define the work breakdown structure. Organise the project into major work packages that
reflect how the work will be executed. Agree the WBS with the project manager and
commercial team before building the programme – changing the WBS after the programme
is built is expensive and disruptive.

Step 2 – Define the Activities

For each work package, define the activities that will be tracked in the master programme.
Each activity should represent a meaningful unit of work with a measurable output. At
Level 2, activities are typically 1–4 weeks in duration.

Step 3 – Calculate Durations

Calculate the duration of each activity from the quantity of work and the production rate.
Document the production rate assumptions. Check the durations against comparable project
data and the experience of the site team.

Step 4 – Build the Logic Network

Connect the activities with logic links. Start with the major finish-to-start dependencies
– the activities that must be complete before others can start. Then add start-to-start
and finish-to-finish relationships for overlapping activities. Check that every activity
has at least one predecessor and one successor.

Step 5 – Assign Calendars

Assign the appropriate calendar to each activity. Check that the calendars reflect the
actual working arrangements – shift patterns, weather restrictions, possession windows.

Step 6 – Add Milestones and Constraints

Add all contract milestones, handover dates and interface events. Add constraints only
where they are justified by real-world requirements. Document the reason for each
constraint.

Step 7 – Resource Load

Assign resources to activities. Check for resource conflicts. Resolve conflicts by
adjusting sequence, adding resources or extending durations. Produce a resource histogram
to show the overall resource demand profile.

Step 8 – Calculate the Critical Path

Run the schedule and identify the critical path. Check that the critical path makes
sense – that it runs through the activities that are genuinely driving the completion
date. If the critical path runs through activities that are clearly not the most
important, the logic network needs to be reviewed.

Step 9 – Check Float

Review the float on non-critical activities. Very high float (more than 4–6 weeks on
a 12-month project) may indicate missing logic. Negative float indicates that the
programme cannot be achieved as currently planned and that recovery action is needed.

Step 10 – Validate and Baseline

Validate the programme against the Level 1 strategy, the estimate and the contract
requirements. Once validated, save the baseline. The baseline is the frozen reference
point against which all future progress will be measured.

Maintaining the Master Programme

A master programme that is not maintained is not a management tool. Regular maintenance
is essential for the programme to remain useful throughout the project.

Monthly Update Process

The master programme should be updated at least monthly. The update process involves:

Record actual start and finish dates for completed activities.
Record percentage complete for in-progress activities.
Update remaining durations for in-progress activities. This is
the most important step. Remaining duration should be based on the actual rate
of progress, not calculated from percentage complete.
Update logic where the sequence has changed from the plan.
Document the reason for any logic changes.
Add new activities for scope changes, variations and unforeseen
work.
Recalculate the schedule and identify the new critical path and
forecast completion date.
Produce a progress report showing actual vs planned progress,
the current critical path and the forecast completion date.

Baseline Management

The baseline should not be changed without a formal change control process. Changing
the baseline to match actual progress – sometimes called “baseline washing” – destroys
the ability to measure performance and assess delay. The baseline is the reference point
for the project. It must be protected.

When a significant change occurs – a major variation, a significant delay event, a
fundamental change to the construction strategy – a new baseline may be established.
This should be done through a formal process, with the agreement of both parties, and
the original baseline should be retained for reference.

The Master Programme in Contract Management

The master programme is a contract document on most major construction projects. It is
submitted to the client, reviewed and accepted (or rejected), and used as the basis for
progress reporting, delay assessment and extension of time claims.

A master programme that is used in contract management must meet a higher standard than
one used purely for internal management. It must be:

Logic-linked. A programme without logic links cannot be used for
delay analysis. Most contracts require a logic-linked programme.
Realistic. A programme that shows activities completing faster than
is achievable will be challenged by the client. Durations must be supportable by
production rate calculations.
Updated regularly. A programme that is not updated cannot be used
to demonstrate the impact of delay events. Regular updates are essential for the
programme to be useful in a claim.
Consistent with the estimate. A programme that shows a different
methodology or different durations from the estimate will be challenged. The
programme and the estimate must tell the same story.

Common Master Programme Failures

1. Too Many Activities

A master programme with 10,000 activities is not more detailed – it is less manageable.
The critical path is buried in noise. Updates take days instead of hours. The programme
cannot be used for strategic decision-making. The right number of activities at Level 2
is 100–500 for most projects.

2. No Logic Links

A programme without logic links is a bar chart, not a schedule. It cannot calculate
the critical path, assess the impact of delays or model what-if scenarios. Every
activity must have at least one predecessor and one successor.

3. Durations Not Calculated from Production Rates

Durations that are guessed or reverse-engineered from a target date are not reliable.
When the programme is challenged – in a delay claim, a variation assessment or a
dispute – durations that cannot be supported by production rate calculations will
be rejected.

4. The Programme Is Not Updated

A programme that is submitted at contract award and never updated is useless for
project management and worthless in a dispute. Regular updates are not optional –
they are the mechanism by which the programme remains connected to reality.

5. The Critical Path Is Not Managed

Many project teams cannot identify the critical path of their own project. If the
team does not know what is driving completion, they cannot manage it. The critical
path must be reviewed at every monthly update and communicated to the project team.

6. The Programme and the Estimate Are Inconsistent

The programme shows one methodology and the estimate assumes another. This is
surprisingly common and means that either the programme or the estimate – or both –
are wrong. The programme and the estimate must be built from the same construction
methodology.

Master Programme and the Efficient Construction Cost (ECC)

The Efficient Construction Cost (ECC) is the cost of executing a scope
of work using the most efficient methodology, plant mix and crew size that is realistic
for the specific project conditions. The master programme is the time model that
corresponds to the ECC cost model.

The master programme and the ECC must be consistent:

The durations in the master programme must be consistent with the production rates
in the ECC model.
The resource assignments in the master programme must be consistent with the plant
and crew costs in the ECC model.
The sequence in the master programme must be consistent with the methodology
assumed in the ECC model.

A master programme that is inconsistent with the ECC is a programme that does not
reflect how the project will actually be executed. It will diverge from reality as
soon as construction starts.

Summary

The Level 2 master programme is the central planning document on any construction
project. It must be logic-linked, resource-loaded, built from production rates and
maintained throughout the project. The key principles are:

Build the master programme from the Level 1 construction strategy
Calculate durations from production rates, not from assumptions
Use logic links that reflect real construction dependencies
Resource-load the programme and resolve conflicts
Identify and manage the critical path
Update the programme monthly with actual progress
Protect the baseline and use change control
Make sure the programme and the estimate are consistent
Use the programme to manage the project, not just to satisfy contract requirements

A master programme that meets these standards is a genuine management tool that will
serve the project from contract award to completion – and will stand up to scrutiny
if a dispute arises.

Need Help with Master Programme Development or Maintenance?

We work with contractors, owners and project teams on methodology-led master programme
development, schedule maintenance and Efficient Construction Cost (ECC) modelling.
Our approach starts with how the work will actually be built – and builds the programme
and estimate from there.

Use the form below to discuss your project.

Level 2 – Master Programme