Comprehensive Audits, Value-for-Money Audits, and Program Evaluations

Apply assurance judgment to comprehensive audits, value-for-money audits, program evaluations, and operational audits.

Special assurance engagements often look beyond historical financial statements. They may ask whether resources were used economically, operations were efficient, programs achieved intended outcomes, or controls support public accountability.

The practical task is to define the accountability question, subject matter, criteria, users, and evidence sources before choosing procedures or making recommendations.

What This Lesson Covers

This lesson focuses on how to:

  • identify when financial statement assurance does not answer the stakeholder’s accountability question
  • distinguish comprehensive audits, value-for-money audits, program evaluations, operational audits, and compliance-oriented assurance
  • apply economy, efficiency, effectiveness, and related public-accountability concepts
  • prioritize special engagement topics based on significance, risk, evidence availability, and usefulness
  • adjust assurance strategy and procedures for non-financial subject matter
  • connect observations, criteria, findings, root causes, recommendations, and communication

Engagement Types And Focus

These engagements differ mainly by subject matter and criteria. The case may not label the engagement, so infer it from the user need.

Engagement focus Main question Typical evidence
Comprehensive audit Is the entity managing resources and responsibilities in a way that supports accountability? Strategy documents, governance minutes, budgets, control reports, performance results, and stakeholder requirements.
Value-for-money audit Are resources acquired and used with economy, efficiency, and effectiveness? Procurement files, cost comparisons, service levels, process data, outcome measures, and benchmarks.
Program evaluation Is the program achieving intended objectives and outcomes? Program logic, eligibility data, outcome metrics, surveys, case files, and funding agreements.
Operational audit Are operations designed and controlled to achieve objectives efficiently and reliably? Process maps, control evidence, cycle times, staffing data, exception reports, and performance dashboards.
Compliance-oriented assurance Is the entity complying with rules, policies, agreements, or legislation? Criteria documents, transaction tests, approvals, filings, correspondence, and exception logs.

Financial statement assertions may still matter in some areas, but they are usually not enough. A program evaluation may need outcome data. A value-for-money audit may need process and benchmark evidence. A compliance engagement needs the criteria from the agreement, policy, law, or funding condition.

Economy, Efficiency, And Effectiveness

Value-for-money work often turns on the distinction among economy, efficiency, and effectiveness.

Dimension Practical meaning Example procedure
Economy Resources are acquired at appropriate cost and quality. Compare procurement process, vendor selection, contract terms, and price benchmarks.
Efficiency Inputs are converted into outputs without unnecessary waste or delay. Analyze cycle time, rework, idle capacity, staffing, and process bottlenecks.
Effectiveness Outputs and outcomes meet intended objectives. Compare program results to stated targets, eligibility rules, and stakeholder outcomes.
Equity or accessibility, if relevant Services reach intended users fairly and consistently. Analyze service access, regional coverage, wait times, and exception patterns.
Sustainability, if relevant Operations can continue without creating unacceptable financial, operational, or social risk. Inspect long-term funding, asset condition, workforce capacity, and risk mitigation plans.

These dimensions should not be treated as synonyms. Paying too much for supplies is an economy issue. Long wait times caused by rework are an efficiency issue. Failure to achieve intended program outcomes is an effectiveness issue.

Project Priority Risks

Comprehensive audit projects should be prioritized where the subject matter is significant and evidence can lead to useful recommendations.

Risk factor Why it increases priority
High public or stakeholder interest The engagement can improve accountability and user confidence.
Large spending or high asset value Economy or efficiency issues may have material resource impact.
Weak governance or monitoring Oversight failures may allow problems to persist.
Poor performance against targets Effectiveness may be impaired.
Complex service delivery or many delivery partners Accountability may be unclear and controls may be inconsistent.
History of complaints, errors, or delays Prior evidence suggests operational or program risk.
New program, system, or funding model Criteria, controls, and performance measures may not yet be mature.

A broad topic such as “review the program” is usually too vague. The stronger focus identifies a specific risk area, such as eligibility controls, procurement economy, wait-time efficiency, or outcome reporting reliability.

Strategy And Procedure Adjustments

Special engagements require procedure design that fits the subject matter. Standard financial statement procedures may be useful, but they rarely answer the whole question.

Objective Strategy adjustment
Assess program effectiveness Define intended outcomes, evaluate measures, test data reliability, and compare results to criteria.
Assess procurement economy Inspect procurement policy, tendering, approvals, vendor evaluation, contract terms, and price comparisons.
Assess process efficiency Map the process, identify bottlenecks, test cycle times, and compare resources used to outputs.
Assess compliance with funding agreement Identify criteria, select transactions, test eligibility and reporting, and evaluate exceptions.
Assess governance over a public program Review roles, accountability reporting, board or committee oversight, and follow-up of prior recommendations.
Assess operational controls Test control design and operating effectiveness over the process objective.

Recommendations should flow from evidence-supported findings and root causes. If the finding is slow processing, the recommendation should address the bottleneck or control failure, not simply say “improve efficiency.”

Application Framework

Step Question Output
1. Accountability question What does the user need to know? Engagement purpose.
2. Subject matter What activity, program, resource use, control, or compliance area is evaluated? Engagement focus.
3. Criteria What benchmark, policy, objective, agreement, or standard applies? Evaluation basis.
4. Evidence What records, data, interviews, observations, or benchmarks are needed? Procedure plan.
5. Finding and response What conclusion and recommendation follow from the evidence? Reportable finding and communication.

Use this sequence when a case involves public accountability, program delivery, grant or funding requirements, operational performance, service outcomes, or value-for-money concerns.

Common Pitfalls

Pitfall Correction
Using financial statement assertions for every special engagement. Define criteria that fit program, operational, compliance, or value-for-money objectives.
Treating economy, efficiency, and effectiveness as synonyms. Identify whether the fact pattern concerns cost, process, or outcomes.
Recommending improvements before proving the finding. Obtain evidence, compare to criteria, and identify root cause before recommending action.
Selecting a broad audit focus that cannot be performed. Choose a focused, criteria-based subject matter with available evidence.
Ignoring user needs. Tie scope and reporting to the stakeholders who need the assurance.

Key Takeaways

  • Special engagements begin with subject matter, criteria, users, and accountability need.
  • Value-for-money work distinguishes economy, efficiency, and effectiveness.
  • Project priority depends on significance, stakeholder concern, risk, evidence availability, and expected usefulness.
  • Procedures should test program, operational, compliance, or resource-use criteria rather than defaulting to financial statement work.
  • Recommendations should flow from evidence-supported findings and root causes.
Revised on Monday, June 15, 2026