Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 6: Project Cost Estimation, Budgeting and Financial Control

Undergraduate Bachelor of Project Management · Year 2 · Full study notes, applied methods and assessment guide

Chapter overview

Develop reliable project cost estimates, build and manage budgets, control expenditure and forecast financial performance using transparent assumptions and evidence. This chapter integrates foundational theory, professional judgement and practical decision-making. Students should use the material to explain concepts, interpret evidence, solve applied problems and communicate defensible recommendations.

Learning outcomes: define specialist terminology; explain relevant frameworks; apply tools to a realistic project; interpret quantitative and qualitative evidence; evaluate ethical, operational and contextual limitations; and recommend measurable actions.

How to study: read each section, make a concept map, work through the applied examples, attempt the case study independently and answer the examination questions using clear assumptions and justified conclusions.

Learning diagram: Project Cost Estimation, Budgeting and Financial Control

Project contextNeed and scopeAnalyseEvidence and optionsPlanRoles and controlsDeliverCoordinate actionReviewLearn

Use this process map to connect the chapter's specialist tools to the wider project life cycle. The review stage feeds evidence back into planning and future decisions.

Chapter contents

1. The role of cost management2. Cost terminology and cost behaviour3. Cost estimating methods4. Building an estimate from a work breakdown structure5. Cost basis, assumptions and exclusions6. Contingency, management reserve and escalation7. Developing the project budget and cash flow8. Cost baseline and control accounts9. Procurement pricing and whole-life cost10. Financial controls and authorisation11. Recording actual costs and commitments12. Variance analysis and cost reporting13. Earned value management fundamentals14. Worked example: calculating cost performance15. Forecasting estimate at completion16. Managing change and preventing cost overrun17. Cost management in public and donor-funded projects18. Case study: county health facility expansion19. Cost audit, close-out and lessons learnedWorked applicationIntegrated case studyAssessment questions

1. The role of cost management

Project cost management establishes what resources will cost, when funds will be needed and how actual financial performance will be controlled. It begins during concept development and continues through definition, procurement, delivery, commissioning and closure. Early estimates support option selection; progressively detailed estimates support authorisation, tendering and control. A cost plan is not simply a total figure. It explains the scope included, exclusions, price basis, currency, tax treatment, estimate date, escalation assumptions, contingency and confidence level. Without these details, two estimates may appear comparable while describing different obligations.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

2. Cost terminology and cost behaviour

Direct costs can be attributed to a defined work package, such as concrete, specialist labour or equipment hired for a site. Indirect costs support several activities, including project management, security, utilities and shared facilities. Fixed costs do not vary directly with output within a relevant range, while variable costs change with volume. Recurring costs arise repeatedly during operations; one-off costs occur once. Capital expenditure creates or improves an asset, while operating expenditure supports ongoing service. Classification depends on the organisation's accounting policy and the decision being made, so the project manager should work with finance specialists.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

3. Cost estimating methods

Analogous estimating uses actual costs from a sufficiently similar completed project and adjusts for differences in scale, location, scope, timing and risk. Parametric estimating applies a measurable rate, such as cost per kilometre, classroom or square metre, to a quantity. Bottom-up estimating develops estimates for detailed activities and aggregates them. Three-point estimating considers optimistic, most likely and pessimistic values to make uncertainty visible. Expert judgement is useful when evidence is limited, but assumptions and the basis of judgement should be recorded. Combining methods can provide a cross-check rather than relying on a single technique.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

4. Building an estimate from a work breakdown structure

A cost estimate should follow the approved scope and work breakdown structure (WBS). For each work package, identify labour hours, materials, equipment, subcontractors, travel, permits, testing, training and other relevant inputs. Apply rates from current quotations, historical records or approved schedules. Include indirect costs where appropriate and check that shared resources are not counted twice. The estimate should reconcile with the schedule: a longer duration may increase site overhead, equipment hire and supervision. A traceable estimate allows reviewers to see how the total was built and which assumptions drive it.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

5. Cost basis, assumptions and exclusions

A basis-of-estimate document explains methods, data sources, quantity assumptions, productivity rates, price date, currency, exchange-rate assumptions, inflation, tax, location factors and uncertainty. Exclusions are equally important. For example, a construction estimate may exclude land acquisition, utility diversions, financing, client-provided equipment or future maintenance. Exclusions must be explicit because stakeholders may otherwise assume they are covered. Record who prepared and reviewed the estimate, the maturity of design information and the conditions under which the estimate remains valid. Update the basis when scope or market conditions change.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

