Start with the records, not the organisation chart
A group-wide CRM may hold activity from several subsidiaries. A finance application can contain separate company ledgers, while a shared document store mixes projects delivered for different customers. Begin with a recognisable business collection and ask which entities created, used or received those records. Being part of the same group does not by itself establish one company’s authority over every contribution.
Use separate entries where the period, source or responsible company differs. An uncertain allocation should remain uncertain. For an initial conversation you can describe the structure in general terms; there is no need to disclose customer identities, individual transactions or confidential agreements.
Separate custody from the right to license
The company paying for a server or software subscription may be the technical custodian rather than the party able to grant additional rights. An IT provider may have access without permission to authorise a new use. Employees, contractors and external partners may have contributed under different arrangements. Distinguish these roles rather than treating access as ownership.
Past acquisitions, mergers or carve-outs can complicate the picture. Record that a transfer occurred, its approximate date and the function that could explain it. This is a prompt for a focused review, not a conclusion about the legal effect of the transaction.
Build an entity-and-system map
Give each business collection a row. Add its system group, period, participating companies and the function that could answer a later question. Describe the company’s known role: creator, user, custodian or unclear. This makes it easier to identify a manageable scope and the decisions needed before samples.
BRIDGERS can discuss the map at metadata level. It does not amount to consent from the companies involved, a mandate to combine their data or permission to approach every potential recipient. A later introduction and licence need a defined collection and the appropriate decisions from the responsible parties.
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.
- Collection and business purpose
- Company role: creation, use or custody
- Period and relevant system changes
- Known transfers or third-party contributions
- Who can clarify an unresolved permission
| Briefing prompt | Record internally | Next question |
|---|---|---|
| Collection and business purpose | Known, estimated or unclear | Who could clarify this? |
| Company role: creation, use or custody | Known, estimated or unclear | Who could clarify this? |
| Period and relevant system changes | Known, estimated or unclear | Who could clarify this? |
Primary reference for further review
The applicable rules and responsibilities must be assessed for the actual collection, purpose and countries involved. The following primary text supports that discussion; reading a source is not an approval of a particular archive or licence.
Questions about this topic
Can the parent company approve every subsidiary’s archive?
Group membership alone does not answer that question. Identify the relevant entity, collection and agreements. The appropriate parties need to decide the scope of any additional use.
Should we name confidential clients in the first enquiry?
No. Describe categories and responsibility questions without individual clients or matters. Identify your contact organisation separately from the business whose records are being considered.
What if the responsible entity is unclear?
Keep that as an open issue. A preliminary discussion can help define the question, but uncertainty is not permission to disclose samples or license records.