Can a release include policies, exceptions and free text, or only structured records?

**Can a release include policies and exceptions, or only records?**

Both can be in scope. A dataset can ship the records alongside a policy file, so each routing or completeness outcome points to the rule that produced it. Exceptions can be represented as cases that depart from the standard path.

**What kinds of exceptions can be generated?**

- Duplicate submissions of the same request - Documents that are present but unusable - Requesters who change details mid-case - Urgent or vulnerable-customer flags that override the usual queue - Cases returned to intake after a downstream team finds a gap - Manual overrides by a supervisor, with a note

**Do we get free text such as emails and notes?**

A release can include generated free text such as covering emails, broker notes and handover comments, linked to the structured record. Free text is where disclosure risk and grounding are hardest to judge, so ask for a sample of it before committing.

**Can we get several domains in one release?**

You can ask for a spread, such as lending, claims and utility connections, with a shared schema and a `domain` field. Whether that suits your customers depends on whether they want depth in one domain or breadth for general-purpose agents.

**Is every field always populated?**

No, and it should not be. Realistic intake data has blanks, placeholders and inconsistent formats. Ask which of these a release includes on purpose.