Repeated client chasing in accounting firms is rarely caused by unresponsive clients. In most cases, it comes from unclear requests, fragmented communication, and a lack of structured tracking within the workflow. These issues lead to delays, extra emails, and inconsistent client experience.

This guide explains how to reduce follow ups by introducing structured request design, automated reminders, and clear audit trails. It shows how better organisation of client communication can improve visibility, reduce workload, and make delivery more predictable across the firm.

What you’ll learn:

  • Why client chasing is usually a workflow issue, not a client problem
  • How unstructured emails and scattered requests create delays
  • The common patterns that lead to repeated follow ups
  • How to design clear, structured information requests
  • Why breaking requests into individual items improves response quality
  • How workflow-based reminders reduce manual follow up effort
  • The role of auditability in tracking requests and responses
  • Which metrics help measure improvement in client communication
  • How to implement structured request systems step by step
  • Why connecting client engagement and delivery workflows improves visibility

In many accounting firms, a significant amount of time is spent chasing clients for information. Teams send follow up emails asking for bank statements, payroll reports, confirmations or signatures. A few days later another reminder is sent. Sometimes the client replies with partial information, which leads to another round of questions.

Over time this becomes routine, and staff accept chasing as a normal part of delivery work.

In reality, repeated follow ups are rarely caused by difficult clients. Most often the issue lies in how information requests are designed and managed. When requests are unclear, scattered across communication channels, or disconnected from the workflow, it becomes difficult for both the client and the firm to see what is still outstanding.

The result is delayed jobs, additional communication and inconsistent client experience.

A structured approach to requests, reminders and record keeping can reduce much of this effort while improving visibility across the delivery process. 

Why client chasing is usually a workflow problem

When firms request information from clients, the process often begins with a long email listing everything required. Several problems appear immediately.

Requests may be buried inside paragraphs of text. Some items may be urgent while others are optional. The client may not fully understand why the information is needed or how it should be provided.

As the job progresses, additional emails may introduce new requests or revised lists. Different team members may contact the client separately. Eventually nobody is certain which version of the request list is the latest.

At this point chasing becomes inevitable. Staff spend time searching email threads and trying to confirm what has already been received.

This situation is not primarily about client behaviour. It is the result of a process that does not clearly organise requests or track their progress.

Common patterns that create repeated follow ups

Across many firms, the same patterns lead to repeated chasing.

One common issue is free text emails that contain several requests in a single message. Clients often reply to the first few items while overlooking the rest.

Another pattern is unclear ownership. If nobody is responsible for monitoring the request status, follow ups occur inconsistently.

Due dates may also be missing. Without a clear deadline, clients may not realise when information is required.

Teams may also maintain several versions of request lists. One version may exist in an email, another in a spreadsheet, and another in internal notes. Staff then spend time reconciling which list is correct.

Finally, clients sometimes respond with incomplete attachments or answers in the wrong format. This leads to additional clarification messages before the job can progress.

These patterns increase communication effort for both sides.

Designing structured information requests

Reducing chasing begins with redesigning how requests are presented.

Instead of sending one large message, requests should be divided into individual items. Each item should clearly describe the information required.

It is also useful to identify which items are required and which are optional. This helps clients focus on the information that is necessary for the next stage of work.

Providing a short explanation of why the information is required can also improve response quality. Clients are more likely to provide accurate information when they understand how it will be used.

For requests that frequently cause confusion, examples can be helpful. A request for bank statements might specify the date range and file format required. Payroll reports might include the exact report name expected.

These adjustments make requests easier to understand and reduce the number of follow up questions.

Reminders that remove manual follow up

Even well-structured requests still require reminders. The difference lies in how reminders are managed.

In many firms, reminders depend on individual staff members remembering to follow up. They may keep notes in personal task lists or calendars. If workloads increase, reminders may be delayed.

A more reliable approach is to connect reminders directly to the workflow.

If a request remains incomplete after a defined period, the workflow prompts the responsible team member to take the next action. This might involve sending a reminder or escalating the request.

When reminders follow a predictable pattern, both staff and clients understand what happens next. The process becomes consistent rather than dependent on personal habits.

Embedding reminders within the workflow also supports compliance oversight. The process encourages good practice rather than relying on individual memory.

Auditability and the record of what happened

Another challenge with client chasing is the lack of a clear communication record.

In many firms the history of requests and responses sits inside individual inboxes. If another team member needs to review the situation, they must search through several email threads.

A structured process keeps this history attached to the job and the client context.

The firm should be able to see what information was requested, when it was requested, and when it was received. This record remains visible throughout the lifecycle of the job.

Clear records reduce uncertainty during reviews because managers can understand the full context quickly. They also provide useful evidence if questions arise about what information the client supplied.

Measuring whether the process is improving

Once requests become structured, firms can track a few simple indicators to assess improvement.

One useful metric is the average number of follow ups per job. A well-designed process should gradually reduce this number.

Another indicator is the number of days spent waiting for client information. Lower waiting time usually leads to more predictable delivery schedules.

Firms can also monitor the completion rate by agreed deadlines and the number of jobs reopened due to missing or incorrect information.

Escalations to managers are another useful signal. If fewer jobs become stuck, the process is likely functioning more smoothly.

Tracking these indicators over several weeks often reveals clear progress.

A practical way to introduce the change

For mid sized and larger firms, the most effective approach is gradual implementation.

Client onboarding is often the best place to start. This workflow involves several information requests and usually highlights where confusion occurs.

The firm can develop standard request packs for different client types and service lines. Each pack defines the required information and the expected format.

Ownership rules should also be defined. The team needs to know who monitors the request status, when reminders occur, and when escalation is required.

Reviewing request patterns weekly helps identify common issues. Templates can then be improved based on real client feedback.

Rolling out the approach gradually helps teams adapt without creating change fatigue.

Connecting client engagement and delivery workflows

Reducing client chasing is easier when client engagement and delivery processes operate within the same workflow environment.

When onboarding, document requests and ongoing service delivery run through connected workflows, teams can see what information is outstanding and what action is required next. Document handling, request tracking and delivery progress remain visible within the same operational context, which helps managers and partners understand where jobs are waiting.

Embedding reminders and process steps inside the workflow also supports consistent delivery. Teams follow the same structured process, which gives compliance leaders greater confidence that requests, responses and reviews are handled correctly.

Keeping the full record of requests and responses attached to the job also strengthens the evidence behind delivery. Firms can see what was requested, when information was received, and how the work progressed through review.