6. Contingency, management reserve and escalation

Contingency is an allowance for identified uncertainty within the approved scope and risk basis. It should be linked to risk analysis rather than treated as spare money for unapproved additions. Management reserve is generally held outside the performance measurement baseline for unforeseen work within the project scope, subject to governance rules. Escalation accounts for expected price changes over time, while foreign exchange allowances address currency exposure. These concepts should not be combined casually. Define ownership, release authority, reporting and replenishment rules so that reserve use is transparent and does not conceal poor estimating.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

7. Developing the project budget and cash flow

The approved budget allocates funding to time periods and control accounts. A cash-flow forecast predicts when payments and receipts will occur, which may differ from when work is performed or costs are recognised. Deposits, milestone payments, retention, tax dates, grant conditions and delayed client payments can create liquidity pressure even when the total budget appears sufficient. Map the schedule to procurement and payment terms. Forecast monthly cash requirements, identify peak funding needs and update projections when delivery dates or supplier terms change. A project can be under budget overall yet temporarily unable to pay its obligations.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

8. Cost baseline and control accounts

The cost baseline is the approved time-phased budget used to measure cost performance, normally excluding management reserve. Control accounts connect scope, schedule, budget and responsibility at a level where performance can be managed. Work-package budgets should be assigned to accountable owners and linked to deliverables. Baseline changes must follow formal change control; otherwise, performance comparisons lose meaning. Maintain a clear record of original budget, approved changes, transfers, actual cost and forecast cost. A baseline is a management reference, not a reason to ignore a justified change in project conditions.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

9. Procurement pricing and whole-life cost

Purchase price is only one element of economic cost. Whole-life cost may include installation, energy, maintenance, consumables, software licences, training, downtime, disposal and residual value. A low initial bid can create expensive operational obligations or performance risk. Compare options over a consistent period and use transparent assumptions for discount rates, utilisation and replacement cycles. Procurement analysis should also consider supplier capacity, warranty terms, local support, compatibility, sustainability and contractual risk allocation. The lowest evaluated cost is not necessarily the lowest initial price.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

10. Financial controls and authorisation

Financial control establishes who may commit funds, approve invoices, change forecasts, authorise variations and release contingency. Segregation of duties reduces the risk that one person initiates, approves and pays the same transaction. Purchase orders should be raised before commitments where policy requires it. Match invoices to contractual terms, evidence of receipt and authorised variations. Maintain an audit trail for approvals and exceptions. Controls should be proportionate: overly complex procedures can delay delivery, while weak controls expose the project to fraud, duplicate payments, scope leakage and unreliable reporting.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

11. Recording actual costs and commitments

Actual cost records expenditure incurred under the organisation's accounting rules. Commitments represent obligations already entered into, such as signed purchase orders or contracts, even if invoices have not arrived. Accruals estimate costs for goods or services received but not yet invoiced. Forecasts should include actuals, remaining commitments and the expected cost of uncommitted work. Reconcile project records with the finance ledger regularly. Check cut-off dates, coding, duplicate invoices, currency conversion and disputed items. If the team reports only invoices paid, it may underestimate the financial exposure of work already ordered.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

12. Variance analysis and cost reporting

Cost variance compares a measure of planned or earned work with actual cost, depending on the control method used. A variance is a prompt to investigate, not an explanation. Determine whether it arises from quantity growth, price inflation, low productivity, rework, delay, exchange rates, scope change, coding error or timing of records. Report the value, cause, forecast consequence, owner and corrective action. Separate one-off timing differences from persistent trends. Reports should be understandable to sponsors and sufficiently detailed for control-account managers to act.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

13. Earned value management fundamentals

Earned value management integrates scope, schedule and cost through three core measures. Planned value (PV) is the budgeted value of work scheduled by the status date. Earned value (EV) is the budgeted value of work actually completed. Actual cost (AC) is the cost incurred for that completed work. Cost variance is EV minus AC; schedule variance is EV minus PV. Cost performance index (CPI) is EV divided by AC; schedule performance index (SPI) is EV divided by PV. These indicators are meaningful only when progress measurement rules are credible and consistently applied.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

14. Worked example: calculating cost performance

