UJ BSc (Construction Project Management) Honours Notes (Unisa-Style Exam Guide)

The UJ BSc in Construction Project Management Honours is a specialist postgraduate programme aimed at building advanced competence in planning, procurement, contract administration, project controls, and construction management leadership. These exam notes are designed to help you answer the kinds of questions typically found in South African university assessments: scenario-based problems, theoretical definitions linked to practice, and structured argumentation using frameworks like PMP/PMBOK logic, contract principles, and risk governance. The guide also aligns with the study habits of South African students (e.g., Unisa-style explanation depth and CUT/TUT-style applied problem solving) while keeping the focus strictly on Construction Project Management Honours outcomes.

1. UJ Honours Research, Dissertation Logic, and Methodology (Academic Writing + Exam-Style Questioning)

At Honours level, many modules across South Africa—whether at UJ, CUT, TUT, or similar institutions—evaluate not only what you know, but how you use knowledge. That means: disciplined academic writing, correct research design, and the ability to justify choices (sampling, data collection, analysis) in a way that would withstand a viva or a panel review.

1.1 Research Problem, Aim, Objectives (and the difference between “topic” and “problem”)

A common exam marker expectation is that you distinguish:

Topic: the broad subject area (e.g., “Project risk management in building construction”).
Research problem: the gap or failure in practice/knowledge that motivates the study (e.g., “Despite widespread use of risk registers, contractors still experience schedule overruns; it is unclear which risk assessment practices predict performance improvements.”)
Aim: a single sentence stating what the study intends to achieve (e.g., “To determine how risk assessment quality influences schedule performance in building construction projects in Gauteng.”)
Objectives: measurable sub-goals that operationalise the aim.

A strong set of objectives at Honours must map to your methods. For example, if your research design is mixed methods (questionnaires + interviews), then at least one objective should explicitly target each data stream.

Example objective set (scenario-ready):

To assess current risk management practices (risk identification, analysis, response planning, monitoring) using a structured questionnaire.
To determine the relationship between perceived risk assessment maturity and schedule performance using correlation/regression (or structured scoring with statistical tests).
To explore, through semi-structured interviews, the reasons risk register updates may not translate into improved control on site.

In an exam, if asked “Explain the difference between aim and objectives,” you should include:

Aim = overall intent; objectives = specific measurable steps.
Objectives should be linked to variables, indicators, or measurable constructs.

1.2 Research approach: quantitative, qualitative, and mixed methods (with defensible choices)

Honours research frequently requires you to justify why you selected a method. Typical decision logic:

Use quantitative when you aim to test relationships between variables and generalise patterns.
Use qualitative when you aim to explain “why” and “how” practices operate in context.
Use mixed methods when you need both breadth and depth.

Defensible justification example (exam-style):

Quantitative component identifies statistical relationships (e.g., risk assessment maturity score vs. schedule variance).
Qualitative component explains mechanisms (e.g., why contractors treat risk registers as compliance documents rather than decision tools).

Counter-argument you must address

Examiners often look for awareness of limitations:

Quantitative limitation: self-report bias (participants may overestimate compliance).
Qualitative limitation: limited generalisability (small sample).
A good answer acknowledges these limitations and suggests mitigation:
Use triangulation (compare questionnaire results with document analysis like risk registers).
Maintain audit trails for qualitative coding.

1.3 Sampling strategies: probability vs non-probability (and sample size logic)

South African university exam questions often ask you to define sampling types and advise which is appropriate. At Honours level, you also need logic for sample size.

Common sampling options in Construction Project Management Honours

Probability sampling (e.g., simple random, stratified, cluster): supports generalisation.
Non-probability sampling (e.g., purposive, quota, snowball): supports depth and relevance.

Purposive sampling is frequently used for interviews with:

project managers,
professional team members (architects/engineers),
quantity surveyors,
contracting managers,
site supervisors,
HSE managers,
procurement officers.

A plausible interview sample size for Honours qualitative work in this field is often 10–20 participants, but justification matters more than the number:

Stop at thematic saturation (new interviews stop producing substantially new themes).

