What should a buyer include in a correction sample request?

Use this checklist to turn an interest in business correction tasks into a reviewable sample request.

- Name the agent's assigned role and the business decision it should make independently. - State whether the sample will support supervised learning, interactive evaluation or human inspection. - Describe the starting information and the output a reviewer needs to assess the decision. - Request an explanation of expected outcomes, including cases where work should remain unresolved. - Identify a technical reviewer for ingestion and a domain reviewer for the business assumptions. - Define how disputed sample outcomes will be recorded and resolved before expanding the brief. - Ask for known exclusions and generation assumptions alongside the sample artefacts.

The request should make the review actionable. A technical reviewer needs to know whether records can be loaded and linked; a domain reviewer needs to know whether the decision logic follows the supplied rules. Neither judgement substitutes for the other.

A useful first step is to write a short acceptance note describing what evidence would make the sample suitable, what would require revision and which unanswered questions would prevent a meaningful evaluation.