Can an addendum be signed electronically?

Yes. Under the federal ESIGN Act and state UETA provisions (15 U.S.C. ch. 96; UETA adopted in 49 states), electronic signatures that show intent, consent, attribution, and retention are legally enforceable, subject to limited statutory exceptions.

What makes the addendum legally valid?

A valid addendum identifies the original contract, clearly states modifications, is signed by authorized parties, and demonstrates signer intent and consent. Retain the executed record and an audit trail showing attribution and timestamp.

Who must sign the addendum?

Individuals with authority to bind their organization must sign. Where authority is delegated, provide title and role in the signature block and document delegation if required by procurement rules.

Is notarization or witnessing required?

Generally no for commercial contract amendments. Notarization is only occasionally required by state law or for specific instrument types; verify local requirements when the addendum affects real estate or power-of-attorney matters.

How long should executed addenda be kept?

Retain executed addenda for project term plus appropriate post-termination period—follow IRS (3 years, IRC §6501(a)), HIPAA (6 years, 45 CFR §164.530(j)), and any industry-specific rules.

What if a signer refuses or disputes the signature?

Preserve all audit logs, communications, and proof of authentication. Dispute resolution depends on the contract provisions; consult legal counsel and consider escalation clauses in the original agreement.

Electronic Signature
Templates
Project Management
Project Management Support Plan Addendum

Project Management Support Plan Addendum

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

PROJECT MANAGEMENT SUPPORT PLAN ADDENDUM

Project Identification

Project Title:

Project ID: Effective Date of Addendum:

Client Service Provider Project Manager (Provider)

Recitals

This Project Management Support Plan Addendum (the Addendum) is made effective as of and supplements the existing Project Management Support Plan dated (the Original Plan). All capitalized terms not defined herein shall have the meanings set forth in the Original Plan.

Purpose and Scope

Purpose: This Addendum documents changes to support levels, responsibilities, deliverables, schedule, and budget as agreed between Client and Service Provider.

Revised Scope of Work Out-of-Scope Items

Deliverables and Acceptance Criteria

Deliverables described below shall be subject to the Acceptance Criteria set forth in each line item. Acceptance requires written sign-off by an authorized Client representative within the specified acceptance period.

Deliverable 1 — Title Acceptance Criteria

Due Date:

Deliverable 2 — Title Acceptance Criteria

Due Date:

Timeline and Milestones

Revised Project Start Date: Revised Project End Date:

Milestone 1

Milestone 1 Target Date:

Milestone 2

Milestone 2 Target Date:

Budget and Payment

Total Addendum Cost: $

Payment Schedule

Hourly Rate for Change Orders (if applicable): $

Pre-approval required from Client for any additional costs exceeding $

Change Order Process

All changes to scope, schedule, or budget shall be effected only by a written Change Order signed by authorized representatives of both parties. A Change Order shall specify the change, impact on schedule, and any price adjustments. The Service Provider shall not proceed with change work until Client approval is documented in accordance with this provision.

Change Order Approval Contacts

Confidentiality

Each party acknowledges that during the performance of this Addendum it may receive Confidential Information of the other party. Confidential Information shall be used solely for performance hereunder and shall be protected with at least the same degree of care as each party uses to protect its own confidential information, but in no event less than reasonable care. Disclosure is permitted only to those employees, contractors, or agents who require access to perform obligations under this Addendum and who are bound by confidentiality obligations no less protective than those set forth herein.

Liability; Indemnity

Except for willful misconduct or gross negligence, each party's liability under this Addendum shall be limited to direct damages and capped at the amount paid by Client to Service Provider under this Addendum. Neither party shall be liable for incidental, special, indirect, or consequential damages, including loss of profits. Service Provider shall indemnify Client against third-party claims arising from Service Provider's breach of material obligations hereunder, subject to the limitations above.

Liability Cap: $

Termination

Either party may terminate this Addendum for convenience upon days prior written notice. Termination for cause may be exercised immediately upon material breach if such breach is not cured within 10 days after written notice.

Reporting & Escalation

Regular status reporting will be provided at a frequency of . In the event of unresolved issues, escalation shall proceed to the following contacts:

Governing Law

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

Representations and Authority

