Describe the contribution precisely
List the record categories, date ranges, business functions, and relationships needed to explain the workflow. Separate the material you are proposing from systems or documents that remain outside scope. A precise description gives your business, technical, and approval teams the same starting point and makes it easier to spot a misunderstanding before delivery work starts.
Keep ownership and use questions separate
Micro1 states that companies retain underlying data ownership. That statement alone does not answer how prepared data may be used, whether a license is exclusive, who may receive it, or whether future contributions are expected. Put each of those questions on the discovery agenda. The point is to obtain defined terms rather than assume what a generic license allows.
Follow the prepared-data journey
Ask how originals are transferred, who can access them, what transformations are made, and whether your company can review representative examples. Micro1 describes de-identification, separate processing, restricted access, and agreed retention rules. Ask how those measures apply to the specific categories in your proposed contribution, including records connected across multiple systems.
Illustrative scope brief
An operations team might propose a defined period of dispatch histories and resolution notes for delivery exceptions. The brief would specify the relevant workflows, included record types, missing fields, and a process owner. It would also identify unrelated records to exclude. This is an example of organizing a conversation, not a recommended contract clause or an indication of acceptance.
Questions before the next step
Does licensing automatically mean recurring revenue?
No. The payment structure and any continuing participation must be specified in the proposed agreement.
Do we have to buy a software product?
This guide concerns Micro1’s data partnership opportunity. Confirm the actual scope and any obligations directly with its team.
A licensing scope brief worksheet you can use
Use these headings to create a descriptive preparation brief. They are not a required Micro1 delivery schema, vendor export specification, or request to submit raw records.
| Field to describe | Meaning in this workflow |
|---|---|
| Included Material | The record categories and period proposed for discussion |
| Excluded Material | Categories remaining outside the proposed contribution |
| Use Question | The intended purpose or restriction to clarify |
| Prepared-Data Review | What examples or transformations the company can inspect |
| Commercial Milestone | The delivery, acceptance, or payment question to resolve |
A more informative description
A scope brief explains the proposed records, their relationships, exclusions, and unresolved use questions. Business and systems owners share the same description.
A description that leaves questions open
Ownership of underlying data is treated as an answer to every question about recipients, exclusivity, duration, or continuing work.
The next decision
Keep the company’s ownership statement separate from the specific permissions and obligations proposed in the agreement.
Download this licensing scope brief worksheet ↓ · Use this template in the inventory tool →
Program statements reflect Micro1’s official data partnership page, reviewed November 14, 2026. Checklists and scenarios are our editorial preparation guidance. They are not customer case studies, legal conclusions, or Micro1 acceptance rules.