In construction, activities are the individual tasks that make up the project schedule. If the WBS defines what is being delivered, activities define how and when each part of that scope will be built.

On a programme (Primavera P6, MS Project, Tilos, etc.), activities are the rows that carry:

• A clear description of the work
• Duration and logic links (predecessors / successors)
• Resources (crews, plant, key materials)
• Dates, float and criticality

Get activities wrong, and your programme becomes either a pretty picture with no link to reality or an unmanageable list that nobody uses.

Activities vs WBS vs Cost Codes

It helps to separate three layers:

• WBS (Work Breakdown Structure) – hierarchy of deliverables and locations
• Activities – discrete chunks of time‑based work used in the schedule
• Cost codes / estimate items – how costs are grouped and tracked

A good pattern is:

• WBS = “containers” of scope (e.g. ST-03-ABUT-S – Structure, Stage 3, South abutment)
• Activities = specific tasks under that container (e.g. “Install pier formwork – P3 South”)
• Cost codes = mapped to the same WBS so you can report time + cost together

What Makes a Good Activity?

A well‑defined activity should be:

1. Manageable
   Long enough to be meaningful, short enough to track.
   As a rule of thumb, somewhere between 1 and 20 working days, depending on project size and control needs.

2. Measurable
   You can say objectively whether it’s 0%, 50% or 100% complete.
   Ideally linked to a countable quantity (e.g. m³, m², lin.m, number of piles, number of spans).

3. Logical
   Has clear predecessors and successors.
   Follows real construction methodology and staging, not arbitrary sequences.

4. Owned
   A team or subcontractor is clearly responsible.
   Someone can stand up in the meeting and say: “This is mine, here is the status.”

Activity Types in Construction Programmes

Common activity types you’ll see:

• Production activities – excavation, piling, concreting, track laying, pavement lifts
• Access / possession activities – possessions, line blocks, lane closures, traffic switches
• Temporary works – propping, temporary track, diversions, falsework
• Design and approvals – design packages, IFC milestones, permits, rail operator approvals
• Testing and commissioning – integrated testing, trial running, handover packages

For methodology‑driven projects (rail / road / infrastructure), it’s worth explicitly modelling:

• Access windows as activities
• Work blocks inside each window as separate activities

That’s how you start linking Efficient Construction Cost (ECC) and possession strategy to the schedule.

Common Activity Mistakes

1. Too detailed
   Every tiny sub‑step becomes an activity.
   The programme explodes into thousands of lines that nobody updates properly.

2. Too coarse
   “Build bridge” as a single 180‑day activity.
   Impossible to track progress or isolate delays and EOT causes.

3. No connection to methodology
   Activities sequenced because the software allows it, not because that’s how you’ll actually build.
   Float and critical path become meaningless.

4. Mixed scope in one line
   Same activity covers different locations, stages or even different WBS elements.
   Hard to understand what’s late, and why.

5. Access not modelled
   Possessions / lane closures not explicitly shown.
   You can’t see where access drives the programme and cost.

Activities and Construction Methodology

To make activities truly useful, build them from construction methodology, not the other way round:

1. Start with staging diagrams and WBS
   Define workfaces, stages, possessions or traffic switches.
   Group scope under these containers.

2. Define work blocks
   For each stage or possession, identify what can be accomplished safely and reliably in that window.
   Turn those into activities with realistic durations.

3. Apply logical constraints

   • Physical (you can’t pour deck before installing girders)
   • Access (you can’t work in Zone A without line block or closure)
   • Resourcing (key plant and crews can’t be in two places at once)

4. Align with estimate and ECC model
   Activity durations and sequences should match the productivity assumptions used in the estimate.
   If methodology or access strategy changes, update both programme and ECC model.

Practical Tips for Activity Setup

• Use consistent naming
  Example: [Zone] – [Element] – [Operation]
  (Zone 3 – Abutment South – Install reinforcement)

• Think in reviewable chunks
  Can you sensibly discuss this activity in a weekly meeting?
  Can supervisors and crews recognise it on site?

• Keep a clear link to quantities
  Note key BOQ item(s) or quantity basis in the activity description or notes.
  That helps reality‑check durations and progress claims.

• Model access and constraints explicitly
  Separate activities for “Possession P06 – enable works” vs “P06 – track slews”, etc.
  Same for traffic switches and major stage changes.

Activities as a Tool, Not Just a Gantt Chart

Well‑structured activities let you:

• See where time is really going (productive vs non‑productive)
• Connect schedule slippage to actual scope and methodology issues
• Support EOT and disruption claims with clear logic
• Drive ECC by measuring scope per access window and productivity per workface

When activities are just “things in P6” with no link to methodology or cost, you lose most of that value.

Need Help Structuring Activities for Your Project?

If your current programme:

• Is either too high‑level to manage or too detailed to maintain
• Doesn’t reflect how the work will actually be staged and accessed
• Is hard to reconcile with the estimate, ECC model or possession / traffic plan

we can help you:

• Re‑structure WBS and activities around real construction methodology
• Model possessions / lane closures and work blocks properly
• Align programme logic with cost, risk and ECC so they all tell the same story
• Set up a schedule that planners, engineers and site crews can actually use

Get in Touch

Use the form below to discuss how we can support your programme and methodology:

Name *
First
Last
Email *
Comment or Message *
Submit