Suppose a project has PV of KSh 4,000,000, EV of KSh 3,600,000 and AC of KSh 4,500,000 at the reporting date. Cost variance equals 3,600,000 − 4,500,000 = −KSh 900,000, indicating that completed work cost more than its budgeted value. CPI equals 3,600,000 ÷ 4,500,000 = 0.80. The project earns KSh 0.80 of budgeted work for each KSh 1.00 spent. Schedule variance equals 3,600,000 − 4,000,000 = −KSh 400,000; SPI equals 0.90. The project is behind its planned value and experiencing cost inefficiency.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

15. Forecasting estimate at completion

Estimate at completion (EAC) forecasts the total cost when the project is finished. If current cost efficiency is expected to continue, a simple formula is EAC = BAC ÷ CPI, where BAC is the budget at completion. If the variance is considered atypical and remaining work is expected to follow the original plan, an alternative is EAC = AC + (BAC − EV). The selected formula must match the reason for the variance and the expected future conditions. Estimate to complete (ETC) is the additional expected cost; variance at completion (VAC) is BAC minus EAC. Forecasts should state assumptions.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

16. Managing change and preventing cost overrun

A proposed change should be assessed for scope, schedule, cost, quality, risk, procurement, operations and benefits before approval. Estimate direct and indirect effects, including design updates, rework, training, licences and maintenance. Identify the funding source and whether the change uses contingency or requires a revised baseline. Unauthorised work should not be hidden inside existing work packages. Early warning indicators include rising commitments, repeated estimate growth, unresolved design questions, low productivity and frequent variations. Recovery actions may include resequencing, value analysis, scope trade-offs or renegotiation, but must not compromise safety or mandatory standards.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

17. Cost management in public and donor-funded projects

Public and donor-funded projects may operate under appropriations, grant agreements, procurement regulations, reporting conditions and restrictions on budget transfers. Funds may be available only within a financial year or approved category. The project team should map each cost to an eligible budget line, retain supporting documentation and understand reporting deadlines. Exchange-rate movement, counterpart funding and delayed disbursement can affect delivery. Transparency, value for money, conflict-of-interest controls and independent audit are particularly important. Never assume that an approved project budget automatically authorises every procurement or reallocation.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

18. Case study: county health facility expansion

A county government plans to expand a health facility with new consultation rooms, a laboratory and solar backup. The initial estimate covers building works but omits laboratory equipment, connection fees, staff training and maintenance. During procurement, imported equipment prices rise and the contractor requests payment for unforeseen ground conditions. Students should map the omissions to the WBS, distinguish scope gap from genuine risk event, test the contract entitlement and update the cash-flow forecast. They should recommend whether to use contingency, seek additional approval, phase the equipment purchase or revise the scope. The answer should protect clinical safety and service continuity.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

19. Cost audit, close-out and lessons learned

Financial close-out confirms that invoices, claims, variations, accruals, assets, retentions and outstanding commitments have been reconciled. Release unused reserves only through authorised processes. Confirm that warranties, licences, maintenance agreements and asset records have transferred to the operational owner. Compare final cost with the approved baseline and explain material variances without concealing scope changes. Capture actual unit rates, productivity, supplier performance and estimate accuracy for future projects. A close-out report should distinguish financial completion from the longer-term question of whether the investment delivers its intended benefits.

Applied analysis: In a real project, the team should identify the decision owner, the evidence required, the people affected and the point at which the issue must be escalated. Translate the concept into an observable action, assign responsibility and record the outcome in the relevant project document. Where several options are available, compare them against agreed objectives and explain trade-offs rather than presenting a preferred option without justification.

Critical reflection: Consider the limitations of the method, the assumptions on which it depends and the conditions that could make its use inappropriate. Test whether the approach remains fair, safe, legally compliant and operationally realistic. Invite challenge from specialists and affected users, and revise the recommendation when new evidence emerges. A sound undergraduate answer explains both how a technique works and why it is suitable in a particular context.

Study checkpoint: Define the key terms, draw the process or relationship, apply it to a project example, identify two risks or limitations and recommend a measurable way to review the result. Use evidence and state assumptions clearly.

Worked application and decision framework

Consider a medium-sized public-sector project with a fixed service deadline, several technical workstreams and a diverse group of users. The project manager first confirms the approved objectives and requirements, then identifies the decision that must be made. Evidence is collected from the schedule, budget, technical specialists, suppliers, operational staff and affected stakeholders. Assumptions are recorded separately from verified facts. Options are assessed against value, feasibility, risk, compliance, equity and lifecycle implications.

