Can an addendum be signed electronically?

Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided intent, consent, attribution, and reliable record retention are present.

Is notarization required for an addendum?

Typically no for commercial contract amendments, but specific jurisdictions or contract clauses may require notarization; verify state rules and the original contract.

What if a signer lacks authority?

If the signatory lacks delegated authority, the addendum may be voidable; confirm internal approval matrices before execution to prevent repudiation.

How do I document cost changes?

State amounts explicitly, indicate whether they are estimates or firm, reference invoicing terms, and include any retention or holdback provisions to tie payment to acceptance.

Can a change be retroactive?

Yes, if parties expressly agree to an effective retroactive date, but retroactive changes can affect invoicing, performance metrics, and liability periods and should be documented clearly.

How should executed addenda be stored?

Store signed PDFs with embedded audit trails in a secure contract repository, preserve metadata, and retain per applicable retention rules (IRS, HIPAA, state regulations).

Electronic Signature
Templates
Project Management
Project Change Request Addendum

Project Change Request Addendum

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

PROJECT CHANGE REQUEST ADDENDUM

Project Identification

Project Title Project ID Client Name Service Provider Project Manager

Change Request Summary

Change Request Addendum No.: Date Submitted: Requested By:

Summary Description of Change Justification / Business Reason

Scope Impact

Scope Modifications (items added, removed or revised) Out-of-Scope Items (items explicitly excluded)

Deliverables and Acceptance

Deliverables Affected Acceptance Criteria

Schedule / Timeline Impact

Original Contract Start Date: Original Contract End Date:

Proposed Revised Start Date: Proposed Revised End Date:

Milestones Affected / New Milestones

Cost / Budget Impact

Estimated Net Change in Contract Price: $ Cumulative Contract Value after Change: $

Cost Breakdown / Budget Line Items Payment / Invoice Schedule Changes

Approvals and Routing

This Addendum shall be effective only when signed by authorized representatives of both parties and, if required by the Contract, after approval by the designated funding authority. Check applicable requirements:

Requires budget or finance approval
Requires formal schedule baseline update
Requires scope re-baseline and change to project documentation

Routing / Sign-off Sequence

Change Order Process and Legal Provisions

Effect of Addendum: Upon execution by authorized representatives of the parties, this Addendum amends and modifies the terms of the underlying Contract only to the extent expressly set forth herein. All other terms and conditions of the Contract remain in full force and effect. In the event of any conflict between this Addendum and the Contract, the express terms of this Addendum shall control to the extent of the conflict.

Representations: Each party represents that the person executing this Addendum on its behalf is duly authorized to do so and that execution and delivery of this Addendum constitutes a valid and binding obligation of the party.

Warranties and Liability: Except as expressly modified by this Addendum, warranties, limitations of liability and remedies in the Contract remain unchanged. Any additional warranty obligations or liabilities arising from the change shall be set forth explicitly in the Cost Breakdown or Acceptance sections above.

Confidentiality: All information exchanged under this Addendum shall be treated in accordance with the confidentiality provisions of the Contract. Where no such provision exists, the parties agree to maintain as confidential any proprietary information disclosed for the purposes of implementing this change.

Entire Agreement: This Addendum, together with the Contract and any other executed change documents, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior understandings specific to this change.

Governing Law and Venue: The validity, interpretation and enforcement of this Addendum shall be governed by the laws of the state identified below, without regard to conflict of law principles. Exclusive venue for any disputes arising under this Addendum shall be in the courts of that state.

Governing Law (State)

Acknowledgment

By signing below, the undersigned representatives acknowledge they have read and understand the terms of this Project Change Request Addendum and have authority to bind their respective party.

Client

Printed Name:

By (Signature):

Date:

Title / Authority:

Service Provider

Printed Name:

By (Signature):

Date:

Title / Authority:

What a Project Change Request Addendum Is and When It Applies

