UFS B.Sc. Construction Management – Project Management Module Notes (PMA/PM)

Project management is one of the core competencies in Construction Management because building projects combine time, cost, quality, procurement, safety, and risk under real constraints. These exam notes focus on the kind of content typically assessed in a UFS B.Sc. Construction Management – Project Management module, including planning tools, scheduling, cost and risk control, contract/procurement concepts, stakeholder management, and project performance measurement. The notes also reflect terminology you will commonly see in South African university materials such as Unisa Project Management study guides and Construction Management/Project Management modules offered by SA universities, while staying aligned to what Construction Management students need for construction projects.

Section 1: Project Fundamentals, Life Cycle, and the Project Management Process

A strong exam performance requires clarity on what a project is, how projects differ from operations, and how the project management life cycle is structured. In construction, this clarity matters because the same “project management steps” must translate into real deliverables: drawings, procurement packages, site activities, inspections, and handover.

What Is a Project in Construction Management?

A project is a temporary endeavor with a defined start and end, undertaken to create a unique output (e.g., a hospital ward, a residential complex, a road section, a warehouse). In construction management, that “unique output” often includes:

A specific design scope (architectural, structural, services)
Regulatory compliance and approvals (municipal, engineering, health & safety)
A procurement approach (design-bid-build, design-build, PPP arrangements)
Physical production on site with constraints (access, working hours, safety, logistics)

Projects differ from operations:

Operations are repetitive and ongoing (e.g., continuous maintenance services).
Projects are one-off and time-bounded (e.g., constructing a substation for 12 months and then commissioning it).

Project Characteristics Exam Questions Often Test

Examiners commonly expect you to recognize and apply project characteristics to scenario questions. Key characteristics include:

Uniqueness – even standardized building types have differences (site conditions, ground conditions, design changes).
Temporary nature – the “end” is often defined by completion, commissioning, or final handover.
Constraints – most construction projects are constrained by:
- Time (programme deadline)
- Cost (budget/cost ceiling)
- Quality/specifications (tolerances, materials, workmanship standards)
- Scope (what is included/excluded)
- Risk (uncertainty in design, procurement, labour availability, and site conditions)
Stakeholders – owners, designers, contractors, consultants, authorities, communities.

Project Life Cycle: Conceptual → Delivery → Closeout

A typical project life cycle can be expressed in phases such as:

Initiation
- Business case justification (why this project?)
- Project charter and initial feasibility
Planning
- Scope definition and WBS (Work Breakdown Structure)
- Schedule development
- Resource planning
- Cost budgeting and baseline
- Risk planning and controls design
- Procurement planning
Execution/Delivery
- Procurement and contracting
- Construction production (site work)
- Quality assurance and quality control
- Communication and stakeholder engagement
Monitoring & Controlling
- Track progress and performance vs baseline
- Manage changes (scope, cost, time)
- Monitor risks and implement responses
Closing
- Commissioning and handover
- Final documentation, as-builts, defects liability processes
- Lessons learned and project evaluation

A common exam angle is to ask students to match activities to phases. For example, “preparing a cost baseline” is planning; “issuing work instructions on site” is execution; “comparing actual costs to budget using earned value” is monitoring and controlling.

The “Project Management Knowledge Areas” Mindset

Even if your module uses a local scheme rather than PMBOK, the logic is similar. Construction projects require integration of:

Scope management (WBS, requirements, acceptance)
Time/schedule management (networks, critical path, milestones)
Cost management (estimation, budgeting, cost control)
Quality management (standards, QA/QC, inspections)
Risk management (identification, analysis, response)
Procurement management (tenders, subcontracting, contracts)
Stakeholder communication (reporting, meetings, approvals)
Integration management (change control, baseline management)

Integration and Baselines: Why They Matter in Construction

A recurring construction exam theme: baselines are reference points. When planning, you develop a baseline plan for:

Scope baseline – approved scope statement and WBS
Schedule baseline – approved programme with milestones
Cost baseline – budget and cost accounts

