Legal Aspects for Project Managers (UP PPM Module) Study Notes

Legal literacy is a core competence for project managers because projects operate within a web of contracts, regulations, safety duties, procurement rules, and risk allocation. In the University of Pretoria (UP) Programme in Project Management (PPM) context, legal aspects are not abstract theory: they directly influence how scope is defined, how stakeholders’ expectations are managed, and how disputes are prevented or resolved. These study notes focus on practical, exam-ready understanding of the legal environment for projects in South Africa, with emphasis on how project decisions translate into legal rights, obligations, and remedies.

1) Core Legal Concepts Every UP PPM Project Manager Must Know (South African Project Law Foundations)

A project manager’s legal responsibility is not only about “knowing the law”, but about applying legal concepts when planning, contracting, executing, controlling, and closing a project. In South African project contexts, the most frequently examined themes are: contract formation and interpretation, legal capacity and authority, remedies for breach, risk and liability allocation, and the relationship between project governance and compliance.

Legal personality, rights, duties, and authority in projects

Most projects involve multiple entities (a client/employer, contractors, consultants, subcontractors, suppliers, and sometimes joint venture partners). Each entity is typically a separate legal “person” that can hold rights and incur obligations under contracts. For exam purposes, it helps to distinguish:

Legal personality: A company, close corporation, or partnership can own property, sue and be sued.
Rights: What the contract or law guarantees (e.g., payment due dates, acceptance criteria, completion obligations).
Duties: What must be done or avoided (e.g., safety compliance, reporting, confidentiality).
Authority: Whether an individual (including a project manager) can bind an organisation.

In practice, authority problems cause real disputes. A project manager may sign correspondence that later becomes evidence of commitments (scope changes, cost/time impacts, acceptance, or waivers). Even if the project manager lacks formal “signing authority,” the client may argue that the organisation is bound based on implied authority, reliance, or ratification.

UP PPM exam angle: In scenario questions, identify (1) which legal entity is the contracting party, (2) who had authority to act, and (3) whether the action created binding obligations.

Common scenario pattern

A client emails: “Proceed with the additional work; we will approve the rate later.”
The project manager orders work.
Later, the client refuses payment claiming no approved variation order.

A legally literate project manager asks: Was there a binding variation mechanism in the contract? Was there a formal change order process? Did the contractor reasonably rely on a representation? Was there a signed instruction or a written authority?

Sources of South African project law relevant to project managers

South Africa’s legal system for project work draws from multiple sources:

Legislation
Examples include general contract law concepts (affected by statutes), procurement rules in government contexts, labour legislation, and occupational health and safety duties. While the exact acts depend on industry, the legal reasoning approach is consistent: determine the applicable statute, define the duty it creates, and identify compliance requirements and enforcement consequences.
Common law
The common law includes principles of contract (offer/acceptance, intention to create legal relations), delict (tort liability for harm), and agency/authority.
Contractual terms
In project management, the contract is often the primary source of duties and procedures. It will set out:
- scope, deliverables, acceptance
- payment structure, retention
- change control and variation procedure
- default/termination rights
- dispute resolution mechanisms (e.g., adjudication/mediation/arbitration/court)
Regulatory and technical standards
Standards may be referenced by contract (e.g., building standards, electrical codes). If the contract incorporates a standard, failure may become breach even if the law alone may not have been violated.
Administrative and governance requirements
Especially for public procurement or publicly funded projects, additional compliance frameworks may apply.

Contract law fundamentals for project management

Contracts govern most project relationships. Exam questions often require applying contract basics to factual matrices.

Contract formation: intention, offer, acceptance

A valid contract generally requires:

Offer and acceptance
Intention to create legal relations
Capacity
Consideration (in classic contract terms, though South African courts often focus on substance rather than technicalities)
Lawfulness
Certainty

Projects create many “quasi-contract” interactions: meetings, minutes, emails, instruction letters, and progress reports. The key is whether those communications demonstrate intention and certainty.

Practical rule: If the contract has strict formalities (e.g., variations must be “written and signed by the client’s designated representative”), then informal communications may not satisfy that requirement—unless the other side can prove waiver, estoppel, or subsequent ratification.

Interpretation: plain meaning vs context

Even when words are clear, disputes arise over interpretation:

