The email is short and polite. A client who's moving on, or the office taking over the work, asks you to send the file along, and there's a forwarding address at the bottom. It reads like a favor, so it waits behind the things that feel urgent.
Then it moves. Someone forwards it with a quick 'can you grab this?', it lands in the front-desk inbox that four people half-watch, and everyone assumes a colleague has it. A week goes by. The request is still sitting there, read and unanswered, which is somehow worse than unread.
Here's the part that makes it more than a courtesy problem. A lot of these requests carry a response deadline set by your board, your bar, or federal rules, and the clock starts when the request arrives, not when you finally notice it. A departing client's matter file, a new accountant asking for prior-year returns, another practice requesting dental or medical records: different professions, same quiet risk. Miss the window and a routine handoff turns into a complaint.
Why the shared inbox swallows these
A records request doesn't look like an emergency. No one's bleeding, no money's moving, and the sender was friendly about it. So it loses every triage contest to the ringing phone and the filing due Friday.
The deeper issue is ownership. When a request lands in a space several people can see, responsibility spreads thin enough to disappear. It's the same reason a chore assigned to five people often gets done by none. A shared inbox is that effect with a login.
Second-guessing makes it worse. Is this person entitled to the whole file, or only part of it? Do we need the client's written okay before we send records to a third party? Nobody wants to be the one who mailed the wrong thing to the wrong address, so the safe move feels like waiting. Waiting isn't safe. It just feels that way.
Confirm who's asking, and what they're owed
Before anything goes out, two questions need clean answers: who is this, and what are they entitled to. Get those wrong and you've either breached a confidence or stonewalled a legitimate request. Both are the kind of mistake that follows you.
Build a short intake step that runs the same way every time. It can be a simple web form you link from your site and your email signature, or a reply template your staff fills in. Either way, it should capture the same fields so nothing gets skipped under pressure.
- Who's requesting, and their relationship to the record: the client themselves, a new provider, an attorney, an executor.
- What they want, specifically: the full matter file, one year's returns, imaging from a date range. 'Everything' is rarely what they actually need.
- Proof it's really them, scaled to the sensitivity: a signed authorization for third-party medical or tax records, a quick identity check for the client in person.
- Where it goes, confirmed against what you already have on file, because a changed address is exactly when a mistake does the most damage.
This is where a little automation earns its keep. A form can require the signed authorization before it'll submit, so an incomplete request never reaches your desk looking finished. It can't judge whether that authorization is valid, though. A person still reads it. The software just makes sure the person has everything they need to decide.
Log it with a due date the same day
The one habit that fixes most of this is boring: every request gets logged the day it arrives, with a due date attached. Not the day you start working it. The day it lands.
Work out the deadline for each type of request once, write it down, and stop rederiving it under stress. Your profession's rules set the clock, and they vary more than you'd think, so confirm the real number for your field rather than guessing. Some are measured in a handful of business days, some in weeks. Then subtract a buffer and treat that earlier date as the real deadline, because the file still has to be gathered, reviewed, and sent.
A lightweight tracked list does the remembering for you. A new row per request, a status, an owner's name, a due date that changes color as it approaches. The tools can be ordinary: a shared spreadsheet with conditional formatting, or the task board you already pay for. What matters is that a request becomes a tracked item with one name on it, not a message hoping to be noticed.
- One owner per request. Shared responsibility is how these vanish. A name next to the row fixes it.
- A due date, visible. The buffered date, not the legal one. You want to be early, not exactly on time.
- A status anyone can read at a glance: received, authorization pending, gathering, sent.
Acknowledge it the moment it's logged
The instant a request is logged, the requester should get a short automatic note: we received your request on this date, here's roughly when to expect the file, here's who to reach with questions. That one message does a surprising amount of work.
It stops the follow-up emails before they start, because people chase silence, not progress. It sets a date, which quietly commits you to it. And it creates a timestamp on your side showing you responded promptly, which is worth having if anyone ever asks when the clock really started.
Keep it human and specific. A note that says "your request came in on the 3rd and we'll have the file to you by the 12th" reassures. A generic auto-reply that could've come from any inbox anywhere does the opposite, so write it like a person wrote it, because at setup time one did.
What this setup won't do
Automation handles the catching and the reminding. It does not handle the judgment, and pretending otherwise is how practices get burned.
Software can't decide whether a requester is legally entitled to a record, whether an authorization covers what's being asked, or whether something in the file needs to be withheld or redacted. Those calls are yours, and they should stay yours. What the system does is deliver the request to you intact, on the clock, with the deadline already counting down, so your judgment gets applied on time instead of three weeks late.
It also won't rescue a filing system you can't search. If gathering the file means digging through boxes in a back room, the tracker will faithfully show you a deadline you're about to miss. That's useful information, but the fix there is your records, not your inbox.
Worth doing this week
You don't need new software to start. You need one channel and one habit.
- Pick the single destination for every records request, and tell your team that's where they go the moment one arrives, no matter who opens it first.
- Write down the deadline for each kind of request you handle, confirmed against your profession's actual rules, with a buffer built in.
- Make the intake checklist: who, what, proof, and where to send it. A form or a template, as long as it's the same every time.
- Draft the acknowledgment note once, in a real voice, with a blank for the date you'll deliver.
- Start the log today, even as a spreadsheet, and put one name next to every open request.
Do that and the next request gets answered the day it lands, not the day someone finally remembers it. If you'd like a hand wiring the form, the tracker, and the automatic acknowledgment together so it runs without anyone babysitting it, that's the sort of thing we set up for Massachusetts practices.