Is an electronic signature valid?

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

Who must sign the revision?

Only persons with delegated signature authority under the contract should sign. Check the contract’s signature authority matrix and procurement rules before accepting execution.

Do I need notarization or witnesses?

Most change orders do not require notarization or witnesses. Verify if a particular state or related document (e.g., deed) imposes special notarization or witness rules.

What supporting documents should I attach?

Attach revised drawings, RFIs, cost backup, schedules, and written directives that justify the change and support payment and schedule impacts.

How do I correct an executed revision?

Prepare a subsequent Revised Change Order that references the executed revision and clearly states corrections; obtain the same approval flow to avoid chain-of-title issues.

Where should the executed file be stored?

Store the signed PDF and audit trail in the project document management system and retain per retention policy to support audits, IRS reviews, or claims.

Electronic Signature
Templates
Project Management
Project Management Revised Change Order

Project Management Revised Change Order

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

PROJECT MANAGEMENT REVISED CHANGE ORDER

Project Identification

Project Title Project ID Client Name Service Provider Project Manager

Change Order Identification

Change Order Number: Revision Effective Date:

Original Contract Date:

Recitals

WHEREAS, the Client and Service Provider entered into a written agreement identified above (the "Agreement"); and WHEREAS, the parties have previously authorized change orders as documented; and WHEREAS, the parties desire to revise the scope, schedule and/or compensation as set forth in this Revised Change Order; the parties agree as follows.

Description of Change

Summary of Change Detailed Scope of Work (Revised) Items Explicitly Excluded (Out-of-Scope)

Deliverables and Acceptance Criteria

Deliverable 1 — Description Deliverable 1 — Acceptance Criteria Deliverable 2 — Description Deliverable 2 — Acceptance Criteria

Timeline and Milestones

Original Contract Start Date:

Revised Contract Completion Date:

Milestone 1

Completion Date:

Milestone 2

Completion Date:

Budget and Payment

Original Contract Amount: $

Total Previously Approved Change Orders: $

This Revised Change Order Amount: $

New Contract Total After Revision: $

Payment Schedule (if changed) Change Order Authorization and Change Control Process

Standard Contractual Provisions

1. Effect of Revision: Except as expressly modified by this Revised Change Order, all terms, conditions, obligations and warranties of the Agreement remain in full force and effect. To the extent of any conflict between this Revised Change Order and the Agreement, this Revised Change Order shall control with respect to the subject matter herein.

2. Warranty: Service Provider warrants that all work performed under this Revised Change Order will be performed in a competent and professional manner consistent with industry standards for projects of similar scope and complexity for a period of ninety (90) days from the date of final acceptance unless otherwise specified in the Agreement.

3. Delay and Schedule Impact: If the revised scope causes a delay to the critical path, Service Provider shall promptly notify the Client in writing and provide a revised schedule. Any time extensions shall be mutually agreed in writing and may affect compensation if expressly stated herein.

4. Limitation of Liability: Except for willful misconduct or gross negligence, neither party shall be liable to the other for consequential, incidental, special or punitive damages arising out of this Revised Change Order.

5. Confidentiality: All non-public information exchanged in connection with this Revised Change Order shall be kept confidential in accordance with the confidentiality provisions of the Agreement. The parties agree not to disclose such information except as required by law and after providing advance notice to the disclosing party where permitted.

6. Governing Law and Dispute Resolution: This Revised Change Order shall be governed by the law specified in the Agreement. The parties shall endeavor to resolve disputes first through good faith negotiation and, if unresolved, by the dispute resolution mechanism set forth in the Agreement.

Certifications and Acknowledgements

By signing below, each party certifies that it has full authority to execute this Revised Change Order, that the information contained herein is accurate to the best of its knowledge, and that this Revised Change Order will become effective upon the later of the signatures of both parties.

Client — Printed Name:

By:

Date:

Service Provider — Printed Name:

By:

Date:

What a Project Management Revised Change Order Is and when it matters

A Project Management Revised Change Order is a written amendment that modifies an earlier change order for a construction, engineering, or project services contract. It documents adjustments to scope, schedule, cost, specifications, or deliverables and links back to the original contract and the prior change order it revises. The revised change order records the reason for the change, detailed work descriptions, updated price and time impacts, and approvals by authorized representatives. When executed properly it becomes part of the contract record and governs downstream obligations and payment.

Why recording a Revised Change Order reduces disputes

A clear revised change order creates an auditable record of agreed-on changes, reduces ambiguity about responsibilities, and preserves subcontractor and owner approval history for claims or audits.

Core elements every professional Revised Change Order should include

A complete document ties the revision to prior approvals, quantifies cost and schedule impacts, and sets signatures and effective dates to avoid ambiguity.

Reference

Cite original contract and change order numbers, dates, and parties so the revision is unambiguously linked to the contract history.

Scope

Describe work added, removed, or modified in measurable terms, including drawings, specifications, or attachment references that define deliverables.

Cost Impact

