Skip to main content

How your evidence is reviewed

What makes it sufficient and what to do when clarification is needed.

Written by Jaxson Perry

The audit team reviews each piece of evidence against the controls it supports. When needed, they can reopen a request and comment with questions or ask for additional information.
​

For a SOC 2 Type 1, the audit team will schedule you for review after you've submitted 100% of your evidence, signaling readiness. You will have time to respond to any follow-up questions or requests, but please respond promptly during this phase to keep your report on schedule and in line with the estimated draft delivery date provided during scoping.
​

What makes evidence sufficient?

Sufficient evidence shows what the request asks for and covers the right system and period. It should be dated and attributable to the person who performed the work.
​

For example, for a change in production, that means showing approval came before deployment and testing was performed.
​

To learn more about each request type and when they open, see Understanding evidence requests.
​

What do I do when the audit team asks for more?

Respond on the evidence request in the audit module and tag your auditor. That keeps your response and questions connected to the control being tested.
​

Not all requests from the audit team require new uploads, its important to answer the question asked. If the ask requires you to replace a file, add a note that explains what changed to help support efficient review.
​

What happens if my evidence falls short?

If testing finds that a control didn't meet its requirement, an exception may be described in your final report.
​

To learn how exceptions affect the opinion, see Reviewing your SOC 2 report.

Did this answer your question?