Map the collections that will remain
Begin with communication systems, business applications, support platforms, development records and document stores. Note each period, whether access is available and the function that understands the contents. Separate a usable application, a backup believed to exist and an unverified reference in an old inventory.
A backup is not evidence that records can be restored with their original relationships. Folder names may not explain the business context. A former operational colleague may be able to describe workflows without restoring or exporting the whole application.
Plan for responsibility after people leave
Who will hold the records, answer questions and decide whether additional review may take place? These can be different parties. A supplier may host infrastructure while another representative is responsible for decisions. Record those distinctions, including changes in availability and known service endings.
Closure provides no blanket permission to retain everything indefinitely or delete records early. Existing duties and commitments are separate questions for the responsible people. A potential licence is an optional commercial path, not a substitute for an orderly records plan.
Make a limited commercial decision
Identify collections sufficiently understandable to discuss without substantial new work. Include access dates and the likely effort of recovering context. A modest, well-defined archive may be easier to assess than a large collection with unexplained sources and permissions. Storage volume is not a reliable priority on its own.
An enquiry to BRIDGERS can describe the overview without sending records. Further work depends on the collection, an actual partner path and available permissions. If no proportionate route emerges, retaining the overview for internal closure planning may be the appropriate outcome.
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, system group and period
- Accessible, backed up or unverified
- Custodian after closure
- Knowledge and decision contacts
- Service endings and retention questions
| Briefing prompt | Record internally | Next question |
|---|---|---|
| Collection, system group and period | Known, estimated or unclear | Who could clarify this? |
| Accessible, backed up or unverified | Known, estimated or unclear | Who could clarify this? |
| Custodian after closure | Known, estimated or unclear | Who could clarify this? |
Questions about this topic
Should we cancel software access before review?
Record intended cancellations and discuss access with the responsible people. This guide does not instruct you to extend or terminate a service; the decision depends on actual duties and needs.
Does closure remove confidentiality restrictions?
No automatic conclusion follows. Identify sources, commitments and people able to review a proposed new use.
Is an enquiry an archive-custody arrangement?
No. The enquiry describes a commercial option. Custody, access and ongoing record obligations require their own arrangements.