What should a sample request include so the pilot has a clear exit decision?

Use this checklist to turn a sample request into a defined review exercise with a clear decision at the end.

- Name the engineering and operational review roles. - State the agent capability being assessed. - Identify the reference policy and unresolved interpretations. - Request representative task inputs and expected outcomes. - Define acceptance evidence and disqualifying defects. - Specify how disagreements and corrections will be recorded. - Describe the proceed, revise and stop decisions.

Review roles matter because technical validity and operational suitability are different judgements. A schema can load correctly while its expected action is unacceptable to the team responsible for the process. Conversely, a realistic case may be unusable if essential evidence is missing from the agent's input.

Agree the review method before inspecting agent results. Otherwise the pilot can drift towards accepting whatever behaviour the current system happens to produce.

A useful exit decision states what the sample supports and what remains untested. Proceeding might justify a broader evaluation pack while leaving production readiness unresolved. Revising might mean clarifying one policy boundary. Stopping can be appropriate when the proposed task does not match the buyer's actual workflow.