DATA TYPES

Which business records should you inventory?

Which company records would you like to discuss for possible paid licensing? The six categories below help identify a collection and its context: for example, a customer request, the work performed and the outcome. Start with the system you recognise. These are inventory prompts, not a list of confirmed buyer programmes or accepted data types. BRIDGERS discusses possible data partnerships as an intermediary. We do not buy company records. Your first enquiry describes the collection; the underlying contents stay with you.

Discuss your company data

Email and correspondence

Note the approximate period and whether messages, replies and attachments still belong to identifiable business sequences. A collection of complete correspondence differs from disconnected individual messages. Record whether business and private material may be mixed and which company or function could explain the source.

Possible employee, customer or professional confidentiality questions need their own review. Describe those categories without opening or copying real messages for an enquiry.

Support and service records

A service system may preserve the original issue, actions taken and the eventual resolution or status. Identify whether those stages remain connected. Approximate periods and broad service categories can help define a manageable collection.

Customer details, attachments, sensitive case information and credentials embedded in tickets are protection questions. Do not submit real tickets as evidence of quality. A category label alone does not show that a partner can use the records.

ERP, finance and accounting

Look for relationships between orders, deliveries, invoices and postings. Note whether those relationships remain available or whether only separate exports survive. Distinguish the companies and periods involved; an application used by a group may contain several different sources and responsibilities.

Financial confidentiality, personal information and retention obligations remain separate issues. Preparing an overview does not authorise changes to the original records or their retention.

CRM and sales history

Identify whether the system contains a sequence of activity, decisions and outcomes or primarily a current contact list. Historical context can change what the collection describes. Note the source and any known customer restrictions.

Contact information, assessments of people and confidential commercial discussions need particular attention. This inventory concerns business records; it does not present a marketplace for selling contact lists.

Your own software and source code

Record the broad project type, original development period and whether its original Git history remains available. Earlier public availability, human or AI-generated contributions, own development and third-party components need distinct answers.

Software has its own detailed enquiry path, chosen explicitly in the general check. Merely including code in a mixed inventory does not qualify it for that path or confirm acceptance. Keep code snippets, repository links and access details out of the first enquiry.

Process and quality documents

Work instructions, process descriptions and quality documents need a version and operational context. Can the responsible function distinguish current material, earlier versions and records of actual use? Note which documents originated in the business and which came from customers or service providers.

Internal methods, personal information and third-party contributions may require different permissions. A document's age does not establish that those questions have disappeared.

Choose a starting point

Use the company data inventory to turn those notes into a short internal overview. Unknown details can remain unknown. The protection questions help keep permissions and confidentiality visible.

What you recogniseUseful next note
A complete business sequenceWhich stages and outcome remain connected
Separate documents or exportsWhich links or context are unknown
Several companies in one systemWhich responsibility and source boundaries need clarification
A large collection with little current knowledgeWhich function could help describe one manageable part
Different categories in the same archiveWhich parts can be distinguished without exporting contents

CAD models and drawings in the archive

Treat models, assemblies, drawings and revision records as a separate category when describing the collection. Their connections and source matter alongside the file count. The CAD licensing overview provides the specialist context on another website. The link is voluntary and does not transfer answers from your enquiry. For a mixed collection of engineering and general business records, you can stay here and make one general enquiry rather than submit the same overview twice.

For a first discussion, send descriptive information about the categories and open questions. Keep files, messages, contracts, code and credentials in your systems. A specific partner introduction requires a separate, documented approval by the authorised decision-maker.

THE FIRST STEP IS A DESCRIPTION.

What records would you like to discuss?

Start with what you know. No files, exports or confidential material are needed for your first enquiry. Open questions can stay open.

Discuss your company data