Which process boundaries make useful training cases for connected agents?

Use this checklist to identify boundaries where crossing into another team's work changes the reasoning required.

- Identify decisions the source team can recommend but cannot authorise. - Find evidence that loses validity before the receiving team acts. - Locate urgency rules that differ between the two queues. - Mark information visible to one team but restricted for another. - Find obligations that survive cancellation of the original request. - Identify transfers where the receiving team can refuse the work.

These features help separate a meaningful handover case from a routine notification. In utilities, an installation request can cross from customer service into field operations with a requested date that conflicts with site access restrictions. The agent must understand which constraint controls the next decision, rather than copy the requested date into another system.

For a first training slice, choose a boundary with a clear decision consequence and enough context to explain it. Adding more teams does not automatically make a case more valuable. A narrow transfer with competing constraints can expose more useful behaviour than a long chain in which every step follows automatically.