# Client chasing is a process problem

Repeated chasing rarely comes down to unreliable clients. It usually comes down to unclear requests and no shared view of what has arrived.

![DutySharp article cover reading client chasing is a process problem](https://dutysharp.co.uk/resources/files/202608/chasing-is-a-process-problem/682f29d4b46d31c8/image/0002_chasing_is_a_process_problem.png)

- Published: 2026-08-29
- Canonical: https://dutysharp.co.uk/resources/chasing-is-a-process-problem

Client chasing is rarely a people problem. It is usually a process problem.

Chasing becomes repetitive when:

- the original request is unclear;
- nobody can see what has already arrived; or
- the next action depends on someone remembering to ask again.

## Reminders are not the fix

Sending another reminder treats the symptom, not the cause. The client was
never confused about being asked; they were unsure what was actually needed,
or their reply landed in an inbox nobody was watching. Chasing again just
repeats the same unclear request through the same blind channel.

## Make the next action obvious

The aim is not to send more reminders. It is to make the next required
action obvious, to the client and to whoever in the practice is tracking the
job.

DutySharp gives accountancy practices a clear, secure view of what is still
needed for each deadline, so outstanding items are visible without anyone
having to ask twice.

## Where does it break down for you?

Where does client chasing usually break down in your practice?

DutySharp is an invite-only hosted service for small UK accountancy
practices. You can request access at
https://dutysharp.co.uk/#request-access.