Pre-audit planning
Study the prior audits, see where risk concentrates, and decide who to talk to and what evidence to request before fieldwork starts.
Planning
- Prior audits
- Risk concentration
- People to interview
- Evidence to request
Audit period 1 Jan – 30 Jun 2026 · scope saved
Pre-audit planning · Atlas Financial
The homework before fieldwork
Prior audits for this auditee, where risk concentrated, who to talk to, and what evidence to ask for, drawn from the work papers the firm already holds and the evidence already supplied.
Starting…
A concept simulation of a planned product. Watch it play, or pressTry it yourself to click through.
What it is
The homework step before fieldwork, where risk-based planning will live; reserved on the audit map in this release.
What you do, as the auditor
- 1Open the Pre-audit planning card in the Planning band of the audit map, once scope is set.
- 2Read the prior audits for the same auditee and where risk concentrated in them.
- 3Decide who to interview and what evidence to request, so fieldwork starts with the right people and documents.
- 4Today: see the card on the audit map; the workbench is not available yet.
On the roadmap
This is on the roadmap. The simulation above is a concept: it shows the intended flow, and screens and behaviour will change.
What it will do
What pre-audit planning will do
Prior audits for the auditee
The read behind the card already returns whether the audit has evidence and which prior audits exist for the same auditee. The workbench will build on those signals rather than start from nothing.
Where risk concentrates
Risk-based planning in the ISACA sense, understanding how the area works and where risk sits before the procedures are chosen. Inherent, control, and detection risk are a later expansion of this step.
Who to talk to and what to request
Turn the planning read into interviewees and evidence requests, so the voice interview and the evidence intake open with the right people named and the right documents asked for.
An honest reserved state
The card is visible and muted. The read returns the reserved state and its reason, and no completeness figure, no risk figure, and no invented number of any kind.
Deliberately not in scope
- Risk appetite and risk tolerance; a later expansion of this feature.
- Blocking fieldwork or the audit programme on planning; neither waits on it in this release.
- A second audit objective or a phase of its own; pre-audit planning is one step of Planning.
Why the card is on the map before the workbench exists
The audit map follows the ISACA Planning phase, and pre-audit planning is one of its steps, reached after scope and before the procedures are determined. Leaving it off the map would tell the auditor that the product skips a step the profession does not. Showing a card that claims planning happened, or that carries an invented completeness figure, would be worse. So the card is visible from the first day of the audit, muted, and not reachable, with a reason that says plainly that the workbench is not available yet. A dedicated read backs it, returning the reserved state and the signals the workbench will later consume: whether the audit has evidence, and the prior audits for the same auditee. It returns no completeness score and no risk figure.
What the workbench will do
Pre-audit planning is the homework before fieldwork: studying prior audits, understanding how the area under review works, where risk concentrates, who to talk to, and what evidence to request. The workbench will put that work inside the audit, reading the prior audits Run Audit already holds for the same auditee and the evidence already linked, and ending in a list of interviewees and evidence requests the fieldwork phase can act on. The full risk assessment, with inherent, control, and detection risk and the firm’s risk appetite and tolerance, is a later expansion of this same step rather than a new feature. In this release fieldwork and the audit programme do not wait on it. Which prior-audit signals the workbench consumes first is an open question in the PRD.
Products
The other products
AI document auditing
AvailableUpload the evidence the auditee already keeps, test the controls against it, correct and sign off the work papers, issue the report.
For the auditor
- NIST CSF
- DORA
- GDPR
- ISO 27001
- PCI DSS
- SOC 2
Voice interview
PlannedInterview the auditee from inside the audit and keep what was said as evidence a work paper can cite.
For the auditor
Cloud configuration review
PlannedConnect a cloud account read-only and test the selected controls against its live configuration, from inside the audit.
For the auditor
- NIST CSF
- ISO 27001
- SOC 2
- PCI DSS
Follow-up on audit
In developmentKeep every work paper with a gap open past report issue, request corrective-action evidence from the auditee, and close only on signed-off evidence.
For the reviewer and audit manager
- NIST CSF
- DORA
- GDPR
- ISO 27001
- PCI DSS
- SOC 2
See it on your own evidence
A walkthrough takes forty minutes: one framework, a handful of controls, and the documents an auditee already keeps.