Declined Signature Workflow: What to Do When a Signer Says No

A declined signature means a signer opened your request and chose not to sign, so the workflow cannot reach completion as designed. Your next move is to confirm the decline in the audit trail, find out why, fix the document or the terms, and send a new or corrected request. This guide walks you through each step, shows how to design your workflow so declines are handled predictably, and explains how to keep the records.

TL;DR

• A decline is an explicit action by a signer. It is different from a request that is simply unopened, expired or stuck in an inbox.
• The sender is notified, and the audit log records the event, so you can verify who declined and when.
• Do not edit a document after anyone has signed it. Correct the terms, then start a fresh request so every signer signs the same final version.
• Keep the declined request, its audit trail and any consent records. Retention rules differ by state and industry.
• Decide in advance who owns a decline, who gets notified, and how long you wait before following up.

Table of Contents

• What a declined signature means
• What happens to the document and the other signers
• Step by step: what to do when a signer declines
• Design your workflow so declines are rare and handled well
• Who sees a decline: routing by team
• Keeping records of declined requests
• Seeing the decline status at a glance
• Our perspective
• Run your signing workflow in one place
• A short checklist before you press send
• FAQ
• Sources

What a declined signature means

In an electronic-signature workflow, a signer can usually do one of three things with a request: sign it, ignore it, or decline it. Declining is the active refusal. The signer opens the document, selects the decline option, and often adds a short reason.

This matters because each outcome calls for a different response:

Treat a decline as information. It usually points to a wrong name, a wrong amount, a missing clause, a signer who is not the right authority, or a business disagreement that needs a human conversation.

What happens to the document and the other signers

What happens next depends on how your platform and your routing are set up, which is why you should decide it before you send anything.

In a sequential workflow, where signer two only receives the document after signer one signs, a decline by signer one means signer two never gets it. In a parallel workflow, other signers may already have signed. Their signatures are tied to the version they saw, so that version should not be silently changed afterward.

The same logic applies to approvals. If an internal approver rejects a document before it reaches the customer, the document should stop there and return to its owner, not move forward with a note.

When you build or review a workflow, answer these questions:

1. Does a decline stop the whole request, or only that signer’s step?
2. Who is notified: only the sender, or also the team lead, legal or the account owner?
3. Are completed signatures preserved with the request, so you can show what was signed and by whom?
4. Is the decline reason captured, or does the signer simply close the window?

If you write these answers down once, every future decline follows the same path instead of becoming a scramble.

Step by step: what to do when a signer declines

1. Confirm the decline in the audit trail

Start with the record, not with assumptions. Guidance from a U.S. university IT knowledge base notes that the document originator receives information when a signer declines, and that the audit log records the transaction (SIU Office of Information Technology). The same guidance treats a missing communication or missing audit log as a reason for skepticism, because the document’s path may have been disrupted.

Open the audit trail for the request and check:

• the signer’s name and email address
• the time of the decline, in a clear time zone
• any reason the signer entered
• earlier events such as sent, delivered and opened

If you want to understand what a good trail contains, see our explanations of how an audit trail works and electronic signatures with an audit trail.

2. Find out why

Contact the signer directly, by phone if the relationship allows it. Ask one open question, such as which part of the document needs to change. Most declines fall into a few groups:

• Data errors: misspelled names, wrong dates, wrong amounts, wrong entity.
• Content disagreement: a clause, price, term or scope the signer does not accept.
• Authority: the person is not the right one to sign, and should have been a different role.
• Trust or process: the signer was unsure the request was genuine, or did not expect it.
• Timing: the signer is not ready yet and used decline because it was the only visible option.

Write the reason in your CRM or ticket next to the request. Over a few months, the pattern tells you which template or step needs work.

3. Decide: fix, renegotiate or close

There are three legitimate outcomes.

• Fix: the problem is an error. Correct it and resend.
• Renegotiate: the signer disagrees with a term. Resolve it in conversation, update the document, and resend.
• Close: the deal or onboarding is not proceeding. Mark the request closed with the reason and keep the record.

Do not pressure the signer to reverse the decline. A clean new request with the agreed terms is faster and easier to defend later than a workaround.

4. Send a new request instead of reopening the old one

A declined request has a recorded outcome tied to a specific version of a document. The cleanest practice is to treat it as finished and send a new request with the corrected document. That gives you two separate, accurate trails: one showing the first version was declined, and one showing the second was signed.

This also protects other signers. Anyone who already signed the first version should be asked to sign the corrected one, so everyone is bound by the same final text. If you use reusable templates, the correction takes minutes: update the template or the field values, and send again.

5. Note the outcome and close the loop

When the new request is signed, link it to the earlier one in your records. Anyone reviewing the file later will see why two requests exist and which one is final.

Design your workflow so declines are rare and handled well

Most declines are preventable. These practices help.

Verify who you are sending to. A request that reaches the wrong person is likely to be declined or ignored. Confirm names and addresses before sending, and for higher-risk documents add identity checks. Our guides on document signing with identity verification and how to verify signer identity online explain the options.

Use templates for repeat documents. A template with locked fields and pre-filled data removes typing errors, which are among the easiest declines to prevent. Fillable forms help when the signer must provide information themselves.

Add a human step before the signer sees it. An internal approval before sending catches wrong prices and wrong clauses before a customer or new hire does.

Tell the signer what is coming. A short note saying what the document is, who sent it and how long it takes reduces trust-based declines. People decline requests they do not recognize.

Provide a way to ask questions. If the only visible option for a confused signer is decline, that is what they will choose. Include a contact line in the message.