A Project Change Request Addendum is a written amendment to an existing project contract that records agreed modifications to scope, schedule, deliverables, cost, or other material terms. It supplements the original agreement without replacing it and must reference the parent contract, describe the change in measurable detail, state any price or schedule adjustments, and include signatures from authorized parties. Properly drafted addenda reduce misunderstandings, preserve traceability of approvals, and create an auditable record for invoicing, change-order tracking, and dispute avoidance.

Why a Formal Addendum Matters for Project Controls

A clear Project Change Request Addendum protects both owner and contractor by documenting mutual consent to modifications, establishing revised obligations, and supporting invoice and schedule reconciliation. It creates an auditable decision trail useful for claims, accounting, and regulatory reviews.

Who Typically Prepares and Signs a Change Addendum

Each signer should have authority under the original contract; routing should preserve signatory order and store the executed addendum with the master contract.

Owner or client project manager — approves scope and budget changes and documents internal approvals.
Prime contractor or vendor representative — prepares technical change descriptions and cost impacts for review.
Legal or contract admin — reviews language for risk allocation, warranty effects, and signing authority.

Core Elements to Include in a Professional Addendum

A useful addendum is concise but complete: reference the original contract, state the change, quantify impacts, set new dates, and include signature and routing details.

Reference

Identify the original contract by title, date, and contract number so the amendment ties unambiguously to the parent agreement.

Change Description

Describe the modification precisely (tasks added/removed, technical specs, deliverable acceptance criteria) to avoid later interpretation disputes.

Cost Impact

State fixed dollar changes or pricing formulas, include taxes or allowances, and indicate payment timing and invoicing references.

Schedule Impact

Provide revised milestone dates, completion deadlines, liquidated damages changes, and any temporary suspension or acceleration instructions.

Approvals

List required approvers, their titles, and any internal authorization numbers; note whether executive sign-off is required.

Signatures

Provide signature blocks with printed names, titles, dates, and a statement that the parties agree to amend and continue the contract under revised terms.

Step-by-Step: Completing a Project Change Request Addendum

Follow an ordered process to ensure the addendum is authorized, clear, and retained with the contract.

01

Draft the Amendment: Summarize the change and impacts in plain, measurable terms.
02

Review Internally: Have PM, finance, and legal review for scope, cost, and risk.
03

Obtain Signatures: Collect signatures from authorized representatives in the agreed order.
04

Distribute and File: Share executed copies with stakeholders and attach to the master contract file.

Configuring an Online Workflow to Process Addenda

Set up a predictable routing workflow to reduce delays and ensure approvals are captured electronically.

Field	Configuration
Initiator	Project manager role submits change request
Approvals	Sequential approval by PM → Finance → Legal
Authentication	Email + SMS code or SSO for higher-risk changes
Storage	Auto-attach executed addendum to contract record

Where to Send and How to Route an Executed Addendum

Routing depends on contract terms: typically the original contracting parties plus internal contract administration receive final copies.

Primary Recipient: Counterparty legal or contract manager receives the executed copy.
Internal Records: Contract administration and finance receive copies for filing and billing.
Project Team: PM and key stakeholders receive notification of schedule or scope changes.
Archive: Store the executed PDF with the contract repository and version history.

Digital Signing and eSubmission Requirements

Ensure the chosen provider supports ESIGN/UETA compliance, secure transport (TLS), and at-rest encryption before sending signature requests.

Authentication: Email + access code or SSO
Audit Trail: IP, timestamp, and action log
File Formats: PDF/A or DOCX supported

Timing Considerations and Typical Deadlines

Understand deadlines that may affect change acceptance, payment, and schedule; some changes tie directly to invoicing cycles and milestone payments.

Change Request Submission:

Submit as soon as change is known to avoid schedule drift.

Approval Window:

Set a defined review period, commonly 5–15 business days.

Effective Date:

Specify when the amendment takes effect (MM/DD/YYYY).

Invoice Cutoff:

Align cost changes with the next billing cycle to prevent disputes.

Record Attachment:

Attach executed addendum to contract file within 3 business days.