For questionnaires, sample size depends on population size and expected effect sizes. A common practical approach is:

Target at least 100–200 responses if your analysis includes regression or multiple constructs.
If resources are limited, you can still do analysis with fewer responses, but you must be cautious about statistical power and report confidence carefully.

1.4 Data collection instruments: questionnaires, interview guides, document analysis

Questionnaire design principles

A strong construction project management questionnaire usually operationalises constructs such as:

risk management maturity (likert-scale items),
stakeholder communication effectiveness,
procurement planning quality,
contract administration effectiveness,
schedule performance perception or measured variance,
claims management effectiveness,
change control discipline.

Example Likert scale items (risk assessment maturity):

“Risk identification is performed at the earliest planning stage.”
“Risks are analysed using both qualitative and quantitative methods where appropriate.”
“Response plans are assigned to responsible persons with deadlines.”
“Risk register updates occur at regular reporting intervals.”

Interview guide principles

An interview guide should avoid leading questions and should align to your research objectives. Example structure:

Describe your role in risk management on projects.
Walk me through your process from risk identification to monitoring.
What documents or tools are used (e.g., risk registers, workshops, bow-tie diagrams)?
Where does the process break down in practice?
How do schedule overruns get linked to risk decisions after the fact?

Document analysis

In construction research, document analysis can include:

risk registers,
project control reports,
meeting minutes,
contract variation registers,
monthly progress reports,
claims correspondence logs,
procurement schedules.

This is powerful because it reduces overreliance on perception-based self-reporting.

1.5 Data analysis methods (qualitative coding, quantitative tests)

Quantitative analysis (exam-ready)

Common techniques include:

Descriptive statistics: mean, standard deviation, frequency tables for each construct.
Reliability testing: Cronbach’s alpha for multi-item scales.
Validity checks: factor analysis (exploratory or confirmatory) if appropriate.
Association tests: Pearson/Spearman correlations.
Regression: predicting schedule variance from risk maturity and other controls.

A high-quality exam answer explains:

why a test is appropriate for your data type (interval vs ordinal; normality assumptions),
what the results mean in project management terms,
limitations of inference.

Qualitative analysis (coding and themes)

Qualitative analysis often uses:

open coding (initial codes),
axial/structural coding (linking codes into categories),
thematic analysis (themes with supporting quotes and examples).

A strong exam answer must include:

how you ensure trustworthiness (triangulation, member checking, audit trail),
how you prevent bias (reflexivity, consistent coding process).

1.6 Academic integrity and referencing logic (what exam markers expect)

Construction research uses many standards and definitions (contracts, risk, governance). Examiners expect:

consistent citation style (often Harvard or institutional style),
accurate bibliographic details,
no “patchwork” plagiarism (especially common when importing online contract clause explanations).

Even if the course is not explicitly “law,” contract definitions must be correctly cited—because construction claims and dispute analysis are contract-sensitive.

2. Construction Project Management Foundations at Honours Level: Scope, Schedule, Cost, Quality, and Integration

Honours assessments in construction project management almost always require you to integrate theory with technical project controls. You must show not only definitions but also how decisions flow from one knowledge area to another: scope drives cost; schedule affects procurement; risk influences all.

2.1 Project lifecycle, phases, and governance structures (from concept to close-out)

A typical construction project lifecycle includes:

Initiation/Concept: feasibility, stakeholder analysis, preliminary scope.
Design development: concept design, detailed design, estimates refine.
Procurement: tender documentation, evaluation, award.
Construction execution: planning for delivery, site operations, progress controls.
Commissioning and close-out: testing, handover, defects correction, final account.

At Honours level, exam markers want you to describe governance:

who makes decisions,
what the reporting mechanisms are,
what approvals are required (variations, rebaselining, extensions of time).

Example governance map (practical):

Project Steering Committee approves budget and strategic changes.
Project Manager owns schedule and cost control processes.
Contract administrator reviews variations and supports claims.
Quantity Surveyor supports cost forecasts and final accounts.
Health & Safety Officer enforces compliance and stops-work where required.

2.2 Scope management: WBS, deliverables, and change control discipline

