# Prompt change review

Use this checklist for prompt, policy, model, retrieval, and tool-description changes.

## Change packet

| Item | Required evidence |
| --- | --- |
| Reason | What problem does the change solve? |
| Scope | Which workflows, users, languages, and tools are affected? |
| Evaluation | Which tests passed, failed, or changed? |
| Risks | What behavior could regress? |
| Rollback | How quickly can the prior version be restored? |
| Approval | Who accepts the change and residual risk? |

## Review checks

- Compare factuality, citation behavior, refusal behavior, tone, latency, and cost.
- Confirm sensitive tools still require the intended approval thresholds.
- Inspect examples where output changed materially, not only aggregate scores.
- Update release notes and monitoring alerts when behavior expectations change.

## Approval rule

No production prompt change ships without an owner, eval evidence, rollback path, and traceable reason.