In-Depth Guide
The Situation
A team wants to buy an AI tool and expects approval after a short conversation.
Where Teams Get Stuck
Decisions made from conversation leave no record of what was known, and the same questions get asked again at audit time.
How RAMP Handles It
RAMP generates the requirements document at intake from the answers the owner gives, and keeps it attached to the system's record.
What goes in it
Purpose, data used, users and people affected, applicable regulations, human oversight, expected controls and known risks.
Why before approval
Written early it is cheap to write and shapes the design. Reconstructed late it is an expensive guess.
Frequently asked questions
- What is a governance requirements document for AI?
- A short document that captures an AI system's purpose, data, users, regulations and expected controls before approval.
Leadership Action Item
No requirements document, no approval request. Next: Gate 1.
Related GuidesView all guides →