What to do when a signer declines a document

A declined signing request feels like bad news, and sometimes it is. More often it is useful news that arrived in the right way. A signer who declines with a reason has told you exactly what is stopping them, in writing, before anyone started work on the wrong terms. The worst outcome for a document is not a decline; it is silence for thirty days. This guide covers what to do in the hour after one arrives. It is general information, not legal advice.

What a decline records

When a signer presses Decline, three things happen. The request moves to declined. The sender receives an email titled Declined, followed by the request title, carrying the reason the signer typed, which can be up to 500 characters and is optional. And the document stops: nothing further is stamped onto the PDF, and the request will never complete or be certified.

The request’s history keeps a declined event with its time and the signer it belongs to, alongside everything that happened before. On the status page, that signer’s badge reads Declined.

What stops, what does not, and why a decline is better than silence are covered in what happens when a recipient declines. The rest of this guide is about the response.

Read the reason before doing anything

The reason tells you which of three problems you have.

The document is wrong. A rate, a date, a name or a scope line does not match what was agreed. This is the easiest case to fix.

The terms are not agreed. The signer wants a clause changed. That is a negotiation, and the signing request was sent too early.

The wrong person was asked. The signer does not have authority, or someone else in their organisation must sign.

The embedded contractor agreement signing example shows a recorded, not imagined, version of the first case. On a reissued copy of a carpentry package agreement, the subcontractor, Jarrah Marsh, pressed Decline and typed that the rates in the stage payment table were not what had been agreed on site. The request moved to declined, nothing was stamped, and the builder received a Declined email carrying that reason word for word. The fix was not persuasion. It was checking the site notes and correcting a table.

The third case needs a different kind of fix. When a finance officer declines a supply agreement with “I cannot sign contracts over this value”, the document may be perfect; the recipient is wrong. Ask who holds that authority, and whether their organisation needs two people to sign, then send a new request to the right signers in the right order. Do not simply add the new person to a copy of the old request and hope, because the declined record should show exactly who was asked first and why it did not work.

If there is no reason at all, call. A decline without a reason could be a mistake on a small phone screen or the end of a deal, and resending blind treats both the same way.

Fix the document and send a new request

A declined request cannot be edited, reopened or resent. Resending is refused once a signer has declined, because resending exists to replace a lost or locked link, not to overturn a decision. So the path is always a new request.

1. Correct the PDF, or confirm with the signer that nothing needs correcting.
2. Check every other signer’s details while you are there.
3. Send a new request with a covering message that says what changed.
4. Withdraw the declined request if anyone else still holds a link to it.

In the covering message, be specific: “The stage payment table now shows the rates agreed on site on 3 September.” A signer who declined because of a figure will look for that figure first.

Where the change is about the terms rather than a mistake, talk before sending. The Queensland Building and Construction Commission’s guidance is a useful reminder of how little ceremony acceptance can need: once a quote is accepted, in writing or even verbally, it becomes a binding contract. Agree the change, then send the document that records it. Payment schedules are the usual flashpoint; the milestone payment clause page explains how they are commonly written so the table matches the conversation.

Withdraw the declined request

Withdrawing, also called voiding, is not only for requests still in progress. A declined request can be withdrawn too. That matters when other people were invited in parallel, because withdrawing expires every outstanding link and emails everyone who was invited and had not yet signed or declined, so nobody is left looking at a document that is already dead.

The timesheet approval signing example shows the full sequence. A supervisor declined a timesheet because Thursday showed 8.0 hours against a roster saying 6.5. The sender then voided the declined request with a note that a corrected sheet had been sent, and issued the fixed PDF as a new request. The first record ends honestly at declined and withdrawn; the second completes.

The same pattern works when the change comes from your side rather than the signer’s. The statement of work signing example withdrew version one with the reason “schedule revised, version two to follow” and sent a corrected version that the client approved before the vendor signed.

Keep the record

Keep the declined request. It is evidence of the first attempt, the reason it failed and when, and it sits on the request list with its own history. Australia’s Electronic Transactions Act 1999, for Commonwealth laws, accepts electronic retention of a record where the method reliably keeps it complete and unaltered and it stays accessible, and the ESIGN Act in the United States asks that a retained electronic record accurately reflect the information and remain accessible for the required period.

For comparison, other signing tools handle the same moment in a similar way. Google’s eSignature help, for example, tells a sender who needs to change a request after sending to cancel it, edit the source document and send a new request. The principle is the same everywhere: the signed version and the version someone refused should never be the same editable file.

The table below lists common decline reasons, what each usually means and what to do next.

Common mistakes

Resending without reading the reason. It usually earns a second decline.

Arguing in the covering message. Settle the disagreement by phone or email first.

Leaving the declined request live. Withdraw it so parallel signers are told.

Deleting the history. Only drafts can be deleted, and the record is worth keeping anyway.

Treating every decline as a lost deal. Many are a wrong number. The day to day workflow for a one signer contract, including when a client stalls, is in e-signature for freelancers.

Build it

The decline to sign page shows the decline from the signer’s side and the email the sender receives. A decline takes an optional reason of up to 500 characters, moves the request to declined, emails the sender with the reason and stops any further stamping. A declined request cannot be resent to that signer but can be withdrawn, which expires outstanding links and emails everyone still holding one. The tutorial on sending a PDF for e-signature covers sending the corrected document as a new request.