Construction Scheduling: A Practical Guide for Contractors and Project Teams

Construction scheduling is the process of translating a construction plan into
a time-based model that shows when each activity will be carried out, how long it will take,
what resources it requires and how it connects to every other activity on the project.

A good schedule is one of the most powerful management tools on a construction project.
A bad schedule – or no schedule at all – is one of the most reliable predictors of cost
overrun, delay and dispute.

This post covers what construction scheduling involves, how it connects to planning and
estimating, the techniques used, and what separates schedules that are genuinely used from
those that are produced for contract compliance and then ignored.

Scheduling vs Planning – Understanding the Difference

Scheduling and planning are related but distinct activities. The distinction matters because
confusing them leads to one of the most common failures in project management: building a
schedule before the plan exists.

Planning is the process of deciding how the work will be done –
the methodology, sequence, resources and constraints.
Scheduling is the process of translating that plan into a time-based model –
assigning durations, dates and logic links to activities.

Planning comes first. Scheduling follows. A schedule that is built without an underlying plan
is a collection of activities with arbitrary durations and no connection to how the work will
actually be executed.

This is not a theoretical distinction. On most projects where the schedule fails to reflect
reality, the root cause is that the schedule was built before the methodology was defined.

What a Construction Schedule Must Do

A construction schedule must do five things to be useful:

Reflect the construction methodology.
The sequence of activities must match the sequence in which the work will actually be
executed. If the schedule shows concrete pours before formwork is complete, or structural
steel before foundations are finished, it is not a real schedule.
Show realistic durations.
Durations must be calculated from production rates – the amount of work a crew and plant
mix can complete per shift or per day. Durations that are guessed, copied from previous
projects without adjustment, or reverse-engineered from a target date are not reliable.
Capture all real dependencies.
Logic links must reflect genuine construction dependencies, not just administrative
preferences. Every finish-to-start, start-to-start and finish-to-finish relationship
should be justifiable by a real-world constraint.
Identify the critical path.
The schedule must clearly show which sequence of activities is driving the completion
date. If the critical path cannot be identified, the schedule cannot be managed.
Be maintainable.
A schedule that cannot be updated regularly with actual progress is not a management
tool. It must be structured so that progress can be recorded, the critical path
recalculated and the forecast completion date updated at least monthly.

The Components of a Construction Schedule

Activities

Activities are the basic building blocks of a schedule. Each activity represents a discrete
unit of work with a defined start, finish and duration. Activities should be sized so that
progress can be meaningfully measured – too large and they become unmanageable; too small
and the schedule becomes unwieldy.

A useful rule of thumb: no activity should be longer than the reporting period (typically
two to four weeks for most projects). Activities longer than this cannot be meaningfully
tracked for progress.

Logic Links (Dependencies)

Logic links define the relationships between activities. The four standard relationship
types are:

Finish-to-Start (FS) – Activity B cannot start until Activity A is complete. The most common relationship.
Start-to-Start (SS) – Activity B cannot start until Activity A has started. Used for overlapping activities.
Finish-to-Finish (FF) – Activity B cannot finish until Activity A has finished. Used where two activities must complete together.
Start-to-Finish (SF) – Rarely used in construction.

Lags (positive or negative time offsets on a relationship) should be used sparingly and
always justified. Excessive use of lags is a sign that the logic has not been properly
thought through.

Durations

Durations are calculated from:

Quantity of work (from the design or bill of quantities)
Production rate (from the methodology – how much work the crew and plant can do per unit time)
Working hours (shift pattern, calendar)

The formula is simple:

Duration = Quantity ÷ Production Rate

A duration that is not derived from this calculation is an assumption. Assumptions should
be documented and reviewed.

Calendars

Calendars define the working days and hours for each activity. A project may have multiple
calendars – for example, a standard 5-day calendar for office activities, a 6-day calendar
for site works, a 7-day calendar for continuous operations, and weather-restricted calendars
for activities that cannot proceed in rain or high winds.

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.

