How does Acuna GRC show audit readiness?
Direct answer
Acuna GRC does not reduce audit readiness to one typed-in number. Readiness shows in what the platform computes: health on every control, measure and requirement, rolled up from task completion on a worse-wins rule, compliance KPIs on the Assure dashboard, and the records behind each control.
For a given audit, you set Period from and Period to, and its Records section groups linked records as In period, Undated and Other periods, hiding nothing. Open issues and corrective actions sit beside it, so before the auditor arrives you can see which controls ran, which records cover the period and what is still open.
What does an auditor actually check?
Whatever the framework, an auditor asks three questions. Is the requirement addressed by a practice that exists? Did the control that checks it operate, and is there proof covering the period under review? When something failed, was it recorded, corrected and verified?
The standards make this explicit. ISO/IEC 27001:2022 requires documented information to be controlled (clause 7.5), internal audits to follow an audit programme with retained results (clause 9.2), and nonconformities and corrective actions to be recorded with their results (clause 10.2). A SOC 2 Type 2 report gives an opinion on whether controls operated effectively throughout a period, so proof from a single day is not enough.
Being ready therefore means being able to answer those questions for every requirement in scope, before the auditor asks.
Why does Acuna GRC not give one readiness score?
A single typed-in percentage hides exactly what an auditor will find: the one control that stopped running, the records that fall outside the period, the corrective action that was implemented but never verified. Averaging strong and weak areas into one figure makes the weak ones disappear.
Acuna GRC shows readiness through values it computes and that can be traced:
- Health on every control, measure and requirement, rolled up on a worse-wins rule, so one failure is not offset by a success elsewhere. See how control health works.
- Compliance KPIs on the Assure dashboard. A compliance threshold shows how many items are compliant out of the total, and clicking a value opens the list behind it.
- The records behind each control, grouped by audit period.
A widget built on records your access profile hides is hidden rather than miscounted, so a figure never claims more than you can see.
How do you prepare an audit in Acuna GRC?
1. Plan the audit in a program, with its type (Internal, External or Certification), planned date, lead auditor and auditee, and link the requirements, measures and documents in scope.
2. Set Period from and Period to. The Records section groups linked records as In period, Undated and Other periods, and hides nothing.
3. Use the global scope filter to limit tables and dashboards to the entity, site or business unit being audited, and narrow compliance KPIs to the framework and its domains.
4. Check health on the requirements in scope, and open the Health tab of any unhealthy control to see which input fails.
5. Review open issues and corrective actions, and the exceptions accepted with their end dates.
6. Generate a report from a template for the period and scopes. Each generation is saved as a snapshot.
What the audit finds is then logged as issues linked to the audit and to the requirement or control concerned, each with a corrective action to verify before closing. See the Assure workspace.
What are the most common readiness gaps?
- Undated records, which cannot be placed in the audit period.
- Controls with no schedule, which are never due and so never show as failing.
- Documents past their yearly review date, which pull down the documentation dimension of the measures they support.
- Corrective actions marked implemented but never verified.
- Exceptions past their Valid until date, or gaps accepted informally with no exception at all.
- Evidence gathered in the last week before the audit instead of as the work was done. See how evidence lifecycle works.
How Acuna GRC handles it
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Solution
Audit preparation
See which records are ready and which are missing, run an internal audit, close findings before the auditor arrives, and prepare it with Swiss experts.
- Module
Evaluations
Spot evaluations and gap assessments, answered in the app or through a portal, frozen on the day, with findings and exceptions tracked to closure.
Sources
- ISO/IEC 27001:2022, clauses 7.5, 9.2 and 10.2
- AICPA & CIMA, SOC 2 (System and Organization Controls)
- Acuna GRC, Assure workspace
This page explains the rules in general terms and is not legal advice.
Frequently asked
Can readiness be shown per framework?
Yes. Compliance KPIs can be narrowed to the frameworks of your programme and their domains, and the global scope filter limits the view to the scopes being audited.
Does Acuna GRC support internal audits as well as certification audits?
Yes. An audit can be Internal, External or Certification, and audits are planned in programs with a frequency and dates.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

