What should a buyer include in a sample request?

Use this checklist to turn an evaluation interest into a sample request that reviewers can act on.

- State the agent capability you need to distinguish. - Supply a sanitised rule outline or request generated rules. - Name the required business roles and decision boundary. - Identify the runner's input and output constraints. - Request visible evidence and separate evaluator rationale. - Define who reviews business plausibility and technical fit. - Record intended uses and unresolved licence questions. - State the pilot's exclusions and acceptance evidence.

Include the decision the sample will inform. A team choosing between agent architectures needs different evidence from a team testing whether a scoring rubric is stable. That purpose should influence the requested cases and the detail in the reference material.

Avoid supplying business records merely because the workflow concerns real operations. A process description or abstract rule outline may be sufficient for initial scoping; discuss any further grounding inputs separately and inspect disclosure risk.

The useful output of the request is a reviewable sample specification. It should let reviewers explain why the proposed material fits the evaluation question, where it falls short and which change would resolve the mismatch.