How should a reseller scope a schedule release and approach onward licensing?

Scoping starts with a narrow question: which part of the schedule lifecycle do your customers need to train or test? Creation, amendment, arrears handling and closure each need different records, and a release that tries to cover all of them at once is harder to inspect.

Useful scope decisions:

- **Domain:** lending, utilities, insurance premiums, delivery plans or another sector - **Layers:** records only, records plus policies, a task pack, or a simulated environment - **Variation:** how many products, policy sets and exception types - **Format:** JSONL, Parquet, or an environment snapshot - **Evaluation material:** graders, expected outcomes and reset methods

Licensing needs particular care for a reseller, because your customers receive rights from you. Ask what onward licensing the licence permits, whether sublicensing is allowed, how attribution and disclosure of the generated nature of the data should be passed on, and what restrictions apply to model training, redistribution and derivative products. Terms, pricing and timing are agreed directly with MirrorFirm; do not assume any from a sample.

A useful first step is a small sample or pilot on one lifecycle stage, tested against your own acceptance checks. That tells you what the material is like before you commit to a broader catalogue.