Construction Constraints: A Practical Guide for Contractors and Project Teams

Constraints are the conditions, limitations and dependencies that shape
how a construction project can be executed. They define the boundaries within which the
construction methodology must operate. They affect the sequence of work, the production
rate, the programme and the cost. Identifying them early, managing them proactively and
reflecting them accurately in the programme and estimate is one of the most important
disciplines in construction planning.

A constraint that is not identified until it stops work on site is not a constraint –
it is a crisis. A constraint that is identified early and managed proactively is a
planning input. The difference between the two is the difference between a project
that is in control and one that is not.

This post covers what construction constraints are, how they are categorised, how they
are identified and managed, and how they connect to the programme, the estimate and
the Efficient Construction Cost (ECC).

What Is a Construction Constraint?

A construction constraint is any condition that limits or controls when, how or in what
sequence work can be carried out. Constraints can be:

Physical – the ground conditions, the geometry of the site, the
proximity of existing structures or services.
Temporal – the time at which work can start or must finish, the
availability of weather windows, the timing of possessions or shutdowns.
Contractual – the dates and milestones imposed by the contract,
the sequence requirements specified by the client, the interface obligations with
other contractors.
Regulatory – the permits, approvals and licences required before
work can start, the environmental conditions that must be met, the safety
requirements that must be satisfied.
Resource – the availability of plant, equipment, materials and
workforce at the required time.
Logical – the construction dependencies that mean one activity
cannot start until another is complete.

Why Constraints Matter

Constraints matter because they directly affect the programme and the cost. A constraint
that is not identified and reflected in the programme will cause the programme to be
wrong. A constraint that is not reflected in the estimate will cause the estimate to
be wrong.

More importantly, constraints that are not identified early will cause disruption on
site. When a constraint is discovered on the day the work is due to start – the permit
has not been obtained, the material has not been delivered, the preceding work is not
complete – the crew is idle, the plant is standing and the cost continues. The day is
lost. If the same constraint had been identified two weeks earlier, it could have been
resolved before it affected the work.

This is the core principle of constraint management: identify constraints early
and remove them before they stop work.

Categories of Construction Constraints

1. Physical Constraints

Physical constraints are imposed by the physical characteristics of the site and the
work. They cannot be changed – they must be worked around.

Ground conditions: Rock, soft ground, groundwater, contamination.
Ground conditions affect the choice of construction method, the production rate
and the plant required. A method that works well in dry, competent rock will not
work in saturated soft ground.
Site geometry: The shape, size and topography of the site. A
confined site limits the size of plant that can be used and the number of machines
that can work simultaneously. A steep site affects haul road grades and truck
productivity.
Existing structures and services: Adjacent buildings, underground
services, overhead lines. These constrain the working envelope, the vibration
limits and the access routes.
Hydrology: Rivers, groundwater, tidal conditions. These affect
when and how work can be done in or near water.

2. Temporal Constraints

Temporal constraints define when work can or cannot be done.

Weather windows: Some activities can only be done in specific
weather conditions. Concrete cannot be poured in extreme heat or frost without
special measures. Earthworks in wet climates may be restricted to dry seasons.
Marine works may be restricted to calm weather windows.
Seasonal constraints: Environmental conditions that restrict
work in certain seasons – breeding seasons for protected species, wet seasons
that make access impossible, fire seasons that restrict hot work.
Possession and shutdown windows: On rail, road and live facility
projects, work can only be done during planned possessions or shutdowns. The
duration and frequency of these windows directly constrain the programme.
Noise and vibration restrictions: Work hours may be restricted
by local regulations or planning conditions. Night work, weekend work or work
near sensitive receptors may be prohibited or limited.

3. Contractual Constraints

Contractual constraints are imposed by the contract documents.

Contract milestones: Dates by which specific activities must be
complete. Failure to meet a milestone may trigger liquidated damages.
Sectional completion dates: Dates by which specific sections of
the works must be handed over. These constrain the sequence and phasing of the work.
Interface obligations: Dates by which the contractor must provide
access, information or completed work to other contractors or the client.
Sequence requirements: Contract requirements that specify the
order in which work must be done – for example, a requirement to complete one
section before starting another to maintain traffic flow or operational continuity.
Access restrictions: Limitations on when and where the contractor
can access the site – for example, restricted access during school hours near a
school, or restricted access during operating hours in a live facility.

4. Regulatory Constraints

Regulatory constraints are imposed by legislation, planning conditions and regulatory
approvals.

Planning and development approvals: Conditions attached to the
development approval that restrict working hours, noise levels, dust, traffic
movements or construction methods.
Environmental approvals: Conditions that restrict work near
waterways, protected vegetation or sensitive habitats. May include exclusion zones,
seasonal restrictions and monitoring requirements.
Permits to work: Permits required before specific activities can
start – hot work permits, confined space entry permits, excavation permits near
services.
Utility clearances: Approvals required from utility owners before
excavating near underground services.
Heritage and cultural heritage approvals: Approvals required before
disturbing areas of heritage or cultural significance.

