Firm and engagement isolation
Row-level security in the database keeps each firm’s data apart, and within a firm an engagement is visible only to its team.
Platform overview
One Engagement File, From Planning to Archive
Audit Workspace keeps every stage of an engagement in a single file. Each stage reads the work of the stage before it, and moves forward only when its checks pass.
Three kinds of engagement
AuditFinancial statement audits under the International Standards on Auditing.
ReviewReview engagements under ISRE 2400 (Revised), with inquiry and analytical procedures.
Agreed-upon proceduresEngagements under ISRS 4400 (Revised): the agreed procedures and the findings.
Stage 1
Planning
Planning builds the picture of the entity and the risks in its financial statements, and fieldwork opens only once the planning checks pass and the risk responses are signed.
Understanding the entity
The entity, its environment and its internal control, documented in one place.
Materiality
Overall and performance materiality from the benchmark you choose.
Trial balance and scoping
The imported trial balance, mapped to the chart of accounts, scoped area by area.
Risk register
Each risk of material misstatement assessed and linked to its planned response.
Stage 2
Fieldwork
Fieldwork works through the programmes area by area, with each procedure’s result and evidence recorded where the reviewer will look for it.
Programmes and procedures
From the firm’s methodology library, recorded per audit area with results and exceptions.
Lead schedules
Each area’s balances from the trial balance, under the financial statement headings.
Sampling and journal testing
Samples sized, selected and evaluated; journal entries scored and tested over the ledger.
Adjustments and findings
Raised from a procedure’s exceptions and posted to the trial balance.
Stage 3
Completion
Completion gathers what is still open across the file, so the partner signs off a file whose checks have passed.
Completion checklist
The completion checks and communication with those charged with governance.
Final analytical review
The financial statements reviewed again at the end, with movements explained.
Reports
The planning and completion reports drafted from the file.
Archive
The file archived and kept for the firm’s retention period.
Across the file
Review, Clients and the Record
Preparer and reviewer sign-off
On every paper, with a sign-off log of each signature given, withdrawn or returned.
Review notes
Raised on the paper they are about and assigned within the engagement team.
Client requests and portal
Request documents from the client, who uploads them through a portal the firm opens per engagement.
Time and activity
Time recorded against the engagement, and an activity history of changes to the file.
Security
Security-Conscious Architecture
Audit Workspace runs on Supabase (database, file storage and sign-in) and Vercel (application hosting). These are the controls the application itself enforces.
Two-step sign-in
Every user can turn on an authenticator-app code at sign-in, and idle sessions are signed out after 60 minutes.
Sign as yourself
The database refuses a signature recorded in anyone else’s name, and every signature change is kept in an append-only log.
Stage locks
Once planning is complete, its papers are locked in the database. Changing them means reopening the plan, which is recorded.
Access the firm controls
Firm admins invite, suspend and remove people. Suspending someone ends their access straight away.
No platform access to audit files
Platform support can read an engagement only while the firm grants time-limited, read-only access, shown on every screen of the file.
For details of how data is processed, see the Privacy Policy and the Terms of Service, or contact us with a security questionnaire.
Bring Your Audit Workflow Together.
Discover how Audit Workspace can support a more connected approach to audit planning, execution, review and completion.