Schedule and Time Management

Introduction

Construction is performed through a temporary sequence of interdependent activities. Time management converts the project scope, design information, resources, and contractual obligations into an executable plan. A schedule is not merely a calendar: it is a model of how work is expected to flow, who must perform it, what resources are required, and when completion can be achieved.

Poor scheduling produces congestion, idle labor, late procurement, rework, disputes, and unsafe acceleration. Effective scheduling supports coordination among the client, designer, contractor, subcontractors, suppliers, and authorities. It also provides a baseline against which progress, delay, entitlement, and corrective action can be assessed.

This chapter explains activity networks, precedence diagrams, critical-path analysis, PERT, resource management, line-of-balance planning, milestones, look-ahead planning, delay analysis, and schedule compression.

Learning Objectives

By the end of this chapter, students should be able to:

1. Decompose construction scope into activities and logical relationships.
2. Develop precedence networks and calculate early dates, late dates, and float.
3. Identify and interpret the critical path.
4. Apply PERT estimates under uncertainty.
5. Develop practical baseline, milestone, look-ahead, and recovery schedules.
6. Explain resource leveling, resource smoothing, and line-of-balance planning.
7. Analyze delays and distinguish critical from non-critical impacts.
8. Evaluate schedule-compression alternatives while recognizing cost, risk, quality, and safety consequences.

1. Foundations of Construction Scheduling

1.1 Work breakdown and activities

Scheduling begins with a work breakdown structure (WBS). The WBS divides project scope into deliverables and work packages. Activities are the measurable operations that consume time and usually require labor, equipment, materials, information, or approvals. Examples include setting out, excavation, reinforcement, formwork, concrete placement, curing, waterproofing, and commissioning.

An activity should be sufficiently detailed to permit assignment of responsibility and progress measurement, but not so detailed that the schedule becomes unmanageable. A useful activity generally has:

• a clear start and finish;
• a defined deliverable;
• an identifiable responsible party;
• a measurable quantity or completion criterion; and
• estimated duration and resources.

Milestones are zero-duration events used to mark significant conditions, such as “building permit approved,” “structure topped out,” or “practical completion.” A milestone is not normally a productive activity and should not be used to conceal duration.

1.2 Logical relationships

The most common relationship is finish-to-start (FS): Activity B cannot start until Activity A finishes. Other relationships are:

Relationships may include a lead or lag. A 3-day FS lag means the successor starts 3 days after the predecessor finishes. A lead permits overlap, but excessive leads can hide risk and should be justified by construction method.

The network must represent technical logic, contractual constraints, site access, procurement, approvals, and resource availability. A schedule that shows only technical logic may be mathematically neat but operationally impossible.

2. Precedence Diagramming and Network Logic

In an activity-on-node (AON) precedence diagram, each node represents an activity and arrows represent relationships. Activities should generally flow from a single project start toward a single project finish. Networks should not contain circular logic. Mandatory logic arises from physical or technical necessity; discretionary logic reflects the selected method and may be changed during optimization.

For a finish-to-start relationship with lag L, the principal forward-pass equation is:

Here, ES_j is the early start of successor j, EF_i is the early finish of predecessor i, and L_ij is the lag from i to j, all measured in consistent time units. For an activity with duration d_j:

The convention above uses time zero as the project start and treats duration as elapsed time. Some organizations use day-one conventions, in which reported dates differ by one calendar day. The convention must be stated and applied consistently.

For a backward pass, if activity i precedes activity j under an FS relationship:

and:

LF and LS are late finish and late start. The minimum is used because an activity with several successors must satisfy the most restrictive successor.

Total float is:

Total float is the amount an activity can be delayed without delaying the calculated project completion, assuming network logic and other conditions remain unchanged. Free float is the delay possible without delaying the early start of any successor. For an FS relationship without lag:

Float is not automatically “free time.” It may be needed by another trade, consumed by approved changes, or reduced by progress elsewhere. Negative float indicates that imposed dates cannot be met under the current logic and durations.

Worked example: critical-path calculation

Consider the following activities, with durations in working days:

Forward pass:

• A: ES = 0, EF = 3.
• B: ES = 3, EF = 8.
• C: ES = 3, EF = 11.
• D: ES = 8, EF = 12.
• E: ES = max(11, 12) = 12, EF = 18.
• F: ES = 12, EF = 15.
• G: ES = max(18, 15) = 18, EF = 22.

The earliest project completion is 22 working days. Backward pass from project finish at day 22 gives:

