Can a release include policies, exceptions and handovers, not just instalment tables?

**Can policies be part of the generated output?**

Yes. A release can include policy records with identifiers, thresholds, effective dates and required approvals, and decisions can cite the policy they applied. A task pack can also include policy versions so that a request is judged against the rule in force on the as-at date.

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

- A deferral request that exceeds the permitted count. - A change requested while a dispute is open. - A delivery split where the supplier cannot meet the second tranche. - A due date that falls on a public holiday in one state but not another. - A payment that arrives against a superseded instalment.

**What about handovers?**

Scheduling often passes between people: a call-centre agent starts a request, and a back-office team finishes it. Generated case notes can record what was agreed, what is outstanding and who owns the next step. A task can then begin mid-case, where the agent must read the handover before acting.

**What are the limits?**

The policies are generated to resemble how organisations behave, not copied from any one organisation's rulebook. Buyers should check that the rules are internally consistent and that they fit the domain they care about. If your own policy is the target, supply it and ask for a pack built to it, which is a pilot scoping question.