🎯 Course Overview

Master the fundamentals of construction project scheduling. This 8-module course covers everything from basic concepts to advanced techniques including CPM, resource loading, baseline management, and delay analysis.

Prerequisites: Basic project management knowledge

Level: Beginner to Intermediate

📖 MODULE 1: Introduction to Project Scheduling

What is Project Scheduling?

Project scheduling is the process of determining the sequence of activities, their durations, start and finish dates, and resource requirements to complete a project on time and within budget.

1.1 Why Scheduling Matters

Stakeholder	Primary Scheduling Need	Key Questions Answered
Owner/Client	Project completion date	When will I get my building?
Contractor	Resource planning	What crews do I need and when?
Subcontractors	Work window	When do I mobilize?
Consultant/PM	Progress monitoring	Are we on track?
Lender/Bank	Payment schedule	When are draw requests expected?
Procurement	Material lead times	When must I order materials?

1.2 Scheduling vs. Planning

Aspect	Planning	Scheduling
Focus	WHAT needs to be done	WHEN it will be done
Output	Scope, WBS, specifications	Dates, durations, sequences
Question	What activities are needed?	When do they start/finish?
Sequence	Comes first	Follows planning

💡 Key Insight: Planning defines the scope (WHAT); Scheduling defines the timeline (WHEN). You cannot schedule effectively without first completing proper planning.

1.3 The Scheduling Process

Define Activities - Break work into schedulable units

Sequence Activities - Determine dependencies/relationships

Estimate Durations - Calculate how long each takes

Assign Resources - Link labor, equipment, materials

Calculate Schedule - Run CPM, determine critical path

Optimize - Level resources, compress if needed

Baseline - Lock approved schedule for comparison

🏗️ MODULE 2: Work Breakdown Structure (WBS)

The Foundation of Every Schedule

2.1 What is WBS?

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work. It's the foundation upon which the schedule is built.

2.2 WBS Levels

Level	Name	Example
1	Project	Office Building Project
2	Phase	Structure, Finishes, MEP
3	Deliverable	Foundations, Columns, Slabs
4	Work Package	Ground Floor Slab
5	Activity	GF Slab Formwork, Rebar, Pour

2.3 WBS Example: Residential Villa

Villa Project
├── 1.0 Preliminaries
│   ├── 1.1 Site Preparation
│   ├── 1.2 Temporary Facilities
│   └── 1.3 Surveying
├── 2.0 Substructure
│   ├── 2.1 Excavation
│   ├── 2.2 Foundations
│   │   ├── 2.2.1 Foundation Formwork
│   │   ├── 2.2.2 Foundation Rebar
│   │   └── 2.2.3 Foundation Pour
│   └── 2.3 Ground Beams
├── 3.0 Superstructure
│   ├── 3.1 Columns
│   ├── 3.2 Beams
│   └── 3.3 Slabs
├── 4.0 Finishes
│   ├── 4.1 Masonry
│   ├── 4.2 Plastering
│   ├── 4.3 Flooring
│   └── 4.4 Painting
├── 5.0 MEP
│   ├── 5.1 Electrical
│   ├── 5.2 Plumbing
│   └── 5.3 HVAC
└── 6.0 External Works

⚠️ Common Mistake: Creating activities directly without a WBS leads to missing work, poor organization, and difficulty tracking progress. Always build WBS first!

2.4 The 100% Rule

The WBS must represent 100% of the project scope. Each level must equal the sum of its children. Nothing missing, nothing duplicated.

🔗 MODULE 3: Activity Attributes and Relationships

Connecting Activities Together

3.1 Activity Attributes

Each activity in a schedule has key attributes:

Activity ID: Unique identifier (e.g., A1000, STR-001)
Activity Name: Clear, descriptive work description
Duration: Time to complete (working days)
Calendar: Work schedule (5-day, 7-day, custom)
Resources: Labor, equipment, materials
Predecessors: Activities that must complete first
Successors: Activities that follow

3.2 Relationship Types (PDM)

Type	Symbol	Meaning	Example	Usage
Finish-to-Start	FS	B starts when A finishes	Pour concrete → Cure concrete	80-90%
Start-to-Start	SS	B starts when A starts	Excavate → Haul spoil	5-10%
Finish-to-Finish	FF	B finishes when A finishes	Install cables → Terminate cables	5-10%
Start-to-Finish	SF	B finishes when A starts	New system starts → Old system shuts down	<1%

3.3 Lag and Lead

Lag (Positive): Waiting time between activities Example: FS + 7 days = B starts 7 days AFTER A finishes Lead (Negative): Overlap between activities Example: FS - 3 days = B starts 3 days BEFORE A finishes

Common Lag Examples:

Concrete curing: 7-28 days lag
Paint drying: 1 day lag
Material delivery: Lead time lag
Permit approval: Waiting period lag

💡 Best Practice: Use FS relationships whenever possible. They're clearest and easiest to understand. Overuse of SS/FF with lags makes schedules complex and error-prone.

3.4 Constraints

Constraint	Meaning	Example
As Soon As Possible (ASAP)	Start earliest possible	Default for most activities
As Late As Possible (ALAP)	Start latest possible	Delay non-critical work
Start No Earlier Than (SNET)	Cannot start before date	Material delivery date
Finish No Later Than (FNLT)	Must finish by date	Contractual milestone
Must Start On (MSO)	Fixed start date	Scheduled inspection
Must Finish On (MFO)	Fixed finish date	Contractual deadline

⚠️ Warning: Hard constraints (MSO, MFO) override CPM logic and can hide critical paths. Use sparingly and only when truly required by external factors.

⏱️ MODULE 4: Duration Estimation Methods

How Long Will It Take?

4.1 Duration Formula

Duration = Quantity ÷ (Daily Output × Number of Crews) Example: Quantity: 500 m² wall plastering Daily Output: 25 m²/day per crew Crews: 2 Duration = 500 ÷ (25 × 2) = 10 days

4.2 Estimation Methods

Method	Description	Best For	Accuracy
Analogous	Based on similar past projects	Early estimates, limited data	±25-50%
Parametric	Unit rates × quantities	Standard construction work	±10-20%
Bottom-up	Detailed crew/resource calculation	Detailed schedules	±5-10%
Three-point (PERT)	(Optimistic + 4×Most Likely + Pessimistic) ÷ 6	Uncertainty handling	Statistical
Expert Judgment	Experienced professionals' input	Complex/unique work	Varies

4.3 PERT Estimation Example

PERT Duration = (O + 4M + P) ÷ 6 Activity: Install structural steel Optimistic (O): 8 days (everything perfect) Most Likely (M): 12 days (normal conditions) Pessimistic (P): 20 days (problems occur) PERT Duration = (8 + 4×12 + 20) ÷ 6 = 76 ÷ 6 = 12.7 days ≈ 13 days

4.4 Factors Affecting Duration

Labor productivity: Skill level, motivation, experience
Weather: Rain, heat, cold impact outdoor work
Site conditions: Access, congestion, layered work
Equipment availability: Crane, pump, scaffolding
Work hours: Standard day, overtime, shifts
Learning curve: Repetitive work gets faster

🧮 MODULE 5: Schedule Calculation (CPM Basics)

Forward Pass, Backward Pass, Float

5.1 Critical Path Method (CPM)

CPM calculates the longest path through the network - this is the minimum project duration. Activities on this path have zero float and cannot be delayed.

5.2 Key Terms

Term	Meaning
Early Start (ES)	Earliest possible start date
Early Finish (EF)	ES + Duration - 1
Late Finish (LF)	Latest finish without delaying project
Late Start (LS)	LF - Duration + 1
Total Float (TF)	LS - ES (or LF - EF)
Free Float (FF)	Delay without affecting successor ES
Critical Path	Longest path; activities with TF = 0

5.3 Calculation Process

Forward Pass - Calculate Early Start and Early Finish for all activities (left to right)

Identify End Date - The maximum EF is the project completion date

Backward Pass - Calculate Late Finish and Late Start (right to left)

Calculate Float - TF = LS - ES for each activity

Identify Critical Path - Activities with TF = 0

5.4 Simple CPM Example

Activity	Duration	Predecessors	ES	EF	LS	LF	TF	Critical?
A - Excavation	3	-	1	3	1	3	0	✅ Yes
B - Foundation	5	A	4	8	4	8	0	✅ Yes
C - Site Office	2	A	4	5	7	8	3	No
D - Columns	4	B	9	12	9	12	0	✅ Yes

Critical Path: A → B → D (Total: 3 + 5 + 4 = 12 days)

💡 Float Strategy: Use float wisely. Activities with float provide flexibility for resource leveling and risk buffering. Don't consume it unnecessarily.

📊 MODULE 6: Schedule Types and Presentations

Different Views for Different Needs

6.1 Schedule Levels

Level	Name	Detail	Audience	Timeframe
1	Master/Summary	Milestones only	Executives, owners	Project life
2	Summary Schedule	Major phases	Management	Project life
3	Contractor Schedule	All activities	Project team	Project life
4	Detailed Schedule	Crew-level detail	Field supervisors	Phase
5	Look-Ahead	Day-by-day work	Foremen, crews	2-4 weeks

6.2 Presentation Formats

Gantt Chart (Bar Chart)

Most common format. Shows activities as horizontal bars against time axis.