• G: LF = 22, LS = 18.
• E: LF = 18, LS = 12.
• F: LF = 18, LS = 15.
• C: LF = 12, LS = 4.
• D: LF = min(12, 15) = 12, LS = 8.
• B: LF = 8, LS = 3.
• A: LF = min(3, 4) = 3, LS = 0.

Thus A, B, D, E, and G have zero total float and form the critical path: A–B–D–E–G. Activity C has total float of 1 day, and F has total float of 3 days. A delay to C of one day may not delay completion; a delay to D of one day will normally delay completion by one day unless corrective action changes the network.

3. Critical-Path Method and Schedule Control

The critical-path method (CPM) uses deterministic duration estimates. Its value is not simply identifying a path; it shows where management attention is most valuable. The critical path can change as actual progress, logic, calendars, and remaining durations change. Therefore, it must be recalculated periodically rather than treated as permanently fixed.

A practical baseline schedule includes:

• approved scope and WBS;
• activity IDs and descriptions;
• logic relationships and constraints;
• calendars and working-time assumptions;
• planned durations and quantities;
• resource and cost assignments where appropriate;
• contractual milestones;
• a data date and baseline approval record.

Progress updating requires a consistent status date. Actual starts and finishes should be recorded, remaining duration should be estimated from current conditions, and incomplete activities should not be marked complete merely because their planned finish date has passed. Schedule variance should be interpreted with physical progress and quality information, not dates alone.

A useful earned-schedule concept compares the time at which earned work was planned to occur with the status date. However, schedule indicators do not replace analysis of logic, remaining work, and likely completion. A project can report high percentage completion while critical enabling work remains late.

4. PERT and Duration Uncertainty

CPM commonly uses one duration. The Program Evaluation and Review Technique (PERT) uses three estimates:

• optimistic time, a: favorable but credible conditions;
• most-likely time, m: normal conditions; and
• pessimistic time, b: unfavorable but credible conditions.

The traditional beta-distribution approximation for expected activity time is:

The estimated variance is:

The standard deviation is σ, and variance has squared time units. These formulas assume that the three estimates represent a reasonable range and that the beta approximation is useful for the activity. They do not guarantee accuracy, and correlation among activities is not captured by simply adding independent variances.

For a path, expected duration is the sum of expected activity durations. If activity durations are treated as independent, path variance is:

and path standard deviation is the square root of path variance. The probability of meeting a target T is often approximated using a normal distribution:

where μ_path is expected path duration. This approximation is most defensible when the path contains several activities and the assumptions are reasonable. In real construction, weather, access, labor productivity, and design changes may be correlated, so simulation or scenario analysis may be preferable.

Worked PERT example

An excavation activity has a = 4 days, m = 6 days, and b = 10 days.

Therefore σ = 1 day. If the activity is part of a path with expected duration 40 days and total standard deviation 2 days, the approximate probability of completion within 43 days uses:

A standard normal approximation gives a probability of about 93%, subject to the stated assumptions. This is a planning estimate, not a contractual guarantee.

5. Resources, Calendars, and Constructability

A purely time-based network may require more labor, cranes, work areas, or supervisors than are available. Resource-constrained scheduling recognizes that activities compete for limited resources.

Resource leveling changes activity timing to eliminate or reduce over-allocation, possibly extending project duration. Resource smoothing adjusts activities within available float to reduce fluctuations while attempting to preserve the completion date. Leveling is appropriate when a resource limit is hard; smoothing is appropriate when the limit is flexible and float is available.

The basic resource-loading process is:

1. assign resources and production quantities to activities;
2. calculate resource demand by time period;
3. compare demand with availability;
4. identify over-allocated periods;
5. resequence or split activities where technically permissible;
6. recalculate the critical path and completion date; and
7. document assumptions and residual risks.

Calendars must distinguish working days, shifts, public holidays, weather allowances, curing periods, restricted hours, and access windows. A concrete activity may have a physical curing constraint even if labor is available. A night shift may increase hours but create noise, lighting, fatigue, and community impacts.

Resource decisions should consider productivity, not only headcount. Adding workers to a confined workface can reduce productivity through congestion. Similarly, acceleration that overloads supervision may increase defects and rework.

6. Line of Balance and Repetitive Construction

The line-of-balance (LOB) method is particularly useful for repetitive projects such as apartments, roads, pipelines, tunnels, and utility corridors. It represents production as movement through locations or units over time. A crew’s production line can be described by its rate:

where r is production rate in units per time, Δu is the change in completed units, and Δt is elapsed time. If a crew must complete n units in duration D at a uniform rate, the average required rate is:

These relationships assume reasonably consistent unit sizes, productivity, and work continuity. They are not reliable when unit scope varies substantially or when access is discontinuous.

LOB planning seeks to maintain a safe separation between successive crews. If the plastering crew moves at a rate faster than the electrical crew, it may catch up and create interference. Buffers, crew-size changes, resequencing, or revised production rates may be needed. LOB makes this spatial-temporal conflict visible in a way that a conventional bar chart may not.

7. Milestones, Look-Ahead Planning, and Short-Interval Control

A milestone schedule communicates major contractual and management commitments: notice to proceed, design release, procurement release, structure completion, commissioning, inspections, and handover. Milestones should be objectively verifiable and linked to activities that make their achievement possible.

Look-ahead planning translates the baseline into an executable near-term plan, often covering 3–6 weeks. It identifies:

• activities due to start or finish;
• prerequisite information and approvals;
• materials and equipment;
• labor and workface availability;
• safety and quality requirements;
• constraints and their removal actions;
• responsible persons and promised dates.

A constraint log is essential. “Start blockwork” is not ready merely because it appears on the schedule; drawings, survey control, preceding works, materials, access, and permits must be available. Weekly commitment planning compares promised work with completed work and investigates reasons for variance. This creates a learning cycle rather than a culture of blame.

8. Delay Analysis and Float Ownership

A delay is a time impact that prevents or threatens planned progress. Delay analysis must establish the affected activity, the relevant baseline or contemporaneous plan, the actual event, its cause, its effect on the critical path, and any concurrent causes.

Common classifications include:

• Excusable delay: generally arises from an event for which the contractor is not responsible, subject to contract terms.
• Non-excusable delay: arises from contractor risk under the contract.
• Compensable delay: may entitle the contractor to additional time and money, depending on the contract.
• Concurrent delay: two independent delay causes overlap and both affect completion; its treatment depends on contract wording and governing law.
• Critical delay: delays contractual or forecast completion because it affects the controlling path.
• Non-critical delay: consumes float but does not currently delay completion.

Analysts should avoid relying solely on as-planned versus as-built comparisons. Time-slice analysis, impacted as-planned analysis, time impact analysis, and windows analysis each have different data requirements and strengths. The selected method should suit the contract, records, event timing, schedule quality, and dispute question.

Float is a property of the network at a particular update, not a permanent entitlement owned automatically by one party. Contracts may allocate float explicitly. Otherwise, parties should examine the wording, project practice, and legal principles. Good records include daily reports, delivery records, inspection requests, correspondence, photographs, updated schedules, weather data, and instructions.

9. Schedule Compression

Schedule compression is used when an imposed date is earlier than the calculated completion or when recovery is required. Two principal methods are:

• Crashing: add resources, overtime, additional shifts, alternative equipment, or subcontract capacity to reduce activity duration.
• Fast-tracking: perform activities in parallel that were originally sequential, accepting additional coordination and rework risk.

Crashing is rational only when the activity can actually be shortened and the additional cost is justified. If an activity has normal duration C_n and normal direct cost K_n, and crash duration C_c and crash direct cost K_c, the linear cost slope is:

The units are currency per time unit. This is a planning approximation and assumes a reasonably linear cost-duration relationship between the stated endpoints. It should not be applied to activities whose cost response is nonlinear or whose duration cannot technically be reduced.

Compression should target activities on the current critical path. Shortening a non-critical activity may have no effect on project completion. After each change, the network must be recalculated because another path may become critical.

Compression example

Suppose activity X normally takes 8 days and costs $24,000. It can be crashed to 5 days at $30,000. Its cost slope is:

If X is critical and the project needs two days of recovery, the incremental direct cost is approximately $4,000, provided the crash option is feasible. The decision must also consider overtime premiums, fatigue, safety, quality, inspection capacity, logistics, and possible indirect-cost savings.

Fast-tracking foundation design and construction, for example, may recover time but can create rework if design information changes. A disciplined approval process, design freeze, interface control, and risk allowance are required.

10. Technology, BIM, and AI-Enabled Scheduling

Scheduling software automates calculations, calendars, baselines, resource histograms, progress updates, and scenario comparisons. Building information modeling (BIM) can connect model components to activities, creating 4D visualization. This can reveal access conflicts, crane reach problems, temporary works requirements, and sequencing errors.