What exactly is “Substantial Completion”?
Does “best endeavours” mean a high standard or a reasonable-efforts standard?
Are “provisional sums” fixed amounts or placeholders?

Interpretation principles typically consider:

the ordinary meaning of language,
the contract as a whole,
the purpose of clauses,
and (where ambiguity exists) surrounding circumstances.

For project managers, interpretation questions often involve:

defining scope boundaries
identifying whether a document is binding (e.g., tender schedules, BoQ, design briefs)
confirming whether risk allocation clauses limit liability

Breach and remedies: what happens when things go wrong?

A project manager should know that legal consequences of breach can be major, including:

termination,
damages,
specific performance,
restitution,
interest and costs,
and reputational and insurance impacts.

Types of breach

Failure to perform (work not done or done incorrectly)
Late performance (delay)
Failure to comply with procedures (e.g., not submitting a notice within contractual time limits)
Repudiation (refusal to perform)

Remedies commonly relevant in project disputes

Damages: compensation for loss caused by breach. Types may include direct costs, consequential losses (depending on the contract and proof), and sometimes loss of profit.
Liquidated damages / penalties: contractually agreed sums for late completion (enforceability depends on reasonableness and drafting).
Specific performance: forcing performance (more common in certain contexts).
Termination: ending the contract under defined triggers.
Set-off and retention: contractual rights to withhold amounts.

Exam technique: In scenario questions, list:

the breach,
whether it is material,
notice requirements,
the remedy likely available,
and any limitation-of-liability or exclusion-of-loss clauses that may affect quantum.

Case-like problem framing for UP PPM exams

Typical exam prompts require identifying:

Which clause addresses the issue (change order, delay, payment, quality)
Whether contractual steps were followed (notice, documentation)
Whether there was reasonable reliance
Whether mitigation was undertaken by the affected party
Whether damages are provable and not too remote

Project managers should therefore build “legal thinking” into project governance:

ensure written records,
enforce procedure compliance,
and treat stakeholder communications as legal evidence.

2) Contract Management and Risk Allocation for Projects (UP PPM Module Focus)

For a project manager, contracting is the operational bridge between planning documents and enforceable obligations. The best project plan fails legally if the contract does not reflect the plan—or if governance mechanisms do not allow legitimate changes, delays, and variations to be properly priced and authorised.

Choosing the right contract structure and understanding roles

Projects typically involve:

Client/Employer (pays and defines requirements),
Main Contractor/Contractor (executes works),
Consultant(s) (design/engineering, project management services),
Subcontractors and suppliers.

In many disputes, the question becomes: Who promised what, to whom, and under which contract?

Contract structures commonly encountered

Lump sum / fixed price: contractor assumes more risk of cost overruns; client expects defined deliverables.
Cost-plus / reimbursable: client bears more cost risk; contractor’s entitlement may depend on cost verification and agreed overhead/profit.
Unit price (BoQ-based): payment depends on quantities measured/declared; disputes arise around measurement methodology and variation of quantities.
Design-and-build: contractor designs and builds; quality and design liability allocation becomes crucial.
Framework agreements: in procurement, may govern future calls-off.

UP PPM exam angle: If the prompt includes “delay compensation” or “variation rates,” the contract type is often designed to influence how the remedy is calculated.

Contract clauses project managers must master

A project manager should treat certain clauses as “high frequency exam clauses”:

Scope and deliverables
- What exactly must be delivered?
- Is the scope described in specifications, drawings, BoQ, or a technical design brief?
- Are there acceptance tests?
Change control / variation procedure
- Who can instruct changes?
- What counts as a variation?
- What notices are required?
- How are rates and time adjustments calculated?
Programme, milestones, and delay
- What is the baseline programme?
- What constitutes a delaying event?
- Are extensions of time (EOT) available?
- Are liquidated damages applicable?
Payment terms
- When is payment due?
- Are certificates required?
- Are there retention amounts?
- What happens if invoices are disputed?
Quality assurance and defects liability
- How is compliance measured?
- What is the defects liability period?
- Is there a remedy for latent defects?
Risk allocation and limitations of liability
- Who bears which risks: weather, ground conditions, design errors, regulatory delays?
- Are indirect/consequential damages excluded?
- Are liability caps present?
Insurance
- Minimum insurance requirements
- Who bears deductibles?
- What is required before starting work?
Termination and suspension
- triggers for termination
- notice periods
- suspension rights (and obligations to mitigate)
Dispute resolution
- negotiation and escalation
- mediation/adjudication/arbitration
- court jurisdiction and legal costs

