7. Construction Planning, Scheduling and Resource Optimization

Introduction and Context

Construction projects convert designs, approvals, materials, labour and capital into physical assets within a defined time and cost framework. Their performance depends not only on the quality of the design or the competence of the contractor, but also on the logic used to plan, sequence and control work. A project may have adequate finance and technically sound drawings yet experience delay because activities were poorly sequenced, resources were overcommitted, interfaces were ignored or schedule risks were underestimated.

Construction planning establishes what must be done, how it will be done, who will do it and what resources will be required. Scheduling converts this plan into a time-based model. Resource optimization then tests whether the proposed programme can actually be executed with available labour, equipment, materials, space and cash. These activities are interdependent. A schedule that ignores resource availability is only a theoretical timetable; a resource plan that ignores activity logic may create unsafe or inefficient production.

For real estate managers, the subject has strategic importance. Completion dates influence financing costs, marketing commitments, rental income, handover obligations and investor confidence. At the project level, planning and scheduling support procurement, coordination, progress measurement, claims administration and decision-making under uncertainty. This chapter examines bar charts, network models, the Critical Path Method (CPM), the Programme Evaluation and Review Technique (PERT), resource allocation and levelling, schedule risk, milestones, buffers and project acceleration.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain the role of construction planning and scheduling in project delivery.

2. Prepare and interpret bar charts and precedence network models.

3. Calculate early and late times, floats and the critical path using CPM.

4. Apply PERT estimates to uncertain activity durations.

5. Allocate and level labour, equipment, materials and other resources.

6. Analyse schedule risk, milestones, buffers and productivity constraints.

7. Compare acceleration strategies and evaluate their cost, risk and feasibility.

8. Use digital scheduling and analytics tools responsibly in managerial decision-making.

From Project Scope to an Executable Programme

Planning begins with scope definition. The project team must understand the product, contractual obligations, regulatory requirements, quality standards, site conditions, interfaces and completion criteria. Scope is then decomposed into a Work Breakdown Structure (WBS). The WBS divides the project into progressively smaller deliverables and work packages. A work package should be sufficiently defined to permit assignment, estimation, scheduling, budgeting and performance measurement.

A schedule is not simply a list of activities. It is a representation of relationships among activities. Each activity requires a defined duration, a logical position, one or more resources and a measurable completion condition. For example, “construct building” is too broad for effective control. It may be decomposed into excavation, foundations, reinforcement, formwork, concrete placement, curing, masonry, services installation, finishes and testing. The appropriate level of detail depends on project size, procurement method, reporting needs and the authority of the person responsible for the work.

The planning process normally proceeds through the following connected decisions:

• establish project objectives, constraints and contractual dates;
• develop the WBS and identify work packages;
• define activities and their deliverables;
• estimate durations and resource requirements;
• determine logical relationships;
• develop the baseline schedule;
• assess resource feasibility and risk;
• approve milestones and control procedures; and
• monitor actual performance and update forecasts.

The process is iterative. A preliminary schedule may reveal that the desired completion date is incompatible with procurement lead times or available crews. The plan must then be revised rather than defended mechanically.

Time Representation: Bar Charts and Milestones

The bar chart, commonly called a Gantt chart, displays activities against a calendar or elapsed-time scale. Each activity is represented by a horizontal bar whose position indicates its start and finish and whose length indicates duration. Progress may be shown by shading, a percentage-complete marker or an actual-progress bar.

Bar charts are useful because they are easy to read and communicate to clients, managers, subcontractors and site personnel. They provide a practical overview of planned work, concurrent operations, procurement periods and major milestones. A milestone is a significant event with zero or negligible duration, such as approval of a design package, completion of foundations, energisation of a building or formal handover. Milestones provide management checkpoints and can be linked to contractual payments or decisions.

The weakness of a basic bar chart is that it does not clearly expose the logic behind the dates. If one activity slips, the chart may not show which later activities are affected. It also tends to conceal the difference between critical and non-critical work. Consequently, bar charts are most effective when derived from a network-based schedule and supported by written assumptions.

A good bar chart should identify the work breakdown coding, responsible party, planned start and finish, current status, key interfaces and relevant constraints. It should distinguish baseline dates from forecast dates. Updating the bar itself without recording the reason for variance produces a visually attractive but analytically weak control document.

