The takeaway

A first inventory describes the data. It does not need to contain the data itself.

Give the assessment a useful starting point

You do not need to assemble a giant export to begin exploring licensing. A concise inventory can help your team explain what exists, where it lives, and who knows it best. Start with systems that record a complete operational process, such as support, order management, or project delivery.

Give one person responsibility for the inventory and invite system owners to validate their rows. The goal is a shared picture of the opportunity and the open questions, not a promise that every collection is ready to license.

Capture eight fields for each collection

A starting inventory you can recreate in a spreadsheet
FieldWhat to record
System and ownerThe application, department, and responsible person
WorkflowThe business task the records describe
Record typesCases, orders, events, documents, or other units
HistoryDate range, known gaps, and migrations
Approximate scaleA count, its unit, and whether it is verified
ConnectionsHow related records are linked across systems
RestrictionsKnown contractual, privacy, or access questions
Export readinessAvailable formats and who can check them

Download the worksheet and keep the first pass descriptive

Download the business data inventory worksheet

The CSV includes the eight fields above, instructions, and a prompt row you can replace. It opens in common spreadsheet applications. Keep the completed file inside your organization; this website has no inventory upload form.

Start with three candidate systems. Ask each system owner to describe the workflow, record unit, date coverage, and unanswered restrictions. A department name is enough for an initial owner field. You do not need to add customer names, employee details, or actual records.

Worked example: a manufacturer with three candidate systems

Hypothetical example—not a customer case study, assessment result, or valuation. Consider a fictional 250-person manufacturer. Its team starts with order management, maintenance, and a customer-support system. The purpose of this exercise is to decide what to investigate next.

Illustrative first-pass inventory and the next question for each owner
Candidate collectionPotential workflow contextUncertaintyNext action
ERP order historyOrder changes, exception handling, and delivery outcomesA migration may have changed identifiers; customer restrictions have not been reviewedAsk operations to confirm the date range and join structure; ask the contract owner about permitted uses
Maintenance work ordersFault reports, attempted repairs, and a recorded resolutionResolution quality varies; technician notes may contain personal or confidential informationAsk maintenance to document status meanings and whether outcomes can be validated; identify a privacy-review owner
Customer-support casesAn issue, troubleshooting steps, escalation, and the final outcomeRetention is unconfirmed and attachments may contain third-party materialConfirm retained history and attachment categories before discussing a sample

For each row, count a meaningful unit. “Orders” and “order-line updates” are different measures; “cases” and “messages” are different measures. In this example no counts have been verified, so the worksheet should say “unverified” rather than invent a total.

The team can now choose an internal action: investigate when the description is useful and the questions have owners; clarify when structure or history is uncertain; or pause when a restriction needs resolution. These are planning labels, not licensing eligibility scores. No dataset is approved, priced, or shared by completing the exercise.

Read where manufacturers can start and the questions to ask before licensing for the next review steps.

Use consistent units and honest uncertainty

“A million records” could mean messages, attachments, field updates, or complete cases. Use a unit a reviewer can understand. If one support case contains many messages, distinguish the number of cases from the number of individual events.

Mark estimates and unverified assumptions clearly. A system owner might know the account began in 2019 but still need to confirm whether all history is retained. Record that as a question instead of representing seven years of complete data as a fact.

Describe structure before sharing samples

A field list or data dictionary can explain a collection without revealing actual customer content. If an example is useful for an initial discussion, create a clearly labeled synthetic example or agree on a reviewed sample process. Do not pass a made-up record off as evidence of your actual data quality.

Dataset documentation research emphasizes making a dataset's origins and intended uses understandable. For this inventory, add short notes that only your team would know: what a status means, why a period is missing, or how a system migration changed identifiers.

This approach follows the documentation principle in Datasheets for Datasets: explain what a dataset contains, how it was collected, and which uses it supports. The eight-field table above is our practical starting format, not a required industry standard.

Finish with a shortlist and next actions

Choose a few candidate collections and assign an owner to each unanswered question. Your next step might be checking retention, locating a customer agreement, or confirming that an export preserves event history.

Bring that shortlist to the assessment conversation. It helps everyone discuss scope and feasibility while keeping the work proportional to the opportunity. A detailed extraction project can wait until the proposed use and review process are clearer.

With your inventory at hand, register for the webinar and use the result to prioritize your follow-up questions.

Turn your inventory into a focused next step. Our guide to preparing a sample for a quality evaluation explains what to document. For a quality-ranking inquiry, visit Ohio Training Data, our business-data quality partner.

Sources & further reading

Sources checked October 5, 2026.

About Ohio Training Data

We help businesses explore data licensing opportunities and help them request a business-data quality review. Have a question about the next step? Get in touch.