What should a buyer ask to have included in a generated booking release?

Use this list when specifying a release so that it can support grading and not only browsing.

- Approval records with structured terms and a separate conditions array with status. - Facility records linked to approvals, with status history and the acting role. - Repayment schedules that reconcile to the stated terms, including residual or balloon lines where the product uses them. - Security items, documents and settlement instructions linked by facility identifier. - A policy set covering authority limits, exception rules and drawdown preconditions. - Expected dispositions (`book`, `hold`, `return`) with the blocking reason for each task. - Starting and expected end state snapshots for every task. - A product and domain mix, such as term loans, asset finance and premium funding, with a stated seed so runs can be repeated.

Also ask how the generated content was grounded and what checks were run for overlap with real material. Those answers belong in the sample documentation, and a buyer should read them before relying on the data.