For the Internal Audit Head
Close audit findings and stop them recurring
An audit function is judged on whether findings stay closed. That requires each finding to be linked to the control gaps and incidents that caused it.
Questions you can answer at any time
- What is our repeat-finding rate, and is it falling?
- Which findings link to a control gap that is still open today?
- Which corrective actions are overdue, by how long, and who owns them?
- For any control tested last cycle, what evidence was provided and was it valid at the time?
Each answer links to the control, evidence, owner and date behind it.
Today
The situation today
The same audit findings come back each year. Evidence requests go out by email and replies arrive late or incomplete. Certification audits and internal reviews use separate trackers that disagree.
The same findings return
When a finding is closed by marking a ticket done without fixing its cause, it returns the next cycle and the audit function loses credibility.
Evidence gathering takes most of the audit
Chasing evidence by email uses the fieldwork budget on administration instead of testing.
Internal and external audits disagree
When internal reviews and certification audits use separate trackers, they give two versions of a control's status, and both get quoted.
With xmodo
What changes
One process for every audit
Internal readiness audits and certification audits use the same process for findings and corrective actions. All audits are tracked in one place.
Scoped evidence requests
Auditors request evidence through a portal. They see the same evidence your team manages, including whether each item is still valid.
Root causes addressed
Findings link to the control gaps and incidents behind them, so your team fixes the underlying cause when it closes a finding.
For the committee: the rate of repeat findings, and whether it is falling.
Your first week
Your first week with xmodo
Day 1
Set up one readiness audit with your own scope, severity scale and methodology.
Day 3
Send scoped evidence requests through the portal. Auditors see the same evidence your team manages, including whether it is still valid.
Day 5
Raise one finding, link it to the control gap behind it, and see the corrective action receive an owner and a due date.
What you own
Reports you can produce
Audit programme with scope, schedule and testing status
Findings register linked to control gaps, incidents and corrective actions
Evidence request log showing what was provided, by whom and when
Closure report showing the linked control gaps and incidents that were resolved
Modules
The modules you would use
Frequently asked questions
Can external audit firms use the portal at no cost?
Yes. External auditors get access to the engagement's evidence requests at no charge. They see only what the engagement scope allows, and every access is logged.
How is finding severity configured?
Your organisation sets its own severity scales to match your audit methodology. Severity sets the expected resolution times and how overdue corrective actions appear on the dashboard.