Each party represents and warrants that it has the full right, power, and authority to enter into this Addendum and to perform all obligations hereunder, and that the individual signing below is authorized to bind the respective party.

Client — Printed Name:

By:

Date:

Service Provider — Printed Name:

By:

Date:

What this Project Management Support Plan Addendum Is

A Project Management Support Plan Addendum is a formal amendment that supplements a primary project management agreement by defining additional support services, changed deliverables, updated responsibilities, and any cost or schedule impacts. It records agreed modifications to scope, staffing, or governance without replacing the original contract, and is used when discrete changes are required during project execution to keep roles, milestones, and acceptance criteria aligned.

Why add an explicit support-plan addendum

An addendum clarifies scope adjustments, assigns new responsibilities, and preserves auditability for approvals and budget changes. It reduces ambiguity, supports change control, and creates a record that helps resolve disputes and track liability and deliverable acceptance.

Who typically prepares and signs this addendum

All signers should have authority to bind their organization for the limited changes recorded; include legal or procurement review when fiscal or compliance risk increases.

Project managers and PMO leads who control scope, resourcing, and schedules; they define operational changes and run approvals.
Contracting officers and vendor account managers who accept cost or timeline adjustments and confirm commercial terms.
External contractors or subcontractors who must acknowledge scope, payment changes, and new milestones before work continues.

Core sections to include in a professional addendum

A clear addendum contains concise, labeled sections so reviewers can confirm changes quickly and consistently.

Scope Amendment

Precisely describe added, removed, or modified tasks, deliverables, and boundaries so obligations are unambiguous.

Roles & Responsibilities

List affected parties, new owner assignments, escalation contacts, and decision authorities for the amended scope.

Milestones & Deliverables

Provide measurable deliverables, acceptance criteria, and updated milestone dates tied to payment or approval triggers.

Change Request Workflow

Define approval steps, who may authorize changes, and how future modifications will be captured and priced.

Cost & Payment

State cost impacts, invoicing schedule, and any retained rights for dispute or audit of added charges.

Reporting & Governance

Specify reporting frequency, required status artifacts, and any additional governance checkpoints introduced by the change.

Step-by-step: completing the addendum

Follow these sequential steps to draft, approve, and finalize an addendum that integrates with the original project agreement.

01

Draft Amendment: Describe exact changes and reference original contract clauses.
02

Internal Review: Route to PMO, finance, and legal for approval and cost validation.
03

Obtain Signatures: Collect authorized signatures and dates from all parties.
04

Distribute & Archive: Share final signed copy with stakeholders and update records.

Configuring an online workflow for the addendum

Set up fields, signer order, and authentication to match organizational approval requirements before sending the document for signature.

Field	Configuration
Document Upload	Upload a PDF or DOCX; enable version naming for traceability.
Field Placement	Place signature, date, and initial fields; mark required fields.
Signer Roles	Assign roles and routing order for approvals and countersignatures.
Authentication	Select email or SMS code authentication; require stronger methods for higher risk.

Where to send and how routing works

This sequence explains typical routing when the addendum is executed electronically or via traditional signatures.

Originator Upload: Project manager uploads the addendum and assigns fields for signers.
Signers Notified: Each signer receives a secure link or email to review and sign.
Sign and Timestamp: Signers apply signatures; audit trail captures timestamp and IP.
Distribution: System or administrator circulates executed copies to finance and archive.

Technical requirements and supported formats

Choose platform settings that preserve the signed record, allow export to archival formats, and meet any industry compliance requirements.

File Formats: PDF and DOCX are supported for reliable rendering.
Integrations: Connectors for Salesforce, NetSuite, and Google Workspace simplify routing.
Security Controls: Use TLS, audit trails, and optional two-factor authentication.

Typical timeframes and internal deadlines

Use these common internal timelines as planning defaults; adjust according to contract terms and procurement rules.

Effective Date Selection:

Specify the effective date and ensure alignment with milestone scheduling and billing cycles.

Internal Review Window:

Allow 3–7 business days for legal and finance to review and comment on the addendum.

Signer Response Time:

Request signatures within five business days to avoid schedule delays.

Execution Confirmation:

Treat the addendum as binding when all required signatures are captured and dated.

Record Update:

Update project and contract records within two business days of final execution.

