Audit asks for evidence, but the team only has verbal assurances. What can we provide?

Insufficient control evidence

Provide truthful records of what was actually performed, distinguishing documented evidence from recollection. Ask the control owner which missing checks can be performed now and recorded accurately. Never backdate an approval or fabricate evidence to make the audit pack look complete.

What to do now

  1. Map each request to its control owner
  2. Collect existing dated evidence
  3. Perform legitimate missing checks where appropriate
  4. Disclose gaps and assign corrective actions
Recommended action flow for insufficient control evidence: Map each request to its control owner then Collect existing dated evidence then Perform legitimate missing checks where appropriate then Disclose gaps and assign corrective actions. Escalate when a required control cannot be evidenced or records appear unreliable.

When to escalate

Escalate when

A required control cannot be evidenced or records appear unreliable.

Who decides

The qualified security privacy legal or control owner

Example

The team records a current access test and openly notes that the earlier review was undocumented.

Mistake to avoid

Creating a retrospective signature that pretends a review happened earlier.

Prevent a repeat

Review access and controls when scope changes; obtain qualified advice for legal, regulatory and high-impact security decisions.

Suggested ApprovedFlow setup

  • Documents
  • Tasks
  • Approvals

Track remediation tasks and non-sensitive review evidence; restrict sensitive incident or security detail through the authorized systems and permissions. See the platform

Related cases

Practice references