Study guide
6.4 Following Up Findings & Recommendations
EPSO Auditors Open Competition AD7, Field of Audit
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Competition Structure & Reasoning Tests
1.1 Competition Format, Eligibility & Selection Rules 1.2 Verbal Reasoning: Text Analysis & Deductive Logic 1.3 Numerical Reasoning: Ratios, Percentages & Data Interpretation 1.4 Abstract Reasoning: Pattern Recognition & Matrix Sequences
2 Chapter 2: Auditing Frameworks, Standards & Professional Ethics
2.1 International Standards on Auditing (ISA) & IAASB Framework 2.2 Public Sector Auditing: INTOSAI & ISSAI Architecture 2.3 The IIA Global Internal Audit Standards (IPPF) 2.4 Professional Ethics, Independence & Professional Skepticism
3 Chapter 3: Audit Risk Assessment & Materiality
3.1 Strategic & Annual Audit Planning 3.2 Understanding the Entity, Environment & Inherent Risk (ISA 315) 3.3 The Audit Risk Model: Inherent, Control & Detection Risk 3.4 Materiality, Performance Materiality & Tolerable Misstatement (ISA 320)
4 Chapter 4: Audit Evidence, Procedures & Sampling
4.1 Sufficient Appropriate Audit Evidence & Financial Assertions (ISA 500) 4.2 Substantive Testing & Substantive Analytical Procedures (ISA 520) 4.3 Audit Sampling: Statistical, Monetary Unit Sampling & Sampling Risk (ISA 530) 4.4 Audit Documentation, Working Papers & Audit Trails (ISA 230)
5 Chapter 5: Internal Control Systems & IT Audit
5.1 COSO Framework: The Five Components & Seventeen Principles 5.2 Tests of Controls, Walkthroughs & Evaluating Deficiencies (ISA 265) 5.3 IT General Controls (ITGC) & Automated Application Controls 5.4 CAATs, Data Analytics & Continuous Auditing 5.5 Audit Methodology, Tools & Knowledge Management
6 Chapter 6: Performance Auditing & The Three Es
6.1 Principles & Mandates of Performance Auditing (ISSAI 300/3000) 6.2 The Three Es: Economy, Efficiency & Effectiveness 6.3 Audit Findings (Condition, Criteria, Cause, Effect) & SMART Recommendations 6.4 Following Up Findings & Recommendations 6.5 Leading & Coordinating Audit Assignments
7 Chapter 7: Fraud Risk, Compliance & Investigative Bodies
7.1 Fraud Risk Assessment, Fraud Triangle & ISA 240 7.2 Compliance Auditing: Legality, Regularity & ISSAI 400/4000 7.3 EU Anti-Fraud Architecture: OLAF, EPPO & Irregularity Reporting
8 Chapter 8: Audit Reporting & Opinions
8.1 Audit Opinions: Unmodified, Qualified, Adverse & Disclaimer (ISA 700/705) 8.2 Key Audit Matters (KAM), Emphasis of Matter & Other Matter Paragraphs 8.3 ECA Annual Reports, DAS & Special Reports 8.4 Quality Assurance & Peer Review
9 Chapter 9: EU Financial Governance & Budget Architecture
9.1 The EU Budget, Multiannual Financial Framework & Own Resources 9.2 The EU Financial Regulation: Budgetary & Financial Principles 9.3 Budget Implementation Modes: Direct, Shared & Indirect Management 9.4 The Annual Discharge Procedure & Parliamentary Oversight (CONT)
10 Chapter 10: EU Written Test (EUFTE) & Reserve List Strategy
10.1 EUFTE: Official Format & Written-Communication Anchors 10.2 Source-Based Drafting Under Time Pressure 10.3 Reserve List & Institution-Led Recruitment
6.4 Following Up Findings & Recommendations
Key Takeaways Explain This Topic AI
Follow-up determines whether agreed action addresses the risk behind a finding, not merely whether management reports an action as complete.
Recommendations need a responsible owner, target date, priority and a clear statement of the intended risk reduction or result.
Evidence and follow-up depth should be proportionate to risk; high-risk actions may require reperformance, inspection or data testing.
Partial, alternative, overdue and risk-accepted actions require transparent assessment and escalation under the relevant governance process.
Closure should record the evidence, evaluator, date, residual risk and basis for the conclusion.
Last updated: October 2026
6.4 Following Up Findings & Recommendations
An audit recommendation has little value if no one determines whether corrective action actually reduced the identified risk. Annex II therefore names following up findings and recommendations and monitoring implementation as part of audit execution.
Follow-up is not a new audit of everything. It is a focused assessment of management's response to the condition, cause, effect and risk documented in the original finding.
Design recommendations for follow-up
A followable recommendation identifies the outcome needed without unnecessarily prescribing management's exact design. Record:
- the finding and risk it addresses;
- the agreed action or management response;
- the responsible owner;
- the target date and priority;
- expected evidence or success indicator; and
any governance body responsible for accepting residual risk.
Vague wording such as “strengthen controls” makes closure subjective. A stronger result statement might require that privileged access be approved, periodically reviewed and promptly removed, with retained evidence.
Maintain a reliable action register
The register should link each action to the final report, owner, due date, risk rating, status, evidence and follow-up conclusion. Protect it against unauthorised alteration and preserve an audit trail of revised dates or actions.
Management owns implementation and should update status. Audit owns the independent assessment of whether the response is adequate. A self-reported “complete” status is evidence to evaluate, not the closure decision.
Plan risk-based follow-up
Set timing and depth according to significance. A low-risk documentation issue may be checked through a revised procedure and a small sample. A critical access-control finding may require configuration inspection, user-list analysis, reperformance of periodic reviews and testing that terminated users were removed promptly.
Consider urgency, implementation complexity, dependency on a larger project and whether delay extends exposure. Combine follow-up work when several recommendations depend on the same system or governance change, but preserve a conclusion for each action.
Evaluate implementation
Use sufficient, relevant evidence. Common procedures include document inspection, inquiry corroborated by records, observation, reperformance, data analysis and limited transaction testing. Ask two separate questions:
Was the agreed or alternative action implemented as represented?
Does it address the original risk to an acceptable degree?
An action can be implemented but ineffective. For example, management may issue procurement guidance yet leave the approval workflow unchanged and show continued non-compliance. Conversely, management may choose a different control that addresses the risk more efficiently. Evaluate substance, not wording identity.
Status conclusions
Use clear categories defined by the organisation, such as open, in progress, implemented, partly implemented, superseded or risk accepted. Avoid “closed” as a convenience for old items. For partial implementation, state what is complete, what remains and the residual exposure.
If management proposes risk acceptance, confirm that the authorised level understands the nature and consequence of the exposure. The audit function does not assume management's responsibility by accepting the risk itself. Where residual risk appears outside appetite or authority, escalate through the applicable governance channel.
Overdue actions require more than reminders. Reassess risk, obtain a revised plan where justified, and report persistent delay or repeated extensions. Do not reset the original due date without preserving the history.
Report and close
Periodic reporting should highlight high-risk overdue actions, recurring themes, disputed conclusions and systemic dependencies. Avoid reporting only completion percentages: ten closed low-risk actions can obscure one critical unresolved weakness.
A closure record should identify the evidence reviewed, procedures performed, evaluator, date, conclusion and residual risk. If follow-up reveals a materially different issue, consider separate audit work rather than silently expanding the original recommendation.
Validate the completeness of the action population as well as individual statuses. Reconcile the register to issued reports, agreed management responses and governance minutes so that omitted or renumbered actions cannot disappear from monitoring. Where one recommendation contains several commitments, define whether each component must be complete before closure; avoid using an average completion percentage that conceals an unresolved critical element.
Mini-case
An audit found that terminated contractors retained application access. Management marks the action complete after issuing a policy requiring same-day removal. Follow-up compares HR termination records with access logs, identifies two late removals and finds that the systems are not integrated. The policy exists, but the control is not operating consistently. The appropriate conclusion is partial implementation, with the residual exposure and required next step reported—not closure based on the policy document alone.