Audit Committee Reporting Dashboard: Risks and Actions

An audit committee reporting dashboard shows which agreed actions remain open, which are overdue, and where findings have recurred. Use a frozen workbook snapshot with a clear cutoff and separate action IDs from finding IDs. That gives the committee a reliable view of remediation progress without implying that a status summary provides audit assurance.

Define what the committee is reviewing

Consider Cedar Ridge Components, an illustrative US manufacturer preparing its September 30, 2026 committee package. The chief audit executive wants the discussion to focus on overdue high-priority actions, completion claims awaiting verification, and recurring issues by unit.

The IIA Global Internal Audit Standards describe performing internal audit services as including findings, recommendations or action plans, and communication with management during and after the engagement. A dashboard organizes information for that discussion; the underlying audit work and professional conclusions remain separate.

Agree these definitions before calculating:

• Open action: anything without verified closure at the cutoff, including management-reported completion awaiting review.
• Overdue action: an open action with an approved due date before September 30. An item due on the cutoff date is not yet overdue.
• Repeat finding: a finding designated as recurring under the internal audit function's methodology. The report does not infer recurrence from similar wording.
• High priority: the approved priority already recorded against the action. The report does not assign new ratings.

These definitions belong alongside the dashboard. The broader enterprise risk report covers approved exposure and loss registers; this page keeps its focus on audit remediation.

The source workbook

The action register has the following snapshot. Dates are real date values in the workbook, and status means status at September 30, not the latest status when someone later opens the file.

The finding register supplies the repeat designation:

Keep evidence references, accountable owners, approved deadline changes, and verification dates in the underlying workbook. They are omitted from these compact tables but should not be omitted from the working register.

The action table contains six actions against five distinct findings. F1 has two actions. Counting repeated action rows would therefore overstate the number of repeat findings.

Build the committee summary

Summarize actions by unit, then count repeat findings from the separate finding register. The repeat column below includes all findings in this reporting cohort, including F3, whose action is closed.

Open actions are A1, A2, A3, A5, and A6. The overdue subset is A1, A3, and A5; A4's old deadline does not make a verified closed action overdue.

The overdue rate is 3 / 5 = 60.0% of open actions. Verified closure is 1 / 6 = 16.7% of actions in this fixed cohort. Repeat findings are 2 / 5 = 40.0% of distinct findings in the cohort. Percentages are rounded to one decimal place, and each denominator answers a different question.

The committee should see the repeat label's scope. Of the repeat findings, only F1 still has open actions. F3 remains in the cohort's historical repeat count; it is not an outstanding remediation item.

For where this page sits in the board package, see management reporting. Keep the summary short enough that the exception detail can carry the discussion.

Put age and decisions beside the totals

Calculate age from the approved due date to the cutoff, in calendar days. Do not age an action from the audit report date when the question is how late remediation has become.

The differences are September 30 minus August 31 = 30 days, minus September 15 = 15 days, and minus September 20 = 10 days. An aging view therefore contains two actions aged 1-15 days and one aged 16-30 days, totaling the same three overdue actions.

The report preparer should ask owners for explanations and retain their words. An overdue label does not establish why progress slowed, and a new expected completion date should not erase the original deadline from the historical record.

For checking the dashboard's definitions and source consistency, dashboard audit addresses that separate review. It is distinct from reporting an internal audit action's closure status.

Variation: one action receives verified closure

Change one input: A5's status becomes verified closed, supported by a September 29 verification date. Leave every other row and the September 30 cutoff unchanged.

The new overdue rate is 2 / 4 = 50.0%. Verified closure is 2 / 6 = 33.3%. Closing A5 reduces the open and overdue counts, while the historical repeat finding count stays unchanged because F4 was not a repeat finding.

Verification must represent the actual review, not a reporting convenience. As a public-sector example, the IRS internal-control guidance distinguishes implementing corrective actions from validating their expected results. A company should follow its own approved verification methodology; that IRS procedure is not a company reporting requirement.

Where it goes wrong

• Counting action rows as findings. F1 would appear twice and inflate recurrence.
• Closing on a completion claim alone. Keep awaiting-verification status visible under the approved definition.
• Moving the cutoff. Later evidence belongs in a later snapshot unless it confirms a status that already existed at the reporting date.
• Hiding missing due dates. Show undated open actions separately rather than treating them as on time.
• Calling closure control effectiveness. A status change does not establish an audit conclusion or erase a finding's history.

Review your action register in Covirage

Upload a sample of your own action and finding workbooks. Covirage maps the columns, and its tools compute and check open actions, overdue counts, and unit summaries; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your register.

See Covirage for board reporting for the supporting reporting context.