What should I request when asking for a sample or pilot?

Put these requests in writing when you ask for a sample or pilot.

- **Coverage:** name the product types and exception types you want, so the sample covers what your customers will search for. - **Formats:** list each record family and file format you need, with the schema version and a manifest describing them. - **Tasks and splits:** ask for task definitions with expected outcomes and a split between training and evaluation cases. - **Defect path:** ask how a defect is reported and how a corrected sample is issued and versioned. - **Known limits:** ask for a note of known limits and grounding gaps, and run your own disclosure and similarity checks. - **Licence questions:** ask about listing, sublicensing, redistribution, field of use and required disclosures. - **Practitioner review:** arrange for a practitioner to read a handful of cases before you commit to a listing. - **Success criteria:** agree what a good result looks like, in terms of your intake checks, before the sample arrives.