Establishing secure connection…Loading editor…Preparing document…

Legal CDA Election Agreement

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

Legal CDA Election Agreement

This Legal CDA Election Agreement (the "Agreement") is made and entered into as of Effective Date: by and between Party A Name: , an entity organized as Corporation LLC Other, with principal place of business at ; and Party B Name: , an entity organized as Corporation LLC Other, with principal place of business at .

RECITALS

WHEREAS, Party A and Party B have previously entered into one or more Confidential Disclosure Agreements or similar instruments governing the exchange of Confidential Information (collectively, the "Existing CDAs"); and

WHEREAS, the parties desire to make an affirmative election under the Existing CDAs to apply specific data categories, handling procedures, and protections set forth herein for the exchange and treatment of Confidential Information and any Controlled Data Assets ("CDA Election"); and

WHEREAS, the parties agree that the terms of this Agreement shall supplement and, where expressly provided, modify the Existing CDAs solely to the extent necessary to effectuate the CDA Election described below.

NOW, THEREFORE

In consideration of the mutual promises and covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. DEFINITIONS

For purposes of this Agreement, the following terms shall have the meanings set forth below. "Confidential Information" means any information disclosed by a Disclosing Party to a Receiving Party, whether in written, oral, electronic or other form, that is designated as confidential or that a reasonable person should understand to be confidential given the nature of the information and the circumstances of disclosure. "Controlled Data Assets" means specific categories of Confidential Information identified in Section 2 below that are subject to heightened controls under the CDA Election.

2. CDA ELECTION AND SCOPE

2.1 Election. Each party hereby elects that the following categories of information exchanged between the parties shall be treated as Controlled Data Assets and governed by the protections specified in this Agreement:

Business Confidential Information (including financials, pricing, strategic plans)
Personal Data (including customer personal identifiers and personnel information)
Technical Data (including software, source code, algorithms)
Other (describe):

2.2 Scope. The CDA Election applies to all Confidential Information of the elected categories disclosed on or after the Effective Date identified above, regardless of the media or format of disclosure, except as expressly excluded in writing by both parties.

3. CONFIDENTIALITY AND DATA HANDLING OBLIGATIONS

3.1 Standard of Care. The Receiving Party shall protect Controlled Data Assets with at least the same degree of care it uses to protect its own Confidential Information of a similar nature, but in no event less than a reasonable standard of care, and shall implement administrative, technical and physical safeguards appropriate to the sensitivity of the Controlled Data Assets.

3.2 Use and Disclosure. The Receiving Party shall use Controlled Data Assets solely for the purposes expressly authorized in writing by the Disclosing Party and shall not disclose such Controlled Data Assets to any third party except as permitted herein or with the Disclosing Party's prior written consent.

3.3 Authorized Recipients. The Receiving Party may disclose Controlled Data Assets only to employees, contractors or agents who have a demonstrated need to know and who are bound by confidentiality obligations at least as restrictive as those set forth in this Agreement. The Receiving Party remains liable for any breach of this Agreement caused by its authorized recipients.

4. DATA SECURITY INCIDENTS

4.1 Notification. In the event the Receiving Party discovers a confirmed or suspected security incident resulting in unauthorized access to Controlled Data Assets, the Receiving Party shall notify the Disclosing Party without undue delay and in any event no later than seventy-two (72) hours after becoming aware of the incident.

4.2 Remediation. The Receiving Party shall take reasonable and prompt action to contain, investigate and remediate the incident and shall provide the Disclosing Party with reasonable cooperation, information and assistance in connection with remediation and any regulatory or third-party notifications required by applicable law.

5. TERM AND TERMINATION

5.1 Term. This Agreement shall commence on the Effective Date and continue for a period of years, unless earlier terminated as provided herein.

5.2 Survival. The Receiving Party's obligations with respect to Controlled Data Assets disclosed during the term of this Agreement shall survive termination or expiration of this Agreement for a period of years, or for such longer period as required by applicable law.

6. REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that it has the full right, power and authority to enter into and perform its obligations under this Agreement and that performance will not violate any agreement or legal obligation to which it is bound.

7. INDEMNIFICATION

