Level 3 – Detailed Work Package Programme

Level 3 – Detailed Work Package Programme: A Practical Guide for Contractors and Project Teams

The Level 3 Work Package Programme is where the construction plan becomes
real. It is the bridge between the master programme and the day-to-day management of work
on site. It takes the work packages defined in the Level 2 master programme and breaks them
down into the detailed activities, sequences, resources and constraints that site engineers,
superintendents and subcontractors need to actually execute the work.

The Level 3 programme is the most important planning document for the people doing the work.
It is where the construction methodology is translated into a day-by-day, crew-by-crew plan
that can be managed, measured and updated in real time. Without it, the master programme
floats above reality and the project is managed reactively.

This post covers what a Level 3 programme must contain, how it is built, how it connects
to the master programme above it and the look-ahead schedule below it, and what separates
a Level 3 programme that genuinely drives delivery from one that is produced and then ignored.


What the Level 3 Programme Is

The Level 3 programme is a detailed, logic-linked, resource-loaded schedule
for a specific work package, phase or area of the project. It contains:

  • A detailed breakdown of all activities within the work package
  • Logic links between activities reflecting the actual construction sequence
  • Durations calculated from production rates and crew/plant mixes
  • Resource assignments at crew and plant level
  • Material delivery milestones
  • Hold points, inspection requirements and permit milestones
  • Interface milestones with adjacent work packages
  • The critical path through the work package

A Level 3 programme typically contains 500–5,000 activities per work
package, depending on the complexity and duration of the work. Activities are typically
1–5 days in duration – detailed enough to manage daily progress but not
so granular that the programme becomes unmanageable.


How the Level 3 Programme Connects to the Rest of the Planning Hierarchy

The Level 3 programme sits between the Level 2 master programme and the Level 4 look-ahead
schedule. Its connections in both directions are critical to the integrity of the planning
system.

Connection to Level 2 – Master Programme

The Level 3 programme must be derived from and consistent with the Level 2
master programme. This means:

  • The start and finish dates of the work package in the Level 3 programme must match
    the corresponding dates in the Level 2 master programme.
  • The interface milestones in the Level 3 programme – the dates by which predecessor
    work packages must be complete and the dates by which this work package must deliver
    outputs to successor packages – must match the corresponding milestones in the Level 2
    master programme.
  • The overall sequence and methodology in the Level 3 programme must be consistent with
    the construction strategy defined in the Level 1 plan and reflected in the Level 2
    master programme.

When the Level 3 programme identifies a problem – a resource conflict, a logic error, a
constraint that was not visible at Level 2 – that information must flow back up to the
master programme. The Level 3 programme is not just a receiver of information from above;
it is also a source of information that improves the master programme.

Connection to Level 4 – Look-Ahead Schedule

The Level 4 look-ahead schedule is a rolling 2–6 week window into the Level 3 programme.
It is not a separate document – it is derived directly from the Level 3 programme by
extracting the activities that fall within the look-ahead window and breaking them down
to daily or shift level.

The Level 3 programme must be maintained at a level of detail that supports this. If the
Level 3 programme has activities that are 4 weeks long with no internal breakdown, the
look-ahead schedule cannot be derived from it. The Level 3 programme must be detailed
enough that the look-ahead schedule can be produced by extracting a window, not by
rebuilding the plan from scratch.


The Components of a Level 3 Programme

1. Activity Breakdown

The work package is broken down into individual activities at a level of detail that
allows daily progress to be measured. Each activity should represent a discrete unit
of work with:

  • A clear description of what is being done
  • A measurable quantity (e.g. “Pour slab – Zone A – 120 m³”)
  • A defined location or area
  • A duration of 1–5 days

Activities that are longer than 5 days should be broken down further. An activity that
takes 3 weeks cannot be meaningfully tracked for daily progress. Breaking it into
smaller activities makes progress visible and makes it easier to identify when the
work is falling behind.

2. Construction Sequence Logic

The logic links in the Level 3 programme must reflect the actual construction sequence –
not a theoretical sequence, not the sequence that would be most convenient for the
programme, but the sequence that the site team will actually follow.

This requires the planner to understand the construction methodology in detail. The
logic links for a concrete structure are different from those for a steel structure.
The logic links for a tunnel are different from those for an open cut. The planner
must work with the site team to define the sequence, not impose a sequence from above.

