What chasing client paperwork is actually costing your practice

Nearly every practice has jobs that can't move until a client sends something back — a signed form, a piece of ID, a set of figures, a consent form. Chasing that isn't difficult work. It's just constant, and because nobody logs "sent a reminder email" as a task, the hours it eats rarely show up anywhere you'd notice them.

The job that waits on someone else

Most client work has a point where the ball is in the client's court. You've asked for what you need — sign here, send this, confirm that — and now the file sits open until it comes back. Some clients send it straight away. Most don't, not because they're difficult, just because your request landed in a week that was already busy for them too, and it slipped down their list the way anything without a deadline does.

So the file stays open. Someone on your side has to notice it's still open, work out what's still missing, and send another message asking for it — worded a little differently each time so it doesn't read as a form letter, but saying the same thing it said last time. That's not one task. It's a small task, repeated across every open file, on a schedule nobody actually set — closer to "whenever someone remembers to check" than any deliberate cadence.

Why it costs more than it looks like

None of this is hard, which is exactly why it's easy to underestimate. Checking a file, working out what's outstanding, and drafting a chase takes a few minutes each time — but it happens across every open matter, every week, and it's the kind of work that gets done in the gaps between everything else rather than as its own block of time. The bigger cost isn't the minutes spent chasing. It's the minutes lost picking the file back up each time: remembering what was asked for, what's arrived, and what's still missing, because the last time anyone looked was a week or two ago.

The knock-on effect is slower delivery. A job that could close in days instead drifts for weeks, not because the work itself is slow, but because it's waiting on a document that nobody chased consistently. Clients notice that lag even when it isn't your fault.

What automating it looks like

The practical version tracks what's been asked for against what's actually arrived, for every open file, and sends the reminder the moment something is overdue — without anyone having to remember which files are still waiting. A short, specific message: what's needed, why, and the easiest way to send it. If nothing comes back after a couple of reminders, the file gets flagged for a person to follow up directly, with the full history attached — what was asked for, when, and what's been sent so far.

You're not handing the judgement call to a machine. You're making sure the reminder that should always go out actually goes out, so the only files left needing your attention are the ones that genuinely need a person.

What it doesn't do

This doesn't replace a phone call to a client who's avoiding a document for a real reason, and it won't decide when to make an exception or extend a deadline. Some documents are sensitive enough that a personal ask, not an automated one, is the right first move — a system built around this should know which files those are and leave them alone.

What it clears is the much larger group: clients who were always going to send what you asked for and just needed a nudge that didn't depend on someone remembering to send it. That's most files, most of the time.

Is this worth building

If your team already knows which clients are slow to send things back — and chasing them depends on someone noticing rather than a process that runs itself — this is very likely worth a conversation. If paperwork mostly comes back on the first ask, the upside is smaller.

dooco hasn't built this one yet. If it's a real cost in your practice, get in touch at hello@dooco.com and we'll work out whether it's worth building for how your practice actually works — or have a look at what dooco has already built.