Project Budgeting and Financial Control (Wits Plus) Notes — Wits Plus for Project Management (PMB 000 / CPM / MNG/UNC style)

Project budgeting and financial control are the practical “language” of project management: they translate project plans into money, and they use financial information to keep delivery on track. In Wits Plus–style project management short courses, the emphasis is typically on how to build a project budget, how to forecast and monitor expenditure, and how to manage variances using disciplined controls. These notes are designed to support exam preparation for Wits Plus and aligned content commonly assessed in South African project management modules (including elements that appear in courses such as MNG 0001, PMB, CPM, and related programme/operations management subjects offered across local universities).

1) Project Budgeting Fundamentals (Linking the WBS to Cost and Control)

Why budgeting is more than “estimating costs”

In project budgeting, the objective is not only to produce a single figure called “the budget”. A good project budget is a managed system with:

• a cost baseline (the approved plan against which performance is measured),
• cost categories that reflect how the project will actually spend,
• a schedule of expected spending (time-phased budget),
• and rules for updates (change control, reforecasting, and variance handling).

This is what makes budgeting a foundation for financial control. Without a structured budget, variance analysis becomes subjective: you can observe overspend but you cannot convincingly explain why, whether it was unavoidable, or what corrective action is possible.

Components of a project budget

A standard project budget structure includes both direct and indirect costs, often organised into categories consistent with procurement and accounting.

Common cost components

• Direct labour (project team time charged to the project)
• Materials / supplies
• Contractor costs (outsourced work)
• Equipment rental / depreciation charges
• Travel and accommodation
• Subcontractor expenses
• Contingency (for identified risks or uncertainty)
• Project management overhead (if applicable)
• Escalation allowances (for expected inflation or price changes)
• Taxes, duties, and permits (where relevant)

A key exam concept is budget completeness: the budget must cover all work required by the scope baseline, plus agreed allowances (contingency, escalation).

Estimating methods: from top-down to bottom-up

Students often memorise estimation “types”, but exams usually test when and why each method is appropriate.

1. Top-down estimating

   • Uses overall project cost estimates based on historical benchmarks or analogous projects.
   • Useful early when scope is incomplete, but risk of low accuracy later.
   • Example: “Similar campus renovation projects averaged R2.8 million; our project is comparable in size.”

2. Bottom-up estimating

   • Builds cost estimates from the Work Breakdown Structure (WBS) down to work packages.
   • More accurate because it links directly to deliverables and activities.
   • Requires detailed scope and resource definition.

3. Analogous estimating

   • A specific top-down approach: compare with similar projects.
   • Works when historical data exists and project similarity is credible.

4. Parametric estimating

   • Uses mathematical relationships (e.g., cost per square metre, cost per unit output).
   • Often used for construction, IT infrastructure, or capacity-based projects.

5. Three-point estimating

   • Uses optimistic, most likely, and pessimistic estimates to model uncertainty.
   • Frequently associated with PERT concepts.

Linking budget to the WBS (the Wits Plus emphasis)

A common exam question asks you to explain why the WBS is the backbone of budgeting.

The logic is:

• The WBS defines what work must be done.
• Each WBS work package has cost drivers (labour hours, quantities, unit rates).
• Budgeting aggregates work package estimates to produce the project total.
• Financial control then monitors actual spending at the same cost breakdown level.

If your budget is not traceable to the WBS, you lose control granularity: you might know you are overspending, but you cannot identify the work package causing it.

Budgeting steps: a practical workflow

A strong answer normally includes a sequence. One such exam-ready workflow is:

1. Confirm scope baseline
   • Ensure the budget corresponds to approved scope (not “wish list” items).
2. Create or refine WBS and work packages
3. Assign resources and labour time
   • Identify roles, rates, productivity assumptions.
4. Estimate quantities and unit rates
5. Calculate work package cost estimates
6. Add escalation and contingency
   • Contingency should be linked to risk, not used as “extra money” for convenience.
7. Aggregate to cost baseline
8. Time-phase budget
   • Create a cashflow or monthly spending curve.
9. Obtain approvals
10. Set up control mechanisms

• Coding structure, reporting cadence, variance thresholds.

Time-phased budgets and cashflow awareness

Exams frequently test the difference between:

