How do I decline a sign in airSlate SignNow?

Decline to sign. Complete signing. Contact the sender and ask them to Void/Cancel the document. You can simply "reply to" the email notification to contact the sender of the document.

How do I change my signature on airSlate SignNow without an account?

If you don't want a free airSlate SignNow account, you can ask the sender of the documents to correct the document without your middle initial as a part of your name and resend it to you. With your full name formatted differently, the airSlate SignNow system will prompt you to "adopt" a new signature.

Can you change your signature at any time?

As Gil Silberman says, you are free to change it arbitrarily whenever you want. So the practical answer is: you'll want replace your State Driver's License/ID card with your new signature, and then go to every bank where you have an account and update your signature on their records. That's probably it.

Do you have to have an airSlate SignNow account to sign?

Does everyone signing the document need an airSlate SignNow account? No, recipients of your documents do not need an account to sign with airSlate SignNow.

How do I sign a document in airSlate SignNow?

Sign up for a free trial at airSlate SignNow, and then log in. Select New > Sign a Document, and then upload the electronic document. Select Sign and then follow the steps to electronically sign your document. Sign up for a free trial at airSlate SignNow, and then log in.

How is airSlate SignNow legally binding?

According to these acts, A document or signature cannot be denied legal effect or enforceability solely because it is in electronic form." airSlate SignNow digital signatures are valid and legally binding around the globe, and are in use in 188 countries today.

How do you make an electronic signature legally binding?

For an electronic signature to be legally binding under the ESIGN Act, it is recommended that all electronic signature workflows include: Intent to sign. Similar to ink signatures, a signer must show clear intent to sign an agreement electronically.

How is airSlate SignNow secure?

\u201cdocuments signed online with legally compliant eSignature software are as valid and binding as traditional pen-and-airSlate SignNow documents.\u201d Contracts signed using enterprise-level electronic signature processes like airSlate SignNow are completely secure and deliver a rigorous audit trail of who signed and when.

How do I create a signature in airSlate SignNow?

Click the link. Your document should open in an electronic signature tool such as airSlate SignNow. Agree to electronic signing. ... Click each tag and follow the instructions to add your digital signature. Verify your identity and follow the instructions to add your digital signature.

Do you have to have an airSlate SignNow account to sign a document?

No, recipients of your documents do not need an account to sign with airSlate SignNow. Your document will be sent via email from dse@airSlate SignNow.net and recipients can review the document, adopt a signature, and complete the signing process without having an airSlate SignNow account.

How do I request an electronic signature?

Open a PDF file in Acrobat DC. Click the Fill & Sign tool in the right pane. Add a recipient: Enter an email address and add a custom message if you want. ... Create your form and signature fields: ... Send your form:

How can I get digital signature?

Click the Sign tool, then Add Digital Signature. Please note that digital signatures must be enabled by your airSlate SignNow administrator. Select cloud-based digitial ID certificate, then click Apply. Select the name of your digital ID certificate provider, or click the link to get a new digital ID.

What is request signing?

Request signature is the API request parameter api_sig which is added to every request to verify request user's authenticity on behalf of which the request is made. The request used to demonstrate request signing is a POST to https://infogr.am/service/v1/infographics .

What is http signature?

The HTTP Signatures specification is intended to provide a standard way for clients to add origin authentication and message integrity to HTTP-based messages. The HTTP Signature Nonces specification describes a way to use the HTTP Signatures protocol over an unsecured channel like HTTP.

How do you sign a document?

All you have to do is open your document, click "Tools," then click "Fill & Sign." Click the "Sign" button in the toolbar and you'll be prompted to type, draw or use an image of your signature.

Electronic Signature
Features
Other
Decline Sign Request Efficiently

Decline Sign Request with SignNow's Secure eSignature Solution

Remove paperwork and optimize digital document processing for higher efficiency and endless possibilities. Explore the perfect manner of running your business with airSlate SignNow.

See how it works!Click here to sign a sample doc

