Ninety days is a useful number for a storage policy.
It is easy to understand. Easy to configure. Easy to automate.
But when the clock reaches day 90, what exactly happened to the information?
Usually, nothing happened
The business value may be unchanged. The retention requirement may be unchanged. The security classification may be unchanged. The information may still be part of an active case, project, customer relationship, analytical workload, or regulatory obligation.
Only one thing changed: the timestamp.
That is an infrastructure event, not necessarily an information event.
Storage policies became lifecycle policies
Many lifecycle practices evolved from the needs of storage infrastructure. Expensive performance capacity had to be protected, so older or less frequently accessed data was moved to less expensive tiers.
That is a legitimate storage optimization technique.
The problem begins when that operational mechanism becomes the organization's definition of the information lifecycle itself.
A business event looks different
A contract expires. A legal hold is issued. A case closes. A regulatory retention period begins or ends. A dataset becomes training material for AI. A record becomes evidence. An information object is superseded by an authoritative replacement.
Those are meaningful changes in context.
They provide a much stronger basis for lifecycle decisions than the passage of an arbitrary number of days.
Use policy to connect context to action
The answer is not to abandon time-based rules. Age can be useful evidence and may be directly relevant to retention or operational policy.
But it should be evaluated alongside identity, relationships, business value, risk, security, protection, compliance, availability, provenance, and other relevant context.
Policy can then determine what should happen and why.
The goal is better decisions
The shift is subtle but important.
Instead of moving information because it became old, move it because its requirements changed.
That turns lifecycle management from a storage schedule into an information-governance capability.