Scope at Honours is not merely “what you build.” It is:

deliverables definition,
breakdown into work packages,
boundaries for accountability.

Work Breakdown Structure (WBS)

A WBS typically breaks work by:

major construction disciplines (civil, structural, MEP, finishing),
location (floors/blocks),
or phase (earthworks, concrete works, installation).

A WBS is the backbone for:

scheduling (activities derived from work packages),
budgeting (cost codes),
quality control (inspection points aligned to deliverables),
risk identification (risks mapped to work packages).

Change control

Change control must be systematic:

Identify change request (scope, design, method, regulation).
Record impact assessment.
Seek approval (client/engineer depending on contract).
Update baseline (scope, schedule, cost) if approved.
Communicate changes to implementers.

Common exam trick: If asked “Why do scope changes cause schedule overruns?”, your answer should not be generic. Provide mechanisms:

incomplete design information at procurement leads to rework,
scope creep increases material lead times,
added work compresses critical path activities,
rework affects labour productivity.

2.3 Schedule management: critical path, baselines, and progress measurement

In construction, schedule is more than dates—it is logic relationships and constraints.

Baseline vs re-planning

Baseline schedule: the original approved schedule against which performance is measured.
Replanned schedule: updated schedule due to accepted changes, constraints, or resequencing.

Honours exam questions often ask:

When should you rebaseline?
What governance is required?

A defensible answer:

Rebaseline when changes are contractually approved and impacts require a new reference point; otherwise you risk “masking” underperformance.

Progress measurement methods (what to use and when)

Two common measurement approaches:

Time-based: progress as percent of time elapsed (less accurate).
Quantity-based / earned value-based: progress based on completed work quantities or value.

Construction teams often use:

physical percentage completion based on measured quantities,
milestone-based controls for critical packages.

Example: milestones

“Structural frame complete”
“MEP rough-in complete”
“Tiling complete”
“Practical completion achieved”

Milestones must be defined and verified; otherwise progress claims become disputed.

2.4 Cost management: budgets, forecasts, and cashflow reality

Cost management at Honours must address:

total project cost,
breakdown by cost codes,
forecast-to-complete,
cashflow timing (not just final cost).

Cost categories commonly used

Direct costs: labour, materials, equipment.
Indirect costs: site overheads, preliminaries.
Contingency: risk buffer.
Escalation: price changes due to market movements.
Professional fees and financing costs (depending on project context).

Forecasting methods

Earned value concepts (if integrated with schedule and budget).
Bottom-up estimating: update rates and remaining quantities.
Trend analysis: cost performance against planned curves.

Important exam link: Cost overruns often correlate with poor risk response and weak change control.

2.5 Quality management: compliance, inspection and testing, and defects lifecycle

Quality in construction includes:

specification compliance,
workmanship standards,
testing and commissioning outcomes,
defect management after handover.

Quality planning components

quality plan with inspection and test plans,
control points linked to critical activities,
documentation and traceability (concrete test results, material certs).

Defect lifecycle

Defects often emerge:

during commissioning,
after practical completion when building systems are fully loaded.

A Honours-level answer should distinguish:

snags list vs serious defects,
responsibility allocation,
root cause analysis to prevent recurrence.

2.6 Integration: linking scope–schedule–cost–risk in one control framework

Integration is the Honours differentiator: you should show cross-knowledge reasoning.

Example integration logic (exam-ready causal chain):

Scope change adds “additional external paving.”
This requires reordering activities and affects procurement lead time for paving blocks.
Schedule impact extends the critical path by 3 weeks.
Cost impact increases direct costs and site overheads for 3 additional weeks.
Risk impact: new scope increases uncertainty; contingency must be reassessed.
Governance: approve variation and update baseline accordingly.

A high-scoring exam response makes this chain explicit, rather than listing knowledge areas separately.

3. Contracts, Procurement, Claims, and Procurement Risk: Applying Construction Law-Like Thinking Without Becoming a Lawyer

Even in non-law modules, Honours Construction Project Management assessments in South Africa often test contract fluency: you must explain how contract structures drive scheduling, cost, and claims outcomes. This is where many students struggle in exams because they focus on definitions but forget contractual consequences.