Example: Variation disputes—how legal reasoning plays out

Consider a scenario typical of project management exams:

Contract states: “Variations must be instructed in writing by the Project Manager/Engineer.”
The client requests additional work via WhatsApp voice note.
The contractor proceeds.
Later, the client refuses to pay, claiming no formal written variation.

Legal outcome depends on multiple factors:

contract formalities and designated representatives,
evidence of instruction and authority,
whether the client subsequently acted to confirm the variation (ratification),
whether there was reliance and if refusal would be unfair under doctrines like estoppel (depending on facts).

Project manager best practice: Only treat variations as authorised when they align with the contract mechanism. If informal requests occur, immediately convert them into:

a written change request,
a variation order process,
and a formal agreement on rates/time impacts.

Notice provisions and time bars

One of the most exam-relevant legal traps is the failure to give notice within the contract time limit. Many contracts include clauses requiring notice for:

claims,
delays,
changes,
damages,
or extension-of-time events.

If a contractor fails to comply, it may lose the right to claim (even if the underlying facts are valid). The rationale is that the employer/client needs early notice to mitigate and manage costs and programme impacts.

Counter-argument exam pattern: A party may argue:

substantial compliance,
that the employer had knowledge,
waiver by conduct,
or that the clause is unreasonable or unenforceable in specific contexts.

Your exam answers should therefore:

explicitly state whether notices were required,
list the notice deadlines,
verify whether the project manager complied,
and explain the legal consequence of non-compliance.

Risk register vs legal risk allocation

Project managers often maintain risk registers, but legal risk allocation is not identical. A legal clause may shift risk for:

foreseeable conditions,
unforeseeable events,
design liability,
regulatory changes,
and force majeure.

A project’s legal and operational risk register should therefore be cross-mapped to contract clauses:

If a risk is “Client bears” under contract, the project plan should reflect that cost/time impacts become client responsibilities (subject to procedure and claims).
If a risk is “Contractor bears,” the contractor’s governance must include robust cost controls and programme contingency.

Liability exclusions and caps: what they mean in disputes

Many contracts exclude or limit:

indirect/consequential damages,
loss of profit,
reputational damages,
and sometimes liabilities beyond a cap amount.

However, exclusions may have carve-outs:

fraud or wilful misconduct,
breach of confidentiality,
personal injury or death,
certain statutory liabilities.

UP PPM exam technique: When facing a claim scenario, do not stop at “breach occurred.” Always ask:

Is the claimed loss the type excluded?
Is there a limitation cap?
Is there a carve-out?
Was mitigation required and done?

Document control as legal evidence

Legal disputes are fought with documents. A project manager’s daily tasks become legal evidence:

instructions (emails, letters),
meeting minutes,
site diary entries,
progress reports,
deviation reports,
approval/acceptance records,
test results and defect lists.

To prepare for potential claims:

ensure chronological diaries,
record factual observations separate from opinions,
store approvals and sign-offs,
maintain traceability between scope references and deliverables.

Exam-ready statement: “The contractor must prove entitlement” is frequently tested. Proof usually depends on documentary trail and compliance with contractual conditions precedent.

3) Procurement, Compliance, and Public-Sector Legal Duties (South Africa Context for UP PPM)

Many UP PPM learners work on government projects or projects funded by public entities. In those settings, procurement rules and compliance requirements shape contractual formation, fairness, documentation, and governance. Even in private projects, compliance is increasingly critical due to safety, environmental obligations, labour laws, and consumer/protection duties.

Procurement governance: fairness, competition, and accountability

Procurement processes aim to ensure:

value for money,
fairness and transparency,
accountability in expenditure,
compliance with applicable procurement frameworks.

In South African public procurement environments, you typically see:

tender requirements,
evaluation criteria,
bid documentation,
and contractual procurement compliance obligations.

For a project manager, procurement matters legally because:

contract formation may be constrained by procurement rules,
irregularities may render outcomes challengeable,
and documentation gaps may undermine enforceability or lead to audit findings.

Common procurement-to-project failure points

