How can sample review reveal a routing requirement that was missing from the brief?

A model lab requests a generated utilities administration sample for routing maintenance enquiries. CASE-1074 describes a faulty meter cabinet at a commercial premises. The sample includes the message, premises record PREM-2187 and a list of maintenance queues.

During review, an operations reviewer cannot justify the proposed destination. Responsibility depends on whether cabinet maintenance falls within the service agreement or remains with the property manager. The premises record contains no coverage information.

The reviewer marks the case as requiring specification revision rather than treating the disputed route as a model error. The sample brief changes to require a coverage reference and a policy for unavailable coverage records. CASE-1074 gains a link to agreement AGR-2187, and its review state changes from unresolved to ready for reassessment.

The consequence is a better-defined task: the model can now use evidence that actually determines responsibility. Adding more messages before resolving that gap would multiply ambiguous labels.

This teaches buyers to treat pilot review as a test of task completeness, including whether disagreement comes from missing context rather than poor model reasoning.