Define one manageable part of the archive
Choose a recognisable group: a support system, a period of correspondence or records associated with one business unit. Use a separate row when the company responsible, source or known restrictions differ. A shared server or application does not establish that every record has the same rights position.
If several companies or countries are involved, record that uncertainty. The address of an adviser making the enquiry may differ from the location of the business whose archive is being described. Keep those facts separate. Exact legal entities and applicable rules can be clarified with the responsible people later.
The data-types guide helps you choose a starting category. The categories are inventory prompts, not confirmed purchasing programmes.
A working inventory you can keep internally
Keep estimates labelled as estimates. A count of messages cannot be added to a count of support cases to produce a meaningful archive total. Copies of the same case in different systems should not silently become separate cases. Unknown quantity is different from a confirmed empty archive.
The overview should describe the collection without reproducing its contents. Customer names, project identifiers and actual messages are unnecessary for an initial discussion.
| Field | What to record at this stage |
|---|---|
| Category and system group | Correspondence, support, a business system, development records or document storage; no access details |
| Period | Known or estimated start and end years, or unknown |
| Scale and unit | A known or estimated number of messages, cases or documents; identify the category it describes |
| Business context | Whether a request, the work performed and its outcome remain connected |
| Source and responsibility | Own, received or mixed contributions; which company or function could answer questions |
| Protection questions | Possible personal information, confidentiality, contractual restrictions or unresolved authority |
Prepare a short briefing
Bring five points together for the first conversation:
An incomplete briefing is usable. Mark a missing answer and the next person or function who might know; you do not need to investigate every system before asking. Keep confidential company and client details in your internal notes. The first enquiry uses general descriptions and your own contact details for a requested reply.
- Which categories and system groups you recognise.
- The approximate period and scale, with units and unknowns marked.
- Whether records preserve a business sequence and its outcome.
- Your role and what is known about the companies and countries involved.
- Known protection or authority questions and the functions that could clarify them.
Recognise CAD as a separate collection
CAD models, drawings and revision records may form a distinct collection inside a wider company archive. Note whether models, assemblies and drawings remain connected and whether their source is known. The CAD licensing overview explains the specialist context on another website. Following this voluntary link does not transfer answers from the general enquiry. You can describe engineering records alongside other business records here in one enquiry; moving to the specialist website is not required for a mixed archive.
Turn open questions into a next step
An unclear permission or possible personal information should remain visible in the overview. Use the personal-data and confidentiality guide to identify the responsible review, rather than treating a complete inventory as legal clearance.
When you want a personal response, submit the general outline through our enquiry. Please retain files, message contents, code, repository links, contracts and credentials in your systems. The licensing process explains the separate decisions before any possible partner introduction.