Award-winning eSignature solution

What decline sign request means and why it matters

A decline sign request is an action available in many electronic signature workflows that lets a recipient refuse to sign a document and optionally provide a reason. Tracking declines is important for recordkeeping, dispute prevention, and process improvement; it ensures senders know which parties did not consent and why. In regulated U.S. contexts, a recorded decline with timestamp and metadata preserves evidence of recipient intent and supports compliance reporting, while enabling teams to route the document for revision or alternative approval paths without losing audit visibility.

Why supporting a decline option is useful

Including an explicit decline action improves transparency, reduces disputes, and preserves a verifiable record of recipient intent while enabling efficient rework or escalation.

Common operational challenges around decline sign requests

Unclear decline workflows can stall approvals and create manual follow-ups across email and phone channels.
Missing decline metadata makes it difficult to determine whether a decline was voluntary or due to technical issues.
Inconsistent policies about required decline reasons lead to incomplete records and audit gaps.
Poorly designed decline flows may discourage feedback and leave senders without actionable information.

Typical user roles and how they use decline actions

Contract Manager

A contract manager reviews declines to determine whether a declined signature requires contract redlining, renegotiation, or escalation. They rely on decline metadata, timestamps, and any recipient notes to route the document back to the drafter or to legal review, ensuring the appropriate audit trail is preserved for future disputes.

HR Administrator

An HR administrator handles declined employee forms or policy acknowledgment requests by recording the decline reason, contacting the employee to resolve the issue if needed, and updating personnel records. They use decline logs to demonstrate compliance with internal policies and regulatory requirements.

Teams that commonly encounter decline sign requests

Legal, HR, procurement, and sales teams often see declines and need clear procedures to handle them efficiently.

Legal teams: capture reason and timeline for dispute resolution and compliance.
HR teams: manage consent-sensitive documents and maintain accurate personnel records.
Sales and procurement: quickly negotiate or revise terms after a documented decline.

Establishing consistent handling rules across teams reduces rework and preserves legally relevant evidence while improving recipient experience.

Core features to look for in decline sign request support

Effective decline handling combines user controls, auditability, and integration to keep document workflows auditable and actionable across teams.

Decline Action

A visible decline button within the signing session that records a refusal event and prevents incomplete signatures while preserving the document state for follow-up and analysis.

Reason Capture

Configurable required or optional reason fields that prompt recipients to explain their refusal and produce structured feedback for legal, HR, or procurement review.

Decline Metadata

Automatic capture of timestamp, IP address, device type, and session identifiers that create an evidentiary record to support later inquiries or regulatory reviews.

Automated Routing

Rules-based routing that sends declined documents to reviewers, legal teams, or back to originators with a log of decline reasons and recommended next steps.

Notifications

Configurable alerts to senders and designated approvers when a decline occurs, including decline reasons and links to the recorded audit trail.

Integrations

Connectors for document storage and CRMs that ensure declined documents and metadata sync to records and trigger downstream processes without manual export.

be ready to get more

Choose a better solution

How the decline sign request flow typically operates

A recipient can decline during the signing session, which triggers recording, optional reason capture, and automated notifications to senders and admins.

Recipient Action: User selects decline in signing interface
Capture Details: System records reason, timestamp, and metadata
Notify Team: Sender and stakeholders receive alerts
Route or Archive: Document follows configured rework or archive path

Collect signatures

24x

faster

Reduce costs by

$30

per document

Save up to

40h

per employee / month

Quick steps to configure a decline sign request workflow

Set up a decline-enabled flow in a few configuration steps to capture reasons and route declines automatically.

01

Enable Decline: Turn on decline action in workflow settings
02

Require Reason: Configure mandatory reason field if needed
03

Set Notifications: Notify sender and relevant stakeholders
04

Define Routing: Route declined documents for revision or escalation

Managing a declined request: next-step checklist

After a decline, follow a concise checklist to resolve the issue and maintain compliance.

01

Review Reason:

Read the recipient explanation and notes

