Can a release include policies, exceptions and refusals, not just records?

**Q: Can a release include policy text?**

Yes, a release can include generated policy documents or structured policy tables, linked to products and tasks. A task can reference the policy an agent should have applied, so you can check whether it found the right rule.

**Q: What kinds of exceptions can be represented?**

- a payment that arrives after a cut-off and posts on the next business day - a request to defer when the account is already in arrears - a delivery schedule where a supplier misses a slot and the remaining dates must be re-planned - a part payment that does not match any instalment - a duplicate request raised through two channels

**Q: Are refusals included?**

They can be. A task pack can contain requests whose correct outcome is to decline, escalate or ask for missing information, with the expected reason recorded. Without these, an agent can score well by approving everything.

**Q: Are handovers modelled?**

A release can include the role that should receive an escalation and the information that role needs, such as account history and the request summary.

**Q: Is any of it real?**

No. Everything is generated. Ask how policies and exceptions were grounded in observed process behaviour, and inspect samples for plausibility and for any resemblance to real records before relying on them.