Nobody opens a records retention schedule and feels a flutter. It’s a table: categories, triggers, citations. About as thrilling as a dial tone.
Employees are not tables. They’re people, and people don’t make records decisions from calm, policy-based rationality. They make them from habit, nerves, and one small, persuasive voice that whispers, just keep it…what’s the harm? If a RIM program wants actual compliance it has to speak to the behavior, not the tidy, rational person the policy imagines. Call them the three records attachment styles: ghosting, clinging, and guilt-keeping. Every organization has all three; a compliant program needs an answer for each.
Ghosting: The Slow Fade
Ghosting isn’t a decision, which is what makes it so common and hard to catch. A file gets opened, gets half-finished, and then…nothing. No classification, no retention trigger, no disposition, not so much as a goodbye text. The project ends, and the document stays exactly where it was left.
Nobody chose to keep this record. Nobody decided it still had business, legal, or fiscal value. It’s there because closing a loop takes a little courage, and inertia never has to raise its hand. Every organization has its monument: the departed employee’s drive nobody will open and nobody will delete.
This is how shared drives become storage units: not scandal, just avoidance, one unfinished thing at a time. The industry has a name for the pileup: ROT (redundant, obsolete, trivial), what happens to files nobody breaks up with. An unclassified record never starts its retention clock, which is exactly how ROT accumulates: nothing ever becomes eligible to leave. And it isn’t a rounding error. Veritas’s Global Databerg Report put a third of stored organizational data in the ROT pile, with just 15% business-critical, and still the number the industry reaches for.
The fix is simple: build an actual ending into the process. Closeout checklists, matter-closing steps, offboarding workflows, all answering one question: what happens to this now? Give records a proper goodbye, or the drift continues. Quietly. Forever.
Clinging: Separation Anxiety, But Make It a Spreadsheet
Then there’s the opposite instinct: the file saved five times, CC’d to three people who never asked, kept “just in case” long past its purpose. This feels careful. It is chaos wearing a very convincing cardigan.
Clinging comes from a familiar fear: what if the official copy disappears? What if I need my version? What if it holds the one perfectly written sentence I’ll want to reuse someday? How will I live without it? So the file multiplies, which is the records-management equivalent of texting “did you land yet?” before the plane has left the gate.
The tender truth is these convenience copies don’t make anyone safer. They get harder to govern, harder to secure, and nearly impossible to dispose of defensibly, because you cannot confidently delete what you cannot find. Every extra copy widens the discoverable footprint and hands a legal hold one more place to fail. The cure isn’t a stern memo about “using the approved repository.” It’s making the system of record so obviously trustworthy, so unmistakably the one, that nobody feels the need to keep a backup, just in case.
Guilt-Keeping: Deleting Feels Disrespectful
Someone worked hard on this. Deleting it feels like erasing the effort, even though nobody’s opened it in three years.
That’s guilt-keeping—mistaking the file for the work. But records are not trophies, and certainly not shrines. It was done, delivered, everyone’s dignity intact. The file hanging around adds nothing to that legacy, just storage cost, over-retention risk, and privacy exposure that grows as personal data sits somewhere it no longer belongs.
Disposition, done properly, isn’t disrespect. It’s discipline and the difference between giving a record a proper retirement and letting it die at its desk.
Records Retention Compliance. The Fix Isn’t a Better Policy. It’s Permission, Made Easy.
One distinction first, because the two are not disposed of the same way. Transitory content and ROT can usually be deleted at an employee’s discretion under policy; nobody convenes a committee over a stale draft. Official records that have reached the end of their retention period are different. Their disposition follows set steps: a review against the retention schedule, a legal-hold check, sign-off from the records or legal owner, and a certificate of destruction logging what went, when, and on whose authority. If a hold is active, disposition stops cold until it lifts. That paper trail is the whole point; it is what makes the disposal defensible when a regulator or opposing counsel asks. The attachment styles flourish mostly in that first lane; the second has guardrails for good reason, and no one should be freelancing there.
Most training answers this with more clarity: tighter schedules, longer FAQs, another reminder nobody reads. Clarity helps, but the gap isn’t knowledge. It’s confidence; doing the right thing takes more effort than doing nothing.
A few moves change behavior:
- Give a real deadline, not a vague rule. “Retain per applicable schedule” tells no one what to do on a Tuesday afternoon. A specific date does.
- Say it out loud. A policy buried in a handbook does nothing while someone’s hovering over delete. A manager saying, plainly, “you can let this go. Keeping it doesn’t honor the work, it just costs us more, for longer,” does everything. They don’t need another line in a policy; they need a person in the room giving them the nod.
- Make deleting the applauded move, and put it on the calendar. Right now, keeping everything looks responsible and deleting looks risky. Flip the script: celebrate the shared-drive cleanup the way you’d celebrate a launch, and give it actual hours. Disposition never fits into spare time. Smart organizations schedule cleanup days rather than hoping closure happens between meetings.
- Make defensible disposition the easy button. If disposition means hunting down a schedule, guessing at a category, and praying nothing’s under legal hold, most people choose inaction. Automated retention triggers and governed, one-click workflows that say this is eligible, here’s why, click to confirm remove the guesswork and the nerve, with approvals still running behind the scenes. The system does the deciding, not somebody’s gut at 4:45 on a Friday.
The Real Records Retention Opportunity for RIM Professionals
Compliance-first messaging assumes people make rational, policy-based decisions about their files. They don’t. They ghost, cling, and guilt-keep their way through inboxes and shared drives the same way they navigate every other relationship, not because they’re careless, but because they’re wonderfully, predictably human.
It’s what happens when humans decide with their hearts what to keep and what to release. The RIM professionals who get real traction aren’t the ones with the most exhaustive schedule. They’re the ones who name the attachment styles running underneath the policy, design programs that work with them, not around them, and make the defensible choice the most charming option in the room.
Records may not actually have feelings. Employees definitely do. And the organizations that say so, out loud, are the ones who’ll get their information and their people happily, elegantly under control.
Disclaimer: The purpose of this post is to provide general education on records management and information governance topics. The statements are informational only and do not constitute legal advice. If you have specific questions regarding the application of the law to your business activities, you should seek the advice of your legal counsel.