Digital tools do not correct poor logic or unreliable data. AI and machine-learning systems can identify patterns in production, forecast delay risk, and compare planned with observed progress from photographs, sensors, or site records. Their outputs require human validation because training data may be incomplete, biased, or poorly matched to the project. Governance should address data ownership, privacy, cybersecurity, auditability, model limitations, and responsibility for decisions. An algorithmic forecast should support—not replace—the project manager’s engineering judgment and contractual duties.

11. Illustrative Case: Recovery of a Repetitive Housing Project

Background

A contractor is constructing 12 identical apartment blocks. The baseline uses four trade crews moving through each block in the sequence: structure, electrical first fix, plastering, and finishes. Practical completion is contractually required in 36 weeks.

Problem

After week 10, structural production is two weeks behind because reinforcement deliveries were unreliable. The electrical crew has begun to catch the structural crew, while plastering has not maintained its planned separation. The monthly update shows four weeks of total float consumed on the controlling sequence.

Analysis

The project team performs a schedule update and a location-based analysis. It finds that the structure crew’s production has fallen from one block every 1.5 weeks to one block every 2 weeks. The delay is critical because all downstream trades depend on structural release. Additional plastering labor would not improve completion because insufficient blocks are ready. Procurement records confirm that delivery reliability, not labor availability, is the primary constraint.

Approach and solution

The team adopts the following recovery plan:

1. establish a second approved reinforcement supplier;
2. release reinforcement packages earlier using a procurement look-ahead;
3. add a small prefabrication crew to reduce site cutting;
4. divide the structural operation into two balanced work zones;
5. resequence electrical work to released zones only;
6. protect a minimum one-block buffer between electrical and plastering crews; and
7. review progress daily using quantities installed, not labor hours alone.

The schedule is re-baselined only through an approved change process; the recovery forecast is kept distinct from the contractual baseline. Safety inspections and reinforcement approval remain hold points and are not removed to gain time.

Outcome

Within four weeks, structural production returns to the required rate. The project recovers approximately two of the four consumed float weeks, while two weeks remain as reduced contingency. The LOB chart shows stable trade separation, and the look-ahead constraint log identifies procurement release dates as leading indicators.

Learning points

The case demonstrates that schedule recovery must address the controlling constraint. Resource addition without workface readiness can increase congestion. Location-based planning is valuable for repetitive work, and the baseline, forecast, and recovery plan must be clearly distinguished. Safety and quality hold points are schedule requirements, not optional delays.

Challenges, Limitations, and Best Practices

Schedules are models, not reality. They simplify weather, uncertainty, human behavior, design development, supply chains, and interactions among trades. Excessive detail creates false precision; insufficient detail prevents control. PERT assumptions may understate correlated risks. CPM may identify a critical path that changes after every update. LOB requires stable production conditions. Software output can appear authoritative even when logic is defective.

Best practice is to:

• build the schedule collaboratively with constructors and trade specialists;
• use a clear WBS, coding structure, calendars, and responsibility matrix;
• validate logic through constructability reviews;
• separate mandatory constraints from preferences;
• use realistic productivity and procurement durations;
• maintain an approved baseline and controlled updates;
• integrate milestones, resources, cost, risk, safety, and quality;
• analyze critical and near-critical paths;
• use look-ahead planning to remove constraints before work is due;
• record actual events contemporaneously; and
• test recovery options for feasibility, cost, safety, quality, and contractual effects.

Chapter Summary

Construction schedule management converts scope into a time-based and resource-aware execution model. WBS activities must have clear deliverables, durations, responsibilities, and logical relationships. Precedence networks permit forward and backward passes, calculation of early and late dates, and identification of total and free float. The critical path is dynamic and must be reviewed as conditions change.

PERT incorporates optimistic, most-likely, and pessimistic estimates, but its probability results depend on assumptions about distributions and independence. Resource leveling addresses hard capacity limits, whereas smoothing uses available float to reduce resource fluctuations. Line-of-balance is especially effective for repetitive, location-based work. Milestones communicate major commitments, while look-ahead planning exposes constraints and converts the baseline into reliable short-term promises.

Delay analysis requires evidence, causation, critical-path impact, and attention to concurrency and float. Schedule compression uses crashing or fast-tracking, but each option must be evaluated for cost, safety, quality, rework, and feasibility. Technology, BIM, and AI can improve visibility and forecasting, yet professional judgment, data governance, and accountability remain essential.

Key Terms

Activity: A defined item of work with a start, finish, duration, and deliverable.

Baseline schedule: The formally approved plan used for comparison and control.

Crashing: Shortening duration by adding resources or increasing expenditure.

Critical path: The controlling sequence of activities with the least schedule flexibility.