Network Models and Activity Logic

Network scheduling represents activities and their dependencies. The most widely used convention is Activity-on-Node (AON), in which a node represents an activity and arrows represent relationships. The common relationship is Finish-to-Start (FS): the successor cannot start until the predecessor finishes. Other relationships are:

• Start-to-Start (SS): the successor may start after the predecessor starts;
• Finish-to-Finish (FF): the successor cannot finish until the predecessor finishes; and
• Start-to-Finish (SF): the successor cannot finish until the predecessor starts, a relationship used relatively rarely.

Relationships may include leads or lags. A two-day lag after concrete placement before a related operation begins represents a waiting period. A lead permits partial overlap, but leads should be used cautiously because excessive overlap can hide unrealistic assumptions.

Network logic must reflect physical, contractual, safety and managerial realities. For example, waterproofing may require substrate preparation and inspection, while ceiling installation may depend on completion and testing of concealed services. A network containing excessive constraints becomes inflexible; one containing too few constraints permits impossible sequences. The scheduler should document assumptions, especially where design information or subcontractor methods remain uncertain.

Critical Path Method

CPM is a deterministic scheduling technique. It uses a single duration estimate for each activity and calculates the earliest and latest times at which activities can occur without extending the project completion date.

For an activity with duration d, the forward pass calculates:

• Early Start (ES): the earliest time the activity can begin;
• Early Finish (EF): ES + d.

For activities with several predecessors, ES is the largest EF among those predecessors. The largest value is used because all predecessor conditions must be satisfied.

The backward pass calculates:

• Late Finish (LF): the latest time the activity can finish without delaying the project;
• Late Start (LS): LF − d.

For an activity with several successors, LF is the smallest LS among those successors. Total float is calculated as:

Total Float = LS − ES = LF − EF.

Activities with zero total float form one or more critical paths. A critical path is therefore a chain of logically connected activities controlling the calculated completion date. It is not necessarily the longest-looking set of activities, nor is it permanently fixed. Changes in durations, logic, calendars or constraints may create a new critical path.

Illustrative CPM Calculation

Consider the following simplified sequence:

| Activity | Description | Duration (days) | Predecessor |

|---|---|---:|---|

| A | Site mobilisation | 3 | — |

| B | Excavation | 5 | A |

| C | Foundation concrete | 4 | B |

| D | Structural frame | 10 | C |

| E | Services rough-in | 6 | D |

| F | Internal finishes | 8 | E |

| G | External works | 7 | D |

| H | Testing and handover | 3 | F, G |

The forward pass gives A: ES 0, EF 3; B: 3–8; C: 8–12; D: 12–22; E: 22–28; F: 28–36; G: 22–29; and H: 36–39. The project duration is therefore 39 days. The controlling chain is A–B–C–D–E–F–H. The external works activity G finishes at day 29, but H cannot begin until F also finishes at day 36. In this simplified network, G has float associated with the difference between those dates. Management attention should nevertheless be maintained because resource conflicts or changes in logic can reduce that float.

CPM supports more than calculation. It helps managers identify activities requiring close control, test the effect of proposed changes, prioritise procurement and examine whether acceleration should be applied to a controlling activity. It does not, by itself, guarantee an achievable programme because it may ignore resource limits and uncertainty.

PERT and Schedule Uncertainty

Construction durations are uncertain because productivity, weather, information release, site conditions, labour availability and approvals vary. PERT addresses this uncertainty by using three estimates for each activity:

• optimistic time (a): favourable but realistic conditions;
• most likely time (m): the duration expected under normal conditions; and
• pessimistic time (b): an adverse but plausible duration.

The expected duration is:

te = (a + 4m + b) / 6

The activity variance is:

Variance = [(b − a) / 6]².

The weighted average gives greater importance to the most likely estimate. Under the traditional PERT assumptions, activity variability can be aggregated along a path. The expected project duration is the sum of expected durations on the selected path, while the path variance is the sum of activity variances. A standard normal approximation can then be used to estimate the probability of achieving a target date:

Z = (Target date − Expected project duration) / Project standard deviation.

