How can audit context be reused across an engagement?
Audit context should be captured once and used wherever it is relevant. Process understanding, system scoping, risks, controls and evidence are connected; treating them as separate documents creates duplication and inconsistency.
A walkthrough may explain how revenue is initiated, approved, recorded and reported. The same evidence can inform the process narrative, process map, risk assessment, control identification, IT scoping and planned response. If each part is prepared independently, teams repeat questions, copy text between files and risk changing one conclusion without updating another.
AI makes reuse more practical because it can structure unstructured evidence and maintain links between related objects. A control identified during process understanding can be connected to the relevant risk, supporting evidence, design assessment and later operating-effectiveness work. Reviewers can then see how the conclusion developed rather than reading isolated documents.
The value is not only time saved. A connected audit file is easier to review, easier to update and more consistent from planning through completion. The firm should still control which conclusions carry forward and require revalidation when evidence or circumstances change.
Platformed capability: Platformed creates connected process, system, risk and control objects from the same body of evidence. A change to a process or control can therefore be reviewed in context rather than copied independently across several working papers.
References: ISA 315 risk assessment resources · Platformed financial audit