Governance, Law & Compliance
Documentation requirement
A rule requiring organizations to keep specific records about an AI system.
Example
A provider must maintain technical documentation describing the system and its controls.
Why it matters
It makes important information available for checking how a system was built or used.
You'll hear it
“Who is responsible for keeping this document current?”
Can you control it?
Not directly
No direct control. This is an obligation on an organization to keep particular records about a system, and the rules usually say what those records have to cover. It falls on whoever builds or runs the system, not on a reader.
Common questions
- Does more documentation always mean better compliance?
- No. Records need to address the actual requirement and accurately describe the system.
- Can a vendor provide all the necessary documents?
- Possibly not. Your organization may also need records of its own decisions and use.
- Should outdated versions be deleted immediately?
- Not automatically. Retention requirements and review needs determine which earlier records should be kept.