✅ Easy to read and understand
✅ Shows timing at a glance
❌ Doesn't clearly show dependencies
❌ Can become cluttered for large projects

Network Diagram (PDM)

Shows activities as nodes/boxes with arrows for relationships.

✅ Clearly shows dependencies
✅ Good for CPM analysis
❌ Harder to read for non-schedulers
❌ No direct time reference

Milestone Chart

Shows only key dates (diamonds or triangles).

✅ High-level overview
✅ Great for executive reporting
❌ No activity detail

6.3 Two-Week Look-Ahead

The look-ahead schedule is the short-term operational plan used for daily execution:

Filters next 2-4 weeks from master schedule
Adds assignment detail
Tracks daily completion
Identifies and removes constraints
Updated weekly

📈 MODULE 7: Baseline and Progress Tracking

Measuring Performance

7.1 What is a Baseline?

The baseline is the approved, "frozen" schedule against which progress is measured. It represents the original plan and becomes the reference for delay analysis.

7.2 Baseline Rules

✅ Save baseline after schedule is approved
✅ Baseline should be realistic and achievable
✅ Include contractual milestones
✅ Resource-load critical activities
❌ Don't change baseline without formal change order
❌ Don't baseline schedule with negative float

7.3 Progress Update Methods

Method	Description	Pros	Cons
Percent Complete	Estimate 0-100% progress	Simple, quick	Subjective, "90% complete syndrome"
Duration Remaining	Days left to finish	Forces forward thinking	Needs experience
Physical Progress	Measure actual quantities	Most accurate	Time-consuming
0/50/100 Rule	0% until started, 50% when started, 100% when done	Simple, consistent	Less granular

7.4 Key Progress Metrics

Schedule Performance Index (SPI): SPI = Earned Value ÷ Planned Value SPI > 1.0 = Ahead of schedule SPI < 1.0 = Behind schedule Schedule Variance (SV): SV = Earned Value - Planned Value SV positive = Ahead of schedule SV negative = Behind schedule

⚠️ 90% Complete Syndrome: Many activities seem stuck at 90% forever. Always verify physical progress; don't rely solely on percent estimates.

7.5 Monthly Schedule Update Process

Record actual start/finish dates
Update remaining durations
Add any new activities
Update logic if needed
Recalculate schedule (run CPM)
Compare to baseline
Identify variances and causes
Develop recovery plan if behind
Issue update report

⚖️ MODULE 8: Delay Analysis Fundamentals

Understanding Project Delays

8.1 Types of Delays

Type	Responsibility	Time Extension?	Cost Recovery?
Excusable Compensable	Owner-caused	Yes	Yes
Excusable Non-Compensable	No one's fault (force majeure)	Yes	No
Non-Excusable	Contractor-caused	No	No (may owe LD)
Concurrent	Both parties	Usually	Usually not

8.2 Common Delay Causes

Owner-Caused:

Late design/information
Changed scope
Site access issues
Late owner-furnished equipment

Contractor-Caused:

Insufficient resources
Poor coordination
Subcontractor failures
Material procurement issues

Neither Party:

Force majeure (pandemic, war)
Unusual weather
Third-party actions
Unforeseen site conditions

8.3 Basic Delay Analysis Methods

Method	Complexity	When Used
Impacted As-Planned	Simple	Prospective analysis
As-Built Analysis	Medium	After completion
Window Analysis	Complex	Concurrent delays
Time Impact Analysis	Complex	Each event analyzed

💡 Documentation Tips: Always document delays contemporaneously. Keep daily logs, photos, meeting minutes, and correspondence. Good records are essential for successful delay claims.

🎓 Course Quiz

Test your scheduling knowledge:

Q1: What is the most common relationship type (80-90% of activities)?

Finish-to-Start (FS)
Start-to-Start (SS)
Finish-to-Finish (FF)
Start-to-Finish (SF)

Q2: An activity with Total Float = 0 is:

Critical - any delay impacts project end
Non-critical - has flexibility
Cannot be determined

Q3: The baseline schedule should be:

Updated whenever progress changes
Frozen after approval, changed only by formal change order
Created at the end of the project

🎯 Course Takeaways

WBS First: Always build WBS before creating schedule
FS Preferred: Use Finish-to-Start relationships whenever possible
Estimate Carefully: Use parametric/bottom-up methods for accuracy
CPM Matters: Understand forward/backward pass and float
Baseline Is Sacred: Don't change baseline without formal approval
Update Regularly: Weekly look-ahead, monthly full update
Document Delays: Records are essential for claims

🤖 Try Our AI Planner!

Practice scheduling with our AI Planner. It helps you create optimized project schedules with proper activity sequences and resource assignments.

Next Article: Critical Path Method (CPM) - Advanced Course

Construction Scheduling Fundamentals