PERT should be treated as a decision aid, not a promise of statistical precision. Its results depend on the quality and independence of estimates. Weather-related risks, for example, may affect several activities simultaneously, violating the assumption that activity uncertainties are independent. Monte Carlo simulation is often more appropriate for complex programmes because it models ranges, correlations and repeated schedule outcomes.

Resource Allocation and Levelling

A time-based schedule becomes executable only when resource requirements are compared with resource availability. Resources include direct labour, supervisory staff, cranes, concrete pumps, formwork systems, temporary works, materials, cash, site space and specialist subcontractors. Resource allocation assigns resources to scheduled activities. Resource levelling adjusts activity timing when demand exceeds availability.

Resource loading is the process of displaying the quantity of a resource required over time. A histogram may show, for example, that the programme requires 80 carpenters during one week although only 50 are available. The planner can then consider changing activity timing, increasing supply, altering construction methods or accepting a longer duration.

Resource levelling generally follows these principles:

1. Protect activities with little or no float.

2. Use available float on non-critical activities before delaying critical activities.

3. Avoid unnecessary peaks and severe fluctuations in crew size.

4. Consider continuity of work, because repeatedly starting and stopping crews reduces productivity.

5. Check space, access, safety and trade interference, not only numerical capacity.

6. Recalculate the critical path after levelling.

Resource smoothing attempts to reduce fluctuations without changing the project completion date, usually by using available float. Resource levelling may extend the completion date because the resource constraint is treated as binding. The distinction is important when reporting the consequences of a management decision.

Common allocation priorities include contractual urgency, criticality, safety, resource continuity, strategic customer commitments and cost. A mathematically efficient allocation may be operationally poor if it creates congestion or forces several trades into an unsafe workspace. Experienced planners therefore combine algorithmic outputs with site knowledge.

Sequencing, Productivity and Constructability

The logic of a schedule should reflect how work will actually be produced. Constructability review examines whether the design, procurement plan, site layout, methods and sequence are compatible. For repetitive buildings, location-based methods such as line-of-balance or flowline scheduling can be valuable. They track crews moving through floors, units or zones and help maintain a steady production rhythm.

Sequencing decisions involve trade-offs. Overlapping activities can shorten the programme but may increase rework, supervision requirements and safety exposure. For example, beginning finishes before the building envelope is sufficiently weather-tight may create damage and repeated work. Conversely, excessive waiting for complete predecessor handover may waste resources. The appropriate sequence is one that balances time, quality, safety, cost and certainty.

Schedule logic should also account for procurement. Long-lead items such as lifts, generators, façade systems or specialist mechanical equipment may control completion even when site activities appear on track. Design release, shop drawing approval, fabrication, shipping, inspection and installation should be modelled rather than represented by a single vague procurement bar.

Milestones, Buffers and Schedule Control

Milestones divide a programme into decision points. Effective milestones are objectively verifiable and linked to consequences. “Progress satisfactory” is weak; “podium slab inspected and accepted” is measurable. Milestones may be contractual, design-related, procurement-related, construction-related or commercial.

A buffer is protected time or capacity intended to absorb variation. Project buffer protects the final completion date, while feeding buffer protects the main sequence from delays in non-critical paths. Management reserve is broader than schedule float and may cover unforeseen work, but it should be governed and not quietly consumed as if it were ordinary float.

Buffers must be visible and controlled. If hidden contingency is embedded in every activity, the programme becomes difficult to interpret and early warning is weakened. If no contingency exists, minor disruptions immediately threaten the completion date. A sound control system records the original baseline, approved changes, current forecast, consumed float, emerging risks and actions required.

Progress measurement should be based on physical accomplishment rather than time elapsed alone. A concrete activity that is 50 percent through its planned duration is not necessarily 50 percent complete. Weighted milestones, quantity installed, earned value measures and objectively verified outputs provide stronger evidence. Schedule Performance Index (SPI), where used, should be interpreted carefully because earned value measures can approach one near completion even when important work remains.

Acceleration and Schedule Compression

When a completion date must be protected, the project team may compress the schedule. Crashing adds resources, overtime, additional shifts, prefabrication or alternative methods to reduce activity duration. It normally increases direct cost and may reduce productivity if supervision, space or material supply becomes inadequate.