Monitoring and controlling means comparing actual performance to these baselines and then deciding how to respond (e.g., corrective actions or change requests). In practice, when you revise a programme due to changed conditions, you do not “pretend” the baseline was never wrong—you manage revisions properly.

Example Scenario (Exam-Type)

Scenario: A municipality plans to construct a community hall. The project budget is fixed, the deadline is set for a community event, and design changes are expected due to stakeholder input.

What to do in initiation:

Confirm the business need (community hall)
Define preliminary scope boundaries (what rooms? parking? basic services?)
Identify major risks (late design approvals, contractor procurement delays)

What to do in planning:

Build a WBS separating enabling works, civil works, building works, MEP (mechanical/electrical/plumbing), external works
Develop schedule logic (foundation depends on geotechnical report)
Set budget baseline with cost codes for each work package
Plan risk responses (e.g., contingency for late materials approval)

What to do in controlling:

Track variance (cost and schedule)
Manage change control if stakeholders add new features
Update risks if geotechnical conditions change

Section 2: Scope Definition, WBS, Scheduling Networks, and Critical Path

This section covers core tools frequently examined in UFS-style Construction Management project management exams: WBS, scope control, activity definition, and scheduling with networks and critical path. Many students know definitions but struggle to apply them to numerical or scenario questions. These notes provide both.

Scope Management: From Requirements to Work Packages

Scope management answers: What exactly is included in the project, and how do we ensure acceptance?

Key Scope Outputs

Scope statement – what the project will deliver and major constraints.
WBS (Work Breakdown Structure) – hierarchical decomposition of deliverables.
Activity list – specific tasks derived from WBS work packages.
Requirements documentation – quality and functional expectations.

In construction, scope frequently expands due to:

Design clarifications
Client-driven changes
Code/regulatory requirements
Unforeseen site constraints (e.g., services relocation)

This creates a practical need for change management (covered later), but exam questions often start with “scope definition” and then lead into “what happens when scope changes?”

Work Breakdown Structure (WBS): How It Is Built

A WBS is a structured decomposition of project deliverables into manageable components. A solid WBS is:

Deliverable-oriented (not just task-oriented)
Hierarchical (e.g., Level 1 → Level 2 → Level 3)
Mutually exclusive and collectively exhaustive (MECE) when possible
Mapped to cost and schedule accounts

Typical WBS Format for Construction

A WBS often groups construction work by:

Building elements (structure, finishes, services)
Disciplines (civil, structural, architectural, MEP)
Work packages (procurement and installation scopes)
Location zones (Zone A, B, C on a site)

Example WBS (simplified):

Level 1: Project (Community Hall)
- Level 2: Civil Works
  - Level 3: Site clearing
  - Level 3: Earthworks and compaction
  - Level 3: Drainage
- Level 2: Structural Works
  - Level 3: Foundations
  - Level 3: Columns and beams
  - Level 3: Slabs
- Level 2: Architectural Works
  - Level 3: Walls and partitions
  - Level 3: Doors and windows
  - Level 3: Internal finishes
- Level 2: MEP Works
  - Level 3: Electrical reticulation
  - Level 3: Lighting and power
  - Level 3: Plumbing and sanitation
- Level 2: External Works
  - Level 3: Parking and paving
  - Level 3: Landscaping

From WBS to Schedule Activities: Activity Definition

After WBS creation, you define activities that represent the work needed to deliver each work package.

Activity Attributes Commonly Required in Exams

Activity ID (e.g., A, B, C…)
Activity description (clear scope of the task)
Duration (in days/weeks)
Predecessor relationships (what must finish before the task starts)
Resources (labour/equipment) and constraints
Assumptions and constraints (e.g., “cannot start until inspection approval”)

Scheduling Techniques: Networks and Dependencies

Construction programmes are usually logic-driven. The most common network structures assessed are:

Precedence diagrams (activity-on-node logic)
Forward pass to compute earliest start/finish times
Backward pass to compute latest start/finish times
Float/slack calculation (buffer time without affecting project completion)

Precedence Relationships (Exam-Friendly)

You need to know and interpret relationships like:

Finish-to-Start (FS): Task B cannot start until Task A is finished.
Start-to-Start (SS): Task B can start when Task A starts (less common in basic exam problems).
Finish-to-Finish (FF): Task B cannot finish until Task A finishes.
Start-to-Finish (SF): Usually not used in standard construction logic.

Most first-stage exam questions use FS relationships.

Forward and Backward Pass: The Core Critical Path Method

To find the critical path:

Step 1: Forward Pass (Earliest Times)

Earliest Start (ES) for the project start is 0 (or the chosen project date baseline).
Earliest Finish (EF) = ES + Duration
ES for an activity equals the maximum EF among its immediate predecessors (for FS relationships).

Step 2: Backward Pass (Latest Times)

Project completion Latest Finish (LF) equals the earliest finish time of the final activities (project duration).
Latest Start (LS) = LF − Duration
LF for an activity equals the minimum LS among its immediate successors.

Step 3: Float (Slack)

Total Float = LS − ES = LF − EF
Critical activities have zero total float (or near zero within rounding).

Numerical Example (Network + Critical Path)

Consider a simplified programme (all relationships are FS):

Activity	Duration (days)	Predecessor(s)
A	5	—
B	3	A
C	4	A
D	2	B, C
E	6	D
F	3	C
G	2	F, D

Goal: Find project duration and critical path.

Forward Pass

A: ES=0 → EF=5
B: ES=5 → EF=8
C: ES=5 → EF=9
D: predecessors B and C → ES=max(8,9)=9 → EF=11
E: predecessor D → ES=11 → EF=17
F: predecessor C → ES=9 → EF=12
G: predecessors F and D → ES=max(12,11)=12 → EF=14

Final activities here are E and G, so project completion is max(EF)=max(17,14)=17 days.

So project duration = 17 days.

Backward Pass

Set completion time = 17.

E: LF=17 → LS=17−6=11
G: LF=17 → LS=17−2=15

Now move backwards:

D is predecessor of E and G.
- From E: LS for D via E means D’s EF must be ≤ ES/E start? In standard CPM: for D, LF equals minimum LS of its successors.
- Successors: E and G.
- D’s successors start times:
  - E’s LS = 11
  - G’s LS = 15
- So D: LF = min(11,15) = 11 → LS = 11−2=9
F predecessor of G:
- G’s LS = 15
- F: LF = 15 → LS = 15−3 = 12
C predecessor of D and F:
- Successors: D (LS=9) and F (LS=12)
- C: LF = min(9,12)=9 → LS = 9−4=5
B predecessor of D:
- D’s LS = 9
- B: LF = 9 → LS = 9−3=6
A predecessor of B and C:
- Successors: B (LS=6) and C (LS=5)
- A: LF = min(6,5)=5 → LS = 5−5=0

Float and Critical Path

Compute total float = LS − ES.

A: LS=0 ES=0 → float 0 (critical)
B: LS=6 ES=5 → float 1 (non-critical)
C: LS=5 ES=5 → float 0 (critical)
D: LS=9 ES=9 → float 0 (critical)
E: LS=11 ES=11 → float 0 (critical)
F: LS=12 ES=9 → float 3 (non-critical)
G: LS=15 ES=12 → float 3 (non-critical because E finishes later)

Critical path: A → C → D → E
Project duration: 17 days

This kind of answer structure (forward pass table + backward pass reasoning + float + path) is exactly how exam scripts earn marks.

Activity Durations and Real Construction Context

In exams, durations are given. In real life (and sometimes in scenario questions), durations depend on:

Labour productivity
Crew availability
Resource constraints (e.g., one crane)
Work sequencing and access

A common pitfall: students treat “critical path” as “most expensive.” Critical path is about time logic, not cost or risk. A non-critical path may still be high-risk or expensive due to procurement lead times or rework likelihood.

Programme Compression and Buffer Thinking

Some modules introduce:

Crashing (reducing duration by adding resources)
Fast-tracking (starting later activities sooner)
Time buffers (strategic and management reserves)

Exams may ask: “Which method is safer and why?” Typical reasoning:

Crashing increases cost and can reduce quality if overworked.
Fast-tracking can increase risk if interfaces are not ready.