Scope ambiguity at tender stage leading to later variation disputes.
Weak evaluation evidence leading to challenges (including bid disputes).
Contract award conditioned on missing approvals, causing later suspension or termination.
Non-compliance with procedural requirements (notice periods, bid amendments, evaluation matrices).
Uncontrolled pre-award commitments (ordering before formal contract).

Compliance obligations affecting project delivery

Compliance covers multiple legal domains:

Occupational Health and Safety (OHS): project managers must ensure safe working practices and compliance with safety requirements.
Environmental compliance: environmental authorisations, impact assessments, and conditions must be respected.
Labour compliance: employment practices, working hours, training requirements, and worker protections.
Tax and statutory registration: ensuring contractor registrations and tax compliance.
Data protection and confidentiality: especially with sensitive project information.

While exam syllabi can vary by module emphasis, the strategic legal approach is:

identify applicable duty,
specify who is responsible (contractor vs employer vs consultant vs project manager),
confirm procedures and evidence required to demonstrate compliance,
manage consequences of non-compliance.

Regulatory compliance and contract incorporation

Contracts often incorporate regulatory requirements by reference. This means:

even if statutory duties exist,
the contract may require additional procedures (reporting templates, inspections, training plans, and documentation).

If contract terms “incorporate” legal or technical standards, then breaches can become both:

a legal violation (statutory liability),
and a contractual breach (entitlement to damages/termination).

Exam example framing: If a tender specification references a standard, and the contractor fails that standard, the employer can claim breach even if “the law” might have permitted a lower standard.

Quality assurance as legal compliance

Quality clauses create enforceable obligations:

workmanship standards,
materials specifications,
test and commissioning procedures,
and acceptance criteria.

A project manager should understand the legal significance of quality systems:

When defects occur, the question is whether the contractor complied with contractual standards.
Test results and acceptance certificates become evidence.
Failure to follow commissioning checklists can reduce a claim for latent defects if documentation shows otherwise.

Public-sector project disputes and the role of documentation

Public-sector projects frequently face challenges:

procurement irregularities,
budget constraints and formal spending authority,
audit scrutiny,
and administrative law exposure if decisions are procedurally flawed.

From a project manager’s perspective, disputes may include:

delay claims,
termination disputes,
payments withheld due to non-compliance with procurement procedures,
or challenges to contract amendments.

Practical legal discipline: separate:

“technical facts” (dates, measurements, test outcomes),
“contractual steps” (notices, approvals, change orders),
“governance evidence” (authorisations, sign-offs, delegations).

Counter-arguments: “We complied with the spirit but not the letter”

In exams, you may see arguments like:

“We met the objective of procurement fairness even if a notice was late.”
“We substantially followed change procedures though not strictly.”

Legal analysis depends on:

whether the clause is procedural condition precedent,
whether late compliance results in prejudice,
whether waiver or ratification applies,
and whether the contract allows discretion for the employer to accept deviation.

UP PPM exam approach:
When asked to evaluate a party’s argument, structure it as:

identify the strict requirement in the contract or policy,
identify the deviation,
assess prejudice,
assess possibility of waiver/ratiﬁcation,
conclude on likely enforceability or claim success.

Example: Compliance-driven payment refusal

A scenario:

The contractor submits an invoice but missing an inspection certificate.
Contract states: “No payment shall be made unless the certificate of practical completion is issued.”

The contractor claims payment due because work is complete. The employer refuses citing contractual precondition.

Legal outcome typically depends on:

whether the certificate is a condition precedent,
whether the employer unreasonably withheld certification,
whether there is implied obligation to act fairly and timely.

The project manager’s documentation becomes central:

Did inspections occur?
Was completion tested?
Were snags recorded and addressed?
Did the employer delay certification due to avoidable reasons?

4) Claims, Dispute Resolution, and Litigation Readiness for Project Managers

Legal aspects for project managers strongly include claims management and dispute resolution processes. Many disputes are avoidable if claims are prepared properly and procedures are followed. The legal system rewards evidence, compliance with contractual mechanisms, and reasonable mitigation.

Claims management as a legal discipline

A claim is not just a complaint; it is a structured request for relief (time, money, or both) based on contractual entitlement. Claims must be:

identified early,
supported by evidence,
priced (where money is involved),
and procedurally compliant (notice and documentation).