Set deadlines that fit the signer. An unrealistic deadline pushes people to refuse rather than delay.

Who sees a decline: routing by team

Different teams need different handling.

Assign an owner by role, not by person, so a decline during vacation does not sit unseen. If a workflow notifies only the original sender, add a shared mailbox or team lead to the notification list.

Keeping records of declined requests

It is tempting to delete a declined request because the deal did not happen. Keep it. The record shows what was sent, to whom, and what the response was. That can matter in a dispute about whether someone was offered terms, or whether a deadline was met.

Retention requirements come from the type of record and the jurisdiction, so check the rules that apply to you. Examples from U.S. regulations show the common themes:

• Federal motor carrier rules require electronic records and signatures to be retainable and accurately reproducible, and to include proof of consent to electronic methods as required by 15 U.S.C. 7001© (49 CFR § 390.32).
• Michigan’s rule on electronic signatures requires retained records to accurately reflect their final form and remain accessible for later reference (Mich. Admin. Code R. 451.4.4).
• Wyoming’s rules require agencies to preserve records relied on for legal rights, with validity documentation gathered at or near signing or the ability to revalidate signatures (077-5 Wyo. Code R. § 5-4).
• Texas rules for covered systems call for retaining the signer’s name, date and signature, and generally verifying the user’s identity (43 Tex. Admin. Code § 217.303).
• California requires real estate brokers to retain copies of documents with electronic signatures in a way that allows inspection (10 CCR § 2729.5).

These rules apply to specific agencies, industries and states. They are not a universal checklist, but they show what a defensible record looks like. If your sector is regulated, ask your compliance lead or counsel which rule governs you. For more on how documented signing processes are validated, see this overview of preserving signing process records.

A practical retention set for every request, declined or signed:

1. The document version that was sent
2. The full audit trail, including the decline event and reason
3. Proof that the signer consented to electronic records
4. Notes on the follow-up and outcome
5. A link to the replacement request, if one was sent

Our eSignature compliance checklist for teams and the electronic signature disclosure page show how consent and disclosure fit into the process. If a dispute is likely, read about electronic signature holds so the audit trail is preserved in the first hours.

Seeing the decline status at a glance

A sender needs the declined status to be visible, not buried. Whatever tool you use, the status of each request should be easy to find in one dashboard, and the decline should reach the sender quickly. For a closer look at how senders learn that a signer declined and how the status appears in a workflow, this explainer on tracking responses to notices shows the same principle applied to another kind of document.

Our perspective

We see a declined signature as a workflow event, not a failure. The teams that handle it well decided in advance what a decline triggers: who is told, what record is kept, and how the corrected document goes out.

That is why we build BeeSign around workflows rather than around a single signing screen. Contracts, templates, approvals, identity verification and audit trails sit in one place, so the person handling a decline can see the whole story without piecing it together from email threads.

We also think control over your data matters most when something goes wrong. With white-label and bring-your-own-cloud options, the records of requests, including declined ones, can stay inside your own infrastructure and under your own brand. Flat-rate pricing without per-envelope fees also means a corrected resend is never a cost you hesitate over.

Our advice: write your decline path down once, put it in your template process, and review declines monthly. Each one tells you what to fix.

Mustafa Abusharkh

Run your signing workflow in one place

BeeSign brings e-signatures, reusable templates, fillable forms, approvals, identity verification and complete audit trails into one platform, so a declined request is easy to trace and easy to resend. The Individual plan is $9.99 per month, and every plan starts with a 7-day free trial. For teams that need their own branding, custom domain or storage, see our white-label and BYOC options or the pricing page.

You can explore the electronic signature product to see how requests, reminders and audit trails fit together.

A short checklist before you press send

• Names, emails, dates and amounts match the source of truth.
• The right role is signing, with the authority to do so.
• The signer knows the request is coming and who it is from.
• A contact line is included for questions.
• Internal approval is complete.
• The deadline is realistic.
• Your team knows who owns a decline.

If the document is legally significant, it helps to confirm the basics of validity first. Our articles on what makes an eSignature valid and whether legal documents can be signed electronically cover the fundamentals.

FAQ

Can a declined e-signature request be reopened?

Usually the better practice is to send a new request. A declined request has a recorded outcome tied to one version of the document, so a fresh request with the corrected text gives you two clean trails. Check how your platform treats declined requests before you rely on any other approach.

Does the sender know when someone declines?

Yes, in common platforms the originator receives information when a signer declines, and the audit log records the event (SIU OIT guidance). Make sure the notification goes to a role or shared mailbox as well as the individual sender.

Should I delete a declined request?

No. Keep the document version, audit trail and consent records, along with a note on the outcome. Retention periods depend on your industry and state, so confirm them with your compliance lead or counsel.

What if other signers already signed before the decline?

Their signatures belong to the version they saw. Do not alter that document. Correct the terms, send a new request, and ask every signer, including those who already signed, to sign the final version.

Sources

• Adobe Sign in Acrobat Pro Basics, SIU Office of Information Technology
• 49 CFR § 390.32, Electronic documents and signatures
• Mich. Admin. Code R. 451.4.4, Electronic signatures
• 077-5 Wyo. Code R. § 5-4, Retention of Electronic Records
• 43 Tex. Admin. Code § 217.303, Process for Accepting Electronic Signatures
• Cal. Code Regs. Tit. 10, § 2729.5, Record retention

Recommended

• How to Add Signature Fields the Right Way
• Multi Signer Contract Workflow Software That Works
• How to Set Up Approval Workflows with BeeSign
• How to Verify Signer Identity Online