Milestones

Milestones are zero-duration activities that mark key events – contract milestones,
handover dates, hold points, interface events with other contractors. They provide
reference points for progress reporting and contract management.

Resources

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

Check for resource conflicts (more resources required than available)
Calculate the cost of the programme (by pricing the resources)
Identify peaks and troughs in resource demand
Model the impact of adding or removing resources on duration

Constraints

Constraints are fixed dates imposed on activities – for example, a must-start-on date for
a weather-dependent activity, or a must-finish-by date for a contract milestone. Constraints
override the calculated dates from the logic network and should be used sparingly. Every
constraint should be justified by a real-world requirement.

Critical Path Method (CPM)

The Critical Path Method (CPM) is the standard technique for analysing
construction schedules. It calculates the longest path through the logic network – the
sequence of activities that determines the earliest possible completion date. This is the
critical path.

Activities on the critical path have zero float – any delay to a critical
activity delays the project completion date by the same amount. Activities off the critical
path have positive float – they can be delayed by up to their float amount without affecting
the completion date.

Understanding the critical path is essential for:

Focusing management attention on the activities that matter most
Assessing the impact of delay events (Time Impact Analysis)
Making decisions about acceleration and resource reallocation
Identifying near-critical paths that could become critical if conditions change

Float – Total Float vs Free Float

Float is the amount of time an activity can be delayed without affecting the project
completion date (total float) or the start of the next activity (free float).

Type	Definition	Use
Total Float	Time an activity can slip without delaying project completion	Identifies critical and near-critical activities
Free Float	Time an activity can slip without delaying its successor	Useful for local scheduling decisions
Negative Float	Activity is already behind the target date	Signals that recovery action is needed

Float ownership is a common source of dispute. Most contracts treat float as a project
resource available to both parties, but this is not always clearly stated. The treatment
of float should be understood before a delay claim is prepared.

Schedule Levels and Their Uses

Level	Detail	Audience	Update Frequency
Level 1	Summary milestones only	Client / board	Monthly
Level 2	Major work packages and milestones	Project manager / client	Monthly
Level 3	Detailed work package activities	Site management	Monthly / fortnightly
Level 4	Short-interval look-ahead	Foremen / crew leads	Weekly

Schedule Updating and Progress Monitoring

A schedule that is not updated is not a management tool. Regular updating is essential
for the schedule to remain useful throughout the project.

A schedule update should include:

Actual start and finish dates for completed activities
Percentage complete for in-progress activities
Remaining duration for in-progress activities (not just calculated from % complete)
Revised logic where the sequence has changed from the plan
New activities for scope changes or variations
Updated forecast completion date based on current progress

The most important field in a schedule update is the remaining duration.
Percentage complete is a lagging indicator – it tells you where you have been. Remaining
duration is a leading indicator – it tells you where you are going.

Baseline Schedule vs Current Schedule

Every project should maintain two versions of the schedule:

The baseline schedule – the original approved schedule, frozen at
contract award or project start. Used as the reference point for measuring progress
and assessing delay.
The current schedule – the live schedule, updated regularly with
actual progress and revised forecasts. Used for day-to-day 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.

Schedule Risk Analysis

A deterministic schedule produces a single completion date. In reality, durations are
uncertain – they depend on weather, ground conditions, resource availability, productivity
and dozens of other factors. Schedule Risk Analysis (SRA) quantifies this
uncertainty by running thousands of simulations with varying durations and producing a
probability distribution of completion dates.

The output of an SRA is typically expressed as:

P50 – the date by which there is a 50% probability of completion
P80 – the date by which there is an 80% probability of completion
P90 – the date by which there is a 90% probability of completion

SRA is increasingly required on major infrastructure projects and is a valuable tool for
understanding the real risk in a programme. A schedule that shows a single completion date
with no acknowledgement of uncertainty is presenting false precision.

