When is D2.2 necessary?

Use D2.2 when you need a concise supplement to record specifics not covered by the primary agreement, such as project-level deliverables, payment exceptions, or temporary modifications.

Can D2.2 be signed electronically?

Yes. Electronic signatures meet ESIGN Act (15 U.S.C. ch. 96) and UETA requirements when intent, consent, attribution, and record retention are documented.

Do I need a notary or witnesses?

It depends on content and state law; notary or witness requirements apply when the supplement alters documents that require notarization, such as deeds or some powers of attorney.

What if a party's name is entered incorrectly?

Mismatched names can impair enforceability; correct errors before signing. If executed, reissue and re-sign the corrected form referencing the original to maintain the audit trail.

How should I store executed copies?

Store signed records in a secure contract repository with tamper-evident storage, backup, and the ability to reproduce audit trails for litigation or audits.

Who can sign D2.2 on behalf of an organization?

Authorized signers are those with delegated authority per corporate resolution or procurement policy; confirm signing authority in advance to avoid invalid execution.

Electronic Signature
Templates
Miscellaneous
Miscellaneous Form D2.2

Miscellaneous Form D2.2

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

MISCELLANEOUS FORM D2.2

This Miscellaneous Form D2.2 (the Agreement) is entered into as of Effective Date: by and between Service Provider Name: (Service Provider) and Client Name: (Client). The Service Provider and the Client are collectively referred to as the Parties.

WHEREAS

WHEREAS, the Service Provider is engaged in the business of providing professional services and possesses the qualifications, experience and ability to perform the services described herein; and

WHEREAS, the Client desires to retain the Service Provider to perform the services set forth in this Agreement, and the Service Provider is willing to perform such services on the terms and conditions contained in this Agreement.

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

1. SCOPE OF WORK

The Service Provider shall perform the tasks, deliverables and services described in this Section and any attachments incorporated by reference. The Service Provider shall perform all services in a professional and workmanlike manner consistent with industry standards.

Detailed Scope of Work

2. PAYMENT TERMS

Compensation: In consideration for the services performed under this Agreement, the Client shall pay the Service Provider the total amount of $ (USD), subject to the payment schedule below.

Payment Schedule and Invoicing

Invoices are due and payable within days of receipt, unless otherwise agreed in writing. Payments shall be made to the Service Provider at the following remit-to instructions:

Remit To / Banking Details

Late Payment: Any amount not paid within the payment period shall accrue interest at % per month (or the maximum lawful rate if lower), plus reasonable collection costs incurred by the Service Provider.

3. TERM AND TERMINATION

Term: This Agreement shall commence on Start Date: and shall continue until End Date: , unless earlier terminated in accordance with this Section.

Termination for Convenience: Either Party may terminate this Agreement without cause upon providing days' prior written notice to the other Party.

Termination for Cause: Either Party may terminate this Agreement immediately upon written notice if the other Party materially breaches any obligation hereunder and fails to cure such breach within thirty (30) days after receipt of written notice specifying the breach.

4. CONFIDENTIALITY

Definition: "Confidential Information" means all non-public information disclosed by a Party (Disclosing Party) to the other Party (Receiving Party), whether oral, written or electronic, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure.

Obligation: The Receiving Party shall (i) hold Confidential Information in strict confidence, (ii) not disclose Confidential Information to any third party except as permitted by this Agreement, and (iii) use Confidential Information solely to perform its obligations under this Agreement. The Receiving Party shall take reasonable measures to protect Confidential Information, not less than those used to protect its own similar confidential information.

Exceptions: Confidential Information does not include information that is (a) publicly available other than by breach of this Agreement; (b) rightfully received by the Receiving Party from a third party without breach of any obligation of confidentiality; (c) independently developed without use of the Disclosing Party's Confidential Information; or (d) required to be disclosed by law or court order, provided the Receiving Party gives prompt notice to the Disclosing Party and limits the scope of disclosure.

5. REPRESENTATIONS; INDEPENDENT CONTRACTOR

