Is an e-signed rider legally binding?

Yes, electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted, provided intent, consent, attribution, and retention requirements are met.

When does the rider take effect?

The rider takes effect on the Effective Date specified in the document; if silent, the signing date may control. State contract rules and any conditional language in the rider can alter this outcome.

Do I need a notary or witness?

Not typically required for DNC riders, but state-specific formalities or corporate execution rules may require a notary or witness; check local requirements and internal delegated authority policies.

How should updates to the DNC list be made?

Use the amendment process in the rider: authorized updater submits written change, counterparty acknowledgment if required, and both parties preserve the audit trail for the change.

What records should be retained?

Retain executed rider, audit logs, and change history in encrypted storage for the retention period stated in policy; federal and HIPAA baselines may apply for related records.

Can the rider conflict with the main contract?

The rider should expressly state it amends and integrates with the main contract; where conflicts exist, the parties should specify priority to avoid ambiguity.

Electronic Signature
Templates
Miscellaneous
Miscellaneous DNC Rider

Miscellaneous DNC Rider

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MISCELLANEOUS DNC RIDER

Parties and Effective Date

Company / Disclosing Party: Counterparty / Receiving Party:

This Miscellaneous DNC Rider (the Rider) is entered into by and between the parties named above and is effective as of (Effective Date).

WHEREAS

WHEREAS, the Disclosing Party and Receiving Party are parties to one or more agreements, whether executed before or after the Effective Date, which govern certain commercial relationships between them (the Underlying Agreement); and

WHEREAS, the parties desire to supplement the Underlying Agreement by establishing Do-Not-Contact restrictions and related procedures to protect specified contacts, customers, vendors, and affiliates from solicitation or outreach by the Receiving Party as set forth in this Rider.

NOW, THEREFORE, in consideration of promises and mutual covenants set forth below, the parties agree as follows:

Scope of Work

Scope of DNC Restrictions and Related Obligations:

Protected Contacts and Exceptions

The Receiving Party shall not, directly or indirectly, contact, solicit, induce, or attempt to do business with any person or entity identified by the Disclosing Party on the Protected Contacts list, nor shall the Receiving Party cause any third party to do so on its behalf, for the duration set forth herein.

Protected Contacts (list names, companies, roles, and any identifying information):

Exceptions: The restrictions in this Rider shall not apply to contacts where the Receiving Party can demonstrate, by written records existing prior to the Effective Date or by independent commercial relationship developed without use of the Disclosing Party's confidential information, that the contact was already a bona fide customer, client, or vendor of the Receiving Party.

Apply restrictions to affiliates of the Disclosing Party?

Yes — Apply to affiliates and subsidiaries listed in the Protected Contacts section

Payment Terms

In consideration for the obligations assumed by the Receiving Party under this Rider, the Disclosing Party shall be entitled to the payments set forth below where applicable. The parties may also agree that this Rider imposes no additional fee and that consideration is satisfied by the parties' existing commercial relationship.

Payment Amount (if applicable): Payment Schedule / Milestones: Late Fee / Interest on Overdue Amounts:

Term and Termination

This Rider shall commence on the Effective Date and shall continue in effect until unless earlier terminated as provided below.

Notice Period for Termination (days):

Either party may terminate this Rider for material breach by the other party that remains uncured for the notice period specified above. Termination shall not relieve the Receiving Party of liability for breaches that occurred prior to termination, and the restrictions described herein that are expressly stated to survive shall remain in force as provided below.

Confidentiality

For purposes of this Rider, Confidential Information includes the Protected Contacts list, any customer or prospect lists, pricing, business strategies, contact details, and any non-public information disclosed by the Disclosing Party in written, electronic, or oral form. The Receiving Party shall hold such Confidential Information in strict confidence and shall not disclose it to any third party except as necessary to perform its obligations and only subject to a written agreement imposing confidentiality obligations at least as protective as those herein.

Confidential Information does not include information that: (a) is or becomes generally known to the public other than by the Receiving Party's breach of this Rider; (b) is rightfully received from a third party without restriction; (c) is independently developed by the Receiving Party without use of the Disclosing Party's Confidential Information; or (d) is required to be disclosed by law or valid legal process, provided that the Receiving Party gives prompt written notice to the Disclosing Party and cooperates in any lawful effort to limit or contest the disclosure.

Remedies; Injunctive Relief

