A data licensing readiness checklist for your first buyer conversation

1. Choose a bounded collection

Begin with one line of work. Examples could include completed equipment repairs, a set of original training materials, or historical logistics exceptions. Explain the starting event, the decisions recorded, and where the outcome is stored. A coherent boundary makes the conversation easier to manage than a proposal to license every file the organization holds.

Write down the exclusions at the same time. A maintenance archive might exclude access codes, customer identities, current security arrangements, or licensed manufacturer content. These exclusions are a starting scope proposal, not a claim that the remaining material is already cleared. Defining them early helps your team understand which questions belong in the review.

2. Inventory the systems and the dates

For each system, record its name, purpose, owner, approximate years of available history, and the kind of records it holds. Distinguish a live system from a retired archive. Note whether attachments, comments, revisions, and outcomes remain accessible. If your team has never checked an old export, mark its contents unverified rather than assuming it contains everything.

Add a short migration history. A change in software can create duplicate IDs, missing attachments, new field names, or incomplete periods. Ask the person who managed the migration what changed. This is a description exercise. Do not run a broad export merely to answer an initial inquiry; first understand what the source system can provide and what approval would be needed.

3. Describe volume with a method

Use counts you can explain. “About 40,000 completed jobs, based on the dashboard's closed-job count for 2021 through 2025” is better than an unsupported exact total. Distinguish complete cases from individual messages, documents, and attachments. A job with ten documents should not become ten completed jobs in a description of the archive.

Record when the count was checked and by whom. If the software can only show an approximate total, preserve that limitation. You can also use a range while preparing the inventory. The goal is to give a reviewer a realistic sense of scale, not to maximize the largest number that can be extracted from the system.

4. Map the connections and missing pieces

List the references that connect one record to another: a project ID, order number, service ticket, or document version. Explain whether those references are stable over time. Note when a conversation refers to a file that no longer exists. This map helps distinguish a collection of isolated fragments from a usable record of the work.

For an internal check, ask a knowledgeable colleague to follow a normal case, an unusual case, and a failed case. They should be able to describe what is clear and what depends on memory. Keep that check within your existing access controls. The inventory can report the finding without including real case details in the material sent for initial qualification.

5. Identify rights and approval questions

Separate the person who administers the software from the person who can approve a commercial license. Record who can review customer agreements, contributor contracts, and confidentiality obligations. The Copyright Office notes that rights may belong to different owners within a larger work.^[1] An archive-wide statement of ownership may therefore need exceptions.

Create a short list with three columns: question, responsible person, and status. Useful entries include contractor-created material, client-owned drawings, third-party publications, and grant-funded resources. Use statuses such as confirmed, excluded, or needs review. The status “needs review” preserves a real uncertainty and gives the next conversation a concrete task.

6. Plan the handling before preparing a sample

The FTC recommends knowing what personal information a business holds, limiting what it retains, protecting it, and planning for disposal and incidents.^[2] Apply that discipline to the proposed collection. Identify likely personal or confidential fields before deciding how a reviewer could inspect a sample.

Ask the prospective recipient how it handles access, storage, transfer, redaction, retention, and deletion, and who performs those tasks. Decide who in your organization would approve the sample and the final package. A generic promise of security cannot replace a handling plan for the actual record types. Your internal system access should remain separate from the early commercial conversation.

7. Set a limit on preparation effort

Name the people whose time might be needed and agree on an initial review budget. That budget can be expressed in staff hours or a small approved spend. Specify what additional evidence would justify a larger commitment. A preliminary expression of interest is useful, but it may not warrant extensive cleanup or custom development.

Identify work that would help the organization regardless of a deal. A better system inventory or documented retention owner may be worthwhile on its own. Keep that internal benefit separate from speculative licensing proceeds. This makes it easier to decide whether to continue if buyer interest is limited or the proposed scope changes.

8. Finish a one-page opportunity brief

Bring the information together in a short brief. It should explain the organization, the proposed collection, its period and scale, the connected workflow, known gaps, exclusions, and approval contacts. Add the questions you want the buyer to answer. A reader should understand the possible asset and the next decision without opening a raw record.

Use the brief to support a preliminary estimate or a conversation with North Fox. If a relevant route emerges, approve the named introduction separately. Keep a copy of what was described at that stage. Later changes in scope, record count, or permissions should be visible so that the final agreement is evaluated against the collection actually being offered.

• Collection: a specific workflow or resource, with the proposed period.
• Evidence: the source and date of any approximate counts.
• People: the records owner, technical contact, and approval contact.
• Questions: known gaps, exclusions, and unresolved permissions.
• Next decision: what a buyer or adviser needs to answer before more work is approved.