> For the complete documentation index, see [llms.txt](https://docs.prove.ly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prove.ly/guides/evidence-vault-and-audit-export.md).

# Evidence vault & audit export

`GUIDES`

Every verification, refresh, and policy version lands in one evidence vault — a living, append-only record of exactly who's qualified against what, kept current in the background.

#### The readiness statement

When an auditor asks, there's no reconstructing a year of training logs. You export a defensible statement of your organization's readiness, as of today:

{% hint style="success" %}
**Readiness Statement — example**

Overall coverage **98%** · Policies in scope **24** · People verified **412 / 420** · Last refreshed **Today · 09:14** · Evidence retained **7 years** — **AUDIT-READY**
{% endhint %}

#### What's in an export

— Every verification record: person, policy version, timestamp, outcome

— Refresh history and the trigger that caused each one

— Coverage over time, per team and per policy

— A tamper-evident, append-only audit trail

***

`CERTIFICATION-READY`

Built for the standards you answer to:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>ISO 27001</strong></td><td>Information security management</td></tr><tr><td><strong>SOC 2</strong></td><td>Security &#x26; availability controls</td></tr><tr><td><strong>GDPR</strong></td><td>EU data protection</td></tr><tr><td><strong>DORA</strong></td><td>Operational resilience for financial entities</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prove.ly/guides/evidence-vault-and-audit-export.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.