Start with the work your team records.
An internal knowledge base, project history, or resolution log can be described for an initial review. These examples show what to inventory. A buyer still needs to assess the material.
| Team | Records to inventory | Review point |
|---|---|---|
| Software and product | Specifications, issue histories, decision records | Code rights and customer contributions |
| Support | Investigation notes, resolution histories, runbooks | Messages, attachments, and identifiers |
| Professional services | Internal playbooks, review procedures, delivery processes | Client-owned work and confidentiality |
| Business operations | Standard procedures, exception logs, process changes | Customer information and commercial restrictions |
Prepare five company details.
Start with the business and its records. Approximate figures are useful when exact counts are unavailable.
- Industry and team size.
- Record types and the systems that hold them.
- Retained history and language.
- Known ownership or confidentiality restrictions.
- The role responsible for reviewing a potential license.
Fit depends on the records and the request.
A company-size band does not establish eligibility. Buyers may need particular workflows, languages, dates, or types of documentation.
Review the licensing requirements guide or read about software-company records.
Describe the records before exporting.
Use the data inventory template internally. Keep underlying records in your systems during the initial fit check.