Each Party represents that it has the full power and authority to enter into this Agreement. The Service Provider is an independent contractor and not an employee, partner or agent of the Client for any purpose.

6. LIMITATION OF LIABILITY

Except for liability arising from willful misconduct or gross negligence, neither Party shall be liable to the other for consequential, incidental, special or punitive damages. The aggregate liability of either Party for claims arising out of this Agreement shall not exceed the total fees paid by the Client to the Service Provider under this Agreement during the twelve (12) months preceding the event giving rise to the claim.

7. GOVERNING LAW

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

8. ENTIRE AGREEMENT

This Agreement, together with any exhibits and attachments expressly incorporated herein, constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, representations and understandings, whether written or oral. Any amendment to this Agreement must be in writing and signed by authorized representatives of both Parties.

9. MISCELLANEOUS

Assignment: Neither Party may assign this Agreement without the other Party's prior written consent, except that the Service Provider may assign to an affiliate or in connection with a merger or sale of substantially all of its assets.

Notices: All notices under this Agreement must be in writing and delivered to the addresses below by hand, courier, or certified mail.

Service Provider Address for Notices Client Address for Notices

Service Provider:

By:

Date:

Client:

By:

Date:

What the Miscellaneous Form D2.2 Is and when it applies

Miscellaneous Form D2.2 is a supplemental administrative form used to capture additional transaction-specific information that standard templates do not cover. Organizations commonly attach it to primary agreements, procurement records, or internal approvals to record clarifications, optional provisions, or project-level metadata. The form is typically short, modular, and intended to be completed alongside a core agreement; it may reference contract line items, delivery schedules, or special conditions. Because its contents can alter obligations, accuracy and consistent distribution to all parties is important for enforceability and recordkeeping.

Why completing D2.2 carefully reduces downstream risk

A clear, fully completed Miscellaneous Form D2.2 prevents ambiguity about supplemental terms, supports audit trails, and provides evidence of agreed exceptions or additions to a contract. Accurate completion reduces disputes over scope, billing, and deadlines and improves traceability during audits or regulatory reviews.

Who typically completes or signs Form D2.2

Departments and roles that commonly prepare or review this form vary by use case, but usually include contract administrators, project managers, procurement staff, and legal reviewers.

Contract administrators who attach D2.2 to purchase orders and vendor agreements for scope clarifications or special payment terms.
Project managers who record project-specific deliverables, milestones, or nonstandard acceptance criteria.
Legal or compliance reviewers who confirm that any supplemental terms align with company policy and applicable law.

Ensure all signatory roles are identified before circulation so the document is routed correctly and executed by authorized representatives.

Step-by-step: completing and executing D2.2

Follow this sequence to prepare, approve, and finalize the Miscellaneous Form D2.2 so it is enforceable and traceable in your records.

01

Prepare Draft: Populate all fields, reference the parent agreement, and add attachments.
02

Internal Review: Route to legal and procurement for policy and budget checks.
03

Signatory Approval: Obtain signatures from authorized representatives in the required order.
04

Record and Distribute: Save executed copy to contract repository and share to stakeholders.

How D2.2 moves through an organization

Typical routing follows a consistent path to ensure approvals, signatures, and archival are captured in sequence.

Initiation: Originator creates D2.2 and attaches supporting documentation.
Stakeholder Review: Procurement, finance, and legal review for compliance and budget alignment.
Execution: Authorized signers sign electronically or on paper.
Archival: Executed document stored in central contract management system.

Typical digital workflow settings for D2.2

Configure your e-signature workflow to match your approval and retention policies before sending D2.2 for signature.

Field	Configuration
Signer Order	Sequential routing to ensure approvals occur in required sequence
Authentication	Email link or SMS code; increase to KBA for high-risk transactions
Audit Trail	Enable full audit logging for IP, timestamp, and actions
Retention	Set automatic archival policy to central repository with versioning

Digital signing considerations and platform requirements

Not all eSignature platforms support the same authentication, audit, or retention features needed for legal defensibility.

Authentication Options: Email, SMS, KBA, or SSO depending on risk and compliance needs
Document Formats: PDF and DOCX support ensures the signed record is preserved
Integration: Connectors to CRM or contract repository aid lifecycle management

