Find the technical knowledge before requesting more work
The person who understands the engineering folders may not manage the servers or software licences. Record those roles separately. The immediate need is to identify information and responsible contacts, not to give a third party passwords or new access permissions.
Ask the responsible IT contact whether the records sit on a server, in project folders, within PDM or PLM, or with a service provider. A backup may be a source, but its existence does not show that it can be restored into a usable engineering collection. Any access to or changes in operational systems require agreement with those responsible.
A working template for your internal overview
| Area | What to record internally | A useful way to leave uncertainty visible |
|---|---|---|
Systems |
Known CAD products, versions and management tools |
Version to be confirmed by technical support |
Scale |
Separate project, design and file-group figures |
File count estimated; duplicates not assessed |
Period |
Known project years or archive sections |
Earlier predecessor-company records are included |
Relationships |
Models, drawings, revisions and supporting records |
Some assembly references have not been checked |
Provenance |
In-house, supplied and mixed material |
Customer contributions have not yet been separated |
Access |
Responsible function and known dependencies |
Access may depend on an active software licence |
Keep this detailed working document inside your organisation. Storage paths, customer names, credentials and individual records do not belong in the first message to BRIDGERS.
Keep different counting units separate
A project may contain several assemblies, each referencing many files. A drawing can exist in several revisions and again as a PDF. Keep existing project and file counts alongside one another rather than turning them into an apparently precise number of independent designs.
Unknown is a valid answer. If a file listing already exists, the responsible person can explain what it covers. You do not need a new complete count for the first enquiry. The scope and effort of any later inventory are discussed separately.
The counting guide helps distinguish designs, revisions, exports and duplicates without treating them as interchangeable units.
Availability and authority need different checks
An accessible project folder may contain customer drawings, third-party libraries or work inherited from another business. A potentially relevant collection can also be difficult to access technically. These issues require different information and, often, different people.
Use the design provenance guide to organise sources and unresolved permissions. Neither age nor a past outsourcing arrangement provides clearance by itself. Existing retention, confidentiality and insolvency-related duties remain separate considerations under the applicable rules and circumstances.
Move from an overview to a sample only by agreement
If a defined collection appears worth exploring, a later conversation may consider a few representative projects. Native files, assembly references, drawings, revisions and related manufacturing or inspection records may then be considered together. An archive-wide overview and a sample perform different tasks.
Before any transfer, the scope, recipient, purpose, protection measures and necessary agreements are established separately. The process overview explains those approval points. For the initial enquiry, your current technical knowledge, role and open questions are sufficient.