Complete IT Audit Lab 6 – Findings, Reporting & Audit Conclusion

Before you begin

• You have finished Lab 5: submitted the Testing Worksheet and Exception Register and saved the debrief.
• The IT Audit Practical Laboratory is still attached and enabled on your Course Offering.

Open Lab 6

1. Open My Learning and the Course Offering Learning Experience.
2. Open Laboratories and launch IT Audit Practical Laboratory.
3. On the hub, open Practical Audit Lab 6 – Findings, Reporting & Audit Conclusion.
4. Select Start Lab 6 (or Continue Lab 6).

Lab 6 uses the same AkwaabaPay engagement file. You do not re-type Lab 1 risks, Lab 2 controls, Lab 3 procedures, Lab 4 criteria, or Lab 5 exceptions.

Work the engagement

Use the Reporting file menu:

1. Briefing — an exception becomes a finding only when you can defend why it matters. Not every exception belongs in the final report.
2. Labs 1–5 input — your risk register, RCM, audit programme, criteria mapping, and Exception Register.
3. Potential findings — review the Lab 5 carry-forward queue. Convert, merge, track as a minor observation, mark as needing more evidence, or do not report. Record a rationale for the last three.
4. Build findings — write Condition, Criteria, Cause, Effect / Risk, and Recommendation. Rate the finding and explain why the rating is proportionate.
5. Minor observations — useful issues that are not formal findings. They are not counted in the main findings total.
6. Management response — record agreement, action, owner and target date. Evaluate whether the response addresses root cause. Define follow-up evidence.
7. Summary & conclusion — executive summary, overall conclusion, Audit Committee notes, and the reporting-pressure scenario. Rating changes because evidence changes, not because pressure increases.
8. Report preview — open the print-ready report (cover, summary, findings, responses, follow-up, limitations). Use the browser to print or save as PDF.
9. Traceability — every finding should trace back through exception, test, procedure, criterion, control, risk and evidence.
10. Submit — submit the final audit pack (findings, executive summary, and conclusion together).
11. Debrief — answer every “Defend your audit report” question. Completing the debrief marks the engagement complete.

The minimum number of formal findings is the smaller of the configured requirement (initially 3) and the number of Lab 5 exceptions carried forward. Professional accuracy takes priority over hitting a count.

After you submit

The engagement is concluded after the debrief. Your lecturer can review, score, or reopen the file. Previous submitted versions stay on the audit trail.

If you are stuck

Use Help search for “IT Audit Lab 6”, or ask your lecturer. Do not ask colleagues to share a model report — different teams may reach professionally defensible outcomes.