3.1 Procurement systems: tendering, negotiated procurement, and framework approaches

Procurement affects risk allocation and time-to-start.

Common procurement modes include:

Traditional lump sum (design separate from construction, client risk often higher until scope is fixed).
Design-and-build (contractor risk shifts and design responsibility clarifies).
Management contracting (management contractor coordinates subcontractors).
Partnering / alliancing (often reduces adversarial claims but requires governance maturity).
Framework agreements (repeat procurement through established terms).

Exam emphasis: “fit for purpose”

When asked “Which procurement method is best?” a good answer qualifies:

For stable, fully designed scope: lump sum can be efficient.
For fast-track or uncertain design: design-and-build or early contractor involvement may reduce schedule risk.
For high complexity with high interdependencies: partnering/alliancing may deliver better collaboration—if governance is strong.

3.2 Contract administration essentials: responsibilities, notices, records

In construction disputes, evidence matters. Exam questions often ask you to list what good contract administration looks like.

Key elements:

Roles and responsibilities: contract administrator, engineer, project manager, superintendent.
Reporting obligations: site diaries, meeting minutes, progress reports.
Notice requirements: especially for variations, extensions of time, claims.
Measurement and valuation: how quantities are assessed.

A high-scoring answer includes:

timeliness of notices,
completeness of records,
traceability linking events to contractual clauses and impact evidence.

3.3 Variations: how they impact cost and schedule (and how to prevent disputes)

Variations are one of the most common claims triggers.

Types of variations

Design changes initiated by the client/engineer.
Site conditions differences (unexpected ground conditions).
Method changes requested for buildability or compliance.
Regulatory changes (new standards, inspections requirements).
Productivity-driven changes (e.g., revised sequencing to avoid clashes).

Variation process (practical sequence)

Variation is identified (instruction or justified request).
Impact is assessed (cost/time implications).
Variation is priced/valued based on contract mechanisms (rates, bills, remeasurement).
Formal instruction/approval is issued.
Works executed under agreed procedures.
Final valuation and documentation for payment/claim.

How disputes form

Disputes occur when:

work is done without formal instruction,
timelines for notices are missed,
valuation method is unclear or inconsistent,
progress measurement does not reflect actual completed works.

In an exam scenario, you should explain:

consequences of missing notices,
importance of contemporaneous records (photos, diary entries, instructions).

3.4 Claims and extensions of time: proving entitlement and causation

Honours-level claims thinking must address three pillars:

Entitlement: what the contract allows.
Causation: what caused the delay (and whether it is the contractor’s responsibility).
Impact quantification: how delay affected the schedule.

Types of delay (useful for exam answers)

Excusable delay (not contractor fault).
Non-excusable delay (contractor fault).
Compensable delay (contractor gets time and money).
Non-compensable excusable delay (time only).

Even without heavy legal detail, you can still teach:

why delay analysis must be structured (baseline schedule with logic),
why “concurrent delays” complicate impact.

3.5 Risk allocation through contracts and procurement

Contract structure allocates risk. Examples:

Lump sum contracts tend to push design completeness risk to the contractor once tender is awarded (depending on clause structure).
Design-and-build shifts more design risk to the contractor.
Faster procurement may increase uncertainty, which must be managed with contingency and collaboration.

In exam questions, markers reward:

identifying the risk owner,
stating mitigation strategies,
suggesting documentation and governance steps.

3.6 Procurement risk management: supplier performance, logistics, and price volatility

Construction procurement risk includes:

supplier delivery delays,
quality failures leading to rework,
material price volatility,
subcontractor insolvency.

A practical risk management approach includes:

vendor prequalification,
performance tracking,
lead time analysis,
escalation clauses or procurement hedging (where contract permits),
contingency planning for critical materials (e.g., structural steel, HVAC units).

Quantitative example for exam calculation (consistent and realistic):
Assume a project needs 60 delivery weeks of total procurement lead time across packages. If supplier performance indicates:

90% on-time delivery rate,
and average schedule slip from late suppliers is 2 weeks when late happens.

