← Back to blog
E-signature·5 min read

How to Chase an Unsigned Contract Without Annoying the Client

Most unsigned contracts were not rejected. They arrived on a bad day. Here is a follow-up cadence that recovers them, and the reason it should stop after three attempts.

You sent the contract on Monday. It is now the following Tuesday and nothing has happened, and you are composing a message in your head that starts "Just circling back…" and hating every word of it.

The discomfort comes from an assumption worth examining: that silence means rejection, and that chasing is therefore a form of begging.

Silence Is Usually Not Rejection

When a contract goes unsigned, the reasons cluster into four groups, and only one of them is "no":

  • It arrived on a bad day. Email came in during a meeting, got scrolled past, and is now forty messages down. Easily the largest group.
  • It needs someone else. Your contact has to get a partner, a finance director or a board to look at it, and that person is away.
  • Something in it gave them pause. A clause, a number, a date. They mean to raise it and have not got to it.
  • They have decided against. Genuinely a no, and they are avoiding saying so.

The first two are administrative and a reminder fixes them outright. The third is a conversation you want to have. Only the fourth is rejection, and it is the smallest group.

Which reframes the follow-up entirely. You are not begging. You are resolving an ambiguity that is costing you both time.

Three, Four, Seven — Then Stop

After a fair amount of watching this, the cadence we settled on is a reminder on day three, day four and day seven after sending, and then nothing.

Day three catches the bad-day group, which is most of them. Sooner feels pushy given a document takes a few days to reach the top of anyone's list. Much later and it has slid too far down to surface.

Day four looks redundant and is not. It catches the person who saw the day-three reminder, thought "I must do that", and did not. A second nudge close behind converts a surprising number.

Day seven is the last automated attempt, and it crosses a weekend — which matters, because a document that needed a quiet hour often gets one on a Monday.

Then it stops. This is the part that matters most, and the part most tools get wrong.

Why Stopping Is the Important Bit

A fourth automated reminder, and a fifth, change what the messages mean. Three reminders read as a system doing its job. Six read as pestering, and the person on the other end stops seeing a contract and starts seeing a nuisance.

There is a second, worse effect. Endless automation lets you avoid the conversation. If a contract is unsigned after a week, the problem is not that they did not see the email — it is something else, and no number of reminders will surface it. What surfaces it is picking up the phone.

So the automation stops on purpose, and hands the problem back to you at the point where a human is the only thing that will work.

Make the Reminder Useful

If you are writing the follow-up yourself, one principle: give them something other than a prompt to feel guilty.

"Just checking in on the contract" puts the entire burden on them. Better versions give them an easy exit or a reason:

  • "The contract expires on the 30th — happy to reissue it if you need more time."
  • "If anything in clause 4 needs adjusting, tell me and I will send a revised version."
  • "Is there someone else who needs to see this before it can be signed?"

That last one is the most useful question in the whole exchange, because it is the one that surfaces a decision-maker you did not know existed — which is a very common reason for silence and one you cannot fix any other way.

Expiry Does the Awkward Part for You

An expiry date on the document is worth more than any wording.

It gives the reminder a reason to exist that is not you wanting something. It creates a deadline without you having to impose one. And when it passes, the document closes itself, which means you are not maintaining a mental list of things that might still be alive.

It also keeps your pipeline honest. A quote with no expiry stays "out" forever, and a pipeline full of those quietly overstates how much work is coming.

What Not to Do

Do not re-send the document as a new one. You end up with two live copies and no idea which was signed. Send a reminder against the original.

Do not change the terms while chasing. Dropping the price in a follow-up teaches the client that waiting is profitable, and you will be waited out on every future contract.

Do not chase the wrong person. If your contact has gone quiet for three weeks, they may have left. One call to the switchboard beats a month of reminders into a dead mailbox.

The Underlying Point

Chasing is unpleasant because it feels like asking for a favour. It is not. The client asked for the work, you priced it, they agreed. The contract is the administrative step between agreement and starting — and reminding someone to complete an administrative step is not an imposition, it is the job.

Automating the first week of it means you never have to feel the discomfort at all, and by the time you do have to make the call, you know it is a real conversation rather than a forgotten email. How ours works is described in contract renewal reminders.

Write better proposals, faster

DraftYourBid learns from your winning proposals and generates tailored bids in minutes — in your voice, not a template.

Create your free account →
How to Chase an Unsigned Contract Without Annoying the Client | DraftYourBid