Fast-tracking overlaps activities that were originally sequential. It can reduce duration without proportionally increasing direct labour, but it raises the probability of design changes, rework, coordination failures and claims. Selective overlap is preferable to indiscriminate concurrency.

A rational acceleration analysis identifies activities on the current critical path, determines their normal and crash durations, calculates crash cost and tests resource and technical feasibility. The cost slope is commonly expressed as:

Cost slope = (Crash cost − Normal cost) / (Normal time − Crash time).

The activity with the lowest feasible cost slope is not automatically the best choice. A decision must also consider safety, quality, subcontractor capacity, approval risk, impact on other paths and the possibility that a different path will become critical. Acceleration should be authorised through a documented change process, with revised method statements, risk assessments and commercial terms.

Schedule Risk and Governance

Schedule risk arises from uncertainty and from incorrect assumptions. Typical sources include incomplete design, uncertain ground conditions, late approvals, labour turnover, material shortages, extreme weather, interface failure, industrial action, changes in regulation and poor productivity. Risk management begins with identification and extends through qualitative assessment, quantitative analysis, response planning and monitoring.

A risk register should identify the risk event, cause, consequence, owner, probability, impact, response and trigger. Responses include avoiding the risk, reducing its probability or impact, transferring an element through contract or insurance, accepting it with contingency, or exploiting an opportunity. Schedule risk analysis should distinguish ordinary activity float from risk allowance. Float is a mathematical property of the current network; contingency is a management provision for uncertainty.

Governance is essential when schedules are used for claims or executive reporting. Baseline changes should be approved, coded and traceable. Actual dates should not be manipulated to make performance appear better. Delays should be analysed by cause, responsibility, concurrency and effect on the critical path. A delay to a non-critical activity may not create compensable time impact, while a delay that consumes float may later become critical. Contractual analysis requires competent interpretation of notice provisions, extensions of time and records.

Digital Scheduling and Data-Enabled Planning

Modern scheduling platforms link WBS codes, calendars, resources, cost accounts, documents and progress records. Building Information Modelling (BIM) can support four-dimensional planning by associating model elements with scheduled activities. This assists visualisation of site logistics, workface planning, temporary works and installation sequences.

Field applications can capture quantities, photographs, inspections and labour hours. Dashboards can compare baseline, actual and forecast dates. Artificial intelligence and machine-learning tools may identify patterns associated with delay or productivity loss, but their usefulness depends on reliable historical data, consistent coding and human review. Automated predictions should not replace professional judgement, especially where data are sparse or project conditions are unique. Cybersecurity, access control, data ownership and auditability must be addressed when project information is shared across organisations.

Illustrative Case: Recovery of a Delayed Mixed-Use Development

Background

This illustrative case concerns a 14-storey mixed-use development containing retail space, offices and apartments. The approved programme required completion in 22 months. The contractor used a bar chart but had not integrated procurement activities or resource histograms into the master schedule.

Situation and Problem

After eight months, the structural frame was three weeks behind plan. The façade subcontractor had not received approved shop drawings, and the tower crane was being used simultaneously for structure, blockwork and mechanical equipment. Management initially proposed overtime across all trades.

Analysis

The project controls team converted the bar chart into an AON network. The analysis showed that structural completion, façade closure, services testing and commissioning formed the controlling sequence. Several apparent delays were not yet affecting completion because they had float, while approval of façade shop drawings had almost no remaining float. Resource loading showed that overtime would worsen crane congestion and increase night-shift inefficiency. PERT-style three-point estimates indicated substantial uncertainty in façade fabrication and authority inspection durations.

Approach and Solution

The team introduced the following measures:

• a design-release milestone was established for each façade zone;
• façade procurement was split into fabrication lots to permit partial installation;
• a second lifting arrangement was hired for selected materials;
• blockwork was resequenced to zones where crane demand was lower;
• the façade and services teams adopted a controlled overlap after weather-tightness criteria were defined;
• a feeding buffer was placed before commissioning;
• weekly look-ahead planning was introduced, with constraints assigned to named owners; and
• acceleration was limited to activities whose cost and safety implications were documented.

Outcome