The parties acknowledge that a breach of the DNC restrictions or confidentiality obligations may cause irreparable harm for which monetary damages would be an inadequate remedy. Accordingly, in addition to any other remedies available at law or in equity, the Disclosing Party shall be entitled to seek injunctive or equitable relief to prevent or curtail any actual or threatened breach, without the necessity of posting bond or proving actual damages.

Notices

Disclosing Party Notice Address: Receiving Party Notice Address:

Notices under this Rider shall be in writing and delivered by hand, nationally recognized overnight courier, or certified mail (return receipt requested) to the addresses provided above or to such other address as a party may designate in writing. Notice shall be effective upon receipt.

Governing Law; Venue

This Rider shall be governed by and construed in accordance with the laws of the state of without regard to conflict of laws principles. The parties submit to the exclusive jurisdiction of the state and federal courts located in that state for disputes arising out of or relating to this Rider.

Entire Agreement; Miscellaneous

This Rider constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes all prior and contemporaneous oral and written understandings, agreements, or communications relating to the Protected Contacts and the DNC restrictions. Except as expressly modified herein, the terms of the Underlying Agreement remain in full force and effect. In the event of any conflict between this Rider and the Underlying Agreement, the terms of this Rider shall control with respect to the subjects addressed in this Rider.

If any provision of this Rider is held to be invalid or unenforceable, the remaining provisions will remain in full force and effect. The obligations of confidentiality and DNC restrictions that by their nature survive termination shall survive for a period of following termination.

Execution

The parties have executed this Rider by their duly authorized representatives as of the Effective Date.

Disclosing Party (Company):

Printed Name:

By:

Date:

Receiving Party (Counterparty):

Printed Name:

By:

Date:

What the Miscellaneous DNC Rider Is and When It Applies

A Miscellaneous DNC Rider is a contract addendum that records Do-Not-Contact or related restrictions and other miscellaneous provisions layered onto a primary agreement. It defines limited-contact lists, permitted communications, exemptions, and narrow operational rules that modify the base contract without rewriting principal terms. The rider clarifies obligations for each party, assigns responsibility for compliance, and establishes notice, retention, and amendment mechanics so the main agreement and the rider operate together as a single integrated instrument.

Why Parties Use a Miscellaneous DNC Rider

A focused rider preserves the main agreement while managing sensitive contact preferences, regulatory restrictions, and operational exceptions. It reduces ambiguity about who may be contacted, how notices are delivered, and how breaches are handled, while supporting auditability and record retention required under U.S. law such as ESIGN and state UETA frameworks.

Typical Parties and Roles That Complete This Rider

Organizations add a Miscellaneous DNC Rider when they need targeted contact controls without renegotiating a full contract.

Enterprise legal and compliance teams managing outbound communications and vendor lists.
Sales or customer-success teams applying customer-specific do-not-contact preferences.
Third-party vendors and subcontractors required to respect client contact restrictions.

The rider is equally useful for vendors, customers, and intermediaries who must document contact restrictions and maintain an auditable record.

Who Signs and Why

Contract Manager

A contract manager or attorney typically signs on behalf of an organization after confirming the rider’s scope matches corporate policy and regulatory obligations; they ensure internal teams receive updated contact lists and compliance guidance.

Authorized Signatory

An authorized executive or officer with delegated signature authority binds the organization to the rider, confirms understanding of obligations, and accepts recordkeeping and enforcement responsibilities.

Essential Elements to Include in a Professional DNC Rider

A complete rider organizes contact restrictions, effective dates, permitted exceptions, enforcement remedies, notice mechanics, and amendment procedures so parties can operate consistently and defensibly.

DNC List

A precise, itemized list of persons, accounts, domains, or numbers subject to contact restrictions and the safe-harbor criteria for removing entries.

Scope

Defines communication channels covered (phone, email, SMS, in-person), transactional exceptions, and whether indirect contact through partners is restricted.

Effective Date

Specifies when the rider begins and whether it applies retroactively to prior notices or only prospectively.

Amendment

Explains how parties add or remove entries, required approvals, and notice timing for changes to the DNC list.

Remedies

Outlines breach consequences, cure periods, and indemnity or liquidated-damage provisions tied to unauthorized contact.

Recordkeeping

Requires retention of communications logs and audit evidence to demonstrate compliance with the rider and applicable laws.

Required Information and Key Fields

Party Names: Full legal names

Effective Date: MM/DD/YYYY

DNC Targets: Emails, phone numbers

Permitted Exceptions: List of allowed contacts

Signatory Authority: Name and title

Notice Address: Street or email

Step-by-Step: How to Complete the Miscellaneous DNC Rider

Follow these sequential steps to ensure the rider is accurate, enforceable, and properly incorporated into the base agreement.

