
Who approves a model going to production
When a model goes live, somebody is accountable for it, whether or not anyone wrote that down. This page sets out who that approver should be, what they need in front of them, and how the decision gets recorded.
The short answer
One named person should approve each model release: the person accountable for the product or process the model affects, not the engineer who built it.
Before deciding, they see the evaluation results against the last approved version, the known risks and failure cases, and the rollback plan. Their decision, and its reasons, is recorded.
Definition
Model release approver: the single named person who decides whether a model, prompt or AI configuration change goes into production, after reviewing its evaluation results, known risks and rollback plan, and whose decision is recorded.
What goes wrong when nobody owns the decision?
Without a named approver, the model goes live because the engineer who changed it was satisfied. Nobody outside the build saw the results, the product owner learned about the change from users, and when something goes wrong there is no record of who decided or what they knew. Alternatively, approval becomes a committee that meets too rarely, so changes pile up and people find ways around it.
Who has to settle this question?
A CTO, AI product lead or business owner at a company putting models or AI features in front of customers or into internal decisions. It matters most when a model affects money, people or customers directly, and when changes are frequent enough that an informal habit has already formed.
What should the approver see, and who should it be?
| Question | Informal habit | A named release approver |
|---|---|---|
| Who decides | The engineer who made the change | The person accountable for what the model affects |
| What they see | A few examples | Evaluation results against the last approved version |
| Known risks | In the builder's head | Written down, with failure cases |
| If it goes wrong | Worked out at the time | A rollback plan agreed before release |
| The record | None | The decision, the reasons and what was seen |
How it works, step by step
The approval is the same short sequence for every release.
Name the approver for each model
Prepare the release packet
Separate the builder from the approver
Human gate: the named approver decides go or no-go
Record the decision and its reasons
Watch after release
What keeps the approval meaningful?
One name
A committee can advise, but one person decides, as approval gates describes.
A full packet. No packet, no decision.
Accepted risks in writing
Shipping with a known issue is allowed, and recorded.
A rollback plan agreed first
The approver knows how to undo it before saying yes.
No self-approval. Builders do not approve their own changes.
Where this fits
This principle sits under every AI workflow in the library, and the Platform page describes how such gates are built. The evaluation results the approver reads come from running the suite on every change, and trust in a new configuration is earned in shadow mode. Use the readiness checklist to see whether a process has the owner such approvals need, and the broader case for keeping some decisions human is when not to automate. The use case library shows the workflows these approvals govern.
How does release approval differ from code review?
| Question | Code review | Model release approval |
|---|---|---|
| Who does it | Another engineer | The person accountable for the outcome |
| What it checks | Whether the change is built correctly | Whether it should go live at all |
| What it relies on | The diff | Evaluation results, risks and a rollback plan |
| What is recorded | Approval of the change | The decision, the reasons and accepted risks |
Related reading
- Approval gates: the general rule of one name per decision.
- Shadow mode: how a new configuration earns trust before release.
- When not to automate: decisions that should stay with people.