The revised programme recovered two of the three lost weeks without general overtime. The remaining week was protected through an approved extension of the commissioning shift and earlier authority coordination. The project did not eliminate all risk, but it replaced reactive acceleration with targeted intervention based on criticality, resources and uncertainty.

Learning Points

The case demonstrates that a visible delay is not always the best target for intervention. Network logic identifies the activities that control completion; resource analysis reveals whether proposed solutions are feasible; and risk analysis prevents false confidence in a single deterministic date. It also shows the importance of integrating design and procurement into construction scheduling.

Common Errors and Professional Practice

Several mistakes repeatedly weaken construction programmes. These include excessive activity detail without reliable updating, missing logic links, treating all activities as critical, using percent complete without measurable rules, ignoring calendars and holidays, failing to model approvals and procurement, and levelling resources without recalculating the critical path. Another serious error is changing baseline dates to conceal delay rather than recording an approved change.

Best practice is to maintain a single controlled master schedule supported by discipline-level schedules. The programme should have clear coding, documented assumptions, realistic calendars, named owners and a defined update cycle. Look-ahead schedules should identify constraints before they affect work. Schedule meetings should focus on decisions and commitments, not merely on reporting red and green indicators. Planners should validate logic with construction personnel and review the programme after every major design, procurement or method change.

Ethically, schedule information must be reported honestly. Deliberately understating risk can lead to unsafe working hours, unfair claims, financial misrepresentation and poor decisions by investors or public authorities. Professional responsibility requires transparency about uncertainty, limitations of models and the consequences of acceleration.

Current Developments

Construction planning is increasingly moving toward integrated production control. Location-based scheduling, takt planning, digital twins, automated progress capture and collaborative planning systems are being combined with traditional CPM. These developments can improve visibility, but they do not eliminate the need for sound scope definition and disciplined field verification. The emerging emphasis is not merely on producing a more complex schedule; it is on creating a reliable flow of work, reducing constraints and making decisions earlier.

Chapter Summary

Construction planning translates project scope into an executable method, while scheduling represents activities, durations, relationships and milestones over time. Bar charts communicate timing clearly but should be supported by network logic. CPM calculates early and late dates, float and critical paths using deterministic durations. PERT incorporates optimistic, most likely and pessimistic estimates to analyse uncertainty, although complex projects may require simulation and correlation analysis.

Resource allocation and levelling test whether the programme can be delivered with available labour, equipment, materials, space and supervision. Resource smoothing uses float to reduce peaks without changing completion, whereas levelling may extend the project. Milestones, buffers and objective progress measures strengthen control. Crashing and fast-tracking can compress schedules but require careful analysis of cost, quality, safety and risk. Digital tools, BIM and analytics improve integration and visibility when supported by reliable data and professional judgement. Ultimately, an effective schedule is a management model for making informed decisions, not merely a calendar of promised dates.

Key Terms

Work Breakdown Structure: A hierarchical decomposition of project deliverables and work packages.

Activity: A defined item of work requiring time and usually resources.

Milestone: A significant, objectively verifiable event with little or no duration.

Bar Chart: A time-scaled chart showing activity durations as horizontal bars.

Network Model: A representation of activities and their logical dependencies.

Predecessor: An activity that must occur before another activity according to defined logic.

Finish-to-Start: A relationship in which a successor starts after its predecessor finishes.

Critical Path: The path of activities controlling the calculated project completion date.

Early Start: The earliest time an activity can begin based on network logic.

Late Finish: The latest time an activity can finish without delaying project completion.

Total Float: The amount of time an activity can be delayed without delaying the project finish, subject to the schedule model.

CPM: A deterministic method for calculating activity timing and critical paths.

PERT: A probabilistic scheduling method using three duration estimates.

Resource Loading: The process of displaying resource demand over time.

Resource Levelling: Adjusting activity timing to resolve resource over-allocation.

Resource Smoothing: Reducing resource fluctuations using available float without changing completion.

Schedule Buffer: Protected time or capacity reserved to absorb variation.

Crashing: Reducing duration by adding resources or increasing expenditure.

Fast-Tracking: Overlapping activities that were previously planned sequentially.

Constructability: The extent to which a design and plan can be efficiently and safely built.

