Requests & Review
Requests connect the two roles in the compliance workflow: AI Developers complete evidence, and AI Stewards review it. There are two queues — one for each side.
Enterprise feature. Available Requests is the developer's queue; My Requests is the steward's review queue. Both live under AI Governance → Compliance.
Available Requests (Developer)
When a steward assigns or broadcasts evidence collection (via Jira or Slack), it appears here for developers to pick up.
Each request shows the agent, the frameworks required, the deadline, and current coverage. A request assigned to a specific person shows for them; broadcast requests are claimable by anyone on the team.
Claim a request
Open Available Requests and accept a request to take ownership of it.
Complete the evidence
Fill the eight evidence categories — see Evidence Collection. The request moves through Accepted → In Progress as you work.
Submit
When coverage is complete, submit it for steward review. It moves to the steward's My Requests queue.
My Requests (Steward)
This is the steward's review queue — every profile that's been submitted and is awaiting review.
Each entry shows the submitter, submission date, coverage %, and per-framework status.
Review a submission
Open a submitted profile and review the evidence across all eight categories. Leave inline comments where something needs work.
Approve or request changes
- Approve — the profile becomes Approved and its evidence counts toward Framework Coverage. An approval snapshot is stored for audit.
- Request changes — the profile returns to the developer as Changes Requested with your feedback; they revise and resubmit.
The review loop
A profile can cycle between Changes Requested and Pending Review as many times as needed before it's approved.
Next steps
- Evidence Collection — what goes into a submission.
- Framework Coverage — where approved evidence lands.
- Roles & Access — steward vs. developer permissions.