01Describe the archiveResponsibilities & output +
You identify the company, systems, years of history and the person responsible for the records.
A company and data profile. No raw export.
Start with the systems you already use. Keep examples descriptive and remove confidential details.
02Review rights and fitResponsibilities & output +
You involve the rights owner; the parties clarify the proposed use and any restrictions.
A list of open rights, privacy and fit questions.
Access to a system does not establish authority to license its contents. Resolve third-party, employee and customer restrictions.
03Compare the agreementResponsibilities & output +
You decide whether proposed terms work for your company. Responsibilities are agreed in writing.
A defined scope, license, acceptance and payment process.
Compare exclusivity, duration, recipients, preparation duties and fees alongside the price. No offer is guaranteed.
04Agree the handoffResponsibilities & output +
The agreed parties prepare, review and transfer only the authorized scope.
Delivery and acceptance evidence under the agreement.
Confirm who removes restricted information, who approves the result and how transfer and retention are controlled before sharing.
This preview prepares a local brief. Any engagement, buyer introduction or data transfer requires a separate conversation and agreement.
Build a profile someone can evaluate
A useful starting point is a description of the business and the work its systems record. List the tools, the teams using them, the years available, and the kinds of events that connect a question to an outcome. A support archive might preserve an issue, several attempted fixes, and a resolution. A project board might preserve a handoff and the reason a deadline changed.
Keep the first profile practical and easy to revisit. Explain what the records contain, how they are organized, and which person understands their limitations. Rough descriptions are more useful than an unexplained storage total. Separate records your company created from material supplied by customers or other parties. At this stage, describe the archive; do not export confidential records or grant access to a live system.
Establish who can make the decision
The person who can retrieve an archive may not be the person who can license it. Identify the owner of the business records and the colleagues who need to review a proposal. Depending on the company, that conversation may involve operations, information security, legal, procurement, or a customer relationship owner. Write down the questions that must be resolved before anyone requests a sample.
Treat missing authority as an open issue rather than assuming it will be straightforward. Contracts, confidentiality commitments, employee records, and third-party content can change what is available. A smaller, clearly authorized scope can be easier to discuss than an expansive archive with uncertain permissions. Keep excluded categories visible in the profile so later conversations do not accidentally expand beyond the original understanding.
| Reviewer | Open question |
|---|---|
| Business owner | Licensing authority |
| System owner | Record coverage |
| Specialist reviewer | Sharing restrictions |
Turn interest into a defined agreement
Buyer interest is the beginning of a commercial discussion. Ask what the proposed use involves, which recipients receive the material, and how the requested scope relates to your profile. Then compare the license duration, exclusivity, preparation duties, acceptance conditions, and payment process. The same headline figure can describe substantially different obligations, so record the complete proposal rather than keeping only its price.
Decide who answers unresolved questions and how changes will be approved. If a request expands from one department to the entire company, revisit the scope and authority instead of treating the expansion as an administrative detail. Keep each proposed version together with its assumptions. You should be able to explain what would be shared, why, and under which conditions before deciding whether to proceed.
−Amount considered alone
−Scope left unclear
+Rights and duration
+Acceptance and payment
Agree what completion will look like
Before a transfer, specify the authorized dataset, the preparation required, and the person approving the result. Agree how sensitive or restricted material will be handled, what transfer method will be used, and what evidence establishes receipt and acceptance. These responsibilities should be explicit. Do not assume that a sourcing partner or receiving company automatically performs every privacy, quality, or operational review.
Keep a record of the approved scope and the evidence associated with each step. Preparing a file, delivering it, receiving acceptance, and receiving payment are separate events. This website currently helps you prepare a local assessment brief; it does not carry out those transaction steps. Use the brief to make a later conversation more concrete, with the unresolved responsibilities already identified.