What should we ask for in an approval-authority sample or pilot?

A useful sample or pilot request is specific enough that you can accept or reject it against written checks.

- State the domain, roles and authority dimensions you want covered, and the exceptions you expect to see. - Ask for linked tables, policy documents in at least two versions, and a data dictionary. - Request expected outcomes and reason codes held separately from the model-visible inputs. - Specify a held-out split by organisation or policy variant, and say how you will use it. - Ask for the generation method to be described, including how grounding and disclosure risk are addressed. - Agree the formats you need, such as JSONL, Parquet or Markdown, and the tool schema if an environment is involved. - Write your acceptance checks first, including label recomputation and perturbation tests. - Confirm permitted use, retention and versioning before any material is loaded into a training run.