A piece of mail comes back to you with a yellow sticker across the front. Return to sender, not deliverable as addressed, no forwarding order on file. You check the name and it's a client you've worked with for years. They moved last spring, and holding the envelope is the first you're hearing of it.
Most stale records are quieter than that. A reminder text goes to a number that belongs to a stranger now. An email bounces softly into a folder nobody opens. The insurer on file merged into a larger one a while back, and the LLC your client formed has become a different entity with a different name on the paperwork.
None of this surfaces when you open the file, because the file looks finished. Name, address, phone, carrier, all sitting in their boxes. The catch is that a record is a photograph of the day you wrote it down, and clients keep living after the shutter clicks. Practices that keep files for years feel this most, because you bill against a matter long after the intake form stopped being accurate.
Where client details quietly go stale
It helps to know which fields drift, because they aren't random. The ones that move are tied to a client's own life and business, and those change without anyone thinking to tell their accountant or their lawyer.
- Mailing address. People move and file a forwarding order that expires in a year. After that, your statements vanish.
- Cell number. A new phone, a ported line that didn't port, a work number that ended with a job.
- Email. A spam-heavy address they abandoned, or a company domain they left behind.
- Insurer or carrier. Policies change hands at renewal, and carriers merge, so the name you have may not exist anymore.
- Entity name. A sole proprietor incorporates, an LLC converts, a business is sold, and the name on your engagement letter no longer matches the one on the tax return.
Each of these is small on its own. Together they explain why a letter bounces, why a confirmation text goes nowhere, and why your front desk keeps retyping the same correction every time a client walks in and mentions, in passing, that they moved.
A once-a-year "confirm your details" link
The fix most practices reach for is a short link you send once a year. It opens a form that already shows what you have on file, the client reads it in under a minute, fixes anything that's wrong, and confirms the rest. No phone tag, no fresh intake packet, just a glance and a tap.
Keep it light. The goal is a thirty-second task for the client, not a questionnaire that gets abandoned halfway. A few things make the difference between a form people finish and one they ignore:
- Prefill everything. Show the current address, number, and email so the client is correcting, not re-entering. Most of the time they'll confirm and be done.
- Ask only what goes stale. Contact details, insurer, entity name. Skip anything you can look up yourself or that never changes.
- Send it when they're already thinking of you. Tie it to a yearly review, a renewal, or the start of tax season, so the ask feels like part of the relationship rather than a cold form.
- Make it work on a phone. Clients will open this standing in line somewhere. If it's hard to read on a small screen, they close it.
- Write down the date they confirmed. That one timestamp is what powers the next piece.
Stagger the sends if a single blast feels like a lot. A fifth of your list each quarter spreads out the replies, and any undeliverable emails that bounce right back become their own small to-do list.
Flag any record nobody has touched in a year
The link catches clients who answer. The flag catches the ones who don't. Store a "last confirmed" date on every record, and have your system quietly raise a hand whenever that date passes twelve months.
A flagged record isn't an emergency. It's a prompt: before you mail this statement or send this engagement letter, give the details a second look, or drop a quick note asking the client to confirm. The flag turns a silent gap into a visible one, which is the whole point.
What you do with a flag can scale to how you work:
- At the light end, a monthly list of stale records your front desk skims during a slow stretch.
- In the middle, an alert that fires when someone opens a flagged file, so the check happens at the moment it matters.
- At the thorough end, an automatic nudge to the client for the oldest records, so the list keeps clearing itself without anyone chasing it.
What this catches, and what it won't
Worth saying plainly: none of this knows a client moved. It can send the ask, track who answered, and mark which files have gone quiet, but it can't learn an address the client never shares. Automation moves the reminder, not the truth.
It also can't tell a typo from a real change. If someone fat-fingers a ZIP code, the form takes it as gospel, so a human still owns the final read on anything that looks off. And a flag only helps if someone acts on it; a list nobody opens is just a quieter version of the problem you started with.
What you get in return is modest and real. Fewer letters that come back, fewer texts into the void, and a front desk that stops retyping the same fix against your billable time. We install these for practices around Route 128, and the honest version is a short form, a yearly send, and a flag, nothing more exotic than that.
Worth doing this week
You don't need software to start. You need to know how bad the drift is, and to put one small habit in place.
- Pull ten older client files and check the contact details against reality. The error rate you find will tell you how urgent this is.
- Add a "last confirmed" date to your records, even if it's just a column in a spreadsheet for now.
- Draft the confirm-your-details message once, in plain language, so it's ready to reuse.
- Pick a yearly trigger, a review or a renewal, and attach the send to it so it happens on its own.
- Set a standing reminder to review anything untouched for twelve months, and clear the first batch by hand.