Delay: An event or condition that extends or threatens planned progress.

Early finish (EF): Earliest calculated finish time of an activity.

Early start (ES): Earliest calculated start time of an activity.

Float: Time flexibility available within a network.

Free float: Delay possible without delaying a successor’s early start.

Fast-tracking: Overlapping activities that were previously sequential.

Lag: Intentional waiting or time separation between linked activities.

Line of balance: Location-based method for planning repetitive production.

Look-ahead plan: Detailed near-term schedule used to remove constraints.

Milestone: Significant zero-duration event or contractual target.

PERT: Probabilistic technique using three duration estimates.

Precedence relationship: Logical dependency between activities.

Resource leveling: Adjusting timing to resolve resource over-allocation.

Total float: Delay possible without delaying calculated project completion.

WBS: Hierarchical decomposition of project scope into manageable work packages.

Review Questions

Short Answer Questions

1. What is the difference between an activity and a milestone?
2. Define total float and free float.
3. Distinguish resource leveling from resource smoothing.
4. What are the three duration estimates used in PERT?
5. Why should a schedule be updated using a defined status date?

Long Answer Questions

1. Explain how a precedence network is developed from a construction WBS, including logical relationships, lags, calendars, and constraints.
2. Describe the forward-pass and backward-pass procedures and explain how the critical path is identified.
3. Discuss the assumptions and limitations of PERT in construction planning.
4. Compare conventional CPM scheduling with line-of-balance planning for a repetitive building project.
5. Explain how a contractor should evaluate a proposed schedule-compression plan.

Analytical / Application Questions

1. Using the activities in the worked CPM example, calculate the effect of extending activity F by four days. Identify whether project completion changes and explain why.
2. A project has a contractual completion target three weeks earlier than the current forecast. Develop a structured method for selecting crashing and fast-tracking opportunities, including safety, quality, cost, and contractual checks.
3. For a repetitive road project, four crews must complete 20 equal sections in 10 weeks. Explain how you would calculate the required production rate, establish crew separation, identify constraints, and monitor performance using a look-ahead and line-of-balance approach.

Multiple Choice Questions with Answers

Question 1

In an activity-on-node network, what does a finish-to-start relationship normally mean?

A. The successor starts when the predecessor starts

B. The successor starts after the predecessor finishes

C. The successor finishes when the predecessor starts

D. Both activities must finish simultaneously

Correct Answer: B. The successor starts after the predecessor finishes

Question 2

For an activity with early start 6 days and duration 9 days, using the time-zero convention, what is its early finish?

A. 3 days

B. 9 days

C. 15 days

D. 54 days

Correct Answer: C. 15 days

Question 3

Which activities normally form the critical path?

A. Activities with the highest direct cost

B. Activities with the greatest number of resources

C. Activities with zero or least total float controlling completion

D. Activities that begin latest

Correct Answer: C. Activities with zero or least total float controlling completion

Question 4

Using PERT, what is the expected duration when a = 4 days, m = 6 days, and b = 10 days?

A. 5.00 days

B. 6.33 days

C. 7.00 days

D. 10.00 days

Correct Answer: B. 6.33 days

Question 5

What is the principal purpose of resource leveling?

A. To increase every activity’s duration

B. To eliminate or reduce resource over-allocation

C. To remove all project milestones

D. To replace the WBS

Correct Answer: B. To eliminate or reduce resource over-allocation

Question 6

Which planning method is especially suited to repetitive work moving through locations or units?

A. Line of balance

B. Cash-flow forecasting

C. Risk register analysis

D. Stakeholder mapping

Correct Answer: A. Line of balance

Question 7

Which schedule-compression method overlaps activities that were previously sequential?

A. Leveling

B. Smoothing

C. Fast-tracking

D. Free-floating

Correct Answer: C. Fast-tracking

Question 8

A normal activity duration is 8 days at $24,000 and a crash duration is 5 days at $30,000. What is the approximate cost slope?

A. $500 per day

B. $1,000 per day

C. $2,000 per day

D. $6,000 per day

Correct Answer: C. $2,000 per day

Question 9

What is the primary function of a look-ahead plan?

A. To replace the contract

B. To identify and remove near-term constraints

C. To calculate tax liability

D. To conceal changes to the baseline

Correct Answer: B. To identify and remove near-term constraints

Question 10

Why must the critical path be recalculated after schedule changes?

A. Because calendars never affect schedules

B. Because another path may become controlling

C. Because milestones have duration

D. Because float is always constant

Correct Answer: B. Because another path may become controlling