Review Questions

Short Answer Questions

1. What is the principal limitation of a basic bar chart?

2. Define total float and state how it is calculated.

3. Distinguish between resource smoothing and resource levelling.

4. What are the three time estimates used in PERT?

5. Why should procurement activities be included in the master schedule?

Long Answer Questions

1. Explain the process of developing a construction schedule from project scope and the WBS.

2. Describe the forward-pass and backward-pass procedures in CPM.

3. Discuss how resource constraints can change a theoretically feasible network schedule.

4. Explain the managerial uses and limitations of PERT and quantitative schedule risk analysis.

5. Compare crashing and fast-tracking with reference to cost, risk, quality and control.

Analytical / Application Questions

1. A project has two parallel paths. One path has zero float, while the other has ten days of float. A resource shortage delays the second path by six days. Explain whether the project completion date necessarily changes and identify what should be checked.

2. A contractor proposes general overtime to recover a delay, but the site has severe crane congestion. Analyse the likely consequences and recommend a more appropriate decision process.

3. A façade package has optimistic, most likely and pessimistic durations of 20, 30 and fifty days. Calculate its PERT expected duration and variance, and explain why the result should not be treated as a guaranteed completion date.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the principal value of a network model compared with a basic bar chart?

A. It eliminates uncertainty in activity durations.

B. It shows logical dependencies and helps identify activities controlling completion.

C. It automatically assigns unlimited resources to activities.

D. It records contract payments without progress measurement.

Correct Answer: B. It shows logical dependencies and helps identify activities controlling completion.

Question 2

In a CPM forward pass, when an activity has two predecessors, its Early Start is normally based on which value?

A. The smallest predecessor Early Finish

B. The average predecessor duration

C. The largest predecessor Early Finish

D. The latest project completion date

Correct Answer: C. The largest predecessor Early Finish

Question 3

An activity has Early Start 12, Early Finish 20, Late Start 15 and Late Finish 23. What is its total float?

A. 3 days

B. 5 days

C. 8 days

D. 11 days

Correct Answer: A. 3 days

Question 4

Which PERT estimate receives the greatest weighting in the expected-duration formula?

A. Optimistic estimate

B. Most likely estimate

C. Pessimistic estimate

D. The standard deviation

Correct Answer: B. Most likely estimate

Question 5

A project team delays a non-critical activity within its available float to reduce a temporary labour peak, without changing the completion date. This is an example of:

A. Fast-tracking

B. Crashing

C. Resource smoothing

D. Risk transfer

Correct Answer: C. Resource smoothing

Question 6

Which situation most directly indicates a need for resource levelling rather than merely revising activity logic?

A. Two activities have the same predecessor.

B. Required crane hours exceed the crane's available hours during the same period.

C. A milestone has zero duration.

D. An activity has a finish-to-start relationship.

Correct Answer: B. Required crane hours exceed the crane's available hours during the same period.

Question 7

What is the main risk of fast-tracking?

A. It always increases project duration.

B. It prevents any activity overlap.

C. It may increase rework and coordination risk by overlapping dependent work.

D. It can only be used on non-critical activities.

Correct Answer: C. It may increase rework and coordination risk by overlapping dependent work.

Question 8

Which statement about a critical path is most accurate?

A. It remains unchanged throughout the project.

B. It consists only of activities with the highest direct cost.

C. It is the path with the greatest number of activities.

D. It may change when durations, logic, calendars or constraints change.

Correct Answer: D. It may change when durations, logic, calendars or constraints change.

Question 9

A schedule buffer is best understood as:

A. Unrecorded delay hidden inside every activity.

B. Protected time or capacity intended to absorb variation.

C. A replacement for construction quality inspections.

D. A method of removing all project risks.

Correct Answer: B. Protected time or capacity intended to absorb variation.

Question 10

Why should AI-generated schedule predictions be reviewed by experienced professionals?

A. AI tools cannot display dates in a calendar.

B. Predictions are reliable only when the project has no uncertainty.

C. Their usefulness depends on data quality and they may not represent unique project conditions.

D. Professional review is required only for non-critical activities.

Correct Answer: C. Their usefulness depends on data quality and they may not represent unique project conditions.