ModelRefs / Refusal Routing — Prompt Pattern
Refusal Routing — Prompt Pattern
Detect out-of-scope requests early and route to a safe fallback.
Overview
Cheap router classifies whether the request is in scope; out-of-scope requests get a templated refusal instead of generation.
When to use it: Reduce risk and cost on a narrow-scope assistant.
Pattern details
| Pattern class | safety |
|---|---|
| Difficulty | beginner |
| Also known as | scope guard, router-refusal |
| Last reviewed | 2026-06-07 |
Known failure modes
- Scope creep — Router drifts and allows everything. Mitigation: Pin router with golden negatives in evals.
When not to use it
- Letting the main model handle out-of-scope (cost + risk).
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Refusal Routing — Prompt Pattern.
Frequently asked questions
When should I use the Refusal Routing prompt pattern?
Reduce risk and cost on a narrow-scope assistant.
What are common failure modes of Refusal Routing?
Scope creep
Does Refusal Routing work across models?
Yes when the anatomy is preserved — see model compatibility matrix on the pattern page.