What should a first routing pilot include and explicitly leave out?

Use this checklist to turn an initial enquiry into a bounded pilot brief.

- Select one domain and intake decision point. - Name the downstream customer use being tested. - Define the included request and exception families. - State which systems and actions are outside scope. - Specify the evidence needed for an acceptance decision. - Identify who reviews operational plausibility and integration. - Record what would justify expanding the scope.

A healthcare administration pilot might cover appointment enquiries entering a central intake queue while excluding clinical assessment and treatment decisions. That boundary determines which facts, destinations and actions belong in the generated material. It also prevents a successful administrative routing task from being interpreted as evidence about unrelated clinical capabilities.

The acceptance decision should connect to the reseller's next step, such as whether the proposed product is understandable and usable by its intended customers. Request a sample that exposes the difficult distinctions within the chosen boundary.

MirrorFirm could use that brief to scope a generated collection or task pack without assuming broader coverage, commercial terms or delivery commitments.