01

Prepare DNC list: Collect and verify contact identifiers to include.
02

Set scope: Specify channels, exceptions, and allowed outreach.
03

Assign authority: Name the person who may update the list.
04

Sign and store: Execute, date, and retain an auditable copy.

How to Configure an Online Workflow for the Rider

Set up fields, authentication, and routing to preserve the audit trail and prevent unauthorized edits during e-signing.

Field	Configuration
Signature Type	Electronic signature with audit trail
Authentication	Email or SMS code verification
Template	Use a locked template to prevent edits
Expiration	Set a signing deadline and reminders

Where to Send the Completed Rider and How It Integrates

Understand routing so the executed rider is filed with the main agreement and accessible to compliance teams.

Send to Counterparty: Deliver via secure eSignature link or email.
Attach to Contract: Store executed rider with the primary agreement record.
Notify Teams: Alert legal, sales, and support teams of updates.
Maintain Audit Trail: Preserve timestamps, IPs, and signer authentication.

Digital Signing Considerations and Platform Requirements

Choose a compliant eSignature workflow that captures intent, consent, attribution, and durable retention.

Authentication: Email, SMS, or stronger
Audit Trail: Timestamped event log
Storage: Encrypted at rest

Key Timing and Deadlines to Track

Track effective dates, review windows, and update cycles so contact restrictions are current and enforceable.

Effective Date:

Date rider obligations commence.

Acknowledgment Deadline:

Timeframe for counterparty to acknowledge changes.

Amendment Window:

Period for adding or removing DNC entries.

Periodic Review:

Regular audit schedule to validate list accuracy.

Retention Trigger:

When retention clock begins for recordkeeping.

Common Mistakes When Preparing a DNC Rider

Using vague identifiers (e.g., 'marketing list') instead of full emails or phone numbers creates enforcement uncertainty and operational errors.
Failing to define exceptions leads to disputes when transactional or legal notices are sent to DNC contacts by mistake.
Not assigning an authorized updater causes operational drift and inconsistent list maintenance across teams and systems.
Omitting retention and audit requirements can undermine proof of compliance in regulatory or contractual disputes.

Penalties and Risks of an Incorrect or Incomplete Rider

Contract Breach: Monetary damages or injunctive relief

Operational Disruption: Lost trust and remediation costs

Regulatory Exposure: Fines where statutory restrictions apply

Litigation Risk: Increased likelihood of disputes

Data Privacy Risk: Improper data use violations

Enforceability Issues: Ambiguities may void rider terms

Practical Use Cases for a Miscellaneous DNC Rider

Two concise examples show how parties use a DNC rider to address specific operational needs without altering the core agreement.

Client Preference Implementation

A vendor receives a customer list requiring email opt-out for marketing

The rider specifies transactional exceptions only
Because the rider is appended to the master services agreement and logged with an audit trail, the vendor enforces filters and documents each compliance action for audits and dispute resolution.

Subcontractor Communication Limits

A general contractor limits subcontractor outreach to authorized contacts for a sensitive project

The rider names permitted representatives and escalation channels
The result is fewer disputes, clear operational handoffs, and a retained record showing adherence to the specified contact rules.

eSignature Vendor Pricing and Feature Snapshot for Completing the Rider

Comparison of common commercial eSignature providers on entry-level price and key feature rows relevant to executing and managing the rider.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies	Varies	Varies

FAQs and Troubleshooting for the Miscellaneous DNC Rider

Answers to common questions about enforceability, digital signing, updates, and recordkeeping for DNC riders.

Need help? Contact support

Is an e-signed rider legally binding?
Yes, electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws where adopted, provided intent, consent, attribution, and retention requirements are met.
When does the rider take effect?
The rider takes effect on the Effective Date specified in the document; if silent, the signing date may control. State contract rules and any conditional language in the rider can alter this outcome.
Do I need a notary or witness?
Not typically required for DNC riders, but state-specific formalities or corporate execution rules may require a notary or witness; check local requirements and internal delegated authority policies.
How should updates to the DNC list be made?
Use the amendment process in the rider: authorized updater submits written change, counterparty acknowledgment if required, and both parties preserve the audit trail for the change.
What records should be retained?
Retain executed rider, audit logs, and change history in encrypted storage for the retention period stated in policy; federal and HIPAA baselines may apply for related records.
Can the rider conflict with the main contract?
The rider should expressly state it amends and integrates with the main contract; where conflicts exist, the parties should specify priority to avoid ambiguity.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now