Begin with the collection you can describe
If you are unsure what counts as company data, start with the data-types overview and the company inventory. They help separate correspondence, service cases, business transactions, process knowledge and software. These are ways of describing records, not a list of confirmed buyer programmes.
Once a category is recognisable, the traceable-workflows guide helps explain how an initial request, the work performed and its outcome connect. It also separates explicit links from assumptions. You do not need to build a combined database or export the collection to use that guide.
Work out which kind of uncertainty matters
An unknown quantity is an inventory issue. An unclear permission is a rights issue. Personal information and confidentiality introduce their own protection questions. Treating all three as a single readiness score can hide the decision that actually needs attention. The rights guide and multi-entity map help keep those questions distinct.
Your business situation can change who is available and what work is proportionate. Use the situation guides for operating companies, insolvency, closure or a company transaction. Where several companies or countries are involved, identify them as an organisational question rather than assuming that a shared system creates one legal position.
Read agreement questions at the right stage
When a collection and possible use are defined, compare exclusive and non-exclusive arrangements by their scope, duration and restrictions. The retention guide deals with a different issue: what must remain available and who is responsible for it. Neither should be replaced by a headline price or an assumption that an old archive is unrestricted.
For a personal response, use the general enquiry to describe the known facts and open questions. The first conversation with BRIDGERS aims to identify a manageable subject and possible next step. It does not grant access, approve sample disclosure or commit you to a licence. Keep confidential records and credentials within your own systems.
A practical briefing for this discussion
Use the following prompts to create a short internal overview. Record what is already known, label estimates and leave unresolved points visible. The working document is for your own preparation; it is not a request to send confidential records or evidence through an initial enquiry. A missing detail can become a specific question for a colleague rather than a reason to investigate every system first.
- Identify a category: data-types overview
- Map the archive: company inventory
- Describe relationships: traceable workflows
- Clarify responsibility: rights and entity guides
- Define the proposal: process and licence scope
| Briefing prompt | Record internally | Next question |
|---|---|---|
| Identify a category: data-types overview | Known, estimated or unclear | Who could clarify this? |
| Map the archive: company inventory | Known, estimated or unclear | Who could clarify this? |
| Describe relationships: traceable workflows | Known, estimated or unclear | Who could clarify this? |
Explore the topics
Company data licensing: the decisions before a partner introductionExplore the steps towards possible paid licensing: describe company records, clarify scope and permissions, and decide on a separate partner introduction.↗Which company can answer for each part of the archive?Map entities, custody and authority across a company archive. Prepare a licensing discussion without assuming shared systems mean shared rights.↗Understand the value drivers before discussing a priceUnderstand context, quality, demand, rights and licence scope. Prepare a useful archive description without inventing a price from file counts.↗Compare what the licence allows, not just the amountCompare collection, purpose, term, exclusivity and payment conditions before choosing a company data licence. A larger offer may cover broader rights.↗Identify personal data and confidential records before a partnership discussionIdentify personal information, confidentiality, contracts and content rights before a data partnership discussion. Use a practical internal questions list.↗Keep retention decisions separate from licensingKeep record retention, system access and a proposed data licence separate. Prepare an archive review without changing existing obligations.↗Show how a business task runs across its systemsDescribe how tasks, systems and outcomes connect in a historical archive. Map known links and gaps before commissioning an export or data join.↗Questions about this topic
Which guide should I read first?
Start with the inventory if the collection is still unclear. If you already know what it contains, choose the guide matching the immediate question: context, responsibility, retention or licence conditions.
Do we need to complete every guide before enquiring?
No. An incomplete overview with clearly marked unknowns is a legitimate starting point. The guides help focus the discussion rather than create an assumed qualification hurdle.
Are these guides legal approval for a data licence?
No. They support preparation and identify questions for responsible people. The actual collection, purpose and parties require their own technical, business and legal consideration.