• Total project budget (Rands allocated overall), and
• Cashflow / time-phased budget (how much is expected each month/quarter).

A project can overspend relative to total budget but still be cashflow-stable, or vice versa. Financial control therefore often includes both:

• Cost performance (total and at cost categories), and
• Cash management (payments, invoices, commitments, receipts timing).

Budget baselines and control levels

You should also understand the idea of a baseline:

• The baseline is an approved benchmark.
• It is updated only through change control.
• Variance analysis compares actuals (and forecasts) to the baseline.

In Wits Plus–type applied learning, students are expected to appreciate the governance: a budget that changes informally each week is not a control baseline; it becomes noise.

2) Financial Control Systems: Monitoring, Reporting, and Variance Management

What “financial control” really means

Financial control is the process of ensuring project financial performance matches plan, by:

• measuring actual expenditure and commitments,
• forecasting future costs,
• analysing deviations (variances),
• and initiating corrective actions through agreed decision rules.

Control is not only a reporting activity; it is a feedback loop.

A useful way to structure your exam response:

1. Measure (collect actual and earned information)
2. Compare (against baseline and standard rates)
3. Analyse (why variance occurred)
4. Decide (approve changes, corrective actions)
5. Act (procure, replan, renegotiate, reallocate resources)
6. Update (forecast, schedule, and risk register where needed)

Key financial terms you must handle correctly

Exams often penalise confusion between these terms:

• Budget (planned value): what you planned to spend.
• Actual cost (AC): what you actually spent.
• Commitments: signed contracts / purchase orders that obligate spend, even if invoices aren’t fully paid yet.
• Forecast (EAC): expected total cost at completion based on current performance.
• Contingency: reserved amount for defined risks/uncertainty.
• Escalation: allowance for price changes over time.

If you are asked for a variance, you typically need to specify what you compare:

• cost variance = budgeted (or earned) cost minus actual cost (depending on the method used).

Control reporting: cadence and information quality

A good financial control system includes:

• Monthly reporting (or weekly for fast-moving projects)
• Standard templates for:
  • expenditure by cost category,
  • commitments vs actuals,
  • forecast-to-complete,
  • risk-driven contingency usage,
  • and cashflow expectations.

Information quality requirements in exams:

• Timeliness (reports submitted consistently)
• Accuracy (correct coding, correct project reference)
• Completeness (all cost categories included)
• Comparability (same method as baseline)

Variance types: cost variance vs schedule variance (even when the question is “financial”)

Even if the question focuses on budgeting, many exams expect a mention of how schedule affects cost.

• Schedule variance can cause:
  • labour inefficiency (idle time, restart costs),
  • escalation (contract price adjustments),
  • additional overhead (site maintenance),
  • and remobilisation costs.

Therefore, strong answers connect financial control to schedule and scope performance.

Common variance causes (with “what to do next”)

A high-scoring exam response typically includes both causes and corrective actions.

1) Scope changes

• Cause: change requests, additional stakeholder needs.
• Control response:
  • process formal change control,
  • update scope baseline,
  • rebaseline budget where approved.

2) Estimation errors

• Cause: wrong productivity assumptions, incomplete quantities.
• Control response:
  • refine estimates (bottom-up re-estimation),
  • update forecasting logic,
  • improve data capture for future projects.

3) Procurement issues

• Cause: late tendering, poor supplier performance, price increases.
• Control response:
  • renegotiate terms where possible,
  • accelerate procurement where feasible,
  • enforce contract management and claims process.

4) Resource performance

• Cause: skill mismatch, understaffing, learning curve.
• Control response:
  • adjust staffing plan,
  • review productivity,
  • provide training or replace resources.

5) Risk realisation

• Cause: a risk event occurs and contingency is needed.
• Control response:
  • document risk event evidence,
  • release contingency according to governance,
  • update risk register and remaining contingency.

Contingency and escalation: governance and exam pitfalls

A frequent exam question is: “Can contingency be used for any overspend?” The correct logic is usually no without approval.

• Contingency is meant for defined uncertainty—often tied to the risk register.
• Escalation is meant for expected price changes.

If contingency is used for a baseline overspend caused by uncontrolled scope growth, that is a governance failure: it hides the real problem rather than solving it.

Earned Value Management (EVM) concepts (financial control in performance terms)

