What should we include in a request for a review sample?

Use the sample request to make the proposed review task inspectable by both domain reviewers and evaluation engineers.

- State the business decision and agent role, including the operational question that the sample should help your team answer. - Request an input inventory that distinguishes supplied records, retrievable evidence and dependencies deliberately left outside the sample. - Ask for a walkthrough connecting decisive facts to acceptable outcomes, with enough explanation to challenge the expected judgement. - Request a failure taxonomy that separates missing evidence, mistaken reasoning, invalid actions and defects in the task itself. - Specify the inspection format your team can use, including whether a static record bundle or executable episode is necessary. - Ask for a limitations statement covering omitted behaviours and the conclusions that the sample cannot support about broader performance.

After inspection, record concrete revision requests against cases rather than broad impressions that the material feels realistic. A useful sample should help the team decide what to retain, change or exclude. It need not demonstrate every sector, exception or integration to support a well-defined next scoping decision.