If you expect 5 critical material orders, then expected number of late deliveries ≈ 5 × (1 − 0.90) = 0.5.
Expected slip ≈ 0.5 × 2 weeks = 1.0 week expected additional delay.
From a risk control viewpoint, management should:

increase buffers around the critical path,
diversify suppliers for single points of failure,
enforce delivery SLAs.

This type of simple expected-value logic often appears in exam-style problem questions.

3.7 Procurement and claims: early warning systems

A mature procurement-claims interface includes:

early warning notices triggered when procurement lead times drift,
cross-functional forums (commercial + planning + procurement + contracts),
decision logs for when the contractor chooses to expedite, substitute, or redesign.

This reduces last-minute surprises and strengthens evidence quality—critical for any extension of time or cost claim.

4. Project Controls, Risk Management, Stakeholder Management, and Sustainability Integration (Advanced Honours Application)

At Honours level, project management is not just “manage the project.” It is “design control systems that work under pressure.” This section focuses on project controls (planning, monitoring, reporting), risk management maturity, stakeholder governance, and integrating sustainability requirements into delivery.

4.1 Project controls: the planning–monitoring–reporting cycle

A robust project controls system includes:

planning standards (WBS, activity coding, schedule logic),
monitoring cadence (weekly progress, monthly reporting),
reporting outputs (S-curves, variance analysis, risk dashboards),
corrective action workflows.

Planning standards

Planning standards typically include:

activity naming convention,
coding structure aligned to cost codes,
logic rules (finish-to-start dependencies for construction activities),
resource assumptions.

Monitoring cadence

Common cycle:

Weekly: site meeting + progress measurement + constraints log.
Bi-weekly: procurement status + expediting actions.
Monthly: earned value or performance analysis + reforecast.

A strong exam answer states why the cadence matters:

short-cycle monitoring prevents drift from compounding,
constraints are resolved while they are still manageable,
documentation remains timely for contractual records.

4.2 Risk management maturity model (how to answer “critically evaluate”)

Risk management at honours level should be evaluated. Students should not simply describe steps; they should critique implementation quality.

A useful maturity framing includes:

Ad hoc: risks recorded inconsistently; reactive responses.
Structured: risk register exists; identification is performed in workshops.
Integrated: risk triggers link to schedule and procurement controls.
Data-driven: risk forecasts are informed by historical performance; dashboards used.
Adaptive: learning loops feed into planning and contract decisions; continuous improvement.

In exams, when asked to “critically evaluate,” you can discuss:

register completeness vs actionability,
ownership (who is responsible for each risk),
trigger clarity (what signals that a risk is materialising),
response monitoring (are actions verified?).

4.3 Risk identification: sources specific to construction projects

Risk identification in construction must capture both “technical” and “business” risk:

design risk (ambiguity, late design approvals),
ground conditions,
procurement risk,
subcontractor performance,
logistics constraints (access, deliveries),
regulatory and permitting risk,
labour productivity risk,
weather and seasonal impacts,
safety risks impacting productivity and shutdowns,
stakeholder risks (community disruptions, client decision delays).

A strong answer includes how you identify:

workshops with cross-functional teams,
review of contract documents and interface points,
lessons learned from similar projects,
site walkdowns and feasibility reviews.

4.4 Quantifying risk: probability-impact, risk scoring, and scenario planning

Risk scoring methods:

Likelihood × Impact = risk score.
Use risk matrices (e.g., 1–5 scales).

However, Honours-level critique matters:

ordinal scales can be subjective,
probability estimates without evidence lead to false confidence.

To improve quantification:

use historical data where available,
incorporate leading indicators (e.g., procurement slippage rates),
develop scenarios (best-case, base-case, worst-case schedule impact).

Concrete scenario example (consistent, exam-friendly):
Consider a finishing subcontract that is on the critical path.

Probability of subcontractor delay: 20%.
If delayed, schedule impact: 4 weeks.
Expected delay = 0.20 × 4 = 0.8 weeks.

If site overhead cost is R150,000 per month and 1 month ≈ 4 weeks, then expected overhead impact ≈ R150,000 × (0.8/4) = R150,000 × 0.2 = R30,000 expected additional overhead.
This helps justify contingency allocation or mitigation:

prequalify subcontractor,
enforce mobilisation milestones,
contract incentives/penalties (where permitted).

4.5 Stakeholder management: mapping influence and designing communication

Stakeholders in construction include:

client and client representative,
engineer/architect,
contractors and subcontractors,
local authorities,
communities and affected land users,
financiers,
regulators (health & safety, environment),
end users (especially in operational projects).

Stakeholder power-interest matrix

Use this to design communication:

high power/high interest: detailed reporting and frequent meetings.
high power/low interest: concise reporting; secure decisions.
low power/high interest: ensure transparency and feedback channels.
low power/low interest: minimal monitoring; avoid unnecessary friction.

Construction communications that prevent failure

constraint logs (what is blocking progress),
decision logs (who approved what and when),
document control registers,
meeting minutes with action owners and due dates.

An exam question might ask: “How does stakeholder management affect schedule performance?” A good answer ties stakeholder actions to decision timelines:

late client approvals extend design freeze,
regulatory re-inspections add time,
community access disputes cause work stoppages.

4.6 Sustainability and ESG integration in delivery (without losing construction practicality)

Many South African projects increasingly incorporate sustainability requirements:

materials selection and waste minimisation,
energy efficiency in building performance,
water management,
embodied carbon considerations,
local employment and procurement targets.

At Honours level, sustainability is assessed as:

how it is operationalised in the construction plan,
how it affects cost and schedule,
how performance is measured.

Exam-style approach:

Identify sustainability requirements in contract or design brief.
Translate into deliverables: specification clauses, material approvals, waste management plan.
Integrate into procurement planning: early sourcing of low-carbon materials to avoid lead time delays.
Integrate into quality inspections: verify installation compliance (e.g., insulation thickness, glazing spec, commissioning tests for energy systems).
Maintain evidence for reporting: documentation, test results, audits.

This is where many students fail because they treat sustainability as a “separate department.” A strong answer shows sustainability as embedded in control systems.

4.7 Ethics, safety, and risk governance (procedural fairness in decision-making)

Construction is high-risk. Honours exam answers must acknowledge:

safety risk control as a priority constraint,
ethical decision-making in variations and claims (no “creative accounting”),
governance structures for stop-work authority and compliance.

Ethics in construction project management includes:

accurate measurement and reporting of progress,
fair valuation of variations,
transparent procurement and conflict-of-interest management.

5. Exam-Ready Problem Solving in Construction Project Management Honours: Scheduling Calculations, Earned Value Logic, Cost Forecasting, and Case Study Answers

This section is designed as a “how to score” guide for the most common exam question types: quantitative calculations (schedule/cost), application of theoretical frameworks to cases, and structured short-essay answers that combine definitions + critical evaluation.

5.1 Scheduling exam problems: critical path, variance, and recovery options

Typical question types

Given a network or activity durations, identify the critical path.
Compute schedule variance:
- planned duration vs actual duration.
Determine impacts of adding resources or re-sequencing activities.
Explain recovery strategies (crashing/fast tracking) and risks.

How to structure your calculation answer

A high-mark answer shows:

activity list,
dependencies,
earliest start/finish times,
latest start/finish times (if required),
slack values,
and a clear statement of the critical path.

Fast-track vs crash (concept + exam critique)

Fast-tracking: overlapping activities that were originally sequential.
Crashing: increasing resources to reduce duration.

Both have risk:

fast-tracking can increase rework if dependencies are not truly independent,
crashing increases cost and can reduce quality if labour becomes rushed.

In an exam, if asked “recommend strategy,” you must:

consider contractual permission for acceleration,
consider procurement lead times,
consider design freeze and approval timelines.

5.2 Earned Value Analysis (EVA): logic, formulas, and interpretation for construction

EVA is frequently tested as a concept and calculation method. Use the standard variables:

PV (Planned Value): budgeted cost of planned work for the time elapsed.
EV (Earned Value): budgeted cost of the work actually completed.
AC (Actual Cost): actual cost incurred for work performed.