Some Wits Plus project management courses include EVM-style thinking. Even if full EVM calculation isn’t required, you should understand the logic.

EVM compares:

• Planned Value (PV): what work was planned to be done by a date.
• Earned Value (EV): what work was actually completed in terms of budgeted cost.
• Actual Cost (AC): actual spending for that completed work.

Key interpretive metrics:

• Cost Variance (CV) = EV − AC
• Schedule Variance (SV) = EV − PV

Key implications:

• CV negative indicates spending is higher than value earned.
• SV negative indicates work is behind plan (which can also drive future cost issues).

Even when numbers aren’t demanded, the conceptual explanation is often examinable: financial control should reflect progress/value, not only cash spending.

A worked example for variance reasoning (with consistent numbers)

Consider a project with a monthly control period.

Assume:

• Budget baseline for Month 3 planned spending (PV) = R300,000.
• Work scheduled by end of Month 3 was expected to be worth EV = R260,000 in budgeted cost.
• Actual cost spent by end of Month 3 (AC) = R330,000.

Then:

• CV = EV − AC = R260,000 − R330,000 = −R70,000
  • Interpretation: costs are R70,000 higher than the value of work completed.
• SV = EV − PV = R260,000 − R300,000 = −R40,000
  • Interpretation: project is behind schedule by value terms.

Financial control actions based on this combined variance:

1. Diagnose: is the overspend due to inefficiency (resource/productivity), procurement (price), or rework (quality)?
2. Forecast EAC: if performance continues, expected cost increases.
3. Decide corrective action: recover schedule (if feasible) or stabilise costs (scope clarifications, better procurement planning).

Forecasting: why “EAC” matters more than retrospective variance

In exams, many students can compute variance but struggle with forecasting. The practical logic:

• Variance tells you where you are.
• Forecast tells you where you will end if nothing changes.

A simple exam-friendly approach to forecasting:

• Start with baseline total budget,
• Adjust for:
  • known scope changes,
  • trends in cost performance (e.g., CPI),
  • risk events already occurred,
  • remaining contingency availability.

You may not always need the full formula, but you should show an approach grounded in governance and evidence.

Change control link: updating baseline vs updating forecast

A high-mark differentiator is distinguishing:

• Baseline updates happen through formal approvals after changes to scope/reasons.
• Forecast updates can happen due to performance trend and emerging risks, without necessarily changing the approved baseline (unless governance requires rebaseline).

3) Budgeting Models, Risk-Adjusted Forecasts, and Cash Management

Integrating risk into budgeting (risk-adjusted budgets)

Risk and budgeting are inseparable in project finance. A project budget must include:

• known costs for known scope,
• risk responses for identified risks,
• and contingency aligned to uncertainty.

Two common budgeting patterns:

1. Contingency as a single reserve

   • Pros: simple.
   • Cons: harder to justify release and may hide drivers.

2. Contingency distributed across work packages / risk responses

   • Pros: traceable to risk logic; easier audit trails.
   • Cons: requires mature risk management.

Exams often reward the ability to explain the governance rationale: contingency should not become a substitute for cost control.

Quantifying risk impacts: practical exam-friendly scenarios

A typical question may present a scenario such as:

• There is a probability that a supplier delays by 2 weeks.
• This delay results in additional site overhead of R40,000.
• There is also a possibility of price escalation.

Even if exact expected monetary value (EMV) calculations are not required, you should demonstrate structured thinking:

• list risk events,
• estimate cost/time impacts,
• incorporate probability/impact logic,
• and update contingency and forecast.

A consistent scenario can be used to anchor logic:

• If delay risk has probability 30% and overhead impact is R40,000, expected cost impact = 0.30 × 40,000 = R12,000.
• If the escalation risk has probability 20% with cost impact R25,000, expected impact = 0.20 × 25,000 = R5,000.
• Combined expected risk impact = R17,000 (before considering correlations).

This makes it easier to justify contingency allocations or to adjust risk response priorities.

Cash management vs accrual expenditure (practical differences)

A financial control question can test your understanding that cash and cost are not the same.

• Actual cost (accrual) may be recorded when services are delivered or invoices are approved.
• Cash flow depends on payment terms (e.g., 30-day terms, milestone payments).