Section 3: Cost Estimation, Budgeting, Earned Value, and Cost Control

Project cost management in construction is heavily tested because students must link planning to performance measurement. This section covers estimating logic, budgeting structure, and earned value concepts (EVM) including key indices.

Cost Management Overview

Cost management in a project generally includes:

Cost estimation – predicting likely costs
Cost budgeting – allocating estimates to work packages and time periods
Cost control – monitoring actual vs plan, and analyzing variances
Change control – handling scope/time-cost impacts of changes

A crucial exam concept: cost planning must align with the WBS. If the WBS does not map to cost accounts, earned value and variance analysis becomes unreliable.

Estimating Methods in Construction Management

1) Analogous Estimating

Use historical data from similar projects to estimate cost quickly. Example uses:

Early feasibility stages when scope is not fully detailed.
Quick screening of project viability.

Strength: fast
Limitation: depends on similarity; may be inaccurate if site conditions differ.

2) Parametric Estimating

Uses statistical relationships (e.g., cost per square meter or cost per linear meter of service) derived from historical data.

Example:

Suppose historical database indicates R 2,800 per m² for a specific standard finishing level in community facilities.
If the project floor area is 800 m²:
- Estimated cost = 800 × 2,800 = R 2,240,000 (at that historical cost basis)

Strength: efficient when credible parameters exist
Limitation: requires careful parameter relevance.

3) Bottom-Up Estimating (Most Exam-Expected for Construction)

Estimate each work package and sum to project total:

Materials
Labour
Equipment
Subcontractors
Overheads and preliminaries (where applicable)

Bottom-up is typically used once design is sufficiently developed (bill of quantities available).

Budgeting: Cost Accounts and Time Phasing

Budgeting converts estimates into a time-phased baseline.

Cost Breakdown Structures

Budgets in construction often reflect:

WBS cost accounts
Cost categories (materials, labour, equipment, subcontract)
Time periods (monthly budgeted spend)

A credible budget baseline supports earned value tracking.

Earned Value Management (EVM): Core Calculations

EVM helps answer three questions:

How much work was planned by now? (Planned Value, PV)
How much work is actually completed? (Earned Value, EV)
How much did it cost to get the completed work done? (Actual Cost, AC)

Definitions

PV (Planned Value): budgeted cost of work scheduled by the status date
EV (Earned Value): budgeted cost of work actually completed
AC (Actual Cost): actual cost incurred for the work performed

From these:

Schedule Variance (SV) = EV − PV
Cost Variance (CV) = EV − AC
Cost Performance Index (CPI) = EV / AC
Schedule Performance Index (SPI) = EV / PV
Estimate at Completion (EAC) and Estimate to Complete (ETC) (depends on assumptions)

Numerical Example (EVM in an Exam Format)

Assume at a particular reporting date:

PV = R 1,200,000
EV = R 1,050,000
AC = R 1,180,000

Calculate:

SV = EV − PV = 1,050,000 − 1,200,000 = −R 150,000
→ Negative means behind schedule.
CV = EV − AC = 1,050,000 − 1,180,000 = −R 130,000
→ Negative means over budget.
CPI = EV / AC = 1,050,000 / 1,180,000 ≈ 0.89
→ For every rand spent, only 0.89 rand of value was earned (cost inefficiency).
SPI = EV / PV = 1,050,000 / 1,200,000 = 0.875
→ Progress is 87.5% of what was planned.

This is a typical “compute indices and interpret” exam question.

Interpreting EVM Results in Construction

EVM tells you the performance status, but you must interpret the “why”:

EV < PV (SV negative): work behind plan; possible reasons:
- procurement delays (materials not delivered)
- labour productivity issues
- design approval delays
- site access restrictions
EV < AC (CV negative): cost overrun for the work done; possible reasons:
- rework and defects
- inefficiencies due to changed sequence
- overtime and premium rates
- poor productivity and equipment downtime

Importantly: it’s possible to have:

Behind schedule but under budget
Ahead of schedule but over budget

Examiners often ask which combinations indicate which types of problems.

EAC and EOT/Completion Logic (Typical Exam Approach)

