How should an environment team scope and license an intake pilot?

Scoping starts with the decisions your environment must exercise, not with volume.

**Pick the request types.** One or two types, such as a loan application and a change-of-details request, are usually enough to test whether the state model works. Add types once the first pair runs.

**Pick the exceptions.** List the failure patterns you care about: missing attachments, duplicates, wrong forms, withdrawals, conflicting identifiers. Each one becomes a tagged task family.

**Pick the interface.** State the file formats, the tool vocabulary and the reset behaviour your harness expects, so the sample can be loaded without rework.

**Raise the licence questions.** Be explicit about whether you need to train, evaluate or both, whether outputs may be redistributed, and how long you need to keep the material. These terms are agreed with MirrorFirm directly; none are assumed here.

**Keep the limits in mind.** The output is generated and informed by observation of how businesses operate. It is not real records, and it does not by itself establish privacy or regulatory compliance. Your team should inspect grounding and disclosure risk in the sample.

A useful first step is a small sample of tasks with the full schema, so you can test loading, reset and grading before committing to a larger scope.