Choose settings that balance signer convenience with the authentication and retention controls your legal and records teams require.

Security and compliance items to note when using D2.2

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Audit Trail: Timestamps, IP addresses, and action logs retained

HIPAA: BAA required for PHI-related content

ESIGN / UETA: E-signatures recognized under federal and state law

21 CFR Part 11: Applicable for FDA-regulated records requiring electronic controls

SOC 2 / ISO: Controls may be required by enterprise counterparties

Common legal and operational risks if D2.2 is incorrect

Ambiguous Terms: May lead to contractual disputes and litigation

Incorrect Dates: Can affect rights, deadlines, and cure periods

Mismatched Parties: May void enforcement or trigger re-execution

Missing Signatures: Leaves the supplement unenforceable

Noncompliant Handling: Regulatory fines if controlled data is mishandled

Improper Retention: Records may be unavailable for audits or disputes

Frequent preparation and execution challenges

Leaving references to sections that do not exist in the primary contract, causing confusion.
Providing vague descriptions of modifications rather than explicit, measurable changes.
Routing to signers who are not authorized, delaying execution and creating invalid signatures.
Using inconsistent identifiers so the supplement cannot be matched to contract management records.

Timing to watch when D2.2 affects compliance or tax reporting

Some uses of D2.2 may trigger deadlines for reporting, payment, or document filing depending on the parent transaction and applicable law.

Tax Reporting Triggers:

Provide payee details promptly to meet information return deadlines

Contract Milestones:

Align effective date to project schedules to avoid missed deliverables

Regulatory Notices:

File required notices within agency windows when supplements change compliance status

Retention Start:

Retention typically begins on execution date

Revision Deadlines:

Submit amendments before the next billing or reporting cycle

Key processing milestones for D2.2

Follow these sequential milestones to move D2.2 from draft to archived executed record.

01

Draft Completed

Form populated and attachments prepared for review

02

Internal Approval

Finance, procurement, and legal approvals secured

03

Execution

Signatures collected in the required order

04

Archival and Distribution

Executed copy stored and shared with stakeholders

How D2.2 differs from a standard amendment or addendum

Use this quick comparison to choose whether to use Form D2.2, a formal amendment, or a simple memo depending on the legal effect desired.

Criteria	Misc Form D2.2	Formal Amendment
Legal Effect	supplementary detail	changes core contract terms
Formality	lower formality	higher formality
Required Approvals	departmental	often executive/legal signoff
Use Case	operational clarifications	contract term changes

eSignature vendor comparison relevant to signing D2.2

Comparing common vendor capabilities can help match platform features to the authentication, bulk distribution, and compliance needs of executing Form D2.2. Pricing shown is plan-level starting price or typical published rate where available.

	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	Yes, 7-day trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Varies by plan	Varies by plan	Yes	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about Miscellaneous Form D2.2

Answers to common execution, signing, and retention questions to resolve issues quickly during preparation or signing of D2.2.

Need help? Contact support

When is D2.2 necessary?
Use D2.2 when you need a concise supplement to record specifics not covered by the primary agreement, such as project-level deliverables, payment exceptions, or temporary modifications.
Can D2.2 be signed electronically?
Yes. Electronic signatures meet ESIGN Act (15 U.S.C. ch. 96) and UETA requirements when intent, consent, attribution, and record retention are documented.
Do I need a notary or witnesses?
It depends on content and state law; notary or witness requirements apply when the supplement alters documents that require notarization, such as deeds or some powers of attorney.
What if a party's name is entered incorrectly?
Mismatched names can impair enforceability; correct errors before signing. If executed, reissue and re-sign the corrected form referencing the original to maintain the audit trail.
How should I store executed copies?
Store signed records in a secure contract repository with tamper-evident storage, backup, and the ability to reproduce audit trails for litigation or audits.
Who can sign D2.2 on behalf of an organization?
Authorized signers are those with delegated authority per corporate resolution or procurement policy; confirm signing authority in advance to avoid invalid execution.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now