How does evidence lifecycle management work in a GRC platform?
Direct answer
In Acuna GRC, evidence is kept as records in the Assure workspace: proof that a control ran or a task was done, unchanged once made. A record has a name, a type, a collection date and an owner, with files or links attached, and a record with neither shows the gap.
Records are created as work happens: completing a task or a control execution lets you link or create a dated record on the spot, and a checklist run creates its record automatically. Records link to controls, measures, requirements, audits and issues, and an audit period groups them as In period, Undated or Other periods.
What are the stages of the evidence lifecycle?
Whatever tool you use, evidence goes through the same stages:
- Collection: proof is produced when the work is done, with a date and the name of the person who did it.
- Linking: the proof is attached to the control, measure or requirement it supports, so it can be found from either side.
- Review: before an audit, someone checks that the proof covers the period under review and that nothing is missing.
- Use: the auditor samples it, and findings, corrective actions and exceptions refer back to it.
- Renewal: the next execution of the control produces fresh proof, and older records remain as history.
ISO/IEC 27001 asks for this without calling it a lifecycle. Clause 7.5 requires documented information to be controlled, including its version, approval, availability and retention. Clause 9.1 requires the results of monitoring and measurement to be retained, clause 9.2 the audit programme and audit results, and clause 10.2 the nonconformities, the actions taken and their results. See which documents ISO 27001 requires.
How is evidence collected in Acuna GRC?
Acuna GRC calls evidence records. References still start with EVD-, and a record is unchanged once made, so it shows what was true when it was collected.
Most records are created as a by-product of the work:
- Completing a task, including a recurring one, lets you link or create a typed, dated record on the spot, and the completion entry names who did the work. See how recurring tasks work.
- Recording a control execution from My Actions does the same.
- A checklist run, answered and signed item by item on a computer or a phone, creates its record automatically, with a PDF of the signed run.
- Connectors feed control values and KPI measurements, and the API can record control executions, so values from connected services arrive dated.
The rest is added in the Records register with a name, a type, a collection date and an owner, then files or links. A record with neither shows the gap, so an empty placeholder does not pass for proof.
How does evidence reach the auditor?
Records link to controls, measures, requirements, audits, issues, corrective actions and treatment plans, so an auditor can follow the trail from a requirement to the measure that meets it, the control that checks it and the records that show the control ran. The register filters by linked control, measure or requirement and by a two-date Collected filter.
For each audit you set Period from and Period to. Its Records section then groups linked records as In period, Undated and Other periods, and hides nothing: an undated record is visible as such rather than silently counted. What the audit finds is logged as issues linked to the audit and the control concerned, and each issue can lead to a corrective action that keeps implementation apart from verification. See how Acuna GRC shows audit readiness and the Assure workspace.
What are the common mistakes?
- Collecting proof at audit time. Screenshots gathered the week before the audit show the state on that day, not that the control ran throughout the period.
- Undated or unowned proof. Without a collection date and a name, a file cannot be placed in the audit period or tied to the person accountable.
- Proof filed per framework. The same access review saved three times for three frameworks drifts out of sync. Link one record to the control, and let the control serve every requirement it meets.
- Overwriting old proof. Replacing last quarter’s file with this quarter’s erases the history an auditor samples.
- Placeholders. A record with a title and nothing attached is a gap, and should be treated as one.
How Acuna GRC handles it
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Module
Integrations and API
Connect Acuna GRC to the security, identity, device, HR, cloud, code, scanner and ticketing tools you already run, with webhooks and an API.
- 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.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is evidence the same as documented information in ISO 27001?
Evidence is part of it. ISO 27001 uses documented information for both documents, such as policies, and records retained as proof, such as monitoring results, audit results and nonconformities. In Acuna GRC, policies live in Documents and proof lives in Records.
Who should collect the evidence?
The person who does the work, at the moment it is done. The control owner or task assignee attaches the record on completion, and the compliance lead reviews coverage before the audit rather than gathering files on everyone’s behalf.
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)