Common metrics:

Schedule Variance (SV) = EV − PV
Cost Variance (CV) = EV − AC
Schedule Performance Index (SPI) = EV / PV
Cost Performance Index (CPI) = EV / AC

Worked example (consistent arithmetic)

Assume at the end of week 6:

PV = R1,200,000 (budgeted progress at week 6),
EV = R1,050,000 (value of work actually completed),
AC = R1,180,000 (actual cost spent).

Compute:

SV = EV − PV = 1,050,000 − 1,200,000 = −R150,000 (behind schedule).
CV = EV − AC = 1,050,000 − 1,180,000 = −R130,000 (over budget).
SPI = EV / PV = 1,050,000 / 1,200,000 = 0.875.
CPI = EV / AC = 1,050,000 / 1,180,000 ≈ 0.898.

Interpretation:

SPI < 1 indicates schedule underperformance.
CPI < 1 indicates cost inefficiency.
Corrective action should target both:
productivity improvement and re-planning for schedule,
cost control measures (procurement review, labour productivity, reduce rework).

An exam marker expects you to link numbers to actions, not only calculations.

5.3 Cost forecasting: EAC logic and bottom-up reasoning

A common EVA-based forecast:

EAC (Estimate at Completion) can use CPI-adjusted approaches:
- EAC ≈ BAC / CPI (if future performance is expected to follow current cost efficiency).

Assume:

BAC (Budget at Completion) = R5,000,000.
CPI computed above ≈ 0.898.

Then:

EAC ≈ 5,000,000 / 0.898 ≈ R5,569,000 (approx).

Examiners usually want you to note assumptions:

if the cause of poor CPI is one-off inefficiency that will be corrected, EAC may be lower than CPI projection.
if inefficiency persists (labour productivity issues continue), EAC may be accurate or even worse.

Therefore:

in a full-answer exam response, propose actions to improve CPI:
- rework reduction via quality control,
- procurement corrections to avoid expensive substitutions,
- productivity improvement through revised sequencing and crew planning.

5.4 Contract and claims problem solving: delay evidence and variation logic

A common case in exams:

a client delays approvals,
the contractor records no formal notices for extension of time,
the schedule slips.

A high-mark answer includes:

identify what the contractor likely needs to prove:
- contractual entitlement,
- causation,
- impact quantification.
explain consequences of missing notices (evidence weakness).
propose mitigation steps:
- reconstruct schedule impacts with contemporaneous evidence,
- prepare time impact analysis,
- document approvals delays and instruction timelines.

For variations:

show how to structure evidence:
- instruction records,
- quantity measurement support,
- material price changes and lead time proof if relevant.

5.5 Case study answer framework (what to write in 10–20 mark questions)

When you get a scenario, a structured answer usually includes:

Identify issues (3–6 bullet points).
Link issues to theory (risk, schedule, scope, procurement, contract governance).
State impacts (cost, time, quality, safety).
Recommend actions (short-term and long-term).
Support recommendations with a method or framework:
- risk matrix + triggers,
- WBS + baseline update,
- variation control process,
- stakeholder communication plan.
Critical evaluation:
- trade-offs,
- constraints (contractual, budget, approvals),
- risks of recommended actions.

This structure reduces the chance of “rambling” and increases mark allocation clarity.

5.6 Integrated mini-case (fully worked exam-style response)

Scenario:
A building project in Gauteng experiences repeated schedule delays. During early stages, design approvals were late, causing incomplete information for tender packages. After award, the contractor implemented subcontract works based on preliminary drawings. Midway, the client issued multiple scope variations related to finishing specifications. In the monthly progress report, the contractor used time-based progress percentages rather than quantity-based measurements. Claims later emerged regarding extension of time and variation costs. The project team also reports that supplier deliveries for key MEP units slipped due to unexpected lead times.

Question (typical exam):
Discuss the likely causes of the schedule overrun and propose an integrated corrective and preventive action plan.

Answer (exam-ready structure)

A. Likely root causes (issue identification)

