What should a sample or pilot request include?

Use this list to prepare a request for a sample or pilot of generated set-up material.

- **Name the domain and trigger:** state the approval that starts the workflow, such as an accepted quote, application, referral or proposal, and the product or service line. - **List the records:** specify the parties, accounts, services, tasks and events the sample should contain, and the links you expect between them. - **Choose exception types:** pick three or four, such as duplicate parties, missing evidence, conditional approvals and post-approval amendments. - **Pick the format:** files in JSONL or Parquet, a task pack with expected end states, a simulated environment, or a staged combination. - **State the onward-use plan:** say whether you will list the material, bundle it or customise it, and what kind of teams your customers are. - **Agree the review:** define the checks you will run, who reviews grounding and disclosure risk, and how findings are returned. - **Leave terms open:** pricing, timing and licence conditions are set in the engagement, so ask for them in writing rather than assuming them.