Common sequencing considerations in Level 3 programmes:

  • Structural sequence: Foundations before columns, columns before
    beams, beams before slabs. The sequence must reflect the actual structural system
    and the formwork/falsework strategy.
  • Zone sequencing: On large sites, work is often divided into zones
    that are worked in sequence or in parallel. The Level 3 programme must reflect the
    zone strategy and the interfaces between zones.
  • Trade sequencing: On multi-trade work packages, the sequence of
    trades must be carefully managed. Civil before structural, structural before
    mechanical, mechanical before electrical – but with overlaps where the methodology
    allows.
  • Curing and setting times: Concrete curing, grout setting, epoxy
    curing and similar time-dependent processes must be reflected in the logic. These
    are often modelled as lags on finish-to-start relationships.
  • Access and crane coverage: Activities that require crane access
    must be sequenced to avoid crane conflicts. The Level 3 programme must reflect
    the crane coverage plan.

3. Durations from Production Rates

Every duration in the Level 3 programme must be calculated from a 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 conditions of
the work package.

At Level 3, production rates should be more precise than at Level 2. The Level 2
master programme uses approximate production rates to establish the overall programme.
The Level 3 programme uses detailed production rates that reflect the specific
conditions of each activity – the access constraints, the pour size, the reinforcement
density, the ground conditions.

Production rate assumptions should be documented for every activity. When the programme
is challenged – in a delay claim, a variation assessment or a dispute – the production
rate documentation is the evidence that the durations were calculated, not assumed.

4. Resource Assignments

Resources are assigned to activities at crew and plant level. For each activity, the
Level 3 programme should show:

  • The crew composition (number and type of workers)
  • The plant and equipment required
  • The shift pattern (day shift, night shift, 10-hour shift, 12-hour shift)

Resource assignments at Level 3 are the basis for the Functional Manning Unit (FMU)
model. Each activity is executed by a defined FMU – a crew and plant mix that works
together as a system. The FMU defines the production rate, which defines the duration,
which defines the cost.

Resource loading at Level 3 allows the planner to:

  • Identify resource conflicts within the work package
  • Check that the resource requirements are achievable given the available workforce
    and plant
  • Produce a resource histogram showing the demand profile for the work package
  • Calculate the cost of the work package from the resource assignments and durations

5. Material Delivery Milestones

The Level 3 programme must include milestones for the delivery of materials that are
on the critical path or near-critical path of the work package. These milestones are
the interface between the construction programme and the procurement programme.

Material delivery milestones should be linked to the activities that depend on them.
If the reinforcement for a concrete pour is not delivered by the milestone date, the
pour activity cannot start. The Level 3 programme must make this dependency explicit.

6. Hold Points and Inspection Requirements

Hold points are mandatory stops in the construction sequence where work cannot proceed
until an inspection or approval has been completed. They must be included in the Level 3
programme as milestones or zero-duration activities with the appropriate logic links.

Common hold points in construction work packages:

  • Foundation inspection before concrete pour
  • Reinforcement inspection before concrete pour
  • Weld inspection before backfill
  • Pressure test before insulation
  • Electrical inspection before energisation

Hold points that are not in the programme will cause unplanned delays when they are
encountered on site. Including them in the Level 3 programme makes them visible and
allows them to be managed proactively.

7. Interface Milestones

Interface milestones are the dates by which this work package must receive inputs from
predecessor packages and deliver outputs to successor packages. They are the connection
points between the Level 3 programme and the Level 2 master programme.

Interface milestones must be agreed with the teams responsible for the predecessor and
successor packages. They cannot be set unilaterally by the work package team. When an
interface milestone is at risk, the impact on the successor package must be assessed
and communicated immediately.


Building the Level 3 Programme

The Level 3 programme is built by the site engineer or superintendent responsible for
the work package, with support from the project planner. The process is:

Step 1 – Extract the Work Package from the Master Programme

Identify the work package in the Level 2 master programme. Extract the start date,
finish date, interface milestones and resource requirements. These are the constraints
within which the Level 3 programme must be built.

Step 2 – Define the Activity Breakdown

Break the work package down into individual activities. Work with the site team to
define the activities – they know the construction sequence better than anyone. Each
activity should have a clear description, a measurable quantity and a defined location.

Step 3 – Define the Construction Sequence

Work with the site team to define the construction sequence. What must be done first?
What can be done in parallel? What are the dependencies between activities? Document
the sequence as a logic network.

Step 4 – 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 the
experience of the site team and comparable project data.

Step 5 – Assign Resources

Assign crew and plant to each activity. Check for resource conflicts. Resolve conflicts
by adjusting sequence, adding resources or extending durations.

Step 6 – Add Material Milestones, Hold Points and Interface Milestones

Add all material delivery milestones, hold points and interface milestones. Link them
to the activities that depend on them.

Step 7 – Check Against the Master Programme

