Can a release include policies, multiple snapshots and deliberately messy submissions?

**Can a release include the policies an environment enforces?**

Yes, a release can include policy rules as structured records and as readable text. Each rule can name the request type it applies to, the fields and documents it requires, the condition that sends a case to a particular queue, and the exceptions allowed.

**Can the same case appear in different states?**

A task pack could provide several snapshots of one case, for instance as received, after a request for information, and after routing. This lets you start an episode midway or compare an agent's path against a reference path.

**Can I ask for messy submissions?**

Yes. You can ask for missing attachments, conflicting dates, duplicate parties, wrong forms and withdrawn requests, and you can specify how often each should appear in a sample.

**Can I get free-text content such as emails and notes?**

A release can include generated correspondence and handover notes linked to case identifiers, so language skills and tool skills can be tested together.

**Are these real business records?**

No. Everything is generated. The design is informed by observation of how businesses work, and a buyer should inspect grounding and disclosure risk in any sample before relying on it.