A simplified approach sometimes used in exams:

If current cost performance is expected to continue:
EAC = BAC / CPI
where BAC = Budget at Completion (total project budget)

Example:

Suppose total budget BAC = R 4,000,000
CPI = 0.89 (from earlier)
EAC = 4,000,000 / 0.89 ≈ R 4,494,382

If actual performance is expected to improve, a different EAC formula may be applied (e.g., incorporate schedule performance). But unless the module specifies it, many exam answers accept the “BAC/CPI” logic as the baseline.

Cost Control Mechanisms in Construction

Cost control requires procedures, not just calculations. Typical control mechanisms include:

Approval thresholds for spending and variations
Procurement control (purchase orders, supplier contracts)
Change control system (documented impact assessment)
Monthly cost reporting with EVM metrics
Forecasting (latest EAC estimate, contingency usage)
Review of productivity and unit rates
QA/QC inspections to reduce rework (which drives cost overrun)

Practical Example: Unit Rates and Rework

Consider a finishing activity where the planned unit rate is:

Labour productivity: 20 m² per day
Cost per m² budget: R 250

If poor workmanship leads to rework and productivity drops to 12 m² per day:

Labour cost per earned m² increases
EV may remain lower than expected (less completed value)
AC increases due to additional labour/mobilization and rework materials

EVM captures the mismatch: EV versus AC and PV.

Section 4: Project Risks, Stakeholders, Communication, and Change Control

Construction projects are dynamic systems. Risk affects schedule and cost directly; stakeholders influence scope and constraints; and change control is the “governance mechanism” that prevents uncontrolled scope creep.

Risk Management Basics: Identifying, Analyzing, Responding

A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives.

Risk Management Cycle

Risk identification
- brainstorm with team
- review past projects
- check design and procurement assumptions
Qualitative analysis
- probability vs impact matrix
Quantitative analysis (where required)
- expected monetary value, simulation, sensitivity
Risk response planning
- avoid, mitigate, transfer, accept, or exploit (positive risks)
Implementation and monitoring
- trigger conditions, risk owners, update risk register

Common Construction Risks Examiners Expect

Technical and design risks

incomplete design at tender
changes in specifications
clashes between structural and services drawings

Procurement and contractual risks

long lead items (elevators, transformers, switchgear)
supplier delays
subcontractor capacity and performance issues

Site and operational risks

ground conditions and differing geotechnical findings
weather disruptions
access constraints and logistics failures

Safety and compliance risks

accidents and lost time injuries (LTIs)
non-compliance with regulations leading to stoppages

Risk Register Structure

A high-scoring answer typically includes a risk register with columns like:

Risk ID
Risk description
Cause
Probability (P)
Impact (I) (time, cost, quality)
Risk rating (e.g., P×I)
Response strategy
Trigger/early warning indicators
Risk owner

Qualitative Risk Matrix Example (Conceptual)

Probability categories might be:

Low, Medium, High

Impact categories:

Low, Medium, High

A common risk matrix yields ratings like:

High probability + high impact = “Top risks”

In exams, if you’re asked “which risks are highest priority?” choose those with:

highest probability
highest impact
or high impact even if probability is moderate

Stakeholder Management: Mapping Power/Interest

Construction projects involve many stakeholders:

client/owner
main contractor
consultants (architectural, engineering)
local authority
subcontractors
end users
community representatives

A common technique is the power/interest grid:

High power, high interest: manage closely, communicate frequently
High power, low interest: keep satisfied
Low power, high interest: keep informed
Low power, low interest: monitor

Communication Management: What to Report and How Often

In a UFS-type construction management context, communication is assessed through practical reporting structures:

Daily site reports (progress, safety incidents, manpower)
Weekly progress meetings (programme status, constraints)
Monthly cost reports (forecasting, EVM metrics)
Quality reports (inspection outcomes, NCRs—non-conformance reports)
Design coordination meetings (RFIs—requests for information, drawing issues)

An exam may ask: “What should be included in a project status report?”
A good answer usually includes:

progress versus programme baseline
issues requiring decisions
risks and mitigation actions
procurement status (materials lead times)
safety status and incidents
change log summary

Change Control: Managing Scope Creep

In construction, changes happen due to:

design development
differing conditions
client requests
regulatory changes

A disciplined change control process ensures:

changes are documented
impacts on time/cost/quality are assessed
approvals are obtained
baselines are updated only when authorized

Typical Change Control Steps

Change request submitted
Impact assessment
- cost impact (materials, labour, subcontract)
- time impact (schedule logic, critical path risk)
- quality impact (specifications and approvals)
Evaluation and options
- accept/implement as requested
- redesign alternatives
- reject or defer
Approval authority review
Update documents
- revised drawings/specs
- updated schedule and budget baselines if approved
Communicate decision
Record and close change

Example: How Changes Affect the Critical Path

If a change affects an activity on the critical path, project completion moves (unless mitigation offsets it). If a change affects a non-critical activity, it may not change completion, but it can still cause resource contention or future delays.

Exam-ready reasoning:

Identify whether changed activity has zero float (critical).
Estimate added duration due to change.
Recalculate critical path if logic changes or float consumed.

Dealing With Conflict and Decision Delays

Construction often suffers from “decision bottlenecks”:

client approval delays
consultant review delays
subcontractor submissions incomplete

Stakeholder communication must reduce these delays by:

defining response times in contract
setting document control and RFI procedures
using integrated master schedules and escalation pathways

Section 5: Contracts, Procurement, Procurement Schedules, Quality Integration, and Exam-Style Project Controls

Project management in Construction Management is inseparable from procurement and contracts. Your schedule depends on what you procure and when; your cost depends on contract terms; and your quality depends on how you specify, inspect, and accept deliverables. This section integrates project controls in a construction-specific way.

Procurement Planning: Make vs Buy Decisions

Procurement decisions include:

which work packages to subcontract
which materials to purchase directly
whether to use a framework supplier list
lead-time planning

Procurement Time Risk

Lead times drive schedule risk. For example:

electrical switchgear may require factory lead time
steel fabrication may have shop drawings approval timelines
bespoke items depend on design finalization

Exam questions often use a scenario like:

“Switchgear delivery lead time increases from 8 weeks to 12 weeks; what happens to the programme?”

Your answer should:

Identify successor activities affected (installation, testing)
Determine if impacted activity is critical
Calculate new completion if enough data exists
Suggest mitigations (expedite shipping, alternative suppliers, resequencing where possible)

Contract Types (Conceptual Exam Coverage)

While your module may not require deep legal interpretation, contract understanding is common in project management exams. Key contract characteristics include:

Lump sum (fixed price)
- risk for cost overruns on contractor
- strong baseline and change control needed
Re-measurement (unit price)
- payment based on measured quantities
- requires measurement discipline and consistent quantities
Design-build
- contractor integrates design and build
- reduces design handover gaps but requires coordination
Time and Materials
- used in uncertain scopes
- requires tight cost monitoring

Why Contract Structure Matters for Project Management

Contract terms influence how you manage variation orders
Contract payment milestones influence cashflow and procurement
Contractual completion and practical completion definitions influence closing processes

Quality Management Integration: QA/QC and Acceptance

Quality in construction is not only about workmanship; it also affects cost and schedule due to rework.

QA versus QC (Exam-Friendly Distinction)

Quality Assurance (QA): systems and processes to ensure quality (training, method statements, audits)
Quality Control (QC): inspections and checks on outputs (tests, checklists, material approvals)

An exam scenario might say:

“Concrete strength test results are below specification.”
Your response should address:

immediate action (stop/hold affected work)
investigation and non-conformance process
repair/replacement plan
schedule impact (critical path risk)
cost impact (extra works and potential claims)

Procurement Schedules: Aligning Buy and Build

A procurement schedule links:

procurement activities (tender, purchase order, submittal, delivery)
installation activities
required lead times

Example Procurement Logic for One Package

For an electrical installation package:

submit shop drawings (depends on approved design)
confirm equipment selection
order materials (switchgear, cables, accessories)
receive deliveries and inspect
install and test

