E-signatures · Glossary
What happens when someone declines to sign?
The request stops. The envelope moves to declined, the sender is emailed with any reason the recipient gave, nobody else is invited, and no further signing happens. Everything recorded before that point stays in the audit trail, including signatures from anyone who had already signed.
Declining is the honest ending, and it is far more useful than silence. It gives the sender a reason and a timestamp instead of a document that quietly rots.
Nuwan Madhusanka · Co-founder
5 min read · Published
| Declined | Ignored | Voided | |
|---|---|---|---|
| Who acts | The recipient, deliberately | Nobody | The sender |
| Reason captured | Optional, and emailed to the sender | None | Optional, kept in the record |
| Envelope status | Declined immediately | Sent or partially signed until it expires | Voided |
| Sender learns | At once, by email | Only by checking, or after expiry | They caused it |
| Later signers invited | No | Only if it is their turn already | No |
Why a decline is better than silence
An ignored request looks identical to one nobody received. The sender cannot tell whether the invitation went to spam, whether the person is on leave, or whether the answer is simply no, and they will spend a fortnight finding out. A decline converts that ambiguity into a fact with a time on it, and usually with a sentence explaining what is wrong. From a purely commercial view it is the cheapest information in the whole process, which is why the option should be visible rather than buried.
What the reason is for
The reason field takes up to five hundred characters and travels to the sender in the notification. Most of the time it says something practical: the price is wrong, the dates need changing, this should go to my manager, or I have already signed a different version. That is a work item rather than a rejection. Encouraging recipients to write one, and reading it before resending anything, prevents the common loop where a corrected document is sent that fixes the wrong problem.
What stops, and what does not
Signing stops for everybody. Nobody further in the order is invited, no more stamping happens, and the document never becomes a completed agreement. What does not stop is the record: signatures already applied remain in the trail with their times and addresses, the intermediate stamped files remain stored, and the envelope keeps its history. That matters when one party signed and another refused, because the first signature is evidence of what that party was willing to agree to.
Recovering the transaction
A declined envelope cannot be reopened. If the objection can be fixed, correct the document and send a new request, which gives everybody a clean version and a fresh set of checks. If the deal is dead, the declined envelope is the record of how it ended and needs nothing further, though some businesses void it as well to close the matter tidily. What should not happen is resending the identical document in the hope of a different answer, which annoys the recipient and produces two records of the same refusal.
Declining is not a legal position
Refusing to sign is not the same as rejecting the underlying agreement, and it is not a repudiation of anything. A person may decline because they lack authority, because the document names the wrong entity, or because they want a change. Treating a decline as a final commercial answer is a mistake senders make when the notification arrives without a reason, which is another argument for making the reason easy to write. Where the answer really is no, the record simply shows it clearly.
What the sender receives and sees
An email titled with the document, carrying the reason if one was given, and a status page showing the envelope as declined with the event in the trail. The certificate of completion is not produced, because nothing completed. Where the sender wants the matter formally closed as well, voiding a declined envelope is permitted, since void is refused only on completed and already voided envelopes. The steps a recipient takes to decline are covered on the make page for declining rather than repeated here. Two habits make the feature work. Say in the invitation message that a decline with a short reason is welcome if something is wrong, because recipients who are not told this will simply do nothing, which is worse for everybody. And triage the notification properly when it arrives: read the reason, decide whether it is a correction, a negotiation or a refusal, and reply to the person before touching the document. Sending a corrected version without acknowledging the objection is the fastest way to receive a second decline from somebody who now feels ignored. A single sentence agreeing with the point, followed by the corrected document, turns a refusal into a signature more often than any rewording of the invitation.
Questions people ask
Can a recipient decline without giving a reason?
Yes. The reason is optional, and plenty of declines arrive blank. The sender then knows the answer without knowing why, which is still better than silence but usually prompts a phone call. Prompting for a short reason in the invitation message helps more than making the field mandatory would.
Can a decline be undone?
No. The envelope is finished, and the way forward is a new request with whatever was wrong put right. That is deliberate, because a document that could flip between declined and signed would be a poor record of what actually happened and when.
What if the wrong person declined?
The envelope still ends, because the system cannot know that the recipient was wrong rather than the answer. Correct the recipient list and send a new request. If the wrong person was invited by mistake, that is worth noting somewhere, since they saw a document intended for somebody else.
Do other recipients learn about the decline?
They are not notified by the system, and anyone who had not yet been invited never sees the document at all. Where several parties were waiting, telling them directly avoids the situation where somebody chases a document that has already ended.
Does a decline affect signatures already given?
They remain in the record with their timestamps, but they achieve nothing contractually, since the document never completed. Anyone who signed early should be told, because from their point of view the transaction simply went quiet after they did their part.
Is declining recorded on the certificate?
No certificate of completion is produced for a declined envelope, since completion never happened. The decline lives in the envelope's event history and in the notification the sender received, which together are the record of how the request ended. Where a formal artefact is wanted for a file, that notification is the closest thing to one, since it carries both the reason and the time.
Make one with e-signatures
The button opens the generator with this use case already described. Change the wording to match your own.
Send a document for signingRelated questions
- Void vs expire on an e-signature requestVoiding is the sender withdrawing a request. Expiry is the clock running out. What each one emails, what recipients see, and what the record keeps.
- Sequential against parallel signingSequential signing invites one person at a time; parallel invites everyone at once. How each affects speed, control and what each signer can see.
- Signer vs recipient in an e-signature requestRecipient is anyone on the envelope; a signer is a recipient who places a mark. The roles signing tools offer, and which ones actually exist here.
Written and checked by the OneCraft team. Last checked .