A scoped process
How a source and a task meet.
An automotive business can describe a workflow it understands. An AI team can name a decision it needs to train or test. A pilot is possible only when the source, intended use, output, and terms fit together.
First: describe the task or source
An AI team names a decision and a failure it needs to investigate. A source owner describes broad categories, history, and who may control the material. Either side can start with a short note.
Then: test the rights and fit
A useful workflow is not automatically available for training or evaluation. Contracts, customer information, vendor terms, the intended recipient, and the intended use may limit or rule out a proposed source. The business and the relevant rights holders must agree what can be examined before any transfer.
Next: define one output
A proposed plan could specify a documented dataset, expert-created examples, or a scored evaluation. It should name the record unit, necessary context, allowed transformations, review sample, grading rules, and an outcome the buyer can check.
Before access: write down terms
The scope settles who prepares and receives material, security and privacy review, exclusions, retention, acceptance criteria, compensation, and payment triggers. Timing follows from the rights, preparation, and agreed work.