Northline Service Desk (fictional) gets a mix of incidents and ordinary requests. The service lead, Morgan Reed, wants High and Highest incidents assigned to the incident owner, Milo Ortiz, the moment they are created, and a saved view of what he is holding.
The data: the HELP project and its existing requests. Ordinary service requests must not be touched by the routing, even when their priority is High.
Done looks like: a scoped rule running as an actor with the right access, one new incident routed by it, one new request left alone, a shared filter for the lead, and a checked statement of the evidence.
Northline's service lead wants high-priority incidents routed to the incident owner the moment they arrive, without touching ordinary requests. You will build the routing, prove it on two new records, and leave a saved view the lead can open each morning.
Each step keeps what you built in the step before. The rule you save in step two is still there when you create records in steps three and four, so you can see it fire, or correctly stay quiet. Do not set an assignee by hand on a record the rule is meant to route: that hides whether the rule works.
The final step asks for the evidence that proves the routing is safe. A good answer points at records and the audit log, not at the rule's name.
Build routing and prove it on records that should and should not match.