Show itemized price changes, allowances, unit rates, and any contingencies; indicate whether amounts are estimates or fixed sums.

Schedule Effects

State new milestones, completion dates, durations added or deducted, and any critical-path impacts with calendar dates.

Approvals

List authorized signatories and their titles, required internal approvals, and any conditional acceptance criteria.

Change Terms

Include payment terms, retainage changes, warranty adjustments, and dispute-resolution steps tied to the revised scope.

Step-by-step: completing a Revised Change Order

Follow these steps to prepare and execute a legally enforceable revision to a project change order.

01

Identify revision: Locate original change order and assign the new revision number.
02

Document changes: Describe scope, attach supporting drawings, and quantify cost and time impacts.
03

Internal approval: Obtain required internal approvals before sending to external parties.
04

Execute and distribute: Collect signatures and circulate final executed copy to all stakeholders.

Configuring an online workflow for Revised Change Orders

Set up a consistent digital workflow to route revisions, capture approvals, and retain a complete audit trail.

Template setup	Create a reusable form with mandatory fields and attachments.
Signer order	Define sequential or parallel signing to match contract approval flow.
Conditional fields	Show cost or schedule fields only when applicable to reduce signer errors.
Authentication	Enable email or SMS codes, or stronger authentication where contract requires it.
Save as template	Save the configured workflow to ensure consistency across projects.

Where a completed Revised Change Order goes next

A final executed revision must be distributed to project stakeholders and stored in contract records for payment and claims support.

Owner: Owner receives executed copy for payment and schedule adjustments.
Contractor: Prime contractor retains the original and updates schedules and cost forecasts.
Subcontractors: Affected subcontractors should receive scopes and pricing changes.
Document control: Upload final signed version to the project repository and replace superseded versions.

Digital signing and storage considerations

Use a platform that captures signer identity, timestamps, and an immutable audit trail for legal defensibility.

Authentication: Email, SMS, or advanced options.
Audit Trail: IP, timestamp, and event log.
File formats: PDF and DOCX supported.

Who typically prepares and signs a Revised Change Order

Ensure signers are listed in the contract’s signature authority matrix to avoid later disputes about authorization.

Project managers draft scope and schedule revisions and coordinate approvals from stakeholders.
Contracts administrators review cost impacts, legal terms, and ensure authority to sign.
Owners or client representatives approve scope and release funds per contract approval rules.

Required data fields to make the revision enforceable

Parties: Full legal names

Revision ID: Unique identifier

Effective Date: MM/DD/YYYY

Scope Summary: Concise description

Cost Impact: USD amount

Signatures: Authorized signers

Typical timelines and internal deadlines for revised change orders

Track statutory notice periods and internal approval SLAs to avoid payment delays and preserve claims.

Notice to Owner:

Provide notice per contract within specified days of event.

Internal Approval SLA:

Commonly 3–10 business days for contract teams.

External Approval Window:

Owners often have 7–30 days to accept or reject.

Payment Adjustment:

Pay application inclusion typically next billing cycle.

Claims Preservation:

Preserve notices per contract to maintain entitlement.

Consequences and contract risks of incorrect revisions

Payment Delay: Late or withheld payment

Scope Disputes: Unclear work responsibility

Claim Denial: For lack of notice

Termination Exposure: Material breach risk

Liability Shift: Unintended indemnity

Audit Findings: Noncompliance with procurement rules

Common mistakes to avoid when preparing a Revised Change Order

Failing to reference the original change order number, which severs the revision from the contract history and causes interpretation disputes.
Using vague scope language like 'additional work as needed' without measurable deliverables, which invites disagreement over what was authorized.
Skipping proper authorization matrix checks and collecting signatures from personnel without delegated signing authority under the contract.
Not updating project schedules and procurement forecasts concurrently, resulting in misaligned resource commitments and delayed payments.

Comparison: eSignature platforms for executing Revised Change Orders

Select an eSignature provider that supports required authentication, audit trails, and any industry compliance requirements such as HIPAA or 21 CFR Part 11.

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

Frequently asked questions about Revised Change Orders

Answers to common procedural, legal, and digital-signing questions encountered when drafting or executing a revised change order.

Need help? Contact support

Is an electronic signature valid?
Yes. Electronic signatures are enforceable in the U.S. under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and record retention requirements are met.
Who must sign the revision?
Only persons with delegated signature authority under the contract should sign. Check the contract’s signature authority matrix and procurement rules before accepting execution.
Do I need notarization or witnesses?
Most change orders do not require notarization or witnesses. Verify if a particular state or related document (e.g., deed) imposes special notarization or witness rules.
What supporting documents should I attach?
Attach revised drawings, RFIs, cost backup, schedules, and written directives that justify the change and support payment and schedule impacts.
How do I correct an executed revision?
Prepare a subsequent Revised Change Order that references the executed revision and clearly states corrections; obtain the same approval flow to avoid chain-of-title issues.
Where should the executed file be stored?
Store the signed PDF and audit trail in the project document management system and retain per retention policy to support audits, IRS reviews, or claims.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now