Suppose the team identifies three options: proceed with the original plan, introduce a controlled pilot, or defer the change until additional evidence is available. The team should compare direct and indirect consequences, including transition costs, staff capacity, service interruption and future flexibility. A weighted scoring model may structure discussion, but weights should be approved and sensitivity-tested. A high numerical score does not override a mandatory legal or safety requirement.

The recommendation should identify the preferred option, supporting evidence, unresolved uncertainty, resource requirements, approval authority, implementation sequence and review triggers. The decision log should record who approved it and why. After implementation, compare actual results with the expected outcomes and capture lessons. This worked process demonstrates how specialist project management methods connect analysis to accountable action.

Decision quality test: Is the problem defined? Are options genuinely comparable? Are assumptions visible? Are affected people represented? Are risks and lifecycle effects assessed? Is authority clear? Can the outcome be measured?

Integrated case study: Project Cost Estimation, Budgeting and Financial Control in a county service improvement project

A county administration plans a service improvement project across several facilities. The project has a defined funding ceiling, a public launch commitment, limited specialist staff and communities with different access needs. During implementation, the team receives new information that challenges an assumption in the original plan. A supplier, operational manager and community representative propose different responses. The sponsor expects a recommendation supported by evidence and a realistic implementation route.

As a student, prepare an analysis using the chapter concepts. Identify the objective and decision boundary; distinguish facts, assumptions, issues and uncertainties; identify affected stakeholders; compare at least three response options; explain the effect on scope, time, cost, quality, risk and benefits; and recommend controls. State what additional evidence would change your recommendation. Include an action owner, due date, escalation threshold and measurable indicator.

In your discussion, consider fairness, accessibility, environmental and social impacts, data protection where relevant, and the ability of the operational team to sustain the outcome. Explain how you would communicate the decision to the sponsor, delivery team, supplier and community. Conclude with a short learning review describing what should be recorded for future projects.

University examination and revision questions

1. Explain the central purpose of project cost estimation, budgeting and financial control.

Model answer: Define the concept, explain why it matters to project objectives and show how it links with scope, schedule, cost, quality, risk, stakeholders and benefits. A strong answer uses a relevant example and distinguishes the method from the outcome it is intended to support.

2. Discuss four factors that influence the selection of an appropriate method.

Model answer: Consider project scale and complexity, uncertainty and data quality, regulatory and safety obligations, organisational capability, stakeholder needs, lifecycle consequences and the cost of analysis. Explain why the factors may lead to different choices in different contexts.

3. Apply the chapter framework to a project that is experiencing a significant change.

Model answer: Confirm the baseline and reason for change, identify impacts and affected parties, develop feasible options, assess evidence and risks, obtain authorised approval, update relevant plans and communicate the decision. Monitor implementation and verify whether the expected result was achieved.

4. Evaluate the limitations of relying only on numerical indicators.

Model answer: Indicators depend on definitions, data quality, timing and assumptions. They may hide distributional effects, emerging risks or user experience. Pair metrics with qualitative evidence, specialist judgement, audit trails and stakeholder feedback. Explain uncertainty rather than presenting a score as a complete description.

5. Explain how ethical and sustainability considerations should influence project decisions.

Model answer: Identify who receives benefits and who bears costs or risks. Consider legal duties, fairness, accessibility, worker and community welfare, environmental effects, lifecycle resource use and transparency. Demonstrate how these considerations affect option appraisal, controls, engagement and monitoring.

6. Prepare a concise recommendation for a project sponsor.

Model answer: State the decision required, preferred option, evidence, assumptions, expected benefits, costs, main risks, alternatives rejected, approvals needed, implementation responsibilities and review triggers. Use plain language and distinguish facts from estimates.

7. Short notes: define key terms, compare two approaches and identify one practical limitation for each.

Model answer: Award marks for accurate definitions, a meaningful comparison, contextual examples and balanced evaluation. Avoid listing terms without explaining their relevance to project decisions.

8. Essay: “Project success depends on more than delivering outputs on time and within budget.” Discuss.

Model answer: Explain the importance of time and cost while examining quality, safety, user adoption, benefits, sustainability, governance and operational readiness. Use examples to show why an efficient delivery process can still fail to create useful outcomes.

Revision checklist and further independent study

For further study, consult current project management textbooks, recognised professional standards, national procurement and safety regulations, institutional library resources and sector-specific guidance. Check publication dates and local applicability. Professional standards and laws can change; students should use the edition and jurisdiction specified by their institution or project sponsor.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.