How might a marketplace scope a pilot for a lending-operations listing?

A product manager at a data marketplace wants a lending-operations listing. They open scoping item SCOPE-0112 and ask for two product types: equipment finance and residential mortgage.

They request clean cases, cases with a missing condition, and cases with an amended approval, each tagged by type, plus policy extracts and a task file with an eval split. They ask for Parquet tables, JSONL tasks and a manifest listing schema version and content.

The sample arrives. A data engineer runs the marketplace's intake checks and a lending-operations contractor reads ten cases. The contractor flags that the mortgage cases lack a valuation condition, which operations teams usually track. The product manager adds this to the pilot scope. The sample is also checked for text that resembles a specific institution; nothing is found, and the check is recorded in the listing file.

The product manager then sends the licence questions: whether the listing may be sublicensed, what disclosure text must pass to buyers, and how corrections are issued. The listing stays in draft until the answers are in writing.

Had the product manager skipped the contractor review, the missing valuation condition would have surfaced in a customer's evaluation, with the marketplace's name on the listing.

**What it teaches:** treat the pilot as a gap-finding exercise and turn each gap into a written scope change.