Reminders that chase for you — without nagging your clients

Every firm has a chasing ritual. On Thursday afternoon a manager opens the tracker, runs down the list, and sends the same weary email to a dozen clients: “Just following up on the documents we requested.” Half of those clients have already sent the documents. They open the email, feel mildly accused, and either reply to correct the record or ignore it entirely. The next week, the manager does it again.

The ritual works, in the sense that documents eventually arrive. It also trains your clients to treat your reminders as background noise, and it spends your best people’s time on the least skilled work in the building. Both problems have the same root: the reminder does not know anything. It is a person guessing, from a stale list, at what might still be missing.

A reminder is only as good as what it reads

A reminder that says “please send your documents” carries no information. A reminder that says “these three items are still outstanding, here is the link” gets acted on, because it tells the client something true and specific.

The difference is the source. In Clivanta, reminders read from the live, stored status of each Request Item. Outstanding is not a hunch and it is not derived from whether a file happens to sit in a folder. It is a fact: an item that is currently requested or in needs revision. Anything the client has already submitted, and anything you have accepted, drops out of the chase automatically.

That single property fixes the trust problem. Because the reminder only ever names things that are genuinely missing, the client learns that when Clivanta emails, it is right. They stop tuning it out. You never again chase someone for a bank statement they uploaded on Monday, because the item that was satisfied is no longer on the list the reminder reads from.

A cadence, not a mood

The manual chase tends to arrive in bursts, driven by whoever remembers and however stressed they are that week. Clivanta replaces that with a deterministic rhythm that does not depend on anyone’s mood.

After an item is requested, the reminders follow a fixed cadence: a first nudge at Day +2, another at Day +5, a firmer one at Day +12, then weekly after that until the item is resolved. Steady expectations beat urgent bursts. A client who knows a reminder comes on a predictable beat plans around it; a client hit with three panicked emails in a day learns to wait for the panic.

Reminders are also batched into sending windows rather than fired the instant a clock ticks over, so a client with several outstanding items gets one considered message rather than a scattered handful. And when an item keeps drifting, the cadence escalates and CCs the Client Owner — the single primary contact for that client — so the right person sees that something is stuck without your team having to manually hunt down who to copy.

There is plumbing underneath this that matters more than it sounds. Bounces are handled, so a reminder sailing into a dead mailbox surfaces as a problem to fix rather than a silence you misread as a slow client. The point of all of it is the same: the routine chasing runs itself, on a schedule you can predict and defend.

Let a client pause without losing the thread

Sometimes a client genuinely cannot get to an item this week. The auditor is waiting on their own bank; the person who has the lease agreement is on leave. If your only options are to keep nagging or to lose track, you will do one of them badly.

Clivanta gives the client a third option: pause the reminders, with a logged acknowledgment. The cadence quiets. The item does not close and it does not disappear from your worklist — it stays open, marked as acknowledged, and the reminders resume on their own after the pause. The client feels heard instead of hounded, and you keep both the relationship and the record. The pause itself is written to the item’s activity log, so if anyone ever asks why a request sat quiet for two weeks, the answer is already in the file.

This is the difference between a system that chases and a system that nags. Nagging ignores what the person on the other end just told you. Chasing, done well, listens and adjusts.

What your team actually does instead

Add these behaviours up and the Thursday ritual mostly disappears. The routine items chase themselves, on cadence, reading true status, escalating only when they need to and quieting when a client asks. Your managers stop being the reminder engine and start handling the genuine exceptions: the client who is truly unresponsive, the item that needs a judgement call, the escalation that a person should make personally.

This is the same idea we set out in getting client documents on time, viewed from the reminder’s side. Getting documents in on schedule is not about chasing harder. It is about building the chase into the process so it reads live status, moves on a predictable cadence, and knows when to step back. When the reminder is derived from the work rather than bolted onto it, the whole thing gets quieter and more effective at once.

There is a defensible-record benefit too, almost as a side effect. Every nudge, every escalation, every pause is timestamped in the item’s immutable activity log. If a client later claims they were never asked for something, you are not searching your sent folder. The trail of who was reminded, when, and how they responded is already sitting in the file.

None of this asks your clients to work harder or learn a new tool. It asks the tool to be honest about what is actually outstanding, and then to be patient and predictable about it. Clivanta handles the chasing so your team can spend its attention on the exceptions that deserve a human.

Chasing clients will never be zero. It should not be a person’s job.