Timedora

Reporting and Following Up on Audit Findings

A practical lesson on validating audit findings, communicating results, planning corrective action, and verifying follow-up.

Validate the and Its Evidence

Build the from the gap

A explains a meaningful difference between —what should be happening—and —what auditors verified is happening. Add cause (why the gap occurred) when evidence supports it, and effect (the actual or potential consequence) to explain why the gap matters. These elements should clarify the issue and support corrective action; they are not boxes to fill with guesses. In particular, do not state a speculative cause or an unquantified effect as established fact.

The audit’s refund example shows how the elements fit together:

Policy requires supervisory approval before refunds exceed $1,000 (). In 12 of 40 sampled refunds above that amount, the files contained no recorded approval (). Staff reported that the system does not require an approval entry (cause, if corroborated). Without a preventive or detective control, unauthorized refunds may go undetected (effect).

The sample result is a verified observation. The staff explanation is a reported explanation, not automatically a verified cause. The possible effect describes exposure, not proof that unauthorized refunds occurred. Keeping those distinctions clear makes the useful without overstating what is known.

Test the evidence and limit the conclusion

Before reporting, check that evidence is relevant to the audit objective and reliable enough to support the reported facts and conclusions. Confirm calculations, sample sizes, dates, and references, and consider contradictory evidence. State the extent of the work and the nature and extent of the issue.

For example, the 12 exceptions among 40 sampled files support reporting that result for the sample. They do not, by themselves, establish the same exception rate for every file in the population. A population-wide projection requires a sampling design that supports it. If the results cannot be projected, limit the conclusion accordingly.

Discuss draft facts with responsible managers and seek relevant records or explanations. This can reveal errors, missing context, or additional evidence. Resolve factual disagreements where possible; document material disagreements that remain, including each party’s rationale. A management explanation deserves consideration, but it does not require auditors to accept an unsupported claim or abandon an independent conclusion.

Communicate Results for the

Make the message clear, fair, and relevant

A final communication should connect the audit’s to its conclusions, significant findings, and any applicable recommendations or action plans. Explain why each matters and prioritize issues by significance and risk. Disclose scope limitations that affect interpretation so readers do not infer more than the audit established.

Use direct language, define technical terms, and give enough context for readers to understand both the issue and the work supporting it. Aim for communication that is objective, balanced, complete, concise, constructive, and timely. If a significant matter needs prompt attention, communicate it before the final report when appropriate rather than waiting for the full report.

Tailor detail without changing the facts

Different readers need different emphasis. Operational managers need enough detail to correct a process. Senior leaders and oversight bodies need to understand the significance of the issue, the exposure, and any decisions required. Tailoring affects presentation and detail—not the underlying evidence or the limits of the conclusion.

When applicable, include management’s response and identify agreed actions, the responsible owner, and the target date. If management and auditors disagree about results or actions, use the organization’s established process to document their positions and seek resolution. Clearly presenting a response does not mean endorsing it; the communication should preserve the evidence-based audit conclusion while giving readers relevant context.

Turn Findings into Practical Action

Make the response address the gap

A recommendation or agreed action should address the gap between and and reduce the related risk to an acceptable level. Where the cause is known, addressing it can help prevent the gap from recurring. Actions should be feasible, proportionate to risk, and specific enough for progress to be assessed.

Auditors may recommend a particular control, offer options, or ask management to develop an . Management generally owns implementation; the auditor’s role is to assess whether the proposed response adequately addresses the . In assessing a plan, consider costs, benefits, resources, dependencies, and the organization’s risk tolerance.

Specify how progress and completion can be checked

A useful identifies:

  1. Action and purpose: What will be done, and which risk or cause it addresses.

  2. Owner: Who is accountable and has authority to carry it out.

  3. Timing: A target date and, where helpful, milestones.

  4. Evidence and effectiveness: What will show the action was completed and how its effectiveness can be assessed.

The refund-control example makes the difference between a testable plan and a vague instruction clear: by September 30, the finance director will configure the system to block refunds over $1,000 until a supervisor approves them. Internal audit will later test a sample of qualifying refunds for recorded approval. This names an action, an owner, a deadline, and evidence that can be checked. “Improve refund controls” does not specify what will change or how anyone will know whether it worked.

Verify Actions and Escalate

Verify completion and effectiveness

Maintain a record of findings, assigned actions, owners, due dates, status, and supporting evidence. has two distinct questions: Was the action completed? and Did it actually reduce the risk? A policy being issued or a task being marked complete may show activity, but does not by itself establish that the risk fell.

Choose verification procedures suited to the risk. They may include inspecting records, retesting controls, interviewing responsible staff, or analyzing later transactions. Document the procedures and results so the basis for the conclusion is clear.

Respond to delay or weak results

If an action is overdue or ineffective, reassess the with management and agree on further steps or an updated date. Escalate significant unresolved risks through established governance channels. If management accepts the risk of taking no action, communicate that decision to the appropriate authority.

Audit’s role is to monitor and verify, not to take over management’s responsibility for managing risk. The point of is to establish, with supporting evidence, whether the agreed response was implemented and whether it achieved its intended effect.

  • : A person accountable for carrying out an action, with authority to do so.