5. Resource Constraints

Resource constraints are imposed by the availability of the resources needed to execute
the work.

Plant availability: The plant required for the methodology may
not be available at the required time. Long-lead plant – TBMs, large cranes,
specialist piling rigs – must be ordered well in advance.
Material availability: Materials with long lead times – structural
steel, precast elements, specialist equipment – must be ordered early. Delivery
delays are one of the most common causes of programme disruption.
Workforce availability: Specialist trades – coded welders, TBM
operators, specialist concreters – may not be available in the required numbers
at the required time.
Design information: Construction cannot proceed without the
design information needed to execute it. Late design is one of the most common
constraints on construction programmes.

6. Logical Constraints

Logical constraints are the construction dependencies that define the sequence of work.
They are the most fundamental type of constraint – they reflect the physical reality
that some work cannot start until other work is complete.

Foundations must be complete before columns can be erected
Columns must be complete before beams can be installed
Structure must be complete before cladding can start
Cladding must be complete before internal fit-out can start
Excavation must be complete before pipe laying can start
Pipe laying must be complete before backfill can start

Logical constraints are represented in the programme as logic links. Every logic link
in the programme should be justified by a real logical constraint. Logic links that
are not justified by a real constraint are artificial constraints that reduce float
and distort the critical path.

Identifying Constraints

Constraint identification is a systematic process that should be carried out at every
level of the planning hierarchy – from the Level 1 strategic plan through to the Level 4
look-ahead schedule.

At Level 1 – Strategic Planning

At the strategic level, the major constraints that will shape the overall programme
are identified:

When can the site be accessed?
Are there seasonal weather windows for key activities?
What are the major long-lead procurement items?
What are the major interface obligations?
What are the major regulatory approvals required?

At Level 2 – Master Programme

At the master programme level, constraints are reflected as:

Logic links between work packages
Milestone dates for regulatory approvals and interface events
Constrained start or finish dates where contractually required
Calendar restrictions for weather-sensitive activities

At Level 3 – Work Package Programme

At the work package level, constraints are identified for each activity:

What must be complete before this activity can start?
What materials, plant and permits are required?
Are there hold points or inspection requirements?
Are there access or working hour restrictions?

At Level 4 – Look-Ahead Schedule

At the look-ahead level, constraints are identified for each activity in the next
2–6 weeks and recorded in the constraint log:

Are the materials on order and confirmed for delivery?
Is the plant available and mobilised?
Are the permits and approvals in place?
Is the preceding work on track to be complete in time?
Are the crew and subcontractors confirmed?

The Constraint Log

The constraint log is the tool used to manage constraints at the working level. It
lists every constraint identified in the look-ahead window, the action required to
remove it, the person responsible and the date by which the action must be completed.

Activity	Constraint Type	Constraint Description	Action Required	Responsible	Due Date	Status
Pour slab – Zone A	Resource	Reinforcement not yet delivered	Confirm delivery date with supplier	Procurement	Mon 15 Jan	Open
Excavate trench – Ch 450	Regulatory	Utility clearance not obtained	Submit utility search and await clearance	Site Engineer	Wed 17 Jan	Open
Install formwork – Level 4	Logical	Level 3 slab not yet complete	Accelerate Level 3 pour – add second pump	Superintendent	Fri 19 Jan	Open
Weld penstock joint – Sta 12	Regulatory	Hot work permit not yet issued	Submit hot work permit application	Safety Officer	Mon 15 Jan	Closed

The constraint log is reviewed at the weekly planning meeting. Open constraints are
tracked until they are resolved. Constraints that are not resolved by their due date
are escalated. The constraint log creates accountability – every constraint has an
owner and a deadline.

Constraints in the Programme

Constraints are reflected in the programme in several ways:

Logic Links

Logical constraints are represented as logic links between activities. Every logic link
should be justified by a real constraint. The planner should be able to explain, in
plain language, why the link exists.

Milestone Activities

Regulatory approvals, interface events and long-lead procurement items are represented
as milestone activities. The activities that depend on them are linked to the milestone.
If the milestone is delayed, the dependent activities are automatically delayed in the
schedule.

Constrained Dates

Where a contractual or regulatory constraint imposes a fixed date on an activity, a
date constraint is applied in the scheduling tool. Date constraints should be used
sparingly – they override the logic network and can distort the critical path. Every
date constraint should be documented with the reason it exists.

Calendars

Temporal constraints – weather windows, possession windows, working hour restrictions –
are reflected in the activity calendars. An activity that can only be done during a
6-month weather window is assigned a calendar that reflects those working months.

Constraints and the Critical Path

Constraints are one of the primary drivers of the critical path. A constraint that
delays the start of a critical activity delays the project completion date by the same
amount. Understanding which constraints are on or near the critical path is essential
for managing the programme.

