What the framework leaves to you
The framework does not prescribe retention periods or evidence formats. Your organization has to set both, and the schedule it sets should be defensible when an auditor, customer, or regulator asks for evidence.
Build the schedule by evidence category. For each category, take the longest applicable requirement from sector rules, contracts, and legal hold, then limit it with privacy and data minimization duties.
Factors that set retention periods
Four factors determine the period for each evidence category. The first three set how long evidence must be kept; the last limits it.
- Sector rules: obligations that apply to your industry and to the AI system in question.
- Contracts: retention terms you have agreed to with customers and partners.
- Legal hold: a hold suspends deletion for the evidence it covers.
- Privacy and data minimization: duties that cap how long personal data may remain in evidence, including logs.
Rule of thumb
For each category, take the longest applicable requirement from sector rules, contracts, and legal hold, then limit it with privacy and data minimization duties. Confirm periods with counsel and record the driver behind each one.
Mapping evidence categories to drivers and formats
Group evidence by the four AI RMF functions. Each group gets its own retention period, and each period should name the driver behind it.
| Function | Evidence |
|---|---|
| Govern | Policies, roles, and approval records |
| Map | Context, intended use, and risk assessments |
| Measure | Test and evaluation results |
| Manage | Monitoring records and runtime decision logs |
Choosing formats that stay verifiable
Store evidence in formats that are:
- Structured: captured in defined fields rather than free-form notes.
- Versioned: so changes to an artifact can be traced.
- Searchable: so evidence can be retrieved for a given agent and time window.
- Tamper-evident: so alteration after the fact can be detected.
Why AI agent evidence needs its own treatment
Runtime decision logs fall under the Manage function, and they are where agent behavior is recorded. Minimization has to remove personal data from these logs, and legal hold has to be able to suspend their deletion.
Runtime policy enforcement, agent identity records, and audit logging can produce evidence that your retention schedule can govern.
Steps to build the retention schedule
- Inventory AI systems and list the evidence each one produces, grouped by Govern, Map, Measure, and Manage.
- Identify applicable sector, contractual, and privacy obligations for each category and confirm periods with counsel.
- Set a retention period per category and record the driver behind it.
- Define format and integrity requirements, including versioning, structured fields, and tamper-evidence.
- Document how legal hold suspends deletion and how minimization removes personal data from logs.
- Test retrieval by requesting evidence for one agent over one time window, then fix gaps before an audit does.