An audit recommendation is a proposed action from the internal auditor so that the condition audited matches the criteria, its risk falls to an acceptable level, and the cause of the finding is addressed. A good recommendation is specific, testable, has an owner, and is agreed with the auditee, so that it actually gets carried out.
This article explains how to write audit recommendations based on the Global Internal Audit Standards 2024 from The IIA, particularly Standards 14.4, 15.1, and 15.2, which were read directly from the document. References were checked as of 16 November 2026. This discussion complements the guides to writing an internal audit report and follow-up on audit findings.
What Is an Audit Recommendation?
An audit recommendation is the part of an engagement result that answers the question “so what needs to be done?” once the finding has been presented. The finding explains what went wrong. The recommendation explains the steps to close that gap.
Under Standard 14.4, internal auditors are asked to decide whether to draft a recommendation, request an action plan from management, or agree on an action together. There are four aims: closing the gap between criteria and condition, reducing risk to an acceptable level, addressing the root cause, and improving the activity audited.
So a recommendation is not just a generic suggestion at the end of a report. It is part of a chain of work that starts from criteria, condition, root cause, and impact. A recommendation that does not connect to the root cause almost certainly only patches the symptoms.
What Is the Difference Between a Recommendation, an Action Plan, and a Finding?
The three are often confused in the field. A clear distinction makes reports easier to read and act on.
| Terms | Content | Who prepares it |
|---|---|---|
| Findings | The gap between criteria and condition, along with its root cause and impact | Internal Auditor |
| Recommendations | A proposed corrective action for the finding | Internal auditor, discussed with management |
| Action plan | Concrete steps, the person responsible, and the completion date from the auditee | Auditee management |
Standard 14.4 stresses that auditors must collaborate with management, but implementing the action remains management's responsibility. Auditors do not carry out the fixes on the auditee's behalf.
What Makes a Good Audit Recommendation?
Based on the standards and report-writing practice, an effective recommendation generally meets the following five points.
- Directly tied to the root cause. Standard 14.3 asks auditors to trace the root cause as far as practicable, because a recommendation that addresses the root cause prevents repeat findings.
- Specific and verifiable. The action must be clear enough for the auditor to check whether it has been completed.
- Feasible and reasonable. Standard 14.4 asks auditors and management to evaluate feasibility, including cost-benefit analysis and fit with risk tolerance.
- Discussed with management. Recommendations must be discussed with the management of the activity audited before they are reported.
- Has an owner and a deadline. Standard 15.1 requires the final communication to name the responsible party and the planned completion date.
How Do You Write an Audit Recommendation Step by Step?
The sequence below helps auditors maintain recommendation quality from finding to report.
- Write up the finding in full, with criteria, condition, root cause, and impact.
- Determine the finding's significance level using the methodology set by the chief audit executive.
- Formulate one or more action options that address the root cause, not only the symptoms.
- Discuss them with the management that has authority to change the activity, then test feasibility and cost.
- Request an action plan, person responsible, and completion date that have been agreed.
- Record the outcome in the working papers and include it in the final report reviewed by the chief audit executive.
Documenting each step matters because Standard 14.6 asks for working papers clear enough that another auditor can repeat the work and reach the same result. See also the guides to audit working papers and audit evidence.
What Do Weak and Strong Audit Recommendations Look Like?
The example below is illustrative, to show the difference in wording quality. It is not data from a real engagement.
| Aspect | Weak wording | Strong wording |
|---|---|---|
| Action | Improve the procurement approval process | Set approval authority limits by transaction value and enforce them in the system |
| Person responsible | The relevant department | Head of Procurement Division |
| Deadline | As soon as possible | End of next quarter |
| Completion evidence | Not stated | New policy document and a sample of transactions retested |
Strong wording makes it easier for the auditee to act and for the auditor to check. Weak wording almost always ends up as a follow-up that hangs unresolved.
What If the Auditee Disagrees with the Recommendation?
Disagreement is normal. Standard 14.4 asks auditors to follow the established methodology so both parties can state their positions and reasons, and then seek a resolution.
According to the implementation considerations of the same standard, the chief audit executive can work with senior management to facilitate resolution. Each party's formal statement can also be attached to the final communication or made available on request.
Management sometimes chooses an alternative action. Standard 15.2 states that if the auditor judges the alternative adequate or better, its progress is monitored until completion.
How Do You Ensure Recommendations Are Actually Implemented?
Standard 15.2 requires auditors to confirm that management implements the recommendation or action plan through an established methodology. That methodology covers three things.
- Asking the auditee about implementation progress.
- Performing follow-up assessments on a risk basis.
- Updating the status of actions in the tracking system.
The extent of procedures is adjusted to the significance of the finding. If a deadline is missed, the auditor must obtain and document management's explanation and discuss it with the chief audit executive. The chief audit executive then assesses whether the delay or senior management's silence means accepting a risk that exceeds tolerance.
The tracking system can be a spreadsheet or software. The same standard notes that a system can automate the flow from risk assessment to completion of the action plan, including reminder emails ahead of deadlines. A practical discussion is in the article handling repeat audit findings.
How Do You Prioritize Recommendations by Finding Significance?
Recommendation priority follows the significance of the finding. Standard 14.3 explains that auditors evaluate existing controls for design and effectiveness, then determine residual risk, meaning the risk that remains even though controls are operating.
In assessing significance, auditors consider the impact and likelihood of the risk, risk tolerance, and other factors that matter to the organization. Rating or ranking findings can also help management sequence its action plans.
- High significance: actions need short deadlines and tighter follow-up.
- Medium significance: actions are scheduled within the normal work cycle with periodic monitoring.
- Low significance: can be communicated in other ways and verified selectively.
The three-level split above is only an example. The scale used follows the methodology set by the chief audit executive in your organization, as Standard 14.3 notes.
What Happens If Management Chooses to Accept the Risk?
Management has the right to decide to accept a risk, but there are limits. Standard 11.5 requires the chief audit executive to communicate the level of risk that is unacceptable.
If the chief audit executive concludes that management has accepted a risk beyond the organization's risk appetite or tolerance, it is discussed with senior management. If it remains unresolved, the matter is escalated to the board. The standard also makes clear that resolving that risk is not the chief audit executive's responsibility.
For cases like this, the implementation considerations suggest documentation covering a description of the risk, the reason for concern, the reason management did not carry out the recommendation, who accepted the risk, and the date of discussion. That record protects the auditor and the organization if questions arise later.
What Are Common Mistakes in Writing Audit Recommendations?
- Too general. Phrases such as “improve oversight” cannot be tested.
- Only addressing symptoms. The root cause is not traced, so the finding returns next year.
- Not discussed beforehand. The auditee learns of the recommendation only after the report is issued.
- No owner and no deadline. Nobody feels ownership of the action.
- Ignoring cost. An action whose cost far exceeds the risk is hard to get approved.
- The auditor takes over execution. This blurs roles and weakens independence.
How Does Audit Software Help Manage Recommendations?
In audits that span units and years, recommendations easily get scattered across files and emails. Audit management software helps collect findings, recommendations, and follow-up status in one place.
Audithink is internal audit management software. Its features page lists management of findings, recommendations, and notices, follow-up monitoring, and automated reports and dashboards. The application supports the audit team's workflow, but it does not replace the auditor's judgment and is not an audit performer.
Frequently Asked Questions about Audit Recommendations
What does an audit recommendation mean?
An audit recommendation is a corrective action proposed by the internal auditor in response to a finding. Under Standard 14.4 of GIAS 2024, the action aims to close the gap between criteria and condition, reduce risk to an acceptable level, address the root cause, and improve the activity audited.
Who is responsible for carrying out audit recommendations?
Auditee management is responsible for carrying out the corrective action. Internal auditors collaborate in formulating recommendations and action plans, but Standard 14.4 states that implementing action on findings is management's responsibility, not the auditor's.
Must audit recommendations be discussed with the auditee first?
Yes. Standard 14.4 requires auditors to discuss recommendations with the management of the activity audited. Early discussion helps test feasibility, cost, and fit with risk tolerance, so the recommendation is more likely to be accepted and carried out.
What happens if the auditee rejects an audit recommendation?
The auditor follows the methodology for resolving differences of opinion so both parties can state their positions and reasons. The chief audit executive can work with senior management, and each party's formal statement can be attached to the final communication, in line with the implementation considerations of Standard 14.4.
How do auditors monitor the implementation of recommendations?
Under Standard 15.2, auditors ask about progress, perform risk-based follow-up assessments, and update the status of actions in the tracking system. If a deadline is missed, management's explanation is documented and discussed with the chief audit executive.
What is the minimum content of recommendations in a final audit report?
Standard 15.1 requires the final communication to include the objectives, scope, recommendations or action plans where applicable, and the conclusion. For assurance engagements, findings and their significance are added, along with the responsible party and the planned completion date for the action.
Conclusion
An audit recommendation that gets carried out comes from a clear root cause, discussion with the auditee, a firm owner and deadline, and disciplined monitoring. Standards 14.4, 15.1, and 15.2 provide a framework that can be applied right away.
If your team wants to manage findings and follow-up in one flow, schedule an Audithink demo.



