Solution · Internal audit engagements
09
Internal audit on the same graph, behind its own wall.
The audit universe, annual plan, engagements, and workpapers sit on the same graph as the controls being audited, and the auditee never sees past the independence wall.
The shape of the problem · 01
What this actually feels like.
- 01The audit universe is a spreadsheet that drifted away from the control library years ago.
- 02Workpapers sit on a shared drive with no link to the controls they test.
- 03Auditors work in the same tools as the people they audit, so independence rests on trust.
- 04Drafting the findings and the risk-and-control matrix eats the week after fieldwork.
How Zovos handles it · 02
Five steps, one graph.
Every step writes back to the same controls, policies, and issues your team already owns. There is no second source of truth.
- 01PlanBuild the audit universe and the annual plan on the same graph as the controls, risks, and programs they cover, so coverage is derived instead of kept in a parallel spreadsheet.
- 02RequestSend PBC audit requests to auditees. They see only the requests addressed to them and their own management responses, never the workspace, plan, or workpapers.
- 03FieldworkWork each engagement in one workbench, with workpapers linked to the controls being audited and aligned to IIA GIAS 2024.
- 04DraftWorkpaper, finding, and RCM drafters do the first pass, proposing findings, root causes, and control mappings. The auditor reviews and signs every draft.
- 05ReportFindings flow into the governed findings queue for remediation. Sign-off independence is enforced, so an internal-audit principal cannot approve a decision it may later audit.
What changes · 03
What the product does instead.
Coverage
The annual plan shows coverage derived from the real control and risk estate.
Independence
It is enforced at sign-off and by the wall, not by policy alone.
Drafting
Agents draft workpapers, findings, and the RCM. An auditor signs.
Standards
Engagements map to IIA GIAS 2024, one of the 54 frameworks in the corpus.
Want to see this on your library?
Bring a control library, a policy, and one regulator paragraph that gives you trouble. We target two-week onboarding.