Design approval delays leading to incomplete tender information and rework/replanning.
Scope variations introduced during execution, increasing critical path risk.
Inaccurate progress measurement (time-based rather than quantity-based), reducing control accuracy.
Procurement lead time volatility for critical MEP packages, producing constraints.
Contract administration and claims weakness if notices/records were not contemporaneous.

B. Link to theory and mechanisms

Late design approvals increase uncertainty in scope definition, causing procurement and scheduling churn.
Scope variations require formal impact assessment; otherwise, schedule and cost baselines become unreliable.
Progress measurement affects schedule control; if EV-like logic cannot be used, corrective actions become delayed.
Procurement risks influence critical path activities—especially if MEP units have long lead times.
Claims require evidence of entitlement and causation; weak records weaken negotiation position.

C. Impacts

Schedule: behind baseline due to both rework and critical procurement delays.
Cost: additional preliminaries (site overheads) and variation costs, plus potential inefficiency.
Quality: risk of rework due to outdated designs/specifications.
Contractual: potential dispute escalation due to disagreement on entitlement and valuation.

D. Integrated corrective actions (short term)

Restore control baseline integrity
- Review approved scope and document accepted variations.
- Establish a revised baseline only for contract-approved changes.
Correct progress measurement
- Move to quantity-based or milestone/earned-value approach for reporting.
- Validate progress measurement with measurable deliverables.
Procurement constraint recovery
- Re-forecast procurement dates for MEP packages based on confirmed supplier commitments.
- Implement expediting plans where contract allows and communicate change consequences.
Delay and variation evidence capture
- Compile site diary evidence, instruction logs, variation registers, and approval timelines.
- Prepare structured delay impact narratives and schedule impact analysis for negotiations.

E. Preventive actions (long term)

Design approval governance
- Introduce formal design submission and approval milestones with escalation paths.
Change control discipline
- Ensure all variations follow a consistent process: identification → impact assessment → approval → baseline update.
Risk management integration
- Integrate procurement lead time risk into schedule buffers and critical path monitoring.
- Use triggers for supplier slippage (e.g., lead time drift beyond a threshold).
Stakeholder communication
- Weekly coordination with client/engineer to confirm decision dates and prevent “hidden” delays.
Quality assurance linked to control
- Ensure inspection and test plans align to critical works to reduce rework loops.

F. Critical evaluation of trade-offs

Fast recovery may require acceleration strategies that increase cost; ensure contract permissions and approvals.
Increasing documentation and measurement accuracy costs time; however, it reduces dispute probability and improves decision speed.
Revising baseline without contract approval risks damaging claims position and undermines accountability.

This is the kind of answer pattern that aligns with South African Honours expectations: problem identification, theory linkage, quantified logic where possible, and structured recommendations.

5.7 How to write high-scoring exam essays and short notes (South Africa Honours style)

A final “exam craft” checklist helps convert knowledge into marks.

For definitions (e.g., “Explain critical path”)

Provide a crisp definition.
Add one construction-specific example.
Mention why it matters (decision-making implication).

For critical discussion (e.g., “Critically discuss risk registers”)

State what good risk registers do.
Then critique what often fails:
- lack of ownership,
- no triggers,
- disconnect from planning/scheduling.
Provide solutions:
- link risks to activities and control thresholds,
- assign risk owners,
- review and update schedule impacts.

For problem solving (EVA, schedule variance)

Show formulas and arithmetic.
Interpret results explicitly:
- behind schedule? cost overrun? efficiency?
Propose actions:
- where to look next, what corrective step to take.

Closing consolidation (what matters most for UJ Honours exams)

For UJ BSc in Construction Project Management Honours Notes, the exam pattern rewards integrated competence:

research logic (problem → aim → objectives → methods → analysis),
disciplined project controls (scope/schedule/cost integration),
contract fluency (variations, notices, evidence, claims logic),
risk maturity and governance (quantify, integrate, learn),
and structured answer frameworks (scenario → issues → mechanism → actions → evaluation).

These are the core competencies consistently assessed in South African university constructions management examinations—whether questions resemble applied case studies or quantitative planning/cost control tasks.