What should a lab include in a sample request?

Use this checklist to turn interest in handover training into a sample request that both technical and procurement reviewers can assess.

Describe the lab's intended use in operational terms. 'Agent training' alone does not explain whether the model will read records, draft transfer notes or execute actions. Likewise, naming a domain does not specify the local conventions the material should represent. Terminology, business calendars and queue practices can affect whether a sample fits the intended setting.

The request should make those assumptions visible without requiring a complete enterprise replica.

- State the target model behaviour and intended use. - Name the domain and relevant Australian operating conventions. - Describe expected context length and retrieval arrangements. - Specify required output formats and ingestion constraints. - Identify optional detail that can be omitted initially. - Ask for a manifest of included artifacts and exclusions. - Nominate who will review operational and technical fit.

A buyer can send this brief to MirrorFirm as the starting point for scoping generated material. Review the response against the brief, recording mismatches explicitly so that an attractive sample does not silently redefine the original training need.