Skip to content
MirrorFirm

What should I ask for in a sample or pilot scoping note?

A checklist of eight requests to include in a scoping note so a pilot sample is narrow, documented, balanced, checkable and clear about licence scope and limits.

Put these requests in the scoping note so the sample can be judged on its merits.

- One domain and one product, so the sample is narrow enough to inspect in full. - A schema file that defines every field, allowed value and link between records. - A balanced case mix covering clean, incomplete, duplicate and escalated submissions. - Numbered policy rules with effective dates and written exception paths. - Reference outcomes, with acceptable alternatives listed wherever more than one exists. - A tool contract and a reset method, if you plan to run agents against the environment. - A short statement of how the material was informed, plus the limits of that grounding and any known gaps. - A licence scope for training, evaluation or both, to be confirmed directly with MirrorFirm.

A precise scoping note lets you judge the sample on its merits and shortens the loop between inspection and the next version.

Audience:
Model labs
Content type:
Checklist
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Application intake