02

Check Metadata:

Verify timestamp and session details

03

Decide Action:

Choose redraft, negotiate, or close

04

Notify Parties:

Inform stakeholders of next steps

05

Update Document:

Apply agreed changes and reissue

06

Record Outcome:

Log the resolution and final status

be ready to get more

Why choose airSlate SignNow

Free 7-day trial. Choose the plan you need and try it risk-free.
Honest pricing for full-featured plans. airSlate SignNow offers subscription plans with no overages or hidden fees at renewal.
Enterprise-grade security. airSlate SignNow helps you comply with global security standards.

Start free trial

Recommended workflow settings for handling declines

Configure the following settings to ensure declines are captured, routed, and audited consistently across your organization.

Workflow Setting Name and Description	Default configuration values for each workflow setting
Require Reason on Decline Actions	Yes, mandatory
Auto-notify Sender on Decline	Immediate email notification
Retain Decline Audit Trail Permanently	Enabled, immutable
Route Declined Documents to Legal	Automatic when disputed
Allow Recipient Attachments on Decline	Optional, enabled

Platform and device requirements for handling declines

Decline functionality should be consistent across web, mobile, and embedded experiences to ensure recipients can refuse to sign regardless of device.

Web Browser Support: Latest Chrome, Edge, Safari
Mobile App Support: iOS and Android apps
Embedded Widget Capabilities: SDK support for decline

Verify that decline actions record identical metadata across platforms and that embedded or mobile experiences present the same required fields and notifications as the web experience.

Security and protection elements tied to decline events

Audit Trail: Full event logging

Encryption at Rest: AES-256 protection

Encryption in Transit: TLS 1.2+ secure transport

Access Controls: Role-based permissions

Immutable Records: Write-once logs

Data Residency Options: US-based hosting

Practical scenarios where decline sign requests matter

Two short case examples illustrate how recorded declines can protect organizations and streamline remediation.

NDAs and procurement offers

A vendor declines an NDA due to unfavorable clauses, providing a short reason for refusal

The decline feature records name, time, and IP address
The procurement team receives a notification and queues redlining

Resulting in a documented negotiation path and reduced procurement delays while preserving an evidentiary trail for legal review.

Employee consent forms

An employee declines a policy acknowledgment citing unclear language, and submits comments for clarification

The HR system captures the decline and attached comments
HR schedules a clarification and updates the form text

Leading to corrected policy language and a clear record of the initial refusal and subsequent acceptance process.

Best practices for secure and accurate decline sign request handling

Follow consistent policies, require contextual information, and integrate decline events with your records management and compliance processes.

Establish a standardized decline policy across teams

Define when declines should be required, who reviews them, and what metadata must be captured. Document the policy, train users, and ensure workflows enforce the required behavior to reduce ambiguity and preserve auditable records.

Require structured reasons and optional attachments

Collect a short, structured reason combined with optional attachments or comments so reviewers have context. Structured responses make reporting and trend analysis feasible without manual review of freeform text.

Preserve decline events in immutable audit logs

Ensure all decline actions, related metadata, and subsequent routing steps are stored in a tamper-evident audit trail retained according to your retention policy for legal and compliance needs.

Integrate declines with downstream systems

Send decline events to CRMs, contract repositories, or ticketing systems to automate follow-up, ensure consistent handling, and avoid manual gaps between signature refusal and remediation.

Connect airSlate SignNow to your apps

Check out airSlate SignNow integrations

Data accuracy, security, and compliance

airSlate SignNow is committed to protecting your sensitive information by complying with global industry-specific

Learn more about security

Frequently asked questions about decline sign requests

Answers to common questions about functionality, recordkeeping, and compliance when recipients decline to sign an electronic document.