Check that the Level 3 programme is consistent with the Level 2 master programme.
The start and finish dates must match. The interface milestones must match. If the
Level 3 programme shows that the work package cannot be completed within the master
programme dates, the master programme must be updated.

Step 8 – Identify the Critical Path

Run the schedule and identify the critical path through the work package. Communicate
the critical path to the site team. Make sure everyone knows which activities are
driving the completion date and which have float.

Step 9 – Baseline and Issue

Save the baseline. Issue the Level 3 programme to the site team, subcontractors and
the project planner. Brief the site team on the programme – the sequence, the critical
path, the key milestones and the resource requirements.


Maintaining the Level 3 Programme

The Level 3 programme must be updated at least fortnightly, and weekly on fast-moving
work packages. The update process involves:

  1. Record actual start and finish dates for completed activities.
  2. Update remaining durations for in-progress activities based on
    actual progress, not calculated from percentage complete.
  3. Update logic where the sequence has changed. Document the reason
    for any logic changes.
  4. Add new activities for scope changes, rework and unforeseen work.
  5. Update material delivery milestones based on the latest procurement
    information.
  6. Recalculate the schedule and identify the new critical path and
    forecast completion date.
  7. Report to the master programme. Feed the updated forecast completion
    date and any changes to interface milestones back into the Level 2 master programme.

Common Level 3 Programme Failures

1. The Level 3 Programme Is Not Built

The most common failure. The master programme is produced and the project goes straight
to look-ahead schedules without a Level 3 programme in between. The look-ahead schedules
are built from memory and informal conversations, not from a detailed plan. The master
programme cannot be maintained because there is no Level 3 data to feed into it.

2. The Level 3 Programme Is Built by the Planner, Not the Site Team

The planner builds the Level 3 programme in isolation, without input from the site
engineers and superintendents who will execute the work. The programme reflects the
planner’s assumptions about the construction sequence, not the site team’s knowledge
of how the work will actually be done. The site team ignores it.

3. Activities Are Too Long

Activities of 2–4 weeks in a Level 3 programme cannot be managed at daily level. The
look-ahead schedule cannot be derived from them. Progress cannot be meaningfully
measured against them. Activities in a Level 3 programme should be 1–5 days.

4. No Resource Assignments

A Level 3 programme without resource assignments cannot identify resource conflicts,
cannot calculate costs and cannot be used to manage the FMU. Resource loading is not
optional at Level 3.

5. Hold Points and Material Milestones Are Missing

Hold points and material delivery milestones that are not in the programme will cause
unplanned delays. They must be included and linked to the activities that depend on them.

6. The Level 3 Programme Is Not Updated

A Level 3 programme that is built at the start of the work package and never updated
is useless after the first week. Regular updates are essential for the programme to
remain connected to reality.

7. The Level 3 Programme Is Inconsistent with the Master Programme

The Level 3 programme shows different dates, different sequences or different resource
requirements from the master programme. The two documents tell different stories. The
project team does not know which one to follow.


Level 3 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 Level 3 programme is where the ECC methodology
is translated into the detailed execution plan.

The connection between the Level 3 programme and the ECC is direct:

  • The production rates in the Level 3 programme are the same production rates used
    to calculate the ECC durations and costs.
  • The resource assignments in the Level 3 programme are the same FMU crew and plant
    mixes used to calculate the ECC.
  • The durations in the Level 3 programme, when multiplied by the resource costs,
    produce the direct cost of the work package – which should match the ECC.

A Level 3 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 the cost model
as soon as work starts, and the project team will lose visibility of where costs are
being incurred.


Summary

The Level 3 work package programme is the bridge between the master programme and
day-to-day site management. It is the most important planning document for the people
doing the work. The key principles are:

  • Build the Level 3 programme from the Level 2 master programme
  • Involve the site team in defining the activity breakdown and construction sequence
  • Calculate durations from production rates and document the assumptions
  • Resource-load the programme at crew and plant level
  • Include all material milestones, hold points and interface milestones
  • Keep activities to 1–5 days so that daily progress can be measured
  • Update the programme at least fortnightly
  • Feed updated forecasts back into the master programme
  • Make sure the Level 3 programme is consistent with the ECC cost model

A Level 3 programme that meets these standards is a genuine management tool that connects
the strategic plan to the daily work. One that does not will leave the site team managing
from memory – and the master programme disconnected from reality.


Need Help with Work Package Programme Development or Maintenance?

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

Use the form below to discuss your project.

Ads Blocker Image Powered by Code Help Pro

Ads Blocker Detected!!!

We have detected that you are using extensions to block ads. Please support us by disabling these ads blocker.

Powered By
Best Wordpress Adblock Detecting Plugin | CHP Adblock