# Model routing policy ops review brief

## Route change

Describe the workflow, current model, proposed model, provider, fallback, data class, quality gate, latency budget, and cost ceiling.

## Evidence

Attach evaluation results, latency samples, cost estimate, provider status, data-boundary review, and rollback plan. Identify any accepted exception and expiry date.

## Decision

Approve, hold, rollback, or run a limited release. Keep the route owner responsible for post-launch quality, latency, cost, and incident signals.