The most dangerous constraints are those that:

Are on the critical path – any delay to these constraints delays
the project.
Have long lead times – regulatory approvals, long-lead procurement
items and interface obligations that take months to resolve must be identified and
actioned early.
Are outside the contractor’s control – constraints that depend on
the client, the designer, a utility owner or a regulator cannot be resolved by the
contractor alone. They must be escalated and managed through the contract.
Are not yet identified – the most dangerous constraints are the
ones that have not yet been found. A systematic constraint identification process
at every level of the planning hierarchy is the best protection against being
surprised by a constraint on the day the work is due to start.

Constraints and the Efficient Construction Cost (ECC)

Constraints affect the Efficient Construction Cost (ECC) in two ways:

1. They Affect the Production Rate

A constraint that limits access, restricts working hours or requires a less efficient
method will reduce the production rate. A lower production rate means a longer duration.
A longer duration means more shifts of plant and crew cost. The ECC increases.

For example: a noise constraint that limits working to 8 hours per day instead of
10 hours per day reduces the production rate by 20%. The duration increases by 25%.
The plant and crew cost increases by 25%. The ECC is higher than it would be without
the constraint.

2. They Add Direct Costs

Some constraints add direct costs that would not otherwise be incurred:

Environmental monitoring required by a regulatory approval
Traffic management required by an access restriction
Temporary works required to protect an adjacent structure
Specialist equipment required to work within a confined space

These costs must be identified and included in the estimate. A constraint that is not
reflected in the estimate will produce a cost overrun when it is encountered on site.

Constraints in Claims and Disputes

Constraints are frequently at the centre of construction claims and disputes. The most
common scenarios are:

Constraints That Were Not Disclosed

The client or designer was aware of a constraint but did not disclose it in the tender
documents. The contractor priced and programmed the work without knowledge of the
constraint. When the constraint is encountered on site, it causes delay and additional
cost. The contractor claims for the impact.

Constraints That Were More Severe Than Anticipated

The tender documents disclosed a constraint but understated its severity. The ground
conditions were worse than the geotechnical report indicated. The access restriction
was more limiting than the contract documents described. The contractor claims for
the difference between the anticipated and actual impact.

Constraints That Were Caused by the Client

The client’s actions created a constraint that was not in the original programme –
late design information, late access, late approval of a method statement. The
contractor claims for the delay and disruption caused by the client-created constraint.

In all of these scenarios, the quality of the contractor’s constraint management
records is critical. A contractor who identified the constraint, recorded it in the
constraint log, notified the client and tracked the impact will be in a much stronger
position than one who did not.

Common Constraint Management Failures

1. Constraints Are Not Identified Until They Stop Work

The most common failure. Constraints are discovered on the day the work is due to
start. The crew is idle, the plant is standing and the cost continues. The constraint
could have been identified and resolved weeks earlier.

2. Constraints Are Not Reflected in the Programme

Constraints are identified but not reflected in the programme. The programme shows
activities starting before the constraints that affect them have been resolved. The
programme is unrealistic.

3. Constraints Are Not Reflected in the Estimate

Constraints are identified but not priced in the estimate. The additional cost of
working within the constraint – reduced production rate, additional temporary works,
monitoring requirements – is not included. The estimate is too low.

4. The Constraint Log Is Not Maintained

A constraint log is started but not maintained. Constraints are added but not closed
out. Actions are assigned but not followed up. The constraint log becomes a list of
problems rather than a management tool.

5. Constraints Outside the Contractor’s Control Are Not Escalated

Constraints that depend on the client, the designer or a regulator are identified but
not escalated. The contractor waits for the constraint to be resolved without formally
notifying the client of the impact on the programme. When the constraint causes delay,
the contractor has no contemporaneous record of having raised it.

Summary

Constraints are the conditions, limitations and dependencies that shape how a
construction project can be executed. They affect the sequence, the production rate,
the programme and the cost. The key principles of constraint management are:

Identify constraints systematically at every level of the planning hierarchy
Reflect constraints accurately in the programme – as logic links, milestones,
date constraints and calendars
Reflect constraints accurately in the estimate – including their impact on
production rates and direct costs
Maintain a constraint log with actions, responsibilities and due dates
Remove constraints before they stop work – not on the day they are encountered
Escalate constraints outside the contractor’s control through the contract
Keep contemporaneous records of all constraints and the actions taken to resolve them

A project that manages constraints proactively will be in control of its programme
and its costs. A project that discovers constraints on the day they stop work will
be managed reactively – and will lose time and money that could have been saved.

Need Help with Constraint Identification or Management?

We work with contractors, owners and project teams on constraint identification,
programme development, look-ahead scheduling and Efficient Construction Cost (ECC)
modelling. Our approach identifies constraints early – and builds the programme and
estimate around them.

Use the form below to discuss your project.

Construction Methodology