In construction, the schedule is the time model of your project.

If the WBS defines what is being delivered, and cost codes define where the money lands, the schedule shows when and in what order everything happens – and activities are the building blocks of that schedule.

Done well, the schedule becomes a living model of your construction methodology. Done badly, it’s just a colourful Gantt chart that nobody believes.

What a Construction Schedule Should Do

A good construction schedule should:

• Reflect how the work will actually be built – method, staging, possessions, traffic switches
• Support cost and resource planning – crews, plant, access, cashflow
• Provide a basis for risk analysis – what happens if key activities slip?
• Underpin claims and EOTs – clear logic, traceable changes
• Tie into Efficient Construction Cost (ECC) and Total Outturn Cost (TOC) – so time, cost and methodology tell the same story

Schedule, WBS, Activities and Cost Codes – How They Fit

• WBS
  Hierarchy of deliverables by area, element, stage.

  “What and where are we building?”

• Activities (within the schedule)
  Time‑based tasks under each WBS element.

  “How and when do we build each part?”

• Cost Codes
  Buckets for cost collection, mapped to WBS and activities.

  “How much did it cost?”

• Schedule
  The network of all activities in time, with logic, constraints, and dates.

  “What is the overall sequence and how long will it take?”

When these are aligned, you can trace any issue:

Scope (WBS) → Activities → Time Impact (schedule) → Cost Impact (cost codes) → ECC/TOC impact

Types of Schedules on a Construction Project

You will typically see several levels of schedules:

1. Tender / Bid Schedule

   • High‑level durations and logic used for pricing and bid strategy.
   • Often optimistic and not fully resourced.

2. Baseline Construction Schedule

   • Detailed, logic‑linked programme agreed at contract award.
   • Becomes the reference for progress measurement and EOT claims.

3. Look‑Ahead Schedules (e.g. 3‑week, 6‑week)

   • Short‑term, high‑detail view used by site teams.
   • Derived from the baseline but tuned with real‑world constraints.

4. Interface / Possession / Shutdown Schedules

   • For rail and road, specific schedules for possessions, line blocks, lane closures, traffic switches.
   • Show exactly what will happen in each access window.

5. Commissioning and Handover Schedules

   • Focused on integration, testing, trials, defects and handover milestones.

Key Features of a Robust Construction Schedule

1. Logic-Driven, Not Date-Driven

Every activity should:

• Have valid predecessors and successors (except start/finish milestones).
• Reflect physical, access, and resource constraints.
• Use relationships (FS, SS, FF, SF) and lags that make sense for the methodology.

2. Linked to Quantities and Productivity

Durations should come from:

• Quantities (BOQ or model)
• Expected productivity (crew output per shift / per day)
• Access regime (hours per shift, days per week, possessions vs normal working)

If the estimate assumes one thing and the schedule assumes another, planning and ECC both suffer.

3. Reflects Access and Staging

For rail / road / brownfield projects, the schedule should explicitly model:

• Possessions / line blocks / lane closures / traffic switches as activities or calendars
• Logical grouping of work within each access window (work blocks)
• Stage boundaries aligned with staging diagrams and WBS

4. Resource and Cost Awareness

Even if you don’t fully resource‑load every activity, the schedule should:

• Be checked for resource clashes (critical crews, key plant)
• Support cashflow / cost phasing discussions
• Tie into cost codes well enough to see where delays will hurt financially

Common Scheduling Problems

1. No link to methodology
   Programme built as a list of activities, not from staging and constructability.
   Critical path and float are technically correct but practically meaningless.

2. Over‑simplified access modelling
   Possessions or lane closures represented as single summary bars or not shown at all.
   You can’t see the real impact of access constraints.

3. Too basic or too detailed

   • Too basic: “Build station” as a few long bars – impossible to manage or claim on.
   • Too detailed: thousands of micro‑activities that nobody updates.

4. No maintained baseline

   • Changes applied directly over the top of the original programme.
   • No clear baseline vs current vs as‑built for EOT and disruption analysis.

5. Disconnected from estimate and cost codes

   • Programme exists in isolation from time‑related cost.
   • ECC and TOC cannot be tested against the actual schedule logic.

Schedules and Efficient Construction Cost (ECC)

ECC is all about how efficiently you convert time and access into delivered scope.

The schedule is the engine for that:

• It shows how much scope is planned per possession / per shift
• It exposes unproductive time, waiting and fragmentation
• It allows you to simulate different staging and access strategies before committing

Typical ECC‑related schedule questions:

• What happens to cost and delivery if we reduce the number of possessions but extend each one?
• Can we re-sequence works to reduce remobilisations and temporary works?
• Are we over‑ or under‑loading access windows with scope, leading to risk or inefficiency?

Answering these requires a schedule that faithfully represents methodology and access, not a generic bar chart.

Schedules and Total Outturn Cost (TOC)

TOC looks at the whole‑of‑life cost of an asset. The construction schedule affects TOC by:

• Driving the duration of disruption during construction (user impacts, revenue loss, etc.)
• Locking in long‑term maintenance access patterns through design and staging choices
• Affecting the timing of renewals and interventions

When TOC modelling is aligned with the schedule:

• You can see the real cost of accelerated vs extended programmes
• You can compare options that reduce future maintenance possessions at the expense of more complex construction staging now
• Business cases become grounded in actual time–cost–methodology relationships

Practical Tips for Better Schedules

• Start with WBS + staging diagrams, then build activities and logic
• Use clear, consistent activity naming with zone / element / operation
• Model access and constraints explicitly (possessions, blockades, traffic switches)
• Keep a clean baseline and record changes – don’t overwrite history
• Review the schedule with people who actually build, not just planners
• Regularly compare plan vs actual and feed learning back into ECC and TOC models

Need Help Making Your Schedule Match Reality?

If your current schedule:

• Looks good in software but doesn’t reflect how you will actually build
• Doesn’t clearly show possessions, lane closures or staging boundaries
• Is hard to reconcile with the estimate, ECC model or cost reporting
• Won’t stand up to EOT / disruption claim scrutiny

we can help you:

• Rebuild or refine schedules around real construction methodology
• Integrate WBS, activities, cost codes, ECC and TOC into a single coherent framework
• Model access, staging and temporary works explicitly so you can optimise them
• Set up practical baseline and update processes that planners and engineers can maintain

Get in Touch

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

Name *
First
Last
Email *
Comment or Message *
Submit