How AUD candidates should distinguish performance audits, program-specific audits, state and local reviews, and other governmental engagements from ordinary financial statement audits.
Governmental work is not limited to financial statement audits and Single Audits. Public-sector auditors may be asked to evaluate program performance, test a specific grant program, review compliance with a state statute, or report on a narrow operational objective.
The AUD exam usually tests these engagements by changing the objective. If the objective is fair presentation of financial statements, ordinary audit reporting logic still matters. If the objective is economy, efficiency, effectiveness, program results, or compliance with specified criteria, the auditor must apply the standards and reporting model that fit that objective.
flowchart TD
A["Governmental or specialized engagement"] --> B{"Primary objective"}
B -- "Financial statement fairness" --> C["Financial audit with applicable GAAS and Yellow Book layers"]
B -- "Federal-award compliance" --> D["Single Audit or program-specific audit"]
B -- "Economy, efficiency, effectiveness, or program results" --> E["Performance audit"]
B -- "Specific state, local, grant, or contractual criteria" --> F["Compliance or specialized attestation engagement"]
C --> G["Opinion and required internal-control or compliance reporting"]
D --> H["Compliance opinion, findings, questioned costs, or agency-specific report"]
E --> I["Findings, conclusions, and recommendations"]
F --> J["Report against specified criteria"]
The first exam move is to identify what the auditor is being asked to report on. Similar-sounding governmental engagements can produce very different reports.
| Engagement clue | Likely engagement | Reporting focus |
|---|---|---|
| “Are the financial statements fairly presented?” | Financial audit | Financial statement opinion plus required governmental reporting layers. |
| “Did the entity comply with federal program requirements?” | Single Audit or program-specific audit | Compliance opinion, internal control over compliance, findings, and questioned costs. |
| “Did the program operate efficiently or achieve intended results?” | Performance audit | Findings, conclusions, and recommendations rather than a financial statement opinion. |
| “Did a department follow a state statute or grant agreement?” | Compliance or specialized engagement | Compliance with specified criteria. |
| “Were procedures performed for a regulator or oversight body?” | Agreed-upon procedures or specialized report | Procedures and factual findings if no assurance is provided. |
Do not assume every governmental engagement is a Single Audit. Single Audit rules apply when the entity expends federal awards above the applicable threshold and the engagement is within the Uniform Guidance framework.
A performance audit evaluates a government program, activity, function, or operation. The objective may involve economy, efficiency, effectiveness, internal control, compliance, program results, or prospective analysis.
| Performance-audit objective | What the auditor evaluates |
|---|---|
| Economy | Whether resources are acquired at reasonable cost and without avoidable waste. |
| Efficiency | Whether resources are converted into outputs with appropriate effort and cost. |
| Effectiveness | Whether the program achieves intended objectives or outcomes. |
| Internal control | Whether controls support reliable operations and compliance. |
| Compliance | Whether the program follows relevant laws, regulations, contracts, or grant terms. |
| Prospective analysis | Whether forecasts, alternatives, or policy options are supported by reasonable methods. |
Performance audits often use interviews, observation, data analysis, benchmarking, document inspection, and sampling. They are evidence-driven, but the report usually communicates findings and recommendations rather than an audit opinion on financial statements.
Performance audit findings are normally built around criteria, condition, cause, and effect.
| Finding element | Meaning | Exam cue |
|---|---|---|
| Criteria | The standard, requirement, benchmark, or expected condition. | What should have happened? |
| Condition | The actual situation identified by the auditor. | What did happen? |
| Cause | The reason the condition occurred. | Why did the gap occur? |
| Effect | The consequence or potential consequence. | Why does the gap matter? |
| Recommendation | The auditor’s proposed corrective action. | What should management or officials consider doing? |
The recommendation should follow from the finding. A vague recommendation such as “improve controls” is weaker than one tied to the identified cause and effect.
A program-specific audit focuses on one federal program rather than the full Single Audit package. It may be used when an auditee expends federal awards under only one federal program and the program’s laws, regulations, or grant agreement do not require a financial statement audit.
| Feature | Program-specific audit | Single Audit |
|---|---|---|
| Scope | One federal program. | Financial statements plus major federal programs. |
| SEFA role | May be narrower or replaced by program-specific schedules depending on requirements. | SEFA is central to the reporting package. |
| Compliance testing | Focused on the selected program’s direct and material requirements. | Focused on major programs selected through the Uniform Guidance approach. |
| Reporting | Agency or program instructions may shape the report. | Uniform Guidance reporting package requirements apply. |
The exam trap is treating a program-specific audit as a shortcut that avoids compliance testing. It does not. The scope is narrower, but the compliance work can still be detailed.
State and local governments often operate under laws, ordinances, budget rules, and grant requirements that add engagement-specific criteria. The auditor must locate the applicable criteria before designing procedures.
| Specialized review | Common criteria | Typical auditor focus |
|---|---|---|
| Budgetary compliance | Adopted budget, appropriations law, or state budget rules. | Whether spending exceeded authorization or was charged to the wrong purpose. |
| Procurement review | State procurement statute, local purchasing policy, or grant terms. | Competition, approvals, conflict-of-interest rules, and documentation. |
| Public works or capital projects | Bond covenants, grant agreements, contract terms, or engineering certifications. | Eligible costs, change orders, retainage, and project documentation. |
| Education or school-district programs | State education rules, federal program rules, or local board policy. | Eligibility, attendance counts, use of restricted funds, and reporting. |
| Public housing or social-service programs | Agency handbooks, regulations, and grant agreements. | Beneficiary eligibility, rent or benefit calculations, allowable costs, and records. |
These engagements may use Yellow Book standards, attestation standards, agency instructions, or a combination. The report should make the criteria and scope clear so users do not mistake a narrow compliance review for a broad audit opinion.
Specialized governmental engagements require evidence that fits the objective. A performance audit may depend heavily on operational data and interviews. A compliance review may depend on grant files and eligibility records. A program-specific audit may depend on the award agreement and agency compliance supplement.
| Evidence source | Best use |
|---|---|
| Statutes, regulations, contracts, and grant agreements | Identify criteria and reporting requirements. |
| Budgets and appropriation records | Test legal authorization and spending limits. |
| Program data | Evaluate outputs, outcomes, timeliness, and efficiency. |
| Beneficiary or participant files | Test eligibility and documentation requirements. |
| Procurement files | Test competition, approval, allowability, and conflict-of-interest rules. |
| Prior findings and corrective action plans | Assess recurring issues and management follow-up. |
Documentation should connect the objective, criteria, procedures, evidence, findings, and report language. Thin documentation is especially risky when the engagement is used by legislators, grantors, inspectors general, or public oversight bodies.
Use this sequence for specialized governmental engagement questions: