There's a closet in most practices that nobody wants to open. Banker's boxes stacked three high, a few labeled in marker that faded years ago, the rest a mystery until you lift the lid. Every closed matter, every old chart, every lapsed policy file went in, and almost nothing has come back out.
Two things are true about that closet at once, and both cost you. You're holding files well past the date you were allowed to destroy them, which quietly turns old records into a liability (a subpoena, a breach, a discovery request all reach whatever you still have). And somewhere in the same pile, the one file you actually needed got tossed early, by someone cleaning house on a slow Friday, because no one could tell which box was safe to shred.
The gap between those two failures is small, and it's the same gap. No file has its own clock. Fix that one thing and most of the closet takes care of itself.
Why the pile only grows
Nobody in a practice sets out to hoard files. It happens because destroying a record takes a decision, and the decision takes knowledge nobody has at the moment the box gets stacked: is this one safe to shred yet? When the honest answer is "not sure," the safe-feeling move is always to keep it, so everything stays.
Multiply that small hesitation by every closed matter over a decade and you get the closet. The cost hides until it doesn't. Records you were free to destroy years ago are still discoverable, still breachable, still sitting on a shelf or a server you pay for, and they protect no one by being there.
The same fog causes the opposite accident. With no reliable way to tell a safe-to-destroy file from one you're still required to hold, someone eventually guesses wrong and shreds the file you needed in front of a board or a judge. Both problems, the hoarding and the early toss, come from the same missing thing: a date on each file that says when it goes.
Give every file its own clock at closing
The fix starts the moment a matter closes, not years later in the closet. You already mark a file done when you close it. Add one more step: stamp it with its destruction date, the single day it becomes safe to shred or delete.
That date isn't one number for the whole practice. Different records run on different clocks, and the clock usually starts at closing, not at opening.
- Tax and accounting records. A closed return or set of workpapers runs on its own window. A common habit is to hold them several years past filing, but your CPA society and the relevant IRS guidance set the real number, so confirm it and write it down once.
- Dental and medical charts. Charts run longer, and a minor's chart resets: the clock often runs from when they reach adulthood, not from the last visit. Your Board of Registration has the rule.
- Closed legal matters. The clock typically starts when the matter ends, and some items (original wills, deeds, anything the client may need back) never go on the shred pile at all. Your bar's guidance governs here.
- Insurance policy files. A lapsed or replaced policy still has a tail, because claims can arrive after the policy ends. Hold them for that tail, whatever your carrier and state rules require.
You set those windows once, per category. The system's only job is the arithmetic: closing date plus retention window equals destruction date, attached to the file the day it closes.
Let the calendar nudge you, not bury you
A destruction date does nothing sitting in a field. The point is to be told when it arrives, in a batch small enough to act on and quiet enough to skip on a busy week without losing the thread.
Picture a short digest, once a month. It lists the files that came due since the last one, grouped by type, with the client or matter name, the closing date, and the rule that put each one on the list. Nothing gets destroyed on its own. The digest just hands you a decision.
A useful nudge gives you enough to decide in one sitting:
- Which files are due, and the retention rule each one is riding on.
- Any reason to pause: an open dispute, a litigation hold, an active audit, a client who asked for their file back.
- A one-click way to approve the batch or push a single file out another year.
Monthly tends to beat weekly here, because retention moves slowly and a weekly ping becomes noise you train yourself to delete. Pick a rhythm you'll actually read.
Log the destruction, because "we shred regularly" isn't proof
Destroying a file on schedule only protects you if you can show you did it on schedule. "We shred regularly" is a shrug, not a record. The log is the part that turns a good habit into something you can stand behind when someone asks.
Keep it boring and complete. For each batch you destroy, record:
- What was destroyed, by category and count (note the matter or chart IDs if your rules want that detail).
- The date it was destroyed and who approved it.
- The method: shredded, wiped, deleted from the active system and the backups.
- The retention rule that made it due, so the reason is on the page, not in your memory.
If a shredding vendor handles the paper, their certificate of destruction goes in the same log. Now the destruction has a paper trail of its own, which is exactly what an auditor, a board, or opposing counsel will ask to see.
What the software decides, and what you still do
Be clear about the line, because it matters. The calendar can track dates, group what's due, flag the holds, and keep the log. It cannot tell you how long your profession requires you to keep a given record, and it shouldn't pretend to.
Those obligations come from your bar, your licensing board, your carrier, the tax code, and sometimes the specific client agreement. You (or your counsel) set each window once, the system applies it, and you approve every batch before anything is destroyed. The tool handles the clock and the paperwork. The judgment stays yours.
Worth doing this week
You don't need to clear the closet by Friday. You need to stop the pile from growing blind and put a clock on what's already there. Start small.
- Write down your retention window for each category you handle, and confirm the number with your board, bar, or CPA society rather than memory.
- Add a destruction date to your file-closing checklist, so every new matter leaves with its own clock from day one.
- Pick one old shelf or folder and tag what's on it with real due dates. One shelf is a fine start.
- Set up a monthly digest of what's come due, and a simple log for what you destroy.
- Run one batch end to end, approval and log included, so the process is real before the volume shows up.
Set it up once and the closet stops being a liability you inherited and starts being a schedule you run. If you'd rather not wire up the reminders and the log yourself, that's the kind of quiet back-office automation we set up at AI Agency Mass, and it tends to earn its keep the first time someone asks you to prove a file is gone.