What should we ask for in a sample or pilot of generated booking material?

Ask for items that let your team run and grade the material, not only read it.

- **Representative cases:** bookable, blocked and ambiguous cases for one chosen product. - **Answer keys:** expected end states, acceptable alternative paths and required handoff facts. - **Policy documents:** authority rules, pricing tiers and conditions lists tied to rule IDs. - **Fault injection:** timeouts, rejected calls and conflicting documents, switchable per task. - **Reset and snapshot path:** a command that restores each task's starting state and exports before and after state. - **Schema and manifest:** field definitions, key relationships and the file layout. - **Review notes:** a way to send back disputed keys or implausible cases and see them addressed. - **Licence summary:** the permitted uses, stated plainly, before you load the material into any pipeline.

Also name the question the pilot must answer, such as whether the agent handles amended approvals, so that the sample can be shaped around it.