A project manager should manage claims through a repeatable lifecycle:

Event identification
Record when the event occurred and what triggered it.
Contractual basis
Cite the specific clause that provides entitlement.
Causation analysis
Link event to impacts (cost increases, delay, disruption).
Mitigation steps
Document actions taken to reduce damage.
Notice and timing
Ensure deadlines in the contract are met.
Quantum preparation
Calculate costs/time impacts using agreed measurement and rate methodologies.
Submission and escalation
Submit according to the contract’s dispute escalation path.
Negotiation and record preservation
Maintain records to preserve rights.

Exam-ready phrasing: “The claimant must prove entitlement and quantify loss” is commonly tested. You should mention both entitlement (legal right) and quantum (amount claimed).

Causation and the “but for” analysis

Causation is frequently the hardest part. Project impacts can have multiple causes:

client-caused delays,
design issues,
weather,
supply chain problems,
contractor inefficiency.

Legal disputes often hinge on whether the claimant can demonstrate that the event caused the claimed impact, and not something else.

A project manager should therefore:

distinguish concurrent delays,
use critical path logic (where applicable),
separate internal inefficiencies from external causes,
and document mitigation and resequencing.

Delay analysis: time, EOT, and liquidated damages

Delay disputes require careful treatment of:

baseline programme,
original completion date,
extensions of time rules,
float allocation,
and the relationship between EOT and liquidated damages.

In exam scenarios, the contract may specify:

that EOT is granted only for “Relevant Events” listed,
that notice must be given within days,
and that liquidated damages apply automatically unless EOT is approved.

A strong exam answer typically covers:

whether the event is a relevant event,
whether notice was timely,
causation of delay,
assessment of delay length,
whether liquidated damages are limited or excluded by EOT.

Variation claims vs delay claims: avoiding double counting

A common error is double counting: claiming the same cost or time under both variation and delay. Legally, damages must correspond to actual additional loss and avoid duplication.

Example:

A variation increases scope and requires overtime (cost).
The overtime also affects programme (delay).
If overtime caused delay is already accounted for in schedule changes, then claiming separate delay compensation may overstate.

Project managers must coordinate:

variation pricing and time impact analysis,
delay cause tracking,
and how the contract defines how time impacts are handled for variations.

Dispute resolution clauses: negotiation, escalation, mediation, adjudication, arbitration

Contracts often include multi-tier dispute resolution:

Good faith negotiations
Escalation to senior management
Mediation
Adjudication (common in construction disputes)
Arbitration or court litigation

A project manager must know:

where each step is triggered,
time limits for starting each step,
and whether adjudication decisions are binding pending arbitration/court.

Exam technique: When asked what steps to take, align them with the dispute clause and confirm:

which step is mandatory,
which is optional,
whether a party can jump tiers,
and what happens if a party refuses to participate.

Litigation readiness: evidence, strategy, and preservation

Even if disputes are resolved early, litigation readiness matters because:

negotiations often rely on how well the case can be proven,
late evidence can be excluded or weakened,
credibility is crucial.

A project manager should adopt litigation-ready habits:

preserve emails, diaries, instructions, approvals,
keep site logs with date/time,
maintain change registers,
record meeting outcomes,
store test results and inspection reports,
and maintain a consistent timeline.

Evidence types and how they’re used

Contemporaneous documents (strong evidence)
Diaries/site notes (factual, date-based)
Certificates (formal records)
Expert reports (delay/quantum technical analysis)
Witness statements (subject to credibility)
Invoices and cost records (quantum proof)

Costs, interests, and legal risk

Disputes can become expensive. Many contracts allocate:

legal costs based on outcomes,
costs of adjudication/arbitration,
and sometimes interest on late payments.

A project manager should:

prepare for cashflow impacts,
ensure claims are not only right but also financially viable,
and consider settlement strategy.

Counter-argument exam prompt:
If asked, “Should the contractor settle early?”, analyse:

strength of evidence (entitlement + quantum),
time and cost of dispute resolution,
business risk and cash constraints,
impact on relationships and future procurement.

Example: Building a dispute timeline (exam-style)

A timeline approach often scores marks:

Day 0: Variation request received.
Day 7: Contractor submits change notice.
Day 12: Employer acknowledges, requests revised pricing.
Day 20: Contractor issues revised quotation.
Day 25: Work commences without formal approval.
Day 60: Completion impacted; EOT claim prepared.
Day 65: Notice of delay submitted.
Day 90: Payment withheld due to missing certificates.

An exam answer would link each step to:

contractual procedures,
entitlement clauses,
and whether any notice failures occurred.

5) Governance, Ethics, and Professional Liability for Project Managers (UP PPM Module—Exam Focus)

Legal aspects for project managers also include governance and professional conduct. Many disputes are not only about technical errors but about ethical choices: misrepresentation, improper approvals, conflicts of interest, negligence, and failure to act in a fiduciary-like or duty-of-care manner (depending on role and context).

Project governance structures and legal compliance

Projects typically operate under governance mechanisms such as:

steering committees,
approval hierarchies,
delegated authorities,
reporting cycles,
risk reviews,
and compliance audits.

Legally, governance matters because:

it shows decision-making processes,
establishes whether actions were authorised,
and demonstrates reasonable diligence.

If a project manager acts outside delegation, the organisation may still be bound depending on:

apparent authority,
estoppel,
ratification by later approval,
or contractual representations.

Exam angle: Identify whether the project manager acted within authority and whether governance processes were followed.

Ethical duties: transparency, confidentiality, and conflict of interest

Legal systems enforce ethics through both contract and law. Key ethical principles with legal consequences:

Transparency: Accurate reporting to prevent misrepresentation claims.
Confidentiality: Protecting proprietary or personal information.
Avoiding conflicts of interest: especially in procurement and subcontracting.
Fair dealing: not using contract clauses to exploit another party unfairly.

A project manager should be cautious about:

accepting gifts or inducements,
steering subcontractors without disclosure,
manipulating progress reporting,
or “informally agreeing” variations to bypass controls.

Negligence and duty of care in project management

Project managers may face claims relating to negligence, depending on:

role (employee vs consultant vs agent),
the duty owed,
breach of that duty,
causation, and
damage.

Common negligence allegations in project contexts include:

poor supervision leading to safety incidents,
failure to follow professional standards,
failure to detect design or quality issues within reasonable time,
inadequate risk management,
or failure to comply with statutory duties.

UP PPM exam framing:
When asked about negligence, use a structured approach:

define duty of care,
define breach (what was not done),
link to harm (causation),
quantify or describe damage.

Safety obligations and legal consequences

Safety is a major legal area. Even without focusing on specific legislation names in an exam, you should demonstrate:

safety planning,
hazard identification,
compliance training,
incident reporting,
and enforcement mechanisms.

From a project management standpoint, safety failures cause:

potential criminal or administrative enforcement (depending on seriousness),
civil claims for damages,
and contractual default risk (termination/suspension).

A project manager’s defence often relies on:

documented safety systems,
evidence of training and oversight,
prompt correction of hazards,
and showing that incidents were not foreseeable or not preventable with reasonable care.

Professional indemnity, liability, and insurance

Professional liability insurance becomes relevant where project managers act as consultants or where professionals are involved. Contracts may require:

specific levels of insurance,
policy terms,
and proof before work begins.

Liability limitations in contracts do not always protect against:

personal injury,
fraud,
wilful misconduct,
or certain statutory obligations.

Exam answer tip: Always mention that insurance and liability clauses can interact. Even if liability is capped, insurance may determine how much is recoverable practically.

Documentation, ethics, and evidence integrity

In disputes, evidence integrity is crucial. A project manager must ensure:

documents are accurate,
time stamps reflect actual events,
diaries are not backdated,
variation claims include complete supporting documents,
and meeting minutes truthfully reflect decisions.

Altering records can create severe legal consequences:

breach of contract and potential fraud allegations,
criminal implications in serious cases,
and credibility collapse in arbitration or court.

Example: Procurement misconduct risk in subcontracting

Scenario:

Contractor appoints a subcontractor outside approved list.
Contractor claims subcontractor had better rates and was selected informally.
Later, client refuses cost reimbursement due to procurement policy breach and lack of approval.

Possible legal effects:

breach of contract (if approval was required),
inability to claim for work not authorised,
and potential audit penalties (especially in public-sector settings).

A strong project manager response:

requires formal approvals before appointment,
ensures subcontract scope aligns with contract scope and safety requirements,
and ensures subcontract terms flow down obligations.

