Home / Guides

A practical data inventory for software companies

Map engineering and customer-operations records into a clear inventory before discussing AI data licensing.

Reviewed 18 October 2026

A useful first inventory should show how engineering and customer work connect. Start with one product area or a completed project, then map the records that describe its history.

Trace a completed change

Choose a representative, non-sensitive example. What started the work? Which decisions changed its direction? How was the final result checked? Record the systems where that history lives.

Keep the context intact

Ask whether links between records still work and whether important decisions were made in systems that no longer exist. Note missing attachments, duplicate exports and periods with incomplete records. Describing those limits early is more useful than producing an impressive file count.

Separate company work from other people’s material

Review ownership and licensing before offering source code, customer material or third-party content. The UK Intellectual Property Office explains that commissioned creators normally retain copyright unless the contract changes that position. Paying for work does not, by itself, settle every onward licensing right.

Prepare for a scoped review

Take a system list and a description of the workflow to the first discussion. Agree who can review samples, how those samples will be prepared and which materials are excluded. Do not export a complete workspace just to start the conversation.