What happens when a recipient declines to sign?
When a recipient declines, the system records the event in the document audit trail with timestamp and metadata. The document status updates to indicate a decline, optional reason text is captured, and configured notifications are sent to the sender and designated stakeholders for follow-up.
Can recipients be required to give a reason for declining?
Yes. Administrators can configure the decline workflow to make a reason field mandatory. Requiring a reason improves traceability and helps teams assess whether a technical issue, a terms dispute, or another factor caused the refusal.
Is a decline legally valid under U.S. eSignature law?
A recorded decline showing recipient identity, timestamp, and context documents the recipient's intent and can be admissible evidence. ESIGN and UETA focus on consent and intent; a documented decline supports determinations about agreement formation or refusal.
How is a decline recorded in the audit trail?
The audit trail logs the decline action, the reason text if provided, timestamps, IP and device details, and any subsequent system actions. This immutable record supports compliance reviews and dispute resolution.
Can declines trigger automated workflows?
Yes. Declines can be configured to trigger automated notifications, route documents to reviewers, start a redrafting workflow, or archive the file. Automation reduces manual handling and speeds resolution.
What should teams do after receiving a decline?
Teams should review the recorded reason, validate metadata for authenticity, contact the recipient if needed, decide whether to revise the document, and document the resolution. Following a consistent process preserves records and reduces escalation.

How decline handling compares across leading eSignature providers

Feature availability and behavior for decline actions differ between vendors; the table highlights common capabilities and quick yes/no availability.

Feature, Requirement, or Capability Name	signNow (Recommended)	DocuSign	Adobe Sign
Decline action availability in signature flow
Mandatory reason capture on decline
Audit trail records decline metadata
Native mobile app decline support

be ready to get more

Get legally-binding signatures now!

Start your free trial

Risks of mishandling declines

Contract Dispute: Increased litigation risk

Regulatory Noncompliance: Potential fines or audits

Data Exposure: Incomplete access controls

Reputational Harm: Loss of trust

Operational Delay: Slower approvals

Record Gaps: Missing metadata

Plan and pricing comparisons including decline-related features

Overview of entry-level plans, free tiers, and whether decline-related audit features are included by default across providers.

Plan, Price, and Limits Comparison	signNow (Recommended)	DocuSign	Adobe Sign	Dropbox Sign	PandaDoc
Starting monthly price (approx.)	From $8 per user per month	From $10 per user per month	From $9.99 per user per month	From $12 per user per month	From $19 per user per month
Free tier or trial availability	Free trial and limited free tier	Free trial only	Free trial only	Free tier available	Free trial available
Decline audit trail included by default	Included by default	Included by default	Included by default	Included in paid plans	Included in paid plans
Google Workspace integration present	Yes, native integration	Yes, native integration	Yes, native integration	Yes, native integration	Yes, native integration
Enterprise compliance and BAA option	BAA available for enterprise	BAA available for enterprise	BAA available for enterprise	BAA available for enterprise plans	BAA available for enterprise

Streamline challenging workflows

Create, perform, and control workflows of any complexness, digitally from virtually anywhere. Scalable electronic signature capabilities let you share documents with the right users the right way and set up roles for each recipient. Stream document workflows faster and easier than ever before.

Automate document management

Improve complicated signing tasks with airSlate SignNowï¿½s powerful capabilities to enhance your operation. Control your automated signature workflows to ensure they're operating at top functionality with quick notifications and reminders.

Enhance in team collaboration

Bring teammates together in a safe, shared workspace. Handle paperwork, use form templates and notices to deliver better cross-organization collaboration. Relieve your staff from having to spend time on repeated activities to enable them to center on valuable, business-crucial activities.

Integrate into your current systems

Work your tasks with market-leading integration. Capture Salesforce, Microsoft Teams, and SharePoint in one business stream. Connect your software to a single system for countless opportunities and more performance.

Remain compliant with market-leading data security

Feel safe understanding that your data is protected by the most recent in encryption security. airSlate SignNow is GDPR and eIDAS compliant and offers you exposure into your signing experience with court-admissible audit trails. Configure user access permissions and roles to manage who has access to what.

be ready to get more

Get legally-binding signatures now!

Start free trial