A project can appear “under budget” on paper but still face cash crunch if:

• payment schedules require upfront payments,
• retainers are withheld and later settled in lump sums,
• or procurement deposits are paid early.

A strong exam answer includes:

• tracking cash-in/cash-out separately,
• ensuring budget sufficiency for payment milestones,
• monitoring commitments to anticipate future outflows.

Commitments tracking: the missing control lever

If you only track actual payments, you can be surprised by large next-month invoice clusters. Commitments tracking closes that gap.

A commitments ledger typically includes:

• supplier contract value for each procurement package,
• value of work ordered but not yet invoiced,
• expected invoice date,
• and expected payment terms.

Financial control uses commitments to update forecasts and reduce unpleasant shocks.

Forecast accuracy: why “forecast error” is a control topic

Forecasts should be:

• based on evidence,
• updated regularly,
• and calibrated against prior forecast performance.

An exam question may ask: “Why do forecasts often fail?” Common reasons:

• Forecast is based on optimistic assumptions (wishful thinking).
• Data quality is poor.
• Teams do not update forecasts at consistent intervals.
• Incentives discourage reporting bad news.
• Change control is weak, so scope changes appear “late”.

A high mark response would mention the need for:

• forecast assumptions register,
• forecast confidence grading,
• and trend analysis.

Risk-adjusted forecasting methods (qualitative and quantitative)

Risk-adjusted forecasting can be done in:

• Qualitative fashion: “high/medium/low risk; expect cost increase”
• Quantitative fashion: incorporate probabilities, scenario ranges, or Monte Carlo in advanced courses.

For Wits Plus level exam answers, qualitative + scenario ranges are often acceptable if reasoning is strong.

Scenario range example

• Base forecast (best estimate): R2,000,000 total.
• Low-risk scenario: R1,900,000.
• High-risk scenario: R2,200,000.

Then, financial control uses:

• how far actual spending sits from base,
• whether risk triggers have occurred,
• and whether contingency release is justified.

Linking budgeting to procurement and contract management

Budgeting fails when procurement is treated as separate from finance.

Key procurement-finance link points:

• Tender price variability (unit price assumptions).
• Contract type (fixed price vs cost-plus).
• Variation clauses (how scope changes impact payment).
• Retention money and milestone acceptance.
• Time and materials billing.

An exam question may describe:

• a supplier is charging higher labour rates than estimated,
• and you must explain how that affects budget controls.

Correct logic:

• verify contract terms and escalation clauses,
• update estimates if productivity differs,
• reconcile invoicing against contract scope,
• and decide whether additional approvals are required.

Cashflow example: time-phased budget into payment planning

Assume a project with time-phased spending across four quarters:

Quarter	Planned cumulative spend (R)	Payment expectation logic
Q1	400,000	mobilisation + early materials
Q2	900,000	site labour + first contractor milestone
Q3	1,500,000	second milestone + equipment deliveries
Q4	2,100,000	final handover + retention release

If actual cash needs appear earlier (e.g., supplier requests a 50% deposit in Q1), the cashflow plan must be updated even if total cost baseline remains unchanged (unless the contract conditions cause a baseline reforecast).

Financial control uses cash forecasting to prevent:

• failed payments,
• contract breaches,
• and delayed work due to liquidity constraints.

Counter-argument: “Does cash control replace cost control?”

No. Cash control does not replace cost control:

• cash deals with liquidity timing,
• cost control deals with efficiency and total project spending.

Both are required. A project manager may “manage cash” but still waste resources and end with a cost overrun that cannot be funded later.

4) Tools and Techniques for Cost Breakdown, Cost Baselines, and Approval Discipline

Cost breakdown structures: codes, categories, and traceability

In exams, you might be asked: “Explain how you would structure cost coding to support control.”

A practical approach includes:

• Cost account: major component (e.g., Construction, Engineering, Project Management)
• Cost element: direct labour, materials, subcontractors, etc.
• WBS work package link: each cost element maps to work packages.
• Procurement package link: each procurement activity maps to cost categories.

Traceability ensures:

• you can identify what caused overspend,
• you can assign accountability,
• and you can support audit trails.

Building a cost baseline: approved budget by work package and time

A cost baseline is typically created as:

• summary by component (for reporting to stakeholders),
• detail by WBS work package (for operational control),
• and time-phased allocations (for performance measurement and cashflow planning).

An exam answer can describe the difference between:

• total baseline,
• incremental baseline per period (monthly/quarterly),
• and remaining baseline.

Variance thresholds and escalation rules

Strong control systems define:

• acceptable variance thresholds,
• reporting triggers,
• and decision authority.

Example rules (write in your own words in the exam):

• If monthly cost variance exceeds 5%, the project controller must submit a variance explanation and corrective action plan within 3 working days.
• If cumulative variance exceeds 10%, escalate to steering committee for approval of rebaseline or contingency release.
• If forecast-to-complete exceeds baseline by more than 15%, stop discretionary spending until approval is obtained.

Even if your exam does not provide numbers, the principle of thresholds is often expected.

Budget change control: what counts as a baseline change?

A frequent exam theme is governance discipline.

Not every change needs rebaseline. Rebaseline is typically required when:

• scope changes materially,
• contract prices change due to approved variations,
• material changes in delivery approach occur.

Whereas forecast updates are required when:

• performance trend changes,
• delays occur due to factors within project influence,
• risk triggers occur.

Students should clarify:

• forecast changes are operational and iterative,
• baseline changes are governance-controlled.

A structured example: baseline vs forecast and approved changes

Consider a project with:

• Approved total cost baseline = R2,100,000 (from the cashflow example earlier: Q4 cumulative spend 2,100,000).
• After Q2, actual performance indicates that labour productivity is lower than expected.

Suppose by end of Q2:

• Planned cumulative spend = R900,000.
• Actual cumulative spend is R980,000.
• Earned value suggests only R850,000 of work is completed value-wise.

Implications:

• cost variance negative and schedule behind.
• forecast-to-complete likely increases.

Now assume the forecast model updates expected total cost:

• from R2,100,000 baseline to R2,250,000 forecast.

If this increase is due to productivity issues (which might be corrected by management action without scope change), governance may not require immediate rebaseline; it depends on decision policy.

But if, during Q3, the client approves an additional scope feature requiring new work package cost of R80,000, then baseline rebaseline is usually needed:

• new approved total baseline = R2,100,000 + R80,000 = R2,180,000 (assuming the feature adds net cost and no offsets are approved).
• Then the forecast might be compared again.

The exam insight: baseline change requires approvals tied to scope, while forecast changes reflect operational reality.

Counter-argument: “Just revise the baseline each time variance appears”

This approach undermines control because:

• it eliminates meaningful benchmarks,
• it makes performance measurement less credible,
• it can hide accountability issues,
• and it becomes harder to audit decisions later.

Correct practice:

• update forecasts frequently,
• update baseline only when warranted by approved scope/contract changes or governance decisions.

Documented assumptions: protecting the budget against ambiguity

Many budgeting exam questions are indirectly about assumptions management.

Assumptions that should be documented:

• unit rates and wage assumptions,
• productivity assumptions (units per labour hour),
• lead times and delivery schedules,
• price escalation rates,
• exchange rate assumptions if importing goods,
• uptime assumptions for equipment,
• acceptance criteria for work completion.

If assumptions change, the forecast should reflect that, and where necessary change control should consider whether the scope definition or cost basis should be reapproved.

Accounting alignment: project code in the organisation’s chart of accounts

Another exam-ready topic is alignment with organisational accounting systems.

The budget should map to:

• the chart of accounts categories,
• cost centres and project codes,
• and invoice categorisation.

Without this mapping:

• actuals cannot be reliably extracted,
• variance analysis is delayed,
• and audit risk increases.

Reconciliation: actuals, invoices, and accrual adjustments

To achieve financial control:

• reconcile procurement records (commitments, purchase orders),
• with finance records (invoices, payments, accruals).

Common reconciliation issues include:

• late invoice processing,
• coding errors,
• duplicate invoices,
• scope mismatches (invoice includes items outside scope),
• and retention settlement timing.

Exams may provide a short scenario and ask “what should you check first?” A high-quality answer lists these reconciliation controls.

5) Integrated Cost Performance Management: Practical Scenarios, Ethics, and Exam-Ready Templates

Integrated thinking: budget, scope, schedule, and governance

Project budgeting and financial control are not stand-alone. They are integrated into:

• scope control (what is being delivered),
• schedule control (when work occurs),
• quality management (rework costs),
• procurement and contract management,
• and stakeholder governance (approvals and reporting).

A high-quality exam answer therefore shows how these domains interact.

For instance:

• If quality issues cause rework, costs rise (financial control).
• If rework causes delays, schedule variance rises and may increase overhead (again financial).
• If delays trigger contractual penalties or accelerate costs, the budget baseline may need review (governance link).

“Exam scenario” case study: campus facility upgrade (time, scope, and cost control)

To build exam realism, consider a scenario that mirrors typical South African project management contexts such as university infrastructure and facilities upgrades.

Scenario details

• Project: “Campus facility upgrade”
• Work includes:
  1. refurbishment of interior rooms,
  2. electrical upgrades,
  3. installation of basic ventilation improvements,
  4. commissioning and handover.
• Baseline total cost: R2,100,000
• Time-phased baseline: Q1 R400,000, Q2 cumulative R900,000, Q3 cumulative R1,500,000, Q4 cumulative R2,100,000.

Month/quarter control events

• Q1: Procurement takes longer due to tender queries; spending is lower than planned (underspend).
• Q2: Spending catches up; labour productivity is lower due to learning curve and rework from initial workmanship issues.
• Q3: Client requests an additional ventilation improvement (scope change).
• Q4: Final handover requires extra testing, partially covered by contingency but also requires schedule recovery.

Financial control outcomes

1. Underspend in Q1
   • Not necessarily “good performance”.
   • It might indicate delay in starting work and risk of cost increase later.
2. Cost overrun driven by rework in Q2
   • Financial control must link to quality reports and root cause analysis.
3. Scope change in Q3
   • Requires change control: baseline revaluation likely needed.
4. Contingency usage in Q4
   • Must align with defined risks and documented evidence.

This scenario tests the integrated approach expected in exams: budgeting and control require evidence, traceability, and governance.

Worked numeric scenario: how a scope change affects budgeting

Let’s make the scenario consistent with a baseline change.

Assume in Q3 the client approves an additional feature with net cost impact:

• Additional scope cost = R80,000

So:

• Original baseline = R2,100,000
• Approved baseline after scope change = R2,180,000 (R2,100,000 + R80,000)

Now suppose by end of Q4:

• Actual total cost = R2,235,000

Then the final cost variance relative to the updated baseline is:

• Cost variance = Actual − Approved baseline = R2,235,000 − R2,180,000 = R55,000 over baseline

If the project used contingency appropriately, you can explain:

• part of overrun may be residual effects (productivity, minor risk realisation),
• and remaining overrun might require corrective action next cycle (estimate refinement).

Ethics and integrity in financial control (commonly assessed indirectly)

Financial control is also about ethics because “bad reporting” can be used to:

• meet performance targets artificially,
• conceal inefficiency,
• or delay escalation until it is too late.

Ethical controls include:

• accurate time recording for labour charges,
• truthful commitment tracking,
• prompt invoice review,
• and transparent communication of forecast risk.

In exam answers, you can score by stating:

• budget reporting must be verifiable,
• and contingency should be released only with justified reasons.

Exam-ready templates: how to structure a 10–15 mark answer

Many Wits Plus exam questions expect a structured, coherent response. A reliable template:

1. Define budgeting and financial control in a sentence each.
2. List key elements of a project budget:
   • cost categories,
   • WBS link,
   • contingency/escalation,
   • time-phasing,
   • baseline approval.
3. Explain the financial control loop:
   • measure (actuals/commitments),
   • compare (baseline),
   • analyse (variance causes),
   • decide (corrective action and change control),
   • update forecast (and baseline if approved).
4. Mention tools (EVM logic, variances, forecasting, commitments tracking).
5. Provide a worked mini-example (even one set of numbers).
6. Conclude with the importance of governance, traceability, and timely reporting.

Mini worked example set (for speed in exams)

To prepare effectively, you need fast recall. Use the following mini-examples.

Example A: deciding whether to release contingency

Assume:

• Risk event occurs with documented evidence.
• Estimated impact = R30,000.
• Remaining contingency = R20,000.
• New escalation occurs adding additional impact = R12,000.

Control logic:

• Remaining contingency can cover R20,000 (partial).
• The additional R22,000 must be addressed via:
  • change request approval if scope-related,
  • reforecast and steering committee approval,
  • or cost reduction actions elsewhere.

This shows you understand contingency boundaries.

Example B: interpreting an underspend

Assume:

• PV by end of a month = R200,000
• EV = R150,000 (less work completed than planned)
• AC = R140,000 (spending lower)

Then:

• SV = EV − PV = R150,000 − R200,000 = −R50,000 (behind schedule)
• CV = EV − AC = R150,000 − R140,000 = +R10,000 (cost performance looks favourable)

Interpretation:

• “Good CV” could be misleading.
• Project is behind schedule (SV negative); later catch-up may raise costs.
• Financial control should therefore focus on schedule recovery plan, not only the CV.

Example C: cashflow vs cost

Assume:

• Actual invoices processed this month = R120,000
• Payments made this month = R60,000 due to 60-day payment terms

Exam logic:

• Cashflow control must use payment schedule.
• Cost control uses accrual/earned records (depending on accounting basis).

Common exam traps and how to avoid them

1. Treating contingency as free money
   • Fix: link it to risks and approvals.
2. Comparing actuals to wrong benchmark
   • Fix: specify PV, EV, or budget baseline depending on method.
3. Confusing schedule variance with cost variance
   • Fix: interpret both; explain interaction.
4. Ignoring procurement and commitments
   • Fix: show awareness of purchase orders/contracts.
5. Mixing cashflow and cost
   • Fix: separate liquidity from expenditure.

Practical “control dashboard” elements (what to show in reporting)

Even if not requested, listing dashboard components helps demonstrate control maturity.

A typical project financial dashboard includes:

• Budget baseline total and remaining budget
• Expenditure to date (actuals)
• Commitments to date
• Forecast at completion (EAC)
• Variance summaries:
  • cumulative cost variance,
  • forecast variance,
• Contingency remaining and contingency used
• Risk triggers and their financial impact
• Cashflow projection (next 3–6 months)
• Procurement status (contracts awarded vs planned)

This helps ensure that financial control is not a late-stage activity but part of regular decision-making.

Integrating corrective actions into financial control reporting

Exams love “what do you do next?” So your answer should tie variances to corrective actions.

Corrective actions can include:

• Replanning: adjust activity sequence and resource allocation
• Resource changes: add staff, replace underperforming teams, improve training
• Procurement actions: renegotiate lead times, expedite shipments, revise supplier strategy
• Scope control: clarify requirements to reduce rework and prevent uncontrolled scope growth
• Quality interventions: early testing to reduce rework costs
• Contract claims: pursue supplier claims if contract conditions were breached
• Stakeholder communication: request approved changes where needed

A mature financial control answer explicitly states which action is applied and why it reduces variance or prevents recurrence.

Putting it all together: an end-to-end exam narrative

If an exam question asks you to discuss project budgeting and financial control comprehensively, the best answers usually follow an end-to-end narrative:

1. Build budget from WBS (cost estimate + quantities + unit rates).
2. Add contingency linked to risks; include escalation logic if relevant.
3. Time-phase budget to reflect expected spending and cash requirements.
4. Approve cost baseline and set reporting cadence.
5. Track actual costs, commitments, and progress.
6. Analyse variances using appropriate comparisons (PV/EV/AC logic or budget vs actual logic).
7. Forecast EAC and update assumptions.
8. Implement corrective actions, and if scope changes are approved, update baseline via change control.
9. Report transparently, ethically, and consistently.

Final checklist for exam success (quick revision)

• Budget = structured cost plan: categories + WBS traceability + time-phasing + contingency/escalation.
• Baseline = approved benchmark; updated only through approved change control.
• Control loop = measure → compare → analyse → decide → act → forecast/update.
• Commitments must be tracked, not only paid invoices.
• Cashflow differs from cost; both matter.
• EVM logic (PV/EV/AC) helps interpret performance beyond raw spending.
• Variance causes drive corrective actions; contingency is risk-governed.
• Ethics: accurate reporting and transparent forecasts.

If you want, I can also generate Wits Plus–style exam questions and model answers specifically aligned to these notes (including short scenarios on scope change, contingency release, and cashflow vs accrual confusion).