Common preparation errors to avoid

Unclear scope language that leaves room for differing interpretations of deliverables and acceptance.
Mismatched party names or contract IDs that break the legal linkage to the original agreement.
Omitting updated payment terms or failing to specify invoicing milestones tied to the change.
Not obtaining proper authority to bind an organization, resulting in signatures being disputed later.

Operational and legal risks of incorrect addenda

Contract Disputes: Unclear amendments increase litigation and arbitration risk.

Payment Delays: Vague cost language can withhold invoices or trigger disputes.

Regulatory Exposure: Failure to preserve records may affect audits and compliance.

Invalid Signatures: Improper authentication can void the amendment.

Data Breach: Poor security of signed records risks confidential disclosure.

Operational Confusion: Not updating project plans causes missed deliverables.

eSignature vendor comparison for executing the addendum

Basic vendor differences by starting price and core capabilities; signNow appears first for parity with other enterprise offerings.

	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 cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Supporting documents and export formats to preserve

Collect related artifacts and export in durable formats to ensure the amendment remains reproducible and auditable.

Supporting Documents

Attach related change requests, approval emails, SOWs, and cost worksheets that demonstrate authorization for the amendment.

File Formats

Store final executed copies as PDF/A and keep an editable DOCX source to support future redlines and version control.

Version Control

Use a naming convention and retain prior versions so auditors can trace the evolution of the change.

Audit Trail

Preserve signer audit logs (timestamps, IP, authentication proof) to demonstrate attribution and intent.

Practical tips for accurate and efficient completion

Small habits and controls reduce risk, accelerate approvals, and keep project delivery on schedule.

Use a standardized template

Start from a vetted addendum template to ensure all necessary sections are present and to reduce review cycles.

Require minimal essential fields

Limit free-text fields; use checkboxes and enumerated lists to speed review and reduce ambiguity.

Confirm signer authority

Validate that signers have delegated authority to bind their organization to avoid later challenges.

Keep a change log

Record who requested changes, approvals, and reasons to maintain an auditable trail for future disputes.

Real-world examples of addendum use

Examples illustrate common scenarios where an addendum resolved scope, staffing, or scheduling issues without reissuing the base contract.

Optica Ventures — Brian Fitzgibbons

When a scope increase required rapid staffing changes, the team issued an addendum describing new deliverables and dates.

"The interface is simple and easy-to-use for our team."
The executed addendum recorded approvals, enabled prompt invoicing, and kept the project on the revised schedule while preserving the original contract record.

Martin Properties — Tim Martin

A site-delay required new milestone dates and inspection responsibilities to be assigned to the contractor.

"I can process and execute all of these documents online with 100% compliance."
The signed addendum updated acceptance criteria, avoided a formal change order process, and provided a clear audit trail for owner and subcontractor billing reconciliation.

Frequently asked questions about execution and validity

Answers to common questions about legal effect, signatures, notarization, and storage for Project Management Support Plan Addenda.

Need help? Contact support

Can an addendum be signed electronically?
Yes. Under the federal ESIGN Act and state UETA provisions (15 U.S.C. ch. 96; UETA adopted in 49 states), electronic signatures that show intent, consent, attribution, and retention are legally enforceable, subject to limited statutory exceptions.
What makes the addendum legally valid?
A valid addendum identifies the original contract, clearly states modifications, is signed by authorized parties, and demonstrates signer intent and consent. Retain the executed record and an audit trail showing attribution and timestamp.
Who must sign the addendum?
Individuals with authority to bind their organization must sign. Where authority is delegated, provide title and role in the signature block and document delegation if required by procurement rules.
Is notarization or witnessing required?
Generally no for commercial contract amendments. Notarization is only occasionally required by state law or for specific instrument types; verify local requirements when the addendum affects real estate or power-of-attorney matters.
How long should executed addenda be kept?
Retain executed addenda for project term plus appropriate post-termination period—follow IRS (3 years, IRC §6501(a)), HIPAA (6 years, 45 CFR §164.530(j)), and any industry-specific rules.
What if a signer refuses or disputes the signature?
Preserve all audit logs, communications, and proof of authentication. Dispute resolution depends on the contract provisions; consult legal counsel and consider escalation clauses in the original agreement.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now