Separate the reasons records remain available
A business may retain records for operational needs, contractual commitments, evidence or applicable legal duties. Those reasons can differ within one system. A completed financial period, closed customer case and old employee record should not be assigned the same retention rule merely because they are stored together.
This guide does not prescribe a universal storage period. Identify the category and the responsible function, and seek appropriate advice for the actual context. Being lawfully stored for one reason does not by itself authorise a new purpose or disclosure to a partner.
Understand access and preservation constraints
A planned system shutdown or supplier exit can affect whether records remain usable. Note existing arrangements, accessible copies and who can explain them. A backup may preserve files without preserving the application or relationships needed to interpret them. That practical uncertainty belongs in the review.
Do not change retention, delete originals or create new unrestricted copies because of a possible licensing opportunity. Decisions about continued storage, migrations and access should follow their own requirements. The initial enquiry needs a description, not the underlying archive.
Create a review plan with separate decisions
For each collection, identify the purpose of retention, custodian, approximate period and any access deadline. Add an independent column for a possible licensing review and its open authority questions. This prevents a commercial discussion from silently becoming an instruction about statutory records.
BRIDGERS can discuss whether a defined subset suggests a proportionate next step. Any preparation or sample disclosure requires an agreed scope. A licence, if one is reached, must coexist with the duties and restrictions applicable to the collection; a promising price cannot resolve those duties.
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.
- Record category and reason for retention
- Responsible function and custodian
- Period and known access deadline
- Originals or systems that must remain available
- Separate authority for proposed additional use
| Briefing prompt | Record internally | Next question |
|---|---|---|
| Record category and reason for retention | Known, estimated or unclear | Who could clarify this? |
| Responsible function and custodian | Known, estimated or unclear | Who could clarify this? |
| Period and known access deadline | 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
Does licensing replace our archive?
No. A proposed additional use and existing record obligations answer different questions. Determine what must remain available and under which arrangements.
Should we postpone a system shutdown for this opportunity?
Record the deadline and ask the responsible people to assess access and preservation requirements. The website does not direct an extension or termination.
Is a retained backup automatically usable for licensing?
No. It may lack context, access tools or necessary permissions. Technical availability, interpretability and authority need separate consideration.