Information lifecycle management
Definition
Information lifecycle management
Information lifecycle management (ILM) tracks a record from the day it is made to the day it is destroyed: create, use, store, archive, dispose. Information governance sets the rules and the owners; ILM is those rules running on a clock, stage by stage.
The point is to stop information living forever by default. Every record has a reason to exist and a date on which that reason expires.
Keeping everything is not caution — it is cost, and it is a larger pile for an attacker to carry away. Disposal is the stage teams skip, and the one a regulator asks about first.
Retention dates are a business decision — not a storage one. Technology can move a file anywhere you like, but only the business can say how long the reason for holding it survives.
Done well, ILM is invisible to the people doing data entry. They capture the record; the schedule does the rest.
Key takeaways
- ILM moves a record through five stages: create, use, store, archive and dispose.
- Governance sets the retention rule, and ILM executes that rule on schedule.
- Disposal is a stage with its own evidence, not an afterthought nobody logs.
- Storage tiering only saves money when the retention dates behind it are right.
How it works
ILM attaches a clock to a record at the moment of capture. You classify it, give it a retention period, move it to cheaper storage as it cools, keep it if law or value demands, then destroy it and record that you did.
| Stage | What happens | Control that matters |
|---|---|---|
| Create | Record is made or received | Classification at capture |
| Use | Staff read, amend and share it | Access logging |
| Store | Moves to cheaper storage tiers | Integrity checking |
| Archive | Held for legal or historic value | Format migration |
| Dispose | Destroyed or transferred out | Certified sanitization |
Controls make those stages real rather than notional. United States records regulations require electronic systems to carry controls for reliability, authenticity, integrity, usability, content, context and structure.
The wording there is worth borrowing. The stated aim is that records can document the business properly for as long as the information is needed, which is a cleaner test than any storage policy.
Disposal has a standard of its own. The National Institute of Standards and Technology (NIST) issued Revision 2 of its media sanitization guideline in September 2025, superseding the 2014 edition that most older policies still cite.
That revision defines sanitization as rendering access to target data infeasible for a given level of effort. It is an honest definition, because it admits that effort, not certainty, is the real variable.
An information security policy sits alongside this work rather than inside it. The policy states how records are protected for as long as they exist; the lifecycle decides how long that is.
Legal holds are the exception that proves the clock exists. When litigation or an investigation starts, the schedule stops for the affected records and nothing is deleted until the hold is formally lifted.
Format is the quiet failure mode. A record kept for thirty years in a file format nobody can open has technically been retained and practically been lost, which is why archive stages plan migrations in advance.
A database administrator usually holds the levers for the middle stages, while a data quality analyst checks that what survives each move is still usable.
Examples
Four sectors run visibly different clocks on the same five stages. What varies is the trigger that starts the clock and the length of the retention period; what never varies is the need for someone to log the disposal.
Banking. Transaction records outlive the accounts they belong to, often by years after closure. That makes archive format the live problem, since a file nobody can open is not really retained.
Contact centres. A recording made for quality coaching and a recording kept for a disputed sale follow different clocks — same file, two rules. Teams usually tag at capture so the shorter clock does not delete the longer one.
Analytics and research. Firms running data mining across old archives find the lifecycle question in reverse: what was kept, in what shape, and whether consent still covers the new use.
Manufacturing. Maintenance and inspection logs stay relevant for as long as the machine runs, which can be decades.
The clock there is tied to an asset rather than to a calendar year — so the schedule keys off disposal of the equipment, not the date the log was written. Plants that get this wrong destroy evidence they later need for a warranty claim.
Providers of data center outsourcing will happily run your storage tiers. They cannot tell you what your retention periods should be, and a good one will say so in the first meeting.
Related terms
- Call recording: produces audio records whose retention clocks are set by purpose and consent.
- Call detail recording: logs call metadata, which is often kept far longer than the audio itself.
- Database administrator: operates the storage, backup and purge mechanics behind each stage.
- Data quality analyst: checks that records stay accurate and usable as they move and age.
- Data center outsourcing: hands storage operations to a provider while retention rules stay in house.
FAQ
How is information lifecycle management different from information governance?
Governance decides the rule and names the owner who may change it. Lifecycle management is that same rule in motion, applying retention periods, storage moves and deletions to actual records on actual dates.
What are the stages of information lifecycle management?
Create, use, store, archive and dispose. Some models split use into an active phase and a reference phase, but the destruction stage is the one most often left undefined in practice.
Is archiving the same as deletion?
No. Archiving moves a record out of daily use while keeping it readable and provable, whereas disposal ends the record and should leave a certificate behind it.
Does ILM reduce cost or risk?
Both, and in that order of visibility. Cheaper storage tiers show up in the budget within a quarter, while the risk benefit only becomes obvious when a breach touches a much smaller pile of data than it would have done.
Who owns information lifecycle management day to day?
Records and technology operations share it, under a single governance owner. The split works when retention dates come from the business and the mechanics of moving and deleting come from the technical team.
Compare providers with records and storage experience in the Outsource Accelerator directory before you move any archive.
Independent