Each party (the "Indemnifying Party") shall indemnify, defend and hold harmless the other party (the "Indemnified Party") from and against any and all losses, damages, liabilities, costs and expenses (including reasonable attorneys' fees) arising out of or resulting from a breach of this Agreement by the Indemnifying Party, including unauthorized disclosure or use of Controlled Data Assets.

8. LIMITATION OF LIABILITY

EXCEPT FOR LIABILITY ARISING FROM A PARTY'S GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR A BREACH OF SECTION 3 (CONFIDENTIALITY AND DATA HANDLING) OR 4 (DATA SECURITY INCIDENTS), NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

9. NOTICES

Notices shall be in writing and deemed given when delivered personally, sent by certified mail (return receipt requested), or sent by nationally recognized overnight courier, to the addresses provided above or to such other address as either party may designate in writing in accordance with this Section.

10. AMENDMENT; WAIVER

No amendment or waiver of any provision of this Agreement shall be effective unless set forth in a written instrument signed by duly authorized representatives of both parties. The failure of either party to enforce any right shall not constitute a waiver of that right.

11. GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to its conflicts of law principles.

12. ENTIRE AGREEMENT

This Agreement, together with the Existing CDAs as supplemented hereby, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous understandings, agreements, representations and warranties, both written and oral, with respect to such subject matter.

13. SEVERABILITY

If any provision of this Agreement is held to be invalid, illegal or unenforceable, the remaining provisions of this Agreement will remain in full force and effect and such invalid provision will be reformed to reflect the parties' original intent to the maximum extent permitted by law.

14. COUNTERPARTS

This Agreement may be executed in one or more counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Signatures transmitted by electronic means shall be binding for all purposes.

ADDITIONAL ELECTION TERMS

Party A Printed Name:

By:

Date:

Party B Printed Name:

By:

Date:

Enter text✕

What the Legal CDA Election Agreement Is

A Legal CDA Election Agreement is a written instrument used by parties to select or confirm that certain confidential data, communications, or transactions will be governed by the terms of an existing Confidential Disclosure Agreement (CDA) or by specified confidentiality and disclosure rules. It typically identifies the parties, describes the categories of covered information, sets the effective date and term, and records any opt-in or opt-out election of specified CDA provisions. The document clarifies obligations for handling, sharing, and protecting sensitive data and creates a record suitable for enforcement or compliance review.

Why a Clear Election Matters

Using a formal election agreement reduces ambiguity about which disclosures are protected, documents the parties’ mutual intent, and helps meet regulatory or contractual obligations for handling confidential or regulated data. A written election supports enforcement, audit readiness, and consistent internal controls.

Why a Clear Election Matters

Typical Parties and Practical Uses

Organizations and individuals use a Legal CDA Election Agreement whenever they need to extend, limit, or specify confidentiality protections for a defined set of data or transactions.

  • Corporate counsel and contracting teams managing supplier or partner data exchanges, ensuring corporate NDAs apply to a specific project or dataset.
  • Clinical research sponsors and health providers designating clinical datasets subject to a master CDA and HIPAA safeguards.
  • Government contractors or grant recipients electing contract-specific confidentiality rules tied to federal procurement or grant terms.

The agreement is useful across transactions that involve proprietary information, regulated data, or multi-party collaborations where clarity about confidentiality scope is essential.

Who Signs and Why

General Counsel

In-house counsel approves and signs the election when it affects corporate confidentiality policies and downstream contractual obligations. They review scope, carve-outs, and alignment with existing CDAs to mitigate litigation and compliance risk.

Compliance Officer

A compliance lead or privacy officer signs on behalf of a business unit when the election triggers regulatory controls (for example HIPAA or data localization rules) and ensures appropriate safeguards, training, and logging are in place.

Core Elements to Include in a Professional Agreement

A well-drafted Legal CDA Election Agreement contains defined parties, precise scope, effective dates, handling rules, permitted disclosures, and signature blocks to avoid ambiguity and enforcement issues.

Parties Identified

List full legal names and entity types for every party, including any doing-business-as names, to ensure the agreement binds the correct legal entities and avoids identity disputes during enforcement.

Scope of Data

Describe categories of confidential information by type and examples rather than broad terms; include exclusions such as public domain or independently developed data to reduce interpretation disputes.

Effective Term

State the effective date and duration, and whether confidentiality obligations survive termination; survival clauses commonly extend for a fixed period or indefinitely for trade secrets.

Permitted Use

Specify allowed purposes for using disclosed data and any restrictions on onward sharing, processing, or cross-border transfer to ensure regulatory compliance and proper access control.

Security Measures

Require baseline technical and administrative safeguards (encryption, access controls, breach notification) and reference any industry-specific standards such as HIPAA or other applicable frameworks.

Signatures and Authority

Include signature blocks with printed names, titles, and dates; state who has authority to sign on behalf of each party to reduce later challenges to enforceability.

Step-by-Step: How to Complete the Agreement

Follow a clear sequence to reduce errors and ensure the election is effective and properly recorded.

  • 01
    Gather documents: Collect the master CDA and related exhibits.
  • 02
    Confirm parties: Verify legal entity names and signing authority.
  • 03
    Define scope: List the exact datasets or activities covered.
  • 04
    Sign and date: Obtain signatures with printed names and titles.

Typical Processing Flow for an Election

A predictable workflow keeps the election traceable and reduces legal friction during audits or disputes.

  • Upload document: Store the draft with version control.
  • Assign reviewers: Route to counsel and compliance for approvals.
  • Execute signatures: Collect signatures in order or simultaneously.
  • Distribute copies: Provide executed copies to all parties and archive.

Digital Workflow Settings to Consider

Configure validation, authentication, and recordkeeping to match the agreement’s sensitivity and legal requirements.

Field Configuration
Signer Authentication Use email plus SMS code or higher for PHI.
Document Versioning Enable version control and filename conventions.
Audit Trail Capture timestamps, IPs, and signer events.
Access Controls Limit viewing to authorized users only.

Digital Signing and eSubmission Essentials

Choose a platform that supports required authentication, secure storage, and an auditable signature record.

  • Authentication: Email, SMS, KBA.
  • Document Formats: PDF, DOCX supported.
  • Integrations: CRM, cloud storage.

Ensure the platform’s compliance posture aligns with the agreement’s regulatory requirements and any needed BAAs or contracts.

Key Timing and Deadlines to Track

Monitor effective dates, notice windows, and retention start points to maintain compliance and preserve legal rights.

Effective Date Entry:

Record the MM/DD/YYYY effective date when parties sign.

Notice Periods:

Track any required advance notice for opt-outs.

Survival Terms:

Note how long confidentiality survives termination.

Audit Windows:

Schedule compliance reviews within set intervals.

Retention Start:

Retention usually begins on the effective date or termination date.

Milestones: From Draft to Archive

Use a milestone checklist to track review, signatures, and archival steps through the agreement lifecycle.

01

Draft Completion

Finalize language and exhibits before review.

02

Legal Review

Obtain counsel sign-off on scope and exceptions.

03

Execution

Collect signatures and date the document.

04

Archival

Store executed copy with access controls and audit trail.

Common Preparation Pitfalls to Avoid

  • Using generic descriptions for covered data invites disputes about whether an item is protected and can undermine enforcement.
  • Failing to confirm signatory authority leads to challenges that delay implementation and may require re-execution.
  • Neglecting to capture an auditable execution trail complicates later proof of intent, attribution, or the signing timeline.
  • Overlooking alignment with regulatory obligations (for example HIPAA or export controls) can trigger compliance violations and penalties.

Potential Consequences of an Incorrect Election

Contract Disputes: Enforceability questions.
Regulatory Fines: Breach may trigger governmental penalties.
Data Exposure: Unauthorized disclosures increase liability.
Operational Delays: Projects can be paused for remediation.
Reputational Harm: Loss of partner trust.
Financial Loss: Costs for remediation and litigation.

Security and Compliance Checklist

Encryption: AES-256 at rest
In-Transit: TLS 1.2/1.3
Audit Trail: Timestamps and IP logs
Access Control: Role-based permissions
BAA Availability: Required for HIPAA
21 CFR Part 11: Compliant where applicable

eSignature Pricing and Feature Comparison

Compare common pricing metrics and compliance features across market options when selecting a signing platform for executing Legal CDA Election Agreements.

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 by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Premium tier) Varies by plan Varies by plan Varies by plan Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA required) Check vendor Check vendor Check vendor Check vendor
Envelope Cap No envelope cap 100 envelopes/user/year limit Varies by plan Varies by plan Varies by plan

Real-World Examples of an Election Agreement in Use

These concise scenarios illustrate how parties use election agreements to resolve scope and compliance questions before data exchange.

Clinical Research Allocation

A sponsor elects to apply a master CDA to trial datasets for one multicenter study to centralize protections.

  • The point: preserve PHI safeguards across sites.
  • Outcome: reduced review cycles and a consistent breach notification process, with a BAA and specific data handling instructions attached to the election agreement.

Vendor Data Access

A company contracts a cloud vendor and elects CDA terms for customer lists and pricing models.

  • The point: ensure downstream subcontractors inherit protections.
  • Outcome: clearer audit rights, defined permitted uses, and routine attestations from the vendor and its subcontractors.

Best Practices for Drafting and Execution

Follow consistent drafting patterns and execution standards to reduce negotiation time and legal risk.

Be Specific About Scope
Define covered information with examples and precise categories; avoid catchall terms that invite later disputes or overbroad protection claims.
Align with Master CDA
Cross-reference the controlling CDA by date and parties to avoid conflicting terms and ensure the election inherits intended obligations.
Standardize Execution
Use a consistent signature block and require printed name and title; require initials on each page when the agreement references page-by-page duties.
Record the Audit Trail
Capture timestamps, signer authentication method, and delivery records; retain the audit trail for the applicable retention period to support enforceability.

Frequently Asked Questions About the Agreement

Answers to common questions about validity, e-signatures, notarization, and updating an existing election agreement.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users