Linear Scheduling (Time-Chainage)

For linear infrastructure projects – roads, railways, pipelines, tunnels – the standard
bar chart or network schedule is often not the best tool. Linear scheduling
(also called time-chainage or time-distance scheduling) plots activities against both time
and chainage (distance along the alignment), making it easy to see:

Where crews are working at any point in time
Where crews will conflict or interfere with each other
The production rate of each crew (the slope of the line)
Where delays in one activity will cascade into others

Tools like TILOS are specifically designed for linear scheduling. For long linear projects,
a time-chainage diagram is often more useful than a Gantt chart for site management.

Common Scheduling Failures

1. Too Many Activities

A schedule with 50,000 activities is not more detailed – it is less manageable. The level
of detail should match the level at which the project can be managed. More activities means
more data entry, more errors and less clarity about what matters.

2. Open Ends

Activities with no predecessors (other than the project start) or no successors (other than
the project finish) are a sign of incomplete logic. Every activity should have at least one
predecessor and one successor.

3. Excessive Constraints

Hard constraints override the logic network and prevent the schedule from calculating
correctly. A schedule with many hard constraints cannot be used for delay analysis or
what-if scenarios.

4. Lags Used Instead of Activities

Using a lag of 10 days on a finish-to-start relationship instead of creating a 10-day
activity hides work from the schedule and makes it impossible to track progress on that
work. Lags should represent genuine time offsets, not hidden activities.

5. No Resource Loading

A schedule without resources cannot be used to check whether the plan is achievable.
Resource conflicts that are not identified in the schedule will become crises on site.

6. The Schedule Is Not Used on Site

The most common failure of all. The schedule is produced for contract compliance, submitted
to the client, and then ignored. Site supervisors manage from memory, whiteboard sketches
and informal conversations. The schedule and the site diverge immediately.

What Makes a Schedule Credible in a Dispute

When a schedule is used in a delay claim or dispute, it will be scrutinised by the other
party’s experts and potentially by an adjudicator, arbitrator or court. A credible schedule
must demonstrate:

That it was prepared before the works, not reconstructed after the fact
That durations were calculated from production rates, not assumed
That logic links reflect genuine construction dependencies
That it was updated regularly with actual progress
That the critical path was correctly identified and maintained
That constraints were justified and not used to manipulate float

A schedule that cannot demonstrate these things will be challenged. The best protection
against a schedule being rejected in a dispute is to maintain it properly throughout
the project.

Scheduling and the Efficient Construction Cost (ECC)

The schedule and the cost estimate are two outputs of the same underlying model – the
construction methodology. The schedule shows how long the methodology takes. The estimate
shows how much it costs. They must be consistent with each other.

A schedule that shows a 12-month programme but an estimate based on an 18-month programme
is internally inconsistent. One of them is wrong. The Efficient Construction Cost
(ECC) is the cost of executing the scope using the most efficient realistic
methodology – and the schedule that corresponds to that methodology is the ECC schedule.

Aligning the schedule and the ECC is one of the most important steps in producing a
reliable bid or project budget.

Summary

A construction schedule is only as good as the plan behind it. The key principles are:

Plan the methodology before building the schedule
Calculate durations from production rates
Use logic links that reflect real construction dependencies
Identify and manage the critical path
Resource-load the schedule and resolve conflicts
Update the schedule regularly with actual progress
Use look-ahead schedules for day-to-day site management
Keep the baseline frozen and use change control
Make sure the schedule is used on site, not just submitted to the client

A schedule that meets these standards is a genuine management tool that will serve the
project from start to finish – and will stand up to scrutiny if a dispute arises.

Need Help with Construction Scheduling or Programme Development?

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

Use the form below to discuss your project.

Construction Scheduling: A Practical Guide for Contractors and Project Teams

Scheduling vs Planning – Understanding the Difference

What a Construction Schedule Must Do