Consent, waivers, and settlement agreements

Legal disputes often end in settlement. Settlement may require:

formal written agreement,
release of claims,
confidentiality provisions,
and sometimes finality clauses (“no further claims”).

Project managers must:

obtain proper authorisation to settle,
ensure settlement scope is understood,
and document any waiver clearly.

Exam scenario:

A senior manager says “we won’t pursue the claim” in a meeting.
Contractor later claims entitlement based on earlier negotiations.

The question becomes: Is that statement a binding settlement or a non-binding discussion? The contract may require written settlement agreements.

Exam technique: Analyse authority and whether the contract requires formal written settlements.

Delegation of authority and signatory controls

Projects use signing authorities to prevent unauthorised commitments. Practical legal governance includes:

delegations matrix,
procurement authority limits,
who can approve variations,
who can sign EOT approvals,
and who can issue instructions that legally bind the employer/client.

If a project manager signs outside authority:

the organisation may deny liability,
but the other party may argue apparent authority or reliance.

Your exam answers should mention both sides:

the client’s argument (lack of authority),
and the contractor’s argument (reliance/ratification).

Closing a project legally: defects, acceptance, and final accounts

Legal closure involves more than “completion.” Key closure steps:

final acceptance and handover documents,
snagging/defects list and completion confirmation,
commissioning test results,
final measurement and final account,
release of retention (if applicable),
final tax invoicing and close-out certification,
and clearing remaining claims.

If closure documentation is careless, later disputes may arise over:

whether defects are within defects liability,
whether completion is truly achieved,
whether final accounts were “full and final” or subject to pending claims.

Exam prompt pattern: “The employer accepted practical completion but refuses final payment due to unresolved defects.”
Your answer should examine:

definitions of acceptance,
defects liability scope,
contractual mechanics for withholding payment,
and evidence of compliance.

Quick Exam-Ready Checklists (UP PPM Legal Aspects)

A) Contract compliance checklist for project managers

Identify contracting parties and authority to bind.
Follow change control: written variation instructions, rate/time agreements.
Manage programme: EOT notices, delay causation documentation.
Follow payment procedures: certificates, invoices, supporting documents.
Maintain quality evidence: tests, inspections, acceptance criteria.
Track contractual notices and time bars (claims are conditional on compliance).
Apply risk allocation: ensure planning aligns with who bears each risk.
Preserve dispute readiness: timelines, diaries, correspondence.

B) Claims submission checklist

Contract clause basis cited explicitly.
Notice given within contractual deadlines.
Causation documented (not just correlation).
Quantum calculated without double counting.
Mitigation actions evidenced.
Supporting documents attached (diary excerpts, approvals, test results).
Escalation steps consistent with dispute resolution clause.

C) Dispute resolution checklist

Identify the contractual dispute tier to trigger.
Gather evidence by timeline.
Prepare concise position paper: facts → contract → entitlement → remedy.
Consider settlement: authority and written settlement requirements.
Ensure confidentiality and record preservation.

Glossary of High-Frequency Legal Terms in Project Management (South Africa)

Breach: failure to perform contractual duties.
Condition precedent: a requirement that must be fulfilled before entitlement arises (e.g., certification required before payment).
Variation: authorised change to scope, time, or cost.
EOT (Extension of Time): contractual relief for delay, often linked to exemptions from liquidated damages.
Liquidated damages: predetermined sum for late completion.
Causation: legal requirement linking event to claimed loss or delay.
Quantum: the amount claimed; must be substantiated.
Repudiation: refusal to perform leading to termination rights.
Waiver: voluntary relinquishment of a right, sometimes inferred from conduct.
Ratification: later approval that can validate earlier unauthorised actions.
Condition in policy/procurement: procedural compliance requirement affecting enforceability in public contexts.
Mitigation: steps taken to reduce loss after a breach or delay.

Concluding Focus for UP PPM Exams

In UP PPM assessments, the highest marks typically come from structured legal reasoning applied to project facts: identify contractual entitlements, respect procedure (especially notices and formalities), show evidence-based causation, quantify impacts without duplication, and align remedies to the dispute resolution mechanisms in the contract. Mastery is less about memorising legal jargon and more about consistently translating project management actions into legally defensible documentation and decision-making.