What should we request in a routing sample before starting a pilot?

Request a sample package that helps your team decide whether to proceed, making each requested artefact answer a practical uncertainty about the proposed evaluation rather than simply displaying a polished successful case.

- A complete task walkthrough showing the information available at each step, so reviewers can estimate the inspection work needed to understand a case. - A declared difficulty rationale describing what makes each selected task demanding, allowing buyers to challenge complexity that comes only from confusing presentation. - A vocabulary guide for business terms and status values, helping reviewers distinguish intended domain knowledge from undocumented assumptions about local terminology. - A list of simulated capabilities and known simplifications, including any business actions represented by fixed responses rather than changing environment state. - An example of reviewer feedback and its proposed disposition format, so the pilot has a concrete way to capture disagreements and requested corrections. - Delivery requirements covering file handling, access dependencies and execution prerequisites, allowing the technical team to identify integration barriers before model testing starts. - A written account of what the sample cannot establish, tying those limits to the pilot questions that would require broader coverage or additional environment behaviour.