What should a pilot request for scheduling tasks include?

A pilot request is stronger when it is specific enough to pass or fail. Include these items:

- **Decision statement.** The one question the pilot should answer, such as whether an agent can handle skip and re-date requests within policy. - **Domain and actions.** One domain and two or three adjustment types, with the exceptions to include. - **Policy source.** Whether you supply rules or want generated ones, and who reviews them. - **Acceptance checks.** Invariants, policy replay, variety measures and a disclosure review you will run on the sample. - **Reviewer.** A named role on your side, such as a billing supervisor, who reads full cases for plausibility. - **Format and harness fit.** Preferred file formats, id conventions, tool names and how the environment should reset. - **Holdout plan.** Which tasks are reserved for later and how variants are grouped. - **Licence questions.** Intended uses, sharing, publication of results and retention, to be agreed before wider use.

Ask for the generation parameters and schema version to be delivered with the sample, so the results can be reproduced.

Timelines, volumes and commercial terms are discussed in scoping and are not set by this checklist. Treat the first sample as a test of fit and be ready to revise the brief after reviewing it.