If design finalization is delayed, procurement of switchgear can be delayed; delays propagate forward.

Project Controls: Reporting, Forecasting, and Corrective Actions

Project controls are what you do when reality differs from plan.

Controls Toolkit

schedule tracking (milestones, progress percentages)
EVM (PV, EV, AC)
cost forecasting (EAC, ETC)
risk register updates
quality reports and NCR tracking
change log tracking

Corrective Action Categories

schedule recovery (resequencing, overtime, additional shifts)
cost recovery (value engineering, productivity improvements)
quality recovery (method statement improvements, rework planning)
risk response (contingency activation, supplier replacement)

A good exam answer includes: what you do now plus how you prevent recurrence.

Integrated Example: Putting It All Together (Mini Case)

Scenario: The construction of a community hall has the following structure:

Civil works (foundations and drainage)
Structural works (columns, beams, slabs)
Architectural works (finishes)
MEP works (electrical and plumbing)
External works (paving and landscaping)

Assume early progress is behind plan because:

structural steel shop drawings were approved late
a long-lead MEP item (electrical switchgear) delivery was delayed
weather disrupted earthworks for 5 working days

Step-by-step exam style response

Update schedule status
- identify impacted activities
- determine whether steel erection or switchgear installation sits on the critical path
Quantify impacts
- revise PV and EV based on completed work
- compute EV, AC, and variances
Update EVM indices
- determine CPI and SPI
Assess cost consequences
- identify additional cost drivers: overtime, remobilization, storage charges
Implement corrective actions
- resequence non-critical work to keep productivity
- expedite deliveries (where contract allows)
- activate contingency for weather disruption
Update risk register
- add a risk like “late design approval persists” if it is continuing
Change control
- if scope is affected (e.g., client requests alternative finish level), ensure documented change request and impact assessment
Quality and safety
- ensure quality inspections continue despite schedule pressure
- update safety plan to reflect changed work sequencing

This mini case ties procurement, schedule logic, earned value, risk, change control, and quality together—exactly what exam questions often test.

Lessons Learned and Closing: Ensuring Knowledge Transfer

Closing is frequently neglected by students but can earn marks in theory questions.

Key closing tasks include:

ensure all deliverables are complete and accepted
process defects liability period documentation
finalize claims/variations and reconciliations
conduct a lessons learned workshop
update templates and historical data for future estimating

A quality lessons learned process improves future estimating accuracy, which improves cost baselines and reduces future earned value variance.

Consolidated Exam Checklist (Rapid Revision)

Use this section as a final revision tool. It is intentionally structured like a marks-earning checklist.

1) In any project scenario question, identify:

project phases (initiation/planning/execution/controlling/closeout)
baseline elements (scope, time/schedule, cost)
stakeholder influences and decision bottlenecks

2) For scheduling / CPM questions, always show:

Activity list and durations
Predecessors (logic)
Forward pass (ES/EF)
Backward pass (LS/LF)
Float calculations
Critical path and project duration

3) For EVM questions, always compute and interpret:

PV, EV, AC
SV = EV − PV (schedule)
CV = EV − AC (cost)
CPI = EV/AC
SPI = EV/PV
EAC logic if BAC and assumption are provided

4) For risk and change questions, include:

risk register with probability and impact logic
response strategy (avoid/mitigate/transfer/accept)
trigger/early warning
change control steps (request → impact assessment → approval → update baselines → communicate)

5) For procurement and quality integration questions:

link procurement lead times to schedule activities
connect contract type to variation and cost control expectations
emphasize QA/QC and acceptance processes

Summary

These UFS B.Sc. Construction Management Project Management module notes covered the full project management lifecycle with construction-focused emphasis: scope and WBS, network scheduling and critical path, cost estimation and budgeting, earned value performance measurement, risk and stakeholder management, change control, and the integration of procurement, contracts, quality, and project controls. With the included exam-style numerical logic (CPM forward/backward pass and EVM variance/index calculations) and scenario-based reasoning (how changes and risks propagate through time and cost), these notes are structured to help you write coherent, marks-focused answers under exam conditions.