What should a lab include in a request for a generated sample?

Use this checklist to turn a broad interest in customer changes into a reviewable sample request.

- Name the business domain and operating context. - Identify the changed detail or circumstance. - Specify the records the model may inspect. - Describe the expected range of task difficulty. - State required language and terminology conventions. - List excluded decisions and sensitive subject areas. - Define the review evidence and acceptance questions.

The brief should distinguish essential coverage from optional variation. A lab studying account maintenance may need requests that affect several active products, but have no need for lending decisions. Stating that exclusion prevents the sample from drifting into a different capability test.

Difficulty should also have an operational definition. It can come from fragmented evidence, an exception rule or a required handover. Longer messages and extra records do not necessarily create a more useful task.

A buyer can ask MirrorFirm to return a proposed coverage map with the generated sample. Reviewers can compare each included case with the brief, identify missing conditions and decide which variations deserve expansion. The first review should establish whether the material tests the intended behaviour, before focusing on volume or presentation polish.