Key Milestones in the Addendum Lifecycle

A sequential milestone view helps teams track the change from proposal to incorporation in project controls.

01

Submit Change Request

Initiator prepares description and cost estimate for review.

02

Internal Review

Finance and legal assess budget and risk impacts.

03

Counterparty Approval

Counterparty approves amendment or proposes revisions.

04

Execution and Archival

Both parties sign and store the executed addendum with the contract.

Common Preparation Mistakes to Avoid

Vague scope language — failing to describe work in measurable terms that tie to acceptance criteria creates disputes and scope creep.
Missing financial detail — omitting whether cost amounts are estimates, not-to-exceed, or firm leads to invoice rejection.
Incorrect signatory — using a person without delegated authority can render the addendum unenforceable and delay action.
Poor version control — not attaching the executed addendum to the master contract causes reconciliation errors and audit findings.

Consequences of an Incorrect or Unexecuted Addendum

Payment Delay: Invoices may be rejected

Scope Dispute: Work may be performed without approval

Liability Exposure: Unallocated risk remains with signer

Audit Findings: Non-compliance flagged in reviews

Contract Breach: Performance obligations may be contested

Legal Costs: Increased attorney fees

Essential Data and Privacy Requirements to Capture

Signer Identity: Full legal name and title

Sign Date: MM/DD/YYYY format

Revision Summary: Concise description of the change

Monetary Impact: Amount and payment terms

Authority Reference: Internal approval number if required

Storage Location: Repository name and file path

Quick eSignature Pricing Comparison for Processing Addenda

Compare common pricing and capability factors for eSignature vendors; signNow is listed first per comparison format to aid vendor evaluation.

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

Real-World Examples of Using an Addendum

Two brief examples show how organizations document and execute contract changes to keep projects on track.

Optica Ventures

A small portfolio manager needed quick scope clarifications for tenant build-outs.

The team executed an addendum to adjust deliverables and payment terms.
The clear amendment reduced billing disputes and allowed timely tenant move-ins while preserving the original lease terms.

Martin Properties

A property services firm used an addendum to extend completion dates after supply delays.

The addendum revised milestone dates and payment holdbacks.
Stakeholders accepted the amendment, enabling approved schedule relief and preventing a formal breach notice.

Practical Tips for Faster, More Reliable Change Addenda

Use standard clauses and clear templates to speed approval and reduce interpretation risk.

Use a Standard Template

Start from a company-approved template that references the parent contract and includes designated fields for scope, cost, schedule, and signatures.

Capture Measurable Details

Avoid vague descriptions; include deliverable criteria, test or inspection steps, and acceptance thresholds to reduce later disputes.

Maintain Version Control

Number change requests, record revision dates, and attach executed addenda to the master contract in the repository.

Authenticate Signers

Require signer authentication appropriate to the change risk (SSO or multi-factor for high-value amendments).

Frequently Asked Questions About Project Change Request Addenda

Answers to common questions about drafting, execution, and enforceability of Project Change Request Addenda.

Need help? Contact support

Can an addendum be signed electronically?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA in most states, provided intent, consent, attribution, and reliable record retention are present.
Is notarization required for an addendum?
Typically no for commercial contract amendments, but specific jurisdictions or contract clauses may require notarization; verify state rules and the original contract.
What if a signer lacks authority?
If the signatory lacks delegated authority, the addendum may be voidable; confirm internal approval matrices before execution to prevent repudiation.
How do I document cost changes?
State amounts explicitly, indicate whether they are estimates or firm, reference invoicing terms, and include any retention or holdback provisions to tie payment to acceptance.
Can a change be retroactive?
Yes, if parties expressly agree to an effective retroactive date, but retroactive changes can affect invoicing, performance metrics, and liability periods and should be documented clearly.
How should executed addenda be stored?
Store signed PDFs with embedded audit trails in a secure contract repository, preserve metadata, and retain per applicable retention rules (IRS, HIPAA, state regulations).

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now