Start with recognisable groups
You do not need to trace every component before making contact. Begin with groups that differ in how they were created or who was responsible: internal development projects, externally commissioned work or supplier components within an assembly.
A mixed project does not need to be forced into a single source category. Mark it as mixed and describe the known contributions in general terms. “Origin not yet established” is a useful answer because it identifies a question for follow-up instead of suggesting certainty that does not exist.
Build an internal provenance matrix
| Source | Useful information to record internally | What still needs separate review |
|---|---|---|
Your employees |
Approximate period, business unit and available internal records |
Authority for the specific additional use being considered |
External designers or contractors |
Broad nature of the commission and where agreements can be found |
The agreed rights, restrictions and other contributors |
Customer-provided material |
Whether it was an input, reference or part of a project |
Customer rights, contractual purpose and confidentiality obligations |
Supplier files |
Components, drawings or subassemblies included |
Supply terms and limits on onward use |
Libraries, templates and standard parts |
Known source or library type |
Licence conditions and whether material needs to be excluded or treated separately |
Inherited or mixed archives |
Systems, businesses and project phases involved |
What evidence remains and who can explain the uncertain parts |
Entries in this matrix do not grant permission. For the first enquiry, a summary of the categories and your current knowledge is enough. Original agreements, named project records and the files themselves can stay in your systems.
Keep three different questions separate
Where did the content originate? This concerns its creation. An internally developed assembly can include a supplier model. Its location in your project folder does not establish how every component was created.
What authority is already documented? This concerns the permitted uses and their limits. An invoice, storage device or archive login does not provide a complete answer. Employee-created work should not automatically be treated as available for every new purpose either.
What information requires protection? Current product configurations, customer relationships, technical details and contractual confidentiality may all matter. Removing individual names does not settle whether the proposed purpose is allowed or the engineering information can be disclosed.
Describe a mixed archive honestly
Here is a fictional example. An archive holds internally developed assemblies, drawings based on customer specifications and models of supplied components. The technical team can partly separate those groups, but has not yet checked the applicable rights.
A useful initial description would be: “Historical design archive containing original and third-party material. Some groups can be separated technically. Permissions and confidentiality restrictions are still being reviewed internally.” That identifies a collection and the open questions without presenting the whole archive as cleared for licensing.
Make supporting evidence findable, not public
Identify internally which team understands the engineering structure and which can locate relevant agreements. In a formal procedure, authority to provide information or approve a further step may also need to be established.
The enquiry only needs your current knowledge. Please do not paste contract extracts, customer names, staff lists or confidential project details into a form. Any subsequent review requires its own scope, recipients and approvals.
BRIDGERS is an intermediary, not the buyer of your archive. Unresolved permissions can be discussed; an enquiry does not automatically trigger disclosure to a data partner. See native files and exports if the technical categories themselves are uncertain, or the licensing process for the next decisions.
Legal references in their proper context
For German material, section 31 and section 43 of the Copyright Act address rights of use and employment-related works. Section 2 and section 4 of the Trade Secrets Act concern protected information and unauthorised use or disclosure. These sources explain separate review questions in that context. They do not settle a particular contract or establish licensing authority in another jurisdiction.