A manufacturer needs a decade-old calibration report to investigate a customer concern. The file exists on a retained storage volume, but its proprietary viewer no longer runs and the file name does not identify the measuring equipment. Keeping the bytes was not enough. Long-term records assurance must preserve content, context, technical interpretability and secure access for the entire required period.
01Treat readable evidence as a managed business capability
A record remains useful when an authorized person can retrieve it, render the meaningful content and understand its connection to the underlying transaction. A successful checksum or backup job addresses integrity of stored bytes but not whether the file can be interpreted without obsolete software. The preservation objective should name the content, metadata and relationships that matter.
Some records depend on specialist systems, embedded objects, digital signatures or linked attachments. Identify these dependencies before retiring applications. A policy that says “retain for ten years” is incomplete if the organization lacks a plan to read the evidence in year nine.
02Identify formats at risk of becoming unusable
Build a format inventory for records with material retention requirements. Include legacy office formats, CAD drawings, electronic laboratory results, email archives, encrypted containers, databases and scans. Assess reliance on licensed applications, unsupported codecs, operating systems, plugins or encryption keys. Record any preservation action needed to preserve meaningful content.
Not every format must be converted immediately. Risk depends on retention horizon, importance, software support and ease of future access. Prioritize unique evidence or records needed to defend consequential decisions. Test the chosen conversion format with real representative files rather than assuming a nominally open format preserves every relevant property.
03Preserve context and authenticity through metadata
A historic image may appear clear while lacking the date, process, identity or approval context needed to explain its evidentiary significance. Preserve creator, time reference, source system, business identifier, classification and relationships to transactions. ISO 15489-1 and ISO 23081-1 offer complementary principles for records and metadata.
Where digitally signed records must remain legally meaningful, obtain specialist advice on long-term signature validation and evidence preservation. A visual image of a signature is not always equivalent to the original validation information. Record transformations so a reviewer can trace the relationship between the original and a preservation rendition.
04Design conversions and migrations as controlled events
Before migrating, identify which properties must be preserved: tables, formulas, attachments, page order, annotations, audit trail or technical geometry. Capture a baseline and sample results after transformation. Use a secure chain of custody, preserve an immutable source copy when justified, and document the tool, date, scope and approval.
Keep an exception log for unreadable or partially converted objects. Do not silently discard unsupported attachments or rewrite historical metadata to match new conventions. An apparently successful batch conversion may lose content in rare but high-value file types, so sampling should deliberately include unusual cases.
05Make retrieval tests representative and repeatable
A meaningful preservation test asks an authorized user to find a selected old record, access it through the current environment and explain what it demonstrates. Include records from multiple years, systems, sensitivity levels and retention classes. Measure whether all necessary pages and attachments are present and legible.
Choose the test set partly at random and partly by risk. A curated demonstration of familiar PDF files gives weak assurance for an archive containing specialized engineering or medical formats. Document failures and remedial action. Repeat tests after significant platform changes, not only at scheduled annual dates.
06Protect records while keeping them available
Controls for confidentiality and integrity should be compatible with long-term access. Key management, account succession, access logging and disaster recovery matter when records outlive staff and IT platforms. Excessive encryption without preservation of decryption capability can make retained evidence inaccessible to legitimate custodians.
The data owner should determine lawful use, while IT maintains technical reliability and records specialists preserve context. Provide a controlled path for urgent retrieval during litigation, customer requests or operational incidents. Do not grant broad unrestricted access merely to simplify future retrieval.
07Illustrative scenario: a retired laboratory system
Illustrative scenario: a laboratory decommissions its old instrument software but must retain testing evidence. During pre-retirement review, the records team learns that exported PDFs do not preserve instrument configuration values needed to reconstruct a result. The migration plan retains validated reports plus a structured export of essential metadata.
The team tests both outputs with independent reviewers and records remaining limitations. The laboratory does not claim that the converted files are technically identical to the original application output; the acceptance decision is based on the defined evidentiary properties. The scenario illustrates why conversion requirements must be specific to the record.
08Set preservation triggers and ownership for the next decade
Assign monitoring responsibilities for format obsolescence, application retirement, security changes and preservation-platform upgrades. Use an inventory of long-lived record series and decide when a new rendering or migration test is necessary. Preservation is a recurring process, not a storage purchase made once.
At management review, present failed retrieval tests, aging unsupported formats, unowned collections and unresolved conversion exceptions. The outcome should be a funded plan for high-risk evidence. A record preserved for years but lost when needed is a governance failure, even if all backup jobs previously reported success.
| Control area | Required decision or record | Evidence test |
|---|---|---|
| Readable content | Native and preservation rendition | Reopen in supported environment |
| Provenance | Creator, event, object relationship | Reconstruct original purpose |
| Migration | Source hash and conversion manifest | Document exceptions and transformations |
| Recovery | Rights, keys and backup restorability | Authorized retrieval after disruption |
Practical Verification Checklist
- Can old representative records be opened and understood on current supported systems?
- Were authenticity, critical metadata, attachments and relationships preserved during migration?
- Is conversion evidence available and are partial failures formally tracked?
- Does the custodian have a tested path for lawful retrieval despite obsolete software or staff turnover?
Build a preservation test set
Select high-value records from each major format and retention age. Record the file properties that a future authorized reader must recover and identify dependencies on external software.
Repeat a retrieval and interpretation test in a clean environment, not just the original system. Capture the failures as funded preservation work with accountable ownership.
Closing Perspective
Long-term retention has value only when records retain readable meaning. Preserve bytes, provenance, interpretability and access rights together, and test them after every material system change.
Technical reading: The source descriptions for ISO 15489-1:2016 and ISO 23081-1:2017 provide the applicable terminology and guidance. Determine requirements from your organization’s actual risks, obligations and scope.
References & Further Reading
The following authoritative publications provide relevant management-system, information-security and records-management guidance. Applicability depends on business context and jurisdiction.
- ISO 15489-1:2016 — Records management concepts and principles
- ISO 23081-1:2017 — Metadata for records, principles
- ISO 16175-1:2020 — Software for managing digital records
- U.S. National Archives — Universal Electronic Records Management Requirements
- ISO/IEC 27001:2022 — Information security management requirements