The One-Thread Rule: Why Client Chasing Never Ends
Chasing clients isn't a discipline problem — it's a channel problem. Here's how a single, tracked portal thread replaces the scattered email trail that keeps work stalled.
Most firms don't have a chasing problem. They have a channel problem. A document request goes out by email on Monday. The client replies from their phone, attaches the wrong PDF, and CCs their spouse. You reply asking for the missing statement. That thread splinters into three, one gets buried under a newsletter, and by Thursday nobody in your firm is sure what's outstanding. So you send another email. The client feels chased. You feel like a debt collector. Nothing has actually moved.
The fix isn't more reminders or a firmer tone. It's collapsing every client interaction onto one tracked thread that both sides can see — which is exactly what a client portal is for, when it's built into your practice workflow instead of bolted on the side.
Why email guarantees chasing
Email feels convenient because everyone already has it. But as a system for running client accounting work, it has structural flaws that no amount of willpower fixes:
- No shared state. You and the client can't see the same list of what's still needed. Each of you is working from a private, partial view of the conversation.
- No status. An email is either sent or not. It can't tell you "received, three of five documents in, two still outstanding."
- It's private to a person, not the firm. If the request lives in one staff member's inbox, nobody else can pick it up, and the trail vanishes when they're on leave.
- Attachments go stale and get lost. Versioning is guesswork, and sensitive financial data sails around unencrypted inboxes.
Every one of those gaps is filled by a follow-up email. The chasing isn't a symptom of disorganised clients — it's the tax you pay for using a channel that can't hold the state of the work.
What "one thread" actually means
The one-thread rule is simple: for any given client job, there is exactly one place the request lives, both parties can see it, and its status is visible without anyone asking. When a client uploads a bank statement, the request updates itself. When three of five items are in, you can see the two that aren't — and so can the client.
This changes the emotional shape of the interaction. The client isn't being nagged by a person; they're looking at a checklist with two ticks missing. That's a task, not a confrontation. Most people will just finish the task.
Good accounting client management software makes the portal the front door for this. In Finye, a document request or query sits against the actual work item on your board, so the portal thread and the job your team is doing are the same object. There's no re-keying, no "I'll update the file once they reply." The client's action moves the job.
Reducing chasing without becoming a nag
Fewer, better-designed touchpoints beat a stream of manual reminders. A few principles worth building into your process:
Ask for everything once, clearly
Batch the full list of what you need into a single request rather than emailing as each gap occurs to you. A client faced with one complete checklist responds faster than one drip-fed five separate asks over two weeks. When your portal shows the whole list with a clear status on each item, the client can knock it out in one sitting.
Let the system remind, on a schedule you set
Automated portal reminders remove the awkwardness and the memory burden. You decide the cadence — say, a nudge at day three and day seven — and it fires whether or not anyone in the firm remembers to send it. Crucially, the reminder only mentions what's still outstanding, because the portal knows what's already been received. No client should ever be chased for a document they already sent.
Make the reply effortless
Every extra step is a reason to defer. If the client has to find a login, remember a password, or work out where to click, your response rate drops. A portal branded to your firm, with a clean upload experience on mobile, removes the friction that turns "I'll do it later" into "I never did it."
Keep one source of truth
When the query, the documents, and the job status all live in your account practice management software, anyone on the team can pick up where a colleague left off. The client experiences continuity instead of being asked the same question twice by two different people.
What this does to your numbers
Chasing has a real cost, and it isn't only the minutes spent writing follow-ups. It's the elapsed time — jobs that sit half-started for weeks because the last document never arrived. That's WIP ageing on your books, deadlines creeping closer, and capacity locked up in work that can't be finished or billed.
Collapse the back-and-forth onto one tracked thread and three things shift:
- Response times shorten, because the ask is clear and the reply is easy.
- Elapsed job time falls, because work isn't waiting on a lost email.
- Team time returns, because nobody is reconstructing where a conversation got to.
You're not being more diligent about chasing. You've removed most of the need to chase at all.
The portal is a workflow tool, not a mailbox
It's worth being clear about what a portal is and isn't. It's not a substitute for talking to clients when a real conversation is needed. And on its own, a file-sharing box that isn't wired to your work just becomes another inbox to check. The value only appears when the portal is connected to the job.
That connection is the point. In Finye, the client portal, your document requests, and the work items on your boards are one system — so a client action updates the job, the job drives the reminder, and the whole firm sees the same live status. The client sees a tidy checklist. You see work that keeps moving. And the endless follow-up email loop, the quiet drain on every firm doing client accounting, mostly disappears.
Chasing feels like a fact of practice life. It isn't. It's what happens when the conversation and the work live in different places. Put them in one place, and the chase largely takes care of itself.